> ========================== > Date: Wed, 21 Jul 2010 16:39:58 -0400 > From: Andres Cimmarusti <acimmarusti@gmail.com> > To: Mauro Condarelli <MC5686@mclink.it> > Cc: backports-users@lists.backports.org > Subject: Re: > ========================== > > attach your /var/log/Xorg0.log and detailed output of dmesg. > They will > probably hold the answers as to why is not working automatically. Here are a matched couple of a failed boot attempt. For Your reading pleasure. ;) > > Now, using option 2, edit your xorg.conf and simply add to the > section > "Device" and under "Configured video device" a line that says: > Driver "nv" Ok, I already guessed that much, but I was waiting for a confirmation :) I will reboot as soon as I send this out. Unfortunately this machine is my gateway to the internet, so when boot fails I'm not able to surf the Internet :( Thanks a lot, for the time being. Regards Mauro > > If that doesn't work then try 'vesa' instead of nv. > > Good luck > > Andres > > 2010/7/21 Mauro Condarelli <MC5686@mclink.it> > > > > > > ========================== > > > Date: Wed, 21 Jul 2010 13:22:20 -0400 > > > From: Andres Cimmarusti <acimmarusti@gmail.com> > > > To: Mauro Condarelli <MC5686@mclink.it> > > > Cc: backports-users@lists.backports.org > > > Subject: Re: > > > ========================== > > > > > > Show us your xorg.conf > > Pronto! (I did not change it since lenny installation via netinstall) > > ============================================ > > # xorg.conf (X.Org X Window System server configuration file) > > # > > # This file was generated by dexconf, the Debian X Configuration > tool, > > using > > # values from the debconf database. > > # > > # Edit this file with caution, and see the xorg.conf manual > page. > > # (Type "man xorg.conf" at the shell prompt.) > > # > > # This file is automatically updated on xserver-xorg package > upgrades > > *only* > > # if it has not been modified since the last upgrade of the > xserver-xorg > > # package. > > # > > # If you have edited this file but would like it to be automatically > > updated > > # again, run the following command: > > # sudo dpkg-reconfigure -phigh xserver-xorg > > > > Section "InputDevice" > > Identifier "Generic Keyboard" > > Driver "kbd" > > Option "XkbRules" "xorg" > > Option "XkbModel" "pc104" > > Option "XkbLayout" "us" > > EndSection > > > > Section "InputDevice" > > Identifier "Configured Mouse" > > Driver "mouse" > > EndSection > > > > Section "Device" > > Identifier "Configured Video Device" > > EndSection > > > > Section "Monitor" > > Identifier "Configured Monitor" > > EndSection > > > > Section "Screen" > > Identifier "Default Screen" > > Monitor "Configured Monitor" > > EndSection > > ============================================ > > .. not much in it :) > > > > > > > > Did you rebuild the proprietary nvidia module for the new > kernel? > > > I'm > > > positive the nvidia driver in Lenny does not support that > kernel, > > > nor do you > > > actually have the nouveau driver installed (since it's only > in > > > Squeeze or > > > Sid). You have two solutions: > > > > > > 1. Download the nvidia driver installer from their website > and > > > run it in > > > single-user mode do nvidia-xconfig and restart > > > > > > 2. Fix your xorg.conf so that you force X to use either "nv" > > > or "vesa" as > > > video driver > > I would like to use this solution because I use this machine > mainly as a > > server and thus the power of the graphics card is largely unused. > > Can You be more specific about what I should change? > > > > I do not understand why a change in kernel triggered all this. > > All X-related files are exactly the same: I am right now typing > using the > > "old" (2.6.26) kernel. > > Is this related to a different hardware detection or to different > fb > > modules? > > > > TiA > > Mauro > > > > > > > > Cheers > > > > > > Andres > > > > > > 2010/7/21 Mauro Condarelli <MC5686@mclink.it> > > > > > > > Hi, > > > > I have a Lenny install using standard linux-image-2.6.26-2-amd64 > > > on a > > > > machien based on the Zotac-ION motherboard (Atom330). > > > > > > > > Since I need support for the Atheros WiFi board I tried > to > > > installthe > > > > backport kernel: linux-image-2.6.32-bpo.5-amd64, bu this > does > > > not work for > > > > me. > > > > It hangs badly when starting X-server with garbage on screen > > > and I cannot > > > > even switch to console (flashing underline cursor in the > top-left > > > corner). > > > > > > > > Booting in single-user mode works ok (unsurprisingly!) > until > > > I exit single > > > > uer and try starting X. > > > > > > > > In my /var/log/messages I found the following suspicious > lines: > > > > > > > > Jul 21 18:23:02 server kernel: [ 26.961636] ADDRCONF(NETDEV_UP): > > > wlan0: > > > > link is not ready > > > > Jul 21 18:23:03 server kernel: [ 28.480340] NET: Registered > > > protocol > > > > family 5 > > > > Jul 21 18:23:04 server kernel: [ 29.594731] mtrr: type > mismatch > > > for > > > > f9c00000,200000 old: write-back new: write-combining > > > > Jul 21 18:23:04 server kernel: [ 29.594785] mtrr: type > mismatch > > > for > > > > f9800000,400000 old: write-back new: write-combining > > > > Jul 21 18:23:04 server kernel: [ 29.594828] mtrr: type > mismatch > > > for > > > > f9000000,800000 old: write-back new: write-combining > > > > Jul 21 18:23:07 server kernel: [ 32.669647] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > Jul 21 18:23:07 server kernel: [ 32.669672] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > Jul 21 18:23:07 server kernel: [ 32.669686] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > Jul 21 18:23:07 server kernel: [ 32.669706] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > Jul 21 18:23:07 server kernel: [ 32.669723] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > .. > > > > Jul 21 18:23:08 server kernel: [ 32.720762] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO_INTR 0x00000010 - Ch 1 > > > > Jul 21 18:23:08 server kernel: [ 32.720776] [drm] nouveau > > > 0000:03:00.0: > > > > PFIFO still angry after 101 spins, halt > > > > Jul 21 18:23:59 server kernel: [ 84.573913] mtrr: type > mismatch > > > for > > > > f9c00000,200000 old: write-back new: write-combining > > > > Jul 21 18:23:59 server kernel: [ 84.573964] mtrr: type > mismatch > > > for > > > > f9800000,400000 old: write-back new: write-combining > > > > Jul 21 18:23:59 server kernel: [ 84.574006] mtrr: type > mismatch > > > for > > > > f9000000,800000 old: write-back new: write-combining > > > > Jul 21 18:24:29 server kernel: [ 114.650385] mtrr: type > mismatch > > > for > > > > f9c00000,200000 old: write-back new: write-combining > > > > Jul 21 18:24:29 server kernel: [ 114.650436] mtrr: type > mismatch > > > for > > > > f9800000,400000 old: write-back new: write-combining > > > > Jul 21 18:24:29 server kernel: [ 114.650478] mtrr: type > mismatch > > > for > > > > f9000000,800000 old: write-back new: write-combining > > > > Jul 21 18:24:39 server shutdown[2944]: shutting down for > system > > > reboot > > > > Jul 21 18:24:41 server kernel: [ 125.813259] mtrr: type > mismatch > > > for > > > > f9c00000,200000 old: write-back new: write-combining > > > > Jul 21 18:24:41 server kernel: [ 125.813312] mtrr: type > mismatch > > > for > > > > f9800000,400000 old: write-back new: write-combining > > > > Jul 21 18:24:41 server kernel: [ 125.813363] mtrr: type > mismatch > > > for > > > > f9000000,800000 old: write-back new: write-combining > > > > Jul 21 18:24:49 server kernel: [ 134.650635] nfsd: last > server > > > has exited, > > > > flushing export cache > > > > Jul 21 18:24:50 server kernel: Kernel logging (proc) stopped. > > > > > > > > I found on the Internet some hint this new "noveau" driver > > > might conflict > > > > with nvidia, but I couldn't understand if and how it applies > > > to me. > > > > > > > > Can someone help me debug this, please? > > > > I am obvipusly willing to send any info deemed useful: > Just > > > ask! :) > > > > > > > > > > > > Thanks in Advance > > > > Mauro > > > > > > > > >
Attachment:
dmesg.0
Description: Binary data
Attachment:
Xorg.0.log.old
Description: application/trash