| View previous topic :: View next topic |
| Author |
Message |
vrai
n00b
Joined: 20 Jan 2005
Posts: 15
|
 Posted: Sat Jun 18, 2005 11:38 am Post subject: Cannot get 2.6.11-r11 to recognise Orinoco Classic Gold card |
 |
|
Hi,
I've been trying for the last couple of weeks to get Wifi set up on my laptop. I bought an Orinoco Classic Gold as this appeared to be supported under 2.6 (as it uses the original Hermes chipset). However I've been unable to get the machine to even acknowledge that it's connected, let alone setup the networking.
I've tried using the Hermes drivers that come with the kernel as well as the orinoco_cs ebuild but both have failed to work. The most output I've got from the kernel is using the built-in drivers, when the card is connected dmesg shows ...
| Code: | cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
prism2_cs: Ignoring new-style parameters in presence of obsolete ones
prism2cs_init: prism2_cs.o: 0.2.1-pre23 Loaded
prism2cs_init: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f |
But iwconfig doesn't see any cards ...
| Code: | eth0 no wireless extensions.
lo no wireless extensions.
wlan0 no wireless extensions. |
I've followed the instructions of a few posts on this topic but have got nowhere. The card does work as I've tested it on an XP machine, also I've had no problems using a PCMCIA CF reader on my machine.
Any help would be great appreciated. I really need a WiFi capable Unix machine and am getting so desperate I'm actually considering buying a PowerBook! |
|
| Back to top |
|
 |
