Matt T. wrote:
On Monday 09 August 2004 10:57, Sid Boyce wrote:
patheve2@tele2.fr wrote:
Hello
After solving JRE with Mozilla (64 bits), I am trying to use a PCMCIA modem card 16 bits (an Hayes Optima 288 or a Com One MC227 56K) with my Asus laptop Athlon64. On it there are SuSE Pro 9.0 AMD64 and SuSE Pro 9.1 AMD64. These cards do not work on it. On an other laptop (Samsung A10) they work fine with a Slack 8.1 kernel 2.4.18 (32 bits). I was discussing with the PCMCIA linux team about this problem and it thinks that the problem can come from the parameter CONFIG_ISA of the kernel config which is not set "y". For a kernel i386 32 bits, this parameter is set "y" (case of the Slack 8.1 above or of the SuSE 9.0 32 bits) and these cards work. So, why is parameter not set "y" for such 64 bits kernel ? Incompatible ? If not, what do I have to do ? Probably to recompile a new kernel ? If yes, where in the xconfig menu (or with KDE) can I set "y" for this parameter. I found CONFIG_ISAPNP but not CONFIG_ISA.
Regards
Pascal Thevenet
I posted to both groups in the last few days saying what to do. Check that /dev/modem is a symlink to /dev/ttyS0 and not to /dev/cua0. Remove /dev/cua* to stop it relinking to /dev/cua0 after reboot. /dev/cua was deprecated many years ago and I don't know why SuSE has reintroduced it. Asus 1501LCe with 9.1 x86_64 and previously with 9.0 x86_64. Psion Gold Card PCMCIA modem working fine after those changes. Regards Sid.
Hello Sid,
I did reboot the latest SuSE kernel, and the I did do as you suggest, I deleted all /dev/cua* devices. Then I inserting the PCMCIA card.
I deleted /dev/cua*, then rebooted and it came up as /dev/ttyS0. Removed the card and "l /dev/modem" came back with "/dev/modem: No such file or directory". Inserted the card and "l /dev/modem" shows /dev/modem -> /dev/ttyS0 newly created.
Result: card recognized, but *no* device assigned to card. Verified by dmesg and /var/log/messages. So it does not set the wrong link, but it does not even assign any /dev/ttySx to the PCMCIA card.
===
Back to 2.6.8-rc2, and now it is fine again, with and without /dev/cua*. The card gets /dev/ttyS4, and is happy with it. (And so am I.)
Conclusion: I assume that we are seeing here a different problem than you. Some code must have been broken in kernels <= 2.6.5 :-(
It seems that way as I still have the problem with up to 2.6.8-rc3-mm2 as long as /dev/cua* exist. I don't think I checked with vanilla 2.6.8-rc3 - in case it's something in the -mm tree. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====