wireless card broken with kernel upgrade

sorry to post here, i've tried the ubuntu forums but no help yet.

i've got ubuntu warty on an IBM thinkpad with a netgear WG511 that was
working great with Prism54 and WEP until this morning.

last night all i did was run the usual apt-get update and apt-get
upgrade and it upgraded a few things, mostly security upgrades
(imagemagic) plus the latest kernel upgrade to 2.6.10-5-386. not sure
what the upgrade was, exactly. it seems like i was using the
2.6.10-5-386 for quite a while now, but i know for certain that it was
upgraded using the security repository, so maybe just a security upgrade
to the kernel. i saw it upgrading and setting up the new kernel.

anyway after rebooting this morning it no longer recognizes eth1. during
boot, it comes up as eth1 failed and couldn't connect to ntpdate. i've
tried /etc/init.d/network restart and tried playing around with the
settings in /etc/networking/interfaces, but nothing works. it won't
recognize eth1.

i've had to go back to kernel 2.6.8.1-4-386 during boot, luckily i still
had this option in the grub menu. which is where i am now posting this.
but all of a sudden, kernel 2.6.10-5-386 has broken my wireless card.
i'm positive the kernel has always been 2.6.10-5-386, the number hasn't
changed, but whatever upgrade it did broke my wireless.

does anyone know what's happened with the kernel upgrade, and how i can
get the card to work and the system to recognize eth1 with the new
kernel? what could have happen, exactly, during a kernel upgrade to all
of a sudden break my neatgear wireless card?

thankful for any answers to fix this, or to go back to the older,
2.6.10-5-386 kernel, that's no longer listed in grub. any chance to roll
back the kernel, if there's no fix?


--
there's no place like ~
there's no place like ~
(remove _eh to email.)

johnny bobby bee <(E-Mail Removed)> writes:


>i've had to go back to kernel 2.6.8.1-4-386 during boot, luckily i still
>had this option in the grub menu. which is where i am now posting this.
>but all of a sudden, kernel 2.6.10-5-386 has broken my wireless card.
>i'm positive the kernel has always been 2.6.10-5-386, the number hasn't
>changed, but whatever upgrade it did broke my wireless.

>does anyone know what's happened with the kernel upgrade, and how i can
>get the card to work and the system to recognize eth1 with the new
>kernel? what could have happen, exactly, during a kernel upgrade to all
>of a sudden break my neatgear wireless card?

>thankful for any answers to fix this, or to go back to the older,
>2.6.10-5-386 kernel, that's no longer listed in grub. any chance to roll
>back the kernel, if there's no fix?

grub should NOT replace old kernels with new. It should keep both. If it
replaces it is broken. Since if the kernel does not work, nothing works,
old kernels should always be left in place.

You will have to reinstall the old kernel (assuming it does not exist in
/boot-- list the files there and see if a version of vmlinuz for that old
kernel is still there).

On the wireless issue, you do not say which wireless driver you are using.
(look in /etc/modprobe.conf ) Is it ndiswrapper? or is it a driver for the
specific card?
Remember that kernel modules have to be compiled for the specific kernel.
This is one of the problems with modules. Look in /var/log/messages from
the boot process for error messages having to do with the wireless card
module.

Unruh wrote:
> johnny bobby bee <(E-Mail Removed)> writes:
>
>
>
>>i've had to go back to kernel 2.6.8.1-4-386 during boot, luckily i still
>>had this option in the grub menu. which is where i am now posting this.
>>but all of a sudden, kernel 2.6.10-5-386 has broken my wireless card.
>>i'm positive the kernel has always been 2.6.10-5-386, the number hasn't
>>changed, but whatever upgrade it did broke my wireless.
>
>
>>does anyone know what's happened with the kernel upgrade, and how i can
>>get the card to work and the system to recognize eth1 with the new
>>kernel? what could have happen, exactly, during a kernel upgrade to all
>>of a sudden break my neatgear wireless card?
>
>
>>thankful for any answers to fix this, or to go back to the older,
>>2.6.10-5-386 kernel, that's no longer listed in grub. any chance to roll
>>back the kernel, if there's no fix?
>
>
> grub should NOT replace old kernels with new. It should keep both.

Grub does not do that. It is the package software that manages updates. In
Red Hat and related systems, RPM packages do the updates, and most RPM
packages replace the old with the new. However, if the kernel RPM packages
are properly built, they will add the new kernel, not replace the old one.

> If it
> replaces it is broken. Since if the kernel does not work, nothing works,
> old kernels should always be left in place.
>
>


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 10:05:00 up 1 day, 23:17, 3 users, load average: 2.23, 2.22, 2.20

Jean-David Beyer <(E-Mail Removed)> writes:

