(old)Puppy Linux Discussion Forum

mistfire wrote:I wonder if someone revised the pup-volume-monitor recently.

https://github.com/01micko/pup-volume-monitor
Latest commit f1120e1 on 18 Apr 2017

bump version to 0.1.17

@peebee

I think pup-volume-monitor showing mounted image on file managers only works on Thunar. I think someone must modify the pup-volume-monitor source code in order to support pcmanfm

@peebee

I accidentally picked your lxpupsc 18.05 (I know that is an old version). I tried to boot it up and mount a sample sfs file on /media. Surprisingly the mounted image appears on pcmanfm

mistfire wrote:@peebee

I accidentally picked your lxpupsc 18.05 (I know that is an old version). I tried to boot it up and mount a sample sfs file on /media. Surprisingly the mounted image appears on pcmanfm

Uses older versions of everything - pcmanfm, libfm, pup-volume-monitor and gvfs...........look in /root/.packages/woof-installed-packages for versions

@peebee I suggestion for you. Perform this experiment. I cant performed this experiment because of very limited data bandwidth that I have.

1. Just boot the latest lxpupsc in pristine state
2. replace the pup-volume-monitor with the old ones from version 18.05
3. Restart the pup-volume-monitor
4. mount an image file and make sure that mountpoint was on /media

if the mounted image file shown on pcmanfm. It means that pup-volume-monitor was altered.

Revert to pup-volume-monitor-0.1.15-1 - no change

Revert to pcmanfm-1.2.5 - no change

Revert to libfm-1.2.5 - behaviour changes

So probably due to the libfm changes between 1.2.5 and 1.3.1

https://git.lxde.org/gitweb/?p=lxde/libfm.git;a=summary

I wonder what changes did they made by lxde developers to libfm? If this will figured out then the pup-volume-monitor must be updated too. Just a thought

@peebee

Are we likely to see a qt desktop version of this any time soon (please)?

scsijon wrote:Are we likely to see a qt desktop version of this any time soon (please)?

Already available as a ydrv add-on:

http://www.murga-linux.com/puppy/viewto ... 39#1028739

or you can add to ScPup64.......

p.s. only adds enough Qt5 to support the desktop......other Qt5 apps may need further Qt5 elements to be added.......if there are common ones that are needed that are not too big I could add these to the ydrv......

peebee,

I am very excited about this distribution!!! I have been away from Puppy for a while and I am very happy to have found this variant.

I was wondering if you could help me figure out how to get my USB wifi dongle functioning.

It needs the driver for rtl8811au, which I think is the same as rtl8812au and rtl8821au.

it looks like maybe this should be the driver.
https://github.com/zebulon2/rtl8812au-driver-5.2.9

On ubuntu I was able to use an rtl8812 dkms package that caused it to function. Any chance you can help me figure out what I need to do here?

Also, I have a bluetooth dongle and would like to connect to my Echo Dot. the packaging says the bluetooth dongle is linux compatible.
plugable.com/products/USB-BT4LE

In the appearance changer, under options, drive icons, i get an error. I figured out I dont need this bc I can change the desktop settings to show the mounted drives. However I wanted to let you know.

Thank you so much for your work here.

Sinc - I had to make a driver for rtl8821ce, so can make you a driver for this. They are kernel specific & need kernel sources. Can you please run (in a terminal) uname -r as we need to know which kernel you are using.

EDIT: Assuming you are using the 5.1.6 stock kernel, I made a driver. Your source did not have a 5.1 kernel patch, but I found source that did. Compiled with warnings, so use at own risk. Driver here: http://s000.tinyupload.com/?file_id=344 ... 2287076113

thank you ozsouth soo much. that pet package worked perfectly. I wish i knew how to do what you did, finding the right source with the correct kernel patch. I am posting from my wifi connection right now.
thank you again for your time in helping me! i appreciate it.

I only state this so my previous post doesn't get lost. if anyone has any idea about the bluetooth dongle let me know. This is an amazing puppy variant. So clean, its really great.

ozsouth, im having one little issue with the driver for the wifi and was wondering if you have any ideas. everytime i reboot the network tool renames my wifi device. it goes from wlan0, wlan1, wlan2, ... etc. And when I save my profile it doesnt connect when i reboot bc, for instance, it will try to connect on wlan7 but my device has been renamed wlan8.
Any ideas?

Im guessing its a deadend on connecting my echot dot huh?

thanks.

I will try this and let you know how it goes with the wifi device counting.

http://www.murga-linux.com/puppy/viewto ... &start=108

