Compro T300 and E700 video/TVcards install struggle

[wedgetail]

AS
I almost invariably start with a nice "Caputino" which is a word we have used for the way we make a very nice milky cup of coffee, it is not a real Caputino but I have grown very fond of it.

[root@KDE-mini gert]# lsmod | grep saa7134_alsa
saa7134_alsa            9415  1
snd_pcm                60446  5 snd_usb_audio,saa7134_alsa,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    43189  19 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,saa7134_alsa,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
saa7134               137245  2 saa7134_alsa,saa7134_dvb
videobuf_dma_sg         7080  3 saa7134_alsa,saa7134_dvb,saa7134
[root@KDE-mini gert]#

I had already had a look at that, sorry I should have posted the result as well but got interrupted. I have just started the system so no modprobe -r saa7134_dvb

[root@KDE-mini gert]# modprobe -r saa7134_dvb
[root@KDE-mini gert]#
[root@KDE-mini gert]# lsmod | grep saa7134_alsa
saa7134_alsa            9415  1
snd_pcm                60446  5 snd_usb_audio,saa7134_alsa,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    43189  19 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,saa7134_alsa,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
saa7134               137245  1 saa7134_alsa
videobuf_dma_sg         7080  2 saa7134_alsa,saa7134
[root@KDE-mini gert]#

Have removed the module saa7134_dvb

[root@KDE-mini gert]# modprobe -r saa7134_alsa
FATAL: Module saa7134_alsa is in use.
[root@KDE-mini gert]#

I have also been searching on the internet on the expression

FATAL: Module saa7134_alsa is in use

While I have found a couple of  interesting threads, a long one most interesting with the moderator seemingly knowing what he wanted to do and the user floundering a bit like me, in the end the thread just died. The other I did not really understand.

That aside I guess I can start by adding an option like saa7134 card=70 tuner=67 ie manhandling the card and tuner?

[AS]

While I have found a couple of  interesting threads, a long one most interesting with the moderator seemingly knowing what he wanted to do and the user floundering a bit like me, in the end the thread just died. The other I did not really understand.

That aside I guess I can start by adding an option like saa7134 card=70 tuner=67 ie manhandling the card and tuner?

Yes, that surely a possible option, provided that you use the correct values for card and tuner ....

[wedgetail]

I could not get away from the fact that 3 KDE-mini system had the same problem or seemed to behave the same. I decided it was time to get the case of the tower and start looking.  There is a card problem, I had forgotten what cards I had in this computer.  I did noticed I had two PCI cards but not the significance.

What is happening the Compro E700 is the one I have been trying to get to work, when this failed I think I borrowed a Compro T300 and that was still installed. I have been working on the wrong card as unfortunately while there were two cards only one registered and it was the T300.   In short I stuffed up really well and truly.  

Right now I have removed the Compro T300 card and only the Compro E700 is installed, this is a bit of a shocker as it hardly shows any registration apart from occupying a pci slot. So far I have no found any device file, that is a bad sign.

The full lspci listing this time,

[root@KDE-mini gert]# lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1)
02:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
04:00.0 Multimedia video controller: Micronas Semiconductor Holding AG Device 0720
05:02.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g
[root@KDE-mini gert]#

[root@KDE-mini gert]# lspci -vnn -s 04:00.0
04:00.0 Multimedia video controller [0400]: Micronas Semiconductor Holding AG Device [18c3:0720]
        Subsystem: Compro Technology, Inc. Device [185b:f000]
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at feaf0000 (32-bit, non-prefetchable) [size=64K]
        Memory at feae0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [100] Device Serial Number 00-00-00-07-20-3c-11-00
        Capabilities: [400] Virtual Channel
[root@KDE-mini gert]#

Searching dmesg gives little information apart from

[root@KDE-mini gert]# dmesg | grep 18c3
pci 0000:04:00.0: [18c3:0720] type 0 class 0x000400
[root@KDE-mini gert]#

[root@KDE-mini gert]# dmesg | grep pci
...............
pci_bus 0000:04: resource 0 [io  0x1000-0x1fff]
pci_bus 0000:04: resource 1 [mem 0xfea00000-0xfeafffff]
pci_bus 0000:04: resource 2 [mem 0xf4000000-0xf41fffff 64bit pref]
....................
[root@KDE-mini gert]#

