[linux-dvb] problem to load videodev module
hi I'm installing my Hauppauge Nexus-s card on a debian with a 2.4.26 kernel. When i compile the drivers all is right but when I do ./insmod-bt8xx.sh i have this message : caravelle:/usr/src/DVB/build-2.4# ./insmod-bt8xx.sh start Inserting DVB modules into kernelinsmod: videodev.o: No such file or directory insmod: bttv.o: No such file or directory insmod: a module named dvb-core already exists insmod: a module named v4l1-compat already exists insmod: a module named v4l2-common already exists insmod: a module named video-buf already exists insmod: a module named cx24110 already exists ./dst.o: ./dst.o: unresolved symbol bt878_find_by_dvb_adap ./dst.o: ./dst.o: unresolved symbol bt878_device_control ./bt878.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_stop ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_start ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_num ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878 caravelle:/usr/src/DVB/build-2.4# indeed there is no videodev.o in my folder, but i have one in my kernel tree. so i first try to put the one i have in my tree in the build folder : it didn't work, i tried to launch videodev module manualy with modprobe, it did't work... So i don't know what to do now... can someone help me please ? cedric picard -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] [Fwd: Re: Re: Avermedia-dvb-t]
I seem to remember a message here about firmware locations. At one point there were 3 different locations in the codebase, and I think got rationalised down to one: /etc/hotplug Try copying your sc_main.mc into /etc/hotplug. dmesg should show a line from sp887 saying that it got the firmware. My box is down right now, so I can't check. Please correct me if I'm wrong. cheers Andrew Locke wrote: ok, i loaded the mt352 module but i only get an error message. here the dmesg output: i2c_adapter i2c-4: sendbytes: error - bailout. mt352_read_register: readreg error (ret == -14) no success in getting the dvb card to work, because of my patch of dvb-bt8xx, the card is recognized and the devices demux0 dvr0 net0 are created by devfs. but they don't seem to work, cat dvr0 doesn't give any output, maybe because of the missing frontend. maybe someone can help me. cheers -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Avermedia-dvb-t
ok, i loaded the mt352 module but i only get an error message. here the dmesg output: i2c_adapter i2c-4: sendbytes: error - bailout. mt352_read_register: readreg error (ret == -14) no success in getting the dvb card to work, because of my patch of dvb-bt8xx, the card is recognized and the devices demux0 dvr0 net0 are created by devfs. but they don't seem to work, cat dvr0 doesn't give any output, maybe because of the missing frontend. maybe someone can help me. cheers -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: driver for VP7041 VisionDTV Twinhan USB DVB-T
Patrick Boettcher wrote: Hi list, I recently bought a VP7041 and was asking on the mailing list, if someone has a working driver or works on one. (http://www.linuxtv.org/mailinglists/linux-dvb/2004/05-2004/msg00223.html) Since I didn't receive an answer, I started to have a look. sorry for me not being responsive WRT your first mail. i made the first mail about this usb adapter, but, then, i just had the time to check that i could get the dump of the USB transaction using those usb sniffer.. the same info it seems your are using to proceed with the protocol analysis! cheer to you! [...] When I'll have the driver ready for real tests, I wonder if it is possible to add it to cvs to reach a wider user community. Or is there another method to do so? actually i'd like to help this effort with some test but our usb adapter is used as a field test device for DVB-T signal availability here in nothern-east of italy, so it's not always in my pocket to maybe test verify your protocol-related question.. hope to see this kind of driver on a cvs. BTW i'm wondering if this kind of usb driver could be completely an user space application because it's based on best-effort usb transaction (dont remember the exact term in usb terminology; not synchronous, i mean) and i remember there are already user space application acting like driver for other usb adapter. this way, an alpha-state driver should be less of a pain WRT crashing the running kernel! bye -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: kernel panic when removing module while IR is active
Markus Wiesner wrote:
I hope this is new, at least I could not find something related via
Google ... (a search in the linuxtv.org archive always returned No
matches no matter what I was looking for?!)
I'm using the onboard IR-receiver (J2) of a technotrend premium 1.6
dvb-s with the vanilla kernel 2.6.6 dvb-driver.
When the dvb_ttpci module is removed while the ir-receiver is receiving
data i always get following kernel oops (manually copied from screen,
may contain typos ...):
Thanks for doing that work, and sorry that it took me so long to
respond.
I cannot test it now (no IR receiver at hand), but I hope this
is fixed in CVS like so:
diff -u -p -r1.12 av7110_ir.c
--- drivers/media/dvb/ttpci/av7110_ir.c 3 May 2004 16:29:28 - 1.12
+++ drivers/media/dvb/ttpci/av7110_ir.c 26 May 2004 12:43:54 -
@@ -195,6 +195,7 @@ int __init av7110_ir_init(void)
void __exit av7110_ir_exit(void)
{
+ del_timer_sync(keyup_timer);
remove_proc_entry(av7110_ir, NULL);
av7110_unregister_irc_handler(av7110_emit_key);
input_unregister_device(input_dev);
It would be cool if you could report back if that fix works for you.
Regards,
Johannes
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Re: nexus-s+debian unstable+kernel 2.6.6
Great script!
My problem was not with my module loading, I never would have thought
that you have to load firmware to get a card to work...
my problem was the the sysfs.
I read the firmware.txt file in the linux kernel source tree
Documatnation/dvb directory,
and had to manually mount /sys with sysfs,
then I used your script to reload the modules, (which got the firmware
from /usr/lib/hotplug/firmware
and I had previously downloaded that from linuxtv.org's dvb downloads,
after reloading wiht the sysfs in place,
everything worked!
Hope this helps others having the same trouble,
this is really some great stuff!!!
Barry Smoke
Valsecchi Patrick wrote:
Barry,
For kernel 2.6.X, you need to install the module-init-tools Debian package. Regarding your
firmware, you need to download it and put it in /usr/lib/hotplug/firmware/dvb-ttpci-01.fw.
Here is a init script I'm using for loading the drivers (I quit trying to find a way to do it using
aliases):
#!/bin/sh
# /etc/init.d/dvb: start/setup the DVB drivers
set -e
PATH=/bin:/usr/bin:/sbin:/usr/sbin
loadDrivers () {
echo -n Starting the DVB drivers:
/sbin/modprobe dvb-ttpci
/sbin/modprobe stv0299
/sbin/modprobe ves1820
echo .
}
unloadDrivers() {
echo -n Stopping the DVB drivers:
/sbin/rmmod dvb-ttpci 2 /dev/null || true
/sbin/rmmod stv0299 2 /dev/null || true
/sbin/rmmod ves1820 2 /dev/null || true
/sbin/rmmod saa7146 2 /dev/null || true
/sbin/rmmod dvb_core 2 /dev/null || true
/sbin/rmmod saa7146_vv 2 /dev/null || true
/sbin/rmmod v4l1_compat 2 /dev/null || true
/sbin/rmmod v4l2_common 2 /dev/null || true
/sbin/rmmod videodev 2 /dev/null || true
/sbin/rmmod firmware_class 2 /dev/null || true
/sbin/rmmod budget_ci 2 /dev/null || true
/sbin/rmmod budget_core 2 /dev/null || true
/sbin/rmmod dvb_core 2 /dev/null || true
/sbin/rmmod saa7146 2 /dev/null || true
/sbin/rmmod ttpci_eeprom 2 /dev/null || true
echo .
}
case $1 in
start)
loadDrivers
;;
stop)
unloadDrivers
;;
restart)
unloadDrivers
sleep 1
loadDrivers
;;
*)
echo Usage: /etc/init.d/dvb [stop|start|restart]
exit 1
;;
esac
exit 0
After that, a cd /dev; ./MAKEDEV dvb will maybe help.
Good luck ;-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Barry Smoke
Sent: Monday, May 24, 2004 10:45 PM
To: [EMAIL PROTECTED]
Subject: [linux-dvb] nexus-s+debian unstable+kernel 2.6.6
I have a nexus-s(hauppauge wintv nexus-s) SAA7146 rev1 board(so the
dvb-core module states.
I see that the 2.6.6 kernel has dvb drivers in it,
however I am unable to get them loaded, and working.
I do a modprobe dvb-core, and it finds the card, and gives an
error on
loading firmware(is this really needed?)
so, I downloaded the dvb-drivers package, and the dvb-apps
package from
the linuxtv.org site, and extracted it,
I tried to use the insmod.sh script provided for the 2.6 kernel tree,
even though I didn't actually try to patch the kernel with it,
since dirvers are already there
I get a bunch of errors on the script,
and nothing loads...
so my first question, is there a insmod script that goes specifically
for current 2.6.6 kernel?
second, after modprobe dvb-core, I get the card recognized, yet I am
unable to talk to it via the apps package,
I am trying scan, with a -c, to simply scan the current freq/lnb,
and I get no frontend0 found error.
I can find no docs on getting the modules loaded in the right
order with
the right aliases,
the closest I think I came, was by looking at the metzler
brother driver,
and the modules.conf additions they had in wiht the package,
(it seemed to do more),
but, does 2.6.6 even use modules.conf...?
what is the correct way to get this card working, and what is
the best
utility(downloaded from where) to do a quick check of the card.
I have the card connected to echostar7(119), which has NASA
Free To Air,
I get that to show, and I'll be happy!
Barry Smoke
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with
unsubscribe linux-dvb as subject.
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Problem to load vidodev
hi I'm installing my Hauppauge Nexus-s card on a debian with a 2.4.26 kernel. When i compile the drivers all is right but when I do ./insmod-bt8xx.sh i have this message : caravelle:/usr/src/DVB/build-2.4# ./insmod-bt8xx.sh start Inserting DVB modules into kernelinsmod: videodev.o: No such file or directory insmod: bttv.o: No such file or directory insmod: a module named dvb-core already exists insmod: a module named v4l1-compat already exists insmod: a module named v4l2-common already exists insmod: a module named video-buf already exists insmod: a module named cx24110 already exists ./dst.o: ./dst.o: unresolved symbol bt878_find_by_dvb_adap ./dst.o: ./dst.o: unresolved symbol bt878_device_control ./bt878.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_stop ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_start ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878_num ./dvb-bt8xx.o: ./dvb-bt8xx.o: unresolved symbol bt878 caravelle:/usr/src/DVB/build-2.4# indeed there is no videodev.o in my folder, but i have one in my kernel tree. so i first try to put the one i have in my tree in the build folder : it didn't work, i tried to launch videodev module manualy with modprobe, it did't work... So i don't know what to do now... can someone help me please ? cedric picard -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: vdr-sc firmware and kernel 2.6.*
Heiko Vogel [EMAIL PROTECTED] wrote: Hi guys, does there exist a modified firmware for the 2.6.* kernel dvb-drivers, which is usable by the vdr-sc plugin? Sorry for bothering -- I have found the solution in /usr/src/linux/Documentation/dvb/firmware.txt mfg, haaner -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] problem with insmod.sh
hi in fact i didn't have to do ./insmod-bt8xx.sh but ./insmod.sh but i have those errors : Inserting DVB modules into kernelmodprobe: Can't locate module input modprobe: Can't locate module evdev modprobe: Can't locate module videodev ./dvb-ttpci-budget.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-ttpci-budget-ci.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-ttpci-budget-av.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_deregister_Rsmp_2f9423f1 ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_set_configuration_Rsmp_9b288256 ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_submit_urb_Rsmp_72617e2b ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_alloc_urb_Rsmp_d18a750b ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_register_Rsmp_3933865c ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_unlink_urb_Rsmp_efd1d356 ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_bulk_msg_Rsmp_8fb32027 ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_free_urb_Rsmp_9e139786 ./dvb-ttusb-budget.o: ./dvb-ttusb-budget.o: unresolved symbol usb_set_interface_Rsmp_8d622c5c ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_deregister_Rsmp_2f9423f1 ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_submit_urb_Rsmp_72617e2b ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_alloc_urb_Rsmp_d18a750b ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_register_Rsmp_3933865c ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_unlink_urb_Rsmp_efd1d356 ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_bulk_msg_Rsmp_8fb32027 ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_free_urb_Rsmp_9e139786 ./ttusb_dec.o: ./ttusb_dec.o: unresolved symbol usb_set_interface_Rsmp_8d622c5c ./skystar2.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg So my first question : is evdev necessary for a hauppauge nexus-s card second : i think video dev is necessary because it is the basic drivers for video in linux if i'm right... so what can i do... thanks -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Avermedia-dvb-t
Ok, here a better patch for dvb-bt8xx.c:
--- dvb-bt8xx.c 2004-05-03 18:29:27.0 +0200
+++ dvb-bt8xx.c.new 2004-05-26 16:44:39.723123464 +0200
@@ -443,6 +443,12 @@
0, 0);
/* A_PWRDN DA_SBR DA_APP (high speed serial)
*/
break;
+ case 0x07711461:
+ dvb_bt8xx_card_match(card_nr, Avermedia
DVB-T,
+(1 26) | (1 14) | (1 5),
+0, 0);
+ /* A_PWRDN DA_SBR DA_APP (high speed serial)
*/
+ break;
case 0x0:
if (card_type == BT878_NEBULA ||
card_type == BT878_TWINHAN_DST)
Me and a friend wrote some debugging code for the mt352.c:
we changed:
#define I2C_MT352_ADDR 0x0f
to
static int I2C_MT352_ADDR=0x0f;
and changed mt352_attach to:
static int mt352_attach (struct dvb_i2c_bus *i2c, void **data)
{
/* important debug :) */
for(I2C_MT352_ADDR=32;I2C_MT352_ADDR--;)
printk(SADD=%x: %x\n,I2C_MT352_ADDR,mt352_read_register(i2c,
0x7f));
/**/
if (mt352_read_register(i2c, 0x7f) == 0x13)
return dvb_register_frontend(mt352_ioctl, i2c, NULL,
mt352_info);
return -ENODEV;
}
it seems that the mt352 on my card doesn't react to any of this addresses.
output:
SADD=XX: 0
i2c_adapter i2c-2: sendbytes: error - bailout.
mt352_read_register: readreg error (ret == -14)
for XX=1f downto 0
thanks to Daniel for his help.
cheers
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Re: driver for VP7041 VisionDTV Twinhan USB DVB-T
On Wed, 26 May 2004, Andrea Venturi wrote: BTW i'm wondering if this kind of usb driver could be completely an user space application because it's based on best-effort usb transaction (dont remember the exact term in usb terminology; not synchronous, i mean) and i remember there are already user space application acting like driver for other usb adapter. Yes, it only has bulk endpoints. But I'm not sure if a user level application is a real alternative to having a real driver, which fits into the dvb api. Since devices are so different in programming this wouldn't make too much sense, would it? this way, an alpha-state driver should be less of a pain WRT crashing the running kernel! Yes, indeed, this is a point. But then it won't work with standard applications (mplayer, xine, scan)... best regards Patrick -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: kernel panic when removing module while IR is active
Johannes Stezenbach schrieb:
Markus Wiesner wrote:
I hope this is new, at least I could not find something related via
Google ... (a search in the linuxtv.org archive always returned No
matches no matter what I was looking for?!)
I'm using the onboard IR-receiver (J2) of a technotrend premium 1.6
dvb-s with the vanilla kernel 2.6.6 dvb-driver.
When the dvb_ttpci module is removed while the ir-receiver is receiving
data i always get following kernel oops (manually copied from screen,
may contain typos ...):
Thanks for doing that work, and sorry that it took me so long to
respond.
It was worth waiting because ...
I cannot test it now (no IR receiver at hand), but I hope this
is fixed in CVS like so:
diff -u -p -r1.12 av7110_ir.c
--- drivers/media/dvb/ttpci/av7110_ir.c3 May 2004 16:29:28 - 1.12
+++ drivers/media/dvb/ttpci/av7110_ir.c26 May 2004 12:43:54 -
@@ -195,6 +195,7 @@ int __init av7110_ir_init(void)
void __exit av7110_ir_exit(void)
{
+ del_timer_sync(keyup_timer);
remove_proc_entry(av7110_ir, NULL);
av7110_unregister_irc_handler(av7110_emit_key);
input_unregister_device(input_dev);
It would be cool if you could report back if that fix works for you.
... that seems to fix it. :-)
Just tried it several times again, to be sure: Without patch every test
still ended in a kernel panic, with patch (applied to vanilla 2.6.6, not
CVS, but should make no difference) everything is fine. No more kernel
panic when VDR is restarted via OSD and I press the OK button a bit too
long. :-)
thank you very much
Markus
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
