2) Mhwaveedit 1.4.22 has a strange bug with vertical cursor
For example ----> start playing a sound file and then
middle button click on the window . The cursor now becomes confused
where it is located.

Hmm....it looks like that rtl2832.ko is not the right module for you....it is probably that dvb_usb_rtl28xxu.ko as you have noticed by dmesg...but the support was not there yet.
I am sorry of the misinformation.
I could post to him. He is finnish developer and last time he posted back promptly.

I too can confirm this build runs snappier and cooler on my eeepc. Something has changed in it, you can feel the difference. It is not huge, but noticeable.

This got my attention, so I had to download the new Exprimo.The cpu temp is at 48 C when idle. That is 2 degrees lower than an older version of Exprimo that I have. Setting up CPU Frequency scaling tool brings the temp down further to 40 C at idle.

There are some nice little apps that I haven't tried before.. Random Wallpaper Switcher, Lazy Fred tools, Redshift GUI. The Laptop tool looks nice: too bad I don't have a laptop to try it out on anymore

A few bug reports from some light testing..

- PAVrecord made a video file but it wouldn't play for me.. maybe it's my inexperience
- some channels work with Streamplay and others don't
- Exprimo Updater didn't seem to do anything ..perhap becuase it is already up to date?

Right-click on movie files and then choose Play Fullscreen doesn't actually play fullscreen.
Further investigation shows that it is linked to mplayershell..I am assuming that it plays full screen with the proper video driver installed. It gave me an idea however.. the pet below should play fullscreen from the get-go. I just made the pet, so some testing is needed. It works for me, though
This replaces the Rox-filer right-clicks "Play Fullscreen" with new links to /usr/bin/mplayer_fullscreen script.

ETP. I cant reproduce your problem with ext4 in hdd. It might be in conjunction with usb media . I would need to test it with usb stick.

Don570. Pfilesearch has definitively problem with /mnt/home symlink, with recent woof builds. I posted about it in Pfind thread. I can search /mnt/home when I have typed to the search path /mnt/home/ and ticked the Search for: File name box.
Mhwaveedit will be reverted back to previous version.

Anikin. I have compiled now with patched source (Thanks to rcrsn51 ) eee.ko module. Attached here. Please test and report.

Tman. I am not sure about your finding. The Play fullscreen Rox right click should be linked to the /usr/local/apps/mplayer which has inside AppRun which executes: exec mplayer -fs "$@"
....so the video files should launch mplayer in fullscreen.
Pavrecord works for me. You should tick the x11grab box if you want to record your desktop ie screencast it.

DC. I have mailed to developer Palosaari. The replies goes something like this. dvb_usb_rtl28xxu driver loads first. Then it starts to query the stick what chips it has inside and loads the corresponding drivers. rtl2832.ko for dvb-modulation and it should maybe load tuner driver and so on....Rtl2832U has also RF-tuner chip inside.
It looks like that some support is still missing. He suggested to download the latest media_build git which has latest commits. and create a new dvb framework from it.
http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers

Okay I downloaded the latest git and compiled it and made it as pet. It has the whole dvb framework with all firmwares, that is why it is big. 3.9 Mb as pet. the pet installed made my dvb-c tuner stick to work with vlc so it should not be total failure. The link to the pet is here:
http://www.smokey01.com/pemasu/Misc/dvb-update-k3.6.2-dpup-0.0.1.pet

