Hi! I just installed an internal PCI US Robotics 56K Performance Pro in my computer replacing the HFS56 Micro Modem. Windows 98 and SuSE resides on the same hard drive. According to Windows 98, the modem is on Communication Port 5 (five). SuSE Linus can not access it. According to the directtions from US Robotics, if my kernel is version 2.3 or higher, it would recognize the modem. However, according to the command, 'uname -a', my linux version is 2.2.18. How do I upgrade the kernel? I can only access the internet via Windows 98. Being a newby, please provide step-by-step directions. Thank you for your help. Ken Green
On Sun, 13 May 2001, Ken wrote:
I just installed an internal PCI US Robotics 56K Performance Pro in my computer replacing the HFS56 Micro Modem. Windows 98 and SuSE resides on the same hard drive. According to Windows 98, the modem is on Communication Port 5 (five). SuSE Linus can not access it.
According to the directtions from US Robotics, if my kernel is version 2.3 or higher, it would recognize the modem. However, according to the command, 'uname -a', my linux version is 2.2.18.
The older kernel only recognizes com 1-4, and this modem insists on being on com 5. But you do not necessarily have to upgrade your kernel just to be able to use this modem. You can make this modem work without upgrading the kernel. Find out the port and IRQ with lspci -v. Then give a command similar to the following (replace my values with yours): setserial /dev/ttyS3 uart 16550a port 0xb800 irq3 Once you have it working, put the command in your /etc/rc.d/boot.local *************************************************** Powered by SuSE Linux 7.0 Professional KMail 1.0.29.2 Bryan S. Tyson bryantyson@earthlink.net ***************************************************
"Bryan S. Tyson" wrote:
On Sun, 13 May 2001, Ken wrote:
I just installed an internal PCI US Robotics 56K Performance Pro in my computer replacing the HFS56 Micro Modem. Windows 98 and SuSE resides on the same hard drive. According to Windows 98, the modem is on Communication Port 5 (five). SuSE Linus can not access it.
The older kernel only recognizes com 1-4, and this modem insists on being on com 5. But you do not necessarily have to upgrade your kernel just to be able to use this modem.
You can make this modem work without upgrading the kernel. Find out the port and IRQ with lspci -v. Then give a command similar to the following (replace my values with yours):
setserial /dev/ttyS3 uart 16550a port 0xb800 irq3
From the root directory and after typing in:
setserial /dev/ttyS3 uart 16500a port d000 irq9 received the following error message: Invalid flag: irq9 Now what? Thanks for anybody help. Ken Green
Try forcing your PCI cards to their own IRQ's so that they aren't sharing IRQ's. You can make sure that the first 4 PCI slots take up IRQ's like this Slot 1 - IRQ9 Slot 2 - IRQ10 Slot 3 - IRQ11 Slot 4 - IRQ12 Most mother boards let you assign IRQ's like this. I don't know your bios so your gonna have to check this out. -> ->>From the root directory and after typing in: -> ->setserial /dev/ttyS3 uart 16500a port d000 irq9 -> ->received the following error message: -> ->Invalid flag: irq9 -> ->Now what? -> ->Thanks for anybody help. -> ->Ken Green -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
Ben Rosenberg wrote:
Try forcing your PCI cards to their own IRQ's so that they aren't sharing IRQ's. You can make sure that the first 4 PCI slots take up IRQ's like this
Slot 1 - IRQ9 Slot 2 - IRQ10 Slot 3 - IRQ11 Slot 4 - IRQ12
Most mother boards let you assign IRQ's like this. I don't know your bios so your gonna have to check this out.
Thanks to you and several other people, I was able to get the modem connected to ttyS3 by using the following commands: lspci -v setserial /dev/ttyS3 uart 16500a port oxdoo irq 9 setserial -g /dev/ttyS3 Thanks to all of those who helped. Regard, Ken Green
Hi. There is nothing wrong in sharing interrupts. In my case since mobo and ISA ports occupy most irq's, I have all PCI cards and mobo USB sharing IRQ 11 (USB controller, two graphics, TV digitizer (audio&video), lan card, two PCI serials, one PCI parallel). A possible reason for the problem is that for sharing irq, software must be written with interrupt sharing in mind. For the serial module this has been done recently (see http://serial.sourceforge.net), so could be you had not serial.c updated, and had to not use serial irq sharing. ----- Original Message ----- From: "Ken Green" <seahawk@bdcsi.net> To: "Ben Rosenberg" <ben@whack.org> Cc: "SLE" <suse-linux-e@suse.com> Sent: Monday, May 14, 2001 2:07 AM Subject: Re: [SLE] Modem on Port 5
Ben Rosenberg wrote:
Try forcing your PCI cards to their own IRQ's so that they aren't sharing IRQ's. You can make sure that the first 4 PCI slots take up IRQ's like this
Slot 1 - IRQ9 Slot 2 - IRQ10 Slot 3 - IRQ11 Slot 4 - IRQ12
Most mother boards let you assign IRQ's like this. I don't know your bios so your gonna have to check this out.
Thanks to you and several other people, I was able to get the modem connected to ttyS3 by using the following commands:
lspci -v
setserial /dev/ttyS3 uart 16500a port oxdoo irq 9
setserial -g /dev/ttyS3
Thanks to all of those who helped.
Regard,
Ken Green
* Webillo Disperso (webillo@mi.madritel.es) [010514 01:23]: ->Hi. -> ->There is nothing wrong in sharing interrupts. In my case since mobo and ->ISA ports occupy most irq's, I have all PCI cards and mobo USB sharing ->IRQ 11 (USB controller, two graphics, TV digitizer (audio&video), lan ->card, two PCI serials, one PCI parallel). -> ->A possible reason for the problem is that for sharing irq, software must ->be written with interrupt sharing in mind. For the serial module this ->has been done recently (see http://serial.sourceforge.net), so could be ->you had not serial.c updated, and had to not use serial irq sharing. -> I personally don't have any issues with IRQ sharing, but I have seen several MB's have had issues with this under Linux..no matter if the software was written for it. It has to do with the hardware not working properly. The suggestion I made just forces a certain situation. It's all good. If you know of another solution..its cool. No problem. -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
According to Windows 98, the modem is on Communication Port 5 (five). SuSE Linus can not access it.
If you get port 5 under windows it is because it is in plug&play mode. If your modem is the type of pci modem that I think it it should have jumpers on it which let you pick the com port or plug&play. If you dont have jumpers on your modem throw it to the nearest trash can. Raul
On Mon, 14 May 2001, Raul wrote:
If you get port 5 under windows it is because it is in plug&play mode. If your modem is the type of pci modem that I think it it should have jumpers on it which let you pick the com port or plug&play. If you dont have jumpers on your modem throw it to the nearest trash can.
In many cases that is true, but not in this case. This modem works fine with Linux. The problem in this case was the kernel only recognized com 1-4. Using set serial solves the problem. The original poster has already reported he has it working. I have been using this modem myself for quite a while with no problems in Linux. *************************************************** Powered by SuSE Linux 7.0 Professional KMail 1.0.29.2 Bryan S. Tyson bryantyson@earthlink.net ***************************************************
participants (5)
-
Ben Rosenberg
-
Bryan S. Tyson
-
Ken Green
-
Raul Gutierrez Segales
-
Webillo Disperso