SUSE + PCMCIA + XIRCOM + TOSHIBA = Big Problem
![](https://seccdn.libravatar.org/avatar/db20ad4c25f4f8dbd3e87d931adfbd2c.jpg?s=120&d=mm&r=g)
I got a Xircom 10/100 Lan + 56K Modem CardBus card on a Toshiba TECRA 8000 laptop and I have no way to set up the ethernet interface. Modem works fine, and my other SCSI PCMCIA card works great! This means PCMCIA configuration is fine. I have checked a lot of times mem addr and IRQs conflicts.
But that is so simple whenever I do a "ifconfig eth0 up" the laptop locks. Also if I use yast and yast2 to set up the network I got the same problem when it tries to initilize the ethernet interface (suseconfig runs after configuration and the laptop hangs up).
Time ago I used redhat on this machine with the same hardware, and it worked from the first day! SuSE support team don't help you with PCMCIA because they argue it is advanced configuration they don't support. The fact is that it is very basic network configuration, and without it my laptop is useless.
I found out at source forge web that I am not the only one with this problem (at least we are two). So, nobody has approached it with success??? Is that simple that PCMCIA in SuSE doesn't work for some hardware it does on redhat, and there is no support at all for it?
I have already post this question before on the list. The fact is that I am very desperate, and a bit pissed of with SuSE.
Thanks.
Pep Serrano
![](https://seccdn.libravatar.org/avatar/d7288411250aa8d0e064a0909fe0351c.jpg?s=120&d=mm&r=g)
I got a Xircom 10/100 Lan + 56K Modem CardBus card on a Toshiba TECRA 8000 laptop and I have no way to set up the ethernet interface.
I have this device (the Realport version) working in my Dell laptop. I run it with SuSE-6.4, but I compile my own kernels. I don't know if there's a problem with the SuSE kernels or if the PCMCIA in 7.1 (which I assume you are using) doesn't like it, but I know there have been problems with this device in the past. It took me a while to get it working some time ago, but since the new tulip driver was released (6 months ago?) it's worked perfectly. Which kernel are you using? 2.2 or 2.4? I've not tried 2.4.
![](https://seccdn.libravatar.org/avatar/892c3502df38a2c25ab86c62f8f1df6d.jpg?s=120&d=mm&r=g)
Pep wrote:
Hi Pep, please make your mailer break lines afte 70'something chars. This looks a bit messy now ;-(
I got a Xircom 10/100 Lan + 56K Modem CardBus card on a Toshiba TECRA 8000 laptop and I have no way to set up the ethernet interface. Modem works fine, and my other SCSI PCMCIA card works great! This means PCMCIA configuration is fine. I have checked a lot of times mem addr and IRQs conflicts. But that is so simple whenever I do a "ifconfig eth0 up" the laptop locks. Also if I use yast and yast2 to set up the network I got the same problem when it tries to initilize the ethernet interface (suseconfig runs after configuration and the laptop hangs up).
This moght be no help at all, but a very far guess / hint: After upgrading to 7.1 on my lap (Siemens Scenic 700) I had the same problem, felt pi**ed and went for a fresh install: voila, network but no sound. Next I was pi**ed with the soundcard description. OSS recognised it and with that data I went into ALSA. Voila, network and sound. After the next reboot, it went back into hang-yourself-up mode. Disabled sound, reboot, voila: network. Restarted sound: Sound and network. Finally, I ended up resorting the start order and all seems fine now. I do not know what sort of conflict I was encountering, but guess some weired IRQ / PCI / IO or whatever collition. Idea could be to boot into runlevel 1 (lilo: linux 1) at the boot prompt, cd into /etc/init.d/rc5.d and execute all start scripts in alphanumerical order, leaving some doubtful candidates out and see what happens.
Time ago I used redhat on this machine with the same hardware, and it worked from the first day! SuSE support team don't help you with PCMCIA because they argue it is advanced configuration they don't support. The fact is that it is very basic network configuration, and without it my laptop is useless.
I found out at source forge web that I am not the only one with this problem (at least we are two). So, nobody has approached it with success??? Is that simple that PCMCIA in SuSE doesn't work for some hardware it does on redhat, and there is no support at all for it?
I have already post this question before on the list. The fact is that I am very desperate, and a bit pissed of with SuSE.
/little rant on yes. I know the feeling. But that is what this list is good for. Once you over a certain stage in Linux, you start to believe that install support is as usuable as windows help. This list is the proffessional supporter sitting on our knees. ;-) /little rant off Juergen
Thanks.
Pep Serrano
http://pep.serrano.net PGP Public Key Fingerprint: 8534 A441 2AD8 AF16 926C FD42 C5D1 1F94 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
![](https://seccdn.libravatar.org/avatar/db20ad4c25f4f8dbd3e87d931adfbd2c.jpg?s=120&d=mm&r=g)
Hi All, I have tried to boot runlevel 1 and just run PCMCIA. Again the same problem. Juergen Braukmann said:
Idea could be to boot into runlevel 1 (lilo: linux 1) at the boot prompt, cd into /etc/init.d/rc5.d and execute all start scripts in alphanumerical order, leaving some doubtful candidates out and see what happens.
Cheers,
Pep.
Best Regards,
Pep Serrano
participants (4)
-
Derek Fountain
-
Juergen Braukmann
-
Pep
-
Pep Serrano