How to load Kworld ATSC-110 modules into Puppy 2.14?

Using applications, configuring, problems
Post Reply
Message
Author
kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

How to load Kworld ATSC-110 modules into Puppy 2.14?

#1 Post by kirk »

I've got a Kworld ATSC-110. I've been trying to get it to work with the instructions here:

http://www.linuxtv.org/v4lwiki/index.ph ... d_ATSC-110

But Puppy's kernel wasn't compiled with the saa7134-dvb module. So I edited the .config, changed to saa7134-dvb=m and saa7134-alsa=m, saa7134-empress=m. Then did a make silentoldconfig. Then make modules. All seemed to go well. So I put the firmware I downloaded with this comand:

# perl get_dvb_firmware nxt2004

in /lib/firmware and tried:

sh-3.00# modprobe saa7134-dvb
FATAL: Error inserting saa7134_dvb (/lib/modules/2.6.18.1/kernel/drivers/media/video/saa7134/saa7134-dvb.ko): Unknown symbol in module, or unknown parameter (see dmesg)

And you can see what I get. I tried the other modules that I built, and they load without error. Then I realized that I had the 2.13 kernel source, so I got the 2.14 kernel source and tried again. Same result.

Could this be a problem with the firmware? (This module tries to load firmware)

If so, besides putting the firmware in /lib/firmware is there something else that must be done?

Here's what dmesg says:

saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7134_dvb: Unknown symbol dvb_pll_tdhu2
saa7134_dvb: Unknown symbol mt352_attach
saa7134_dvb: Unknown symbol request_firmware
saa7134_dvb: Unknown symbol dvb_pll_philips_td1316
saa7134_dvb: Unknown symbol dvb_pll_attach
saa7134_dvb: Unknown symbol dvb_pll_tuv1236d
saa7134_dvb: Unknown symbol videobuf_dvb_unregister
saa7134_dvb: Unknown symbol videobuf_dvb_register
saa7134_dvb: Unknown symbol nxt200x_attach
saa7134_dvb: Unknown symbol tda10046_attach
saa7134_dvb: Unknown symbol mt352_write
saa7134_dvb: Unknown symbol dvb_pll_configure
saa7134_dvb: Unknown symbol dvb_pll_tdhu2
saa7134_dvb: Unknown symbol mt352_attach
saa7134_dvb: Unknown symbol request_firmware
saa7134_dvb: Unknown symbol dvb_pll_philips_td1316
saa7134_dvb: Unknown symbol dvb_pll_attach
saa7134_dvb: Unknown symbol dvb_pll_tuv1236d
saa7134_dvb: Unknown symbol videobuf_dvb_unregister
saa7134_dvb: Unknown symbol videobuf_dvb_register
saa7134_dvb: Unknown symbol nxt200x_attach
saa7134_dvb: Unknown symbol tda10046_attach
saa7134_dvb: Unknown symbol mt352_write
saa7134_dvb: Unknown symbol dvb_pll_configure
sh-3.00#

Thanks,

Kirk

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#2 Post by tempestuous »

kirk,
I have a collection of drivers and utilities which I have been intending to contribute, so your post prompts me to attach the DVB drivers now.
These are modules for TV tuner cards NOT already provided by Puppy vers 2.12/2.13/2.14
Specifically:

ivtv
ivtv-fb
saa717x
video-buf-dvb
cx88-alsa
cx88-blackbird
cx88-dvb
cx88-vp3054-i2c
pvrusb2
saa7134-alsa
saa7134-dvb
isl6421

saa7134-empress is already included in Puppy's zdrv file.
The package also provides the necessary firmware files for several different drivers, originally from http://dl.ivtvdriver.org/ivtv/firmware/
And the package also includes the MAKEDEV-DVB.sh script, to create the necessary device nodes for DVB devices.

EDIT: attachment removed.
IVTV+DVB-modules-k2.6.18.1.pet is now fixed, and available at -
http://puppyfiles.org/dotpupsde/dotpups ... er-1.0rc1/
Last edited by tempestuous on Wed 21 Mar 2007, 00:45, edited 1 time in total.

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#3 Post by kirk »

Thanks, I downloaded the package twice. Pupget says there was an error installing it and to look in /root/.packages. It all seemed to be there, so I manually installed it. Ran the MAKEDEV-DVB script. When I modprobe saa7134-dvb. I get this:

