You are not logged in.

#1 2008-08-12 12:35:00

ras0ir
Member
From: Ankara/Turkey
Registered: 2008-06-20
Posts: 65
Website

[solved] v86d segfault

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

#2 2008-08-15 17:04:21

setsuna
Member
From: Italy
Registered: 2008-04-10
Posts: 30

Re: [solved] v86d segfault

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

#3 2008-08-15 18:42:09

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

Re: [solved] v86d segfault

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

#4 2008-08-15 19:53:32

ras0ir
Member
From: Ankara/Turkey
Registered: 2008-06-20
Posts: 65
Website

Re: [solved] v86d segfault

Thanks shining smile
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

#5 2008-08-15 21:00:21

methuselah
Member
Registered: 2007-10-02
Posts: 570

Re: [solved] v86d segfault

ras0ir wrote:

Thanks shining smile
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

#6 2008-08-29 02:00:44

fop518
Member
Registered: 2008-08-27
Posts: 13

Re: [solved] v86d segfault

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

#7 2008-08-29 06:19:37

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

Re: [solved] v86d segfault

Just for your information, this was said in the comments of the bug report :

Thomas Bächler (brain0) wrote:

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

#8 2008-09-02 17:39:37

fop518
Member
Registered: 2008-08-27
Posts: 13

Re: [solved] v86d segfault

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

Board footer

Powered by FluxBB