Re: can't detect NIC -- solved.
On Fri, Aug 31, 2001 at 12:04:04PM -0400, Susan G. Kleinmann wrote: It looks like this problem is related to pcmcia-cs and not to the boot-flop pies work at all. The problem (finding my Linksys Ethernet combo card) is solved in the latest version (3.1.29) of pcmcia-cs, which has not yet been packaged for Debian. This card is one of many which use the 'pcnet_cs' driver. In the current (3.1.28) version of pcmcia-cs, there was a bug in the file which is installed on Debian systems as /etc/pcmcia/config. This stanza has a remark symbol incorrectly placed: card Asix AX88190 Fast Ethernet # version Fast Ethernet, 16-bit PC Card, *, AX88190 manfid 0x0149, 0xc1ab bind axnet_cs should be: card Asix AX88190 Fast Ethernet version Fast Ethernet, 16-bit PC Card, *, AX88190 # manfid 0x0149, 0xc1ab bind axnet_cs This problem will disappear from the boot-floppies package as soon as pcmcia-cs version 3.1.29 replaces the current version. Thanks to John Robinson for his help, which did eventually help lead to this solution. Susan Kleinmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't detect NIC
On Wed, Aug 29, 2001 at 09:52:52PM -0400, Susan G. Kleinmann wrote: Susan G. Kleinmann wrote: I'm tyring to install the i386 disks from 'testing' on a Toshiba 1805-S 203, to which I've added a Linksys Combo ethernet card. John H. Robinson wrote: this is what i did, since i knew that the 3.1.22 modules worked for my PCMCIA NIC: installed kernel-source-2.2.19and pcmcia-source into a woody chroot. unpacked them both i took the /boot/config-2.2.19-reiserfs, copied it into /usr/src/kernel-source-2.2.19/.config, cd'd into /usr/src/kernel-source-2.2.19, applies the reiserfs patch (you can skip that part), and did a make-kpkg modules i then installed that .deb, took the /lib/modules/2.2.19/pcmcia directory and tar'd it up, and cp'd the tarbal onto an MSDOS formatted floppy. Thanks for the info. I tried it, got a bunch of unresolved symbol errors, then recompiled the kernel which I'd used to build the pcmcia tarball, replaced the kernel on the floppies, tried again, and still didn't detect the card. I notice that in the 3.1.29 version of the pcmcia card services (not yet packaged for Debian), the CHANGES file says: Fixed some axnet_cs/pcnet_cs config file conflicts Perhaps this will fix the problem. I then gave up and installed potato on the machine, and that worked fine, until of course, I upgraded to the latest version of pcmcia_cs (3.1.28) which gives me the same errors I'd gotten with the woody boot-floppies. It looks like this problem is related to pcmcia-cs and not to the boot-floppies work at all. Thanks again for your speedy response. Susan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't detect NIC
On Fri, Aug 31, 2001 at 12:04:04PM -0400, Susan G. Kleinmann wrote: It looks like this problem is related to pcmcia-cs and not to the boot-floppies work at all. i've seen that, too. i'd recommend installing the 3.1.22potato pcmcia-cs, and if that works, hold the package there echo pcmcia-cs hold| dpkg --set-selectons -john -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't detect NIC
Susan G. Kleinmann wrote:
I'm tyring to install the i386 disks from 'testing' on a Toshiba 1805-S203,
to which I've added a Linksys Combo ethernet card.
John H. Robinson wrote:
you didn't mention which flavour (if any) you were using.
I just used the plain vanilla set of disks:
woody/main/disks-i386/3.0.13-2001-08-25/images-1.44/{rescue,root}.bin
and
woody/main/disks-i386/3.0.13-2001-08-25/images-1.44/driver-{1,2,3,4}.bin
I guess that somehow the system doesn't know that eth0 should be
identified with the pcnet_cs driver. How can I tell it?
i found something similar with my Xircom CreditCard Ethernet CE3B-100BTX
card - some versions (3.1.28) of pcmcia-card-services detect it as a
memory card.
The version of cardmgr that is on the system is indeed 3.1.28.
however, i found that compiling the 3.1.22 modules, and using it with
the 3.1.28 cardmgr (as is found on bf-3.0.13 and greater) provides
satisfactory results.
I guess I'm a little confused here. Do you mean that I should find a
very old version of pcmcia-source (3.1.22 rather than the current 3.1.28),
and then compile that (with some kernel or other)? I take it that when/after
I do that I should place the result *somehow* on the rescue or root disks.
I emphasize somehow because today I ran into another set of problems
which I guess would have to be solved first:
I got the boot-floppies source and just ran 'make' on it, and then
tried to peer at the results. I was able to mount the rescue.bin file on a
loop device:
losetup /dev/loop0 resc1440.bin
mount /dev/loop0 /mnt
umount /mnt
but I was not able to mount root.bin or root1440.bin the same way:
losetup /dev/loop1 root.bin
mount /dev/loop1 /mnt
mount: you must specify the filesystem type
When I guess 'ext2' I got the wrong fs type, ... message; ditto for msdos.
So I don't know how to check the contents of root.bin, or add/replace files
on it.
to gain even more feedback as to what is going on, either start a shell,
or go over to VC2 and start the shell there, and check the output of
dmesg.
I gave cardmgr the option -v, and then looked at the output of dmesg.
It looks as if the system is trying to put the card at IRQ 11.
I notice that WindowsME (the other OS on this laptop right now), seems
to put the card at IRQ 5 at I/O 0x300. I see the messages:
PCI irq 11 test failed and later
axnet_cs: unable to read hardware net address for io base 0x300
How can I force cardmgr to pick up pcnet_cs instead of axnet_cs?
These attempts (admittedly blunderbuss) failed:
-- Erase axnet_cs.o before cardmgr has a chance to find it;
and erase the axnet line in modules.dep. The system still failed
to pick up pcnet_cs by itself.
-- Copy the pcnet_cs.o file to axnet_cs.o and copy the dependencies
for pcnet_cs.o to the dependencies for axnet.o in modules.dep
The system appeared not to have read the modules.dep file under
/target/lib, because it didn't properly pick up the depended-on modules.
If success here is just a matter of forcing cardmgr to try irq 5, then
how do I do that? In particular, what answer should I provide on one of
the dialog boxes related to setting up PCMCIA services?
In an entirely different approach:
I tried to circumvent the whole problem today by copying the base files
to some directory in the Windows partition, and then telling the
installation script that I wanted to install the base system from a mounted
disk. After a number of iterations, I got stuck at the invalid
release file message.
At this point, I don't see a way to install Debian, short of using
the potato floppies. Any alternative ideas appreciated.
TIA,
Susan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
can't detect NIC
I'm tyring to install the i386 disks from 'testing' on a Toshiba 1805-S203, to which I've added a Linksys Combo ethernet card. When I select the menu item to configure the PCMCIA card(s), I choose the i82365 card type option. At that point, the system seems to detect the Linksys card: i.e., it beeps twice, and the link light on the media coupler turns on. Next, I try to configure the network. However, at this point, I get the message no network interfaces were found. When I execute a shell and look at the modules that were loaded when I configured the PCMCIA cards, I notice that they include axnet_cs and af_packet. Both of these are marked as (unused). On other laptops, I've used the pcnet_cs modules to drive the Linksys card. If I simply remove the axnet_cs module and those it depends on modprobe -r pcmcia_core and then install pcnet_cs modprobe pcnet_cs the link light stays on, but the configure-the-network dialog still reports no network interfaces. I guess that somehow the system doesn't know that eth0 should be identified with the pcnet_cs driver. How can I tell it? Or is there some other way to get the system to recognize the NIC? Susan Kleinmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't detect NIC
On Tue, Aug 28, 2001 at 11:03:16AM -0400, Susan G. Kleinmann wrote: I'm tyring to install the i386 disks from 'testing' on a Toshiba 1805-S203, to which I've added a Linksys Combo ethernet card. you didn't mention which flavour (if any) you were using. I guess that somehow the system doesn't know that eth0 should be identified with the pcnet_cs driver. How can I tell it? i found something similar with my Xircom CreditCard Ethernet CE3B-100BTX card - some versions (3.1.28) of pcmcia-card-services detect it as a memory card. however, i found that compiling the 3.1.22 modules, and using it with the 3.1.28 cardmgr (as is found on bf-3.0.13 and greater) provides satisfactory results. to gain even more feedback as to what is going on, either start a shell, or go over to VC2 and start the shell there, and check the output of dmesg. -john -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
