SEO

Hello guys,

I'm trying to make Qingy work at my "favorite" resolution (1024x768),
but even if I tried to follow suggestions

http://gentoo-wiki.com/HOWTO_Qingy
http://qingy.sourceforge.net/faq.php
http://forums.gentoo.org/viewtopic-t...ght-qingy.html

and even if now my qingy seems to be correctly set

askar@athena ~ $ grep qingy /etc/inittab
c2:2345:respawn:/sbin/qingy tty2 -n

askar@athena ~ $ cat /etc/fb.modes
mode "1024x768-60"
# D: 64.033 MHz, H: 47.714 kHz, V: 60.018 Hz
geometry 1024 768 1024 3072 16
timings 15617 159 52 23 1 107 3
vsync high
rgba 5/11,6/5,5/0,0/0
endmode

askar@athena ~ $ cat /etc/directfbrc
mode=1024x768-60
depth=16

I'm still having qingy starting at only 640x480x8 resolution. I can't
either have more output from qingy in order to see what's happening...
uhmpf :S

help

askar.bektassov@gmail.com wrote:
> Hello guys,
>
> I'm trying to make Qingy work at my "favorite" resolution (1024x768),
> but even if I tried to follow suggestions
>
[chop]
> askar@athena ~ $ cat /etc/fb.modes
> mode "1024x768-60"
> # D: 64.033 MHz, H: 47.714 kHz, V: 60.018 Hz
> geometry 1024 768 1024 3072 16
> timings 15617 159 52 23 1 107 3
> vsync high
> rgba 5/11,6/5,5/0,0/0
> endmode

Does "fbset" report the same? (emerge sys-apps/fbset if you don't have it)

How about "ls -l /dev/fb*"?

If neither are successful, chances are you need to recompile your kernel
with framebuffer support, and remove any special hardware drivers that are
incompatible with framebuffer support.

Regards,
--
*Art

Hello Arthur,

thanks for reply and yes, fbset reports the same, since I used output
of fbset to fill fb.modes file. Here are my fb dev files

askar@athena ~ $ ls /dev/fb* -l
lrwxrwxrwx 1 root root 4 May 3 19:13 /dev/fb0 -> fb/0
crw-rw---- 1 root video 29, 1 Feb 13 19:03 /dev/fb1
crw-rw---- 1 root video 29, 2 Feb 13 19:03 /dev/fb2
crw-rw---- 1 root video 29, 3 Feb 13 19:03 /dev/fb3
crw-rw---- 1 root video 29, 4 Feb 13 19:03 /dev/fb4
crw-rw---- 1 root video 29, 5 Feb 13 19:03 /dev/fb5
crw-rw---- 1 root video 29, 6 Feb 13 19:03 /dev/fb6
crw-rw---- 1 root video 29, 7 Feb 13 19:03 /dev/fb7
crw-rw---- 1 root root 10, 63 Apr 13 21:01 /dev/fbsplash

/dev/fb:
total 0
crw-rw---- 1 root video 29, 0 Apr 13 21:01 0

I wouldn't mind to recompile the kernel; but the fact is that
everything else works correctly, including the nice livecd-2006.0
gensplash theme.

And which would be the special hardware drivers that are incompatible
with fb?! Currently I use simple vesafb... and disabled all the others.

askar.bektassov@gmail.com wrote:
>
> And which would be the special hardware drivers that are incompatible
> with fb?! Currently I use simple vesafb... and disabled all the
> others.

vesafb should work fine, in addition to those listed here:
http://www.directfb.org/index.php?pa...ort%2FGraphics

Other than that, have you tried changing the line in /etc/directfbrc to read
just "mode = 1024x768" instead of "mode = 1024x768-60"? The -60 is only
supported for vesafb-tng and vesafb for kernels >= 2.6.13, and might not
work with the gentoo-supplied directfb apps?

Regards,
--
*Art

Yep, initially I tried with simple 1024x768 I'm not sure of this, but
then I thought that the mode is just a descriptive string, so there
could also be

mode "bah"
...
endmode

in /etc/fb.modes and

mode=bah

in /etc/directfbrc

by the way still nothing. And can't figure out either how to get
more information from qingy, when I start it with -v flag, it just says
which keys are mapped to which actions, and nothing about resolution.
Also it is strange, but should directfb query /etc/fb.modes in order to
start a mode? and actually my fb.modes contains a single entry in. Here
is my dfbdump output

askar@athena ~ $ cat dfbdump
(*) DirectFB/Config: Parsing config file '/etc/directfbrc'.

---------------------- DirectFB v0.9.22 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
-----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2006-04-17 04:19)
(*) Direct/Memcpy: Using SSE optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 8771)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 8772)...
(!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence
integrated media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)

DirectFB uptime: 00:00:00

-----------------------------[ Surfaces
]-------------------------------
Reference . Refs Width Height Format Video System
Capabilities
------------------------------------------------------------------------
------ ------
0k 0k -> 0k total

----------------------------------[ Contexts of Layer 0
]-----------------------------------
Reference . Refs Width Height Format Location on screen Regions
Active Info Level
--------------------------------------------------------------------------------------------
N/A : 1 1024 x 768 RGB16 0.0, 0.0 -> 1.0, 1.0 0
(*) SHARED N/A