Dear Readers- I have a Gateway 700 MHz Athlon-based PC running Suse 6.3 and kernel 2.2.12. I have 2 pci modems installed. The first is the GVC modem that came with the computer and the second is a 3com model 5610 PCI faxmodem which people have used successfully with linux. Under Windows, the GVC modem has settings com2 and IRQ 5 while the 3com modem has settings com5 and IRQ 9. When I type lspci -v in linux I get the following info: 00:12.0 Serial controller: US Robotics/3Com: Unknown device 1008 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 1008 Flags: medium devsel, IRQ 9 I/O ports at ffe0 Capabilities: [dc] Power Management version 2 00:13.0 Communication controller: CONEXANT: Unknown device 1036 (rev 08) Subsystem: GVC Corporation: Unknown device 1036 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at febe0000 (32-bit, non-prefetchable) I/O ports at ffa8 Capabilities: [40] Power Management version 2 After linking /dev/modem to /dev/ttyS1 (for the GVC modem) or /dev/ttyS4 (for the 3com modem) I use the setserial command as follows: etserial /dev/ttyS1 irq 5 port ffa8 autoconfig (for the GVC modem) or etserial /dev/ttyS1 irq 9 port ffe0 autoconfig (for the 3com modem) Now, when I try to use kppp, it says "Sorry, the modem is busy" When I try to use YAST to configure a PPP network and use Autodetect modem in wvdial I get the message that it was unable to detect a modem. Do these problems suggest that I do not have some piece of software installed or perhaps some module not loaded? Any help with this very frustrating problem would be appreciated. Thanks for the help. Tim Fritz -- 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/Doku/FAQ/
Tim Fritz wrote:
Dear Readers-
I have a Gateway 700 MHz Athlon-based PC running Suse 6.3 and kernel 2.2.12. I have 2 pci modems installed. The first is the GVC modem that came with the computer and the second is a 3com model 5610 PCI faxmodem which people have used successfully with linux. Under Windows, the GVC modem has settings com2 and IRQ 5 while the 3com modem has settings com5 and IRQ 9.
When I type lspci -v in linux I get the following info:
00:12.0 Serial controller: US Robotics/3Com: Unknown device 1008 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 1008 Flags: medium devsel, IRQ 9 I/O ports at ffe0 Capabilities: [dc] Power Management version 2
00:13.0 Communication controller: CONEXANT: Unknown device 1036 (rev 08) Subsystem: GVC Corporation: Unknown device 1036 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at febe0000 (32-bit, non-prefetchable) I/O ports at ffa8 Capabilities: [40] Power Management version 2
After linking /dev/modem to /dev/ttyS1 (for the GVC modem) or /dev/ttyS4 (for the 3com modem) I use the setserial command as follows:
setserial /dev/ttyS1 irq 5 port ffa8 autoconfig (for the GVC modem)
or
setserial /dev/ttyS1 irq 9 port ffe0 autoconfig (for the 3com modem)
Now, when I try to use kppp, it says "Sorry, the modem is busy"
When I try to use YAST to configure a PPP network and use Autodetect modem in wvdial I get the message that it was unable to detect a modem.
Do these problems suggest that I do not have some piece of software installed or perhaps some module not loaded? Any help with this very frustrating problem would be appreciated. Thanks for the help.
Tim Fritz
--
Sounds like you have a dreaded Winmodem!! I believe most PCI modems perform most of their functions in software, and the software runs only under Windows. You may have to splash out on a real modem which performs its functions in hardware. Most ISA modems are real modems, but it pays to check first. I believe there is a list somewhere of modems, saying which will work under Linux and which won't -- cll -- 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/Doku/FAQ/
cll wrote:
Tim Fritz wrote:
Dear Readers-
I have a Gateway 700 MHz Athlon-based PC running Suse 6.3 and kernel 2.2.12. I have 2 pci modems installed. The first is the GVC modem that came with the computer and the second is a 3com model 5610 PCI faxmodem which people have used successfully with linux. Under Windows, the GVC modem has settings com2 and IRQ 5 while the 3com modem has settings com5 and IRQ 9.
When I type lspci -v in linux I get the following info:
00:12.0 Serial controller: US Robotics/3Com: Unknown device 1008 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 1008 Flags: medium devsel, IRQ 9 I/O ports at ffe0 Capabilities: [dc] Power Management version 2
00:13.0 Communication controller: CONEXANT: Unknown device 1036 (rev 08) Subsystem: GVC Corporation: Unknown device 1036 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at febe0000 (32-bit, non-prefetchable) I/O ports at ffa8 Capabilities: [40] Power Management version 2
After linking /dev/modem to /dev/ttyS1 (for the GVC modem) or /dev/ttyS4 (for the 3com modem) I use the setserial command as follows:
setserial /dev/ttyS1 irq 5 port ffa8 autoconfig (for the GVC modem)
or
setserial /dev/ttyS1 irq 9 port ffe0 autoconfig (for the 3com modem)
Now, when I try to use kppp, it says "Sorry, the modem is busy"
When I try to use YAST to configure a PPP network and use Autodetect modem in wvdial I get the message that it was unable to detect a modem.
Do these problems suggest that I do not have some piece of software installed or perhaps some module not loaded? Any help with this very frustrating problem would be appreciated. Thanks for the help.
Tim Fritz
--
Sounds like you have a dreaded Winmodem!! I believe most PCI modems perform most of their functions in software, and the software runs only under Windows. You may have to splash out on a real modem which performs its functions in hardware. Most ISA modems are real modems, but it pays to check first. I believe there is a list somewhere of modems, saying which will work under Linux and which won't --
cll
-- 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/Doku/FAQ/
Go here to check on your modem: http://www.grapevine.net/~gromitkc/winmodem.html Make sure you know the model number of the modem. Nevada -- 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/Doku/FAQ/
On Mon, 20 Mar 2000, Nevada wrote: Ok, I've made these work once or twice. Firstly, you need to make sure that the I/O address is specified as Hexadecimal (put a 0x) in front of it or it is assumed by setserial to be a decimal value. The command that I've used and gotten to work with these modems is something like etserial /dev/modem irq 9 port 0xffe0 uart 16450 skip_test spd_vhi where /dev/modem is a symbolic link to whichever serial device you wish to use for the modem.
cll wrote:
Tim Fritz wrote:
Dear Readers-
I have a Gateway 700 MHz Athlon-based PC running Suse 6.3 and kernel 2.2.12. I have 2 pci modems installed. The first is the GVC modem that came with the computer and the second is a 3com model 5610 PCI faxmodem which people have used successfully with linux. Under Windows, the GVC modem has settings com2 and IRQ 5 while the 3com modem has settings com5 and IRQ 9.
When I type lspci -v in linux I get the following info:
00:12.0 Serial controller: US Robotics/3Com: Unknown device 1008 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 1008 Flags: medium devsel, IRQ 9 I/O ports at ffe0 Capabilities: [dc] Power Management version 2
00:13.0 Communication controller: CONEXANT: Unknown device 1036 (rev 08) Subsystem: GVC Corporation: Unknown device 1036 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at febe0000 (32-bit, non-prefetchable) I/O ports at ffa8 Capabilities: [40] Power Management version 2
After linking /dev/modem to /dev/ttyS1 (for the GVC modem) or /dev/ttyS4 (for the 3com modem) I use the setserial command as follows:
setserial /dev/ttyS1 irq 5 port ffa8 autoconfig (for the GVC modem)
or
setserial /dev/ttyS1 irq 9 port ffe0 autoconfig (for the 3com modem)
Now, when I try to use kppp, it says "Sorry, the modem is busy"
When I try to use YAST to configure a PPP network and use Autodetect modem in wvdial I get the message that it was unable to detect a modem.
Do these problems suggest that I do not have some piece of software installed or perhaps some module not loaded? Any help with this very frustrating problem would be appreciated. Thanks for the help.
Tim Fritz
--
Sounds like you have a dreaded Winmodem!! I believe most PCI modems perform most of their functions in software, and the software runs only under Windows. You may have to splash out on a real modem which performs its functions in hardware. Most ISA modems are real modems, but it pays to check first. I believe there is a list somewhere of modems, saying which will work under Linux and which won't --
cll
-- 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/Doku/FAQ/
Go here to check on your modem:
http://www.grapevine.net/~gromitkc/winmodem.html
Make sure you know the model number of the modem.
Nevada
-- Ray Schwamberger Linux Technician Atipa Linux Solutions -- 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/Doku/FAQ/
On Mon, 20 Mar 2000, cll wrote:
Sounds like you have a dreaded Winmodem!! I believe most PCI modems perform most of their functions in software, and the software runs only under Windows.
We knew all along that winmodems suck processing power, but now we have at least a passable handle on how badly. The iOpener internet appliance - which sells for $99 retail - has a 150 MHz Pentium-class processor. Now you know for certain that, at that price, they are going the cheapest that is just barely good enough for the unsophisticated user. But it has a real modem. -- 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/Doku/FAQ/
participants (5)
-
muzh＠ihug.co.nz -
phthor＠isat.com -
rschwamberger＠atipa.com -
tafritz＠msg.ucsf.edu -
warrl＠blarg.net