Have installed uvesafb but nothing happens.

Message

XrateR · Post by **XrateR** » Sat Nov 01, 2008 10:03 am

Hello,
I have just done all steps in Spock's uvesafb guide. But then I rebooted nothing happen.
The only line I added to my lilo.conf is this one:

Code: Select all

append="video=uvesafb:1024x600-32,mtrr:3,ywrap"

Is that wrong?

\\ xrater

swimmer · Post by **swimmer** » Sat Nov 01, 2008 10:17 am

Do you use the latest klibc and v86d? Also did you set CONFIG_INITRAMFS_SOURCE correctly?

HTH
swimmer

XrateR · Post by **XrateR** » Sat Nov 01, 2008 10:26 am

swimmer wrote:Do you use the latest klibc and v86d? Also did you set CONFIG_INITRAMFS_SOURCE correctly?

HTH
swimmer

I emerge the newest version in portage and set CONFIG_INITRAMFS_SOURCE to "/usr/share/v86d/initramfs"

swimmer · Post by **swimmer** » Sat Nov 01, 2008 11:39 am

What does "dmesg|grep -i vesa" show you? I don't use lilo so I can't help you on this part ...

Greetz
swimmer

XrateR · Post by **XrateR** » Sat Nov 01, 2008 1:35 pm

This is the output from " dmesg|grep -i vesa ":

Code: Select all

exie ~ # dmesg|grep -i vesa
[    0.000000] Kernel command line: auto BOOT_IMAGE=Gentoo ro root=803 video=uvesafb:1024x600-32,mtrr:3,ywrap
[    0.308376] uvesafb: Intel Corporation, Intel(r) 82945GM Chipset Family Graphics Controller, Hardware Version 0.0, OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS, VBE v3.0
[    0.322531] uvesafb: VBIOS/hardware supports DDC2 transfers
[    0.335115] uvesafb: monitor limits: vf = 61 Hz, hf = 38 kHz, clk = 45 MHz
[    0.335374] uvesafb: scrolling: redraw
[    0.421019] uvesafb: framebuffer at 0xd0000000, mapped to 0xf8a00000, using 3750k, total 7872k
[    0.421214] fb0: VESA VGA frame buffer device
exie ~ #

Edit: Here is my lilo.conf also:

Code: Select all

compact
lba32

boot = /dev/sda
image = /boot/bzImage_new
        root = /dev/sda3
        label = Gentoo
        read-only # read-only for checking

append = "video=uvesafb:1024x600-32,mtrr:3,ywrap"

swimmer · Post by **swimmer** » Tue Nov 04, 2008 11:28 am

Hmm - can't see any errors ...

What do you expect that happens?

Greetz
swimmer

bbgermany · Post by **bbgermany** » Tue Nov 04, 2008 11:52 am

As the howto of Spock tells you, check out: /sys/class/graphics/fb0/modes for the supported resolutions.

bb

njcwotx · Post by **njcwotx** » Thu Nov 06, 2008 2:33 am

append="video=uvesafb:1024x600-32,mtrr:3,ywrap"

try taking out the append=" "

just put

Code: Select all

video=uvesafb:1024x600-32,mtrr:3,ywrap

that is the way it is on mine. Make sure you "emerge x86v klibc" too. Looks like you set the initramfs too. You should also see that framebuffer support should be loaded.

I looked at my line it is set like this.

kernel /boot/kernel-2.6.23-gentoo-r4 root=/dev/sda3 video=vesafb:1024x768-32@60 splash=silent,theme:emergence quiet
initrd /boot/fbsplash-emergence

Master of the Darkside · Thu Nov 06, 2008 9:31 am

provided you got everything right with the config, try disabling "Processor type and features -> Tickless system" and rebuild your kernel.

bbgermany · Post by **bbgermany** » Thu Nov 06, 2008 4:55 pm

njcwotx wrote:kernel /boot/kernel-2.6.23-gentoo-r4 root=/dev/sda3 video=vesafb:1024x768-32@60 splash=silent,theme:emergence quiet
initrd /boot/fbsplash-emergence

if you use grub, this is ok. but XrateR is using lilo, so append... is right.

