Re: sid: Console problems after starting X
On Fri, 2010-09-03 at 00:58 -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. thanks, Joel -- Joel Roth -- Passing along a tip from Wayne Topa that helped me. maybe it will help you. I did a dist-update a while back using a stock kernel had this same issue ,I think?? Do dpkg -l console-setup if you don't have it installed, install it. HTH Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284046625.4792.5.ca...@beast.johnwfoster.info
Re: sid: Console problems after starting X
On Fri, 3 Sep 2010 00:58:21 -1000 Joel Roth jo...@pobox.com wrote: [...] What video card/driver are you using? -- Rares Aioanei debian.dev.list -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100906101456.3089ea1d.debian.dev.l...@localhost.localdomain
Re: sid: Console problems after starting X
On Mon, Sep 06, 2010 at 10:14:56AM +0300, Rares Aioanei wrote: On Fri, 3 Sep 2010 00:58:21 -1000 Joel Roth jo...@pobox.com wrote: [...] What video card/driver are you using? -- Rares Aioanei debian.dev.list The card is: lspci | grep -i radeon 01:05.0 VGA compatible controller: ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics] The driver, I don't know. You can maybe find it in the /var/log/Xorg.0.log file pasted into a previous mail. The problem seemed to be solved by going to a stock kernel. Thanks for your questions. Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100906224711.ga19...@sprite
Re: sid: Console problems after starting X
On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 01:35:28PM +0300, Andrei Popescu wrote: On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. Mahalo Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904112051.gb2...@sprite
Re: sid: Console problems after starting X
On Sat, 04 Sep 2010 06:35:28 -0400 (EDT), Andrei Popescu wrote: On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Nice work, Andrei! -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1948183613.604400.1283605583354.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Sb, 04 sep 10, 09:06:23, Stephen Powell wrote: Nice work, Andrei! Not fair, you did the heavy lifting :) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 07:04:58PM +0300, Andrei Popescu wrote: On Sb, 04 sep 10, 09:06:23, Stephen Powell wrote: Nice work, Andrei! Not fair, you did the heavy lifting :) Both deserving of a beer, if not a pizza as well, to be collectible at some future FTF. -j Regards, Andrei -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904190356.gb5...@sprite
Re: sid: Console problems after starting X
Hey, On Sat, 4 Sep 2010 01:20:51 -1000 Joel Roth jo...@pobox.com wrote: Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. I think the cause of the problem is that there was just an xorg and kernel update, this may have also updated the ATI driver, and as far i understand it, due to KMS, you have to upgrade the kernel modules in lockstep with the userspace bytes or unhappy things happen, like this. (I have very little experience with ATI and mainline graphics drivers, so I may be wrong! caveat emporium!) Mahalo Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic If you still want to build your own kernel, build it off the updated debian src, or build the kernel modules into there own package. Or if you want to use a newer mainline, think about building the ati driver as well ;) -- Regards, Angus Hedger Debian GNU/Linux User PGP Public Key 0xEE6A4B97 signature.asc Description: PGP signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 08:37:55PM +0100, Angus Hedger wrote: Hey, On Sat, 4 Sep 2010 01:20:51 -1000 Joel Roth jo...@pobox.com wrote: Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. I think the cause of the problem is that there was just an xorg and kernel update, this may have also updated the ATI driver, and as far i understand it, due to KMS, you have to upgrade the kernel modules in lockstep with the userspace bytes or unhappy things happen, like this. (I have very little experience with ATI and mainline graphics drivers, so I may be wrong! caveat emporium!) Mahalo There do seem to be some kernel options that needed to be enabled, hence my success using a stock kernel. Thanks! Joel Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic If you still want to build your own kernel, build it off the updated debian src, or build the kernel modules into there own package. Or if you want to use a newer mainline, think about building the ati driver as well ;) -- Regards, Angus Hedger Debian GNU/Linux User PGP Public Key 0xEE6A4B97 -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904210255.ga2...@sprite
sid: Console problems after starting X
Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. thanks, Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903105821.ga3...@sprite
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Okay, here is one start. A boot message: udevd-work[905] kernel provided name 'uinput' and NAME='input/uinput' disagree. Please use SYMLINK+= or change kernel to provide proper name. This looks like a warning, not a failure. Another piece of the puzzle... I just did a dist-upgrade. (And another brokenness, suspend works once, second time is black screen (no backlight.) I should have known better not to dist-upgrade a well functioning system.) Regards, thanks, Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903105821.ga3...@sprite -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903183300.gc3...@sprite
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Yeah, that happened to me too, a while ago. It's the X driver. Specifically, it's the KMS settings that are messing you up. I hate KMS. It does solve certain problems for developers, but causes other problems for users. Maybe in a few years all these KMS-related bugs will get sorted out. But for now, they are a pain. How to fix it depends on your chipset. In one case, I had an nvidia card, and the upgrade switched me from the nv driver to the nouveau driver. I could get around it by blacklisting the nouveau driver and creating an explicit /etc/X11/xorg.conf file that specifies driver = nv in the appropriate place. For other chipsets, such as Intel, you may be able to set a module parameter like kms=0, or some such thing. Search the internet for your card manufacturer, Linux, and KMS, and maybe you'll find something. These techniques are only a temporary stopgap measure. Eventually, there will be no option. You will either have to use KMS or not use an X server at all. Oh joy. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1744286447.595363.1283545337251.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 04:22:17PM -0400, Stephen Powell wrote: On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Yeah, that happened to me too, a while ago. It's the X driver. Specifically, it's the KMS settings that are messing you up. I hate KMS. It does solve certain problems for developers, but causes other problems for users. Maybe in a few years all these KMS-related bugs will get sorted out. But for now, they are a pain. Good lead! For example, we have LKML posts such as: Re: Resume problem with radeon+KMS (2.6.34-rc2 and before) http://lkml.indiana.edu/hypermail/linux/kernel/1003.2/02225.html Which hits one of my problems as well. FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.833236] [drm] Initialized drm 1.1.0 20060810 [ 1478.934354] [drm] radeon kernel modesetting enabled. [ 1478.934483] radeon :01:05.0: setting latency timer to 64 [ 1478.939239] [drm] radeon: Initializing kernel modesetting. [ 1478.939410] [drm] register mmio base: 0x9630 [ 1478.939415] [drm] register mmio size: 65536 [ 1478.945526] ATOM BIOS: Tos_SCT10AP_MC [ 1478.945576] [drm] Clocks initialized ! [ 1478.945969] [drm] Detected VRAM RAM=256M, BAR=256M [ 1478.945978] [drm] RAM width 32bits DDR [ 1478.946151] [TTM] Zone kernel: Available graphics memory: 899812 kiB. [ 1478.946186] [drm] radeon: 256M of VRAM memory ready [ 1478.946191] [drm] radeon: 512M of GTT memory ready. [ 1478.946257] [drm] radeon: irq initialized. [ 1478.946263] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration [ 1479.057510] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057517] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057530] [drm] Enabling audio support [ 1479.057850] [drm] Radeon Display Connectors [ 1479.057855] [drm] Connector 0: How to fix it depends on your chipset. In one case, I had an nvidia card, and the upgrade switched me from the nv driver to the nouveau driver. I could get around it by blacklisting the nouveau driver and creating an explicit /etc/X11/xorg.conf file that specifies driver = nv in the appropriate place. For other chipsets, such as Intel, you may be able to set a module parameter like kms=0, or some such thing. Search the internet for your card manufacturer, Linux, and KMS, and maybe you'll find something. These techniques are only a temporary stopgap measure. Eventually, there will be no option. You will either have to use KMS or not use an X server at all. Oh joy. I expect it will be debugged in time. Regards, Joel -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1744286447.595363.1283545337251.javamail.r...@md01.wow.synacor.com -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903205759.ga4...@sprite
Re: sid: Console problems after starting X
On Fri, 03 Sep 2010 16:57:59 -0400 (EDT), Joel Roth wrote: FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.833236] [drm] Initialized drm 1.1.0 20060810 [ 1478.934354] [drm] radeon kernel modesetting enabled. [ 1478.934483] radeon :01:05.0: setting latency timer to 64 [ 1478.939239] [drm] radeon: Initializing kernel modesetting. [ 1478.939410] [drm] register mmio base: 0x9630 [ 1478.939415] [drm] register mmio size: 65536 [ 1478.945526] ATOM BIOS: Tos_SCT10AP_MC [ 1478.945576] [drm] Clocks initialized ! [ 1478.945969] [drm] Detected VRAM RAM=256M, BAR=256M [ 1478.945978] [drm] RAM width 32bits DDR [ 1478.946151] [TTM] Zone kernel: Available graphics memory: 899812 kiB. [ 1478.946186] [drm] radeon: 256M of VRAM memory ready [ 1478.946191] [drm] radeon: 512M of GTT memory ready. [ 1478.946257] [drm] radeon: irq initialized. [ 1478.946263] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration [ 1479.057510] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057517] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057530] [drm] Enabling audio support [ 1479.057850] [drm] Radeon Display Connectors [ 1479.057855] [drm] Connector 0: Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/123733784.596256.1283548289546.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 05:11:29PM -0400, Stephen Powell wrote: On Fri, 03 Sep 2010 16:57:59 -0400 (EDT), Joel Roth wrote: FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. I installed firmware-linux-nonfree, and the *ERROR* message is gone. Also, the 'disabling GPU acceleration' message is gone. Which sounds like it can only be good. :-) However I have the same issue as before: First switch from X to virtual console: small font. Next switch: black screen. Thanks for your help with this. Joel -- .''`. Stephen Powell : :' : `. `'` `- -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903213211.ga2...@sprite
Re: sid: Console problems after starting X
On Fri, 03 Sep 2010 17:32:12 -0400 (EDT), Joel Roth wrote: On Fri, Sep 03, 2010 at 05:11:29PM -0400, Stephen Powell wrote: Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. I installed firmware-linux-nonfree, and the *ERROR* message is gone. Also, the 'disabling GPU acceleration' message is gone. Which sounds like it can only be good. :-) However I have the same issue as before: First switch from X to virtual console: small font. Next switch: black screen. Thanks for your help with this. Well, that needed to be done anyway. Unfortunately, it was not sufficient to solve the problem. But it's a step in the right direction. Please post the output of your /var/log/Xorg.0.log file. Maybe it will give me some ideas. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1313416886.599388.1283560530317.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 08:35:30PM -0400, Stephen Powell wrote: On Fri, 03 Sep 2010 17:32:12 -0400 (EDT), Joel Roth wrote: On Fri, Sep 03, 2010 at 05:11:29PM -0400, Stephen Powell wrote: Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. I installed firmware-linux-nonfree, and the *ERROR* message is gone. Also, the 'disabling GPU acceleration' message is gone. Which sounds like it can only be good. :-) However I have the same issue as before: First switch from X to virtual console: small font. Next switch: black screen. Thanks for your help with this. Well, that needed to be done anyway. Unfortunately, it was not sufficient to solve the problem. But it's a step in the right direction. Please post the output of your /var/log/Xorg.0.log file. Maybe it will give me some ideas. Okay, here goes. I also observe that I can start X once. After killing it once, it won't start again. Regards, Joel = /var/log/Xorg.0.log === X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux sprite 2.6.33.2 #1 SMP Wed Jun 16 03:35:14 HST 2010 x86_64 Kernel command line: root=/dev/sda8 ro smp single Build Date: 24 August 2010 02:59:40PM xorg-server 2:1.7.7-4 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Sep 3 16:51:09 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No device specified for screen Default Screen Section. Using the first device section listed. (**) | |--Device Configured Video Device (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (**) Option DontZap false (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81eaca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:1:5:0) 1002:9613:1179:ff6a ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics] rev 0, Mem @ 0x8000/268435456, 0x9630/65536, 0x9620/1048576, I/O @ 0x6000/256 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading
