HOWTO: LINUX & Neotel Prime (2010)

[Other Pineapple Smurf]

Ok, I've just discovered how to get the Neotel Prime device working under Linux (without compiling drivers), this applies to all newish kernels that use the option.ko driver.

No need to compile anymore and you get the full speed. The method on Neotels website is Mkay, but you get throttled due to the driver and not the divice.

as root, execute the following:

echo "1d09 4000" > /sys/bus/usb-serial/drivers/option1/new_id

Thats it!!!!!!

This is a special work around that the driver maintainers have made to support devices not yet in the driver. * It is actually the preferred method and will also work with GSM modems that are not yet in the option.ko driver.

NOTE: If you are not loading the "option.ko" driver then you need to do the following instead:

As root:

modprobe -v option
echo "1d09 4000" > /sys/bus/usb-serial/drivers/option1/new_id

 

[Other Pineapple Smurf]

My UDEV rules:

File: /lib/udev/rules.d/99-neotel.rules

# udev rule
ACTION=="add",ATTRS{idVendor}=="1d09",ATTRS{idProduct}=="4000",RUN+="/usr/local/sbin/neotel_driver.sh"

File: /usr/local/sbin/neotel_driver.sh

#!/bin/sh
modprobe -v option
echo '1d09 4000' > /sys/bus/usb-serial/drivers/option1/new_id

(As root, do not forget to "chmod +x /usr/local/sbin/neotel_driver.sh" )

Now my neotel works perfect at each reboot !!!

This has been tested under Ubuntu9.10 and Arch Linux.

 

[sjm]

On Fedora (& probably a few other distributions) you need to specify the path to modprobe in neotel_driver.sh, so it becomes

File: /usr/local/sbin/neotel_driver.sh

#!/bin/sh
/sbin/modprobe -v option
echo '1d09 4000' > /sys/bus/usb-serial/drivers/option1/new_id

My UDEV rules:

File: /lib/udev/rules.d/99-neotel.rules

# udev rule
ACTION=="add",ATTRS{idVendor}=="1d09",ATTRS{idProduct}=="4000",RUN+="/usr/local/sbin/neotel_driver.sh"

File: /usr/local/sbin/neotel_driver.sh

#!/bin/sh
modprobe -v option
echo '1d09 4000' > /sys/bus/usb-serial/drivers/option1/new_id

(As root, do not forget to "chmod +x /usr/local/sbin/neotel_driver.sh" )

Now my neotel works perfect at each reboot !!!

This has been tested under Ubuntu9.10 and Arch Linux.

 

[Other Pineapple Smurf]

Some updated: I found my UDEV rules where not always being execute by Ubuntu, or executed when I expected them to. My work around, is to rather create a cron job

File: /etc/cron.d/neotel

@reboot root /usr/local/sbin/neotel_driver.sh > /dev/null

This will execute my script at each reboot. This happens only after the cron dameon has started up and there seem to be enough delay for my script not to run into any issues.

I also noticed that since I switched to this method (no longer compiling drivers), my Neotel connection is way more stable. I do not understand enough of driver compiling to understand why? (Personally I'm also migrating to ARCH LINUX and have /dev/null interest in Ubuntu)

 

[Crummy_Gummy]

Hiya

This approach worked really well for me with my NoeConnect device. I have an issue that when a phone call is made the device disconnects. Once the device goes back onto "internet mode" you have to restart it before I can reconnect as the whole interface locks up. Have any of you come across/fixed this issue before?

 

[Other Pineapple Smurf]

Make sure you are using my method and not the one on the Neotel site. The "old" method that is posted there uses a dodgy driver that causes this. You need to either power cycle your USB or unload/reload the drivers each time.

My method overcomes that as it uses the preferred drivers for CDMA phones.

I'm now running Arch Linux and cannot comment on other distros. Ubuntu is moving to "services" to control networking (that came through today at my work PC). I did find that network manager was really dodgy this year and caused much frustration.

I personally use wvdial in the background to check if my connection is up and dial if not found.

 

[majikins]

is this the ets2252+ phone?

Hi

Will this work for the ets2252+ phone?

M

 

[Other Pineapple Smurf]

Hi, I've used the same for various GSM modems with 100% success. You just need to do a "lsusb" to get the vendor/product id.