OK, one more report on this bug. It's BACK. And the reason, since the kernel
hasn't been updated, must
be the other updates just issued to dhcp. Once again, I can plug an external
device into the machine
(Realtek) and connect, but the internal card doesn't work. It claims to see the
device,
>From: Jonathan Nieder
>To: Paul Zimmerman
>Cc: 673...@bugs.debian.org
>Sent: Saturday, July 14, 2012 11:44 AM
>Subject: Re: [lenny -> squeeze regression] wifi broken (?)
>Jonathan Nieder wrote:
&g
- Original Message -
Jonathan Nieder wrote:
>Do I understand correctly that when you say "the machine recognizes
> it again" at [1] you are talking about the squeeze kernel, then?
Yes, the standard i386 Squeeze kernel is what I have been using. Trying
to use the backported kernel fro
Jonathan Nieder wrote:>Is this summary of your experience
with the ath5k card correct?
> behavior on lenny:always worked
Yes, it worked fine in Lenny.
>behavior on squeeze: broken, symptoms not described yet
The problem was just as described in bug 604613, which you cloned this from.
Well, I was very reluctant to go to the trouble of putting it back, but
when I did the machine recognizes it again. This is getting very,
very weird. There was no sign of it the last time it was installed. Maybe
this is related to the other weird hardware effects of the backported
kernel? I also fo
Well, I finally decided to make another effort on this wifi problem.
Re-installed the card and then got the back-ported kernel installed again.
Booted into "recovery mode" and there is no wlan0 at all. The card is
no longer recognized, so I guess I did something wrong and killed it.
Even restarti
Sorry I didn't save the Xorg.0.log in time from that boot of the 3.2 kernel. It
might have
been very informative.
This machine has many problems with the X system. First it apparently does not
report accurate screen size because the initial boot of both Lenny and Squeeze
had a huge over-s
OK, I went and looked through the logs from my attempt to use the backported
3.2 kernel.
Even editing down to just the one boot by that kernel there is more than 50k of
text for each.
So, here are my best guesses at relevant excerpts.
[from kern.log]
May 18 09:19:22 Nomad kernel: imklog 4.6.
Jonathan Nieder wrote:
>Paul Zimmerman wrote:
>> No go. I don't know how to tell if it has been updated since early
>> March, but the 3.2 kernel does exactly the same thing now that it
>> did then. It looks like it is booting ok, but when it gets to
>> loadi
No go. I don't know how to tell if it has been updated since early March, but
the 3.2 kernel does exactly
the same thing now that it did then. It looks like it is booting ok, but when
it gets to loading the desktop
it freezes with a black screen. Apparently it runs into some sort of problem
st
Ben Hutchings wrote:
>On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote:
>> So what is happening with this bug? It seems to be the same thing that
>> has broken what was perfectly working wifi on my laptop when I had
>> Lenny installed. But upgrading to Squeeze so I
So what is happening with this bug? It seems to be the same thing that has
broken what was perfectly working wifi on my laptop when I had Lenny installed.
But upgrading to Squeeze so I could continue to get security updates has left
me with no wireless connection unless I plug in an external dev
The current kernel in Squeeze cannot use wifi devices requiring the ath5k
driver. I discovered this after finally upgrading from Lenny to Squeeze when
the security updates ended. No tweaking of the install seemed to help, and no
suggested fixes from various "help" sites made any difference. Yet
13 matches
Mail list logo
