Thanks Rolf,
I found out the reason why I the installation of the DEV driver was not
working. I made an extra entry in the grub.conf (for the new bootloader)
to start my original RH7.2 boot image. I copied the vmlinuz<version> to
vmlinuz.old and all other related files like initrd<version>.img etc. I
assumed that recompiling and 'make install' would replace the original
boot image files. I never checked it and could not understand why my
efforts had no effect at al, until I found out that the new boot image
files suddenly had the word 'custom' added to their names.... So all the
time I had been switching back an forth between two copies of the same
kernel. I have not been compiling kernels for a few months (I hardly
ever have the time to digg into linux) but somtimes things change.
However I have some problems left with my DVB card and maybe someone
could shed some light, or give me some hints where to look for a solution.
The status so far:
I compiled the DVB/driver and did make insmod. For some reason the
'videodev' module could not be found, but to my surprize XawTV could be
started. I have N-TV as the only station. I cannot change the channels.
I see the numbers change in the window bar of XawTV when I attempt to
switch channels but the in=mage remains firmly on N-TV. Sound is only
heard via a loop cable from my DVB card 'audio out' to my Sound card
(Soundblaster live) line input. This is of course not reacting to mute
or volume changes. Again the window bar shows 'Mute' or 'Volume 0%' when
I press volume down or switch mute. It is impossible to increase the
volume. Making of a channel list has no effect on things.
I hope someone can help
Thanks in advance
Ton van Baalen
Rolf Siebrecht wrote:
Hi! ;-)
On Mon, 29 Oct 2001, FRE0000076763 wrote:
/opt/download/DVB
?make?
/usr/src/linux/scripts/pathdown.sh: TOPDIR: parameter null or not set
ntuxzap.cc:37: syntax error before ?*?
ntuxzap.cc:116: ?EObjectType? was not declared in this scope
[...]
I think it's not advisable to call 'make' from the top directory of the
driver package. 'cd' to the various subdirectories and call 'make' there.
To compile tuxzap applications,
cd apps/tuxzap
then call
./autogen.sh
then
make
and finally
make install
But read apps/tuxzap/README before. You must have the CDK library
installed to let the compilation of ntuxzap be successful. And - not
mentioned in that README file - you must also have installed GTK header
files and static libraries: most often contained in an rpm package called
'gtk-devel' as part of your distribution CDs.
/opt/download/DVB/driver
?make? went fine
?make insmod? gave errors:
/usr/src/linux/scripts/pathdown.sh: TOPDIR: parameter null or not set
dvb_net.o: unresolved symbol alloc_skb_R0270e4f2
dvb_net.o: unresolved symbol netif_rx_Rb85c5e94
dvb_net.o: unresolved symbol skb_over_panic_Rc43a84cc
Did you select correct network settings when you executed 'make
[menu|x]config' to configure kernel compilation? I don't know in detail
which network settings are responsible to omit these missing symbols. But,
you may compare the network sections of your /usr/src/linux/.config file
with one of the "official" config files in /usr/src/linux/configs - and
check if you have identical or similar network settings.
(/usr/src/linux/.config contains the result of 'make [menu|x]config', so
to speak.)
Another test: "alloc_skb", "netif_rx" and "skb_over_panic" should be
listed in /usr/src/linux/System.map after kernel compilation.
?/opt/download/VDR make? gave errors:
I don't use VDR. VDR has its own mailing list @ vdr@xxxxxxxxxxxx
Bye,
Rolf
