LinHES Forums
http://forum.linhes.org/

DVB USB failing to find firmware since CPU upgrade: FIXED
http://forum.linhes.org/viewtopic.php?f=2&t=14297		 Page 1 of 1
Author:  turpie [ Tue Feb 20, 2007 4:24 pm ]
Post subject:  DVB USB failing to find firmware since CPU upgrade: FIXED
My system has just started having a problem loading the modules for my USB DVB tuners. In dmeg the kernel says something about the tuners being in a 'cold state' and needing to load firmware, but it claims it cant find the firmware. The stupid part is that if I unplug and reinsert the tuners then the kernel reloads them correctly.

The only change I have made to the system is swapping the CPU from a single core AthlonXP 3200+ to a dual core AthlonXP 3800+.

Do I need to swap back?
Or is there a tweak that will get things working again?
Author:  turpie [ Tue Feb 20, 2007 5:55 pm ]
Post subject: 
I should make it clear that these tuners have been working great for months.

Also I upgraded the RAM to 1GB from 512MB the day before, but it worked fine that night.
Author:  turpie [ Wed Feb 21, 2007 9:05 pm ]
Post subject: 
I'd really rather not have to try swapping processors again, but could that really be the problem?
Author:  bruce_s01 [ Thu Feb 22, 2007 4:04 am ]
Post subject: 
It might be worthwhile trying out reducing your memory down to the the original to test.
I'm not saying this is actually the problem, it could be because of the devices being a bit slow, so the faster processor is too quick for it.
Are you running through a USB hub? Are they both connected to USB 2.0 ports?

Bruce S.
Author:  turpie [ Thu Feb 22, 2007 4:33 pm ]
Post subject: 
bruce_s01 wrote:
It might be worthwhile trying out reducing your memory down to the the original to test.
I'm not saying this is actually the problem, it could be because of the devices being a bit slow, so the faster processor is too quick for it.
Are you running through a USB hub? Are they both connected to USB 2.0 ports?

Bruce S.

Thanks for replying Bruce, its nice to know somebody cares. :lol:

For the time being I have swapped back to the original RAM and CPU configuration. I will be away this weekend and didn't want to destroy any of the WAF that I've built up . :wink:

Also, while flipping through the BIOS settings again (due to the cpu change) I remembered that I had turned on "AMD Liveâ„¢" so I turned that off as well.

With everything changed back it is now working again. When I get time next week I will try a more scientific diagnosis.
Author:  turpie [ Thu Feb 22, 2007 4:46 pm ]
Post subject: 
bruce_s01 wrote:
I'm not saying this is actually the problem, it could be because of the devices being a bit slow, so the faster processor is too quick for it.
Are you running through a USB hub? Are they both connected to USB 2.0 ports?

I have all four tuners connected to the rear usb ports. I had wondered if the boot process might be quicker and wasn't giving the tuners enough time to 'wake up' before the drivers were loaded.
Do you think a hub might add a slight initialisation delay?

Could I move those drivers to later in the boot process? & How?
Author:  bruce_s01 [ Thu Feb 22, 2007 9:49 pm ]
Post subject: 
Quote:
Do you think a hub might add a slight initialisation delay?

Possibly, but I'm just guessing here. It may help initialisation, but I don't know how it would affect usage when actually capturing.

As you said in your previous reply, a more scientific approach to the changes may help. That's the problem with a working system, you don't want to have it down for too long and so do all the changes at once. :)

Bruce S.
Author:  turpie [ Thu Mar 01, 2007 4:36 pm ]
Post subject: 
I have finally got back to this.

Earlier in the week I put the extra stick of RAM in, with no negative effects.

This morning I swapped the CPU again (AthlonXP 3200+ to a dual core AthlonXP 3800+) and the firmware problem returned. This time I wasn't using the "AMD Live!" option in the BIOS which I had hoped was the problem.

Not wanting to downgrade the CPU again I played around with the modules and found that if removed the driver and then reloaded it it would fix the firmware issue.

So I have added the following commands to the end of my /etc/init.d/bootmisc.sh files:
Code:
rmmod dvb-usb-vp7045
modprobe dvb-usb-vp7045

I dont know if this is the best way to do this, but it works for now. If anyone knows the "proper" way please reply.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/