First: remove the /lib/modules/3.6.2-dpup/kernel/drivers/media/* ....I mean media folder with all subfolders. the new build has totally different folder structure, Install the pet, it runs depmod also through pinstall.sh, reboot to be sure and test again. This latest git should have more support added to different usb id`s. It might work better. Test and report.

Tman. I am not sure about your finding. The Play fullscreen should be linked to the /usr/local/apps/mplayer which has inside AppRun which executes: exec mplayer -fs "$@"
....so the video files should launch mplayer in fullscreen.

Oh you are right. Sorry, my mistake. When I checked the link, all I saw was Mplayer, then I closed the Rox window. Later I went into /usr/share/applications/mplayer.desktop and saw that the exec option was mplayer_shell.. sorry about that. Nevertheless using exec mplayer -fs is not enough in -vo x11 mode, which is what Mplayer will default to with some video drivers. My card, for example when using the generic nv driver will not play videos in fullscreen with default Mplayer settings, until I upgrade to the Nvidia driver.
I should be more precise.. yes they play in fullscreen mode, but the videos are not stretched to fullscreen. The videos play with big black frames around them. To stretch the video in fullscreen, you need something like this: exec mplayer -fs -zoom -x 1024 -y 768.

Tman. Got it now. If the /usr/local/apps/mplayer/AppRun would run that mplayer_fullscreen script....would it fix the vo x11 problem ?

Could you change that AppRun content to reflect that change and test it...if you have the graphics which need it.
It would be simple way to change all the video formats Rox right click Play Fullscreen behavior.

You can also edit /etc/mplayer/mplayer.conf to have vo=x11 and uncomment this row: #zoom=yes

And there is also /root/.mplayer/mplayer.conf which has default vo=xv for gnome-mplayer.

Gnome-mplayer seems to obey this file /root/.config/gnome-mplayer/gnome-mplayer.confLast edited by pemasu on Wed 17 Oct 2012, 10:09; edited 1 time in total

Tman. Got it now. If the /usr/local/apps/mplayer/AppRun would run that mplayer_fullscreen script....would it fix the vo x11 problem ?

Could you change that AppRun content to reflect that change and test it...if you have the graphics which need it.

Yes you could change the Apprun content, but then the Play Fullscreen right-click would be a shortcut of a shortcut. It would link to Apprun, which would link to mplayer_fullscreen. Why not just link to it directly, by installing the pet? Yes you can change the config options, but not everyone would know how. My script finds the screen resolution, then adjusts the -zoom -x ???? -y ???? accordingly. It's a modification of Barry's mplayer_shell. What mplayer_shell does is it sets -vo xv by default, but if it finds that you have a certain video driver, it switches to -vo x11, since the other option doesn't work with all video drivers. I already made a screenshot before I read your last post, so I might as well put a link to it here.

Edit: my pet already has the Rox right-click included..it overwrites the old Play Fullscreen right-click options and replaces them with new links, but under the exact same name, so you don't have to erase the old right-click options.

Tman. I dont understand your reasoning. Here is my mplayer-fullscreen-fix-0.0.1 pet. Extract it and check contents.
Yours pet is more complicated. There is no need to change the OpenWith mime type definitions. Just the original symlinks to the /usr/local/apps/mplayer is ok. Change only the content of /usr/local/apps/mplayer/AppRun to launch mplayer_fullscreen script.

I checked the mplayer_fullscreen script. It does not point back to the /usr/local/apps/mplayer. I dont see any loops there.

You just need the original Rox right click /root/.config/rox.sourceforge.net/OpenWith/* folder contents which had those symlinks to the /usr/local/apps/mplayer to launch that AppRun content. I think this way it is simpler and in line how the Rox right clicks should work.

Use: Rox right click: Look Inside to see /usr/local/apps/mplayer content, otherwise you dont see the AppRun inside it.

Both should work..but I have only tested on my nividia GT240 card. You may notice I have extra options that are commented out, that is becuase those options have not been fully tested. The code is modified a bit, since -vo x11 only needs the -zoom option. The rest can have it included...but don't require that option to stretch the video to fullscreen.

Tman. Some notes about that script. Xvesa is nowadays as an option only in Wary...I think. Dpups, Racy etc does not have it:
no|xserver_xvesa||exe
But it does not hurt to be there.

vo=x11 has been attached to the vesa driver, that is ok,I think.
Commented rows:
About that radeon_dri.so checking I am not so sure, there is bunch of other dri drivers which will be installed by that xorg_high, for example I use i915.dri.so for dri, and vo=gl does not work for me.
That it is commented out, is good thing.

My suggestion. What about if I enable in build.... in /etc/mplayer/mplayer.conf the commented row: #zoom=yes to zoom=yes so that it is activated.

It does not hurt my vo=xv mplayer video output but zooms to fullscreen when I have vo=x11 video output.

Would that be fixing solution, when the video output defaults to vo=x11 with some graphics.

Also for gnome-mplayer, I could remove the /root/.mplayer/config file which has for gnome-mplayer the default vo=xv definition, Gnome-mplayer might work better together with that /etc/mplayer/mplayer.conf zoom=yes ....Last edited by pemasu on Wed 17 Oct 2012, 11:26; edited 1 time in total

My suggestion. What about if I enable in build.... in /etc/mplayer/mplayer.conf the commented row: #zoom=yes to zoom=yes so that it is activated.

It does not hurt my vo=xv mplayer video output but zooms to fullscreen when I have vo=x11 video output.

Would that be fixing solution, when the video output defaults to vo=x11 with some graphics.

Also for gnome-mplayer, I could remove the /root/.mplayer/mplayer.conf file which has for gnome-mplayer the default vo=xv definition, Gnome-mplayer might work better together with that /etc/mplayer/mplayer.conf zoom=yes ....

Your solution to enable zoom works for me... darn it! Too bad I didn't know about it. But that's okay, I learned a few new coding tricks while making that script. You don't need to change anything in /root/.mplayer .. The xv option for Gnome Mplayer works fine .. I think it is becuase you have mesa or xorg-high already installed. My pup doesn't come with mesa, so I had to add the x11 output to it or else the x-server would crash when launching a video. I will add mesa to my non-Lite Solidpup, since Tote reported that xv is considerably faster.

Wait a minute... why does Gnome-mplayer play in xv, and Mplayer defaults to x11? ... I think you need to edit /usr/bin/mplayer_shell, and get rid of the -vo x11 stuff, since you've got Xorg-high? preinstalled... then I don't think you need to change any other settings.

Tman. I think you need to check inside Gnome-Mplayer > Edit > Preferences and change from there the video output to xv and x11 for seeing what really works. That is the most confidential way to test it. No matter what these configuration scripts says....when you change the video output inside Gnome-Mplayer it should show you what really works.

Rebooting into another pup (Slacko 5.3.3.2) on the same stick but in an entirely different directory, I was amazed when it proceeded to increase the save file size.

Whilst this does not explain the crash the increase in the save file on another pup on the same stick is in fact normal behaviour.

When the app to increase the savefile is executed it creates a flag in the root of the drive holding initrd.gz regardless of whether
or not initrd.gz is held in a subdirectory. The file is named pupsaveresize.txt and simply contains the figure to increase the savefile by.

This flag is in no way specific to any pup and if another pup on the same stick is launched it will apply the increase and if successfull
will then delete the flag. In all fairness there is a on screen warning to re-launch the pup who's savefile you intend to increase but it would
make more sense to put the flag in the same directory as initrd is launched from and then to search in the order subdirectory/root. This would deal with both
single pups (likely to be in the root) and multiple pups (likely to be in subdirectories) on USB sticks. A matter for BK perhaps?

With regard to the crash that I experienced, I had re-booted successfully a number of times and the crash seemed to have been provoked by the
presence of the flag._________________Regards ETP

Tman. I think you need to check inside Gnome-Mplayer > Edit > Preferences and change from there the video output to xv and x11 for seeing what really works. That is the most confidential way to test it. No matter what these configuration scripts says....when you change the video output inside Gnome-Mplayer it should show you what really works.

Sorry for the late reply:
You were right, pemasu. Gnome Mplayer was not playing in xv mode, it was playing in x11 mode.
I took a look at your /root/.mplayer.conf settings:
the vo=xv option was being totally ignored, while the zoom=yes option was working. So it seems your original solution to enable zoom in /etc/mplayer/mplayer.conf is the right way to go..

The vo=??? option for gnome-mplayer looks like it sticks only when that option is in the /root/.config/gnome-mplayer.conf file.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum