Linux - HOWTO (With Stats)

Status
Not open for further replies.
Tazz_Tux said:
I just had the fortune of having a HUAWEI card here and it has been the easiest card to get going under Linux. I would suggest that you either go for the option - they have open source drivers - or the HUAWEI card.
Click to expand...

Thanks for the feedback.

What do you mean by 'easiest'? No additional/exotic drivers required?

Signal strength-wise, is it on a par with the Option card?
 
Spot on - you will notice that it detects the card as an option card - so you can just use the option card's wvdial entry. I have completed the new wvdial layout that I wanna try so I will keep the guys updated when I have a gap :)

Laterz !

zoot said:
Thanks for the feedback.

What do you mean by 'easiest'? No additional/exotic drivers required?

Signal strength-wise, is it on a par with the Option card?
Click to expand...
 
anyone have a list of the AT Commands for the Novatel card ? I am trying to send sms' from Linux.. how would one go about it ?
 
nicojvr said:
anyone have a list of the AT Commands for the Novatel card ? I am trying to send sms' from Linux.. how would one go about it ?
Click to expand...

Try the following:

Use the storage command to select the correct memory area

AT+CPMS=”SM”

Enable text mode

AT+CMGF=1

Start a new message:

AT+CMGS=”phone number of recipient”

The GT response is “>”

The plain text message is typed in entered with a terminating CTRL-Z.

If the message is sent without error then after a few seconds you receive:

+CMGS: n

where n is the SIM message store number.
 
Hi Tazz_Tux
thanks for all you contributions to this forum.
Could you please help me with the HUAWEI card? I followed all the steps for the Option card but when I check my dev's Suse picked it up as a HUAWEI card. Is there any where in the Option setup which I therefore need to edit and replace the word Option with HUAWEI or what do have to do to get HUAWEI going? As you can probably see I'm a bit of a new one with Linux! Thanks
 
Hey,

Can you post the /var/log/message output when you insert the card ?

Laterz !

gerkot said:
Hi Tazz_Tux
thanks for all you contributions to this forum.
Could you please help me with the HUAWEI card? I followed all the steps for the Option card but when I check my dev's Suse picked it up as a HUAWEI card. Is there any where in the Option setup which I therefore need to edit and replace the word Option with HUAWEI or what do have to do to get HUAWEI going? As you can probably see I'm a bit of a new one with Linux! Thanks
Click to expand...
 
here we go

Jun 14 19:09:04 ossie kernel: hub 6-0:1.0: USB hub found
Jun 14 19:09:04 ossie kernel: hub 6-0:1.0: 1 port detected
Jun 14 19:09:04 ossie kernel: PCI: Enabling device 0000:04:00.1 (0000 -> 0002)
Jun 14 19:09:04 ossie kernel: ACPI: PCI interrupt 0000:04:00.1 -> GSI 5 (level, low) -> IRQ 5
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: OHCI Host Controller
Jun 14 19:09:04 ossie kernel: PCI: Setting latency timer of device 0000:04:00.1 to 64
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: irq 5, pci mem 0x40801000
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 7
Jun 14 19:09:04 ossie kernel: hub 7-0:1.0: USB hub found
Jun 14 19:09:04 ossie kernel: hub 7-0:1.0: 1 port detected
Jun 14 19:09:04 ossie kernel: load_module: err 0xffffffef (dont worry)
Jun 14 19:09:05 ossie kernel: usb 6-1: new full speed USB device using ohci_hcd and address 2
 
After this type

Code: 
modprobe usbserial

Laterz !

gerkot said:
Jun 14 19:09:04 ossie kernel: hub 6-0:1.0: USB hub found
Jun 14 19:09:04 ossie kernel: hub 6-0:1.0: 1 port detected
Jun 14 19:09:04 ossie kernel: PCI: Enabling device 0000:04:00.1 (0000 -> 0002)
Jun 14 19:09:04 ossie kernel: ACPI: PCI interrupt 0000:04:00.1 -> GSI 5 (level, low) -> IRQ 5
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: OHCI Host Controller
Jun 14 19:09:04 ossie kernel: PCI: Setting latency timer of device 0000:04:00.1 to 64
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: irq 5, pci mem 0x40801000
Jun 14 19:09:04 ossie kernel: ohci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 7
Jun 14 19:09:04 ossie kernel: hub 7-0:1.0: USB hub found
Jun 14 19:09:04 ossie kernel: hub 7-0:1.0: 1 port detected
Jun 14 19:09:04 ossie kernel: load_module: err 0xffffffef (dont worry)
Jun 14 19:09:05 ossie kernel: usb 6-1: new full speed USB device using ohci_hcd and address 2
Click to expand...
 
