Carsten Koch-Mauthe wrote:
How many Carsten Koch's are on this list now? %-) > sorry wenn ich deutsch schreibe, aber mit mein englisch ist nicht ganz > so gut. The list language is english. You have to speak english or not speak at all. > Ich versuche hier eine Hauppauge NOVA-s Karte (Technotrend TT-DVBsat > budget PCI) unter einem Suse 7.2 mit Kernel 2.4.16 zum > laufen zu bringen. Leider klappt das nicht so ganz. > Als erstes habe ich versucht den Treiber SIEMENS-DVB 0.9.3 zu benutzen. > Diesen kann ich allerdings nicht kompilieren. > Der Versuch die Treiber zu erstellen endet folgenderma�en: > > saa7146_core.c:872: parse error before > his_object_must_be_defined_as_export_objs_in_the_Makefile' This looks like you got non-printable characters in your source. Extra CRs? Did that file somehow get in touch with windoze? > dvb 232224 0 > dvb_frontend 3104 0 [dvb] > dvb_demux 13824 1 [dvb] > saa7146_v4l 14724 0 (unused) > saa7146_core 13376 0 [dvb saa7146_v4l] > tuner 4260 1 > stv0299 2688 1 > tda8083 1824 0 (unused) > SP8870 2432 0 (unused) > L64781 3360 0 (unused) > VES1820 3264 0 (unused) > VES1893 3456 0 (unused) > dmxdev 7764 1 [dvb] > dvb_filter 7232 0 [dvb] > videodev 4576 1 [dvb] > dvb_net 2752 0 [dvb] > dvbdev 1632 1 [dvb] > > Das sind die geladenen Module. Ob das alles sein mu� ? Yes, this looks OK. > Sieht ja ganz gut aus. Nur bekomme ich keine Applikation zum laufen. Ich habe tuxzap >etc. installiert, der startet auch aber z.B. tuxview haengt sich auf. Cannot help you with this. I never tried tuxview. > Starte ich den vdr hagelt es auch nur Fehlermeldungen im syslog, es erscheint aber >keinerlei Oberfl�che. vdr does not work with a nova card alone. It requires at least one full card as a primary card. Secondary card(s) can be nova cards. VDR uses the full card's OSD for its GUI, which is displayed on the TV screen, not the computer monitor. > Jan 20 21:18:06 router vdr[5286]: VDR version 0.98 started > Jan 20 21:18:06 router vdr[5286]: loading /disks/stuff/video/setup.conf > Jan 20 21:18:06 router vdr[5286]: loading /disks/stuff/video/channels.conf > Jan 20 21:18:06 router vdr[5286]: loading /disks/stuff/video/keys-pc.conf > Jan 20 21:18:06 router vdr[5286]: probing /dev/ost/frontend0 > Jan 20 21:18:06 router vdr[5288]: EIT processing thread started (pid=5288) - > master > Jan 20 21:18:06 router vdr[5286]: probing /dev/ost/frontend1 > Jan 20 21:18:06 router vdr[5286]: found 1 video device > Jan 20 21:18:06 router vdr[5286]: setting primary DVB to 1 > Jan 20 21:18:06 router vdr[5286]: switching to channel 2 > Jan 20 21:18:06 router vdr[5286]: ERROR (dvbapi.c,3074): Das Argument ist > ung�ltig > Jan 20 21:18:06 router vdr[5286]: ERROR: failed to set PIDs for channel 2 > Jan 20 21:18:06 router vdr[5286]: retrying > Jan 20 21:18:07 router vdr[5286]: ERROR: channel 2 not sync'ed on DVB card > 1! > Jan 20 21:18:07 router vdr[5286]: panic level: 0 > Jan 20 21:18:07 router vdr[5286]: retrying > Jan 20 21:18:09 router vdr[5286]: ERROR: channel 2 not sync'ed on DVB card > 1! > Jan 20 21:18:09 router vdr[5286]: panic level: 1 > Jan 20 21:18:09 router vdr[5286]: retrying > Jan 20 21:18:09 router vdr[5286]: ERROR: illegal video device handle (-1)! Klaus, I agree with Carsten here: the above messages are not very informative to say the least. Maybe it would be useful if VDR could check for a supported configuration at initialization time and issue a understandable message like "Primary card must be a full DVB-S card" or "Budget card not supported as a primary card" in a case like the above? Carsten. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
