Dell 1535 + Ubuntu + Modem = disaster
 

Trying to activate a USB modem on my computer (see steps below) disables sound in all applications and all wireless communication and it appears may be responsible for disabling portions of other applications.

Unfortunately I must have the modem capability where I do most of my computer work and the computer has no built in modem.

Support from Dell "Linux Support" has been less than useless. I am not all that advanced in Linux as yet so it does not take much jargon to confuse me.

#######################

Documentation for a similar but different modem/sound/wireless "Dell problem" is found at:

http://linux.dell.com/wiki/index.php..._Does_Not_Work
http://linux.dell.com/wiki/index.php...Kernel_Upgrade

& known issues list at bottom of:
http://linux.dell.com/wiki/index.php/Ubuntu_8.04

########################

System Specifications:

Computer:........ Dell Studio 1535 laptop
Modem ........... USRobotics usr5837
OS............... Ubuntu 8.04 (hardy heron)
-- Kernel ....... 2.6.24-16 generic
-- Gnome ........ 2.22.1
Processor 0: .... Intel Core 2 Duo CPU T5750 @ 2.00GHz
Processor 1: .... Intel Core 2 Duo CPU T5750 @ 2.00GHz

##########################

USRobotics Modem Information

The modem which is touted as Plug and Play does not work until steps 1-4 of the troubleshooting routine provided by USRobotics are executed.
Then the modem works but the Sound, wireless etc. won't work.

--------- USRobotics Trouble shoot instructions --------

Open a terminal shell and log in as root.

1. Verify modem enumeration with the following command:

lsusb

Below is an example output.

Bus 001 Device 002: ID 0baf:0303 U.S. Robotics

2. Verify the CDC ACM module as loaded with the following command:

lsmod

If the version of Linux kernel has the CDC ACM driver compiled into it, you
should now be able to use a terminal emulator program (for example: minicom)
to attach to the modem.

If the kernel has the CDC ACM driver built as a module, then you may have to
enable the driver with the following command:

modprobe acm
(used in 2.4.x kernels)

modprobe cdc_acm
(used in 2.6.x kernels)

3. Verify device node creation.

Some distributions will automatically create a device node
for the modem in /dev. Below is the device node as created in Fedora 7.

crw-rw---- 1 root uucp 166, 0 2007-09-12 10:33 ttyACM0

The CDC ACM driver allows up to 32 modems. If the device node does not exist,
create one using the following command:

mknod /dev/ttyACM0 c 166 0

Additional device nodes can be created for additional modems as follows:

mknod /dev/ttyACM1 c 166 1
mknod /dev/ttyACM2 c 166 2
mknod /dev/ttyACM3 c 166 3

4. Access the modem.

Use a terminal emulator program (for example: minicom) to access the modem using
the device node created above. For example, setup the serial port for minicom to
use the device node /dev/ttyACM0.

5. Internet dialers.

Applications such as WvDial and KPPP may require access to the modem via the
/dev/modem device node.

You can set up a symbolic link from /dev/modem to the ACM modem device by using
the following command:

ln -s /dev/ttyACM0 /dev/modem

Try this:

Have your computer where sound, etc is working. Then go to a terminal (just like you did to run those commands you posted) and type (or paste) the following:

(replace "somefilename" with a convenient file name that you are not already using.)

Then plug in your USB modem. Give it a moment, and when the messages (if any) stop scrolling, press control-C (Ctl key + C). Then post the contents of somefilename. If no messages happened when you plugged in the modem, don't bother posting the results -- just let me know there were no messages.

Try the same thing again (makeing sure sound, etc are working first), but after typing the above command, do what you normally do before you plug in the modem. Then plug in the modem You should definately get output this time. Please post it.


The following two URLs lead to 404 errors. I am reasonably sure those dots in them represent some missing information.



Also, please post which version (8.04, etc) of Ubuntu you are using. If you don't know what it is, you can probably find out by typing (in a terminal)

