[plug] Framebuffer problem

[Peter Wright]

On Mon, May 29, 2000 at 12:40:57PM +0800, Matt Kemner wrote:
> On Mon, 29 May 2000, Peter Wright wrote:
> 
> > open_framebuffer: failed to open /dev/fb0 - no such device.
> 
> > yoda:/dev# fbset 
> > open /dev/fb0: No such device
> 
> What does dmesg say?
> Does it have any errors regarding the framebuffer?

See below. No messages at all regarding the framebuffer.

> Sounds to me like framebuffer didn't load for some reason.

Yes, I have to agree now...

> Do you get the penguin logo on boot?

Nope. :-(
And I even played around with the vga settings - I tried to give VGA
0301 (just as it suggests in the Framebuffer HOWTO), but it told me
that wasn't a valid mode. Which would be consistent if the framebuffer
wasn't loaded.

yoda:/dev# dmesg 
Linux version 2.2.15 (root at rocket) (gcc version 2.95.2 20000313
(Debian GNU/Linux)) #2 Mon May 29 11:15:58 WST 2000
Detected 299948033 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 598.02 BogoMIPS
Memory: 128128k/131072k available (948k kernel code, 416k reserved,
1524k data, 56k init)
Dentry hash table entries: 16384 (order 5, 128k)
Buffer cache hash table entries: 131072 (order 7, 512k)
Page cache hash table entries: 32768 (order 5, 128k)
CPU: Intel Mobile Pentium II stepping 0a
Checking 386/387 coupling... OK, FPU using exception 16 error
reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch at atnf.csiro.au)

[ rest snipped as nothing relevant ]

So I did get a message about the MTRR, but SFA about the vesafb. :-/
It's certainly starting to look like the framebuffer stuff just flat
out isn't in the kernel. Strange, as I would have thought that the
/proc/devices having an fb device listed would mean it _is_ in the
kernel.... Can anyone correct me on this?

The other (2.2.14) machine has been up for over 63 days, so it doesn't
have anything relevant to the boot left in its dmesg output (just a
lot of smb_retry errors).

> My dmesg output says:
> 
> matroxfb: Matrox Millennium G200 (AGP) detected
> matroxfb: MTRR's turned on
> matroxfb: 1152x900x32bpp (virtual: 1152x1819)
> matroxfb: framebuffer at 0xDF000000, mapped to 0xd0005000, size 8388608
> Console: switching to colour frame buffer device 144x56
> fb0: MATROX VGA frame buffer device

Dammit, now _that_ looks meaningful and good.
I want a dmesg like that *sad look*. :(

> Everything else you've posted checks out (device major/minor etc)
> 
>  - Matt

Thanks - I guess I'll go back and have a hard look at my kernel
config - maybe see if I can see any reference to framebuffer stuff in
my System.map?

Pete, clutching at straws.
-- 
http://cygnus.uwa.edu.au/~pete/

--
"Open Standards, Open Documents, and Open Source"

  -- Scott Bradner (Open Sources, 1999 O'Reilly and Associates)