Ssue 8 not detecting my isapnp modem as a modem
 

It knows about the device under isapnp on the hardware device listing but it is not listed under modem. I cant set up my internet connection no matter if I use dev modem or ttySx as device. I have the same setup working in Mandrake 9 using dev modem with no problems. Any body have any idea how to let Suse know where my modem is? It is a Diamond Supraexpress. Thanks

Usually when you have /dev/modem its just a symlink or link from the corresponding /dev/ttySx... Just link it to the correct ttySx and see what happens.

Also, I am moving this to the hardware forum, where its more suitable since its a hardware problem.

I tried manually configuring the "other modem" in Suse but no matter what dev/ttySx i use it wont work. Kppp cannot connect also. In my Linux Mandrake 9 partition the modem is at /dev/ttyS1 and works fine. When I browse the hardware info in Yast2, it is listed as isapnp and i am able to get the resources such as irq etc. I am wondering if there is a way to let the operating system know that the modem is actually at this resource address. Also, Suse detects a modem which it labels as AT modem but if i try to configure it it doesnt work. I think this is /dev/modem.

you may have to add a setserial line in boot.local
http://sdb.suse.de/sdb/en/html/hoe_pci_modem.html

I would try a PCI modem instead. I have always had trouble with ISA devices in Linux.

Thanks for all the advice. I followed the Suse setserial trail. and was able to configure the modem by doing:
1. pnpdump > /etc/isapnp.conf
2. uncomment the part of isapnp.conf which sets io to 0x3e8 and irq to 4 (corresponding to /dev/ttyS2) and also remove the (CHECK) on the io line
3. setserial /dev/ttyS2 UART unknown
4. isapnp /etc/isapnp.conf
5. setserial /dev/ttyS2 UART 16550A
6. Yast2 to setup the connection from here.
7. edit /etc/rc.d/boot.local to include step # 5

It works! the only problem I have is that when Suse 8 automatically runs isapnp /etc/isapnp.conf at startup it results in a conflict because step # 3 above is not executed prior to step # 4. Is there a way to tell the OS not to assign a UART to /dev/ttyS2 (thus leaving its speed at "unknown") during startpup so isapnp /etc/isapnp.conf will not fail? Thanks again for any help. I am writing this from Suse 8.

Never Mind. I was able to figure out what to do. Just open /etc/rc.d/serial and on the line for run_setserial /dev/ttyS2 uart 16450 port 0x3e8 irq 4 under Manual Configuration, just change 16450 to unknown and the rest of the steps should work without an error. Thanks again for everybody's help in this matter.