pcHDTV :: View topic - ANNOUNCE: pcHDTV 2000 & 3000 drivers included in the ker

tijoev

I am getting closer. At least this time I saw the pchdtv cards while compiling the kernel.

I get an error when I try to make my image:

linux:/home/joev/linux-2.6.11 # make bzImage
CHK include/linux/version.h
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
SKIPPED include/linux/compile.h
CHK usr/initramfs_list
GEN .version
CHK include/linux/compile.h
SKIPPED include/linux/compile.h
LD .tmp_vmlinux1
drivers/built-in.o(.text+0x8b885): In function `i2c_writebytes':
: undefined reference to `i2c_transfer'
drivers/built-in.o(.text+0x8b905): In function `i2c_readbytes':
: undefined reference to `i2c_transfer'
drivers/built-in.o(.text+0x8c081): In function `or51132_set_parameters':
: undefined reference to `request_firmware'
drivers/built-in.o(.text+0x8c0c0): In function `or51132_set_parameters':
: undefined reference to `release_firmware'
drivers/built-in.o(.text+0x8c12c): In function `or51132_set_parameters':
: undefined reference to `request_firmware'
make: *** [.tmp_vmlinux1] Error 1
linux:/home/joev/linux-2.6.11 # INSTALL_PATH=/boot make install
make[2]: *** No rule to make target `vmlinux', needed by `arch/i386/boot/compressed/vmlinux.bin'. Stop.
make[1]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make: *** [install] Error 2

never had this before. Wondering if it has to do with undefined reference to `request_firmware'.

I copied the firmware update files to /usr/lib/hotplug/firmware.

HDTV buff

tijoev

Compiling a kernel is not too much for me. I have compiled kernels before there were rpms. I have never gone for patches or development kernels.

The vanilla kernel from the 2.6.11 download with the .12-rc2 patch did not compile.

No I did not run the script because I do not like or use rpms, I do not quite get the squence of events since I have no internet access on this machine and that .config file is why too much overhead for my use.

Let's start here, are the firmware updates from the website suppose to be in /usr/lib/hotplug/firmware?

tijoev

HDTV

Your .config file will not compile on my box. It does the same thing that a vanilla 2.6.11 compile does; just exits after a while without giving the conventional " make bzImage....."

The rpm does the same thing.

Guest

tijoev
I do not do RPM's at all and I'm running into the same glitch you are. I suspect the ( unstable ) source changed slightly from when he picked it up and we did. You are trying the April 4th one right ?
I'm thinking about tracing though the perl code in documentation to see if I can find a glitch.

tijoev

tijoev

Guest

No I run Gentoo at home and Redhat for work. I was refereing to the build date.
I even tried cheating and attempted using the full unstable kernel source which never worked for me before either. I have much better luck patching up. Bad thing is I had an Air2pc working within 2 days, wish the guy would have traded cards with me Wink

I've had this one 2 months and basic ntsc is as far as I've gotten with it.

Are you the same person who posted another thread using SuSE 9.2? I am wondering if this maybe a SuSE thing at this point.

Not sure what yo mean by "...trying April 4th..."

I have been working with:

linux-2.6.11.tar.gz 01-Mar-2005 23:59 44M kernel.org

patch 2.6.12-rc2 kernel.org[/quote]

HDTV buff

HDTV buff

photonwave

Hello "Guest", I may be able to offer you some help.

I'm using the Gentoo 2.6.12-r2 kernel with the built-in DVB drivers successfully. If you're seeing the undefined reference errors that tijoev is seeing, the problem may lie in your choice of kernel options. I suggest using the genkernel program to compile your kernel with the --menuconfig option:

inkling

I had the error about release_firmware too when trying to compile for 2.6.10. Turned out my kernel wasn't configured for hotplug. It's in General options near the top, same place as accounting, SysV IPC, etc.

It's pretty new, so it might not be enabled by default.

2.6.10 seemed to have better support (more options) for udev, compared to 2.6.7. I could be wrong about that, but I noticed 2.6.7 didn't like to modprobe the compiled modules, same release_firmware error, even with hotplug enabled, but 2.6.10 did ok, maybe because of the extra options that 2.6.10 provided.

Note: this was on unpatched 2.6.7 and 2.6.10 kernels so lots of old junk was likely to have been a major cause for at least the 2.6.7 problems.

I'm not sure if that helps, but,

Good Luck

-ink

mnestroy

I followed your instructions and got the Kernal to update, I restarted my PC and a new popup window detected the card, I dont think it was the right card though,

But anyways can you give me some pointers of what steps to do next?

1. What enteries need to be put in the modprobe.conf to get my HD-3000 to work?

2. Do I still need to compile any of the tools or drivers from the manufactures website?

Thanks!

tijoev

HDTV

Yes I did make a mistake the ` for '. That is a number one after the -n switch. The post just makes pipes, the small letter l and the number one look the same.

I appreciate your help but the condesending attitude has got to go Dude. This has been a very frustrating process and at this point I am not going to even look at it again until I move and can have this box available to the internet. Hope fully, the 2.0 dvb driver module will just simply work with Myth and I can be done with this foolish proccess.

If not, I'll just wait for a stable kernel release.

Guest

Add me to the successful compiles now. I went back through very carefully and the only option I did not have selected was /I2C bit-bang. So for a grin I selected it and what do you know it compilled clean and detected the card.
Thanks,,

Now I wonder how many others are having the same problem ?

[quote="photonwave"]Hello "Guest", I may be able to offer you some help.
I successfully emerged the "vanilla-sources", chose the "bit-banging" options under I2C