Page 2 of 50 FirstFirst 123412 ... LastLast
Results 16 to 30 of 736

Thread: USB2 backport from 2.4.27 to 2.4.4/2.4.18/2.4.20 SUPPORT

  1. #16
    Join Date
    Jun 2004
    Posts
    191
    Quote Originally Posted by Jamie
    Perhaps /etc/hotplug/usb.map? I haven't messed with that file, but I believe it maps vendor/product id's to driver module names.It sounds to me like you have the wrong usbnet module loaded initially if it doesn't recognize that vendor/product id. Older usbnet modules won't recognize that device (and you'll get that message). Only the latest usbnet.o knows about it.
    Yes, the map file was what I was looking for. Thanks. I've added it in, I'll report back how it works.

    As to the usbnet.o file, the one in lib/modules is the latest one (or so I think)
    -rw-r--r-- 1 0 0 41332 Jun 27 19:38 usbnet.o
    Is there any way another one could be loading from somewhere else? The only old copy I have is in /lib/modules_bu (backup) and I don't think that would be used, but...
    here's the output of find:
    Code:
    tivo-bedroom:/$ find / -name usbnet.o
            /lib/modules/usbnet.o
    /lib/modules_bu/usbnet.o
    /hack/usb-2.4.27/obj/drivers/2.4.20/usbnet.o
    I can't remember how to recursive grep with this grep witout the -R option, so I'm having a tough time finding what loads the usbnet.o file (I know it has to be in one of these support threads...)

  2. #17
    Join Date
    Feb 2005
    Posts
    41

    Toshiba DVDR Series2.5 with Linksys USB200m

    Well I successfully installed the new drivers for my usb200m adapter, but I don't see any difference in FTP/TyTool transfer speed (pegged at 500kByte/sec) compared to the stock drivers... So I'm looking to see what I can fix/tweak...

    Here's my boot:
    Code:
    usb.c: registered new driver usbdevfs
    usb.c: registered new driver hub
    usb.c: starting integrated EHCI driver
    ehci_hcd EHCI-Direct: BRCM-EHCI
    ehci_hcd EHCI-Direct: irq 8, pci mem fffe8170
    usb.c: new USB bus registered, assigned bus number 1
    ehci_hcd EHCI-Direct: illegal capability!
    ehci_hcd EHCI-Direct: USB 0.0 enabled, EHCI 10.10, driver 2003-Dec-29/2.4
    hub.c: USB hub found
    hub.c: 2 ports detected
    bcm-usb.h: TiVo 2-chip USB Host Controller
    usb.c: EHCI initialization succeeded
    hub.c: new USB device EHCI-Direct-2, assigned address 2
    usb.c: USB device 2 (vend/prod 0x77b/0x2226) is not claimed by any active driver.
    usb-ohci.c: USB OHCI at membase 0xfffe8100, IRQ 8
    usb-ohci.c: usb-OHCI-Direct, BRCM-OHCI
    usb.c: new USB bus registered, assigned bus number 2
    hub.c: USB hub found
    hub.c: 2 ports detected
    bcm-usb.h: TiVo 2-chip USB Host Controller
    usb.c: registered new driver usbnet
    eth0: register usbnet usb-EHCI-Direct-2, ASIX AX8817x USB 2.0 Ethernet
    My ifconfig:
    Code:
    eth0      Link encap:Ethernet  HWaddr 00:10:60:84:BE:F4
              inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:43 errors:0 dropped:0 overruns:0 frame:0
              TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:6353 (6.2 Kb)  TX bytes:9031 (8.8 Kb)
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    Any ideas or suggestions?
    Thanks!
    -- S8C

  3. #18
    Join Date
    Aug 2004
    Posts
    4,087
    Quote Originally Posted by Jeff D
    As to the usbnet.o file, the one in lib/modules is the latest one (or so I think)
    -rw-r--r-- 1 0 0 41332 Jun 27 19:38 usbnet.o
    ok. time for a new theory: The hotplug stuff is unloading the usbnet driver when you unplug the dlink device, but not reloading it when you plug in the airlink.
    Is there any way another one could be loading from somewhere else? The only old copy I have is in /lib/modules_bu (backup) and I don't think that would be used, but...
    here's the output of find:
    Code:
    tivo-bedroom:/$ find / -name usbnet.o
            /lib/modules/usbnet.o
    /lib/modules_bu/usbnet.o
    /hack/usb-2.4.27/obj/drivers/2.4.20/usbnet.o
    I can't remember how to recursive grep with this grep witout the -R option, so I'm having a tough time finding what loads the usbnet.o file (I know it has to be in one of these support threads...)
    Busybox is annoying...

    You can pipe find into xargs and run grep there: find / -type f | xargs grep usbnet./

  4. #19
    Join Date
    Aug 2004
    Posts
    4,087
    Quote Originally Posted by santa8claws
    Well I successfully installed the new drivers for my usb200m adapter, but I don't see any difference in FTP/TyTool transfer speed (pegged at 500kByte/sec) compared to the stock drivers... So I'm looking to see what I can fix/tweak...
    Transfer performance on the series 2.5 is bad. There doesn't seem to be a lot we can do about it. Still, I get ~1.3 MB/sec, so you should be able to do better than 500KB/sec t if the box is idle. There are three places where performance might be affected: the tivo, the PC, and in-between. You can elliminate the in-between as an issue by testing a direct point-to-point connection with a cross over cable.

  5. #20
    Join Date
    Jun 2004
    Posts
    191
    Jamie, it appears your theory may be on the right track....(see below).

    I patched the map file to include the adapter under the ax8817x section.

    If I reboot with the airlink adapter connected it starts up working, this despite the report of an unclaimed device. All lights on and working.

    If I swap out the airlink for the dlink the dlink powers up and works.
    If I then swap out the dlink for the airlink the airlink doesn't come online.

    -----

    If I start from scratch with the airlink connected I can disconnect and reconnect the adapter and it powers up fine. If I then try to swap for the dlink the dlink doesn't come up.

    here's the progress of mod load status as the operations happen:
    Code:
    Airlink boot:
    lsmod
    Module                  Size  Used by    Not tainted
    ax8817x                26640   1
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [ax8817x usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    
    Airlink disconnected:
    ax8817x                26640   0
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [ax8817x usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    
    Airlink reconnected:
    ax8817x                26640   1
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [ax8817x usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    
    Works!
    Swap out airlink for dlink
    
    Dlink connected:
    Doesn't work!
    Module                  Size  Used by    Not tainted
    ax8817x                26640   0 (unused)
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [ax8817x usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    
    Swap Dlink for Dlink: 
    Works!
    Module                  Size  Used by    Not tainted
    ax8817x                26640   1
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [ax8817x usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    
    Dlink disconnected:
    Notice what happened to ax8817x! usb-ochi also doesn't show ax8817x.
    
    usb-ohci               23888   0 (unused)
    usbcore               101936   0 [usb-ohci]
    router                 66896  36
    therm                   1488   0
    fan                     2240   0
    ideturbo                5216   1
    irblast                 3792   0 (unused)
    brcmdrv-rb           1228256 138
    cobra                  91264   4
    oslink                 26112  12
    ircatch                26832   2
    i2c_Series2            14320   0 [therm fan cobra]
    modemtty_Series2        4896   0
    fpga                    1920   2
    tivoconfig               960   0 (unused)
    It seems there is something specific to the dlink unloading that removes ax8817x rather than just decrementing the use counter. This didn't happen when a) airlink adapters are swapped out, or dlink was swapped in and not claimed (didn't start up).

    BTW: Since you asked and I never responded... HDVR2 (series 2) running 6.2 (2.4.20 kernel)
    Last edited by Jeff D; 06-28-2005 at 01:39 AM.

  6. #21
    Join Date
    Jun 2005
    Posts
    4

    USB2 drivers not increasing xfer speeds

    Trying to update a Hughes HDVR2 6.2 system to USB2 drivers
    Using the usbobj2.4.27-20050104.tar.bz2 (http://www.dealdatabase.com/forum/at...achmentid=4258) files. The transfer speed I get from either ftp or from tytools is ~600k which is what I was getting before switching drivers. I'm going through a 100mb belkin router which is connected to a 100mb switch and that is connected to my DirecTivo via a linksys USB200M.

    Here's what I did: I backed up (moved) from /lib/modules ax8817x.o, usbcore.o, and usb-ohci.o. The ehci-hcd.o file was not in /lib/modules.
    Then, I copied in the following to /lib/modules:
    ./usb-2.4.27/obj/hosts/2.4.20_Series2/usbcore.o
    ./usb-2.4.27/obj/hosts/2.4.20_Series2/usb-ohci.o
    ./usb-2.4.27/obj/drivers/2.4.20/usbnet.o
    set symlink usbnet.o to ax8817x.o

    Finally I restarted Tivo and afterwards I don't see any performance improvement.

    Here's the ifconfig output if it helps:
    bash-2.02# ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

    eth0 Link encap:Ethernet HWaddr 00:10:60:85:A9:21
    inet addr:192.168.2.101 Bcast:192.168.2.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:2794 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:4765861 dropped:4248 overruns:0 carrier:0 coll:0


    Attaching the console boot log.

    Any ideas?
    Last edited by jmrwiseguy; 06-28-2005 at 02:42 AM.

  7. #22
    Join Date
    Jun 2004
    Posts
    191
    jmrwiseguy, not that I know what I'm talking about, but you didn't mention anything about the new mfs_ftp files. Did you update those too?

    links are in the soapbox derby thread linked in post #1 of this topic.

  8. #23
    Join Date
    Jun 2005
    Posts
    4
    Quote Originally Posted by Jeff D
    jmrwiseguy, not that I know what I'm talking about, but you didn't mention anything about the new mfs_ftp files. Did you update those too?

    links are in the soapbox derby thread linked in post #1 of this topic.
    No, I only updated the files that Jamie listed in his original post. I did look at the soapbox derby thread but it looked like it was only for the mfs tools stuff. For now, I'm just using tivoftpd for doing ftp so I didn't think I would need to update the mfs stuff. Perhaps somebody can tell me otherwise.

    However, in that soapbox derby post there was a mention of a usbcore.o loading tweak -- I'm not using that -- should I?

    Also, I didn't do the vwait patch either because it was for 4.01b.

    Thanks,

  9. #24
    Join Date
    Aug 2004
    Posts
    4,087
    Quote Originally Posted by jmrwiseguy
    No, I only updated the files that Jamie listed in his original post. I did look at the soapbox derby thread but it looked like it was only for the mfs tools stuff. For now, I'm just using tivoftpd for doing ftp so I didn't think I would need to update the mfs stuff. Perhaps somebody can tell me otherwise.

    However, in that Soapbox derby post there was a mention of a usbcore.o loading tweak -- I'm not using that -- should I?

    Also, I didn't do the vwait patch either because it was for 4.01b.
    The soapbox derby thread has a lot of good performance tuning tips and is probably a good place to continue to discuss "how do I get this to perform better?".

    I always recommend getting some baseline bandwidth measurements with netperf before worring about application level performance. If you can't get good netperf numbers, you're unlikely to get good application performance.

    As I mentioned earlier:
    There are three places where performance might be affected: the tivo, the PC, and in-between. You can elliminate the in-between as an issue by testing a direct point-to-point connection with a cross over cable.
    You might try a crossover cable to eliminate your switch and router devices as culprits in the slowdown. Yoiu might also want to look at the later versions of the drivers, which have some additional support for "pause frame" flow control. It might make a difference for you, depending on your switch and router.

    mfs-utils (mfs_* tools) has an improved tserver (for tytool) and improved import/export utilities (for mfs_ftp). This can help your overall transfer performance since they reduce the cpu load on the tivo during a transfer. Once you have good base network performance, it makes sense to start looking for performance improvements on the application side.

    I know that 7.1x doesn't have the vwait problem. I'm not sure, but I don't think 6.2 has it either. In general though, it makes sense to run top on the tivo and look for processes that are hogging cpu. Tivo network transfers are almost always cpu limited.
    Last edited by Jamie; 06-28-2005 at 03:25 PM.

  10. #25
    Join Date
    Nov 2004
    Posts
    10

    35

    Quote Originally Posted by Jamie
    You are at a point here where it is difficult to diagnose further without a serial console cable.

    There are several possibilities that might be causing your problems and those of gpontis, described elsewhere:

    6.2 network configuration issues
    One way to eliminate this as a possibility is to boot up to a bare bash, with no tivo software running, and install and configure the device from the serial console. If that doesn't work either, then it probably isn't a 6.2 only issue.
    Serial console is all set up and working like a champ (man, I'm really glad I finally took this step...). I got to the bare bash and insmod'ed the drivers. Then I was unsure of what to do, so I set the rc.sysinit file back the way it was before. Thought I probably needed to set up network configs but wasn't really sure (or confident) in what to do.

    Quote Originally Posted by Jamie
    Link negotiation
    I really only tested with 1000 and 100 mbps switches. I didn't test half duplex on hubs. It's possible there is a problem negotiating the link type with the link partner. What are you connecting to?
    Belkin Wireless-G router. Symptoms are the same whether I connect wirelessly or wired.
    Quote Originally Posted by Jamie
    More than one hardware version.
    It could be that there is more than one version of this hardware, and the driver works with some (mine) but not others (yours). I think this is unlikely, but possible. The appears to be revision info in /proc/bus/usb/devices if you have usbdevfs mounted (mount -t usbdevfs usbdevfs /proc/bus/usb). My AGIGAUSB shows: Rev= 0.01.
    I cannot, for the life of me, get anything to come up when I try to open the devices file, so I can't tell what the version is. Again...I'm sure it's just something I am doing wrong.

    I'm thinking that at this point, I need to bone up more on Linux commands. To tell the (brutal) truth, right now I feel like a total noob who's well-read on DDB (many months) but is still missing some really important aspects. Maybe I'm just better at lurking and waiting for answers...

    Nonetheless, I have attached my boot log from the last reboot. Hey, at least I'm trying, right? There's a bunch of "Inode" alerts, but I figure I'll cross that bridge at another time.

    [EDIT] I should note that reverting back to the original drivers works fine with a Hawking HUF11 or Belkin F5D5050 USB 1.1 adapter.
    Last edited by wbgolden; 06-29-2005 at 12:39 AM. Reason: added attachment
    Imagine what I could do with a Cowboy HatCam

  11. #26
    Join Date
    Aug 2004
    Posts
    4,087
    Quote Originally Posted by wbgolden
    Serial console is all set up and working like a champ (man, I'm really glad I finally took this step...). I got to the bare bash and insmod'ed the drivers. Then I was unsure of what to do, so I set the rc.sysinit file back the way it was before. Thought I probably needed to set up network configs but wasn't really sure (or confident) in what to do.
    The basic idea is to insmod the modules, ifconfig the interface, and start testing. It can be useful to mount /proc and /tmp first. Without /tmp, you have no place to put files.
    Code:
    mount -o /var
    mount -t proc proc /proc
    insmod /lib/modules/usbcore.o
    insmod /lib/modules/usbnet.o
    ifconfig eth0 192.168.1.200 netmask 255.255.255.0    # substitute your tivo  IP here
    ping 192.168.1.100                                   # subtitute your pc IP here
    netperf -H 192.168.1.100 -C -c -- -m 131072          # netperf test to your PC running netserver
    You can startup up tivoftpd and transfer files if you want/need to.
    I'm thinking that at this point, I need to bone up more on Linux commands. To tell the (brutal) truth, right now I feel like a total noob who's well-read on DDB (many months) but is still missing some really important aspects. Maybe I'm just better at lurking and waiting for answers... :
    We're on the bleeding edge here. I don't mind pointing you in the right direction once in a while, but if you're getting frustrated, let it go for now and the device support will no doubt get smoother downstream.
    Nonetheless, I have attached my boot log from the last reboot. Hey, at least I'm trying, right? There's a bunch of "Inode" alerts, but I figure I'll cross that bridge at another time.
    Looks like you didn't attach the log. Sounds like the inode alerts are normal e2fsck warnings when the /var file system is repaired after an unclean shutdown. These are par for the course with an unjournalled file system.

  12. #27
    Join Date
    Nov 2004
    Posts
    10
    Quote Originally Posted by Jamie
    We're on the bleeding edge here. I don't mind pointing you in the right direction once in a while, but if you're getting frustrated, let it go for now and the device support will no doubt get smoother downstream.
    I agree. Thanks for your time, Jamie. I will keep a watch on what's happening with the Airlink device(s), but not spend a bunch more of your (et. al) and my time trying to be "the guy that got the ASOHOUSB working with--his--6.2 Directivo"...lol

    [corny]From all I've seen you've done great things on this forum and have been more than patient with people like me. Again, thank you[\corny]

    wbg
    Last edited by wbgolden; 06-29-2005 at 12:47 AM.
    Imagine what I could do with a Cowboy HatCam

  13. #28
    Join Date
    Jun 2004
    Posts
    191
    Jamie, any idea where I should go to look into the hotswap problem?

    And an update to the other stuff. Today my AV receiver for the bedroom came back so when installing it I made some new network cables for that and the tivo. The airlink adapter was disconnected and reconnected, then I started up some transfers. Was I shocked to see transfer rate of 23Mbps!!! And this on a transfer that was saving to a mapped network drive, even with the extra traffic it was fast. Guess I may have a "bad" cable.

  14. #29
    Join Date
    Nov 2003
    Posts
    105
    Not wishing to pull this off thread, but I found that the only way I could get any joy at all with networking on 6.2 was by mimmicking the way 4.x configures the adapters, using the netconfig.tcl script in this thread:

    http://www.dealdatabase.com/forum/sh...t=43375&page=6

    That said, I have read people who did have success, and I think I also read that the insmod and ifconfig need to happen very early on in the boot sequence (hence Alphawolf's 6.2 init configs that run an /etc/rc.runfirst script). That said, this could be merely relating to MRV which is definitely to be discussed in another thread. Sorry if it's a red herring, but it can't hurt to try this perhaps.

  15. #30
    Join Date
    Aug 2004
    Posts
    4,087
    Quote Originally Posted by Jeff D
    Jamie, any idea where I should go to look into the hotswap problem?
    Step 1 would be to learn about how linux hotplug works in general. There's a paper here and a website here.

    Step 2 would be to learn what's different the way TiVo sets things up. The first observation is that /sbin/hotplug is a program rather than a shell script. Is there source available? Not that I know of, but I haven't looked very hard. Without source, you can try to reverse engineer it by treating it as a black box (feed it inputs/env settings and see what it seems to do) and/or disassemble and study the code. You'll find that the /etc/hotplug/usb.map file is referenced from tivoapp, not hotplug. Perhaps routerplus/rpsniff could help understand the IPC.

    I haven't completed these two first steps myself, and as I said, it's not high on my priority list at present, as I can live without hotplugging for now.
    Last edited by Jamie; 06-29-2005 at 03:19 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •