6.2 & USB 2.0 upgrade

[gschaefer]

Thanks to all the posts on here I've successfully got 2 Hughesh S2 DTivo's up and running on 6.2!!!

Here's most of what has been done to date:

upgraded to 6.2 via slices
added busybox tools for telnet, ftp
disabled netfilter to disable the filtering so I can telnet/ftp in
applied buffer hack to 60 minutes
installed TivoWebPlus Project - v1.1-pre2 w/ various .itcl/.tcl fixes to work with 6.2 better
superpatch-67all-NutKase-1.0 to enable HMO/MRV
set_mrv_name_67 to set unique DTivo names

My question is how do I upgrade from USB 1.1 to USB 2.0 to get better MRV performance? :)

[mateom199]

Well, I'm glad you made it that far without posting or asking any questions, you must have read and done your homework.

That said, please search, I'm sure you'll find the answer.
Hint: "Jamie's backported"

BTW, this really belonged in Newbie

[gschaefer]

yeah, that _now_ seems like a better place to post! I'm such a newbie I never saw the newbie section! Someone can delete or move this if that makes it better.

Thanks agian, about to try the 'Jamie's backported' suggestion! Hope I have good results! :)

:x

[Rich04]

Call me ignorant, but I used the kernel from ptvupgrade to update my Dtivo to 6.2 hacked. What kernel version of the usbcore.o should I be using? Sorry for the stupid question, but I can't seem to find it anywhere.

Rich

[94SupraTT]

My question is how do I upgrade from USB 1.1 to USB 2.0 to get better MRV performance? :)


- back up /lib/modules to somewhere safe
- delete ax8817x.o, usbcore.o, usb-ohci.o, and (if it exists) ehci-hcd.o
- copy in the new modules: usbcore.o, usb-ohci.o, and usbnet.o
- symlink usbnet.o to ax8817x.o

According to the following thread that process should work fine.

http://www.dealdatabase.com/forum/showthread.php?t=42997&highlight=6.2+usb2.0

[Rich04]

I grabbed the alldeadhomiez version and patched them with Jamie's patch. I found the usbcore.o I need in the usb-2.4.27/host/obj/hosts/2.4.20_Series2/ directory (I think). Where do I find the correct corresponding usbnet.o and usb-ohci.o. I am completely lost on how to install these. Please help! I've read the readme and am now more confused.

-Rich

[Greubin]

I grabbed the alldeadhomiez version and patched them with Jamie's patch. I found the usbcore.o I need in the usb-2.4.27/host/obj/hosts/2.4.20_Series2/ directory (I think). Where do I find the correct corresponding usbnet.o and usb-ohci.o. I am completely lost on how to install these. Please help! I've read the readme and am now more confused.

-Rich

