You are right, I don't have Windows running on this system.I bought the card a few days ago and plugged it into my system on thursday, connected it and booted into my gentoo-linux. I had built a new kernel with the drivers compiled as modules. Hmm, I admit, that I took out an ISDN-card and put the Skystar2 into the same slot.
After booting, I tried "modprobe -v budget" (found that on the Wiki), but no card was found. Googling around, I found hints on using flexcop, but that also didn't help.
Then I came across this mailinglist with your question (and the answers from Yvan). I saw that I had the same problem and also tried your patch (and the suggestion from Yvan). I recompiled, shut down the system, plugged the Skystar2 into another slot and rebooted.
Same problem. So I asked here. After your reply I installed the kernel-modules for VMware, but didn't started vmware itself.
I let the system run over the night and on the next day, the ID was correct.Could it be that the card, still connected to the Dish, made some internal upgrade?
I do hope, that error does *not* come again :-) Ciao, Michael Zitat von Bernhard Huafbauer <huafbauer@xxxxxxxxxxxxx>:
You have bootet no windows with this card inserted? So we can say it has nothing to do at all with windows?Then, have you this card longer unused laying around (like in my case 2 years)?If yes, probably there is some mechanism that on driver installation (on windows) it runs not with the correct id ... would this make sense? I can remember some rumours that the driver with this cards writes something to the eeprom of this card ... something like following: http://www.dvbviewer.com/de/index.php?page=manual&chapter=h&sub=h3 Unter Umständen kann Ihre DVB-Karte auch für den Fernseh- undRadioempfang nachhaltig blockiert (?gelockt?) worden sein ? unglücklicherweise ist in dem B2C2-Chip der Karte eine solche Funktion vorgesehen, die sich nichtso einfach rückgängig machen lässt. Dies tritt insbesondere im Zusammenhangmit Software von EON (Europe Online) auf, in seltenen Fällen jedoch auch ausanderen, nicht genau bekannten Gründen. http://linuxtv.org/hg/v4l-dvb?f=d0e826dedcb1;file=linux/drivers/media/dvb/b2c2/flexcop-eeprom.c;style=gitweb 30 31 /* These functions could be used to unlock SkyStar2 cards. */ 32 33 static int eeprom_writeKey(struct adapter *adapter, u8 *key, u32 len) http://www.dvbportal.de/files/eonlock.chm But this is only speculation. Regards BernhardPS.: Fehler die von selbst verschwinden kommen meist auch wieder von selbst ...Am Freitag, 22. Dezember 2006 14:15 schrieb Michael Joswig:Ah, that makes sense. I remember from "the early days of linux" I had to start Windows once to use an ISDN-Card. Unfortunately I no longer have Windows on my system. But a funny thing happened today: Yesterday I installed some kernel-modules for vmware (vmnet and vmon) and left the system running. Today, when I tried to show my wife the error, I saw the correct ID. I'm not sure, if I really want to know why this happened, but the card is now working perfectly. Thanks for the support, Michael Zitat von Bernhard Huafbauer <huafbauer@xxxxxxxxxxxxx>: > Hello, > one thing I nearly forgot is, I bootet one time windows to examine > there what happens if I install the driver. > I started first a device manager by this script > set DEVMGR_SHOW_NONPRESENT_DEVICES=1 > set DEVMGR_SHOW_DETAILS=1 > start devmgmt.msc > to see which pci-ids it has currently and then if I remember correctly > it has already the correct one, and without > installing any driver, I rebooted to linux immediately. > (The windows is a old installation from 2002 and I don't remember if I had > installed there already the driver for this device in 2003) > Probably a small chance ... > > Regards > Bernhard > > > Am Donnerstag, 21. Dezember 2006 19:18 schrieb Michael Joswig: >> Yes, I read this. And I also did try reinserting. I also tried using >> another slot, but it failed every time. >> >> Don't know much about pci, and wonder how the ID could change without >> any other changes. >> >> I'll give it another few tries tomorrow, thanks. >> >> Ciao, >> Michael >> >> Zitat von Bernhard Huafbauer <huafbauer@xxxxxxxxxxxxx>: >> >> > Hello, >> > this card was working after I reinserted it another time (same pc, >> > pci-slot, operating system). >> > So I don't know why for the first time it has the wrong pci-id. (And >> > changing the driver to >> > access the wrong pci-id also didn't work either). >> > Now it's perfectly working with kernel version 2.6.18.1-kanotix-1 >> > with pci-id [13d0:2103]. >> > >> > (As mentioned earlier in >> > http://www.linuxtv.org/pipermail/linux-dvb/2006-December/014719.html) >> > >> > Kind regards >> > Bernhard >> > >> > >> > Am Donnerstag, 21. Dezember 2006 15:57 schrieb Michael Joswig: >> >> Hi, >> >> >> >> I've seen an email from Bernhard Huafbauer about a Skystar2 card which >> >> is not recognized because of a wrong(?) PCI-ID (Sat Dec 2). >> >> >> >> I have the same problem. My Technisat Skystar2 card has ID 13d0:2102. >> >> >> >> On the Flexcop-Chip is written: >> >> Technisat >> >> Flexcop IIB >> >> MMS46-000 >> >> 0607 >> >> >> >> My kernel is 2.6.18-gentoo-r4 >> >> >> >> How can I help to support this card? >> >> >> >> Ciao, >> >> Michael >> >> >> >> >> >> ---------------------------------------------------------------- >> >> This message was sent using IMP, the Internet Messaging Program. >> >> >> >> >> > >> > _______________________________________________ >> > linux-dvb mailing list >> > linux-dvb@xxxxxxxxxxx >> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > >> > >> >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program._______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Attachment:
pgp3kxlFcrm78.pgp
Description: Digitale PGP-Unterschrift
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