augury
l33t
Joined: 22 May 2004
Posts: 722
Location: philadelphia
|
| Posted: Sat Jun 18, 2005 1:38 pm Post subject: |
|
|
| have you tryed sys-apps/pcmcia-cs? looks like it would apply. runs as a daemon. |
|
| Back to top |
|
|
vrai
n00b
Joined: 20 Jan 2005
Posts: 15
|
| Posted: Sat Jun 18, 2005 2:09 pm Post subject: |
|
|
| Quote: | | have you tryed sys-apps/pcmcia-cs? looks like it would apply. |
It's already installed and /etc/init.d/pcmcia claims to be running.
I tried the latest Kubuntu LiveCD and that detected the card; also I was able to get a working network connection so the hardware is clearly supported by Linux. The relevant output of dmesg is ...
| Code: | Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 0000:00:11.0
Yenta: CardBus bridge found at 0000:00:11.0 [1179:0001]
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000007
PCI: Found IRQ 11 for device 0000:00:11.1
Yenta: CardBus bridge found at 0000:00:11.1 [1179:0001]
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000011 |
| Code: | orinoco 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
orinoco_cs 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
eth1: Station identity 001f:0001:0008:0048
eth1: Looks like a Lucent/Agere firmware version 8.72
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:C0:7D:3C
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f |
... while iwconfig (prior to my setting the essid/wep key) shows ...
| Code: | lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
eth1 IEEE 802.11-DS ESSID:"" Nickname:"HERMES I"
Mode:Managed Frequency:2.422 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry limit:4 RTS thr:off Fragment thr:off
Power Management:off |
It looks to my like this should be working. I've got the Yenta bridge driver compiled in to the kernel - and I've tried installing the orinoco ebuild. However these all failed to detect the card. Obviously I could use Kubuntu as I now know it works using that distro, but I'd rather stick with Gentoo. |
|
| Back to top |
|
|
vrai
n00b
Joined: 20 Jan 2005
Posts: 15
|
| Posted: Sat Jun 18, 2005 3:00 pm Post subject: |
|
|
Right - I've tried to copy the Kubuntu setup as closly as I can in Gentoo. I've got the Yenta drivers installed, which are detecting the bridge at boot time, and I emerged the latest orinoco drivers. However modprobing the driver doesn't cause the card to be detected, all I get in dmesg is the module's copyright notice.
What I did notice is that under Kubuntu (a patched 2.6.10 kernel) iwconfig has eth1 rather than wlan0. Why is this? Is it simply a difference between 2.6.10 and 2.6.11, or am I missing another piece of configuration?
Oh, and the cardctl output doesn't seems to recognise the wifi card ...
| Code: | sudo /sbin/cardctl status
Socket 0:
no card
Socket 1:
5V 16-bit PC Card
function 0: [ready] |
... it just sees it as a generic 16bit PC Card.
| Code: | sudo /sbin/cardctl info
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1="Lucent Technologies"
PRODID_2="WaveLAN/IEEE"
PRODID_3="Version 01.01"
PRODID_4=""
MANFID=0156,0002
FUNCID=6 |
Can anyone help? |
|
| Back to top |
|
|
zonk
Apprentice
Joined: 23 May 2005
Posts: 176
|
| Posted: Sat Jun 18, 2005 4:32 pm Post subject: |
|
|
i have an orinoco classic gold working under 2.6.11
the following kernel options are important:
| Code: | Device Drivers -> Networking Support [*]
[*] Network device support
[*] Wiresless LAN drivers (non-ham radio)
[M] Hermes chipset 802.11b support (orinoco, prism2, symbol) as a module
[M] Hemers PCMCIA support as a module
[*] PCMCIA network device support
Bus Options ->PCCard (PCMCIA/Cardbus) Support [*]
[M] 16-bit PCMCIA Support
[*] 32-bit CardBus Support
[M] CardBus yenta-compatible bridge support |
now try
for the socket with the orinoco, that should give you a product id like "Lucent Technologies", "WaveLAN/IEEE" and more details. if you can't get to there, i suspect your cardbus bridge is different. once you get the id output, though, you are golden, and from your "cardctl info" output above, i suspect that it will work, i'm just typing the whole mess before this sentence for reference. now all you will need is:
| Code: | ifconfig ethX up
iwconfig ethX essid "yournetworkid"
dhcpcd ethX |
and you should be connected to your access point. you may want to patch the orinoco drivers so you can scan for access points, something not supported out of the box. |
|
| Back to top |
|
|
zonk
Apprentice
Joined: 23 May 2005
Posts: 176
|
| Posted: Sat Jun 18, 2005 4:58 pm Post subject: |
|
|
oh, you will also need to
| Code: |
emerge wireless-tools |
if you haven't already. |
|
| Back to top |
|
|
vrai
n00b
Joined: 20 Jan 2005
Posts: 15
|
| Posted: Sun Jun 19, 2005 11:35 am Post subject: |
|
|
I followed your advice but now I can't access any PCMCIA device. I'm assuming it's related to the rather worrying dmesg output ...
| Code: | Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected ALi M1644 chipset
agpgart: Maximum main memory to use for agp memory: 189M
agpgart: AGP aperture is 64M @ 0xf0000000
kobject_register failed for rsrc_nonstatic (-17)
[<c02c0cbb>] kobject_register+0x5b/0x60
[<c0131ae1>] mod_sysfs_setup+0x51/0xc0
[<c0132bc1>] load_module+0x7a1/0xa70
[<c0132efa>] sys_init_module+0x6a/0x1c0
[<c0102f33>] syscall_call+0x7/0xb
kobject_register failed for yenta_socket (-17)
[<c02c0cbb>] kobject_register+0x5b/0x60
[<c0131ae1>] mod_sysfs_setup+0x51/0xc0
[<c0132bc1>] load_module+0x7a1/0xa70
[<c0132efa>] sys_init_module+0x6a/0x1c0
[<c0102f33>] syscall_call+0x7/0xb
kobject_register failed for rsrc_nonstatic (-17)
[<c02c0cbb>] kobject_register+0x5b/0x60
[<c0131ae1>] mod_sysfs_setup+0x51/0xc0
[<c0132bc1>] load_module+0x7a1/0xa70
[<c0132efa>] sys_init_module+0x6a/0x1c0
[<c0102f33>] syscall_call+0x7/0xb
kobject_register failed for yenta_socket (-17)
[<c02c0cbb>] kobject_register+0x5b/0x60
[<c0131ae1>] mod_sysfs_setup+0x51/0xc0
[<c0132bc1>] load_module+0x7a1/0xa70
[<c0132efa>] sys_init_module+0x6a/0x1c0
[<c0102f33>] syscall_call+0x7/0xb
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0x100-0x4ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
cs: IO port probe 0x100-0x4ff: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38f 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
PCMCIA registration PCCard core failed for socket c13c342c
PCMCIA registration PCCard core failed for socket c13c302c
prism2_cs: Ignoring new-style parameters in presence of obsolete ones
prism2cs_init: prism2_cs.o: 0.2.1-pre23 Loaded
prism2cs_init: dev_info is: prism2_cs
RegisterClient: Unknown error code 0xffffffed
ds: unable to create instance of 'prism2_cs'!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c02c198f
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: prism2_cs p80211 pcmcia ehci_hcd parport_pc parport ali_agp agpgart
CPU: 0
EIP: 0060:[<c02c198f>] Not tainted VLI
EFLAGS: 00010202 (2.6.11-gentoo-r11)
EIP is at kref_put+0x1f/0xa0
eax: 00000000 ebx: 00000000 ecx: c03a4bb0 edx: ce852ee4
esi: c03a4a30 edi: c0543a80 ebp: c1257c68 esp: cdc53e70
ds: 007b es: 007b ss: 0068
Process cardmgr (pid: 7304, threadinfo=cdc52000 task=ce689530)
Stack: c0155381 cdb37e64 cdb37e64 00000000 ce852ea0 c0543a68 c03a4a78 00000000
c03a4a30 c03a4bcf 00000000 ce852f08 c0337e0b ce852ee4 c016c445 cdb37e64
00000296 c02c0f28 ce852f08 ce852f20 c02c0f30 c13fbed0 cfcec580 c02c19a9
Call Trace:
[<c0155381>] invalidate_inode_buffers+0x11/0x60
[<c03a4a78>] pcmcia_put_bus_socket+0x18/0x20
[<c03a4a30>] pcmcia_release_bus_socket+0x0/0x30
[<c03a4bcf>] pcmcia_release_dev+0x1f/0x30
[<c0337e0b>] device_release+0x5b/0x60
[<c016c445>] iput+0x55/0x80
[<c02c0f28>] kobject_cleanup+0x98/0xa0
[<c02c0f30>] kobject_release+0x0/0x10
[<c02c19a9>] kref_put+0x39/0xa0
[<c02c0f5f>] kobject_put+0x1f/0x30
[<c02c0f5f>] kobject_put+0x1f/0x30
[<c02c0f30>] kobject_release+0x0/0x10
[<c03a5178>] bind_request+0x1d8/0x2c0
[<c03a6223>] ds_ioctl+0x543/0x6a0
[<c01649e8>] do_ioctl+0x58/0x80
[<c0164be5>] vfs_ioctl+0x65/0x1e0
[<c0164da5>] sys_ioctl+0x45/0x70
[<c0102f33>] syscall_call+0x7/0xb
Code: 1b e4 ff eb c8 8d b4 26 00 00 00 00 83 ec 18 89 74 24 14 8b 74 24 20 89 5c 24 10 8b 5c 24 1c 85 f6 74 52 81 fe 80 e8 13 c0 74 1c <ff> 0b 0f 94 c0 84 c0 75 0c 8b 5c 24 10 8b 74 24 14 83 c4 18 c3 |
If I try to access the card I get the following error ...
| Code: | sudo /sbin/cardctl ident
open_sock(): No such device |
I'm assuming it's due to a module not being loaded - but I can't see any hint of what module(s) that might be. |
|
| Back to top |
|
|
zonk
Apprentice
Joined: 23 May 2005
Posts: 176
|
| Posted: Sun Jun 19, 2005 4:57 pm Post subject: |
|
|
wow, you yenta module is failing spectacularly. i don't know enough about yenta to help you with that, sorry. hopefully someone else can.
i noticed that you are loading prism2 drivers, though. why? |
|
| Back to top |
|
|
vrai
n00b
Joined: 20 Jan 2005
Posts: 15
|
| Posted: Sun Jun 19, 2005 5:17 pm Post subject: |
|
|
Thanks for your help but I've lost patience with Gentoo in this case. I've installed the latest Kubuntu which detected and setup my card during install. I'll stick with Gentoo on the desktop/server but I can't be arsed to fight my way through Linux's terrible Wifi support.
Here's to hoping that Apple offer cut price PPC Powerbooks when they move to Intel! |
|
| Back to top |
|
|
|
Networking & Security
