Page 1 of 1
Issues with 2.6.13-r3 Linux Kernel - SOLVED

Posted:
Mon Oct 10, 2005 3:36 am
by elrod
Hi, my uirt is not being recognized by a new linux build with 2.6.13-r3.
It works fine on another server which is 2.6.11-r3.
On the failing server when I plug it in I see a new full speed USB device but nothing describing it. The other server mentions USB_UIRT.
Is there a kernel config option that has to be set differently now?
What config options are required?
Thanks,
Eric

Posted:
Mon Oct 10, 2005 11:29 am
by jrhees
That's unusual -- the ftdi_sio driver is what is used in Linux to drive the USB-UIRT. You may want to look and see if it is included in the your new build's distribution.
-Jon

Posted:
Mon Oct 10, 2005 4:21 pm
by elrod
Jon, I'll look at that. Would you happen to know how I get the module added in via the kernel .config? Is it USB_SERIAL=y?

Posted:
Fri Oct 14, 2005 7:01 pm
by elrod
Ok, found the correct .config options (duh) and now it gives the message "now attached to ttyUSBO". However, that does not show up in /dev. What does show up is /dev/tts/USB0.
So, I changed the lirc to link to that location.
lircd starts with no errors
irrecord says:
- Code: Select all
No UIRT device found at /dev/tts/USB0
I'm using lirc 7.1 and the patch.
Help....

Posted:
Fri Oct 14, 2005 10:55 pm
by jrhees
That seems odd (with my limited experience of Linux).
Usually it will be placed at \dev\tty\USBx not tts...
If the FTD_SIO is working correctly, you should be able to open a terminal program on the port \dev\tty\USBx and aim a remote at the USB-UIRT and press some buttons and see junk appear on the terminal screen.
-Jon

Posted:
Mon Oct 17, 2005 4:12 pm
by elrod
Hi Jon, opened a terminal program and nothing was spit out to the console. However, it did make me pay more attention and I noticed something strange:
1) hitting remote buttons makes uirt flash
2) open console on serial port
3) hit remote, flashes once and then no more flashing
4) no output to console
5) close console
6) uirt flashes in reaction to remote again.
Nothing in dmesg.
Any ideas on how to further debug what is happening?

Posted:
Tue Oct 18, 2005 12:14 am
by jrhees
You may want to take a look at the Linux howto posted by another user today.
-Jon

Posted:
Wed Oct 19, 2005 12:22 pm
by elrod
Thanks Jon, that got me going.
For future use here is the link to the howto:
[url]
http://65.36.202.170/phpBB2/viewtopic.php?p=3959#3959[/url]