An awesome app called Qingy (Part 1)

Message

s4t4n · Post by **s4t4n** » Wed Jun 21, 2006 2:32 pm

zietbukuel wrote:Nothing has changed, I can't move the damn mouse

You also forgot to mention about the kind of mouse you have...

zietbukuel · Post by **zietbukuel** » Wed Jun 21, 2006 8:40 pm

I have a microsoft intellimouse usb and ps2 compatible mouse, is that enough?

This is the output of lsusb:

Code: Select all

Bus 002 Device 003: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical

tane_stelzer · Post by **tane_stelzer** » Mon Jul 03, 2006 6:27 am

OK have emerged qingy but have some problems, firstly i have no mouse and yes i have
mouse-protocol=IMPS/2
in my directfbrc and yes i have got the gpm useflag. So does any body have any ideas for this? another problem is that the resolution si well very very low. My framebuffer is set to 1024x768 and i have alsa set that as a mode in my directfbrc? Can anybody help me out on this?
Tane

Joebel · Post by **Joebel** » Mon Jul 03, 2006 11:44 am

Qingy keeps dropping me into text mode. I hope someone over here understands what's happening.

I'm already using vesafb-tng: My boot rule in grub.conf works like

Code: Select all

  kernel (hd0,4)/boot/bzImage root=/dev/hda7 video=vesafb:ywrap,mtrr:0,1400x1050
-24@60 splash=verbose,theme:emergence CONSOLE=/dev/tty1
  initrd = /boot/fbsplash-emergence-1400x1050

That works fine. I get a nice 1400x1050 screen, with a nice splash image and all. --> vesafb-tng seems to work fine.

Using fbset I get an output, which I save into /etc/fb.modes:

Code: Select all

mode "1400x1050-60"
    # D: 122.339 MHz, H: 65.213 kHz, V: 59.993 Hz
    geometry 1400 1050 1400 2800 24
    timings 8174 238 88 33 1 150 3
    vsync high
    rgba 8/16,8/8,8/0,0/0
endmode

I create /etc/directfbrc

Code: Select all

mode=1400x1050-60
depth=24

When I boot up the bootsplash and all works fine. But qingy returns me to text mode. If i use qingy-DirectFB --verbose i get:

Code: Select all

*) Direct/Thread: Running 'Keyboard Input' (INPUT, 9506)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(!) DirectFB/FBDev: Could not mmap MMIO region (offset 0, length 0)!
    --> Invalid argument
(!) DirectFB/Core: Could not initialize 'gfxcard' core!
    --> General I/O error!
Unrecoverable error: reverting to text mode!

DAMN! On my other old laptop qingy is working fine, but here I can't get it to work. Since this "new" laptop has an ATI Technologies Inc Radeon R250 Lf card (ATI Mobility), I tried the radeonfb instead of the vesafb-tng framebuffer driver in the kernel. Issueing qingy-DirectFB --verbose with radeonfb gives me:

Code: Select all

*) Direct/Thread: Running 'Keyboard Input' (INPUT, 9490)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/RADEON: found Radeon R250 Lf [FireGL 9000]
(*) DirectFB/Graphics: ATI Radeon 0.2 (Michel Dänzer)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
(!) DirectFB/DirectFBCreate: Setting desktop buffer mode failed!
     -> No virtual resolution support or not enough memory?
        Falling back to system back buffer.
(!) DirectFB/DirectFBCreate: Setting system memory desktop back buffer failed!
     -> Using front buffer only mode.
(!) DirectFB/core/layers: Could not set primary region config!
    --> Not supported!
Unrecoverable error: reverting to text mode!
(!) [ 9486:    0.000] --> Caught signal 11 (at (nil), invalid address) <--
Killed

So now I'm lost as to what to do to get Qingy to work on this laptop. Anyone have a clue?

Joebel · Post by **Joebel** » Sat Jul 15, 2006 8:43 am

Joebel wrote:Qingy keeps dropping me into text mode. I hope someone over here understands what's happening.