Unfortunately this matches the following too well, unless I have missed something, can't believe there would not be some /dev/dvb similar to the other card, it is from the same company.

[root@KDE-mini gert]# ls -l /dev/dvb
ls: cannot access /dev/dvb: No such file or directory
[root@KDE-mini gert]#

[root@KDE-mini gert]# dmesg | dvb
bash: dvb: command not found
[root@KDE-mini gert]#

I am starting to get lost, but I think I need to follow up on the 18c3:0720 when I get my brains back again.  

[root@KDE-mini gert]# lspci -vvvnn -s 04:00.0
04:00.0 Multimedia video controller [0400]: Micronas Semiconductor Holding AG Device [18c3:0720]
        Subsystem: Compro Technology, Inc. Device [185b:f000]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at feaf0000 (32-bit, non-prefetchable) [size=64K]
        Region 1: Memory at feae0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [58] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Device Serial Number 00-00-00-07-20-3c-11-00
        Capabilities: [400 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-

[root@KDE-mini gert]#

[root@KDE-mini gert]# lspci -qq
..........................
04:00.0 Multimedia video controller: Micronas Semiconductor Holding AG nGene PCI-Express Multimedia Controller    
[root@KDE-mini gert]#


Checking internet for the 18c3:0720 and 185b:f000

The combination Micronas - Compro starting to look hard

04:00.0 Multimedia video controller [0400]: Micronas Semiconductor Holding AG Device [18c3:0720]
        Subsystem: Compro Technology, Inc. Device [185b:f000]

I am not sure about this nGene relationship, except when running under windows it seems this what is used. Checkin further.

[wedgetail]

I think for the moment I have got as far as I can.  My understanding is that I probably have to look at using ngene module, which is a new one for me. I have installed

[root@KDE-mini gert]# modprobe ngene
[root@KDE-mini gert]#

[root@KDE-mini gert]# dmesg |grep ngene
[root@KDE-mini gert]#

[root@KDE-mini gert]#dmesg |grep 18c3
pci 0000:04:00.0: [18c3:0720] type 0 class 0x000400
[root@KDE-mini gert]#

[root@KDE-mini gert]# lsmod |grep ngene
ngene                  19867  0
dvb_core               76614  1 ngene
i2c_core               16500  2 ngene,nvidia
[root@KDE-mini gert]#

Installing this however does not get the card registered, no sign in dmesg as far as I can see. There is a number of steps here I would like to understand.
For example when you plug in any say PCI card etc, should that not create a dynamic /dev/xxx associated with the card?  There is something fundamental I am missing.

Looking on the internet it seems that I need some firmware ngene_15.fw or ngene_17.fw
I got a zip file from a German site and it seems this contains all the 'bits' to compile firmware. That is pushing me whilst interested have think about next step. 

[AS]

Code: [Select]

modinfo ngene
the above will tell you if you need the firmware or not, if yes its filename will be listed at the beginning ...

AS

[wedgetail]

AS
Oooops, yes I should have looked at that.

[root@KDE-mini gert]# modinfo ngene
filename:       /lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/media/dvb/ngene/ngene.ko.gz
license:        GPL
wedgetail comment  no firmware
author:         Micronas, Ralph Metzler, Manfred Voelkel
description:    nGene
srcversion:     6E3C21BAF0A770637993D9D
alias:          pci:v000018C3d00000720sv00001461sd0000062Ebc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD20bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD10bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DD00bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DB02bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000DB01bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000ABC4bc*sc*i*
alias:          pci:v000018C3d00000720sv000018C3sd0000ABC3bc*sc*i*
depends:        dvb-core,i2c-core
vermagic:       2.6.38.8-pclos3.bfs SMP preempt mod_unload modversions 686
parm:           one_adapter:Use only one adapter. (int)
parm:           debug:Print debugging information. (int)
parm:           adapter_nr:DVB adapter numbers (array of short)
[root@KDE-mini gert]#

The alias numbers look very familiar in the sd column
Hmmm, since my card has slightly different sub version ID I figure until the following alias is available, no card recognition?

alias:          pci:v0000 18C3 d0000 0720 sv0000 185B sd0000 F000 bc*sc*i*

Ok, I assume no point in talking about firmware until the card is recognised?

Have I not seen somewhere it is possible to add alias's?    In modprobe.conf??


Just to follow up on your post about 'firmware' is listed at the beginning, as an example I have used following from my system

[root@KDE-mini gert]# modinfo rt61pci
filename:       /lib/modules/2.6.38.8-pclos3.bfs/kernel/drivers/net/wireless/rt2x00/rt61pci.ko.gz
license:        GPL
firmware:       rt2661.bin
firmware:       rt2561s.bin
firmware:       rt2561.bin
description:    Ralink RT61 PCI & PCMCIA Wireless LAN driver.
version:        2.3.0
author:         http://rt2x00.serialmonkey.com
srcversion:     6720A149B41740C386AC8B2
alias:          pci:v00001814d00000401sv*sd*bc*sc*i*
alias:          pci:v00001814d00000302sv*sd*bc*sc*i*   1814:0302
alias:          pci:v00001814d00000301sv*sd*bc*sc*i*
depends:        rt2x00lib,rt2x00pci,eeprom_93cx6,crc-itu-t
vermagic:       2.6.38.8-pclos3.bfs SMP preempt mod_unload modversions 686
parm:           nohwcrypt:Disable hardware encryption. (bool)
[root@KDE-mini gert]#

[root@KDE-mini gert]#lspci -vn
.............................
        05:02.0 0280: 1814:0302
        Subsystem: 1186:3a71
        Flags: bus master, slow devsel, latency 64, IRQ 22
        Memory at febf8000 (32-bit, non-prefetchable) [size=32K]
        Capabilities: [40] Power Management version 2
        Kernel driver in use: rt61pci
        Kernel modules: rt61pci
[root@KDE-mini gert]#

[wedgetail]

Pheeewww, oh boy small step closer perhaps.  Searching the net indicates that 'nGene' module is used but with varying success.

With ngene installed

[root@KDE-mini gert]# dmesg|grep  -i ngene
nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[root@KDE-mini gert]#

I modified my modprobe.conf

[root@KDE-mini gert]# cat /etc/modprobe.conf
install scsi_hostadapter /sbin/modprobe ata_piix; /sbin/modprobe ahci; /bin/true
install usb-interface /sbin/modprobe ehci_hcd; /sbin/modprobe uhci_hcd; /bin/true
alias pci:v00001814d00000302sv00001186sd00003A71bc02sc80i00 rt61pci
alias wlan0 rt61pci
alias pci:v00001969d00001026sv00001043sd00008304bc02sc00i00 atl1e
alias eth0 atl1e

alias pci:v000018C3d00000720sv0000185Bsd0000F000bc*sc*i* ngene
[root@KDE-mini gert]#

Trying to pass the 'home made' alias to ngene but I am unsure how I can confirm that this has happened.   ZZZzzzz.....  

[Just17]

AS
Thanks, I thought it was the other way, I hope I can remember for a few months.

Well with the tuner = 67 doing a w_scan

[root@KDE-mini gert]# w_scan -ft -c AU -k
w_scan version 20101204 (compiled for DVB API 5.1)
using settings for AUSTRALIA
DVB aerial
DVB-T AU
frontend_type DVB-T, channellist 3
output format kaffeine channels.dvb
Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> DVB-T "Philips TDA10046H DVB-T": good :-)
Using DVB-T frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.2
frontend Philips TDA10046H DVB-T supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO not supported, trying HIERARCHY_NONE.
FEC_AUTO
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning 7MHz frequencies...
177500: (time: 00:01)
..................
.......................
816500: (time: 04:55)
816625: (time: 04:57)

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!
[root@KDE-mini gert]#

Absolutely no frequency picked up, ZZZzzzz....

I realise the above post concerns the T300 ............  but just to comment ....  not being able to find any transponders is most often due to a lack of signal.

It seems from the above that all the hardware is working and only a signal is missing.

Correct aerial available & attached when scanned?

[wedgetail]

Just18
Yes I believe you are right, the more I have rummaged in my records I found some scans that showed at some time I did get results from Australian signals. 

I am so sure that the T300 will work that I have not yet installed it again.  I made a major mistake many months ago running two cards and from same company not really understanding the mechanism at play.  This time I am a bit better prepared but the E700 that is a hard nut to crack in Linux systems.

There is very little information about Compro E700 on the internet for Linux, though it works fine under windows.  I thought I even saw somebody writing about copying dll from windows into Linux and call it firmware.  I am keeping an eye open for info on using dll's as I travel the net.