26 replies to this topic

[dcallan]

Nebula Linux-2.6 HOWTO (reloaded)

I folks. This is my new howto thread for Nebula Linux (2.6.9+) installation. I decided to not edit/replace the original howto as it would make the rest of the existing posts in that thread very confusing to read through. I will just put a link and disclaimer in there once I post this new one.

Since I have (thus far) only done this in FC3 (and have already found alternative methods), I am going to segregate the guides into several posts based on distribution:

Fedora Core 3
SUSE 9x
Gentoo

I am putting place-filler posts in for SUSE and Gentoo for now. Maybe link in some more guides for xine, kaxtv and myth later on too.

** UPDATES **
(2005-03-14) - Updated rpm link for udev and fixed typo errors in kernel/grub building instructions
(2005-04-04) - Updated rpm link for udev

Edited by dcallan, 04 April 2005 - 11:09 PM.

[dcallan]

Fedora Core 3 - Nebula HOWTO

Assumptions:

Fedora Core 3 installed (w' Development Tools packages)
Internet access (lots of package updating)
Nebula DVB card installed

Basic Outcomes:

Upgrades all system packages using ATrpm apt-get (OPTIONAL)
Upgrades udev to development release (and creates /dev/dvb rules)
Either:
- Uses latest 2.6.10 FC3 kernel (from package upgrades)
OR
- Re-links kernel dvb sources (from CVS copy of dvb-kernel) and rebuilds current 2.6.9 kernel as "-prepdvb" version
Configures modprobe.conf to load dvb modules on startup
Builds dvbtune/dvbstream/tzap for testing

Paul Pettigrew's FC3 + CVS dvb-kernel + Nova-T Install MINI-HOWTO was the guide that followed most closely when I was doing this install. As he says:

Quote

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.

Unfortunately, I have not yet finished setting up Myth so that bit can come later. For now I mention it in case you do not wish to do the whole atrpms / apt-get overhaul. You pretty much just need to upgrade (via yum) the current modutils, and kernel rpms (if you are doing 2.6.10). You still need to download the kernel SRPM (for 2.6.9 kernel) and udev from a fedora mirror.

---------------------------------------------------------------------------

1. Upgrade system packages using ATrpm kickstart OPTIONAL

- Download Latest version of ATrpms-kickstart to /usr/src/
- Run the commands:

rpm –Uvh atrpms-kickstart-25-1.rhfc3.at.i386.rpm
yum upgrade
apt-get install modutils
apt-get update && apt-get dist-upgrade

export MYKERNEL=`uname -r`
echo "export MYKERNEL=\`uname -r\`" > /etc/profile.d/kver.sh
chmod 755 /etc/profile.d/kver.sh

---------------------------------------------------------------------------

2. Upgrade udev package to 078-8ESSENTIAL

- Download Latest version of udev to /usr/src/
- Run the commands:

cd /usr/src
rpmbuild --rebuild udev-078-8.src.rpm
rpm -Uvh  /usr/src/redhat/RPMS/i386/udev-078-8.i386.rpm

- Create udev rules file for dvb (run: vi /etc/udev/rules.d/51-dvb.rules )
File: "51-dvb.rules"

KERNEL="dvb0.dvr*", NAME="dvb/adapter0/dvr%n"
KERNEL="dvb0.demux*", NAME="dvb/adapter0/demux%n"
KERNEL="dvb0.frontend*", NAME="dvb/adapter0/frontend%n"
KERNEL="dvb0.audio*", NAME="dvb/adapter0/audio%n"
KERNEL="dvb0.ca*", NAME="dvb/adapter0/ca%n"
KERNEL="dvb0.osd*", NAME="dvb/adapter0/osd%n"
KERNEL="dvb0.net*", NAME="dvb/adapter0/net%n"
KERNEL="dvb0.video*", NAME="dvb/adapter0/video%n"

KERNEL="dvb1.dvr*", NAME="dvb/adapter1/dvr%n"
KERNEL="dvb1.demux*", NAME="dvb/adapter1/demux%n"
KERNEL="dvb1.frontend*", NAME="dvb/adapter1/frontend%n"
KERNEL="dvb1.audio*", NAME="dvb/adapter1/audio%n"
KERNEL="dvb1.ca*", NAME="dvb/adapter1/ca%n"
KERNEL="dvb1.osd*", NAME="dvb/adapter1/osd%n"
KERNEL="dvb1.net*", NAME="dvb/adapter1/net%n"
KERNEL="dvb1.video*", NAME="dvb/adapter1/video%n"

KERNEL="dvb2.dvr*", NAME="dvb/adapter2/dvr%n"
KERNEL="dvb2.demux*", NAME="dvb/adapter2/demux%n"
KERNEL="dvb2.frontend*", NAME="dvb/adapter2/frontend%n"
KERNEL="dvb2.audio*", NAME="dvb/adapter2/audio%n"
KERNEL="dvb2.ca*", NAME="dvb/adapter2/ca%n"
KERNEL="dvb2.osd*", NAME="dvb/adapter2/osd%n"
KERNEL="dvb2.net*", NAME="dvb/adapter2/net%n"
KERNEL="dvb2.video*", NAME="dvb/adapter2/video%n"

KERNEL="dvb3.dvr*", NAME="dvb/adapter3/dvr%n"
KERNEL="dvb3.demux*", NAME="dvb/adapter3/demux%n"
KERNEL="dvb3.frontend*", NAME="dvb/adapter3/frontend%n"
KERNEL="dvb3.audio*", NAME="dvb/adapter3/audio%n"
KERNEL="dvb3.ca*", NAME="dvb/adapter3/ca%n"
KERNEL="dvb3.osd*", NAME="dvb/adapter3/osd%n"
KERNEL="dvb3.net*", NAME="dvb/adapter3/net%n"
KERNEL="dvb3.video*", NAME="dvb/adapter3/video%n"

---------------------------------------------------------------------------

3. Use linux 2.6.10 OR Rebuild linux 2.6.9
(Option1 is recommended)
Option 1 - Using current 2.6.10 FC3 kernel:
- Upgrade to latest FC3 kernel rpm (should have already happened if system has been updated)

yum update kernel kernel-utils

- Fetch the dvb-apps from cvs:

cd /usr/src
mkdir dvb-cvs
cd dvb-cvs/
cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv login
cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv co dvb-apps
cd /usr/src/

*Note: Password for CVS is blank (just hit enter)
GO TO STEP 4

OR

Option 2 - Fix existing 2.6.9 kernel with CVS dvb-kernel:
- Download Linux 2.6.9 SRPM to /usr/src/
- Run the commands:

cd /usr/src
cd /usr/src/
rpm -Uvh kernel-2.6.9-1.667.src.rpm
cd redhat/SPECS/
rpmbuild -bp --target=i686 kernel-2.6.spec
cd ../BUILD/
cp -a kernel-2.6.9/linux-2.6.9 /usr/src/
cd /usr/src/
ln -s linux-2.6.9 linux-2.6
cd linux-2.6
ls -al configs/
cp configs/kernel-2.6.9-i686-smp.config ./.config
cd ../
mkdir dvb-cvs
cd dvb-cvs/
cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv login
cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv co dvb-kernel dvb-apps
cd dvb-kernel/
./makelinks /usr/src/linux-2.6.9
cd /usr/src/

*Note: Password for CVS is blank (just hit enter)

- Run:

cd linux-2.6
make menuconfig

- Set Local Version to "dvb" (in General Settings)
- Exit, saving new kernel config
- Run:

make bzImage && make modules
make modules_install
cp ./arch/i386/boot/bzImage /boot/vmlinuz-2.6.9prepdvb
cp System.map /boot/System.map-2.6.9prepdvb
cd /boot
mkinitrd ./initrd-2.6.9prepdvb.img 2.6.9

- Add the folowing to "/boot/grub/grub.conf"

title Fedora Core (2.6.9prepdvb)
        root (hd1,0)
        kernel /vmlinuz-2.6.9prepdvb ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.9prepdvb.img

(NOTE: Replace /dev/VolGroup00/LogVol00 with your root partition location, if different)

---------------------------------------------------------------------------

4. Configures modprobe.conf to load dvb modules on startup

- Edit /etc/modprobe.conf and insert:

options bttv card=0x68 i2c_hw=1
install bttv /sbin/modprobe --ignore-install bttv && { /sbin/modprobe dvb-bt8xx; /sbin/modprobe nxt6000; /bin/true; }
remove bttv { /sbin/modprobe -r dvb-bt8xx dst nxt6000 dvb-core; }; /sbin/modprobe -r --ignore-remove bttv

- Give it a reboot and select your new kernel in the grub menu
- After you boot, you should have some lines like this in your dmesg output:

Quote

Linux video capture interface: v1.00
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI interrupt 0000:03:06.0[A] -> GSI 22 (level, low) -> IRQ 193
bttv0: Bt878 (rev 17) at 0000:03:06.0, irq: 193, latency: 32, mmio: 0xf4100000
bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID is 0071:0101
bttv0: using: Nebula Electronics DigiTV [card=104,insmod option]
bttv0: gpio: en=00000000, out=00000000 in=00ffb0cf [init]
bttv0: IRQ lockup, cleared int mask [bits: GPINT*]
bttv0: using tuner=-1
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI interrupt 0000:03:06.1[A] -> GSI 22 (level, low) -> IRQ 193
bt878(0): Bt878 (rev 17) at 03:06.1, irq: 193, latency: 32, memory: 0xf4101000
DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (NxtWave NXT6000 DVB-T)...

---------------------------------------------------------------------------

5. Build dvbtune/dvbstream/tzap from "dvb-apps" for testing the dvb frontend

<<<<<<<< UNDER CONSTRUCTION >>>>>>>>>

---------------------------------------------------------------------------

Edited by dcallan, 07 February 2006 - 01:52 PM.

[dcallan]

SUSE 9x

<<<<<<<< UNDER CONSTRUCTION >>>>>>>>>

[dcallan]

Gentoo

<<<<<<<< UNDER CONSTRUCTION >>>>>>>>>

[kantoine]

Hi

Did you see in my thread on digitv and suse that I found out where the "firmware" comes from ?

In the linux kernel; /usr/src/linux.xxx/Documentation/dvb/firmware.txt

Also I googled "firmware SC_MAIN.MC" and got lots more.

[yeahbut]

Is there any new progress being made on this how-to? I am particularly interested in the SuSe aspect, as I already have a working system with Fedora and Gentoo, I don't seem to be able to sort out the SuSe side of the equation....

[dcallan]

yeahbut, on Mar 4 2005, 08:59 AM, said:

Is there any new progress being made on this how-to?

Regrettably, none whatsoever right now  

yeahbut, on Mar 4 2005, 08:59 AM, said:

I am particularly interested in the SuSe aspect, as I already have a working system with Fedora and Gentoo, I don't seem to be able to sort out the SuSe side of the equation....

<{POST_SNAPBACK}>

Yeah, sorry about that but I am pretty much swamped with work right now.  
Plus I still need to get the Myth setup sorted out properly for FC3 before I can move on to doing it with Gentoo/SUSE.

What part are you stuck on (kernel or software)?

[yeahbut]

dcallan, on Mar 4 2005, 10:31 AM, said:

Yeah, sorry about that but I am pretty much swamped with work right now. 
Plus I still need to get the Myth setup sorted out properly for FC3 before I can move on to doing it with Gentoo/SUSE.

What part are you stuck on (kernel or software)?

<{POST_SNAPBACK}>

Actually it's more to do with the modules, I know next to nothing about SuSe, but it is such a polished distro, I would like to get it working...

The problem could be something to do with the auto-detection system for TV cards in SuSe, it doesn't seem to detect them correctly (DVB ones anyway)

When I load the dvb-bt8xx & nxt6000 modules nuffin' werks

Don't know enough about Suse yet unfortunately.

With the latest FC3 kernels though, there is hardly any configuration required...

[DJBenson]

Got a little stuck now. I've followed the guide (using Fedora Core 3) with no errors until I rebooted and checked the dmesg output and found:

Linux video capture interface: v1.00
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 3 (level, low) -> IRQ 3
bttv0: Bt878 (rev 17) at 0000:00:0d.0, irq: 3, latency: 64, mmio: 0xf7e00000
bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID is 0071:0101
bttv0: using: Nebula Electronics DigiTV [card=104,insmod option]
bttv0: gpio: en=00000000, out=00000000 in=00ff00cb [init]
bttv0: using tuner=-1
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
dvb_bt8xx: unable to determine DMA core of card 0,
dvb_bt8xx: if you have the ALSA bt87x audio driver installed, try removing it.
dvb-bt8xx: probe of dvb0 failed with error -14

It's the last three lines I think where things go wrong and the driver fails to load. Any idea's what the problem is here?

I'm dying to get my DigiTV card working in Linux then I can dump Window$ alltogether.

[alien2k_uk]

DJBenson, on Apr 2 2005, 07:55 AM, said:

Got a little stuck now. I've followed the guide (using Fedora Core 3) with no errors until I rebooted and checked the dmesg output and found:

<snip>
dvb_bt8xx: unable to determine DMA core of card 0,
dvb_bt8xx: if you have the ALSA bt87x audio driver installed, try removing it.
dvb-bt8xx: probe of dvb0 failed with error -14

It's the last three lines I think where things go wrong and the driver fails to load. Any idea's what the problem is here?

I'm dying to get my DigiTV card working in Linux then I can dump Window$ alltogether.

<{POST_SNAPBACK}>

On my 2.6.6 system (Debian Sarge, with some unstable thrown in where I want it, and the Myth, Freevo and Marillat repositories) at least, nxt6000 must be inserted before dvb-bt8xx, otherwise I get a very similar message. Note that I don't get any output in /var/log/messages when nxt6000 is inserted, but going ahead and inserting dvb-bt8xx afterwards gets me a working Nebula card!

Also, be careful what modules get loaded by autodetection scripts - as a precaution I remove anything related before inserting nxt6000 and dvb-bt8xx. If I rebooted more often I'd probably put an initscript just before Myth starts to clean things up, although that's probably the wrong thing to do.

I don't know if you have to do it in this strict order in later kernels (or even whether one ever had to do it at all...), but the SmartLink modem driver uses major number 212 as does DVB in anything after what I've got - and I'd be dead meat if the modem stopped working for "some stupid expensive TV thing that doesn't even get Sky One" (not that it stops anyone wanting to come in my room when they've missed something they know I record )!

Sam

[dcallan]

DJBenson, on Apr 2 2005, 04:55 PM, said:

bt878: AUDIO driver version 0.0.0 loaded
dvb_bt8xx: unable to determine DMA core of card 0,
dvb_bt8xx: if you have the ALSA bt87x audio driver installed, try removing it.
dvb-bt8xx: probe of dvb0 failed with error -14

It's the last three lines I think where things go wrong and the driver fails to load. Any idea's what the problem is here?

<{POST_SNAPBACK}>

Indeed, there is a conflict of sorts between dvb_bt8xx and snd_bt87x. This has happended for a few other users too (See thread).

I have not experienced it personally, but the working solution I know of is to unload the ALSA module as part of the bttv loading. Try altering your install script in modprobe.conf to:

install bttv /sbin/modprobe --ignore-install bttv && { /sbin/rmmod snd_bt87x; /sbin/modprobe dvb-bt8xx; /sbin/modprobe nxt6000; /bin/true; }

Alternately you could try out Sam's (alien2k_uk) suggestion - of loading the tuner module first - by just reversing the order of the modules in the original install script:

install bttv /sbin/modprobe --ignore-install bttv && { /sbin/modprobe nxt6000; /sbin/modprobe dvb-bt8xx; /bin/true; }

Actually (since I can't replicate this bug) I would like to know if disabling this ALSA module causes any subsequent problems with the sound devices/system (or is it just a fluke of hw combo that causes it to be loaded in the first place)?

Cheers,
-Dan

[Simon]

Well I've just installed my "first draft" Debian / MythTV system, after tiring of some of the limitations of Windows / DigiTV.  So far, I'm very impressed!

From the point of view of WIndows vs Linux, I can now use the computer remotely while someone is watching TV.  Considering how much use our TV gets, this is very liberating.

And Myth offers some nice features too, such as always-on timeshift and the ability to use "any" AV device as input.

Still, I have to improve the picture quality.  It seems that Myth is not performing a BOB interlace, which I find on DigiTV is the only interlace method that produces decent results on my ordinary TV.  Are other interlacing options available in MythTV?

[Simon]

Well I found the BOB interlace feature (the help text had made me think it was not what I was supposed to use).  After putting the nVidia driver into PAL mode, I now have essentially smooth video, except that it now has a little jitter every 10 seconds or so.  Still too annoying to get rid of WIndows all together.

[JimmyB]

I am about to take the plunge with my DigiTV and Gentoo/MythTV. I can write up a guide if people are interested.

[HyperReality]

FYI: It looks like support for the MT352 version of DigiTV USB (ie the latest version) has been added to the Linux DVB CVS, thanks to Patrick Boettcher.

There is also a patch for the MT352 based DigiTV PCI card available: http://www.linuxtv.o...ril/001479.html but it is yet to be committed to CVS. If anyone with an MT352 based PCI card is able to do some testing and confirm the correct operation of the patch, it would be appreciated as one the the resident bt8xx experts on the linux-dvb mailing list can then commit the change to the Linux DVB CVS tree for all to enjoy.

Lastly, if there is someone with a Nxt6000 based DigiTV USB who is willing to test out the code for those versions of DigiTV, please let us know, and we'll put Patrick in touch with you.

[kantoine]

HyperReality, on Jun 19 2005, 05:19 PM, said:

FYI: It looks like support for the MT352 version of DigiTV USB (ie the latest version) has been added to the Linux DVB CVS, thanks to Patrick Boettcher.

There is also a patch for the MT352 based DigiTV PCI card available: http://www.linuxtv.o...ril/001479.html but it is yet to be committed to CVS. If anyone with an MT352 based PCI card is able to do some testing and confirm the correct operation of the patch, it would be appreciated as one the the resident bt8xx experts on the linux-dvb mailing list can then commit the change to the Linux DVB CVS tree for all to enjoy.

Lastly, if there is someone with a Nxt6000 based DigiTV USB who is willing to test out the code for those versions of DigiTV, please let us know, and we'll put Patrick in touch with you.

<{POST_SNAPBACK}>

As I have one of these earlier cards with Nxt6000 which is recognised in Suse9.3 I would
be very happy to be a guinea pig:) I have been trying to get this to work in linux for at least 18 months.

[blah]

DJBenson, on Apr 2 2005, 04:55 PM, said:

dvb_bt8xx: unable to determine DMA core of card 0,
dvb_bt8xx: if you have the ALSA bt87x audio driver installed, try removing it.
dvb-bt8xx: probe of dvb0 failed with error -14

If you need to stop the snd_bt87x module loading or doing anythying (as opposed to
unloading it after it has loaded) you might want to try this:

options snd_bt87x enable=0

I have had my nebula working for a few years now, so I am not sure if that line actually does anything or if it is just leftover cruft in my config files from when I was first getting it working.

also I remember that the order that modules were loaded did seem to change whether it
worked or not (although I have another analogue tv card which uses bttv, and it may have been
due to that).
so anyway, what I have in my init script is:
        rmmod snd_bt87x
        modprobe bttv
        modprobe dvb-core dvb_shutdown_timeout=0;
        modprobe nxt6000
        modprobe bt878
        modprobe dvb-bt8xx

[davej]

thought I'd hit the jackpot here, finally some concrete advice.  I have worked through the steps discussed in the thread, having experienced the failure to determine the DMA core message in dmesg.  I have adjusted the sequence of loading (I have an nxt6000 version of the nebula)  and ensured that the snd_bt87x module is unloaded prior to loading the bttv etc.  

Whereas previously tvtime or xawtv would at least find a card, now xawtv -hwscan does not even detect the card.  

As a real neophyte to linux, I am pretty lost from here.  Any advice appreciated - I am happy to google my heart out (it's how I got here) and learn how to do things, but kernel and module tweaking is well beyond me - small words spoken loudly please!

I have been messing about for more than a year on and off (work permitting) to try and get this card to work under linux.  Again, any advice appreciated.

cheers

[davej]

davej, on Jan 29 2006, 08:33 PM, said:

thought I'd hit the jackpot here, finally some concrete advice.  I have worked through the

erm, is anyone else still here?

[dcallan]

Hi Dave,

I apologise for the current state of this guide. It is most likely quite out of date right now (as I am currently working in Canada right now, and have been here since mid-2005). I will be back home in June and plan to rebuild the guide at this time. Until then I will do my best to get you on the right track for the meantime.

I can make some general guesses, but to it would help if we knew what disto and kernel you are trying to do this with? Even if you just email me your whole "dmesg" output it would help me know what modules are running... anyway, here goes

davej, on Jan 29 2006, 07:33 PM, said:

having experienced the failure to determine the DMA core message in dmesg.  I have adjusted the sequence of loading (I have an nxt6000 version of the nebula)  and ensured that the snd_bt87x module is unloaded prior to loading the bttv etc.

OK, But are you getting the "success" messages in your dmesg output?

Quote

DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (NxtWave NXT6000 DVB-T)...

It is pretty much the primary outcome of all this udev/modules/kernel stuff that you end up with the following device:
/dev/dvb/adapter0/frontend0

The (NXT6000 series) nebula DVB card is made up of several common (BrookTree) media components which are often easily identified by standard driver modules. However it is all useless for DVB purposes unless the digital tuner (NXT6000) is properly initialised and working in conjunction with them - available to the system as a dvb "frontend" device.

davej, on Jan 29 2006, 07:33 PM, said:

Whereas previously tvtime or xawtv would at least find a card, now xawtv -hwscan does not even detect the card.

Unless you have downloaded a CVS snapshot of the version4 sources for xawtv, I suspect that this may be a good thing actually.
If these are the standard tvtime/xawtv packages that came with Fedora, then (IIRC) they are only intended for use with analogue tuner cards (many of which also use the bt878 chipset) and when they detect the "Brooktree" tuner device I suspect that they are mis-indentifying the Nebula as such. This is exactly what happened to me when I was first experimenting with the nebula in late 2003 (and all I got out of those apps was a whole lot of blue screens - the bttv module is answering but with no analogue tuner it has nothing to show). If it can't connect to /dev/video then it might be because it is used by dvb modules instead.

Put simply, you need to try some other software to test a DVB card.

If you try to use dvbtune or dvbstream and the nebula is not fully working, you will get an error really quick about not being able  to find any dvb "frontend" to do the tuning with. I have some very old instructions for that here: http://www.dtvforum....&hl=#entry22407  ...but you will need to do some research on what your local frequencies/PIDs are for that.
I'm sorry I don't have anything easier to follow (at hand) right now.

Other good apps to try are Xine and MythTV (although I am a year behind the times right now - so if some else can suggest a better test app for basic dvb functions, please do )

[touc]

Hi,

I'm trying to get my revision 2 DigiTV PCI card (with the MT352 chip) working under Mandriva Linux 2006 and I'm having some problems. This comes with a 2.6.12 kernel so I've upgraded to the later 2.6.14 kernel (which supports the MT352 chip). Initially I was'nt getting any frontend registered then I added the instructions as described to modprobe.conf and now it looks better but KDETV or XAWTV do not get anything. My modprobe.conf looks like:

alias eth0 sk98lin
alias sound-slot-0 snd-intel8x0
alias eth2 eth1394
install scsi_hostadapter /sbin/modprobe sata_nv; /bin/true
remove snd-intel8x0 /sbin/modprobe -r snd-pcm-oss; /sbin/modprobe --first-time -r --ignore-remove snd-intel8x0
install snd-intel8x0 /sbin/modprobe --first-time --ignore-install snd-intel8x0 && { /sbin/modprobe snd-pcm-oss; /bin/true; }
install usb-interface /sbin/modprobe ohci-hcd; /sbin/modprobe ehci-hcd; /bin/true
alias ieee1394-controller ohci1394
alias net-pf-10 off
alias net-pf-10 off
options kqemu major=0
alias eth1 sk98lin
options bttv radio=1 gbuffers=4
install bttv /sbin/modprobe --ignore-install bttv && { /sbin/modprobe dvb-bt8xx; /sbin/modprobe mt352; /bin/true; }
remove bttv { /sbin/modprobe -r dvb-bt8xx dst mt352 dvb-core; }; /sbin/modprobe -r --ignore-remove bttv

My dmesg looks like:

bttv: driver version 0.9.16 loaded
bttv: using 4 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:05:07.0[A] -> Link [LNK2] -> GSI 3 (level, low) -> IRQ 3
bttv0: Bt878 (rev 17) at 0000:05:07.0, irq: 3, latency: 32, mmio: 0xd2000000
bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem ID is 0071:0101
bttv0: using: Nebula Electronics DigiTV [card=104,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ff00cf [init]
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
bttv0: using tuner=-1
bttv0: registered device video0
ts: Compaq touchscreen protocol output
bttv0: registered device vbi0
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:05:07.1[A] -> Link [LNK2] -> GSI 3 (level, low) -> IRQ 3
bt878(0): Bt878 (rev 17) at 05:07.1, irq: 3, latency: 32, memory: 0xd2001000
DVB: registering new adapter (bttv0).
  Vendor: VIA-P	 Model: VT6205-DevB	   Rev: 2.82
  Type:   Direct-Access					  ANSI SCSI revision: 02
Attached scsi removable disk sdc at scsi4, channel 0, id 0, lun 0
  Vendor: IOMEGA	Model: ZIP 250		   Rev: 31.G
  Type:   Direct-Access					  ANSI SCSI revision: 00
  Vendor: VIA-P	 Model: VT6205-DevM	   Rev: 2.82
  Type:   Direct-Access					  ANSI SCSI revision: 02
DVB: registering frontend 0 (Zarlink MT352 DVB-T)...

Any ideas ?

Steve

[HyperReality]

You might want to have a look at this post. AFAIK, the Twinhan cards use the same linux Bt878A support as the DigiTV PCI (and other Bt878 based cards), so there may be an issue with the 2.6.14 kernel that is causing this problem for you? Maybe try the 2.6.16.9 kernel like treblid is using?

[qedqed]

Just curious, why is the topic pinned with the Nebula tag? A lot of general linux dtv info in here folks.

[dcallan]

qedqed, on Feb 19 2007, 06:53 AM, said:

Just curious, why is the topic pinned with the Nebula tag? A lot of general linux dtv info in here folks.

A lot of it is massively out of date anyway

Wondering whether it would be time to un-pin it?

I keep meaning to build another Myth box from scratch and re-write the the whole thing but have not had much time to devote to DVB stuff for the last 6 month or more    (sorry)

[qedqed]

dcallan, on Feb 19 2007, 10:33 AM, said:

A lot of it is massively out of date anyway

Wondering whether it would be time to un-pin it?

I keep meaning to build another Myth box from scratch and re-write the the whole thing but have not had much time to devote to DVB stuff for the last 6 month or more    (sorry)

I have been testing a number of DVB devices recently with a good success rate, I am looking to post the info somewhere but the category seems  a little inappropriate ;-)

Perhaps just a "Linux-2.6 Howto" ???