Sorry sinc, I've been away - just saw your post. Definitely worth trying ifnames. Using Frisbee to connect might help too. Sorry, I know zip about bluetooth & seems I'm in sizeable company by the lack of responses.

ozsouth, thank you so much for your reply. its no problem at all. I appreciate your response. thank you again.

and by the way, adding the ifnames did not fix the issue with my wlan counting higher after each reboot. but my house was struck but lightning over the weekend and I have no internet at home at the moment (waiting for the cable company to come out and fix the lines) but I'll keep searching the threads. It looks like peebee may have dealt with some of these issues on the upupbb thread. i will try installing upupbb and see what i can do. i really like the lxde though.

14-jul-2019

Delta to 19.06+3

ISO md5 = 9dbff89a2b169c9e2851683160d69209 LxPupSc64-19.06+3-uefi-T.iso

Must be applied to: 49eaf0f6fd8bb212acd20a9894235115 LxPupSc64-19.06+0-uefi-T.iso

Updates are cumulative - only the most recent needs to be applied.

22-jul-2019

Delta to 19.06+4

ISO md5 = 21586cf6b145d07d5129acfbd6d5d749 LxPupSc64-19.06+4-uefi-T.iso

Must be applied to: 49eaf0f6fd8bb212acd20a9894235115 LxPupSc64-19.06+0-uefi-T.iso

Updates are cumulative - only the most recent needs to be applied.

Quite a lot of changes due to:
BUILD_FROM_WOOF='testing;36ae4e6f7;2019-07-16 09:25:58 +0800'

Needs initrd.gz updating as well as puppy_LxPupSc64_19.06.sfs

LxPupSc64 19.06 +4 installed from the delta on my usual i5 laptop, the Fujitsu S761. md5sum was correct, installed first pristine, then as an update of +3 with the stock kernel, then as an update of +3 with the 5.2.1 kernel. One quirk noted, save that for later.

Boot, dmesg checks, video FPS, SNS connection, sound, CPU and mem use at idle all good in all cases above. No problems running Sylpheed, Slimjet from SFS, Geany, PcManFm etc. in any case above either. Overall function seems unchanged from +2 or +3.

The quirk is that after a lidsuspend, with the stock /etc/ACPI/actions/suspend.sh or with any of my variants thereon unless a wmrestart is performed on re-awaking, the touchpad mapping is quite wonky (multiple windows generated and then the touchpad buttons lock up. So after a few clicks I need to Ctrl-Alt-Backspace and run Xwin to get going again. Then everything is fine until the next lidsuspend. I have had this behavior in the distant past (some X-Slackos IIRC) but not in a long time. +3 with any kernel doesn't exhibit this behavior, +4 with any kernel does. LxPupSc 19.06 +4 does not nor does upupdd etc.

I only have this series of i5 laptops to test on. Do you have a lappie to try a lidsuspend on?

Other than testing I seldom use the 64b LxPupSc so it's a small thing and +3 is fine in any case. I've poked at it a bit but I'm pretty time limited right now. Driving 3 hrs RT a day for a 4 minute waltz with a linear accelerator

Cheers,

Update: Now with the 5.2.3 64b kernel. Nothing changed wrt the LxPupSc64 +4 touchpad problem on wakening from a lidsuspend, suspend from shutdown GUI, or echoing mem to /sys/power/state to suspend. LxPupSc64 +3, the current LxPupSc and the current upupdd do not have this issue, no matter what kernel is used. Beats me what changed from LxPupSc64 +3 to +4. All of my usual tricks shutting down and restarting the input drivers, running flsynclient -s, etc. fail, as they did in the olden days. Only a wmrestart brings back the touchpad buttons and keeps scrolling working.

Other than that (non kernel issue), the 5.2.3 kernel is excellent in all 3 pups above. No hitches or glitches at all seen with it.

I'm running LxPupSc64 +3 in the usual directory and have +4 in the 'experimental' kennel. A small thing but I hope it doesn't spread.

Needs initrd.gz updating as well as puppy_LxPupSc64_19.06.sfs

BUILD_FROM_WOOF='testing;12111462e;2019-08-10 14:52:41 +1000'

16-aug-2019

Delta to 19.06+5

ISO md5 = 0c33e8dfcbbf6d05c945baf757ac6887 LxPupSc64-19.06+5-uefi-T.iso

Must be applied to: 49eaf0f6fd8bb212acd20a9894235115 LxPupSc64-19.06+0-uefi-T.iso

Updates are cumulative - only the most recent needs to be applied.

Also update to devx for gcc-9.2.0