On Tue, Apr 20, 2004 at 11:53:58AM -0400, andrew burd wrote: > does it appear in dmesg output? yep, seems completely normal to me:
... drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub atyfb: 3D RAGE (XL) [0x4752 rev 0x27] 8M SDRAM, 29.498928 MHz XTAL, 230 MHz PLL, 100 Mhz MCLK fb0: ATY Mach64 frame buffer device on PCI atyfb: 3D RAGE (XL) [0x4752 rev 0x27] 8M SGRAM, 29.498928 MHz XTAL, 230 MHz PLL, 100 Mhz MCLK fb1: ATY Mach64 frame buffer device on PCI ikconfig 0.7 with /proc/config* Initializing Cryptographic API ... and lspci shows: 0000:00:13.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 0000:01:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) On 2.4.24, con2fbmap just works fine. On 2.6.5, 'con2fbmap 6 1' from console 1 says: Console: switching to colour frame buffer device 144x56 and returns my prompt (however, my 2nd monitor stays black). 'con2fbmap 1 1' from console 1 says nothing and 2nd monitor stays black (prompt doesn't return though, and I can't see what I type). Then typing 'con2fbmap 1 0' doesn't return my console on fb0, and I have to login via ssh and reboot my machine (reboot -f, as normal reboot doesn't work). If I login via ssh from a cold boot, and then type 'con2fbmap 1 1', it just returns my prompt, and 2nd screen stays blank (though if I type on console 1, the screen isn't updated anymore). However, if I then type 'con2fbmap 1 0' from the ssh session, my console does switch back to fb0, and suddenly console 1 gets updated with 2 'Console: switching to colour frame buffer device 144x56' messages. So, I guess this is a kernel issue, and not X. Admar
