Loading device drivers

I just bought a Freecom DVB-T USB stick that I'm trying to get working
with SuSE 10.0. The drivers are already present in 10.0 and I have also
downloaded the firmware file and put that in the correct place.

When I run lsmod I can see that the drivers are not loaded. When I try
to load the drivers with modprobe I get an error message saying that the
driver files cannot be found. I have confirmed that the drivers are in
the correct directory.

Why can modprobe not find the drivers? What am I doing wrong?

Raymond
(newbie)

Raymond Dalgleish adjusted his/her tinfoil beanie to post:

> I just bought a Freecom DVB-T USB stick that I'm trying to get working
> with SuSE 10.0. The drivers are already present in 10.0 and I have
> also downloaded the firmware file and put that in the correct place.
>
> When I run lsmod I can see that the drivers are not loaded. When I try
> to load the drivers with modprobe I get an error message saying that
> the driver files cannot be found. I have confirmed that the drivers
> are in the correct directory.
>
> Why can modprobe not find the drivers? What am I doing wrong?
>
> Raymond
> (newbie)


Hi Raymond,

Can you see any messages in /var/log/messages when you plug the thing
in?

You can monitor this in real time by pressing Ctrl+Alt+F10 and watching
the console output Alt+F7 should get you back to the GUI.

Or if running KDE then have kwatch ( in the System>Monitor>Kwatch menu )
and set it up to monitor the /var/log/messages and watch that to see if
anything is printed when you plug it in.

The module ( dvb-usb-dtt200u ) should be automatically loaded on plugin
as far as I can gather from the kernel docs, that is if the stick uses
that chipset, some manufacturers change the internal chips but not the
model name and so maybe it does not use that module?

Post the messages here if you are stuck so we can see what is happening,
keep it short please to save confusion :-)

HTH

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:
> Raymond Dalgleish adjusted his/her tinfoil beanie to post:
>
>
>>I just bought a Freecom DVB-T USB stick that I'm trying to get working
>>with SuSE 10.0. The drivers are already present in 10.0 and I have
>>also downloaded the firmware file and put that in the correct place.
>>
>>When I run lsmod I can see that the drivers are not loaded. When I try
>>to load the drivers with modprobe I get an error message saying that
>>the driver files cannot be found. I have confirmed that the drivers
>>are in the correct directory.
>>
>>Why can modprobe not find the drivers? What am I doing wrong?
>>
>>Raymond
>>(newbie)
>
>
>
> Hi Raymond,
>
> Can you see any messages in /var/log/messages when you plug the thing
> in?
>
> You can monitor this in real time by pressing Ctrl+Alt+F10 and watching
> the console output Alt+F7 should get you back to the GUI.
>
> Or if running KDE then have kwatch ( in the System>Monitor>Kwatch menu )
> and set it up to monitor the /var/log/messages and watch that to see if
> anything is printed when you plug it in.
>
> The module ( dvb-usb-dtt200u ) should be automatically loaded on plugin
> as far as I can gather from the kernel docs, that is if the stick uses
> that chipset, some manufacturers change the internal chips but not the
> model name and so maybe it does not use that module?
>
> Post the messages here if you are stuck so we can see what is happening,
> keep it short please to save confusion :-)
>
> HTH
>

Hi,

kwatch recorded the following when I plugged and un-plugged the TV stick:

---------------[/var/log/messages]---------------
Mar 13 20:28:57 linux kernel: usb 1-3: new high speed USB device using
ehci_hcd and address 4
Mar 13 20:29:13 linux kernel: usb 1-3: USB disconnect, address 4

As you can see, the device was detected but that did not trigger
anything else to happen.

Thanks,

Raymond

Raymond Dalgleish adjusted his/her tinfoil beanie to post:


> Hi,
>
> kwatch recorded the following when I plugged and un-plugged the TV
> stick:
>
> ---------------[/var/log/messages]---------------
> Mar 13 20:28:57 linux kernel: usb 1-3: new high speed USB device using
> ehci_hcd and address 4
> Mar 13 20:29:13 linux kernel: usb 1-3: USB disconnect, address 4
>
> As you can see, the device was detected but that did not trigger
> anything else to happen.

Look like it either does not recognise the device or the device does not
report what it is and so cannot load the correct modules.

I wonder if this is covered on the DVB website.

I will try and grab a spare 5 mins to have a look if there is anything
special needed for that stick.

Watch this space, though it might not be till the morning now.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise wrote:

