Linux - HOWTO (With Stats)

Status
Not open for further replies.
Hey Nick,

Good one - we all work from memory some times and even mine lets me down on some bad days ;)

As for the E220 - check the first post, it's got the details on there - has been there for about 5 days now....

Enjoy !

nickw said:
You have, appropriately, called my bluff! I'm between Vodaphone connections just now, in fact, having relinquished my PCMCIA card and not yet got the Huawei E220 working. So what I was suggesting was from memory, mostly, based on what I was remembering from the PCMCIA card. I *thought* that was how I was getting it to disconnect, but don't have the card to remember completely what I was doing.

I would have thought that sending the card a reset would have, in effect, given a disconnect? But honestly, my memory on how I was disconnecting is fading - and I make no suggestion of doubting your call on this...

I've still been plugging away at trying to get the E220 working, but simply don't have the capability to do it - I'm looking forward to you getting one to work with!

SUMMARY: Don't follow my suggestions re: disconnecting.

Nick
Click to expand...
 
Huawei E220

Tazz_Tux said:
As for the E220 - check the first post, it's got the details on there - has been there for about 5 days now....
Click to expand...

Oh yes, oh yes, oh YES! It is working for me! Minor typo on your post 1 instructions: in doing the modprobe to insert the device, you have "verdor" instead of "vendor", but works fine now...

I did end up going through the process several times, watching the creation of the /dev/ttyUSB? etc. Then one last hiccup came when it would connect but wasn't able to modify /etc/ppp/pap-secrets or /etc/ppp/chap-secrets, but was connecting - that reminded me that I haven't sorted out ownerships/permissions and needed to use sudo for wvdial - but even I figured that one out.

Tazz_Tux, thank you very much - you have been exceedingly patient and professional in your contributions to this forum. Next time you're in NZ, I for sure owe you a beer!

Nick
 
Last edited:
Hey Nick,

No problems and happy surfing under Linux - hope you enjoy it ! Didn't they say it can't be done ? :rolleyes: As for the verdor/vendor - I will go with my screen ran low on ink - fixed now :D

Laterz !

nickw said:
Oh yes, oh yes, oh YES! It is working for me! Minor typo on your post 1 instructions: in doing the modprobe to insert the device, you have "verdor" instead of "vendor", but works fine now...

I did end up going through the process several times, watching the creation of the /dev/ttyUSB? etc. Then one last hiccup came when it would connect but wasn't able to modify /etc/ppp/pap-secrets or /etc/ppp/chap-secrets, but was connecting - that reminded me that I haven't sorted out ownerships/permissions and needed to use sudo for wvdial - but even I figured that one out.

Tazz_Tux, thank you very much - you have been exceedingly patient and professional in your contributions to this forum. Next time you're in NZ, I for sure owe you a beer!

Nick
Click to expand...
 
Yo tazz,

Do you know if there's a DUMeter equivalent for Gnome? Or at least any gui meter that monitors (live) connection usage, i.e. not only every 5 mins or so...

Thx, SW
 
In gnome add a network monitor - tell it to monitor ppp0 and you will see it appear on the top of your screen - might be called system monitor or something like that :)

sevenworth said:
Yo tazz,

Do you know if there's a DUMeter equivalent for Gnome? Or at least any gui meter that monitors (live) connection usage, i.e. not only every 5 mins or so...

Thx, SW
Click to expand...
 
E220 with Ubuntu

Hi,

You can get root on Ubuntu very easily: sudo passwd root , define root password and you're done.

Trying to get Huawei E220 working in Ubuntu with no luck, precisely the same as reported at taoofmac.com

Right now trying the install option as seen on the modprobe.conf manpage, will let you know.
 
Hi bilu,

Did you follow my instructions and the top of this thread ?

Laterz !

bilu said:
Hi,

You can get root on Ubuntu very easily: sudo passwd root , define root password and you're done.

Trying to get Huawei E220 working in Ubuntu with no luck, precisely the same as reported at taoofmac.com

Right now trying the install option as seen on the modprobe.conf manpage, will let you know.
Click to expand...
 
sky.akash said:
You have to enable local administrator log in to actually log in as root though ;)
Click to expand...

No, you don't. Look here. But if you mean graphical login, then yes, at least in Kubuntu you need to edit /etc/kde3/kdm/kdmrc and change to AllowRootLogin=true, probably similar in Ubuntu to change GDM settings.

Tazz_Tux said:
Hi bilu,

Did you follow my instructions and the top of this thread ?

Laterz !
Click to expand...

The instructions at the top of this thread and at the ubuntu forums are no different from those at taoofmac.com.
Remove usb-storage, add usbserial vendor=0x12d1 product=0x1003, and the nodes if they don't exist yet. But just like at taoofmac I get into a race condition, it loads /dev/ttyUSB0 only and then Mass Storage again, and I lose access to ttyUSB0, can't get any answer from it through minicom.

From what I found so far it seems the device only reports itself as mass-storage, then at Windows the auto-installed drivers do the rest. I think I partly found the answer in the modprobe.conf manpage, especially the install command which allows you to install a different driver than the one detected.

Some nice examples can be found at /etc/modprobe.d/alsa-base :

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe -Qb snd-ioctl32 ; : ; }

In our case would be something like /etc/modprobe.d/huawei_usb:

install usb-storage /sbin/modprobe --ignore-install usb-storage $CMDLINE_OPTS && { /sbin/modprobe usbserial vendor=0x12d1 product=0x1003 ; : ; }

I've tried this and it works just as good as your instructions at the top of the thread, and taoofmac's, but automatically. By just as good I mean ttyUSB0 loads first and then Mass Storage takes it over again.

At taoofmac there's also a link to a kernel patch but I want to ignore that path.
Right now I'm starting to investigate udev rules, since HAL gets data from udev.
udev renames devices based on their data as specified on rules, maybe I can get it to identify it as something else than usb-storage and then apply the modprobe workaround I mentioned before, making it work without affecting other usb-storage devices.
 
eerrr I think this must be a ubuntu only thing, since I also got the USB storage first, but then after running that command it simply gave up. Look for any "hot-plug" software that is running and maybe that causes the race. Either that or they fixed it in a later kernel :)

Maybe create the ttyUSB files first...then try the unload usb && bla

bilu said:
The instructions at the top of this thread and at the ubuntu forums are no different from those at taoofmac.com.
Remove usb-storage, add usbserial vendor=0x12d1 product=0x1003, and the nodes if they don't exist yet. But just like at taoofmac I get into a race condition, it loads /dev/ttyUSB0 only and then Mass Storage again, and I lose access to ttyUSB0, can't get any answer from it through minicom.

From what I found so far it seems the device only reports itself as mass-storage, then at Windows the auto-installed drivers do the rest. I think I partly found the answer in the modprobe.conf manpage, especially the install command which allows you to install a different driver than the one detected.

Some nice examples can be found at /etc/modprobe.d/alsa-base :

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe -Qb snd-ioctl32 ; : ; }

In our case would be something like /etc/modprobe.d/huawei_usb:

install usb-storage /sbin/modprobe --ignore-install usb-storage $CMDLINE_OPTS && { /sbin/modprobe usbserial vendor=0x12d1 product=0x1003 ; : ; }

I've tried this and it works just as good as your instructions at the top of the thread, and taoofmac's, but automatically. By just as good I mean ttyUSB0 loads first and then Mass Storage takes it over again.

At taoofmac there's also a link to a kernel patch but I want to ignore that path.
Right now I'm starting to investigate udev rules, since HAL gets data from udev.
udev renames devices based on their data as specified on rules, maybe I can get it to identify it as something else than usb-storage and then apply the modprobe workaround I mentioned before, making it work without affecting other usb-storage devices.
Click to expand...
 
Novatel U630 on Kubuntu 6.10

Hello,

I have a Novatel U630 which worked perfectly under my SuSE Linuxes.

Now I switched to Kubuntu 6.10 and the card doesn't work correctly. First I switched off the pin, so it is easier.

The card is recognized correctly, if I insert it, following messages are logged:

v 25 08:07:24 ratte kernel: [ 104.983820] pccard: PCMCIA card inserted into slot 1
Nov 25 08:07:24 ratte kernel: [ 104.984186] pcmcia: registering new device pcmcia1.0
Nov 25 08:07:24 ratte kernel: [ 105.003217] 1.0: ttyS0 at I/O 0x3f8 (irq = 177) is a 16550A
Nov 25 08:07:24 ratte kernel: [ 105.003523] pcmcia: registering new device pcmcia1.1
Nov 25 08:07:24 ratte kernel: [ 105.022304] 1.1: ttyS1 at I/O 0x2f8 (irq = 0) is a 16550A

It isn't recognized as USB device, in SuSE it was exactly the same but there it worked perfectly.

Output of ls -l /dev/ttyS*