MFS soapbox derby (http://www.dealdatabase.com/forum/showthread.php?t=39328&highlight=soapbox+derby)

[ZooMigo]

According to the following thread that process should work fine.

http://www.dealdatabase.com/forum/showthread.php?t=42997&highlight=6.2+usb2.0

Tried it today, totally hosed my system, back to square 1.

Good thing is, I make great notes on exactly how I got far enough along to try and get the new drivers installed, so it shouldn't be hard to get it back to that point. I guess the lesson learnt was to make a backup of the hacked drive next time before I try and add that next hack.

Kevin

BTW, I suspect the main reason for failure was that I had the wrong set of files for my system. I used the 3.1.5 kernel, but not sure how to figure out which version (I used 2.4.4) of the drivers to install.

[94SupraTT]

Tried it today, totally hosed my system, back to square 1.

Good thing is, I make great notes on exactly how I got far enough along to try and get the new drivers installed, so it shouldn't be hard to get it back to that point. I guess the lesson learnt was to make a backup of the hacked drive next time before I try and add that next hack.

Kevin

BTW, I suspect the main reason for failure was that I had the wrong set of files for my system. I used the 3.1.5 kernel, but not sure how to figure out which version (I used 2.4.4) of the drivers to install.

You did the following?


- back up /lib/modules to somewhere safe
- delete ax8817x.o, usbcore.o, usb-ohci.o, and (if it exists) ehci-hcd.o
- copy in the new modules: usbcore.o, usb-ohci.o, and usbnet.o
- symlink usbnet.o to ax8817x.o

If so the old files should be backed up. All you would have to do is put them back in /lib/modules and you should be fine. Of course if you lost network connectivity you would need to pull the drive to do so.

Did you overwrite the existing files? If so, thats not good.

[ZooMigo]

yeah, I tried it this way -

make a directory called bkup at /lib/modules/bkup
copied the old versions in with cp xxxx
fired up an ftp client
deleted the old versions from /lib/modules
copied in the new ones with the ftp client
edited my .author file
sent a reboot command

thats when the troubles started. the tivo rebooted just fine, but my network connector died. no lights or anything (FA-120). So I pulled the drive, put it in my computer and checked to make sure I had all the right files in the right places and checked my .author file again.

Put the drive back in the tivo and same deal, no network adapter. So pull it back out to undo the change. deleted the new files, copied the old ones back from /bkup and edited author to remove the insmod commands. Put it back in the tivo and its stuck at "powering up". Let it sit for about an hour and still stuck. Pull it back out one more time, check everything again on the pc, power it back up and still stuck at "powering up".

Mind you, everything was working fine before I tried to load the new drivers. I used the AW 6.2 small for the clean install onto a backup (new) drive. Loaded a hacked 3.1.5 kernel with killinit, loaded the mrv thing from deadhomiez, found a compatible version of tserver (the one I used with 3.1.1 gave me timezone errors).

The only weird thing it was doing before I tried loading new drivers was this: when I pulled a recording over with tytools the last little bit would be a random chunk of video from a previous recording. It looked like what was happening was that tytools wanted info beyond the end of the recording so tserver just sent whatever was on the drive regardless of whether it belonged to the program or not. No big deal, I just edited the weirdness off. Guess I need to read up on end padding.

Oh, and I guess the whole point is, with my 3.1.1 system (sleepered) I was getting 2.8-3.6 mpbs transfer speeds. With the 6.2 system I had speeds around 800kbps. Good thing is I have been experimenting with 6.2 on a separate drive from my system drive so even though I killed the tivo all I had to do was put the old drive back in and it was up and running.

Kevin

[gschaefer]

This was my SECOND attempt in getting USB 2.0 up and running. So now I did it again, after the restart, no USB 2.0 AND no USB 1.1!!! Next, I get to yank out the drive and restore the /lib/modules/ to undo the damage and hope that works. Though all this yanking the drives in and out really isn't my favorite thing anymore! I need an external drive already at the pace I seem to be going!

Has ANYBODY gotten USB 2.0 up and running under 6.2?! Maybe it's not even possible? All the write ups seem to be for 4.x systems, which I'm cautious to apply--not knowing if something horrid will result. Thankfully my DTivo is operational, just no net connectivity at present. Soon to be resolved! Even if I have to get back to 800kbps! :)

[shawn]

Yes, USB 2.0 works under 6.2.

[Jamie]

Yes, usb2 backport drivers work fine on 6.2 and 7.1b.

Get a serial cable and setup serial console access. Once you have that, there's little reason to pull the drive anymore. Without this, debugging is nearly impossible.

Learn what linux kernel version you have (hint: "uname -r"). Its important that you install modules that match your kernel version.

If you are using HMO/MRV on 6.2, read up on the network configuration issues that apply.

[Rich04]

I'm having the exact same issues as gschaefer, and I am still not having any luck. I have followed the steps given in this thread to a t, and nothing has worked. As I stated before I grabbed the drivers, patched them, and have been trying to figure out which of the files from this version to help. Thanks for the support.

Rich

[willard322]

....BTW, I suspect the main reason for failure was that I had the wrong set of files for my system. I used the 3.1.5 kernel, but not sure how to figure out which version (I used 2.4.4) of the drivers to install.I think I saw that for 6.2 you need to use version 2.4.20. But I may be wrong.

[stevel]

2.4.20 is correct for 6.2.

I was unsure if I could do this swap "live", so I pulled the disk to do it. Worked fine.

[rbautch]

I suspect some of these problems may be caused by an incorrect symlink. Try this command from within the /lib/modules directory: ln -s usbnet.o ax8817x.o then check to see that it actually created an ax881x.o "file". If you don't see this entry, your FA120 will definitely not work.

[ZooMigo]

Thx for the help in this thread. My next day I will have enuf time to play with the new drive is Tuesday, so I'll report back what I find after that.

Kevin

[johnsolo]

Why is everyone pulling their drives? I only own a S2 SA, and I have a serial port on my unit, maybe DTV Tivos don't have those? When I had problems updating network drivers, I used the serial connection to copy things back. Anyways just my 2c

[cheer]

Why is everyone pulling their drives? I only own a S2 SA, and I have a serial port on my unit, maybe DTV Tivos don't have those? When I had problems updating network drivers, I used the serial connection to copy things back. Anyways just my 2c
Yes, we have console ports, but the DTivo doesn't come with a console cable and many folks don't make or buy one.

Tsk, tsk.

[Lord-dogbert]

Don't pull your drives guys. For like 8 bucks at rat shack you can get the parts in this link and make a cable.

http://www.dellanave.com/projects/tivo/tivocable.html

[ZooMigo]

OK, Tuesday has come and gone, so here is the update I promised you guys.

First thing, I got my sh*t together and burnt everything I need to do a clean install/hack onto a single CD. Then I copied all that junk onto a spare drive I had laying around just in case I needed to make changes (I did). Then I set about writing a bunch of scripts to cover me in case I messed up. The first script just copied the 62small onto a bare drive, second script installed hacks and files. Script 3 and 4 were a do/undo pair. First one installed the usb backport drivers, 2nd one uninstalled. With all this stuff written, I started in on a new drive.

Installed 6.2 and pulled. Made the phone call to get it up and working. Put the drive back in the pc and backed it up. This would save a step in the future if I goobered up. Ran the first hack script (installed basic networking, decryption, hmo/mrv, copied over the custom .author, hacked 3.1.5 kernel, etc.). put the drive back in and run the superpatch tcl scripts. Happiness so far. Try to copy a file over the network and running around 0.7 Mbps. One more time into the PC to install the backport drivers and then back into the TiVo and my network speed is now around 1.6 Mbps. Not like the 2.5-3 I had with 3.1.1, but I suppose I can live with it for now.

Next step is to save all the scripts I wrote off to a CD in case of disaster. Nice thing is, the last time I did the process, it took just about an hour including moving the drive twice and doing the setup call. My point? Yeah, the backport drivers work with 6.2. Now to just figure out how to make them faster.

Kevin

[isdnmatt]

I was also successful in getting the backported drivers up and running. Just replaced the modules and symlinked as mentioned above. Worked like a charm.

However, I can only sustain downloads of 1.7mb/s using tytools. What am I missing to get up to the 2.5-3 mb/s range? It's not too big of a problem since its more than double the original speed (.73mb/s) and I let it extract overnight.

[bengalfreak]

Don't pull your drives guys. For like 8 bucks at rat shack you can get the parts in this link and make a cable.

http://www.dellanave.com/projects/tivo/tivocable.html

Why do that when for $10 you cab get the cable already assembled from PTV?

[alfa66]

I 've just performed the upgrade, the unit (DSR7000) came up fine :cool:

