[linux-dvb] Re: Nova-t 500 simple loading problem

Jeffrey Borg jeffrey at borgs.net
Sun Feb 4 22:10:31 CET 2007


Hi,

Everything related to dvb are all modules. The firmware is in the 
/ partation. Which is mounted & accessable at bootime. The other card 
requires firmware and it loads correctly (saa7134 based card)

Jeffrey

On Thu, 1 Feb 2007, Eduard Huguet wrote:

> Hmmm... The firmware not found problem clearly suggest that the partition
> containing the file it it's not mounted when the card is initialized. ¿Are
> you sure that those modules are really compiled as modules and not included
> embedded into the kernel?
>
> The firmware files are usually contained in /lib/firmware (at least, in my
> Sabayon/Gentoo box). ¿Maybe in yours the firmware are on any partition that
> for any unknown reason is mounted later? Check dmesg to see if the card is
> initialized before disks are mounted.
>
> Cheers
> Eduard
>
>
>
>
>
> 2007/1/31, Jeffrey Borg <jeffrey at borgs.net>:
>> 
>> 
>> This is thi initial load
>> 
>> Jan 30 20:47:29 tux2 dib0700: loaded with support for 2 different
>> device-types
>> Jan 30 20:47:29 tux2 dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
>> cold state, will try to load a firmware
>> Jan 30 20:47:29 tux2 dvb-usb: did not find the firmware file.
>> (dvb-usb-dib0700-01.fw) Please see linux/Documentation/dvb/ for more
>> details on firmware-problems.
>> (-2)
>> 
>> 
>> a liile while later (I did the modprobe manually)
>> Jan 30 20:49:39 tux2 usbcore: deregistering interface driver
>> dvb_usb_dib0700
>> Jan 30 20:49:44 tux2 dib0700: loaded with support for 2 different
>> device-types
>> Jan 30 20:49:45 tux2 dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
>> cold state, will try to load a firmware
>> Jan 30 20:49:45 tux2 dvb-usb: downloading firmware from file
>> 'dvb-usb-dib0700-01.fw'
>> Jan 30 20:49:45 tux2 dib0700: firmware started successfully.
>> Jan 30 20:49:45 tux2 dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
>> warm state.
>> Jan 30 20:49:45 tux2 **WARNING** I2C adapter driver [Hauppauge Nova-T 500
>> Dual DVB-T] forgot to specify physical device; fix it!
>> Jan 30 20:49:45 tux2 dvb-usb: will pass the complete MPEG2 transport
>> stream to the software demuxer.
>> Jan 30 20:49:45 tux2 DVB: registering new adapter (Hauppauge Nova-T 500
>> Dual DVB-T).
>> Jan 30 20:49:45 tux2 **WARNING** I2C adapter driver [DiBX000 tuner I2C
>> bus] forgot to specify physical device; fix it!
>> Jan 30 20:49:45 tux2 DVB: registering frontend 1 (DiBcom 3000MC/P)...
>> Jan 30 20:49:45 tux2 MT2060: successfully identified (IF1 = 1220)
>> Jan 30 20:49:46 tux2 dvb-usb: will pass the complete MPEG2 transport
>> stream to the software demuxer.
>> Jan 30 20:49:46 tux2 DVB: registering new adapter (Hauppauge Nova-T 500
>> Dual DVB-T).
>> Jan 30 20:49:46 tux2 **WARNING** I2C adapter driver [DiBX000 tuner I2C
>> bus] forgot to specify physical device; fix it!
>> Jan 30 20:49:46 tux2 DVB: registering frontend 2 (DiBcom 3000MC/P)...
>> Jan 30 20:49:46 tux2 MT2060: successfully identified (IF1 = 1220)
>> Jan 30 20:49:46 tux2 dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
>> initialized and connected.
>> Jan 30 20:49:46 tux2 usbcore: registered new interface driver
>> dvb_usb_dib0700
>> 
>> 
>> I am still not 100% sure why the frimware is found on the 2nd loading.
>> 
>> Jeffrey
>> 
>> 
>> On Wed, 31 Jan 2007, Eduard Huguet wrote:
>> 
>> > Ok, then I have no idea why you get this error first time. Try to post
>> your
>> > dmesg file, maybe it can help.
>> >
>> > Cheers
>> > Eduard
>> >
>> >
>> >
>> >
>> > 2007/1/31, Jeffrey Borg <jeffrey at borgs.net>:
>> >>
>> >> Hi
>> >>
>> >> Everything is a module for the dvb stuff, even the other card needs
>> >> firmware. Just that this one dosen't initalize the first time.
>> >>
>> >> Jeffrey
>> >>
>> >> On Wed, 31 Jan 2007, Eduard Huguet wrote:
>> >>
>> >> > Hi,
>> >> >   ¿Do you compile the driver for the card as a module? Make sure you
>> do,
>> >> > because that card needs the firmware to be loaded, and if the driver
>> is
>> >> > compiled inside the kernel (not as a module) then it initializes too
>> >> early
>> >> > (before file systems are mounted) and it won't find the firmware
>> file.
>> >> >
>> >> > Cheers
>> >> >
>> >>
>> >
>> 
>


More information about the linux-dvb mailing list