bb

njcwotx · Post by **njcwotx** » Fri Nov 07, 2008 10:10 pm

lol, I just assumed everyone used grub

XrateR · Post by **XrateR** » Sun Nov 16, 2008 12:10 pm

Okey now this thing starts to annoying me.
I don't know that I missing, but it is something.

Here is my status and what I have done:

1. I followed Spock's guide and have dubble checked everything.
2. I configure my lilo:

Code: Select all

compact
lba32

boot = /dev/sda
image = /boot/kernel-2.6.27-gentoo-r2
        root = /dev/sda3
        label = Gentoo
        read-only # read-only for checking

append = "video=uvesafb:800x600-32,mtrr:3,ywrap"
initrd /boot/initramfs

3. dmesg|grep -i vesa output:

Code: Select all

[    0.000000] Kernel command line: auto BOOT_IMAGE=Gentoo ro root=803 video=uvesafb:1024x600-32,mtrr:3,ywrap
[    0.311732] uvesafb: Intel Corporation, Intel(r) 82945GM Chipset Family Graphics Controller, Hardware Version 0.0, OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS, VBE v3.0
[    0.351630] uvesafb: VBIOS/hardware supports DDC2 transfers
[    0.364584] uvesafb: monitor limits: vf = 61 Hz, hf = 38 kHz, clk = 45 MHz
[    0.364960] uvesafb: scrolling: redraw
[    0.480682] uvesafb: framebuffer at 0xd0000000, mapped to 0xf8a00000, using 3750k, total 7872k
[    0.480876] fb0: VESA VGA frame buffer device

A part from this I have tried,
- different resolutions
- without the initrd line
- copy the initramfs to /boot from /usr/share/v86d/initramfs

My question is if you need to do something more besides Spock's guide?
Do you need splashutils too or to do something else?

\\ xrater

mljohns4 · Post by **mljohns4** » Sat Nov 22, 2008 3:49 am

I'm currently having similar difficulties and was curious if you would be willing to do a

Code: Select all

cat /var/log/messages | grep -i v86d

and see what that returns. I would be interested in comparing your results to mine, which I have captured in this post:

http://forums.gentoo.org/viewtopic-t-71 ... -v86d.html

XrateR · Post by **XrateR** » Sun Nov 23, 2008 5:04 pm

mljohns4 wrote:I'm currently having similar difficulties and was curious if you would be willing to do a

Of course!

Code: Select all