> Raymond Dalgleish adjusted his/her tinfoil beanie to post:
>
>
>> Hi,
>>
>> kwatch recorded the following when I plugged and un-plugged the TV
>> stick:
>>
>> ---------------[/var/log/messages]---------------
>> Mar 13 20:28:57 linux kernel: usb 1-3: new high speed USB device using
>> ehci_hcd and address 4
>> Mar 13 20:29:13 linux kernel: usb 1-3: USB disconnect, address 4
>>
>> As you can see, the device was detected but that did not trigger
>> anything else to happen.
>
> Look like it either does not recognise the device or the device does not
> report what it is and so cannot load the correct modules.
>
> I wonder if this is covered on the DVB website.
>
> I will try and grab a spare 5 mins to have a look if there is anything
> special needed for that stick.
>
> Watch this space, though it might not be till the morning now.
>
hi I check up your device at dvb forum were i mod at. in windows it is a
bda device which is not even very well supported in the windows enviroment
perhaps MT or progdvb or DVBViewer would support it..( other then the
original software) as it goes there no mention of it working in linux.. the
only usb dvb device I know that worked was ss2 bcb2 chipsets and maybe the
twinhan..
i think this is your device
1. DibCom DIB3000-P (Demodulater / TS-to-USB)
2. Microtune MT2060 (broadband tuner)
3. Cypress CY7C68013A "FX 2" (USB microcontroller)

you could try a google search on these you might find a hidden linux module
somewhere..

sash wrote:

> baskitcaise wrote:
>
>> Raymond Dalgleish adjusted his/her tinfoil beanie to post:
>>
>>
>>> Hi,
>>>
>>> kwatch recorded the following when I plugged and un-plugged the TV
>>> stick:
>>>
>>> ---------------[/var/log/messages]---------------
>>> Mar 13 20:28:57 linux kernel: usb 1-3: new high speed USB device using
>>> ehci_hcd and address 4
>>> Mar 13 20:29:13 linux kernel: usb 1-3: USB disconnect, address 4
>>>
>>> As you can see, the device was detected but that did not trigger
>>> anything else to happen.
>>
>> Look like it either does not recognise the device or the device does not
>> report what it is and so cannot load the correct modules.
>>
>> I wonder if this is covered on the DVB website.
>>
>> I will try and grab a spare 5 mins to have a look if there is anything
>> special needed for that stick.
>>
>> Watch this space, though it might not be till the morning now.
>>
> hi I check up your device at dvb forum were i mod at. in windows it is a
> bda device which is not even very well supported in the windows enviroment
> perhaps MT or progdvb or DVBViewer would support it..( other then the
> original software) as it goes there no mention of it working in linux..
> the
> only usb dvb device I know that worked was ss2 bcb2 chipsets and maybe
> the twinhan..
> i think this is your device
> 1. DibCom DIB3000-P (Demodulater / TS-to-USB)
> 2. Microtune MT2060 (broadband tuner)
> 3. Cypress CY7C68013A "FX 2" (USB microcontroller)
>
> you could try a google search on these you might find a hidden linux
> module somewhere..


here a listing for it perhaps it is working now but you probably need to
install the module for it..

http://www.livingroomlinux.com/wiki/index.php/DVB_USB

>
> here a listing for it perhaps it is working now but you probably need to
> install the module for it..
>
> http://www.livingroomlinux.com/wiki/index.php/DVB_USB

http://www.acaciaclose.co.uk/16253/?...ession*id*val*

here another usefull link perhaps you seen it..

sash adjusted his/her tinfoil beanie to post:

> hi I check up your device at dvb forum were i mod at.

Sash,

Thanks very much for the info, any chance of a link to your groups
please?

Will be added to my ever expanding list of "things to do, sites to look
at" :-)


--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

sash wrote:
>>here a listing for it perhaps it is working now but you probably need to
>>install the module for it..
>>
>>http://www.livingroomlinux.com/wiki/index.php/DVB_USB
>
>
> http://www.acaciaclose.co.uk/16253/?...ession*id*val*
>
> here another usefull link perhaps you seen it..
>
>
Hi sash,

Thanks for the links. I had already checked these out and the Freecom
stick is actually covered in section 2.9 of the first of the links that
you supplied.

I actually bought this stick because of the recommendation on Mike
Choy's excellent "Acacia Close" site - your second link. He has the
thing running successfully under SuSE 10.0. I have been in touch with
him and he has suggested that I run the stick from a powered hub rather
than directly from a USB port. He thinks that it might be a power issue.
I'll give it a try this evening and report back tomorrow.

Raymond

Raymond Dalgleish adjusted his/her tinfoil beanie to post:

> Hi sash,
>
> Thanks for the links. I had already checked these out and the Freecom
> stick is actually covered in section 2.9 of the first of the links
> that you supplied.
>
> I actually bought this stick because of the recommendation on Mike
> Choy's excellent "Acacia Close" site - your second link. He has the
> thing running successfully under SuSE 10.0. I have been in touch with
> him and he has suggested that I run the stick from a powered hub
> rather than directly from a USB port. He thinks that it might be a
> power issue. I'll give it a try this evening and report back tomorrow.

Ah never thought of that one, I have a similar problem here with my USB
you can sometimes get messages in the logs if the power is low as well
( but not always )

I have a stupid small USB Lava Lamp someone bought me for Xmas and when
I had that in the computer port ( it takes its power from the USB
obviously ) my camera would not get recognised or would throw errors.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp