An awesome app called Qingy (Part 1)

[rush_ad]

Code: Select all

Making all in tdfx
make[3]: Entering directory `/var/tmp/portage/DirectFB-0.9.22/work/DirectFB-0.9.22/gfxdrivers/tdfx'
if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../lib -I../../lib -I../../src  -D_REENTRANT  -I/usr/include/libmpeg3  -Wall -O3 -ffast-math -pipe -march=athlon64 -O2 -pipe -D_GNU_SOURCE  -Werror-implicit-function-declaration -MT tdfx.lo -MD -MP -MF ".deps/tdfx.Tpo" -c -o tdfx.lo tdfx.c; \
then mv -f ".deps/tdfx.Tpo" ".deps/tdfx.Plo"; else rm -f ".deps/tdfx.Tpo"; exit1; fi
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -I../../lib -I../../lib -I../../src -D_REENTRANT -I/usr/include/libmpeg3 -Wall -O3 -ffast-math -pipe -march=athlon64 -O2 -pipe -D_GNU_SOURCE -Werror-implicit-function-declaration -MT tdfx.lo -MD -MP -MF .deps/tdfx.Tpo -c tdfx.c  -fPIC -DPIC -o .libs/tdfx.o
In file included from /usr/include/linux/fb.h:4,
                 from tdfx.c:38:
/usr/include/asm/types.h:28: error: conflicting types for 'int64_t'
/usr/include/sys/types.h:194: error: previous declaration of 'int64_t' was here
/usr/include/asm/types.h:29: error: conflicting types for 'u_int64_t'
/usr/include/sys/types.h:200: error: previous declaration of 'u_int64_t' was here
make[3]: *** [tdfx.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/DirectFB-0.9.22/work/DirectFB-0.9.22/gfxdrivers/tdfx'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/DirectFB-0.9.22/work/DirectFB-0.9.22/gfxdrivers'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/DirectFB-0.9.22/work/DirectFB-0.9.22'
make: *** [all] Error 2

!!! ERROR: dev-libs/DirectFB-0.9.22 failed.
!!! Function src_compile, Line 86, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build

this error now

[hans0r]

it somehow conflicts with your kernel-headers.
which kernel-headers do you use?

[rush_ad]

i am not sure what are kernel headers. how do i find out and if thats the problem then how do i fix it

[rush_ad]

anyone got an answer for me?

[Berni]

Sorry, I don't have a real answer for you...did you try to change your Cflags (perhaps even other architecture like athlon-xp only) or try to "emerge linux-headers".

But I had a problem when I upgraded DirectFB today: The mouse didn't work anymore. The reason is, that the new versions (>0.9.21) don't poll /dev/psaux anymore, even if you use and need this device (=> serio_raw driver in 2.6.X-kernels). So if you have a special mousedevice, either use DirectFB 0.9.20 or delete the following in the sourcefile /inputdrivers/ps2mouse/psmouse.c:

Code: Select all

else if (!strncmp( uts.release, "2.6.", 4 ) || !strncmp( uts.release, "2.5.", 4 ))
          check_psaux = false;

Then, DirectFB (and Qingy) polls /dev/psaux as well as /dev/input/mice and everythinkg works fine again.

[rush_ad]

i have emerged linux-headers and that didnt help. may be trying out an old version may work. i will let you know.

[rush_ad]

here is the deal
i emerged DirectFB-0.9.21 and it compiled fine. stupid 0.9.22 gave me problems.

[Peach]

hi all, I've been using qingy for a long time, but now I must report a great problem:
I've just upgraded to gentoo-dev-sources-2.6.11-r4
once I've booted the machine nothing goes wrong as long I can log in through qingy without problems, but when I log out (doesen't mind if X or just a mere console) I get a total system freeze... that's upsetting me
any idea what I can do?
I'm trying to see if the old kernel gives me the same problem. I'll be back with a report on that.
unfortunately nothing can be catched by the logger

[s4t4n]

hi all, I've been using qingy for a long time, but now I must report a great problem:
I've just upgraded to gentoo-dev-sources-2.6.11-r4
once I've booted the machine nothing goes wrong as long I can log in through qingy without problems, but when I log out (doesen't mind if X or just a mere console) I get a total system freeze... that's upsetting me
any idea what I can do?
I'm trying to see if the old kernel gives me the same problem. I'll be back with a report on that.
unfortunately nothing can be catched by the logger

Unfortunately framebuffer is one of the most often changed areas in linux kernels, and this means that occasionally things will break. I can't really do anything about this, nor do (probably) the DirectFB folks, so you basically have two options:
- Try rebuilding DirectFB and see if things get working again
- Revert to the old kernel.

I, too, tried 2.6.11 and found it worse that 2.6.10 (it didn't hang on me, probably because I use a different framebuffer driver than you do), as bootsplash wouldn't working anymore, so happily reverted to 2.6.10. I tend to believe that a kernel that works good is better than the latest cutting edge release

[Peach]

...you basically have two options:
- Try rebuilding DirectFB and see if things get working again

I'm trying this option... let's see if something changes (I'm using DirectFB 0.9.21)

- Revert to the old kernel.

I've just tried to reboot with ye olde kernel, and the problem doesen't appear as I suspected...

I, too, tried 2.6.11 and found it worse that 2.6.10 (it didn't hang on me, probably because I use a different framebuffer driver than you do), as bootsplash wouldn't working anymore, so happily reverted to 2.6.10. I tend to believe that a kernel that works good is better than the latest cutting edge release

You're right, the upgrade-at-any-cost-habit is something I'm fighting against (myself).
Framebuffer and kernel releases are two separate thing that are compelled to live with each other, that's the real problem... hope noone else will report this problem
anyway I'm using the radeonfb drivers

[s4t4n]

anyway I'm using the radeonfb drivers

Interesting. Me, too...
Also, I'm using the open-source driver for X-Org, not the proprietary ati one. What X driver are you using?

[raylpc]

anyway I'm using the radeonfb drivers

Interesting. Me, too...
Also, I'm using the open-source driver for X-Org, not the proprietary ati one. What X driver are you using?

I have the exactly same config.

[Scorpion265]

ok, either I am on crack, or something is just not right. I have my fb running at 1280x1024 in the fb.modes, and I have the same resolution set in directfbrc... no matter what I do, the damned backgrounds are always too small for the screen. This makes the text bleed off the screen, and the buttons are in the wrong place. Can anyone please help me with this? I'd really like it to display right so I don't have to go back to agetty.

[s4t4n]

ok, either I am on crack, or something is just not right. I have my fb running at 1280x1024 in the fb.modes, and I have the same resolution set in directfbrc... no matter what I do, the damned backgrounds are always too small for the screen. This makes the text bleed off the screen, and the buttons are in the wrong place. Can anyone please help me with this? I'd really like it to display right so I don't have to go back to agetty.

That is fixed in the CVS version of qingy, that makes themes really look the same across all resolutions, even nonstandard ones like 1280x800. Have a little patience until I have time to finish the new release...

[Scorpion265]

That is fixed in the CVS version of qingy, that makes themes really look the same across all resolutions, even nonstandard ones like 1280x800. Have a little patience until I have time to finish the new release...

Thats awesome news! I'm looking forward to the update where can I monitor the major updates to the portage tree? will you be updating this thread?

[s4t4n]

Thats awesome news! I'm looking forward to the update

where can I monitor the major updates to the portage tree? will you be updating this thread?

Sorry? I'm not sure I understand your question...
When I release a new version of qingy, I also update the ebuilds in Portage, if that is what you were asking...

[Scorpion265]

I was just wondering if there is a page or something that you update when a new major release comes out, and when the portage tree is updated.

[s4t4n]

I was just wondering if there is a page or something that you update when a new major release comes out, and when the portage tree is updated.

Every time I release a new version of qingy, http://qingy.sourceforge.net/news.php gets updated, and Portage is provided with an ebuild in a matter of minutes It takes a little time to spread the new ebuild from Portage CVS repository to all the rsync mirrors, tough...

[Scorpion265]

Killer release, that fixed the issue with the themes! Thanks much!

[s4t4n]

Killer release, that fixed the issue with the themes! Thanks much!

Thanks

Note that most themes will have to be modified to take full advantage of this, expecially regarding background images...

For the non initiated, qingy 0.6.0 is out

[dencar]

I thought I'd try my favourite log-in manager, qingy-0.6.0, but got the shutdown system-freeze. I am using linux-headers-2.6.11-r1 with my favourite ck-kernel, presently 2.6.11-ck8-r1. I re-emerged DirectFB-0.9.22, to no avail. Unfortunately, it looks like it's back to kdm for the time being.

[tecknojunky]

I've been struggling making themes work with 0.5.3 because in the info file...

...As said, a theme may be a directory in `/etc/qingy/themes'. The subdirectory name will be the name of the theme.

Searching these forums I've found (lucky stroke considering the stopwords) that they in fact go into /usr/share/qingy/themes. Please fix the info file

[s4t4n]

I've been struggling making themes work with 0.5.3 because in the info file...

...As said, a theme may be a directory in `/etc/qingy/themes'. The subdirectory name will be the name of the theme.

Searching these forums I've found (lucky stroke considering the stopwords) that they in fact go into /usr/share/qingy/themes. Please fix the info file

I know, qingy info page is severely outdated, I should find the time to update (rewrite) it...
Just changed the ebuilds to point users to the more up to date source of information, which
is qingy homepage (http://qingy.sf.net)...

[rcs]

I have two questions/problems.

One is the one as described in 'Qingy touchpad "absolute" positioning problem', which talks about issues with a touchpad being treated like a touchscreen.

The second; is the splash black, then graphic initialization (with nasty colors) necessary? It happens when qingy first starts up, or when switching between consoles. I have a 1400x1050 framebuffer on beginning in very early boot, and I want to continue that all the way through.

Thank you for any responses.

[WhiteSpade]

Hey, I posted in another thread, but I have since completely re-installed my system and so I figured I would post in here which has more traffic in it. Currently, I cannot start qingy. Its set to run, but every time I start the computer I get

Code: Select all

"Unrecoverable error: reverting to text mode!"

I have run fbset and I get:

Code: Select all

fbset
mode "1024x768-206"
   #D: 297.000 MHz, H: 170.298 kHz, V: 205.6774 Hz
   geometry 1024 768 1024 768 8
   timings 3367 352 144 56 1 224 3
   vsync high
   rgba 8/0,8/0,8/0,0/0

endmode

The refresh rates seem high to me and the "rgba 8/0,8/0,8/0,0/0" seems suspicious to me. I am running this on a laptop (Inspiron 1150)
Despite the suspicious values I have already added this mode, word for word, value for value, into my /etc/fb.modes file
I have also run (as root) "qingy-DirectFB --verbose" and what I get is:

Code: Select all

qingy-DirectFB --verbose
(*) DirectFB/Core: Single Application Core. (2005-06-14 09:14)
(*) Direct/Memcpy: Using libs memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 5754)...
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 5757)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 5758)...
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (convergencec integrated media GmbH)
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and current mode is not supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0, 8/0, 0/0 (8bit)
(!) DirectFB/Core/layers: Failed to initialize layer 0!
    --> Initialization error!
(!) DirectFB/Core: Could not initialize 'layers' core!
    --> Initialization error!
Unrecoverable error: reverting to text mode!

I have already created an /etc/directfbrc file and its contents are only:

Code: Select all

mode=1024x768

I installed DirectFB with the correct USE setting

Code: Select all

USE="fbcon" emerge DirectFB

and I do have framebuffering compiled into the kernel.
I also think its worth mentioning that I am able to start and function in Fluxbox. I realize that Fluxbox is based on X so the setting would be different from those in DirectFB, but I figured it was good to mention that I do have a graphical environment functioning with more than 8 bit depth.
So, pretty much I am stumped. I am left with two things on my mind. One: I need to confirm that frame buffer support is working, so I am wondering if anyone knows of a way to test this. Two: The version in portage is version 0.5.3 and I know that 0.6.0 is released, but not in portage. Maybe my issue could be resolved with the newer version, but I doubt.
Any help or input would be greatly appreciated.
**Edit** I got fbsplash working tonight. So I know that frame buffer support is there.