sh-3.00# modprobe saa7134-dvb
WARNING: Error inserting video_buf_dvb (/lib/modules/2.6.18.1/kernel/drivers/media/video/video-buf-dvb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting saa7134_dvb (/lib/modules/2.6.18.1/kernel/drivers/media/video/saa7134/saa7134-dvb.ko): Unknown symbol in module, or unknown parameter (see dmesg)

sh-3.00# dmesg
video_buf_dvb: Unknown symbol dvb_dmxdev_init
video_buf_dvb: Unknown symbol dvb_register_adapter
video_buf_dvb: Unknown symbol dvb_dmx_release
video_buf_dvb: Unknown symbol dvb_net_init
video_buf_dvb: Unknown symbol dvb_dmx_swfilter
video_buf_dvb: Unknown symbol dvb_dmxdev_release
video_buf_dvb: Unknown symbol dvb_net_release
video_buf_dvb: Unknown symbol dvb_unregister_frontend
video_buf_dvb: Unknown symbol dvb_register_frontend
video_buf_dvb: Unknown symbol dvb_unregister_adapter
video_buf_dvb: Unknown symbol dvb_dmx_init
saa7134_dvb: Unknown symbol dvb_pll_tdhu2
saa7134_dvb: Unknown symbol mt352_attach
saa7134_dvb: Unknown symbol request_firmware
saa7134_dvb: Unknown symbol dvb_pll_philips_td1316
saa7134_dvb: Unknown symbol dvb_pll_attach
saa7134_dvb: Unknown symbol dvb_pll_tuv1236d
saa7134_dvb: Unknown symbol videobuf_dvb_unregister
saa7134_dvb: Unknown symbol videobuf_dvb_register
saa7134_dvb: Unknown symbol nxt200x_attach
saa7134_dvb: Unknown symbol tda10046_attach
saa7134_dvb: Unknown symbol mt352_write
saa7134_dvb: Unknown symbol dvb_pll_configure
video_buf_dvb: Unknown symbol dvb_dmxdev_init
video_buf_dvb: Unknown symbol dvb_register_adapter
video_buf_dvb: Unknown symbol dvb_dmx_release
video_buf_dvb: Unknown symbol dvb_net_init
video_buf_dvb: Unknown symbol dvb_dmx_swfilter
video_buf_dvb: Unknown symbol dvb_dmxdev_release
video_buf_dvb: Unknown symbol dvb_net_release
video_buf_dvb: Unknown symbol dvb_unregister_frontend
video_buf_dvb: Unknown symbol dvb_register_frontend
video_buf_dvb: Unknown symbol dvb_unregister_adapter
video_buf_dvb: Unknown symbol dvb_dmx_init
saa7134_dvb: Unknown symbol dvb_pll_tdhu2
saa7134_dvb: Unknown symbol mt352_attach
saa7134_dvb: Unknown symbol request_firmware
saa7134_dvb: Unknown symbol dvb_pll_philips_td1316
saa7134_dvb: Unknown symbol dvb_pll_attach
saa7134_dvb: Unknown symbol dvb_pll_tuv1236d
saa7134_dvb: Unknown symbol videobuf_dvb_unregister
saa7134_dvb: Unknown symbol videobuf_dvb_register
saa7134_dvb: Unknown symbol nxt200x_attach
saa7134_dvb: Unknown symbol tda10046_attach
saa7134_dvb: Unknown symbol mt352_write
saa7134_dvb: Unknown symbol dvb_pll_configure
sh-3.00#

I've never used this card. Maybe it's bad. The Windows software that it came with had the wrong key. I sent the vendor an Email. Probably should try to get it working with their software first then try it with puppy. The firmware that should be for this card is the nxt2004. I'll post it here in case you want to add it to the package.

Thanks for your help!
Attachments
dvb-fe-nxt2004.fw.gz
(6.51 KiB) Downloaded 234 times

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#4 Post by tempestuous »

There should be no compatibility problems with these modules, since they were compiled from the correct 2.14 kernel source -
http://puptrix.org/sources/kernel-2.6.1 ... 14.tar.bz2

I suspect it may just be a problem of dependent modules not loading. So try to load all modules in this order -

modprobe i2c-core
modprobe firmware_class
modprobe tda1004x
modprobe nxt200x
modprobe mt352
modprobe dvb-pll
modprobe dvb-core
modprobe video-buf
modprobe video-buf-dvb
modprobe v4l2-common
modprobe v4l1-compat
modprobe videodev
modprobe ir-common
modprobe ir-kbd-i2c
modprobe compat_ioctl32
modprobe saa7134
modprobe saa7134-dvb

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#5 Post by tempestuous »

kirk wrote:Pupget says there was an error installing it and to look in /root/.packages.
The dotpet is designed to run depmod at the end of the installation, maybe this failed.
So the solution might just be to run "depmod".

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#6 Post by kirk »

I did do a depmod -a. I'll try loading them in the order you listed. Puppy automaticly loads many of those, so I'll rmmod them first. It will be a few days before I can give it another try. Thanks again!

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#7 Post by kirk »

Finaly got back to this thing. Removed All the modules that had anything to do with the tv card. Loaded them in the order recommended. No errors! Then ran tvtime. Didn't work. then I realized I had removed the module tuner and not reinstalled it. So I modprobed tuner and then it worked. I rebooted and then just did a modprobe saa7134-dvd, and it installed without error. Strange. I think something might have loaded the firmware the first go around, and now it's fine.

Thanks for the help tempestuous.

Post Reply