Re: kernel pcmcia modules
I hope it's ok to reply to the list only.
Am Sonntag, 13. Juli 2003 03:34 schrieb Russell Coker:
> > yes, try PCIC=yenta_socket
> OK I did that, the yenta driver is loaded on a reboot, and the result is
> the same. The device driver for my ethernet card gets loaded, but the
> interface is not configured.
> I've attached a relevant section of my kernel message log for removing a
> card and inserting it again.
To me, this looks like three times the same procedure.
Without any error message ? Check daemon.log, syslog, messages.
> Also for some reason my machine does not beep when the card is inserted.
Cardservices can't identify the card. In the log, there's only the kernel PCI
identification.
To make sure:
What's the output from 'cardctl ident' and 'card status' ?
What happens after a 'cardctl resume' ?
Tracking:
Did you apply the right /etc/pcmcia/config, as suggested in the documentaion ?
( There are two versions, for 2.2 resp. 2.4 kernels)
Is your card matched in that file by at least one entry ?
You can setup custom entries if you got sth back from cardctl ident.
> I did some tracing on the /etc/pcmcia/network script which is not being run
> at all, this seems to be at the core of the problem.
If the card type isn't recognized, there's no decision about the requested
service possible. So cardmgr can't launch anything.
Another basic thing to look is if cardservices (tools), modules and kernel are
fitting together. I assume you've choosen the right components, but let's
make sure:
- There's a pcmcia-modules-kernelXXX package installed that applies esp. to
your 2.4 kernel version + cpu type
- Cardservice tools (pcmcia-cs) are from the debian package
- It's a 16 Bit Cardbus Card
As i understood it, pcmcia-cs deals with 16 bit Cardbus Cards ( t.i., Version
2.x) but not very well with newer 32 bit Cards and also not with any other
'hotp-plugin'. There's the package 'hotplug' for that, dealing with USB,
PCI-Cards and 32 bit PCMCIA-Cards; but not with 16 bit ones.
Both, pcmcia-cs and hotplug, are capable to startup network connections.
On Debian, both link into /etc/networks and ifup/down somehow; however they
might interfere each other. It's recommendet to user either one.
- You make it easy
At this point, you didn't install related services, or at least didn't start
them from rcS.d / rc2.d.
There are some tools to detect network configuration at boottime,
or with changed plugins. Debian provides the 'laptop-net' package with
configuration schemes; some other packages may (or may not) depend on that.
etc/default/laptop-net specifies network-card drivers to be loaded at
boottime. Also recommendet are e.g. 'whereami', or 'ifupdwon' from T. Hood.
greets
--
mi <mrl>
Reply to: