...hmm, I still think I need to sort out /dev/fb#, but what's bwtwo to look like?
/var/log/dmesg looks acceptable: Console: switching to mono frame buffer device 142x54 fb0: bwtwo at 3.fe000000 the Debian logo is still garbled. For what it's worth, XsunMono dies after a read() as follows: Program received signal SIGSEGV, Segmentation fault. 0xd2f64 in miIntersect () (gdb) backtrace #0 0xd2f64 in miIntersect () #1 0xa96e4 in mfbCopyArea () #2 0xafa90 in mfbPutImage () #3 0xd992c in miDCInitialize () #4 0xd9c58 in miDCInitialize () #5 0xe6a18 in miSpriteInitialize () #6 0xe68cc in miSpriteInitialize () #7 0xd92a4 in miPointerUpdate () #8 0xd8f54 in miPointerInitialize () #9 0x3dd6c in DefineInitialRootWindow () #10 0x4573c in main () #11 0xe00bc46c in __libc_start_main () from /lib/libc.so.6 Anybody seen something like that? Martin > what's the incantation for the BW framebuffer of the ELC? > > I'm getting a garbled 'logo' on bootup. The Debian logo was fine when tftp'ing the 2.2.1 slink kernel. > > Also X dies, but the screen I'm seeing seems also to be garbled, like it was grayscale instead of > BW. > > I'm using a newly installed potato with the 2.2.15 kernel . The adequate X server is XsunMono > I hope. > > Is there anything going awry with the device detection on bootup? > How can I check? > > Martin > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]