FS#9482 - uvesafb support: include v86d and rebuild klibc
Attached to Project:
Arch Linux
Opened by Giorgio Lando (patroclo7) - Thursday, 07 February 2008, 09:19 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 06 April 2008, 09:09 GMT
Opened by Giorgio Lando (patroclo7) - Thursday, 07 February 2008, 09:19 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 06 April 2008, 09:09 GMT
|
Details
Description:
The kernel 2.6.24 in testing include the new uvesafb driver as a module. However, in order to use it, two actions are needed from the user and could perhaps be done from the distro (when 2.6.24 hits testing): 1) klibc needs to be rebuilt against a kernel tree including uvesafb (so against a 2.6.24 kernel), as stated in http://dev.gentoo.org/~spock/projects/uvesafb/ 2) uvesafb needs a regulating daemon, called v86d, see again http://dev.gentoo.org/~spock/projects/uvesafb/. May be this could be included in an official repo since it is a needed in order to use a kernel module in the stock kernel. It is actually in the AUR. The package in the AUR includes also the initcpio hook needed to run v86d in early userspace. However, this initcpio could be unnecessary, for me it is enough that the user lists the regulating daeomon in BINARIES in /etc/mkinitcpio.conf. And actually the possible scenarios with uvesafb are heterogeneous, as you can see in the wiki article for uvesafb: http://wiki.archlinux.org/index.php/Uvesafb, so perhaps it is enough to package the v86d regulating daemon and leaves to the user the freedom to define everything else. Additional info: * package version(s): kernel26-2.6.24, klibc-1.5-3, v86d-0.1.3 Steps to reproduce: |
Closed by Roman Kyrylych (Romashka)
Sunday, 06 April 2008, 09:09 GMT
Reason for closing: Implemented
Sunday, 06 April 2008, 09:09 GMT
Reason for closing: Implemented
::Loading Initramfs
-/init: 44: replace: not found
-/init: 44: replace: not found
export: 44: bad variable name
I am going to add this to testing as soon as I finished updating klibc-udev (I also built the old klibc-udev version against the new klibc for testing purposes). Please be patient for another day or so.
I also built v86d. I think the messages I get in dmesg are now more sane, but 'modprobe uvesafb' still gives me a blank screen and seems to freeze my machine.
this is the output of the "file" command for v86d_klibc
v86d_klibc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked (uses shared libs), stripped
and this is the output of the "file" comma[iceman81@wopr sbin]$ file v86d-ice
v86d-ice: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.16, statically linked, stripped
maybe that "uses shared libs" could be the problem...
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22
i use 915resolution_static BEFORE loading uvesafb module in order to use 1280x800 resolution.
to do so i patched the init file in the ramdisk.
i also patched initscripts in order to use silent splash screen during the boot.
v86d-ice works even with all this tricks.
i changed /lib/initcpio/install/v86d and /lib/initcpio/hooks/v86d.
now it works perfectly. i think all the packages about v86d on aur are quite useless now.
bye
giuseppe
v86d (0.1 KiB)
bug 9813