Hello again Matt At first, I tested my Com One modem card MC277 with WinXP on my laptop (WinXP, SuSE 9.0 and SuSE 9.1). Sure, it works without driver. I had a look in the hardware profil. WinXp gives this : - first socket : memory ranges : fd200000-fd200fff , feaf7000-feaf7fff , fb200000-fd1fffff, feafc000-feafcfff I/O ranges : dc00-dcff , d400-d4ff - second socket : memory ranges : fa200000-fa200fff , feaf5000-feaf5fff , fdaf5000-feaf4fff , feaf6000-feaf6ffff I/O ranges : d000-d0ff , cc00-ccff - PCI bridge : I/O range : b000-dfff memory range : f8a00000-feafffff (NB : same info than with lspci -v) After pluggin of the MC227, WinXP "says" about it : IRQ: 09 I/O Range : c8f8-c8ff port : COM5 driver : serial.sys, modem.sys In case of the Hayes modem card, the port is COM4 instead of COM5 and there is a 3rd driver : hayes.sys So, why not to use these data in the config.opts file ? For memory : fa200000-feafcfff, for I/O : b000-dcff . I did it but with no success. I don't know which values to use for I/O and memory . I tried with the range of PCI bridge : no success. No more hope ? And a curious behaviour during the shutdown of the laptop : the process fails at the stopping of the PCMCIA service when a modem card is plugged and no way after for reaching a complet shutdown. I have to switch off the laptop with the button. Regards Pascal ============================================ On Tuesday 23 November 2004 04:34, patheve2 wrote: /> Hello / /> / /> Yes, I confirm that the infos I gave are the right ones for / /> kernel 2.6.8 . For no confusion (right english word ?) I join the / /> 3 files : serial.opts, config and config.opts. I used these for he / /> following tests. Curious behaviour of the modem card, in particular / /> the Com One which should work according this website : / /> http://tuxmobil.org/pcmcia_ci10478.html / /> So, with these below details, I hope that it will help you to find the / /> reason why the modem cards are so "hard" to work properly :-) / /> / /> Regards / /> / /> Pascal / /> / /> 1/ case of the Com Oen card MC227 (modem) / /> So, before pluggin : / /> / /> - lsmod : / /> / /> ds 21128 4 / /> yenta_socket 21248 0 / /> pcmcia_core 66188 2 ds,yenta_socket / /> / /> And after pluggin : / /> / /> - dmesg : / /> cs: memory probe 0xf8a00000-0xfd1ff000: excluding 0xf8a00000-0xfa4f3fff / /> 0xfadf0000-0xfb26dfff 0xfb6ec000-0xfd65dfff / this is *not* good. On my system serial_cs says which serial port it did assign to the card (I'm not at the system, so I cannot quote the exact message). Once it worked, it did not mention the memory ranges, which it did scan, anymore. This looks as if you insert the card, then cs gets started, scans the memory, but does not find anything. Thus the card does not get a serial port assigned. You need to work on the memory / port ranges, as long as there is no serial port assigned to your card by serial_cs. (If the card does not need a special driver, then of course serial_cs is irrelevant, but that driver would need to get loaded). /> / /> - more /var/log/messages under root login : / /> / /> Nov 22 21:37:13 snidre kernel: cs: memory probe 0xf8a00000-0xfd1ff000: / /> excluding 0xf8a00000-0xfa4f3fff 0xfadf0000-0xfb26dfff 0xfb6ec000-0xfd65dfff / /> Nov 22 21:37:13 snidre cardmgr[2816]: socket 0: Serial or Modem / /> / /> - lsmod : / /> serial_cs 11176 1 / /> ds 21128 5 serial_cs / /> yenta_socket 21248 1 / /> pcmcia_core 66188 3 serial_cs,ds,yenta_socket / /> / /> - ls -al /dev/mod* : / /> / /> lrwxrwxrwx 1 root root 9 Nov 22 21:37 /dev/modem -> /dev/cua4 / /> / /> / /> 2/ case of the Hayes Optima288 card (modem) : / /> / /> - more /var/log/messages under root login (not enough data with only / /> dmesg) : / /> / /> Nov 22 21:44:28 snidre cardmgr[2816]: socket 0: Hayes Optima 288 / /> Nov 22 21:44:29 snidre kernel: ttyS5 at I/O 0xd000 (irq = 9) is a 16450 / Here ttyS5 seems to get assigned. I wonder why dmesg does not show it. Is there really no mention of ttyS5 in dmesg? /> / /> - lsmod : / /> / /> serial_cs 11176 1 / /> ds 21128 5 serial_cs / /> yenta_socket 21248 1 / /> pcmcia_core 66188 3 serial_cs,ds,yenta_socket / /> / /> - ls -al /dev/mod* : / /> / /> lrwxrwxrwx 1 root root 9 Nov 22 21:44 /dev/modem -> /dev/cua5 / I do not think that /dev/cua5 is the good device. Try to make a link /dev/modem -> /dev/ttyS5 instead, and try to talk to the modem (minicom should be OK, or dial with kppp) If this does not work, then your back at the problem that serial_cs does not read your card correctly. Sorry, in a rush, the car is leaving. HTH, Matt