From: Roman S. <sun...@gm...> - 2009-08-14 16:34:01
|
Hi! On 14.08.2009, at 16:44, Florian Tobias Schandinat wrote: > 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. > yes, it's working log: Jun 22 06:15:50 mini2133 [ 59.646904] VIA Graphics Intergration Chipset framebuffer 2.4 initializing Jun 22 06:15:50 mini2133 [ 59.727808] vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size. Jun 22 06:15:50 mini2133 [ 59.732024] Console: switching to colour frame buffer device 80x30 # grep viafb /proc/modules viafb 71840 1 - Live 0xef642000 i2c_algo_bit 4656 1 viafb, Live 0xef624000 >> 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" >> ... >> 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. # modprobe viafb viafb_accel=0 viafb_active_dev=LCD viafb_mode=1024x768 works.... log: Jun 22 06:30:01 mini2133 [ 40.666874] VIA Graphics Intergration Chipset framebuffer 2.4 initializing Jun 22 06:30:01 mini2133 [ 40.748196] vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size. Jun 22 06:30:01 mini2133 [ 40.752198] Console: switching to colour frame buffer device 128x48 # fbset -i mode "1024x768-60" # D: 64.998 MHz, H: 48.362 kHz, V: 60.002 Hz geometry 1024 768 1024 768 32 timings 15385 160 24 29 3 136 6 rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : Via Address : 0xc0000000 Size : 268435456 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 1 YWrapStep : 0 LineLength : 4096 MMIO Address: 0xfc000000 MMIO Size : 16777216 Accelerator : Unknown (50) "test color mode" - it's like lcd test : red-green-blue-grey- gradient-...etc |