Neoconnect Lite under Linux?

E

elton!!

Member
Joined
Dec 28, 2005
Messages
13
Reaction score
0
Does it not work at all? :( I was unable to find any indication that it does... :(

And is it just the Prime device thats getting an upgrade or will there be a new Lite device too?
 
Last edited:
I was wondering the same thing, does the Neotel hardware work with Linux?
 
It's the same technology as the Prime device so it should work under linux. There was thread a while back explaining the procedure. I think the title was "Neotel working under Linux". You might want to try searching for it. I have used it successfully on my linux machine although I couldn't exceed 480kbps download speeds for some reason (this shouldn't be a problem on the Lite package).
 
I have the Prime device, but what I have come across on the forums is that the Lite device will connect the same using pppconfig or wvdial.

@elton: If your considering Neotel then get the device, test it out and you have 7 days to return it if your not happy with the service. If you do get it working (which you should), then it would help others.
 
Neoconnect lite linux woes

I just signed up today and have not been able ot get the device working under linux. I attempted to follow the guides on the forum, but ran into a couple of issues:

1- The device was detected as a usbserial device on plugin/bootup, however no ttyUSB devices are detected.
2- Along with the bootup usbserial detection, another driver was loaded. The driver name was : ti_usb_3410_5052
3- The ti_usb_3410_5052 driver reports an error "ti_usb_3410_5052: probe of 2-2:1.0 failed with error -5"
4- My attempt to fix this was: "rmmod ti_usb_3410_5052 && rmmod usbserial && modprobe usbserial vendor=0x0451 product=0x3410". This produced a ttyUSB0 device.
5- The ttyUSB0 device didn't do anything using wvdial or pppconfig and pon. Nothing changed on the neotel devices screen(a windows dialups displays some informtion when dialing).

This problem presented itself on 2 different computers, both running Ubuntu 8.04

lsusb output
Code: 
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0451:3410 Texas Instruments, Inc. TUSB3410 Microcontroller
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Bootup dmesg output
Code: 
[   35.100867] usbcore: registered new interface driver usbserial
[   35.100885] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[   35.100908] usbcore: registered new interface driver usbserial_generic
[   35.100910] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   35.118380] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 3410 1 port adapter
[   35.118397] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 5052 2 port adapter
[   35.118425] ti_usb_3410_5052: probe of 2-2:1.0 failed with error -5
[   35.118432] usbcore: registered new interface driver ti_usb_3410_5052
[   35.118435] /build/buildd/linux-2.6.24/drivers/usb/serial/ti_usb_3410_5052.c: TI USB 3410/5052 Serial Driver v0.9
[   35.266803] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 21
[   35.266935] PCI: Setting latency timer of device 0000:00:11.5 to 64
[   35.782147] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 22

modprobe usbserial .... dmesg
Code: 
[  521.130386] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial deregistering driver TI USB 3410 1 port adapter
[  521.130424] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial deregistering driver TI USB 5052 2 port adapter
[  521.130440] usbcore: deregistering interface driver ti_usb_3410_5052
[  554.937613] usbcore: deregistering interface driver usbserial_generic
[  554.937653] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic
[  554.937669] usbcore: deregistering interface driver usbserial
[  563.188614] usbcore: registered new interface driver usbserial
[  563.188892] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[  563.189140] usbserial_generic 2-2:1.0: generic converter detected
[  563.189416] usb 2-2: generic converter now attached to ttyUSB0
[  563.189637] usbcore: registered new interface driver usbserial_generic
[  563.189642] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial Driver core
 
Well you would want to use minicom to "talk" to your modem, so you would startup minicom and go to setup to tell it to connect to /dev/ttyX, then start using the modem commands ATZ initialization commands etc. If you do get a response, then you know your pppconfig/script is the problem. If you aren't getting any response, then you know your driver isn't setup correctly.
 
Well it seems I did do it correctly last night. No response at all, connected to ttyUSB0, the only usb serial device on the system and detected when the device is plugged in.

Next attempt is a serial cable between the device and computers serial port. As far as I'm aware, the cable is a usb to serial adaptor. As such hopefully the issues are in the cable and not the device
 
Well I tried, neither linux nor windows saw the device when connected through a serial cable. The cable itself is old and did not fit snuggly into the device, so I cannot say if it is the device or the cable that wasn't working. Or I could be completely wrong and that serial port looking port is something else entirely
 
No luck yet, even tried editing the device driver source (from an internet search result) and compiling the kernel.

EDIT: My metric for success is if wvdialconf detects a modem
 
@Kasbah: The one immediate problem I see is the modprobe being in the wrong order. The modprobe command should be executed before the device is even plugged in, as it informs the kernel what to expect from a device with vendor id = x and product id = y (x=0451 and y=3410 in this case). This should be done between startup and the device being plugged in. If the device has already been plugged in you'll either have to rrmod the usbserial and ti_usb_3410_5052 drivers (best done before unplugging and might not solve the issue) or reboot.

I kindof gave up on the linux driver for a while (Had more important things to do and found that using my linux_laptop synergy sharing the keyboard and windows ICS on the dialing machine worked for me). Some possible solutions I'm planning on looking at are newer kernels (built by me) or older kernels (2.4 series or earlier 2.6). I don't hold that much hope though.
 
Jacl said:
@Kasbah: The one immediate problem I see is the modprobe being in the wrong order. The modprobe command should be executed before the device is even plugged in, as it informs the kernel what to expect from a device with vendor id = x and product id = y (x=0451 and y=3410 in this case). This should be done between startup and the device being plugged in. If the device has already been plugged in you'll either have to rrmod the usbserial and ti_usb_3410_5052 drivers (best done before unplugging and might not solve the issue) or reboot.

I kindof gave up on the linux driver for a while (Had more important things to do and found that using my linux_laptop synergy sharing the keyboard and windows ICS on the dialing machine worked for me). Some possible solutions I'm planning on looking at are newer kernels (built by me) or older kernels (2.4 series or earlier 2.6). I don't hold that much hope though.
Click to expand...

ty Jacl
I will try rebooting then before plugging in the Lite device will do a modprobe and see what happens, I'm a new user to the Linux scene so basically trial and error for me. I just got back and see I have the iso for Xubuntu completed, going to boot up with Xubuntu and see what I can get right.

Would be awesome if you managed to get a kernel built by you that supports the Lite device :-) really it would, best of luck boet.
 
Has anyone managed to get the Lite device working on Linux?

I would appreciate some help please... :)

I am using Ubuntu 8.10 and got to creating a ttyUSB0 device but it does not seem to dial (after running pppconfig) and wvdialconf just says it failed to connect... :mad:

Am I missing something?

TIA ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X