exie ~ # cat /var/log/messages | grep -i v86d
Nov  8 18:11:35 exie [    0.308963] uvesafb: failed to execute /sbin/v86d
Nov  8 18:11:35 exie [    0.309081] uvesafb: make sure that the v86d helper is installed and executable
Nov  8 18:44:00 exie [    0.309592] uvesafb: failed to execute /sbin/v86d
Nov  8 18:44:00 exie [    0.309704] uvesafb: make sure that the v86d helper is installed and executable
Nov  9 18:38:56 exie [    0.309084] uvesafb: failed to execute /sbin/v86d
Nov  9 18:38:56 exie [    0.309195] uvesafb: make sure that the v86d helper is installed and executable
Nov  9 19:01:09 exie [    0.302052] uvesafb: failed to execute /sbin/v86d
Nov  9 19:01:09 exie [    0.302164] uvesafb: make sure that the v86d helper is installed and executable
Nov  9 22:55:07 exie [    0.308000] uvesafb: failed to execute /sbin/v86d
Nov  9 22:55:07 exie [    0.308119] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 08:02:38 exie [    0.308994] uvesafb: failed to execute /sbin/v86d
Nov 10 08:02:38 exie [    0.309111] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 09:44:30 exie [    0.303032] uvesafb: failed to execute /sbin/v86d
Nov 10 09:44:30 exie [    0.303142] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 13:10:09 exie [    0.304180] uvesafb: failed to execute /sbin/v86d
Nov 10 13:10:09 exie [    0.304293] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 13:48:09 exie [    0.308102] uvesafb: failed to execute /sbin/v86d
Nov 10 13:48:09 exie [    0.308212] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 13:59:08 exie [    0.308027] uvesafb: failed to execute /sbin/v86d
Nov 10 13:59:08 exie [    0.308140] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 15:08:03 exie [    0.307025] uvesafb: failed to execute /sbin/v86d
Nov 10 15:08:03 exie [    0.307136] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 15:34:35 exie [    0.304483] uvesafb: failed to execute /sbin/v86d
Nov 10 15:34:35 exie [    0.304596] uvesafb: make sure that the v86d helper is installed and executable
Nov 10 19:06:14 exie [    0.302989] uvesafb: failed to execute /sbin/v86d
Nov 10 19:06:14 exie [    0.303108] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 10:24:34 exie [    0.302600] uvesafb: failed to execute /sbin/v86d
Nov 11 10:24:34 exie [    0.302712] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 12:40:17 exie [    0.308044] uvesafb: failed to execute /sbin/v86d
Nov 11 12:40:17 exie [    0.308156] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 13:35:50 exie [    0.303599] uvesafb: failed to execute /sbin/v86d
Nov 11 13:35:50 exie [    0.303712] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 13:57:12 exie [    0.304118] uvesafb: failed to execute /sbin/v86d
Nov 11 13:57:12 exie [    0.304230] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 15:11:11 exie [    0.307421] uvesafb: failed to execute /sbin/v86d
Nov 11 15:11:11 exie [    0.307533] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 16:41:22 exie [    0.304524] uvesafb: failed to execute /sbin/v86d
Nov 11 16:41:22 exie [    0.304635] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 18:38:17 exie [    0.304565] uvesafb: failed to execute /sbin/v86d
Nov 11 18:38:17 exie [    0.304677] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 18:21:44 exie [    0.306502] uvesafb: failed to execute /sbin/v86d
Nov 11 18:21:44 exie [    0.306614] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 19:19:26 exie [    0.305060] uvesafb: failed to execute /sbin/v86d
Nov 11 19:19:26 exie [    0.305172] uvesafb: make sure that the v86d helper is installed and executable
Nov 11 19:24:45 exie [    0.308118] uvesafb: failed to execute /sbin/v86d
Nov 11 19:24:45 exie [    0.308229] uvesafb: make sure that the v86d helper is installed and executable

Hmm, wierd date. But there you have it.

staffan · Post by **staffan** » Sun Nov 23, 2008 7:30 pm

I'm not able to help, unfortunately, but I have exactly the same problem.

When I looked for /var/log/messages, I didn't find anything (not even the file) so I can't help with that and right now, my Gentoo box is compiling X so it will be busy for a while.

If anyone wants to see some output from my system, I'll be happy to provide it as soon as it's stopped compiling.

dtjohnst · Post by **dtjohnst** » Sun Nov 23, 2008 9:48 pm

bbgermany wrote:As the howto of Spock tells you, check out: /sys/class/graphics/fb0/modes for the supported resolutions.

bb

Did you try this suggestion from bb? I know you said you tried "other resolutions", but were they supported?

XrateR · Post by **XrateR** » Mon Nov 24, 2008 6:16 am

dtjohnst wrote:
bbgermany wrote:As the howto of Spock tells you, check out: /sys/class/graphics/fb0/modes for the supported resolutions.

bb
Did you try this suggestion from bb? I know you said you tried "other resolutions", but were they supported?

Yes I have.

mljohns4 · Post by **mljohns4** » Wed Nov 26, 2008 5:19 am

You appear to have an error similar to mine within your syslog.

Check out my other post and see if the solution I presented there is of any help.

http://forums.gentoo.org/viewtopic-t-71 ... -v86d.html

XrateR · Post by **XrateR** » Wed Nov 26, 2008 5:26 pm

mljohns4 wrote:You appear to have an error similar to mine within your syslog.

Check out my other post and see if the solution I presented there is of any help.

http://forums.gentoo.org/viewtopic-t-71 ... -v86d.html

I have already check that. =(

dtjohnst · Post by **dtjohnst** » Wed Nov 26, 2008 11:27 pm

Did v86d emerge cleanly? If you're running a pure 64-bit system, you may need to compile it with the x86emu USE flag.