Bug 64262 - Valhalla: initrd-everything.img: unresolved symbols in airo_cs.o
Summary: Valhalla: initrd-everything.img: unresolved symbols in airo_cs.o
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda-images
Version: 7.3
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-30 21:03 UTC by Aleksey Nogin
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-17 18:35:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Aleksey Nogin 2002-04-30 21:03:06 UTC
Just tried to do 7.2->7.3 upgrade on my laptop, but it failed to initialize my
Aironet card:

cardmgr[41]: socket 1: Aironet PC4800
cardmgr[41]: executing: 'modprobe airo_cs.o'
cardmgr[41]: + /tmp/airo-cs.o: unresolved symbol reset_airo_card
cardmgr[41]: + /tmp/airo-cs.o: unresolved symbol init_airo_card
cardmgr[41]: + /tmp/airo-cs.o: unresolved symbol stop_airo_card
...
(copied by hand, so may contain typos).

I used vmlinuz and initrd-everything.img from images/pxeboot (by downloading
them and sticking them into my grub.conf).

Comment 1 Michael Fulbright 2002-05-01 15:29:20 UTC
What is a aironet card?

Comment 2 Aleksey Nogin 2002-05-01 16:04:04 UTC
Aironet PC4800. (Aironet Wireless Communications, Inc was bought by Cisco, so
it's also known as Cisco PC4800, I guess). In short, it's the card that the
airo_cs driver is supposed to work with (aironet4500_cs too, but according to
bug #40552 for 4800 (as opposed to 4500 cards), airo_cs works better).

Anyway, this bug is more about airo_cs driver failing to load because of
unresolved symbols, is it really important what card caused it to be loaded?

Comment 3 Michael Fulbright 2002-07-17 18:35:45 UTC
Jeremy we don't support wireless network cards in the install do we?

Comment 4 Jeremy Katz 2002-07-18 02:56:07 UTC
No, wireless cards aren't supported for installing because we have no way to set
up the wireless tools parameters.


Note You need to log in before you can comment on or make changes to this bug.