From: JPT <j-p-t@gmx.net>
To: linux-media@vger.kernel.org
Subject: Running Technisat DVB-S2 on ARM-NAS
Date: Sun, 21 Sep 2014 16:26:30 +0200 [thread overview]
Message-ID: <541EE016.9030504@gmx.net> (raw)
Hi,
I want to turn my Netgear ReadyNAS RN104 into a VDR.
I already run a self made kernel 3.16.3) and plain debian on it.
For hardware and software details see http://natisbad.org/NAS3/
I recently compiled those DVB modules into the kernel.
And after a lot of struggle to get a clean build, I succeeded in loading
the modules:
dvb_usb_technisat_usb2, dvb_usb, dvb_core, stv090x, rc_core
but device recognition somehow does not fully work.
usb 2-1: new high-speed USB device number 3 using xhci_hcd
usb 2-1: New USB device found, idVendor=14f7, idProduct=0500
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: TechniSat USB device
usb 2-1: Manufacturer: TechniSat Digital
usb 2-1: SerialNumber: ************
technisat-usb2: set alternate setting
technisat-usb2: firmware version: 17.63
dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) error while loading driver
(-12)
usbcore: registered new interface driver dvb_usb_technisat_usb2
How my I find out more about the error -12? It's a lot of wrapped
"return ret" in the code...
Is there any way of enabling more logging?
I believe it comes from the dvb-usb-technisat-usb2 module, but there is
no c file?
thanks.
Jan
next reply other threads:[~2014-09-21 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 14:26 JPT [this message]
2014-09-21 14:38 ` Running Technisat DVB-S2 on ARM-NAS Antti Palosaari
2014-09-21 15:10 ` JPT
2014-09-21 15:28 ` Antti Palosaari
2014-09-21 17:28 ` JPT
2014-09-21 20:45 ` Jannis
2014-09-22 8:26 ` Jan Tisje
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541EE016.9030504@gmx.net \
--to=j-p-t@gmx.net \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.