Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR 4: uart:unknown port:1A0 irq:9 5: uart:unknown port:1A8 irq:9 6: uart:unknown port:1B0 irq:9 7: uart:unknown port:1B8 irq:9 8: uart:unknown port:2A0 irq:5 9: uart:unknown port:2A8 irq:5 10: uart:unknown port:2B0 irq:5 11: uart:unknown port:2B8 irq:5 12: uart:unknown port:330 irq:4 13: uart:unknown port:338 irq:4 14: uart:unknown port:0 irq:0 15: uart:unknown port:0 irq:0 16: uart:unknown port:100 irq:12 17: uart:unknown port:108 irq:12 18: uart:unknown port:110 irq:12 19: uart:unknown port:118 irq:12 20: uart:unknown port:120 irq:12 21: uart:unknown port:128 irq:12 22: uart:unknown port:130 irq:12 23: uart:unknown port:138 irq:12 24: uart:unknown port:140 irq:12 25: uart:unknown port:148 irq:12 26: uart:unknown port:150 irq:12 27: uart:unknown port:158 irq:12 28: uart:unknown port:160 irq:12 29: uart:unknown port:168 irq:12 30: uart:unknown port:170 irq:12 31: uart:unknown port:178 irq:12 32: uart:unknown port:302 irq:3 33: uart:unknown port:302 irq:3 34: uart:unknown port:302 irq:3 35: uart:unknown port:302 irq:3 36: uart:unknown port:302 irq:3 37: uart:unknown port:302 irq:3 38: uart:unknown port:302 irq:3 39: uart:unknown port:302 irq:3 40: uart:unknown port:302 irq:3 41: uart:unknown port:302 irq:3 42: uart:unknown port:302 irq:3 43: uart:unknown port:302 irq:3 44: uart:unknown port:0 irq:0 45: uart:unknown port:0 irq:0 46: uart:unknown port:0 irq:0 47: uart:unknown port:0 irq:0 48: uart:unknown port:0 irq:0 49: uart:unknown port:0 irq:0 50: uart:unknown port:0 irq:0 51: uart:unknown port:0 irq:0 52: uart:unknown port:0 irq:0 53: uart:unknown port:0 irq:0 54: uart:unknown port:0 irq:0 55: uart:unknown port:0 irq:0 56: uart:unknown port:0 irq:0 57: uart:unknown port:0 irq:0 58: uart:unknown port:0 irq:0 59: uart:unknown port:0 irq:0 60: uart:unknown port:0 irq:0 61: uart:unknown port:0 irq:0 62: uart:unknown port:0 irq:0 63: uart:unknown port:0 irq:0 linux:/home/galt # On Tue, 4 Jun 2002 10:23:58 -0700, a large badger frolicked about on your keyboard, and out came:
Yes com 4 is ttyS3
compare the data US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8 4-1 match the IRQ 3 and IO address to the results of the command cat /proc/tty/driver/serial do you find a match listed? write down all the linux com ID # that match the irq 3. ok now as root type ln -s /dev/ttyS<id here> /dev/modem
note there is a space between /dev/ttySx and /dev/modem remember to fire up wvdial after each attempt to test modem
(also you might want to check Kde control center information interupts and find that device on irq 3 is "serial" if so it is your modem)
the format is /dev/ttyS<#> and a space then /dev/modem the format is (must be root) setserial <space> /dev/ttyS<#> always do what insides <> but omit ,<> and its contents thats whats up lets cut to the chase please email me the results of cat /proc/tty/driver/serial and I will tell you what /dev/ttySx to use and then your modem will work. max
On Tuesday 04 June 2002 09:50 am, 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
> > is 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.
On Tuesday 04 June 2002 21:23, Forrest Halford wrote:
Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest
linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR ===========================(Big Snip, old info)
Forrest, From your info here, it would seem you have a com1 (3F8 irq4) and a com2 (2E8 irq:3). Usually the second port is 2F8 and I think that is settable in your bios. Anyway, your modem is on com1 it seems, showing the baud:19200 readings. That should be 115200 if it is a 56k modem, but you can change that in your settings with Yast2. If I were you, I would delete any modems setup on your Linux side, using Yast2, then go over to Winders and remove your modem from it's settings also. I would then go back to Linux and try setting up the modem, with Yast2, again to see if things look any better. Unless you are having some type of IRQ conflict, setting up an external modem should not be so difficult, especially in Linux! Patrick -- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
Sorry for the delay in my response. The summer at my college just started. OK DO NOT listen to these other guys that are giving you advice as it seems that they have not read the complete thread of the conversation, are addressing only individual posts and not the overall problem and its full details, and are therefore complicating matters and my job in helping you. Patrick is WRONG. The modem that we want to configure is NOT assigned as com 1 ! From the results of linux:/home/galt # cat /proc/tty/driver/serial we see that you in fact have two serial modems/nics/devices as part of your system (you obviously have an extra internal serial device) . The MODEM WE ARE CONCERNED WITH is the external one plugged in your serial port. OK you sent me this info about your modem: my info is such:
US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8
If you compare that to the output of cat /proc/tty/driver/serial you find that your modem is configured for /dev/ttyS3 It matches exactly. OK type the following exactly, remember you must type this exactly, case is vital and don't forget spaces where they are indicated. this means space <space>........ space, but do not type these characters. alternately you can cut and paste each example that follows (but not the ones with <space>). as root: ln<space>-s<space>/dev/ttyS3<space>/dev/modem or better yet cut and paste the following as root: ln -s /dev/ttyS3 /dev/modem now fire up wvdial as a regular user: ie su <regular user name here> wvdial If there are any error messages generated by any of the above commands or if this doesn't work, cut and past all error messages in an email to me. OK hope this works. if not we will fix it. Max On Tuesday 04 June 2002 06:23 pm, Forrest Halford wrote:
Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest
linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR 4: uart:unknown port:1A0 irq:9 5: uart:unknown port:1A8 irq:9 6: uart:unknown port:1B0 irq:9 7: uart:unknown port:1B8 irq:9 8: uart:unknown port:2A0 irq:5 9: uart:unknown port:2A8 irq:5 10: uart:unknown port:2B0 irq:5 11: uart:unknown port:2B8 irq:5 12: uart:unknown port:330 irq:4 13: uart:unknown port:338 irq:4 14: uart:unknown port:0 irq:0 15: uart:unknown port:0 irq:0 16: uart:unknown port:100 irq:12 17: uart:unknown port:108 irq:12 18: uart:unknown port:110 irq:12 19: uart:unknown port:118 irq:12 20: uart:unknown port:120 irq:12 21: uart:unknown port:128 irq:12 22: uart:unknown port:130 irq:12 23: uart:unknown port:138 irq:12 24: uart:unknown port:140 irq:12 25: uart:unknown port:148 irq:12 26: uart:unknown port:150 irq:12 27: uart:unknown port:158 irq:12 28: uart:unknown port:160 irq:12 29: uart:unknown port:168 irq:12 30: uart:unknown port:170 irq:12 31: uart:unknown port:178 irq:12 32: uart:unknown port:302 irq:3 33: uart:unknown port:302 irq:3 34: uart:unknown port:302 irq:3 35: uart:unknown port:302 irq:3 36: uart:unknown port:302 irq:3 37: uart:unknown port:302 irq:3 38: uart:unknown port:302 irq:3 39: uart:unknown port:302 irq:3 40: uart:unknown port:302 irq:3 41: uart:unknown port:302 irq:3 42: uart:unknown port:302 irq:3 43: uart:unknown port:302 irq:3 44: uart:unknown port:0 irq:0 45: uart:unknown port:0 irq:0 46: uart:unknown port:0 irq:0 47: uart:unknown port:0 irq:0 48: uart:unknown port:0 irq:0 49: uart:unknown port:0 irq:0 50: uart:unknown port:0 irq:0 51: uart:unknown port:0 irq:0 52: uart:unknown port:0 irq:0 53: uart:unknown port:0 irq:0 54: uart:unknown port:0 irq:0 55: uart:unknown port:0 irq:0 56: uart:unknown port:0 irq:0 57: uart:unknown port:0 irq:0 58: uart:unknown port:0 irq:0 59: uart:unknown port:0 irq:0 60: uart:unknown port:0 irq:0 61: uart:unknown port:0 irq:0 62: uart:unknown port:0 irq:0 63: uart:unknown port:0 irq:0 linux:/home/galt #
On Tue, 4 Jun 2002 10:23:58 -0700, a large badger frolicked about on your keyboard, and out came:
Yes com 4 is ttyS3
compare the data US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8 4-1 match the IRQ 3 and IO address to the results of the command cat /proc/tty/driver/serial do you find a match listed? write down all the linux com ID # that match the irq 3. ok now as root type ln -s /dev/ttyS<id here> /dev/modem
note there is a space between /dev/ttySx and /dev/modem remember to fire up wvdial after each attempt to test modem
(also you might want to check Kde control center information interupts and find that device on irq 3 is "serial" if so it is your modem)
the format is /dev/ttyS<#> and a space then /dev/modem the format is (must be root) setserial <space> /dev/ttyS<#> always do what insides <> but omit ,<> and its contents thats whats up lets cut to the chase please email me the results of cat /proc/tty/driver/serial and I will tell you what /dev/ttySx to use and then your modem will work. max
On Tuesday 04 June 2002 09:50 am, 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
>> > x is 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.
-- Remember: Always think positively. You will prevail.
Max Webb, You are so full of it, it smells all the way over here! :o) Check your port numbers again and then check your own external modem, if you have one! From his Linux readout, his modem seems to be showing up on Com1 and the second port is misconfigured in his bios as it should be 2F8 instead of 2E8! Have you seen his machine yourself? Do you know how many serial ports he has showing up on the back of his computer? I doubt it and if you further check the port number addresses I think you will find differences there as well. Also, Linux checks for the devices attached to those ports it finds and tries to get the max readout from it. Since he has a 56k modem, it stands to reason that the higher reading will show up there, because 9600 baud is the standard nothing hooked up port speed reading. Did you take a look? My guess is you haven't been keeping up with the thread as he has tried the /dev/ttyS3 already without success! What turnip truck did you just get off of today? I hope you don't continue to confuse the gentleman much more with your superior intellect or he will give up trying to fix it! Patrick ---------------------------- On Wednesday 05 June 2002 12:52, Max Webb wrote:
Sorry for the delay in my response. The summer at my college just started. OK DO NOT listen to these other guys that are giving you advice as it seems that they have not read the complete thread of the conversation, are addressing only individual posts and not the overall problem and its full details, and are therefore complicating matters and my job in helping you. Patrick is WRONG. The modem that we want to configure is NOT assigned as com 1 ! From the results of linux:/home/galt # cat /proc/tty/driver/serial we see that you in fact have two serial modems/nics/devices as part of your system (you obviously have an extra internal serial device) . The MODEM WE ARE CONCERNED WITH is the external one plugged in your serial port. OK you sent me this info about your modem:
my info is such:
US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8
If you compare that to the output of cat /proc/tty/driver/serial you find that your modem is configured for /dev/ttyS3 It matches exactly.
OK type the following exactly, remember you must type this exactly, case is vital and don't forget spaces where they are indicated. this means space <space>........ space, but do not type these characters. alternately you can cut and paste each example that follows (but not the ones with <space>). as root: ln<space>-s<space>/dev/ttyS3<space>/dev/modem
or better yet cut and paste the following as root:
ln -s /dev/ttyS3 /dev/modem
now fire up wvdial as a regular user: ie su <regular user name here> wvdial
If there are any error messages generated by any of the above commands or if this doesn't work, cut and past all error messages in an email to me. OK hope this works. if not we will fix it. Max
On Tuesday 04 June 2002 06:23 pm, Forrest Halford wrote:
Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest
linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR ============================
-- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
Patrick Max was right It was ttyS3 because my modem was on com 4 in windows,....which is the same interrupt as com 2. irq 3 Max It works, I can dial in now,.....On Thu, 6 Jun 2002 00:05:24 -0400, a large badger frolicked about on your keyboard, and out came:
Max Webb,
You are so full of it, it smells all the way over here! :o)
Check your port numbers again and then check your own external modem, if you have one! From his Linux readout, his modem seems to be showing up on Com1
No, com 4 is the same irq as 4 in windows, and that is where it is...4-1 is 3 ...ttyS3 is what worked.....
and the second port is misconfigured in his bios as it should be 2F8 instead of 2E8! No from windows, I see 2E8 on the bios for that port and IRQ..... Hard to argue with success.
Have you seen his machine yourself? Do you know how many serial ports he has showing up on the back of his computer? I doubt it and if you further check the port number addresses I think you will find differences there as well. Also, Linux checks for the devices attached to those ports it finds and tries to get the max readout from it. Since he has a 56k modem, it stands to reason that the higher reading will show up there, because 9600 baud is the standard nothing hooked up port speed reading. Did you take a look?
My guess is you haven't been keeping up with the thread as he has tried the /dev/ttyS3 already without success!
Wrong. I messed up the spaces on the basic commands. I failed there, and now I see, thanks to Max and others help, how important the spaces are.
What turnip truck did you just get off of today? I hope you don't continue to confuse the gentleman much more with your superior intellect or he will give up trying to fix it! He (Max) got off the turnip truck that has the fixed modems in suse 8, like mine. 8-) Now, if I can get my university to let me connect to them, instead of the "No Carrier" stuff that I have been getting.
Patrick ---------------------------- On Wednesday 05 June 2002 12:52, Max Webb wrote:
Sorry for the delay in my response. The summer at my college just started. OK DO NOT listen to these other guys that are giving you advice as it seems that they have not read the complete thread of the conversation, are addressing only individual posts and not the overall problem and its full details, and are therefore complicating matters and my job in helping you. Patrick is WRONG. The modem that we want to configure is NOT assigned as com 1 ! From the results of linux:/home/galt # cat /proc/tty/driver/serial we see that you in fact have two serial modems/nics/devices as part of your system (you obviously have an extra internal serial device) . The MODEM WE ARE CONCERNED WITH is the external one plugged in your serial port. OK you sent me this info about your modem:
my info is such:
US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8
If you compare that to the output of cat /proc/tty/driver/serial you find that your modem is configured for /dev/ttyS3 It matches exactly.
OK type the following exactly, remember you must type this exactly, case is vital and don't forget spaces where they are indicated. this means space <space>........ space, but do not type these characters. alternately you can cut and paste each example that follows (but not the ones with <space>). as root: ln<space>-s<space>/dev/ttyS3<space>/dev/modem
or better yet cut and paste the following as root:
ln -s /dev/ttyS3 /dev/modem
now fire up wvdial as a regular user: ie su <regular user name here> wvdial
If there are any error messages generated by any of the above commands or if this doesn't work, cut and past all error messages in an email to me. OK hope this works. if not we will fix it. Max
On Tuesday 04 June 2002 06:23 pm, Forrest Halford wrote:
Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest
linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR ============================
-- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
On Thursday 06 June 2002 01:16, Forrest Halford was heard muttering:
Patrick
Max was right
It was ttyS3 because my modem was on com 4 in windows,....which is the same interrupt as com 2. irq 3 ========================
Forest, Glad to hear you got it working, however you got it working. Not so sure about all the right and wrong of it, but that doesn't matter as long as you are getting online with everything now. Good luck on the university hookup and happy Linuxing! Patrick -- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
yeah, I am getting a weird "no carrier" error message when they try to shake hands and log on....... I was this after they changed the modem pool at the school and the way they said to fix it in windows was to put S 32 = 98 under advanced connection settings, "extra settings" Then it worked.... but, I do not know how to do that in LINUX!! I will call ITS at school tomorrow and see what they say... How many want odds on they say "We do not support linux!" ...SLAM!! the phone.....!?? *SIGH* help? (he asks timidly) Forrest On Thu, 6 Jun 2002 02:16:05 -0400, a large badger frolicked about on your keyboard, and out came:
On Thursday 06 June 2002 01:16, Forrest Halford was heard muttering:
Patrick
Max was right
It was ttyS3 because my modem was on com 4 in windows,....which is the same interrupt as com 2. irq 3 ========================
Forest, Glad to hear you got it working, however you got it working. Not so sure about all the right and wrong of it, but that doesn't matter as long as you are getting online with everything now. Good luck on the university hookup and happy Linuxing!
Patrick -- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
Patrick, thanks for all of your "A+ wisdom." Have an A+ day! On Wednesday 05 June 2002 11:16 pm, Patrick wrote:
On Thursday 06 June 2002 01:16, Forrest Halford was heard muttering:
Patrick
Max was right
It was ttyS3 because my modem was on com 4 in windows,....which is the same interrupt as com 2. irq 3
========================
Forest, Glad to hear you got it working, however you got it working. Not so sure about all the right and wrong of it, but that doesn't matter as long as you are getting online with everything now. Good luck on the university hookup and happy Linuxing!
Patrick
-- Remember: Always think positively. You will prevail.
Patrick, perhaps you should seek professional mental health services. I am sorry I was not able to address this attack on my person until just now as I have been busy. Patrick there are an number of good Windoze for dummies books out there for your kind. Forget about Unix and perhaps maybe with great effort you may be able to learn to use a newbie OS like windoze ... then again, maybe not. Have and A+ day! On Wednesday 05 June 2002 09:05 pm, Patrick wrote:
Max Webb,
You are so full of it, it smells all the way over here! :o)
Check your port numbers again and then check your own external modem, if you have one! From his Linux readout, his modem seems to be showing up on Com1 and the second port is misconfigured in his bios as it should be 2F8 instead of 2E8! Have you seen his machine yourself? Do you know how many serial ports he has showing up on the back of his computer? I doubt it and if you further check the port number addresses I think you will find differences there as well. Also, Linux checks for the devices attached to those ports it finds and tries to get the max readout from it. Since he has a 56k modem, it stands to reason that the higher reading will show up there, because 9600 baud is the standard nothing hooked up port speed reading. Did you take a look?
My guess is you haven't been keeping up with the thread as he has tried the /dev/ttyS3 already without success! What turnip truck did you just get off of today? I hope you don't continue to confuse the gentleman much more with your superior intellect or he will give up trying to fix it!
Patrick ----------------------------
On Wednesday 05 June 2002 12:52, Max Webb wrote:
Sorry for the delay in my response. The summer at my college just started. OK DO NOT listen to these other guys that are giving you advice as it seems that they have not read the complete thread of the conversation, are addressing only individual posts and not the overall problem and its full details, and are therefore complicating matters and my job in helping you. Patrick is WRONG. The modem that we want to configure is NOT assigned as com 1 ! From the results of linux:/home/galt # cat /proc/tty/driver/serial we see that you in fact have two serial modems/nics/devices as part of your system (you obviously have an extra internal serial device) . The MODEM WE ARE CONCERNED WITH is the external one plugged in your serial port. OK you sent me this info about your modem:
my info is such:
US RObotic external Fax modem on Windows Com4, IRQ 3 at address 2E8
If you compare that to the output of cat /proc/tty/driver/serial you find that your modem is configured for /dev/ttyS3 It matches exactly.
OK type the following exactly, remember you must type this exactly, case is vital and don't forget spaces where they are indicated. this means space <space>........ space, but do not type these characters. alternately you can cut and paste each example that follows (but not the ones with <space>). as root: ln<space>-s<space>/dev/ttyS3<space>/dev/modem
or better yet cut and paste the following as root:
ln -s /dev/ttyS3 /dev/modem
now fire up wvdial as a regular user: ie su <regular user name here> wvdial
If there are any error messages generated by any of the above commands or if this doesn't work, cut and past all error messages in an email to me. OK hope this works. if not we will fix it. Max
On Tuesday 04 June 2002 06:23 pm, Forrest Halford wrote:
Okay guys here is the output on the cat /proc/tty/driver/serial command: Again, thanks for all of the help with the linux newbie,....I will try to return the favor. regards Forrest
linux:/home/galt # cat /proc/tty/driver/serial serinfo:1.0 driver:5.05c revision:2001-07-08 0: uart:16550A port:3F8 irq:4 baud:19200 tx:8 rx:0 RTS|DTR 1: uart:unknown port:2F8 irq:3 2: uart:unknown port:3E8 irq:4 3: uart:16550A port:2E8 irq:3 baud:9600 tx:8 rx:0 CTS|DSR
============================
-- Remember: Always think positively. You will prevail.
On Friday 07 June 2002 19:20, Max Webb was heard muttering:
Patrick, perhaps you should seek professional mental health services. I am sorry I was not able to address this attack on my person until just now as I have been busy. Patrick there are an number of good Windoze for dummies books out there for your kind. Forget about Unix and perhaps maybe with great effort you may be able to learn to use a newbie OS like windoze ... then again, maybe not. Have and A+ day!
--------------------------------- Way to go Webb, I really enjoy your little barbs! I hope it wasn't too much of a strain on you to come up with all of those at once! :o) I think I might have read your books, the "dummy" ones! Maybe one day you too will be able to use Linux proficiently and can spend more time on your books than irritating those of us that already know everything! ;o) Patrick -- --- KMail v1.4.1 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
participants (3)
-
Forrest Halford -
Max Webb -
Patrick