Patrick, You are very right. I am running a dual boot system. First 15G are used for Windows XP Professional. Next 15 G are for SuSE 7.3 I am using Microsoft Multiboot (similar in XP to NT version), and seems to work ok. BIG question: By "remove the modem" you mean physically? or just erase it from hardware list in Windows? I will try that... and it has sense, since I dont understand why "lspci -v" command throws this: 02:0b.0 Communication controller: TOPIC SEMICONDUCTOR Corp: Unknown device 0000 Subsystem: TOPIC SEMICONDUCTOR Corp: Unknown device 0000 Flags: medium devsel, IRQ 4 I/O ports at d800 [disabled] [size=8] ^--------------------------------DISABLED? I have done some research and reading to establish which modem to use with Linux, and from the famous http://www.linmodems.org , it seems modems using TOPIC chipset (specially 5634PCV) are one of the few hardware modems that work with linux...... that is why it is supposed to work only by using "setserial" command, and not using a software driver..... And yes, it costed me $50+ :) -------------------------------------------------------- Juan Francisco Torres Ch. ----- Original Message ----- From: "Patrick" To: "Juan Francisco Torres Chacón" Sent: Monday, July 08, 2002 1:50 PM Subject: Re: [SLE] Modem 5634PCV and Suse 7.3 On Monday 08 July 2002 12:26, Juan Francisco Torres Chacón wrote:

Well i am still fighting with my new machine and SuSE 7.3

I have a 5634PCV SurfRider from Archtek Telecom, and it is supposed NOT to be a Winmodem...

I have followed the procedure described, using: setserial /dev/ttyS2 port irq uart16550A (obtained from /proc/pci)

But nor wvdialconf or minicom recognizes the modem....

ANYONE? the "lspci -v" command shows an strange "disabled" text in front of I/O address... this is it?

Help please

---------------------------------------------------- Juan Francisco Torres Ch. ==================

Juan, Are you running a dual boot system? Do you have Windows installed as well on that machine? I am going to assume you do since your mail came from Outlook Express. Most of the setups I have seen and done with an internal hardware modem always seem to fail on the Linux side if the modem is first setup on the Windows side. Win seems to block or hinder the modem from being recognized in Linux for some reason. Try this, remove the modem from the windows side and boot into Linux. Use Yast2 control center to set up your modem now. You might want to check which com port Windows has it set on before removing, so you can know what ttyS0x number it should be on in Linux. I think you will find Linux has an easier time locating it automatically this way. After setting Linux, then you can boot back to Windows and set it there again. I am not familar with this modem to know if it is a hardware or software (winmodem). You might check the manufacturer's site for more info or the selling price of the modem. If the modem sells for $30 or less, it is quite likely a winmodem. Hardware modems usually sell for $50+, even from the discount houses. Patrick -- ----------end of line........ --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206