I had the same problem. See my thread on the matter to see the solution.

With the hardware connected and switched on go into the device manager and you should see the modem is present and it has a device name, something like SL01. Write down this name exactly. Now go to the networking control panel where you will see a list of possible modems. These are just default names. Edit the top name to show the actual device name as reported by the device manager. For me this was all it took to get both the onboard modem and an external serial modem, connected through a serial to USB converter, to work.

Andrew375,
I agree that it sounds like our problems are at least similar. However, when I try to execute the fix you describe, I find that my my understanding of common linux terms fails me.

When I try to go to the above underlined components in the Ubuntu 8.04 (Hardy Heron) menu structure, I find no entries that are a match for the terms that you used. Whatever the device manager or Networking Control Panel are, they are either identified by some other terms or are farther down in the menu structure where I have not found them.

Could you please advise me as to the menu locations
(e.g. System/Administration/Network Settings/...)
or command line entries, that you are referring to.

I feel your pain!
 

I went back to my lap top last night retraced the steps I took. I am on Ubuntu 8.01 with the standard Gnome desk top. All these steps are with the graphical interface, I did not resort to using the command line.

Click on the network icon, top right on my setup, it looks like a desktop computer. In the drop down menu select Manual configuration -> point to point connection.

In the PPO properties (general tab) select "serial modem". Click on the "modem" tab and in the "port" box change the device name to that which the device manager reports. In my case this is "/dev/ttySL0", this drives the internal software modem. The "SL" part of the name reflects the fact that the modem is accessed through the SmartLink driver, which comes under "restricted packages" in the software installation menu. The "0" is the number zero btw.

With a generic external 56k modem connected to the USB port, though a USB to Serial converter, I did not need to install any drivers. I believe the device name was "/dev/ttyS0" That is (S)erial (0)zero.

Re-reading your original post I suggest you use the name "/dev/ttyACM0", note the 0 is the number zero.

Finish by entering the required telephone numbers, user name and password then "OK" and close the box.

It appears the sticky part is getting that device name. I've noticed that after updating my system to 8.01 the Device manager has disappeared. Just in case it was under System -> Administration -> Device manager. In anycase it looks like the device name was reported the diagnostics you ran. Like me you couldn't see the significant information for all the rest of the stuff.

Hope this helps.

Thank you thank you thank you !!!
 

Andrew:

The following from your last suggestion turned out to be the entire key.
I simply needed to properly identify the modem. I use Gnome PPP dialer becuase it is more intuitive to set up. USRobotics (USR) said that the modem should be plug and Play for Linux, maybe so sometimes but my computer and distribution needed some manual setup, and unfortunately USR did not explain what was needed in any intelligible manner. Your pointing out the correct device name by analyzing USR's instructions was all that it took. Everything works fine now. Better modem dial-up speed than I have consistantly gotten before, so I guess USR made a pretty good modem inspite of their arcane instructions.

I appreciate your persistence in helping me get this sorted out. It only took me 6 months to get this computer working right (pretty much).

Now on to fixing the spell checker in the Version of FireFox that Dell set it up with. about 1/2 the words in what I am typing now are marked as misspelled and all the suggested corrections are in German (at least I think it is German). I would ask Dell, but their support has proved worthless or such a misdirection and confusion as to be worse than worthless.

Again, Andrew, Thank you, Thank you, Thank you.

dgoddard

I am so pleased about this. When I managed to figure out the solution I've never been so pleased with myself as it was the first time I had actually solved a Linux problem totally by myself and was actually able to post a complete solution to a problem that apparently no else had encounted.

But now to know my contribution has actually helped someone else is brillient!! I am really, REALLY pleased.:):)

Many thanks for getting back to let me know the outcome.

Andrew

Met this one before ;)
R-click in a ffox text box (like this quick reply box I am currently typing in)
Languages
Set it to whatever you like (Eg. en_GB)