Re: TV Card setup (repost) - baskitcaise, help please! :-)

From: JPB (jpb_at_email.pt)
Date: 10/02/04 

Date: Sat, 02 Oct 2004 20:44:21 +0930

baskitcaise wrote:
> JPB adjusted his/her tin foil beanie and asbestos underwear to write:
>
>
>>Nothing indicating errors that I can see. This below relates to
>>startup of the machine yesterday and is relevant to the matter being
>>discussed, I believe:
>>
>>Oct 1 18:16:16 amd kernel: agpgart: Found an AGP 2.0 compliant device
>>at 0000:00:00.0.
>>Oct 1 18:16:16 amd kernel: agpgart: Putting AGP V2 device at
>>0000:00:00.0 into 4x mode
>>Oct 1 18:16:16 amd kernel: agpgart: Putting AGP V2 device at
>>0000:01:00.0 into 4x mode
>>Oct 1 18:16:16 amd kernel: Linux video capture interface: v1.00
>>Oct 1 18:16:16 amd kernel: saa7130/34: v4l2 driver version 0.2.9
>>loaded
>>Oct 1 18:16:16 amd kernel: saa7133[0]: found at 0000:00:0b.0, rev:
>>240, irq: 11, latency: 64, mmio: 0xcfffb800
>>Oct 1 18:16:16 amd kernel: saa7133[0]: subsystem: 1043:4845, board:
>>Proteus Pro [philips reference design] [card=1,insmod option]
>>Oct 1 18:16:16 amd kernel: saa7133[0]: board init: gpio is 0
>>Oct 1 18:16:16 amd kernel: saa7133[0]: gpio: mode=0x0000000
>>in=0x0000000 out=0x0000000 [pre-init]
>>Oct 1 18:16:16 amd kernel: saa7133[0]: dsp access wait timeout
>>[bit=WRR]
>>Oct 1 18:16:16 amd kernel: saa7133[0]: dsp access wait timeout
>>[bit=WRR]
>>Oct 1 18:16:16 amd kernel: vmnet1: no IPv6 routers present
>>Oct 1 18:16:16 amd kernel: saa7133[0]: i2c eeprom 00: 43 10 45 48 54
>>20 1c 00 43 43 a9 1c 55 d2 b2 92
>>Oct 1 18:16:16 amd kernel: saa7133[0]: i2c eeprom 10: 00 ff e2 0f ff
>>20 ff ff ff ff ff ff ff ff ff ff
>>Oct 1 18:16:16 amd kernel: saa7133[0]: i2c eeprom 20: 01 40 01 02 03
>>01 01 04 08 ff 00 89 ff ff ff ff
>>Oct 1 18:16:16 amd kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff
>>ff ff ff ff ff ff ff ff ff ff ff
>>Oct 1 18:16:16 amd kernel: saa7133[0]: registered device video0
>>[v4l2]
>>Oct 1 18:16:16 amd kernel: saa7133[0]: registered device vbi0
>>Oct 1 18:16:16 amd kernel: saa7133[0]: registered device radio0
>
>
> Well after a quick look it seems that your card is being picked up as an
> saa7133 device and is loading the module and putting it on /dev/video0,
> also it is loading the radio as well on /dev/radio0

The potential problem with that could be that according to the Asus
website, the saa7133 model is NTSC - i.e. for North America, while the
7134 is supposed to be PAL.
>
>>Actually speaking of this, you may be kind enough to enlighen me of
>>something else here: Is there a way to limit the maximum size of the
>>/var/log/messages and /var/log/warn files? These two, when I checked
>>them this morning, were together taking up over 1.4Gb of hard drive
>>space! -- And most of what's in them goes like this:
>>
>>"Oct 2 10:23:35 amd kernel: SFW2-INext-ACC-TCP IN=eth1 OUT=
>>MAC=00:40:f4:29:04:c4:00:90:1a:40:bd:ac:08:00 SRC=193.217.226.190
>>DST=203.122.244.179 LEN=48 TOS=0x00 PREC=0x20 TTL=103 ID=2755 DF
>>PROTO=TCP SPT=13673 DPT=6600 WINDOW=65535 RES=0x00 SYN URGP=0 OPT
>>(0204058C01010402)"
>
>
> These are messages from your firewall and can get a bit out of hand the
> source is 193.217.226.190 destination 203.122.244.179, is the first
> number your DNS server by any chance?

No idea, really...I confess I am a bit green when it comes to these
things...

The second number belongs to my ISP, but the first one, when looked up
on reverse DNS lookup site, resolves as "revertdist-adsl.dax.net" -
which is something I've never heard of, and when attempting to contact
that site, it gives out "connection refused". I can ping it, but that's
all.

My firewall settings in Yast are set up to log critical lost packets,
but I have no idea what the message above may relate to...
>
> You can change the loglevel of the firewall to drop the messages, have a
> look in Yast>security & Users>firewall

Done.
>
>>Can't see that I need to have gigabytes of this gobbledygook on my
>>hard drive...I reckon a hundred meg or so would be plenty sufficient!
>>:-)
>
>
> You should have a cron job that runs every day/week to trim the logs
> with "logrotate", this will compress the logs and start a new one for
> you and after a set length will delete the old logs.

