Re: Fwd: orinoco wireless on sid
On Wed, Dec 14, 2005 at 07:11:53PM -0500, Michael Marsh wrote:
> Hi all.
>
> I sent this to debian-laptop a few days ago, and haven't gotten any
> responses, so I thought I'd try the wider-readership list.
>
> It's now a full week since I lost my wireless, and still no indication
> that the kernel team has looked at my bug report. I was going to try
> compiling the orinoco module myself, but the kernel-source version for
> 2.4.27 (-11) doesn't match the kernel-image version (-12), and I have
> no idea what kind of mess I might create if I use the wrong-version
> module.
>
> ---------- Forwarded message ----------
> From: Michael Marsh <michael.a.marsh@gmail.com>
> Date: Dec 12, 2005 6:54 PM
> Subject: orinoco wireless on sid
> To: debian-laptop@lists.debian.org
>
>
> Hi all.
>
> Last week I upgraded my kernel to 2.4.27-12, from
> kernel-image-2.4.27-2-686, and promptly lost my orinoco network driver
> to an unresolved symbol:
> root@localhost:~# modprobe orinoco
> /lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o:
> /lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o:
> unresolved symbol ALIGN
> /lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o:
> insmod /lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o
> failed
> /lib/modules/2.4.27-2-686/kernel/drivers/net/wireless/orinoco.o:
> insmod orinoco failed
>
> Consequently, I've been wireless-less (would that be "wire"?) for the
> better part of a week. Not life-threatening, to be certain, but
> definitely inconvenient.
>
> Is anybody else seeing this? Alternatively, does anyone else have the
> same configuration (sid, orinoco, 2.4.27-12 on 686) working correctly?
> I'm interested in corroboration, work-arounds, or a demonstration
> that it's something particular to my own setup.
>
> I filed a bug report pretty much immediately after the problem hit me
> (bug #342503), but there's been no response from the kernel team
> (including any indication that the report has been read).
>
> Thanks.
>
> --
> Michael A. Marsh
> http://www.umiacs.umd.edu/~mmarsh
> http://mamarsh.blogspot.com
>
>
Hello,
>From your debugging output, I see that modprobe is trying to load the
module from the 2.4.27-2 directories. I haven't seen a problem like it
before, but you might want to see if you have a
/lib/modules/2.4.27-12-686 dir. Another thing to check is if the driver
is packaged seperatly.
Not knowing anything about the driver, and not having one to play with,
my only suggestion is to downgrade your kernel to the working version.
Sorry I can't be more help.
Pete
Reply to: