James, Hartmut, I have also had "interesting" PCI ID behaviour from my Compro VideoMate, on FC4. I have seen the correct PCI ID in dmesg, but I usually get 1850:0000 (or was it 185b:0000?). I can't remember the exact ID. I've been using a modprobe.conf workaround to get the saa7134-dvb module loaded. My suspicion was that it was related to whether the machine was reset or went through a power-down. James, I have had a somewhat tortured path to getting things going also. There are many points to stumble on. But I am getting close. I have had the remote working. But perhaps like you, I get only brief periods to work on it, perhaps once overy 4 days to 2 weeks. Cheers, Mark ----- Original Message ----- From: "James Lawrence" <james.lawrence@xxxxxxxxx> To: "Hartmut Hackmann" <hartmut.hackmann@xxxxxxxxxxx> Cc: <linux-dvb@xxxxxxxxxxx> Sent: Wednesday, March 29, 2006 6:59 AM Subject: Re: Compro VideoMate DVB-T300 auto detect problem- suggested code fix > Hi Hartmut, > > Hartmut Hackmann wrote: > > > Hi, James > > > > James Lawrence wrote: > > > >> Hi Hartmut, > >> > >> I started again from the top with yet another clean install of > >> gentoo. This time the kernel version was 2.6.15r7. > >> This time, when I modprobe saa7134 the card is recognized correctly > >> with PCI ID of 185b:c900, with NO CODE MODs. > >> I have not yet tested to see if the cards actually work - I will > >> post another reply only if they do not. > >> I have not yet checked the remote control issue as I have not yet > >> got that far. I will post a reply to that message when I have tested > >> it. > >> > >> <snip> > > > > > > I forgot to reply, right? > > Ok, I removed the patch from the repository. > > > > Thanks for the info. > > Hartmut > > I saw the correct behaviour once only - now it loads with the wierd PCI > ID again. I think it is probably fair to say that the weird PCI ID is > due to some error on my computer or with my configuration so it would > not be appropriate to modify the repository. > > I was playing around trying to get sound working, which involved > compiling the kernel and loading a variety of modules. Somewhere along > that path the machine started to read the PCI ID incorrectly again. I > tried to back out to the point where it would read the PCI ID correctly > again but the incorrect behaviour has stuck. > > I don't understand the source of my difficulties but I am beginning to > wonder whether I have a flakey motherboard or whether there are > interactions going on in the software that are beyond comprehension for > my small mind. I am experiencing considerable difficulty - much more > than I have ever had before in all my years of computing and playing > around with things in the linux world I get frustrated enough each time > I look at the machine that it is at least several days before I loook at > it again. I am on the verge of unplugging everything and putting it away > for six months. > > A hint as to my latest frustrations, which have nothing to do with DVB: > I have been very carefully following instructions for installing gentoo > and documenting what works on my wiki. And yet every time I try I find > that something else goes wrong. The time before last, it took inordinate > effort to get sound working. Last time I couldn't get LVM2 to compile > (never been a problem before ...), this time I can't get the machine to > boot because it keeps trying to mount the root partition as EXT2 when it > is reiserfs (never been a problem before ... and I can't see what I have > done differently - reiserfs is compiled into the kernel). > > Arrgghh!!! > > Sorry - I needed to vent. By the way, I have not yet got as far as > testing the remote control again. > > Regards, > James. > > _______________________________________________ > > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