{SNIPPED}

So now I'm lost as to what to do to get Qingy to work on this laptop. Anyone have a clue?

Never mind: got it working using radeonfb.

groovec · Post by **groovec** » Mon Jul 17, 2006 10:06 am

can you tell me how?
i have the same problem. allready tryed redeonfb, but it still goes into text mode.

Joebel · Post by **Joebel** » Mon Jul 17, 2006 10:38 am

groovec wrote:can you tell me how?
i have the same problem. allready tryed redeonfb, but it still goes into text mode.

Assuming that you are refering to my previous post:
- first I compiled the kernel with radeonfb ( and no other fb - no vesafb-tng).
- Then I added the correct rule and an initrd in grub.
- after booting up and seeing the correct framebuffer working, i ran recompiled DirectFB, Qingy and fbset.
- ran fbset and entered the returned info into fb.modes. directfbrc adresses that mode. set qingy theme to non-default.
- rebooted --> working graphics for qingy.

The key for me this time was: first get radeonfb working, regardless of qingy or Directfb.

When radeonfb worked, I startdd the Directfb en qingy work from scratch on, ensuring that I was working with fbset-values valid for radeonfb.

If you need grub entries of any other file-stuff, just ask.

s4t4n · Post by **s4t4n** » Mon Jul 17, 2006 11:28 am

Joebel wrote:
Joebel wrote:Qingy keeps dropping me into text mode. I hope someone over here understands what's happening.

{SNIPPED}

So now I'm lost as to what to do to get Qingy to work on this laptop. Anyone have a clue?
Never mind: got it working using radeonfb.

I will always like problems that solve themselves

groovec · Post by **groovec** » Mon Jul 17, 2006 11:47 am

thank you for the info, but it seems i have another problem :

Code: Select all

added keybinding: 'win' will switch to left tty...
added keybinding: 'menu' will switch to right tty...
added keybinding: 'ALT-p' will poweroff machine...
added keybinding: 'ALT-r' will reboot machine...
added keybinding: 'ALT-s' will activate screen saver...
added keybinding: 'ALT-z' will put machine to sleep...
added keybinding: 'CTRL-ESC' will revert to text mode...
Session locking is NOT enabled.

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

(*) DirectFB/Core: Single Application Core. (2006-07-17 10:26)
(*) Direct/Memcpy: Using SSE optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 21434)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 21435)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(!) DirectFB/FBDev: Could not mmap MMIO region (offset 0, length 0)!
    --> Invalid argument
(!) DirectFB/Core: Could not initialize 'gfxcard' core!
    --> General I/O error!
Unrecoverable error: reverting to text mode!

i had qingy running for a long time. but months ago after a update i only get into text mode.
i tryed anything, also deleting alle config files and begin from scratch.

EDIT:
i had still vesafb-tng compiled in the kernel. i removed that and the error is gone. but still not working :

Code: Select all

(*) DirectFB/Core: Single Application Core. (2006-07-17 10:26)
(*) Direct/Memcpy: Using SSE optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 11946)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 11947)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/RADEON: found RV350 [Mobility Radeon 9600 M10]
(*) DirectFB/Graphics: ATI Radeon 0.2 (Michel DXnzer)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
(!) [11943:    0.000] --> Caught signal 11 (at 0x247c8910, invalid address) <--

Joebel · Post by **Joebel** » Mon Jul 17, 2006 12:12 pm

groovec wrote:thank you for the info, but it seems i have another problem :

Code: Select all

 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(!) DirectFB/FBDev: Could not mmap MMIO region (offset 0, length 0)!
    --> Invalid argument
(!) DirectFB/Core: Could not initialize 'gfxcard' core!
    --> General I/O error!
Unrecoverable error: reverting to text mode!