crw-rw---- 1 root dialout 4, 64 Nov 25 08:07 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Nov 25 08:07 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 Nov 25 08:05 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 Nov 25 08:05 /dev/ttyS3

Output of ls -l /dev/ttyU*
ls: /dev/ttyU*: No such file or director
I don't have ttyUSB devices.


pccardctl info prints this out:
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1="Novatel Wireless"
PRODID_2="Merlin UMTS Modem"
PRODID_3="U630"
PRODID_4=""
MANFID=00a4,0276
FUNCID=2

pccardctl status:
Socket 0:
no card
Socket 1:
5.0V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "serial_cs"
Subdevice 1 (function 1) bound to driver "serial_cs"

If I select ttyS0 or ttyS1 in wvdial.conf following output is generated:
sudo wvdial
--> WvDial: Internet dialer version 1.56
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.

cat /etc/wvdial.conf

[Dialer Defaults]
Modem = /dev/ttyS0
Baud = 57600
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Area Code =
Phone = *99***1#
Username =internet
Password =internet
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 300
DialMessage1 =
DialMessage2 =
ISDN = 0
Auto DNS = 1

The serial devices don't work. Also with minicom there is no way to get it work. I think something is wrong with access rights, so the programs cannot talk with the devices.

Could you please help me?
 
Hey Crasherblue,

I am assuming that all of this is running as root ? If not, make sure that the user is part of the "Dialout" group (normally that is what it is called).

I would suggest trying this as root first, get it working there and then move to having a user do this. Another thing I picked up is the Baud Rate, you can pump that up a tad :)

Maybe also follow my setserial instructions at the start of this thread :)

Laterz !

crasherblue said:
Hello,

I have a Novatel U630 which worked perfectly under my SuSE Linuxes.

Now I switched to Kubuntu 6.10 and the card doesn't work correctly. First I switched off the pin, so it is easier.

The card is recognized correctly, if I insert it, following messages are logged:

v 25 08:07:24 ratte kernel: [ 104.983820] pccard: PCMCIA card inserted into slot 1
Nov 25 08:07:24 ratte kernel: [ 104.984186] pcmcia: registering new device pcmcia1.0
Nov 25 08:07:24 ratte kernel: [ 105.003217] 1.0: ttyS0 at I/O 0x3f8 (irq = 177) is a 16550A
Nov 25 08:07:24 ratte kernel: [ 105.003523] pcmcia: registering new device pcmcia1.1
Nov 25 08:07:24 ratte kernel: [ 105.022304] 1.1: ttyS1 at I/O 0x2f8 (irq = 0) is a 16550A

It isn't recognized as USB device, in SuSE it was exactly the same but there it worked perfectly.

Output of ls -l /dev/ttyS*

crw-rw---- 1 root dialout 4, 64 Nov 25 08:07 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Nov 25 08:07 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 Nov 25 08:05 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 Nov 25 08:05 /dev/ttyS3

Output of ls -l /dev/ttyU*
ls: /dev/ttyU*: No such file or director
I don't have ttyUSB devices.


pccardctl info prints this out:
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1="Novatel Wireless"
PRODID_2="Merlin UMTS Modem"
PRODID_3="U630"
PRODID_4=""
MANFID=00a4,0276
FUNCID=2

pccardctl status:
Socket 0:
no card
Socket 1:
5.0V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "serial_cs"
Subdevice 1 (function 1) bound to driver "serial_cs"

If I select ttyS0 or ttyS1 in wvdial.conf following output is generated:
sudo wvdial
--> WvDial: Internet dialer version 1.56
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.

cat /etc/wvdial.conf

[Dialer Defaults]
Modem = /dev/ttyS0
Baud = 57600
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Area Code =
Phone = *99***1#
Username =internet
Password =internet
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 300
DialMessage1 =
DialMessage2 =
ISDN = 0
Auto DNS = 1

The serial devices don't work. Also with minicom there is no way to get it work. I think something is wrong with access rights, so the programs cannot talk with the devices.

Could you please help me?
Click to expand...
 
Hello Tazz_Tux,

yes I'm trying this as root. The setserial instructions (setserial -a /dev/ttyS0 low_latency spd_warp). The baud rate isn't the problem, the device is not responding.

Do you have any idea what I could try now?

Thanks
crasherblue

Tazz_Tux said:
Hey Crasherblue,

I am assuming that all of this is running as root ? If not, make sure that the user is part of the "Dialout" group (normally that is what it is called).

I would suggest trying this as root first, get it working there and then move to having a user do this. Another thing I picked up is the Baud Rate, you can pump that up a tad :)

