You are not logged in.
Pages: 1
Hi,
I'd like to use uvesafb, so i compiled with it 'M'
I've already installed v86d from testing repository (using ABS)
But strangely i got segfault:
(from dmesg)
v86d[63]: segfault at 8049ffc ip 08049aeb sp bfa478c0 error 7 in v86d[8048000+2000]
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
/etc/modprobe.d/uvesafb content:
options uvesafb mode=1024x768-32 scroll=ywrap
Any ideas?
Is it related to the BIOS?
Last edited by ras0ir (2008-08-15 19:53:46)
Offline
Same problem here (arch64), after some search, it seems related to some changes in the kernel (2.6.25->2.6.26) that broke uvesafb (at least for us).
I didn't find a solution yet.
Offline
Oh, so there are actually people using v86d?
I reported this 20 days ago, not one single comment :
http://bugs.archlinux.org/task/11014
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Thanks shining
I've replaced add_binary "/sbin/v86d_klibc" "/sbin/v86d" with add_binary "/sbin/v86d" in /lib/initcpio/install/v86d now it's working.
Offline
Thanks shining
I've replaced add_binary "/sbin/v86d_klibc" "/sbin/v86d" with add_binary "/sbin/v86d" in /lib/initcpio/install/v86d now it's working.
my dmesg still says this after doing the fix above:
uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executable
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22
$ pacman -Q v86d
v86d 0.1.5.2-1
This is on the 2.6.27-rc1 zenmm kernel in the AUR... uvesafb was compiled as yes "*".
Offline
I am also getting that mesg after following the wiki instructions.
i get the exact line about v86d and the same 3 about uvesafb.
i tried removing the /sbin/v86d_klibc as suggested above, but that didnt do anything.
thoughts?
Offline
Just for your information, this was said in the comments of the bug report :
Again, adding v86d instead of v86d_klibc is a bad idea and will give you a much bigger initramfs image.
There is currently no known way to get v86d_klibc working on 686.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I was getting the exact same error even after removing /sbin/v86d_klibc...
i resolved the issue by changing the order of my hooks in mkinitcpio.conf to
HOOKS="base udev 915resolution autodetect pata scsi sata v86d usbinput keymap filesystems"
I believe just moving v86d after autodetect and sata did the trick.
go figure.
-m
Offline
Pages: 1