Re: [Bugme-new] [Bug 13976] New: viafb + vmalloc

[Florian Tobias Schandinat <FlorianSchandinat@gmx.de>]

Hi,

thanks a lot for your testing!

Roman Sergeev schrieb:
> test # 1
> * send to kernel "vmalloc=260M"
> 
> # modprobe viafb

For my patch to fix this bug I would be interested in something like this:
* send to kernel "vmalloc=260M"
# modprobe viafb viafb_accel=0
If it is similar to the result of test #2 I could simply disable 
hardware acceleration if the second ioremap fails which is IMHO better 
than refusing to work as hardware acceleration is a nice to have but not 
crucial for device operation.

> test # 2
> * send to kernel "vmalloc=300M"
> * modprobe viafb
> * loaded ok
> 
> status:
> # grep viafb /proc/modules
> viafb 71840 1 - Live 0xece42000
> i2c_algo_bit 4656 1 viafb, Live 0xece24000
> 
> log:
> Jun 21 23:52:12 mini2133 [   47.308459] VIA Graphics Intergration 
> Chipset framebuffer 2.4 initializing
> Jun 21 23:52:12 mini2133 [   47.393518] Console: switching to colour 
> frame buffer device 80x30
> 
> but i see "test color mode"
> 
> fbset -i
> 
> mode "640x480-60"
>     # D: 25.175 MHz, H: 31.469 kHz, V: 59.940 Hz
>     geometry 640 480 640 480 32
>     timings 39722 48 16 33 10 96 2
>     accel true
>     rgba 8/16,8/8,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : Via
>     Address     : 0xc0000000
>     Size        : 268156928
>     Type        : PACKED PIXELS
>     Visual      : TRUECOLOR
>     XPanStep    : 0
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 2560
>     MMIO Address: 0xfc000000
>     MMIO Size   : 16777216
>     Accelerator : Unknown (50)
> 
> if i loading  module with parametrs "modprobe viafb viafb_mode=800x600 
> viafb_refresh=60"
> they still go "test color mode"
> log:
> Jun 22 00:28:11 mini2133 [  142.994541] VIA Graphics Intergration 
> Chipset framebuffer 2.4 initializing
> Jun 22 00:28:11 mini2133 [  143.079079] Console: switching to colour 
> frame buffer device 100x37

This looks fine. I'd guess the driver itself is working. Unfortunately I 
do not fully understand the term "test color mode". Can you describe 
what you see? monocolor, if yes what color or some strange patterns? 
even whether it is shown immediately or is somehow slowly painted might 
help.

Perhaps using the module parameter viafb_active_dev= with one of CRT, 
DVI or LCD helps?
If it doesn't....well I'm aware of one bug in that code that I hit on my 
netbook. Will send you a fix if your observations sound related.

> ps: other \ standart  kernel framebuffer module on this card works well

Yeah, the problem we now hit is some monitor misconfiguration but as the 
standard vga/vesa driver does not really know about those device 
specific things that's expected.


Thanks,

Florian Tobias Schandinat

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july