Did you put a space between setserial and the device? Did you put the appropriate spaces in when executing the ln command like so? ln -s /dev/ttyS3 /dev/modem? I was wondering because the info that you show does not have the spaces in there. Marshall Heartley A+,Network+ "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible." On Tue, 2002-06-04 at 12:50, Forrest Halford wrote:
OK I realy appreciate the help, but this message keeps coming up
my info is such:
US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8 4-1 should be linux ttyS3 yes??
When linux is starting up it says...... interupt 3 ttyS3 is 16550A Whatever that means.....
Now for the results when I ldo what you just mentioned..... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ galt@linux:~> su Password: linux:/home/galt # l-s/dev/ttyS3/dev/modem bash: l-s/dev/ttyS3/dev/modem: No such file or directory linux:/home/galt # setserial/dev/ttyS3 bash: setserial/dev/ttyS3: No such file or directory linux:/home/galt # setserial/dev/ttyS1 bash: setserial/dev/ttyS1: No such file or directory linux:/home/galt # setserial/dev/ttyS2 bash: setserial/dev/ttyS2: No such file or directory linux:/home/galt # setserial/dev/ttyS3 bash: setserial/dev/ttyS3: No such file or directory linux:/home/galt # setserial/dev/ttyS4 bash: setserial/dev/ttyS4: No such file or directory linux:/home/galt # setserial/dev/ttyS5 bash: setserial/dev/ttyS5: No such file or directory linux:/home/galt # setserial/dev/ttyS6 bash: setserial/dev/ttyS6: No such file or directory linux:/home/galt # setserial/dev/ttyS7 bash: setserial/dev/ttyS7: No such file or directory linux:/home/galt # setserial/dev/ttyS8 bash: setserial/dev/ttyS8: No such file or directory linux:/home/galt # setserial/dev/ttyS9 bash: setserial/dev/ttyS9: No such file or directory linux:/home/galt #
What gives ?
Thanks Forrest
On Mon, 3 Jun 2002 22:31:49 -0700, a large badger frolicked about on your keyboard, and out came:
it is a lower case L
you need to determine the com port that your modem is assigned to. you can do this by knowing what irq your external modem uses an IRQ interupt request is sort of like an adress that is stored in the bios for each piece of hardware conected to the computer the piece of hardware and the processor use this irq to get each other attention and comunicate. we need to know your modems irq generally speaking two devices should not share the same irq because sometimes this causes a conflict we need to know your modems irq get it from kde control center --- information -- interrupts in the list it should be a device called serial write the irq down or find it in windows like i said or get it from looking at the jumpers in your modem and its manual just determine its irq or check your bios setup program for its irq we need to know your modems irq wvdial or any dialup program needs to know the comport that is assigned to your modem the comport is a combination of your modems irq and an IO address represented by a number with you irq for your modem we can determine your com port for Linux at promt type cat /proc/tty/driver/serial find the device that matches your irq or the one that list a baud rate and write down the number at the start of that line its your /dev/ttyS# replace the # with the number you may have to try this with a couple of them that match the irq then use your /dev/ttyS# in the following l -s /dev/ttyS<com id> /dev/modem fire up wvdial and try if not keep replacing the # with numbers 0 through20 in /dev/ttyS# and retrying wvdial each time until it works max
On Monday 03 June 2002 09:50 pm, Forrest Halford wrote:
l -s /dev/ttyS<com id> /dev/modem
Is that supposed to be "l" or ?
Also, I do not understand this part....
then type setserial /dev/ttySx where x is a number 1-9 keep doing this until you find your modems irq and the result says unknown and then use the ln comand but replace the ttySx with the ones that match your irq
Thanks, we are getting closer.... 8-) Forrest
On Mon, 3 Jun 2002 21:47:06 -0700, a large badger frolicked about on your keyboard, and out came:
ok heres what we do. if it is a dual boot machine boot into windows right click on my computer select properties look in device manger for your modem and for installed com ports what com port does your modem use in windows subtract 1 from your windoze com port # the result its your linux com id and in Linux do l -s /dev/ttyS<com id> /dev/modem or what IRQ does your modem use in device manger windows? determine your modems IRQ from it or it manual
then type setserial /dev/ttySx where x is a number 1-9 keep doing this until you find your modems irq and the result says unknown and then use the ln comand but replace the ttySx with the ones that match your irq
On Monday 03 June 2002 09:10 pm, Forrest Halford wrote:
I have a US RObotics 56k external fax modem. The greatest modem ever made for linux and it worked great under Suse 7.2
this is an AMD duron 750 MHz with biostar board and 128 megs of sdram
The modem works great on windows....
Have you tryed yast2 network basic modem configuration?
Yes, it hangs at 0% done in the searching for installed modems part.....
Thanks for all the help.....we will get there....
Forrest
On Mon, 3 Jun 2002 21:02:55 -0700, a large badger frolicked about on your
keyboard, and out came:
Ok, What type of modem do you have? IE internal PCI, Internal ISA, external serial modem, external usb modem, internal laptop modem, pcmcia modem/eternet combo ? Are we talking about a laptop?
please let me know
That tool mark means it needs to be configred
Have you tryed yast2 network basic modem configuration?
we will solve your problem
It may be the a combo modem/ethernet device and actually be
00:09.0 Ethernet controller: 3Com Corporation 3c900 Combo [Boomerang] Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at e800 [size=64] Expansion ROM at <unassigned> [disabled] [size=64K]
On Monday 03 June 2002 08:41 pm, Forrest Halford wrote: > Thanks for the detailed response.... > But,.... > Ok here is what I get, and I cannot find my modem, while it does show > up in the "information" part of the KDE menu......as the correct > modem.....it has the little tool mark nest to it ,...... > > > galt@linux:~> su > Password: > linux:/home/galt # lspci -v > 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] > (rev 03) Flags: bus master, medium devsel, latency 0 > Memory at d8000000 (32-bit, prefetchable) [size=64M] > Capabilities: [a0] AGP version 2.0 > Capabilities: [c0] Power Management version 2 > > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 > AGP] (prog-if 00 [Normal decode]) > Flags: bus master, 66Mhz, medium devsel, latency 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: 0000c000-0000cfff > Memory behind bridge: dc000000-ddffffff > Prefetchable memory behind bridge: d0000000-d7ffffff > Capabilities: [80] Power Management version 2 > > 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super > South] (rev 40) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to > ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 > Capabilities: [c0] Power Management version 2 > > 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) > (prog-if 8a [Master SecP PriP]) > Flags: bus master, medium devsel, latency 32 > I/O ports at d000 [size=16] > Capabilities: [c0] Power Management version 2 > > 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) > (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 > Flags: bus master, medium devsel, latency 32, IRQ 10 > I/O ports at d400 [size=32] > Capabilities: [80] Power Management version 2 > > 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super > ACPI] (rev 40) Flags: medium devsel, IRQ 9 > Capabilities: [68] Power Management version 2 > > 00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 > Audio Controller (rev 50) Subsystem: Sigmatel Inc: Unknown device > 7609 Flags: medium devsel, IRQ 5 > I/O ports at dc00 [size=256] > I/O ports at e000 [size=4] > I/O ports at e400 [size=4] > Capabilities: [c0] Power Management version 2 > > 00:09.0 Ethernet controller: 3Com Corporation 3c900 Combo [Boomerang] > Flags: bus master, medium devsel, latency 32, IRQ 11 > I/O ports at e800 [size=64] > Expansion ROM at <unassigned> [disabled] [size=64K] > > 00:0b.0 ATM network controller: Intel Corp.: Unknown device 5005 (rev > 02) Subsystem: Intel Corp.: Unknown device 0003 > Flags: bus master, slow devsel, latency 32, IRQ 10 > I/O ports at ec00 [size=256] > Memory at df000000 (32-bit, non-prefetchable) [size=256] > > 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon QD > (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Radeon 7000/Radeon > Flags: bus master, stepping, 66Mhz, medium devsel, latency > 32, IRQ 12 Memory at d0000000 (32-bit, prefetchable) [size=128M] I/O > ports at c000 [size=256] > Memory at dd000000 (32-bit, non-prefetchable) [size=512K] > Expansion ROM at <unassigned> [disabled] [size=128K] > Capabilities: [58] AGP version 2.0 > Capabilities: [50] Power Management version 2 > > linux:/home/galt # > > > From: Max Webb aka "That weird Linux guy", aka the guy that cant ever > seem to > > >get a date and is home most saturday nights watching the tv, aka the > > genius ... > > > > Ok your modem / dev problem is simple. Unix/Linux treats every > > hardware device that makes up the system as a file; it sees all > > harware as merly files. Iinux interacts with hardware through these > > files. It must be noted that they are special files that can be > > created only by the OS when said devices are installed. BUT > > /dev/modem is really not a device file. It is a sybolic link (in > > windoze talk= a short cut) to a real device file. So we can make a > > sym link called /dev/modem and point it to your modems com port. > > > > All we have to do is the following to get your modem working: > >1. Determine if your modem is recognized > >2. Determine its com port settings > >3. Make a sym from /dev/modem to your com port. > >Dont worry its not as hard as it sounds! > > > > What to do. > >1. At a terminal or console promt > >A type su (to login as root {admin}) > > type <your root password here> > > type lspci -v (to list all pci devices & sys > > devices) You should now see a bunch of devices and atributes for > > each listed. scroll down or up until you find one titled a "serial > > controller" or "serial device." It will probably be followed by the > > name of your modems manufactuer. A few line below that you will > > find an entry begining with the word flags. At the end of that > > entry you will find what IRQ your modem uses. Write it down. On > > the next line you will find what IO address your modem uses. Write > > it down exactly. > > > >2. type clear > > type cat /proc/tty/driver/serial > >You should now see a list of com port numbers and the IO address and > > IRQ's that make each up. Look for your modems port and irq in this > > list. the row that matches gives you your com port id. > >In Unix/ linux com port follow the following format. > >(winoze) ---> Linux/Unix > >com 1 = /dev/ttyS0 > >com 2 = /dev/ttyS1 > >com 3 = /dev/ttyS2 etc > >ok for get the windoze com number and remember what # you wrote down > > for you from your match. > > > >3. type ln -s
> the unix com port id # > /dev/modem > > > >Example: ln -s /dev/ttyS4 /dev/modem > >if your modem uses id 4 > >note the capital S in com port names. > > > >Thats it! your done . try wvdial now > > > >The reason for the modem sym link is that ideally when you install, > > this link is made so the apps that use your modem dont have to > > figure out your com port id. They just use /dev/modem > > > >Have fun and if you have anymore problems or this doesnt work let me > > know. Max > > > >On Monday 03 June 2002 04:22 pm, Forrest Halford wrote: > >> Hello > >> > >> When I run wvdial I get the message > >> cannot open /dev/modem; no such file or directory... > >> > >> However there is a directory called modems..... > >> > >> WIll someone tell me what thier suse 8.0 > >> > >> /dev > >> directory looks like so that I may try to copy it.... > >> > >> I have a modem but cannot configure it in yast2 and wvdial spits > >> up this error... > >> > >> I treid to create a file named modem but it gave me a wrong otcl > >> type error.... > >> > >> Help > >> Forrest > > > >-- > >Remember: > >Always think positively. > >You will prevail. -- Remember: Always think positively. You will prevail.
-- Remember: Always think positively. You will prevail.
-- 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 archives at http://lists.suse.com