Re: [mythtv-users] FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO (1Jan05)
On Tue, 18 Jan 2005 13:56:19 +, Graeme Hilton <[EMAIL PROTECTED]> wrote: > > > = FC3 + CVS dvb-kernel + Nova-T Install > > MINI-HOWTO > > = By: Paul Pettigrew, Sydney-Australia. 1 Jan 2005 > > > > > > > To unload the drivers that may already be loaded (but are not our fresh > > CVS ones), and to load up our CVS ones, enter the following commands > > respectively: > > # ./insmod.sh unload > > > > # ./insmod.sh load > > There will be some errors, as drivers for cards we do not have will > > attempt > > to load. If you get this behaviour, this is fine for now, as we will > > determine shortly if our drivers have loaded correctly. For me, I get the > > following output to the 'load' command: > > Inserting DVB modules into kernel > > FATAL: Module crc32 not found. > > FATAL: Module firmware_class not found. > > FATAL: Module evdev not found. > > > > The devices will now be created. Confirm by entering: > > # ls /dev/d* > > > > You will now see: > > /dev/dnrtmsg /dev/dvb0.demux0 /dev/dvb0.frontend0 > > /dev/dsp /dev/dvb0.dvr0 /dev/dvb0.net0 > > Everything seems to work until I reach this point where the /dev/dvb > entries just don't exist. I've upgraded udev to the latest version in > the development directory on atrpms.net > > The /sbin/lspci -v brings up the following: > 00:0b.0 Multimedia video controller: Conexant Winfast TV2000 XP (rev 05) > Subsystem: Hauppauge computer works Inc.: Unknown device 9002 > Flags: bus master, medium devsel, latency 32, IRQ 169 > Memory at ea00 (32-bit, non-prefetchable) [size=16M] > Capabilities: [44] Vital Product Data > Capabilities: [4c] Power Management version 2 > > 00:0b.2 Multimedia controller: Conexant: Unknown device 8802 (rev 05) > Subsystem: Hauppauge computer works Inc.: Unknown device 9002 > Flags: bus master, medium devsel, latency 32, IRQ 169 > Memory at eb00 (32-bit, non-prefetchable) [size=16M] > Capabilities: [4c] Power Management version 2 > > 00:0b.4 Multimedia controller: Conexant: Unknown device 8804 (rev 05) > Subsystem: Hauppauge computer works Inc.: Unknown device 9002 > Flags: bus master, medium devsel, latency 32, IRQ 169 > Memory at ec00 (32-bit, non-prefetchable) [size=16M] > Capabilities: [4c] Power Management version 2 > > Which is slightly different to that in the Howto, in that the howto has > a Phillips chip mentioned, where mine has Conexant. > > I'm new to Fedora and Linux in genereal so would apprectiate any advice > on what I've done wrong, or any steps I can take to fix this. > > PS. My system is Athlon 64 bit, so where I can I've used the x86_64 rpms > instead of the i386's. > > -- > Graeme Hilton > > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > Try this guide instead, the philips chipset is the old style Nova-T's, the Conexant chip is the new style. Thanks to Richard for the guide. http://www.helkit.com/cgi-bin/twiki/bin/view/Main/MythTVDVB-TAndConexantNotes -- Regards, ~CM ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO (1Jan05)
= FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO = By: Paul Pettigrew, Sydney-Australia. 1 Jan 2005 To unload the drivers that may already be loaded (but are not our fresh CVS ones), and to load up our CVS ones, enter the following commands respectively: # ./insmod.sh unload # ./insmod.sh load There will be some errors, as drivers for cards we do not have will attempt to load. If you get this behaviour, this is fine for now, as we will determine shortly if our drivers have loaded correctly. For me, I get the following output to the ‘load’ command: Inserting DVB modules into kernel FATAL: Module crc32 not found. FATAL: Module firmware_class not found. FATAL: Module evdev not found. The devices will now be created. Confirm by entering: # ls /dev/d* You will now see: /dev/dnrtmsg /dev/dvb0.demux0 /dev/dvb0.frontend0 /dev/dsp /dev/dvb0.dvr0 /dev/dvb0.net0 Everything seems to work until I reach this point where the /dev/dvb entries just don't exist. I've upgraded udev to the latest version in the development directory on atrpms.net The /sbin/lspci -v brings up the following: 00:0b.0 Multimedia video controller: Conexant Winfast TV2000 XP (rev 05) Subsystem: Hauppauge computer works Inc.: Unknown device 9002 Flags: bus master, medium devsel, latency 32, IRQ 169 Memory at ea00 (32-bit, non-prefetchable) [size=16M] Capabilities: [44] Vital Product Data Capabilities: [4c] Power Management version 2 00:0b.2 Multimedia controller: Conexant: Unknown device 8802 (rev 05) Subsystem: Hauppauge computer works Inc.: Unknown device 9002 Flags: bus master, medium devsel, latency 32, IRQ 169 Memory at eb00 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 00:0b.4 Multimedia controller: Conexant: Unknown device 8804 (rev 05) Subsystem: Hauppauge computer works Inc.: Unknown device 9002 Flags: bus master, medium devsel, latency 32, IRQ 169 Memory at ec00 (32-bit, non-prefetchable) [size=16M] Capabilities: [4c] Power Management version 2 Which is slightly different to that in the Howto, in that the howto has a Phillips chip mentioned, where mine has Conexant. I'm new to Fedora and Linux in genereal so would apprectiate any advice on what I've done wrong, or any steps I can take to fix this. PS. My system is Athlon 64 bit, so where I can I've used the x86_64 rpms instead of the i386's. -- Graeme Hilton ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO (1Jan05)
[EMAIL PROTECTED] wrote: Produced in appreciation of the support and knowledge gained from linux-dvb & mythtv-users mailing lists, with the hope of helping others. (Drafting note - yet to complete modprobe.conf section - tips appreciated!) Paul PS: Feedback / improvements most welcome. PPS: Happy New Year! Hi Paul, Looks good so far - feel free to add the Nova-T Conexant info from http://www.helkit.com/cgi-bin/twiki/bin/view/Main/MythTVDVB-TAndConexantNotes for the instructions on how to get it to load automagically. Cheers, Richie ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO (1Jan05)
Right now I am making one with a PCHDTV 3000 card in mind. On Fri, 31 Dec 2004 22:27:56 -0500, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Produced in appreciation of the support and knowledge gained from linux-dvb & > mythtv-users mailing lists, with the hope of helping others. > > (Drafting note - yet to complete modprobe.conf section - tips appreciated!) > > Paul > > PS: Feedback / improvements most welcome. > PPS: Happy New Year! > > === > = FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO > = By: Paul Pettigrew, Sydney-Australia. 1 Jan 2005 > === > 0. ACKNOWLEDGEMENTS > > This guide is the result of many months of trial & error and a heavy > reliance on the following information sources: > http://www.linuxtv.org/mailinglists/linux-dvb/ > http://wilsonet.com/mythtv/ > http://mythtv.info/moin.cgi/FrontPage > http://www.ethics-gradient.net/myth/mythdvb.html > http://www.google.com/ > ...and many others... > > To those who have contributed to their development, thank you. I hope that > this MINI-HOWTO adds to the available documentation and makes it easier > (than it was for me) for others in the future. > --- > 1. PREAMBLE > > Note: FC3 has switched from a static /dev/ directory to one that is > dynamically managed via udev. This allows device nodes to be created on > demand as drivers are loaded. For more information on udev, refer to the > udev(8) man page and the following link: > http://people.redhat.com/~harald/udev.html > > This MINI-HOWTO assumes that an FC3 Installation has been completed, and > that a Hauppauge WinTV-NOVA-T DVB card has been installed prior to > installing FC3. > > I follow this guide as a pre-requisite to running MythTV, and some of the > steps (such as using apt-get to update the system and setting access rights > for the user 'mythtv') are linked to that outcome. > --- > 2. GET & INSTALL APT TO UPDATE SYSTEM > > Get the latest version of the ATrpms-kickstart tool from: > http://download.atrpms.net/other/packages/fedora-3-i386/atrpms/ > atrpms-kickstart-25-1.rhfc3.at.i386.rpm > > Now install the apt package list by entering the following: > # rpm âUvh atrpms-kickstart-25-1.rhfc3.at.i386.rpm > > Now we'll run a command that fetches all the latest metadata for apt to > process, so it knows what is out there and available to install: > # apt-get update > > With Fedora Core 3, there's a little intermediate step that wasn't > necessary with FC2, but it'll save some trouble at dist-upgrade time: > # apt-get install apt yum modutils > > Now kickoff an OS upgrade by entering the following: > # apt-get update && apt-get dist-upgrade > > The above command will take an eternity. Once it is done, you can > check what version of kernel is running / installed with the following > commands: > # uname âr > # rpm âqa | grep kernel > > Which for me gave the following output (respectively): > 2.6.9-1.667 > > kernel-utils-2.4-13.1.39 > kernel-2.6.9-1.667 > > Ie, that kernel 2.6.9-1.667 is installed. Note: I have experienced udev > segmentation faults with kernel 2.6.9-1.681_FC3, which prevents the > /dev/dvb/adapter0/xxx structure being created. The vanilla FC3 kernel > works just fine. > --- > 3. SET THE MYKERNEL VARIABLE > > Now, we're going to set up a custom environment variable that will make > life easier when installing kernel modules via apt. With the latest > change in kernel module naming conventions (a coordinated effort between > ATrpms, DAG, FreshRPMs and a few other rpm repositories), all systems > can simply use this environment variable, like so: > # export MYKERNEL=`uname -r` > # echo "export MYKERNEL=\`uname -r\`" > /etc/profile.d/kver.sh > > The latter command means it will survive reboots (i.e. you cannot set an > environemnt variable in /etc/rc.local). > --- > 4. CHECKING THE HAUPPAUGE CARD (HARDWARE) > > Check to see that the system has detected the Hauppauge WinTV-NOVA-T DVB > card. Type in the following command and look for the phrase > "Multimedia video controller" to check that the card is being recognized > on the PCI bus: > # /sbin/lspci > > My Hauppauge NOVA-T, as recognised on the PCI bus, gives me the following: > 02:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) > > To see more detail, enter: > # /sbin/lspci -v > Look for our entry above, and additional lines will be below it: > 02:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) > Subsystem: Technotrend Systemtechnik GmbH Technotrend-Budget / > Hauppauge WinTV-NOVA
[mythtv-users] FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO (1Jan05)
Produced in appreciation of the support and knowledge gained from linux-dvb & mythtv-users mailing lists, with the hope of helping others. (Drafting note - yet to complete modprobe.conf section - tips appreciated!) Paul PS: Feedback / improvements most welcome. PPS: Happy New Year! === = FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO = By: Paul Pettigrew, Sydney-Australia. 1 Jan 2005 === 0. ACKNOWLEDGEMENTS This guide is the result of many months of trial & error and a heavy reliance on the following information sources: http://www.linuxtv.org/mailinglists/linux-dvb/ http://wilsonet.com/mythtv/ http://mythtv.info/moin.cgi/FrontPage http://www.ethics-gradient.net/myth/mythdvb.html http://www.google.com/ ...and many others... To those who have contributed to their development, thank you. I hope that this MINI-HOWTO adds to the available documentation and makes it easier (than it was for me) for others in the future. --- 1. PREAMBLE Note: FC3 has switched from a static /dev/ directory to one that is dynamically managed via udev. This allows device nodes to be created on demand as drivers are loaded. For more information on udev, refer to the udev(8) man page and the following link: http://people.redhat.com/~harald/udev.html This MINI-HOWTO assumes that an FC3 Installation has been completed, and that a Hauppauge WinTV-NOVA-T DVB card has been installed prior to installing FC3. I follow this guide as a pre-requisite to running MythTV, and some of the steps (such as using apt-get to update the system and setting access rights for the user 'mythtv') are linked to that outcome. --- 2. GET & INSTALL APT TO UPDATE SYSTEM Get the latest version of the ATrpms-kickstart tool from: http://download.atrpms.net/other/packages/fedora-3-i386/atrpms/ atrpms-kickstart-25-1.rhfc3.at.i386.rpm Now install the apt package list by entering the following: # rpm Uvh atrpms-kickstart-25-1.rhfc3.at.i386.rpm Now we'll run a command that fetches all the latest metadata for apt to process, so it knows what is out there and available to install: # apt-get update With Fedora Core 3, there's a little intermediate step that wasn't necessary with FC2, but it'll save some trouble at dist-upgrade time: # apt-get install apt yum modutils Now kickoff an OS upgrade by entering the following: # apt-get update && apt-get dist-upgrade The above command will take an eternity. Once it is done, you can check what version of kernel is running / installed with the following commands: # uname r # rpm qa | grep kernel Which for me gave the following output (respectively): 2.6.9-1.667 kernel-utils-2.4-13.1.39 kernel-2.6.9-1.667 Ie, that kernel 2.6.9-1.667 is installed. Note: I have experienced udev segmentation faults with kernel 2.6.9-1.681_FC3, which prevents the /dev/dvb/adapter0/xxx structure being created. The vanilla FC3 kernel works just fine. --- 3. SET THE MYKERNEL VARIABLE Now, we're going to set up a custom environment variable that will make life easier when installing kernel modules via apt. With the latest change in kernel module naming conventions (a coordinated effort between ATrpms, DAG, FreshRPMs and a few other rpm repositories), all systems can simply use this environment variable, like so: # export MYKERNEL=`uname -r` # echo "export MYKERNEL=\`uname -r\`" > /etc/profile.d/kver.sh The latter command means it will survive reboots (i.e. you cannot set an environemnt variable in /etc/rc.local). --- 4. CHECKING THE HAUPPAUGE CARD (HARDWARE) Check to see that the system has detected the Hauppauge WinTV-NOVA-T DVB card. Type in the following command and look for the phrase Multimedia video controller to check that the card is being recognized on the PCI bus: # /sbin/lspci My Hauppauge NOVA-T, as recognised on the PCI bus, gives me the following: 02:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) To see more detail, enter: # /sbin/lspci -v Look for our entry above, and additional lines will be below it: 02:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend-Budget / Hauppauge WinTV-NOVA-T DVB card Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at f602 (32-bit, non-prefetchable) [size=512] If you don't see your card on the PCI bus, make sure that it's been installed in a bus-master slot (for some motherboards, only the PCI slots closest to the AGP slot have this capability). -