Aah. That was the one I got from using vesafb-tng instead of radeonfb on an ATI-based laptop. The fact that you see this error disappear after using radeonfb (and dumping vesa from the kernel shows that going for radeonfb in this is indeed a prudent course of action.

groovec wrote: EDIT:
i had still vesafb-tng compiled in the kernel. i removed that and the error is gone. but still not working :

Code: Select all

(*) DirectFB/Core: Single Application Core. (2006-07-17 10:26)
(*) Direct/Memcpy: Using SSE optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 11946)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 11947)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/RADEON: found RV350 [Mobility Radeon 9600 M10]
(*) DirectFB/Graphics: ATI Radeon 0.2 (Michel DXnzer)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
(!) [11943:    0.000] --> Caught signal 11 (at 0x247c8910, invalid address) <--

That looks a lot like the stuff I had when initially going for radeonfb, but without setting up everything up again. Is the framebuffer stuff itself (without DirectFB apps) working allright? Do you now have a higher resolution in console mode?

If not, you might wanna consider arranging that first. That'll ensure that the radeonfb stuff is set correctly, before entering the DirectFB-realm. It that's correct, then recompiling and starting the fbset stuff might work. It did for me!

hey, I know it sounds a bit tredious. But in that sequence I finally succeeded.

groovec · Post by **groovec** » Mon Jul 17, 2006 12:53 pm

framebuffer itself is working, i have the console running in 1024x768-32@85.

fbset :

Code: Select all

mode "1024x768-85"
    # D: 98.902 MHz, H: 70.243 kHz, V: 85.454 Hz
    geometry 1024 768 1024 768 32
    timings 10111 192 32 34 14 160 6
    rgba 8/16,8/8,8/0,0/0
endmode

exact the same is in /etc/fb.modes

recompiling DirectFB fbset and qingy also did not solve the problem.

s4t4n · Post by **s4t4n** » Mon Jul 17, 2006 1:07 pm

groovec wrote:framebuffer itself is working, i have the console running in 1024x768-32@85.

fbset :
Code: Select all
mode "1024x768-85"
    # D: 98.902 MHz, H: 70.243 kHz, V: 85.454 Hz
    geometry 1024 768 1024 768 32
    timings 10111 192 32 34 14 160 6
    rgba 8/16,8/8,8/0,0/0
endmode
exact the same is in /etc/fb.modes

recompiling DirectFB fbset and qingy also did not solve the problem.

Note that I'm running DirectFB 0.9.24 (not the latest - it gives me issues).
Try putting the following in /etc/directfbrc:
mode=1024x768
depth=32
no-hardware

groovec · Post by **groovec** » Mon Jul 17, 2006 1:20 pm

I'm running the same version
i created that config with the settings but still the same problem :/
when i get home i will try to downgrade DirectFB to a version where qingy worked for me. maybe 0.9.24 is just f**ked up with my hardware.

Sachankara · Post by **Sachankara** » Sat Jul 22, 2006 6:20 pm

It's a pity that Qingy does not work with the hardened glibc.

It just terminates and returns to the normal text login. Someday in the future, I'll try to do a backtrace and a bugfix, and then submit it. But that'll have to wait for now... :/

Paczesiowa · Post by **Paczesiowa** » Mon Aug 07, 2006 10:00 pm

