LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices

Reply
 
Search this Thread
Old 12-29-2006, 04:40 PM   #1
madwac
Member
 
Registered: Jul 2006
Distribution: kernal 2.6.20-1 2948.fc6 LC2210D
Posts: 48

Rep: Reputation: 15
wvdial in LC2210D


I've been at this for month's and can't get help. The folks at linux certified started on this and then blew me off. I figured if I bought a certified linux machine I would be able to get help but mention Wvdial and everybody runs. Anyway they told me to create a myWvdial.conf file and edit it. the file was in root so I cp'd it to joe's user acount and it has full permissions. the file is still oewned by root@local host. Here is my last try....what's going on..anybody?
[joe@localhost ~]$ wvdial --config myWvdial.conf
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy
[joe@localhost ~]$ wvdial --config ./myWvdial.conf
--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy
[joe@localhost ~]$ wvdialconf tmp.wv
Scanning your serial ports for a modem
ttyS0<Info>: Device or resource busy
Port Scan<*1>: S0
ttyS1<Info>: Device or resource busy
Port Scan<*1>: S1
ttyS2<Info>: Device or resource busy
Port Scan<*1>: S2
ttyS3<Info>: Device or resource busy
Port Scan<*1>: S3
ttyS4<Info>: Device or resource busy
Port Scan<*1>: S4
ttyS5<Info>: Device or resource busy
Port Scan<*1>: S5
ttyS6<Info>: Device or resource busy
Port Scan<*1>: S6
ttyS7<Info>: Device or resource busy
Port Scan<*1>: S7
ttyS8<Info>: Device or resource busy
Port Scan<*1>: S8
ttyS9<Info>: Device or resource busy
Port Scan<*1>: S9
ttyS10<Info>: Device or resource busy
Port Scan<*1>: S10
ttyS11<Info>: Device or resource busy
Port Scan<*1>: S11
ttyS12<Info>: Device or resource busy
Port Scan<*1>: S12
ttyS13<Info>: Device or resource busy
Port Scan<*1>: S13
ttyS14<Info>: Device or resource busy
Port Scan<*1>: S14
ttyS15<Info>: Device or resource busy
Port Scan<*1>: S15
ttyS16<Info>: Device or resource busy
ttyS0<Info>: Device or resource busy
Port Scan<*1>: S0
ttyS1<Info>: Device or resource busy
Port Scan<*1>: S1
ttyS2<Info>: Device or resource busy
Port Scan<*1>: S2
ttyS3<Info>: Device or resource busy
Port Scan<*1>: S3
ttyS4<Info>: Device or resource busy
Port Scan<*1>: S4
ttyS5<Info>: Device or resource busy
Port Scan<*1>: S5
ttyS6<Info>: Device or resource busy
Port Scan<*1>: S6
ttyS7<Info>: Device or resource busy
Port Scan<*1>: S7
ttyS8<Info>: Device or resource busy
Port Scan<*1>: S8
ttyS9<Info>: Device or resource busy
Port Scan<*1>: S9
ttyS10<Info>: Device or resource busy
Port Scan<*1>: S10
ttyS11<Info>: Device or resource busy
Port Scan<*1>: S11
ttyS12<Info>: Device or resource busy
Port Scan<*1>: S12
ttyS13<Info>: Device or resource busy
Port Scan<*1>: S13
ttyS14<Info>: Device or resource busy
Port Scan<*1>: S14
ttyS15<Info>: Device or resource busy
Port Scan<*1>: S15
ttyS16<Info>: Device or resource busy
Port Scan<*1>: S62
ttyS63<Info>: Device or resource busy
Port Scan<*1>: S63
ttyS64<Info>: Device or resource busy
Port Scan<*1>: S64
ttyS65<Info>: Device or resource busy
Port Scan<*1>: S65
ttyS66<Info>: Device or resource busy
Port Scan<*1>: S66
ttyS67<Info>: Device or resource busy
Port Scan<*1>: S67
ttyS68<Info>: Device or resource busy
Port Scan<*1>: S68
ttyS69<Info>: Device or resource busy
Port Scan<*1>: S69
ttyS70<Info>: Device or resource busy
Port Scan<*1>: S70
ttyS71<Info>: Device or resource busy
Port Scan<*1>: S71
ttyS72<Info>: Device or resource busy
Port Scan<*1>: S72
ttyS73<Info>: Device or resource busy
Port Scan<*1>: S73
ttyS74<Info>: Device or resource busy
Port Scan<*1>: S74
ttyS75<Info>: Device or resource busy
Port Scan<*1>: S75
ttySL0<Info>: Device or resource busy
Port Scan<*1>: SL0


Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wvdial/