Maybe also follow my setserial instructions at the start of this thread :)

Laterz !
Click to expand...
 
Other than that, I am fresh out of ideas....

The reason that I asked about the baud rate is that wvdial might/will see garbage as "Not responding"

Laterz !

crasherblue said:
Hello Tazz_Tux,

yes I'm trying this as root. The setserial instructions (setserial -a /dev/ttyS0 low_latency spd_warp). The baud rate isn't the problem, the device is not responding.

Do you have any idea what I could try now?

Thanks
crasherblue
Click to expand...
 
Problem solved

Hello again,

I solved this stupid problem by deinstalling Kubuntu 6.10 AMD64 (yes I have an athlon64) and installing Kubuntu 6.10 i386 :D . Now it works with the same configuration as under AMD64, so it seems it is a architecture specific problem (like so often I experienced in the last 2 years; none of my tested linux distributions worked correctly under AMD64 :sick: )

So I can say bye bye, thank you for your help.
crasherblue
 
weird !!!

There is always gentoo....

http://www.gentoo.org

:D

crasherblue said:
Hello again,

I solved this stupid problem by deinstalling Kubuntu 6.10 AMD64 (yes I have an athlon64) and installing Kubuntu 6.10 i386 :D . Now it works with the same configuration as under AMD64, so it seems it is a architecture specific problem (like so often I experienced in the last 2 years; none of my tested linux distributions worked correctly under AMD64 :sick: )

So I can say bye bye, thank you for your help.
crasherblue
Click to expand...
 
Novatel Merlin U740 and PIN

Hey all,
I've not wanted to disable the PIN, for no other reason than I just don't :)
Of course, with the current wvdial.conf setup, dialling out with wvdial pin novatel 3gonly internet will result in the PIN getting sent, and then ppp dialling out before the Novatel card is "verified" by the PIN.

I thus wanted a manner of using wvdial to simply send the PIN without dialling out. My solution is a bit of a hack but it works. Oh, I'm running Ubuntu Edgy Eft, the greatest thing to hit the linux community since linux itself.

The idea is to remove critical stuff from the [Dialer Defaults] section and move it to the [Dialer novatel] section so that the [Dialer pin] section only has the PIN number in it and does not try to dial out.

The relevant bits of my wvdial.conf then look like this:
Code: 
[FONT="Fixedsys"][COLOR="Blue"][Dialer Defaults]
Modem = /dev/ttyUSB0[/COLOR][/FONT]
In this way, the modem link is set by default. This could be moved to the [Dialer novatel] section if you use another modem on your system.
Code: 
[FONT="Fixedsys"][COLOR="Blue"][Dialer pin]
Init1 = AT+CPIN=xxxx
Dial Attempts = 1
Auto Reconnect = off[/COLOR][/FONT]
So dialling wvdial pin will only set the PIN. It will complain that no valid phone number or username has been supplied but then who cares, we're not dialling out yet. This command will then exit once the Init1 string has been sent OK. I'm not sure if the redial configuration at the bottom is really necessary, I just don't want wvdial to hang around.
Code: 
[FONT="Fixedsys"][COLOR="Blue"][Dialer novatel]
Dial Command = ATDT
Stupid Mode = on
Phone = *99***1#
Username = username 
Password = password 
Baud = 460800
Init2 = ATZ
Init3 = ATE0V1&D2&C1S0=0+IFC=2,2
ISDN = 0
Modem Type = Analog Modem[/COLOR][/FONT]
We can now dial wvdial novatel 3gonly internet to connect. The [Dialer novatel] section contains all the connection strings and configurations needed.

Alternatively, one could execute wvdial pin & wvdial novatel 3gonly internet

---------8< snip >8--------------

As for inserting the required module, I'm a little rusty on things to do it automatically as the card is inserted into the PCMCIA slot. Any help on this would be greatly appreciated.

I can, however, show what I did to alias the Novatel card on my Ubuntu 6.10 system.

I was getting tired of typing sudo modprobe usbserial vendor=0x1410 product=0x1400 each time, especially since I can never remember what the vendor and product IDs are.

So I aliased the module in /etc/modprobe.d/ directory by creating a novatel file as such:
Code: 
# Novatel U740 Merlin
alias novatel usbserial
options novatel vendor=0x1410 product=0x1400
Then I simply need to sudo modprobe novatel instead.

This saves me milliseconds each time to type and half a minute to figure out the vendor and product IDs. A win-win situation for my short-term retention in the long run...
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X