Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
10-21-2004, 02:35 AM
|
#1
|
Member
Registered: Aug 2004
Location: Bern, Switzerland
Distribution: Kubuntu, FC, RHEL
Posts: 48
Rep:
|
RH doesn't detect my USB Modem
I've connected a Zyxel Omni 56K Plus USB Modem to a 64Bit Box running Redhat Enterprise Linux 3. However, it doesn't get detected.
Here's the details
Code:
# wvdialconf /etc/wvdial.conf
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8
Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16
Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24
Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 SA0
Port Scan<*1>: SA1 SA2 SC0 SC1 SC2 SC3 SI0 SI1
Port Scan<*1>: SI2 SI3 SI4 SI5 SI6 SI7 SI8 SI9
Port Scan<*1>: SI10 SI11 SI12 SI13 SI14 SI15 SR0 SR1
Port Scan<*1>: SR2 SR3 SR4 SR5 SR6 SR7 SR8 SR9
Port Scan<*1>: SR10 SR11 SR12 SR13 SR14 SR15 SR16 SR17
Port Scan<*1>: SR18 SR19 SR20 SR21 SR22 SR23 SR24 SR25
Port Scan<*1>: SR26 SR27 SR28 SR29 SR30 SR31 SR256 SR257
Port Scan<*1>: SR258 SR259 SR260 SR261 SR262 SR263 SR264 SR265
Port Scan<*1>: SR266 SR267 SR268 SR269 SR270 SR271 SR272 SR273
Port Scan<*1>: SR274 SR275 SR276 SR277 SR278 SR279 SR280 SR281
Port Scan<*1>: SR282 SR283 SR284 SR285 SR286 SR287 USB0 USB1
Port Scan<*1>: USB2 USB3 USB4 USB5 USB6 USB7 USB8 USB9
Port Scan<*1>: USB10 USB11 USB12 USB13 USB14 USB15 ircomm0 ircomm1
Port Scan<*1>: ircomm2 ircomm3 ircomm4 ircomm5 ircomm6 ircomm7 ircomm8 ircomm9
Port Scan<*1>: ircomm10 ircomm11 ircomm12 ircomm13 ircomm14 ircomm15
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
I haven't been successful with setserial yet, because I don't know on what device it is supposed to be. I've tried with /dev/ttyUSB0 1 and 2 but I always got this as an answer:
Code:
# setserial /dev/ttyUSB0
/dev/ttyUSB0: No such device
I've got 2 USB slots on the box and when plugging the modem into one or the other, I get one small difference in the output of /proc/bus/usb/devices which is rendered in bold below:
Code:
# cat /proc/bus/usb/devices
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.04
S: Manufacturer=Linux 2.4.21-15.EL ehci-hcd
S: Product=Intel Corp. 82801EB USB2
S: SerialNumber=00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
T: Bus=04 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 2
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=a001 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=01 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms
I: If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=9ca0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
Only difference is here:
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
Difference ends here
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0586 ProdID=1500 Rev= 0.01
C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=9cc0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 32/900 us ( 4%), #Int= 2, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=9ce0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=2500 Rev= 0.00
S: Manufacturer=Dell
S: Product=DRAC4
S: SerialNumber=0000000
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=16ms
I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid
E: Ad=82(I) Atr=03(Int.) MxPS= 6 Ivl=2ms
I've found a documentation of this file. The meaning would be that only the " Topology line changes.
The first time it reads:
Bus number: 3
Level in topology for this bus: 1
Parent deviceNumber: 1
Connector/Port on Parent for this device: 0
Count of devices at this level: 1
Device Number: 2
Device Speed in Mbps: 12
MaxChildren: 0
The second time it reads:
Bus number: 3
Level in topology for this bus: 1
Parent deviceNumber: 1
Connector/Port on Parent for this device: 1
Count of devices at this level: 1
Device Number: 3
Device Speed in Mbps: 12
MaxChildren: 0
That's how far I got. But I have no idea if this can help me identify the device where it is connected, and then, have my box "see" the modem. Any help greatly appreciated.
|
|
|
10-21-2004, 06:07 PM
|
#2
|
LQ Guru
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700
Rep:
|
I don't think it has loaded a driver for the modem at all. Almost all USB modems were of one singular type, so let's hail mary load that driver:
/sbin/modprobe acm
If that loads right, check:
dmesg
And see what stty device it got in /dev.
If in doubt, post back with the output of dmesg and the error from modprobe.
Cheers,
Finegan
|
|
|
10-22-2004, 01:31 AM
|
#3
|
Member
Registered: Aug 2004
Location: Bern, Switzerland
Distribution: Kubuntu, FC, RHEL
Posts: 48
Original Poster
Rep:
|
Thanks Finegan. I got that hint about the driver yesterday and have a link ready. But before compiling a driver and all the stuff I hope your trick works.
First of all, everything you told didn't output an error message. That's already a good sign. Here's my session:
Code:
# /sbin/modprobe acm
# dmesg | grep acm
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
# cd /dev
# ls -l | grep stty
lrwxrwxrwx 1 root root 4 Oct 7 18:01 systty -> tty0
Ok, so next thing to try, but I'm not sure the tty0 is really what we want...
Code:
# setserial /dev/tty0
Cannot get serial info: Invalid argument
Well... stuck again... Going to try to compile the driver anyway and will report my progress here. If you have any suggestions, don't hesitate to post. Thanks
|
|
|
10-22-2004, 02:30 AM
|
#4
|
Member
Registered: Aug 2004
Location: Bern, Switzerland
Distribution: Kubuntu, FC, RHEL
Posts: 48
Original Poster
Rep:
|
Since it didn't work, I thought rebooting the machine would help. But instead it forgot all I told it before. How to make the changes from modprobe persistent?
Then this:
http://www.zyxel.com/support/knowled...lag=1021681602
Q: Is there Linux driver for omni.net USB model?
A: Sorry, so far we do not have plan to support Linux driver for omni.net USB.
dammit. Ok. Then we have to buy another modem. Any suggestions for a good Linux USB-modem? It has to be an USB since there's no available serial port on the box. Thanks
|
|
|
10-22-2004, 05:10 PM
|
#5
|
LQ Guru
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700
Rep:
|
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
Were the only two lines to appear, it'll load no matter what, unlike most drivers that kick errors if the device isn't present. If there's a line after that about what stty got assigned then its the acm chipset...
The only reason I have one is that we got them free in these Dish Network throw-aways that we gutted for parts.
Modems are usually pretty regional, the USB ones I have are called "New Media v.90 USB Modem", no model number, nothing... and most of the googling I can do brings up adsl and cable modems. Dial-up is a hard world under Linux just for this reason. There isn't anything in our HCL about them and very little elsewhere, maybe if you can test them before you buy...
Cheers,
Finegan
|
|
|
10-25-2004, 06:37 AM
|
#6
|
Member
Registered: Aug 2004
Location: Bern, Switzerland
Distribution: Kubuntu, FC, RHEL
Posts: 48
Original Poster
Rep:
|
We are going a different track now. Last friday we've ordered an additional PCI-Serial card and I'm trying to install it right now.
|
|
|
10-25-2004, 09:30 AM
|
#7
|
Member
Registered: Aug 2004
Location: Bern, Switzerland
Distribution: Kubuntu, FC, RHEL
Posts: 48
Original Poster
Rep:
|
Serial PCI Card problems
The PCI Card we bought is the following:
EX-41092: 2S PCI Serial card RS-232 32/64-Bit with 2 x FIFO 16C950, (3.3V and 5V)
There's even a step-by-step installation instruction for Linux.
The spot in the installation instructions where they say that in the file /proc/pci I should find an information like "Vendor id=1409, Device id=7168" however lost me a little bit, since it didn't appear in my file. So I did the following:
Code:
# lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0f.0 Serial controller: Oxford Semiconductor Ltd EXSYS EX-41092 Dual 16950 Serial adapter
00:0f.1 Parallel controller: Oxford Semiconductor Ltd: Unknown device 9500
00:14.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:14.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:14.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:14.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP (rev 3a)
The lines I'm emphasizing above appeared only when the card was inserted, so I suppose they refer to it. Then I checked the /proc/pci file again. Here are the lines that appear only when the card is inserted:
Code:
Bus 0, device 15, function 0:
Class 0700: PCI device 1415:950a (rev 0).
IRQ 11.
I/O at 0x2440 [0x245f].
Non-prefetchable 32 bit memory at 0x42000000 [0x42000fff].
I/O at 0x2460 [0x247f].
Non-prefetchable 32 bit memory at 0x42100000 [0x42100fff].
Bus 0, device 15, function 1:
Class 0701: PCI device 1415:9500 (rev 0).
IRQ 11.
I/O at 0x2430 [0x2437].
I/O at 0x2438 [0x243f].
I/O at 0x2480 [0x249f].
Non-prefetchable 32 bit memory at 0x42200000 [0x42200fff].
So I then proceeded with setserial as follows, using the hexadecimal addresses emphasized above:
Code:
setserial /dev/ttyS2 uart 16550A port 0x2440 irq 10 baud_base 921600 spd_normal skip_test auto_irq
setserial /dev/ttyS3 uart 16550A port 0x2460 irq 10 baud_base 921600 spd_normal skip_test auto_irq
Now the problem: whenever I run "wvdialconf /etc/wvdial.conf" and get the message:
Code:
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
First I had them on ttyS1 and ttyS2 respectively, but the computer used to lock (keyboard. network, screen) whenever I run wvdialconf. Is there an IRQ problem somewhere? I know the devices ttyS1 and ttyS2 are free.
|
|
|
10-25-2004, 07:21 PM
|
#8
|
LQ Guru
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700
Rep:
|
Honestly, I know very little about serial devices. I've had to use minicom exactly once in order to repair an old SAN device, and the thread title and the number of posts is going to make for fewer eyeballs on this thread. I would not consider it double posting at all if you started a whole new thread as this really is a whole new problem.
Cheers,
Finegan
|
|
|
All times are GMT -5. The time now is 09:09 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|