On Fri, 2012-06-15 at 18:18 -0500, Jonathan Nieder wrote:
> 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.
Right. If a card doesn't show up in lspci then it is in a very unhappy
state - it's not connected properly or a critical part of the controller
chip has locked up.
> 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.
Yes it's not clear exactly what Paul has changed.
There haven't been any recent changes to the ath5k driver in either
squeeze or wheezy, so I tend to think that the driver bug is getting
mixed up with unreliable hardware.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
Attachment:
signature.asc
Description: This is a digitally signed message part