Wan Tat Chee schrieb: > > On Thu, 25 Apr 2002, Gunther Thoenes wrote: > > > Hello, > > now the saa7134 driver and FlyVideo 3000 works excellent. > > Whow :) > > Gunther, > > Are you using LINE2 for your TV audio input? > Please confirm. No, the saa7134 driver-code is unchanged. May be in the probe phase the driver found a AC97 on board sound chip inscription and goes fail. The chip is'nt on the board. I,ve only compile a smal new kernel. > > saa7134[0]/audio: scanning 6.500 MHz => dc is 0 [0/0] > Do you still see dc = 0 when you've tuned into a specific channel? > > saa7134[0]/audio: ctl_mute=0 automute=0 input=Television => mute=0 > > input=Television > > saa7134[0]/audio: found PAL-BGHI main sound carrier @ 0.000 MHz > > > > ^^^^^ > > it shouldn't be zero if you're tuning into a specific channel > > > > Mute = 0 means that sound is enabled. Your hint caused me to look again in the kernel config. I remembered previously saw the line after /sbin/lsmod: .... emu10k1 57504 0 (autoclean) ac97_codec 9664 0 (autoclean) [emu10k1] <<== not on my board sound 56908 0 (autoclean) [emu10k1] soundcore 3972 9 (autoclean) [saa7134 emu10k1 sound] ..... It works undisturbed as on the other OS. All code as come from bytesex.org, is unchanged compiled. Gunther