If you still have problems, send mail to wvdial-list@lists.nit.ca.
 
Old 12-29-2006, 04:57 PM   #2
dombrowsky
Member
 
Registered: Dec 2005
Location: New York
Distribution: Debian/GNU
Posts: 235

Rep: Reputation: 31
when you see a message "Device or resource busy" in linux, it is almost always a lie.

What it really means is the driver for the device is broken and has no idea what its doing. What's your device? A modem connected to the serial port? Are you sure the port works correctly?
 
Old 12-30-2006, 06:15 PM   #3
madwac
Member
 
Registered: Jul 2006
Distribution: kernal 2.6.20-1 2948.fc6 LC2210D
Posts: 48

Original Poster
Rep: Reputation: 15
Thankyou sooooo much for your help!
The device is a linmodem. Below is all that's mentioned in the paper work they sent me.
iii. Using the Linmodem

The modems on all models are known as softmodems or linmodems. These modems use the computers
resources, such as cpu, ram, and sound hardware, instead of dedicated hardware like traditional modems.
Linmodems require a software daemon to be running.
For the modem to work, an alsa sound driver will need to be loaded. Systems with Intel ICH
audio cards should use the snd-intel18x0m driver. (I believe this is what i HAVE). Systems with supported
Intel HDAudio chipsets need only load the sound card driver, snd-hda-intel. Systems with Via sound cards
will use the snd-via82xx-modem driver.
A user-space daemon, slmodemd, will create the modem device used by dialing applications.
The default modem device is /dev/ttySLO, which is usually linked to /dev/modem. The daemon will need to
to start up configured with the correct country code and the alsa flag. A startup script, /etc/init.d/
slmodemd, is provided.
Once the device is set up, you can use wvdial to dial out. To use wvdial, first run
"wvdialconf/etc/wvdial.conf". Edit /etc/wvdial.conf with your providers number, username and password,
then run "wvdial-f/etc/wvdial.conf".
When they started helping me they had me type # ls -al /dev/ttySLO but it didn't work so I typed ls -l /dev/ttyS* which printed....
Lrwxrwxrwx 1 root root 10 2006-07-10 09:17 /dev/ttySLO ->/dev/pts/1
He then wrote that he got the modem working on his test system by typing
# chmod 777 /dev/pts/1n ( I can't remember if I did this or not)
He then wrote saying " It may be different on your system for where /dev/ttySLO
is linked to, on my system it's linked to /dev/pts/o so please change the
permission on the correct device for your system. Try typing "wvdialconf tmp.wv"
as a normal user and let us know your results." this didn't work.
I'm pretty sure I have a modem on /dev/ttySLO which is com 1.
He had written me at first to type wvdialconf tmp.wv.....
This he said would write details about the modem to the temp file tmp.wv-"You
should see a line with 'found a modem on /dev/ttySLO' "Please edit the temp with your isp settings etc." (I did this)
He said "You may need to comment 'Modem Type= Analog Modem' by using a semicolon,'
I didn't understand this.
Once edited , save the file and tyoe the following...
wvdial --conftmp.wv
this did nothing.
I should probably delete everthing and start over but my gut tells me I'm almost there and its just some stupid little thing.
The guy who was helping me ...his superior said to remove the files and start over so I did.
Now he said "to create a config file you should use wvdialconf like this...
"Wvdialconf myWvdial.conf. Now edit this file and then try to dial out using
..."wvdial --config myWvdial.conf" or "wvdial --config=/full/path/to/myWvdial.conf"
You can imagine for a newbie this was getting old when that didn't work.
So one guy online suggested copying the file out of root to a user account (which I wanted to do anyway because I figured I don't want to dial out as root so I thats where it stands.
What kills me is I have 6 books on linux/fedora and no mention of anythng he's
talking about. Since I'm trying to learn though I am determined to do this through
the console. then when I'm done i will write a paper on it for the blog.

Last edited by madwac; 12-30-2006 at 06:19 PM.
 
  


Reply

Tags
device, dialup, error, kernel, linux, wvdial


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
WvDial Streams Linux - Software 6 12-30-2006 06:25 PM
wvdial cammet Linux - General 1 07-31-2005 06:09 PM
need help with wvdial weng Linux - Networking 2 01-22-2004 04:41 AM
wvdial help Johnsernickle Linux - Networking 1 10-07-2002 05:25 AM
wvdial pir2 Linux - Networking 2 06-20-2002 08:41 PM


All times are GMT -5. The time now is 04:43 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration