Re: [leaf-wisp] ath0 PCMCIA card not recognised?
Michael Mee <[email protected]> Fri, 21 Jan 2005 19:26:44 -0800
| Newsgroups | gmane.linux.leaf.wisp-dist |
|---|---|
| Message-ID | <[email protected]> |
Thanks Steve! > `tail -f /var/log/messages` and insert the card. You should then > recieve quite a detailed explantion of the problem. > > post us that block of text. I first created the file /etc/pcmcia/atheros.conf with the contents: device "atheros" class "network" module "ath_pci" card "Proxim 8671 card" manfid 0x0125,0x0007 bind "atheros" card "Netgear WAB501" manfid 0x0271,0x0012 bind "atheros" because without this the /var/log/messages entry showed it was an unrecognised device (neither card appears anywhere in the existing conf files). After that I get the following trace: Jan 22 00:50:35 Jan 22 00:50:37 wisprouter kernel: cs: cb_alloc(bus 1): vendor 0x168c, device 0x0012 Jan 22 00:50:37 wisprouter cardmgr[1934]: socket 0: Netgear WAB501 Jan 22 00:50:37 wisprouter cardmgr[1934]: executing: 'modprobe ath_pci' Jan 22 00:50:37 wisprouter cardmgr[1934]: + insmod: /lib/modules/2.4.25: No such file or directory Jan 22 00:50:37 wisprouter kernel: ath_pci: 0.8.4.0 BETA Jan 22 00:50:37 wisprouter kernel: PCI: No IRQ known for interrupt pin A of device . Please try using pci=biosirq. Jan 22 00:50:37 wisprouter kernel: ath_pci: cache line size not set; forcing 4 Jan 22 00:50:37 wisprouter kernel: ath_pci: cannot reserve PCI memory region Jan 22 00:50:37 wisprouter kernel: ath_pci: No devices found, driver not installed. Jan 22 00:50:37 wisprouter cardmgr[1934]: + Using /modules/ath_pci.o Jan 22 00:50:37 wisprouter cardmgr[1934]: + insmod: init_module: ath_pci: No such device Jan 22 00:50:37 wisprouter cardmgr[1934]: modprobe exited with status 1 Jan 22 00:50:37 wisprouter cardmgr[1934]: module /lib/modules/preferred/pcmcia/ath_pci.o not available Jan 22 00:50:38 wisprouter cardmgr[1934]: get dev info on socket 0 failed: Resource temporarily unavailable Jan 22 00:50:38 wisprouter cardmgr[1934]: wrong module 'ath_pci' for device 'atheros'? If I add the pci=biosirq line to the syslinux.cfg file and reboot, then I get: Jan 22 01:03:43 wisprouter kernel: cs: cb_alloc(bus 1): vendor 0x168c, device 0x0012 Jan 22 01:03:43 wisprouter cardmgr[1935]: socket 0: Netgear WAB501 Jan 22 01:03:43 wisprouter cardmgr[1935]: executing: 'modprobe ath_pci' Jan 22 01:03:43 wisprouter cardmgr[1935]: + insmod: /lib/modules/2.4.25: No such file or directory Jan 22 01:03:43 wisprouter kernel: ath_pci: 0.8.4.0 BETA Jan 22 01:03:43 wisprouter kernel: PCI: No IRQ known for interrupt pin A of device . Jan 22 01:03:43 wisprouter kernel: ath_pci: cache line size not set; forcing 4 Jan 22 01:03:43 wisprouter kernel: ath_pci: cannot reserve PCI memory region Jan 22 01:03:43 wisprouter kernel: ath_pci: No devices found, driver not installed. Jan 22 01:03:43 wisprouter cardmgr[1935]: + Using /modules/ath_pci.o Jan 22 01:03:43 wisprouter cardmgr[1935]: + insmod: init_module: ath_pci: No such device Jan 22 01:03:43 wisprouter cardmgr[1935]: modprobe exited with status 1 Jan 22 01:03:43 wisprouter cardmgr[1935]: module /lib/modules/preferred/pcmcia/ath_pci.o not available Jan 22 01:03:44 wisprouter cardmgr[1935]: get dev info on socket 0 failed: Resource temporarily unavailable Jan 22 01:03:44 wisprouter cardmgr[1935]: wrong module 'ath_pci' for device 'atheros'? I.e., essentially the same message, but without the use pci=biosirq suggestion. Any other ideas? (Also, any idea how to get the kernel-pcmcia package installed in place of the existing one - then yenta_socket might work as the controller, as suggested by http://linux.seindal.dk/item23.html, towards the middle). thx! michael ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl