AirLink ASOHOUSB help

[cmessa]

I just picked up an Airlink ASOHOUSB usb adapter for my tivo. I have been successfully using a USB200M for about a year. I think it was a version 1 because I also bought a version 2.1 and it is not working.

The ASOHOUSB is not working either. I have updated the networking files from Jamie's backport drivers for kernel 2.4.20. I am using a Directivo 6.2a system. When I plug in the ASOHOUSB I get the power light and sometimes the link light comes on solid, but can never ping the Tivo. If I put the USB200M back in, it works fine. I checked the tivolog file and this is what I see when I plug in the different devices.

Dec 16 04:01:00 (none) LinuxHotplug[165]: Unplug device 0b95/7720 <Airlink ASOHOUSB>
Dec 16 04:01:01 (none) LinuxHotplug[165]: Plug device 0b95/7720 <Airlink ASOHOUSB>
Dec 16 04:01:13 (none) LinuxHotplug[165]: Unplug device 0b95/7720 <Airlink ASOHOUSB>

Dec 16 04:01:25 (none) LinuxHotplug[165]: Plug device 077b/2226 <Linksys USB200M>
Dec 16 04:01:25 (none) NetworkInterface[165]: If0: Startup 00:13:10:dc:0c:f7 <Linksys USB200M> medium 4
Dec 16 04:01:25 (none) NetworkInterface[165]: If0: Setting IPv4 params
Dec 16 04:01:25 (none) LinuxNetworkInterface[165]: If0: Manual config
Dec 16 04:01:25 (none) NetworkInterface[165]: If0: Done setting IPv4 params

It looks like I have the usb.map files correct because it recognizes the ASOHOUSB, but I do not get the network interface info like I do with the USB200M.

I have tried rebooting, but still no go. I also have tried other things like the insmod commands some used in the RC.SysInit.Author file. I also tried the commands to turn off the network, sleep, then turn it back on. Both are suggestions that I have seen in other thread. None seemed to make a difference.

Anyone got any ideas as to what might be going on. Maybe I did something wrong with the backport drivers? I copied the three (I think three) files over, did the system link like I was supposed to and the USB200M seems to be fine.

Thanks for anyone's help. Maybe if I get this working, the USB200M v2.1 will also start to work. I get the same info in the log with it, but I get no lights on it at all.

CMessa

[Jamie]

kernel and or messages from /var/log would be more useful than tvlog.

Also, from bash on serial, check ifconfig. Does eth0 show up?

[cmessa]

What files should be in the /var/log folder? All I see is a svclog and TivoLogHead. What ones are useful? Not much in svclog.

I will have to look into getting a serial cable. Been doing this for several years and managed to get by without, I guess that will have to change :) I think I have some parts around here to make my own cable.

thanks for the help.
CMessa

[Jamie]

What files should be in the /var/log folder? All I see is a svclog and TivoLogHead. What ones are useful? Not much in svclog.

I will have to look into getting a serial cable. Been doing this for several years and managed to get by without, I guess that will have to change :) I think I have some parts around here to make my own cable.

thanks for the help.
CMessaThere should be a bunch of log files in /var/log. kernel and messages are primarily kernel messages. tvlog, tverr and tclient are useful logs from the tivo software. Files with an "O" at the beginning of the name are older versions of the same files. I think a SA tivo rolls the logs each time it makes a service call, IIRC.

[cmessa]

ok, I finally got a serial cable from 9th tee. works fine, I get see the info when it boots up. I am unable to actually type anything because I never get a prompt. I am thinking that I must not have something right in that department, but I will search for an answer. What am I looking for when I do finally get the bash prompt?

Cmessa