>Unruh wrote:
>> johnny bobby bee <(E-Mail Removed)> writes:
>>
>>
>>
>>>i've had to go back to kernel 2.6.8.1-4-386 during boot, luckily i still
>>>had this option in the grub menu. which is where i am now posting this.
>>>but all of a sudden, kernel 2.6.10-5-386 has broken my wireless card.
>>>i'm positive the kernel has always been 2.6.10-5-386, the number hasn't
>>>changed, but whatever upgrade it did broke my wireless.
>>
>>
>>>does anyone know what's happened with the kernel upgrade, and how i can
>>>get the card to work and the system to recognize eth1 with the new
>>>kernel? what could have happen, exactly, during a kernel upgrade to all
>>>of a sudden break my neatgear wireless card?
>>
>>
>>>thankful for any answers to fix this, or to go back to the older,
>>>2.6.10-5-386 kernel, that's no longer listed in grub. any chance to roll
>>>back the kernel, if there's no fix?
>>
>>
>> grub should NOT replace old kernels with new. It should keep both.

>Grub does not do that. It is the package software that manages updates. In
>Red Hat and related systems, RPM packages do the updates, and most RPM
>packages replace the old with the new. However, if the kernel RPM packages
>are properly built, they will add the new kernel, not replace the old one.

Of course. I "misspoke" I meant the package manager, not grub.
In my mind I was thinking "package manager" and my fingers were typing "grub"
Under rpm you should always use rpm -i, not rpm -U when installing kernels.
Mandrake changed their kernel package naming convention to ensure that
all kernels had unique names precisely to alleviate this problem.

>> If it
>> replaces it is broken. Since if the kernel does not work, nothing works,
>> old kernels should always be left in place.

Unruh wrote:
> grub should NOT replace old kernels with new. It should keep both. If it
> replaces it is broken. Since if the kernel does not work, nothing works,
> old kernels should always be left in place.

that's what i thought, and maybe it didn't change the grub menu at all.
all i know is that during the apt-get upgrade i definitely saw apt
getting and setting up a new kernel. but the kernel still looked the
same to me when i looked at uname -a.

either way, something definitely happened. but i started fooling around
with /etc/networking/interfaces and i got it going. for some reason it
(whatever *it* was) switched my eth0 and eth1. eth1 used to be my
wireless and eth0 my regular (wired) network card. but since i didn't
have eth0 starting up auto on boot, something must have switched the
two. 'cause all i did was switch out the names eth1 for wired lan and
eth0 for wireless card in the interfaces script and everything's working
again.

i'd love to know what happened and what caused the switch, but glad that
it's working again.

cheers.


--
there's no place like ~
there's no place like ~
(remove _eh to email.)

johnny bobby bee <(E-Mail Removed)> writes:

>Unruh wrote:
>> grub should NOT replace old kernels with new. It should keep both. If it
>> replaces it is broken. Since if the kernel does not work, nothing works,
>> old kernels should always be left in place.

>that's what i thought, and maybe it didn't change the grub menu at all.
>all i know is that during the apt-get upgrade i definitely saw apt
>getting and setting up a new kernel. but the kernel still looked the
>same to me when i looked at uname -a.

Look in /boot That has all the kernels you have. Look at the stuff
following vmlinuz in the name.
It sounds to me like apt-get DID replace your old kernel. replace, not just
add the new one. That is just wrong. It should not happen and is a bug in
apt-get if it does that.



>either way, something definitely happened. but i started fooling around
>with /etc/networking/interfaces and i got it going. for some reason it
>(whatever *it* was) switched my eth0 and eth1. eth1 used to be my
>wireless and eth0 my regular (wired) network card. but since i didn't
>have eth0 starting up auto on boot, something must have switched the
>two. 'cause all i did was switch out the names eth1 for wired lan and
>eth0 for wireless card in the interfaces script and everything's working
>again.

freezing the eth? name to a particular card is one of Linux's problems.
However look in modprobe.conf you should have aliases called eth0 and eth1
linked to specific modules.

Unruh wrote:
> Look in /boot That has all the kernels you have. Look at the stuff
> following vmlinuz in the name.
> It sounds to me like apt-get DID replace your old kernel. replace, not just
> add the new one. That is just wrong. It should not happen and is a bug in
> apt-get if it does that.

well here's the weird thing vmlinuz-2.6.10-5-386 has a date of may 20,
but initrd.img-2.6.10-5-386 has a date of may 27 which is when i did my
last apt-get upgrade and i noticed it upgrading and setting up the new
kernel. what gives? why is the vmlinuz dated the 20th even though i
don't remember apt-get updating anything kernel-realted on that date,
but only the img file is dated the 27th, the day i actually saw the
upgrade take place?

