Re: Get vesafb to work (was: nvidia-drivers in testing)
On Mon, Oct 29, 2001 at 05:55:02PM +0100, Jan Ulrich Hasecke wrote:
| "Daniel T. Chen" <chenda@cs.unc.edu> writes:
|
| > Rumours are that vesafb works just fine, though.
|
| Ok, I compiled a new kernel 2.4.12, disable rivafb and enable
| vesafb. All problems with the new nvidia-drivers seems to be gone.
|
| But I cannot get the vesafb to work.
|
| After booting there is no Tux-Logo anymore and when I try to fbset
| something I get the error: cannot open /dev/fb0
|
| which is there
| ls -l
| crw--w--w- 1 root tty 29, 0 30. Nov 2000 /dev/fb0
This only means there is an inode with that name. The existence of
device files is meaningless unless you are using devfs.
| Do I miss something? This is my .config
What about bootloader config? Add "vga=0x31A" to your kernel command
line.
-D
Reply to: