LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   VESA problem in kernel log - what does it mean? (https://www.linuxquestions.org/questions/linux-hardware-18/vesa-problem-in-kernel-log-what-does-it-mean-211580/)

vincebs 07-30-2004 03:22 PM

VESA problem in kernel log - what does it mean?
 
Hi everyone, I was browsing through my /var/log/messages file when I found the following line:

Jul 30 15:58:46 localhost kernel: vesafb: probe of vesafb0 failed with error -6

I was wondering what this means. I browsed on the Internet and found that VESA deals with video cards. I am running an ATI Rage 128 PRO card. When I type lsmod, I find that I'm running the r128 module but other than that I can't find any mention of the card in any of the /var/log files.

And if this has anything to do with it, I also get this message earlier on:

agpgart: Detected an Intel i815 Chipset, but could not find the secondary device.


What can I do to eliminate these messages?

Thanks,

Vince

jomen 07-31-2004 07:32 AM

How do you boot your machine - with a boot-loader? - which one are you using?

I use lilo - and do have the (almost) same card:

My lilo.conf looks like this:

----------------------

boot=/dev/hda

map=/boot/map-bmp
install=/boot/boot-bmp.b

bitmap=/boot/ins64a.bmp
bmp-colors=14,11,,15,9,0
bmp-table=21,287p,2,4,175p
bmp-timer=73,29,12,8,0

prompt
timeout=50


image=/boot/linux-2.6.7
label=linux-2.6.7
root=/dev/hda2
append="video=aty128fb:1024x768"
read-only



image=/boot/lfskernel
label=linux-2.4.24
root=/dev/hda2
append="video=aty128fb:1024x768"
read-only


other=/dev/hda1
label=Windows-XP

--------------

i.e. I appended this command to get a graphics-console with dimensions 1024x768 - very nice:

append="video=aty128fb:1024x768"

vincebs 08-02-2004 01:43 PM

I use GRUB. So you don't have this problem?

rjlee 08-02-2004 02:44 PM

This probably isn't related to the boot-loader, lilo or grub.

vesafb is the framebuffer device for a generic VESA graphics card, and is used for things like showing animation on a virtual terminal. If you're using X windows, not having vesafb isn't going to be much of a problem.

The best solution is to switch to the framebuffer device for the actual graphics card you're using.

jomen 08-02-2004 04:40 PM

Oh - yes rjlee - you are probably right...and you are not...

This is related to the boot-loader in the way, that it is right there, where you tell it to give the option to the kernel, what framebuffer-device (and with what options to it) you want the kernel to be using....
It's not related to it, because you could always later switch to that framebuffer-device - at least thats what I think you should be able to do. Not sure if this actually works...
But I do think, that doing it via lilo (or the boot loader in general and its ability to pass options to the kernel) is the more direct and more elegant way...

...and NO - I do not have this problem - but is it a problem ? Or is it just an error message?

rjlee 08-03-2004 03:21 AM

Unless you have bugs in the framebuffer device, you should be able to switch after booting but your monitor won't work between unloading the vesafb module and loading the other one.

It is an error message, in that things like svgalib are likely to stop working; you probably won't be able to show graphics or animation on a terminal without actually running X windows.

As to whether that's a problem this depends on if you find yourself wanting to do that or not.

vincebs 08-03-2004 02:02 PM

How do I switch to the frame buffer device for my ATI card?

Would any of you know how to setup the frame buffer kernel parameter in GRUB?


All times are GMT -5. The time now is 10:31 PM.