-rw-r--r-- 1 root root 4403200 2005-05-27 01:49 initrd.img-2.6.10-5-386
-rw-r--r-- 1 root root 4235264 2005-02-08 02:27 initrd.img-2.6.8.1-3-386
-rw-r--r-- 1 root root 4235264 2005-02-08 02:49 initrd.img-2.6.8.1-4-386

-rw-r--r-- 1 root root 1188485 2005-05-20 10:22 vmlinuz-2.6.10-5-386
-rw-r--r-- 1 root root 1097539 2004-11-18 06:35 vmlinuz-2.6.8.1-3-386
-rw-r--r-- 1 root root 1099120 2005-01-14 04:03 vmlinuz-2.6.8.1-4-386

>
> freezing the eth? name to a particular card is one of Linux's problems.
> However look in modprobe.conf you should have aliases called eth0 and eth1
> linked to specific modules.

the onlly modprobe.conf file i could find was:
/usr/share/doc/module-init-tools/examples/generate-modprobe.conf.gz
/usr/share/man/man5/modprobe.conf.5.gz

i can't actually find a modprobe.conf file.
either way, i'm not sure why the new kernel swapped eth0 and eth1. at
least i got it working again.




--
there's no place like ~
there's no place like ~
(remove _eh to email.)

johnny bobby bee <(E-Mail Removed)> writes:

>Unruh wrote:
>> Look in /boot That has all the kernels you have. Look at the stuff
>> following vmlinuz in the name.
>> It sounds to me like apt-get DID replace your old kernel. replace, not just
>> add the new one. That is just wrong. It should not happen and is a bug in
>> apt-get if it does that.

>well here's the weird thing vmlinuz-2.6.10-5-386 has a date of may 20,
>but initrd.img-2.6.10-5-386 has a date of may 27 which is when i did my
>last apt-get upgrade and i noticed it upgrading and setting up the new
>kernel. what gives? why is the vmlinuz dated the 20th even though i
>don't remember apt-get updating anything kernel-realted on that date,
>but only the img file is dated the 27th, the day i actually saw the
>upgrade take place?

>-rw-r--r-- 1 root root 4403200 2005-05-27 01:49 initrd.img-2.6.10-5-386
>-rw-r--r-- 1 root root 4235264 2005-02-08 02:27 initrd.img-2.6.8.1-3-386
>-rw-r--r-- 1 root root 4235264 2005-02-08 02:49 initrd.img-2.6.8.1-4-386

>-rw-r--r-- 1 root root 1188485 2005-05-20 10:22 vmlinuz-2.6.10-5-386
>-rw-r--r-- 1 root root 1097539 2004-11-18 06:35 vmlinuz-2.6.8.1-3-386
>-rw-r--r-- 1 root root 1099120 2005-01-14 04:03 vmlinuz-2.6.8.1-4-386

So, assuming you were running 2.6.10 before, that version got wiped.
(It could be that the upgrade onlyupgraded initrd)


>>
>> freezing the eth? name to a particular card is one of Linux's problems.
>> However look in modprobe.conf you should have aliases called eth0 and eth1
>> linked to specific modules.

>the onlly modprobe.conf file i could find was:
>/usr/share/doc/module-init-tools/examples/generate-modprobe.conf.gz
>/usr/share/man/man5/modprobe.conf.5.gz

/etc/modprobe.conf
alias eth0 3c59x
alias eth1 ipw2200


>i can't actually find a modprobe.conf file.
>either way, i'm not sure why the new kernel swapped eth0 and eth1. at
>least i got it working again.

It depends on which gets found first by the kernel. the first one is eth0,
the next eth1, etc.





>--
>there's no place like ~
>there's no place like ~
>(remove _eh to email.)

Unruh Wrote:
> johnny bobby bee <(E-Mail Removed)> writes:
>
>
> So, assuming you were running 2.6.10 before, that version got wiped.
> (It could be that the upgrade onlyupgraded initrd)
>
>
>
> /etc/modprobe.conf
> alias eth0 3c59x
> alias eth1 ipw2200
>
>
>
> It depends on which gets found first by the kernel. the first one is
> eth0,
> the next eth1, etc.
testtesttest


--
white

test
"white" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Unruh Wrote:
>> johnny bobby bee <(E-Mail Removed)> writes:
>>
>>
>> So, assuming you were running 2.6.10 before, that version got wiped.
>> (It could be that the upgrade onlyupgraded initrd)
>>
>>
>>
>> /etc/modprobe.conf
>> alias eth0 3c59x
>> alias eth1 ipw2200
>>
>>
>>
>> It depends on which gets found first by the kernel. the first one is
>> eth0,
>> the next eth1, etc.
> testtesttest
>
>
> --
> white