chenning wrote:
> following is the dmesg dump from target board:
Actually, there are several useful messages produced by Card Services in
the system log that are not displayed by dmesg. The last dozen or so
lines of /var/log/messages (if you're using Nicolas' ramdisk or a
derivative; otherwise see the equivalent on your distribution) might be
instructive if your board is genuinely not detecting the card.
You sent me your .config, which has CONFIG_IP_PNP=y and
CONFIG_IP_PNP_BOOTP=y. (Let me apologize for being a bad person in not
replying more promptly.) Perhaps someone else who might have written an
NFS-root HOWTO-like document for Assabet (ahem, ahem =) will chime in to
correct me here, but I think the Card Services userland scripts
(network.opts, in particular) are the intended place to do BOOTP-style
configuration of PCMCIA network interfaces. You'll notice that the
IP-Config error occurs before the root filesystem is mounted, which
means that cardmgr has not yet had a chance to direct Card Services to
configure the LP-E client driver, thus there are no network interfaces.
On a marginally related note, for those of you who use ramdisk_ks but
are annoyed by the kernel version dependency presented by cardmgr (in
the form of /lib/modules/`uname -r`), I've updated the disk image on my
Assabet page. Pleasantly, cardmgr 3.1.20 no longer exits when it can't
find a module directory, so I've removed that portion of the filesystem.
(Nicolas' default Assabet configuration has statically linked the
pcnet_cs and ide_cs drivers, anyway.)
-jd
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
