Hi, Paul Zimmerman wrote:
> The 3.2 kernel can't load X, but locks up solid, so I've never gotten the > chance to try. When I started in "recovery" mode I tried to find the card > and it didn't show up. So 1 out of 1 times it didn't detect it -- when in > recovery mode. Are there things related to network that are not loaded or > initialized in recovery mode? In recovery mode "init" doesn't start any services, including networking (one can run "service networking start" to start it by hand). But I don't think that should affect lspci output. Do I understand correctly that when you say "the machine recognizes it again" at [1] you are talking about the squeeze kernel, then? Just trying to keep what's been discovered so far straight. For the future: you can help feeble-minded folks like me by mentioning which kernel version you are testing for each observation you describe. Best of all if you attach full "dmesg" output from the corresponding boot so we can see if anything weird happened during initialization. Thanks again for the quick feedback. Ciao, Jonathan [1] http://bugs.debian.org/673496#94 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120615231814.GB3547@burratino