I try to create theme with that default gentoo wallpaper. ( http://www.gentoo.org/images/background ... 24x768.jpg ) and it looks like this: http://img107.imageshack.us/img107/193/qingy2mr6.png
(I switched background in dragonfly theme) why does this look so poor? ( looks almost like 16 colours and it't not 'sharp' ) when I view that jpg file with dfbsee it looks ok.

s4t4n · Post by **s4t4n** » Tue Aug 08, 2006 9:44 am

Paczesiowa wrote:I try to create theme with that default gentoo wallpaper. ( http://www.gentoo.org/images/background ... 24x768.jpg ) and it looks like this: http://img107.imageshack.us/img107/193/qingy2mr6.png
(I switched background in dragonfly theme) why does this look so poor? ( looks almost like 16 colours and it't not 'sharp' ) when I view that jpg file with dfbsee it looks ok.

I would say that you are running DirectFB in 16bit color depth. Try setting it to 32 bit by putting depth=32 in /etc/directfbrc

Paczesiowa · Post by **Paczesiowa** » Tue Aug 08, 2006 4:11 pm

big thx!! that worked, but it's kinda strange that i could view it properly with dfbsee which uses directfb. anyway tx:]

s4t4n · Post by **s4t4n** » Tue Aug 08, 2006 5:41 pm

Paczesiowa wrote:big thx!! that worked, but it's kinda strange that i could view it properly with dfbsee which uses directfb. anyway tx:]

Well, DirectFB allows a program to override its default settings; maybe dfbsee manages color depth directly...

Paczesiowa · Post by **Paczesiowa** » Fri Aug 11, 2006 9:48 pm

I wanted default gentoo theme but there was only picture on ur site (no theme download link) so here it is:

http://img156.imageshack.us/img156/9324/qingycf3.png

http://two.xthost.info/Paczesiowa/gentoo.rar

s4t4n · Post by **s4t4n** » Thu Aug 24, 2006 7:53 am

Paczesiowa wrote:I wanted default gentoo theme but there was only picture on ur site (no theme download link) so here it is:

http://img156.imageshack.us/img156/9324/qingycf3.png

http://two.xthost.info/Paczesiowa/gentoo.rar

I can see the screenshot and it looks nice, but I cannot download the theme from the link you provided. Can you check it please?

Paczesiowa · Post by **Paczesiowa** » Thu Aug 24, 2006 3:58 pm

sorry, crappy free file hosting:/

try this: http://rapidshare.de/files/30600231/gentoo.rar.html

btw these buttons are great because they are png with transparent background so they will work with any background ( my friend did them)

s4t4n · Post by **s4t4n** » Thu Aug 24, 2006 4:14 pm

Paczesiowa wrote:sorry, crappy free file hosting:/

try this: http://rapidshare.de/files/30600231/gentoo.rar.html

btw these buttons are great because they are png with transparent background so they will work with any background ( my friend did them)

Got it. Looks very nice

I'm interested in making it (with minor modifications) the default theme for Gentoo; do you have anything against that? Of course you will get due credits. Also, are you aware of any copyright issues with the theme graphic and font?

Paczesiowa · Post by **Paczesiowa** » Thu Aug 24, 2006 4:34 pm

I don't care that much for licenses:D I'm sure that whoever did that wallpaper, he will agree to use it in gentoo program:] and font isn't that important, I choosed it because it's the only font I know (windows user, I use desktop linux for few weeks)

and I dont want any credit, I just took already created theme, switched wallpaper and asked friend to create buttons.

s4t4n · Post by **s4t4n** » Mon Aug 28, 2006 1:41 pm

Paczesiowa wrote:I don't care that much for licenses:D I'm sure that whoever did that wallpaper, he will agree to use it in gentoo program:] and font isn't that important, I choosed it because it's the only font I know (windows user, I use desktop linux for few weeks)

and I dont want any credit, I just took already created theme, switched wallpaper and asked friend to create buttons.

Unfortunately, we cannot publish / make available items those license we cannot be sure of... The arial font, for example, afaik can only be used on a machine with a valid MS windows license...

babrodtk · Post by **babrodtk** » Wed Aug 30, 2006 12:57 am

I see a lot of people have gotten help in this thread, and I too have some difficulties getting qingy and DirectFB to talk to each another.

I have set up DirectFB to log to /var/log/directfb.log. It uses radeonfb, and works correctly

Code: Select all

# dfbsummon
(*) DirectFB/config: Parsing config file '/etc/directfbrc'.(*)

cat /var/log/directfb.log shows no errors, and I get the framebuffer to work (even mouse and keyboard

) ). If I however delete /var/log/directfb.log, and run qingy (which then should run DirectFB which should create the logfile again), the log file is not created.

Right before qingy reverts to text mode I get the following

Code: Select all

TERM environment variable not set

This is also what I get when switching between the tty's.

I am using DirectFB 0.9.24 and qingy 0.9.1.

Does anyone have an idea of what might be wrong?