However I did not see any speed improvement in tytool, I get 0.7Mb/s just like before :(

Any idea ?

Is it possible that the superpatch_67 slows things down?

alfa66

DSR7000:
- msf tools 2.0 (bigger drive)
- ptvupgrade (networking, ftp, telnet)
- superpatch_67 (this works great with tytool, haven't tried HMO yet)

[bnm81002]

Why do that when for $10 you cab get the cable already assembled from PTV?



where did you see that, I checked ptvupgrade and didn't see any null modem serial cable for $10?

[dave4089]

I think I saw that for 6.2 you need to use version 2.4.20. But I may be wrong.

I recently got these drivers working with 6.2 on my Philips DSR704. My network adapter is a Linksys UBS200M. You definitely want the 2.4.20 version with 6.2.

Dave

[isdnmatt]

Any new developments on breaking the 1.5-6mb/s barrier? It is a great improvement over the stock drivers, but what is holding it back from higher transfer speeds?

[shawn]

I get 2.8 meg/sec on 6.2 with FA120

[isdnmatt]

Please share how you got to that point? I also have a FA120 and 6.2, but can only accomplish 1.7mb/sec.

Matt

[shawn]

pull the access card and put the Tivo to standby, i go from about 1.7 to as high as 2.8. Im sure others are getting faster then that.
This is thru Tytools
Its been a while since setup but it was one of the versions of tserver out there and Jamies updated USB drivers only.

[kfcrary]

Any idea why pulling the access card helps?

[Jamie]

Any idea why pulling the access card helps?I assume it stops the tuners from capturing to the live buffer. But standby on a DTivo does that too, IIRC. Does pulling the access card result in better network performance than standby? On a SA, we tune to a dead channel to get a slight performance improvement, but it doesn't seem to be as big an effect.

[isdnmatt]

I get no difference in transfer when the tivo is in standby. I'll have to try pulling the card next.

[dantes]

Just wondering...

After symlinking with the ln -s usbnet.o ax8817x.o command up above i noticed it sticks the shortcut in /var/tmp

do i have to move it at all ?

[eastwind]

Just wondering...

After symlinking with the ln -s usbnet.o ax8817x.o command up above i noticed it sticks the shortcut in /var/tmp

do i have to move it at all ?
You need to ln from /lib/modules/usbnet.o (or wherever you put the backported driver) to /lib/modules/ax8817x.o. For instance:
mount -o remount,rw /
cd /lib/modules
mkdir orig
mv ax8817x.o orig
ln -s /path/to/backported/usbnet.o ax8817x.o
mount -o remount,ro /
Since I was in /lib/modules, the link is created there.

ew

[cyklfreak]

ok, this is killing me!!!

First off I spent 2 days trying to get a serial cable to work and couldn't!! so I cant give the log!!

I have done everything that has been suggested at least 30 times and I still can't get the drivers to work!!

they will work on my cheap adapter but not on my airlink ax88772 chip. I really dont know what I am doing wrong.

when I plug in the adapter only 1 light comes on( link light comes on but power light stays off)

any ideas what I could be doing wrong?

I noticed that there was an All-In-One tivotools released not long ago. I have the previous one loaded, could that be it??

thanks for the help!!!

B

[Jamie]

ok, this is killing me!!!Sigh. You keep posting your usb backport problems in every thread except the usb backport support thread (http://www.dealdatabase.com/forum/showthread.php?t=44114). You really must have a working serial console to debug networking problems. If you are having trouble building a cable, buy one from 9thtee.

[cyklfreak]

you know what is funny, I bought one!

I truly am sorry if I am getting on your nerves but i found something that said that someone added 2 product lines to their /etc/hotplug/usp.map file
quote:

For those that need it...
In the /etc/hotplug/usb.map file you need to add these two lines to the
device ax8817x section:

Code:

product 0b95 7720 Airlink ASOHOUSB
product 0b95 1780 Airlink AGIGAUSB

I did that and I got power!!


I just want this to work !!

Once again, I apologize!!

B

[Jamie]

and I guarantee I did NOT read that in the support thread!!
That's funny, because what you quoted is from post #31 in the support thread.

Glad you got it working, finally.

[cyklfreak]

damn you are fast!!

I tried to edit that before it was read!!

BTW just power not able to connect!!

B