| View previous topic :: View next topic |
| Author |
Message |
foolish_gambit
n00b
Joined: 13 Oct 2003
Posts: 12
|
 Posted: Tue Apr 20, 2004 8:22 pm Post subject: PCMCIA wont start |
 |
|
Hopefully this is the right forum for this question. Im migrating to 2.6 and can't get PCMCIA to work. It looks like Im missing something in my kernel but I don't know what. Heres what I get:
root@herman:/>> /etc/init.d/pcmcia start
* PCMCIA support detected.
* Starting pcmcia...
cardmgr[11125]: no sockets found!
* cardmgr failed to start. Make sure that you have PCMCIA
* modules built or support compiled into the kernel [ !! ]
any suggestions?
_________________
"It's not our fault....we're outnumbered by stupid people 10-1" |
|
| Back to top |
|
 |
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Wed Apr 21, 2004 8:02 am Post subject: |
|
|
What's your lspci output?
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
foolish_gambit
n00b
Joined: 13 Oct 2003
Posts: 12
|
| Posted: Wed Apr 21, 2004 5:08 pm Post subject: lspci |
|
|
root@herman:/>> lspci
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 460 Go] (rev a3)
02:06.0 USB Controller: NEC Corporation USB (rev 41)
02:06.1 USB Controller: NEC Corporation USB (rev 41)
02:06.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 33)
02:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 05)
_________________
"It's not our fault....we're outnumbered by stupid people 10-1" |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Wed Apr 21, 2004 5:39 pm Post subject: |
|
|
hmm... I have the same symptoms, but I can't see anything in common .
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
Enderson
Retired Dev
Joined: 12 Nov 2003
Posts: 141
Location: Arapiraca/Maceió, AL, Brazil
|
| Posted: Thu Apr 22, 2004 1:59 am Post subject: |
|
|
How is your kernel configuration?
The carbus modules are up?
Tell us more!
_________________
--
Nothing to say here! |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Thu Apr 22, 2004 2:56 pm Post subject: |
|
|
My problem is that my ancient laptop uses a PCI->PCMCIA bridge . It's a Cirrus Logic PD6729 and it's not supported under 2.6 kernels. It works just fine under 2.4 and pcmcia-cs
| Code: | Module Size Used by
nfsd 58536 8
exportfs 4896 1 nfsd
lockd 43688 2 nfsd
sunrpc 120264 2 nfsd,lockd
pd6729 9204 0
|
I did find a patch to add PD6729 support under 2.6 and applied that, but still no go. I get this in dmesg:
| Code: | PCI: Enabling device 0000:00:0d.0 (0080 -> 0081)
PCI: No IRQ known for interrupt pin A of device 0000:00:0d.0.
pd6729: Cirrus PD6729 PCI to PCMCIA Bridge.
pd6729: configured as a 2 socket device.
pd6729: Enabling PCI_COMMAND_MEMORY.
pd6729: Failed to register IRQ 0, aborting
pd6729: probe of 0000:00:0d.0 failed with error -16
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
svc: unknown version (3)
spurious 8259A interrupt: IRQ7.
|
PCMCIC support is compiled into kernel rather than as modules, since that seemed to offer less scope for thingsto go wrong, and since the pcmcia-cs package modules won't work under 2.6 anyway.
The bridge module itself is a module. Here's some relevant configs:
| Code: | #
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
# CONFIG_PCMCIA_DEBUG is not set
# CONFIG_YENTA is not set
CONFIG_PD6729=m
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
CONFIG_PCMCIA_PROBE=y
#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
CONFIG_PCMCIA_PCNET=y
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
|
The network card itself is FA411
I hope something suggests itself to you out of all this, because I'm pretty much stumped
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
brodo
Guru
Joined: 15 Apr 2003
Posts: 319
|
| Posted: Fri Apr 23, 2004 7:05 am Post subject: |
|
|
| boroshan wrote: | | My problem is that my ancient laptop uses a PCI->PCMCIA bridge . It's a Cirrus Logic PD6729 and it's not supported under 2.6 kernels. It works just fine under 2.4 and pcmcia-cs |
FYI: there is work going on porting the PD driver to 2.6. |
|
| Back to top |
|
|
boroshan
l33t
Joined: 16 Apr 2003
Posts: 730
Location: upside down
|
| Posted: Fri Apr 23, 2004 7:16 am Post subject: good news |
|
|
| brodo wrote: |
FYI: there is work going on porting the PD driver to 2.6. |
Good news indeed:)
Is there a forum somewhere where I can follow developments? After putting in all this effort I feel like I'd like to track developments
_________________
Don't let THEM immanentize the Eschaton! |
|
| Back to top |
|
|
brodo
Guru
Joined: 15 Apr 2003
Posts: 319
|
|
| Back to top |
|
|
brodo
Guru
Joined: 15 Apr 2003
Posts: 319
|
| Posted: Fri Apr 23, 2004 8:47 am Post subject: |
|
|
| Back to the original problem: does your kernel config include CONFIG_YENTA _SOCKET = "y" ? try out latest 2.6. kernel (2.6.6-rc2+), as it contains some IRQ fixes for your socket. anything of interest in dmesg? |
|
| Back to top |
|
|
K-Dawg
Apprentice
Joined: 06 Jan 2004
Posts: 186
Location: Denver, Colorado
|
| Posted: Fri Apr 23, 2004 2:08 pm Post subject: |
|
|
| EDIT ...wrong info |
|
| Back to top |
|
|
foolish_gambit
n00b
Joined: 13 Oct 2003
Posts: 12
|
| Posted: Sun Apr 25, 2004 4:55 pm Post subject: |
|
|
<*> PCMCIA/CardBus support
My CONFIG_YENTA was not set, that may well solve my problem. Ill try it later today.
I see nothing PCMCIA related in my dmesg. Probably because of the former problem, the kernel isnt seeing my CardBus Socket.
Thanks!
_________________
"It's not our fault....we're outnumbered by stupid people 10-1" |
|
| Back to top |
|
|
|
Networking & Security