Well, I guess I'd better do some googling on this...all the bad old
Windows habits are coming back to haunt me... :-(

Something that as of now I have no experience with & no idea how to do
it. But that'd be a whole new thread...

>
>>/dev/video0: OK [ -device /dev/video0 ]
>> type : v4l2
>> name : Proteus Pro [philips reference
>> flags: overlay capture tuner"
>
>
> Yep there it is, but it is being seen as the Proteus this is the only
> way I could get mine working even though there was a specific
> ( manufacturer ) setting for my card it would not work.
>
> Do you get anything on xawtv or motv, best start them from the command
> line and look for errors.

I always start xawtv from the CLI, and have reproduced the output here
before. Not much help there.

>
>>file:/usr/src/linux-2.6.5-7.108/Documentation/video4linux/CARDLIST.saa7134
>> >
>> > ( that is if you are using the .108 version of the kernel )
>>
>>
>>You've lost me a little on this one; please let's elaborate on
>>that...The file in question has the following entry for my card:
>>
>>" 15 -> ASUS TV-FM 7134
>>[PCI_VENDOR_ID_ASUSTEK:4842,PCI_VENDOR_ID_ASUSTEK:4830]"
>>
>>How does this relate to your suggestion below? I can't see anything
>>corresponding to your entry - i.e. where is the card number (I presume
>>this would be "15" for my card?) and where are the options relevant to
>>the settings? That is, I understand the tuner option, but what about
>>the others?

>
>>Did you actually use a "trial and error" approach?
>
>
> Yep :) It was a case of spending a long time with google ( searching out
> the actual chip manufacturer and the chip specs, however I could have
> done it quicker if I had just tried all the options :)
>
> Whoops sorry, the above was a comment on myself not "you" :)
>
Yes, I understand that.

>>Excuse yet another silly question, then: What is the command one can
>>use to activate any change in these settings without having to reboot
>>the computer? ("Where do you want to go today?" maybe? :-))
>
>
> The easiest way is to use rmmod and insmod as root, you can use:-
>
> rmmod saa7133

This is what I get when I try that:

amd:/home/jpb # rmmod saa7133
ERROR: Module saa7133 does not exist in /proc/modules
amd:/home/jpb # rmmod saa7144
ERROR: Module saa7144 does not exist in /proc/modules

>
> As it seems to be loading the saa7133 modules to remove the loaded
> modules then make the changes to the modprobe.conf and probably run
> a :-
>
> depmod -A
>
> This will sort out any new modules and any dependencies, this just makes
> sure that if you have changed things all the related stuff is updated,
> then you can do :-
>
> insmod saa7133

amd:/home/jpb # insmod saa7144
insmod: can't read 'saa7144': No such file or directory
amd:/home/jpb # insmod saa7133
insmod: can't read 'saa7133': No such file or directory
>
> or maybe a "modprobe" instead of "insmod" ( you will know which one is
> correct :) to load the module again with the changes made, that should
> work for you with no reboot.
>
amd:/home/jpb # modprobe saa7133
FATAL: Module saa7133 not found.
amd:/home/jpb # modprobe saa7134
amd:/home/jpb #

So that seems to be working? The saa7134 is present? -- Obviously then
it is loading the correct module. But why then the insmod command says
"no such file or directory"?

>
>> > <<snip>>
>> >
>> > #YaST2 configured TV card
>> > # 2_DJ.XzkttnXJLD4:Medion 7134
>> > alias char-major-81-0 saa7134
>> > alias char-major-81-1 off
>> > alias char-major-81-2 off
>> > alias char-major-81-3 off
>> > options saa7134 card=1 gbuffers=8 gpio_tracking=1 tuner=1
>> >
>> > <<pins>>
>> >
>> > If those do not work for you then try the other "card" No`s and
>> > different tuners.
>>
>>
>>I'm happy to try that, as simply using your paragraph above in my
>>modprobe.conf did not produce the desired result - i.e. no stations
>>are found on scan still.
>
>
> Well it appears that your card is being seen as saa7133 so maybe you
> need to change the "7134" to "7133"

That still leaves the problem of the modules not perhaps being loaded
(as per terminal output above) - plus I do wonder how relevant it is in
this instance that the 7133 is supposedly only for NTSC.

>>Just explain in a slow and simple way ;-) how to use the above
>>information from kernel source docs in modprobe.conf, please. If it is
>>simply a matter of trial and error, well, then - I'm no stranger to
>>that! :-)
>
>
> The card=1 tells the module certain things about the chipset so it knows
> what type of magic to work with it :) the gbuffers option allocates
> buffers for the video to help smooth out the display, maybe you need to
> put card=15 for your card ?

Done. No result.
>
>>No worries; I feel a bit like that too. The buildup to the wet season
>>has started here in Darwin, so it is rather humid and I might need a
>>bit of a walk along the beach, as well as a coffee I've just finished,
>>to wake up! :-)
>
>
>
> Once again I would like to apologise for my somewhat late reply, it is
> just that things here are "up and down like a who^es drawers" and my
> lan is all running from cables thrown out of the window, so when it
> rains I have to shut down the network ( which it does a lot of here in
> Wales, there is no rainy "season" ), all good fun but a pain in the
> *** :)

No need to apologise. Here, it is the Northern Territory - or NT. It is
commonly nicknamed "Not Today" - because of the very laid-back pace! :-)

I appreciate all your contributions to this.

> I hope that might set you on a bit further if not then just holler and I
> will see if I can explain it a bit more.

I'll fiddle a bit more tonight and then no doubt you'll hear from me
tomorrow! :-)

Cheers,
John