Jun 16 07:58:06 ossie kernel: ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Jun 16 07:58:06 ossie kernel: PCI: Enabling device 0000:04:00.0 (0000 -> 0002)
Jun 16 07:58:06 ossie kernel: ACPI: PCI interrupt 0000:04:00.0[A] -> GSI 5 (level, low) -> IRQ 5
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.0: OHCI Host Controller
Jun 16 07:58:06 ossie kernel: PCI: Setting latency timer of device 0000:04:00.0 to 64
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.0: irq 5, pci mem 0x40800000
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 6
Jun 16 07:58:06 ossie kernel: hub 6-0:1.0: USB hub found
Jun 16 07:58:06 ossie kernel: hub 6-0:1.0: 1 port detected
Jun 16 07:58:06 ossie kernel: PCI: Enabling device 0000:04:00.1 (0000 -> 0002)
Jun 16 07:58:06 ossie kernel: ACPI: PCI interrupt 0000:04:00.1 -> GSI 5 (level, low) -> IRQ 5
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.1: OHCI Host Controller
Jun 16 07:58:06 ossie kernel: PCI: Setting latency timer of device 0000:04:00.1 to 64
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.1: irq 5, pci mem 0x40801000
Jun 16 07:58:06 ossie kernel: ohci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 7
Jun 16 07:58:06 ossie kernel: hub 7-0:1.0: USB hub found
Jun 16 07:58:06 ossie kernel: hub 7-0:1.0: 1 port detected
Jun 16 07:58:06 ossie kernel: load_module: err 0xffffffef (dont worry)
Jun 16 07:58:08 ossie kernel: usb 6-1: new full speed USB device using ohci_hcd and address 2
Jun 16 07:58:30 ossie su: (to root) iss on /dev/pts/7
Jun 16 07:58:38 ossie kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Jun 16 07:58:38 ossie kernel: usbcore: registered new driver usbserial_generic
Jun 16 07:58:38 ossie kernel: usbcore: registered new driver usbserial
Jun 16 07:58:38 ossie kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
 
Try the two modprobe commands on the first post - modprove useserial vendor....

Just remember to rmmod usbserial in between :)

Laterz

gerkot said:
Jun 16 07:58:06 ossie kernel: ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
*snip*
Jun 16 07:58:38 ossie kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Click to expand...
 
Huawei card

Hi Tazz_tux

I check the product and vendor id through the cat /proc/bus/usb/devices command. I ran the modprobe usbserial command. My problem is that I dont know the port name, and if I do find /dev/
grep Huawei I dont get anything. Then I can edit the wvdial.conf file.
Any thoughts on that?

cheers
 
Hey gerkot,

Once the card is detected properly, the usbserial driver will log this info into syslog. Have a look at the example for option, you will see that it tells you what port it is registering.

Laterz !

gerkot said:
Hi Tazz_tux

I check the product and vendor id through the cat /proc/bus/usb/devices command. I ran the modprobe usbserial command. My problem is that I dont know the port name, and if I do find /dev/
grep Huawei I dont get anything. Then I can edit the wvdial.conf file.
Any thoughts on that?

cheers
Click to expand...
 
Hi Tazz_tux

I done the modprobe thing using the product and vendor ID's found with the cat /proc/bus/usb/devices command. I can see it loads a generic USB driver but it stops there and never registers the card at a specif port. Any other suggestions? Is it possible that the generic driver doesnt support the Hauwei card under Suse?

Cheers
 
WVDIAL not working with Huawei but Kinternet working to a point

I've given up with Wvdial seeing my Huawei card. I had the most success with Kinternet: at least it dials and see the modem. However, I get an error message IPCP: timeout sending Config-Requests and the card disconnects. Anyone have any ideas to fix or work around? I'm on Suse9.3

Cheers
 
Can you post some IPCP messages that you seeing ?

This would be the same as 619 under Windows from what I remember :(

gerkot said:
I've given up with Wvdial seeing my Huawei card. I had the most success with Kinternet: at least it dials and see the modem. However, I get an error message IPCP: timeout sending Config-Requests and the card disconnects. Anyone have any ideas to fix or work around? I'm on Suse9.3

Cheers
Click to expand...
 
Hi Tazz_tux

Thanks for prompt reply. I found the problem. One of the AT commands was specified wrong on page 4 or 5 of this thread. Init8 should read:
INIT8='AT+CGDCONT=1,"IP","internet"'

I'm in area with no 3G reception (Carletonville) at present. But GPRS seem to be working fine.

Cheers
 
Nozomi 2.1 Released

Hey everyone,

The updated driver is release. Here is a changelog:

* - Stability Improvements. Incorporated spinlock wraps patch.
* - Updated for newer 2.6.14+ kernels (tty_buffer_request_room)
* - using __devexit macro for tty

Note that this driver is *BETA* and that my webspace still had the old one (nozomi.old.tgz)

I havn't personally tried it, but let me know !

Laterz !
 
Problem with Linux Connecting to VOdacom

I have been running a 3G connection (Novatel card on Suse 10.0) for a number of months with great success. (Thanks to all the good support in this forum). I have the problem where for some reason, the DNS server ip addresses comes through as 10.11.12.13 and I have implemented the workaround where I put the DNS names in the resolv.conf file. As I said this has been working very well for about 6 months now.

About 3 weeks ago I started getting problems when connecting to Vodacom. When I look in the log files, I can see that pppd is able to start up, communicate with the modem and start the ICMP negotiations. Of late, after the second try, the modem gives a Hangup and of course the whole process has to restart.

This is a recent development and I don't know if anything has changed on the Vodacom side. Of course trying the Windows Only Help desk tells you to go away because they dont support Linux.

Has anybody else seen this behaviour? Has anybody been able to fix this?
Any help will be appreciated
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X