Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have picked up a scsi serial modem from an old computer I've cannibalised. It goes fine under linux, windows cannot see it at all!
[later: setting the generic 56k V90 win driver for com1 made a click, but the modem don't respond to the "more details" querie. Did not get a click, though, for the slower drivers ... so, hopefully, this means this is a 56k modem.]
However, I have no idea what it is ... is there are way of querying the scsi devices in linux?
I thought of using cdrecord -scanbus for this (RH9/2.4.20-6) but it keeps telling me I'm using it wrong.
It seems to have a Cirrus Logic chipset (written on the IC's) 9518 & 9517
Anyay - If I find out what it is I'll stick in the HCL. I figure your guys wuold like to have a chuckle over a modem windows cannot use
(I have another one too - UMC chipset and a logo "sysgration" on an e-prom ... untried, I'll let you know more when it's been tested.)
Last edited by Simon Bridge; 05-23-2005 at 06:11 AM.
Your assumption is incorrect - the modem plugs into the (black) scsi slot on the motherboard. It will not fit into any of the (white) pci slots. lspci has no entry for any modems.
Bear in mind here that kudzu detects the modem and it appears on the ttySx device according to however I set the jumpers. I can configure it and dial out. The only issue, besides what it is, is that the speaker dosn't seem to work.
In case you don't believe me...
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc.VT82C686 AC97 Audio Controller (rev 50)
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: Trident Microsystems Cyberblade/i1 (rev 6a)
Ok, I've never heard of a SCSI modem so my next guess is that the modem is an ISA card. In this case The
n the modem is an actual hardware device. So in order to set the speaker level you will need to use an AT command. It has been awhile and I do not remember what it is at the moment.
Excuse me, you're right ... it is ISA (my bad - it's been a while for me too) I guess I got confused because I have an scsi (says so in the manual) scanner (Genius Colorpage-I) which comes with an interface card (from good ol' MS) which only fits the ISA slot. I just got into the habit of referring to the ISA slots as "scussy slots". Sloppy thinking.
OK. So, to rephrase the question... how do I query ISA devices?
I turn the speaker on with # echo "atv" > /dev/ttyS1 (currently set to COM2). No noise - but today it has decided to speak up :/
I can dialout with # echo "atdt <phone number>" > /dev/ttyS1
Hang up with ath and end session with atz.
Maybe this is why I'm having trouble with RH9's network config wizard.
The config works fine, except that the pp0 device (modem) starts as "active". If I try to use the device manager to "deactivate" it, it thinks for a while (30-90s) then return an error: "cannot deactivate ppp0".
In terminal # ifdown ppp0 does something invisible (slow but no errors or nuthin - 800MHz Celeron, so even invisible/silent responces show up as a lag-time) but if I next do
# ifup ppp0
I get "ppp0 already up. Initiating redial"
... but I do not hear a dial.
(Remember, # echo "numbers" > /dev/ttyS1 will dial audibly.)
In minicom - there are no problems.
(Perhaps this should be a different thread? === ASI modem won't deactivate ===)
Querying ISA devices.
ISA cards are kinda dark and creepy, there is no nice tool like "lspci" to probe ISA. ISA is the evil old "plug and pray" behavior. You could try to enable "ISA plug and Pay" (PnP) in your kernel, but it fails to detect the ISA cards, you might have to set interrupts, dma and that kind of tricky config by yourself. Personnally, I hate ISA cards
But still you card is detected, if I understand right. I never tried to make a call with my modem echoing to the device, you are really brave lol. You better install some nice dialer that would do the job for you. I like "wvdial", it's a very minimal, but very complete, script to do that.
Dialler? Sure: minicom autodetects the modem and dials out nicely.
The CLI echo method for locating serial modems is the one taught me by the mad dog
I found a dark place on the card where a large sticker once lived. I checked the box I ripped it out of - and found the sticker ... it says "Dynalink Voice-Data-Fax Modem" I would have liked a baud rate in there too ...
One of these numbers may be a product ID - but Dynalink are no longer around. By "plug-n-pray" I guess you mean there are no standard identifiers stored on the card? (Like psi cards have in the chipset or overiden in an on-board e-prom?) I had more hope for this other card with an e-prom on it, but it has similarily silent. However, I've never known an ISA card to not work.
The windows 56kV90 driver makes a click - but I think 56k would be a tad optimistic for a card this old. At themo, it goes fine at 9600. If I get it dialing from the redhat-config-network dialog, then I'll fiddle the baud rate up until it stops going.