[Marvel-linux] Re: Kernel Konfusion! + 2. Re: Kernel Konfusion! (Martin Collins) + 3. Still Audio problems and other bugs

[boer K. <boe...@my...>]

> Message: 1
> Date: Tue, 28 Sep 2004 14:58:13 +0100
> From: ljones <lj...@li...>
> To:  mar...@li...
> Subject: [Marvel-linux] Kernel Konfusion!
> 
> I've recently decided to try to pick up on this again (i.e. patching
> the linx kernel and compliing the mgavideo capture driver) just
> recently, but I'm still having quite a few problems. Firstly, there's
> the problem of kernels. The driver_fb from CVS contains patches for
> versions 2.6.0 and 2.6.7, but neither of these work with Mandrake 10
> official as it uses 2.6.3-7mdk. I've also found neither of these
> kernel patches work with the kernel source supplied on the mandrake
> CDs. After using the 2.6.7 patch I get this:
> 
> 
> # patch -p1 < /home/aaaaa/mga/driver_fb/kernel-2.6.7.patch
> 
> patching file drivers/video/matrox/i2c-matroxfb.c
> Hunk #1 FAILED at 91.
> 1 out of 1 hunk FAILED -- saving rejects to file 
> drivers/video/matrox/i2c-matroxfb.c.rej
> patching file drivers/media/video/msp3400.c
> Hunk #1 FAILED at 1421.
> 1 out of 1 hunk FAILED -- saving rejects to file 
> drivers/media/video/msp3400.c.rej
> 
> Or after using the 2.6.0 patch I get this;
> 
> # patch -p1 < /home/aaaaa/mga/driver_fb/kernel-2.6.0.patch
> 
> patching file drivers/i2c/algos/i2c-algo-bit.c
> Hunk #1 succeeded at 383 (offset 4 lines).
> Hunk #2 succeeded at 401 (offset 4 lines).
> patching file drivers/media/video/msp3400.c
> Hunk #1 succeeded at 456 (offset -4 lines).
> Hunk #2 succeeded at 580 (offset -4 lines).
> Hunk #3 succeeded at 1410 (offset -35 lines).
> patching file drivers/video/matrox/i2c-matroxfb.c
> Reversed (or previously applied) patch detected!  Assume -R? [n]
> Apply anyway? [n]
> Skipping patch.
> 1 out of 1 hunk ignored -- saving rejects to file 
> drivers/video/matrox/i2c-matroxfb.c.rej
> patching file drivers/video/matrox/matroxfb_maven.c
> Hunk #1 FAILED at 1249.
> 1 out of 1 hunk FAILED -- saving rejects to file 
> drivers/video/matrox/matroxfb_maven.c.rej
> 
> I'm not entirely sure what all this means but I'm guessing its because
> 
> the kernel versions differ?
That's quite right, as Martin pointed out. However, a vanilla 2.6.8
patched to 2.6.9-rc2 appears to accept the 2.6.7 patch from
driver_fb. I have no experience with the mgatv code.


> From: Marco Gusy <pic...@ya...>
> To: mar...@li...
> Date: Wed, 29 Sep 2004 00:28:38 +0200
> Subject: [Marvel-linux] Still Audio problems and other bugs
> 
> Hi all, i use a lot the tv capabilities of my marvel g400. It worked
> great on my mandrake 9.2. When I installed gentoo i had no way to make
> it work on a 2.4.26 kernel. I then tried the 2.6.8 r4 gentoo kernel...
> but looks like there are a lot of bugs.

Actually, it does work on 2.4-series kernels, but it's quite difficult
to get it work as you have to load framebuffer modules in the right
order, and change the iv script. You need the official driver for this
one, I used the 11b version. If you want details on how to configure
your kernel, and on what to load in what order etc, I'll be happy to
post my kernel.config and relevant startup scripts.

As mentioned above, 2.6.9-rc2+driver_fb works excellent in my setup.

> 
> -Audio doesn't work sometimes when I change channel (the marvel switch
> off audio). This happens always when I repeat lavrec on a channel for
> the 2nd time and so on. I noticed I can restore this volume on by
> starting xawtv and press the "+" key... but i can't understand which
> volume it refers to. (yes, I patched the kernel as from readme)
> -(workaroundable)Xawtv shows pink garbage when i open it for the first
> time, i have to switch to composite input and then tv to get the right
> picture.-(workaroundable)Screen corruption when module starts (also in
> console mode). Yes, I know you warned about this: but the 2.4 version
> didn't behave like 2.6... so I wish it could be fixed. One note: if i
> put the driver_fb modules in autostart the console disappears in a
> green screen mess irreversibly.
> 
> I wish i could code something to help you, but I don't speak c
> language :-\
> 
> Thanks for the driver!
Thanks to the devvers from me too!
Wicher