LxPupSc64 - 64bit version of Puppy with the LXDE desktop
ROX in LxPupSc
G'day peebee,
My apologies for the lack of clarity in my post about my inability to set up ROX as I like it in your latest 64-bit LxPupSc.
That Rox (as the fortunate-for-me fallback in your LxPupSc Pups) doesn't allow movement of the column lay-out from the default.
So I ran woodenshoe-wi's modified 64-bit ROX pet in the hope of a lay-out fix.
I could move the columns with this pet installed but not permanently as each new ROX opened had the old default lay-out.
And I had forgotten that you meant this Pup series to prefer a non-ROX+non-JWM environment; I've been using the previous Pup's savefile with each recent updated version so miss the original first-start-up that earlier I had switched away from each time.
I'm sorry to say I find LXDE and PcManFM a bit too different and cumbersome compared to ROX/JWM - perhaps, it's just a case of the 'devils I know'.
Like you, I would like to see from someone interested, a full 64-bit BionicPup to complement your very nice 32-bit versions.
David S.
Postscript:
Just now, I tried an old 32-bit ROX (that is good in 32-bit Pups with an intractable ROX) in an LxPupSc1806(+3) but the result was not too good (screenshot) .
So renewing the Pup's savefile and rebooting, in this same Pup, I then tried a 64-bit ROX from another 64-bit Pup (BK's Werewolf) that has my desired default lay-out.
And now it's 'all good' (screenshot).
The good ROX file (ROX-Filer) I put in the directory /usr/local/apps/ROX-Filer/ , running from a sym-link (screenshot). I could have just copied it over the original ROX-Filer.
So now I have fixes for my minor issues with LxPupSc64 while using it in not quite the expected way .
My apologies for the lack of clarity in my post about my inability to set up ROX as I like it in your latest 64-bit LxPupSc.
That Rox (as the fortunate-for-me fallback in your LxPupSc Pups) doesn't allow movement of the column lay-out from the default.
So I ran woodenshoe-wi's modified 64-bit ROX pet in the hope of a lay-out fix.
I could move the columns with this pet installed but not permanently as each new ROX opened had the old default lay-out.
And I had forgotten that you meant this Pup series to prefer a non-ROX+non-JWM environment; I've been using the previous Pup's savefile with each recent updated version so miss the original first-start-up that earlier I had switched away from each time.
I'm sorry to say I find LXDE and PcManFM a bit too different and cumbersome compared to ROX/JWM - perhaps, it's just a case of the 'devils I know'.
Like you, I would like to see from someone interested, a full 64-bit BionicPup to complement your very nice 32-bit versions.
David S.
Postscript:
Just now, I tried an old 32-bit ROX (that is good in 32-bit Pups with an intractable ROX) in an LxPupSc1806(+3) but the result was not too good (screenshot) .
So renewing the Pup's savefile and rebooting, in this same Pup, I then tried a 64-bit ROX from another 64-bit Pup (BK's Werewolf) that has my desired default lay-out.
And now it's 'all good' (screenshot).
The good ROX file (ROX-Filer) I put in the directory /usr/local/apps/ROX-Filer/ , running from a sym-link (screenshot). I could have just copied it over the original ROX-Filer.
So now I have fixes for my minor issues with LxPupSc64 while using it in not quite the expected way .
- Attachments
-
- 32bitRox-in-64bitPup.jpg
- Ooops! Trying a 32-bit Rox-Filer in 64-bit Pup not good.
- (85.64 KiB) Downloaded 1065 times
-
- 64bitRoxfixed.jpg
- Werewolf Rox in use - good lay-out and pinboard as normal
- (127.53 KiB) Downloaded 1069 times
-
- NewRoxFiler-linked.jpg
- using a link to the Werewolf file in the same directory
- (29.6 KiB) Downloaded 1065 times
Interim delta to 18.06+6
iso md5 = 91e58da5e4a7ef5d29c4befe06ffe04f lxpupsc64-18.06+6.iso
Just Slackware64 Current updates
Later 64-bit kernels (4.18.x) are available
iso md5 = 91e58da5e4a7ef5d29c4befe06ffe04f lxpupsc64-18.06+6.iso
Just Slackware64 Current updates
Later 64-bit kernels (4.18.x) are available
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Interim delta to 18.06+7
iso md5 = b64f4891e0196221dc210be00712164a lxpupsc64-18.06+7.iso
Just Slackware64 Current updates to Wed Sep 12 21:19:38 UTC 2018
inc. OpenSSL: 1.1.1 11 Sep 2018, built on: Wed Sep 12 19:59:38 2018 UTC
Later 64-bit kernels (4.18.x) are available
iso md5 = b64f4891e0196221dc210be00712164a lxpupsc64-18.06+7.iso
Just Slackware64 Current updates to Wed Sep 12 21:19:38 UTC 2018
inc. OpenSSL: 1.1.1 11 Sep 2018, built on: Wed Sep 12 19:59:38 2018 UTC
Later 64-bit kernels (4.18.x) are available
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
pcmanfm
PCMANFM is displaying chronic freezes on LxPupSc64.
I've reinstalled several times (frugally) with the same result.
This seems to happen when i open a second tab and then try to switch back to the first...
Any help would be appreciated with this very fine pup.
I've reinstalled several times (frugally) with the same result.
This seems to happen when i open a second tab and then try to switch back to the first...
Any help would be appreciated with this very fine pup.
Which version of LxPupSc64 are you using, & which kernel? I am using 18.03 with 4.14.47 kernel, & can open several tabs & switch between. (in a terminal, uname -r will give kernel detail). Could also be a video issue - trying the modesetting driver may help. (exit to prompt, run xorgwizard, select modesetting & run xwin).
I'm running lxpup64 18.06 +7 with the latest 4.18.9 64b kernel on this hardware, using the intel driver:
System: Host: puppypc395 Kernel: 4.18.9-lxpup64 x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
Mobo: FUJITSU model: FJNB225 serial: N/A
UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery CMB1: charge: 51.5 Wh 100.0% condition: 51.5/62.2 Wh (83%)
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 797/2501 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.Org 1.20.1 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
Resolution: 1366x768@60.00hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.2.0
Network: Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 120.0GB (40.6% used)
Weather: Weather data failure: Thu Sep 20 20:48:28 CDT 2018
Error: location server up but download error - wget: 4
Info: Processes: 153 Uptime: 2 min Memory: 209.6/4787.8MB Client: Shell (bash) inxi: 2.3.40
No issues switching between tabs on pcmanfm seen. Screenshot below...
Edit: weather in inxi worked later. Probably just slow server -violent storms here tonight-
System: Host: puppypc395 Kernel: 4.18.9-lxpup64 x86_64 bits: 64 Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
Mobo: FUJITSU model: FJNB225 serial: N/A
UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery CMB1: charge: 51.5 Wh 100.0% condition: 51.5/62.2 Wh (83%)
CPU: Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 797/2501 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
Display Server: X.Org 1.20.1 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
Resolution: 1366x768@60.00hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.2.0
Network: Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 120.0GB (40.6% used)
Weather: Weather data failure: Thu Sep 20 20:48:28 CDT 2018
Error: location server up but download error - wget: 4
Info: Processes: 153 Uptime: 2 min Memory: 209.6/4787.8MB Client: Shell (bash) inxi: 2.3.40
No issues switching between tabs on pcmanfm seen. Screenshot below...
Edit: weather in inxi worked later. Probably just slow server -violent storms here tonight-
- Attachments
-
- Screenshot.png
- (243.44 KiB) Downloaded 782 times
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Interim delta to 18.06+8
iso md5 = caac51733f4afe70fe27dad17c6d6dbf lxpupsc64-18.06+8.iso
Just Slackware64 Current updates to Fri Sep 21 18:51:07 UTC 2018
Later 64-bit kernels (4.18.x) are available
iso md5 = caac51733f4afe70fe27dad17c6d6dbf lxpupsc64-18.06+8.iso
Just Slackware64 Current updates to Fri Sep 21 18:51:07 UTC 2018
Later 64-bit kernels (4.18.x) are available
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Interim delta to 18.06+9-uefi
iso md5 = ec8f0d43b32df96ee6f5fb659c4feeb3 lxpupsc64-18.06+9-uefi.iso
Just Slackware64 Current updates to Fri Sep 28 03:55:56 UTC 2018
+ now a uefi bootable iso (? not tested)
Later 64-bit kernels (4.18.x) are available
iso md5 = ec8f0d43b32df96ee6f5fb659c4feeb3 lxpupsc64-18.06+9-uefi.iso
Just Slackware64 Current updates to Fri Sep 28 03:55:56 UTC 2018
+ now a uefi bootable iso (? not tested)
Later 64-bit kernels (4.18.x) are available
Last edited by peebee on Sat 06 Oct 2018, 09:20, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hi peebeepeebee wrote:+ now a uefi bootable iso (? not tested)
I love that you took the effort to make your iso this way!!
It would be nice if this behaviour were standard for Puppy builds (woof CE builds).
Imo it makes Puppy more easily portable and more usable for new users.
(Regulars probably do a frugal install with grub4dos manually and switch the machine to legacy boot in the bios.
Or they put it on the HD directly and use one of many ways to boot it from there, legacy or uefi.)
So I've tested it.
I put the iso on a pendrive with the dd command and tried to boot it on my uefi laptop.
The pendrive was recognised as uefi bootable in the bios as well as legacy bootable. (The laptop supports legacy boot as well.)
Booting succeeded for both! YES!
I went one step further and created pupsave.
First I used the fix-usb.sh to make a third partition on the pendrive, ext3.
I had to disable the exit after the sanity check for 3rd partition empty. I do not know why it says there is something on the 3rd partition.
Then I saved a pupsavefolder to this partition. But on reboot it was not found.
I put another pupsavefolder on the root of an ext3 partition on the ssd/HD. There the pupsave was found and loaded.
If one could put the pupsave on the same stick as the Puppy and have it used, one would have a even more portable Puppy.
So I tried to add puppy boot param.
That should be possible with F2 when the boot screen comes up in legacy boot, but on that moment there is an error in red displaying "DESKTOP FAIL: Black-screen/hangs... " and it is not possible to add anything.
Instead I tried by editing (e) the kernel line, both in eufi (grub2?) and legacy (syslinux?). There I added psave=sdb3 and booted. And that worked!
Would there be a way to avoid this workaround and to have Puppy looking for fitting pupsaves everywhere?
Might have been a "Lost & Found" folder. I think gparted sometimes (always?) creates one when you resize/create a new partition.foxpup wrote:...
First I used the fix-usb.sh to make a third partition on the pendrive, ext3.
I had to disable the exit after the sanity check for 3rd partition empty. I do not know why it says there is something on the 3rd partition...
Could be, though I did not use gparted. Gparted does not handle these pendrives well after dd; gparted is completely clueless; ROX handles it better.mikeslr wrote:Might have been a "Lost & Found" folder.
Reminds me that I left some small thing out of my little howto:
After using fix-usb.sh one has to make the filesystem (mkfs ...) as fix-usb says. If not, you still do not 'see' the third partition.
Mike, you have an idea how to accomplish this:
It has to happen in the init, doesn't it?to have Puppy looking for fitting pupsaves everywhere?
Search for SaveFile/Folder
Hi foxpup,
Sorry. I know little about init, and even less about USB-OSes created by dd.
mikesLr
Sorry. I know little about init, and even less about USB-OSes created by dd.
mikesLr
Re: Search for SaveFile/Folder
Me neither, just investigating ... and guessingmikeslr wrote:Hi foxpup,
Sorry. I know little about init, and even less about USB-OSes created by dd.
mikesLr
LxPupSc64 - 64bit version of Puppy with the LXDE desktop
Installed 18.06+9-uefi to the hard drive of HP desktop:
System: Host: puppypc9263 Kernel: 4.17.0-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial: MXX232077R
Mobo: Foxconn model: 2ADA v: 1.00 BIOS: AMI v: 7.12 date: 06/07/2012
CPU: Quad core Intel Core i5-3550 (-MCP-) speed/max: 1602/3301 MHz
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
Display Server: X.org 1.20.1 driver: intel tty size: 180x31 Advanced Data: N/A for root
Network: Card-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 2000.4GB (1.0% used)
Weather: Conditions: 72 F (22 C) - Mostly Cloudy Time: October 11, 5:05 PM EDT
Info: Processes: 146 Uptime: 1:22 Memory: 372.2/11901.7MB Client: Shell (bash) inxi: 2.3.8
Added Kpat and Smplayer/Smtube,no luck with Kodi.
Added Chromium64_69.0.3497.100+pepper_31.0.0.122_lx_spot.sfs
Thanks.
System: Host: puppypc9263 Kernel: 4.17.0-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.06
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial: MXX232077R
Mobo: Foxconn model: 2ADA v: 1.00 BIOS: AMI v: 7.12 date: 06/07/2012
CPU: Quad core Intel Core i5-3550 (-MCP-) speed/max: 1602/3301 MHz
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
Display Server: X.org 1.20.1 driver: intel tty size: 180x31 Advanced Data: N/A for root
Network: Card-1: Ralink RT5390 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 2000.4GB (1.0% used)
Weather: Conditions: 72 F (22 C) - Mostly Cloudy Time: October 11, 5:05 PM EDT
Info: Processes: 146 Uptime: 1:22 Memory: 372.2/11901.7MB Client: Shell (bash) inxi: 2.3.8
Added Kpat and Smplayer/Smtube,no luck with Kodi.
Added Chromium64_69.0.3497.100+pepper_31.0.0.122_lx_spot.sfs
Thanks.
- Attachments
-
- screenshot.jpg
- (47.82 KiB) Downloaded 1115 times
Video issue
I have had trouble playing some videos via seamonkey 2.49.4 - works fine in Slacko64-6.9.9.9, Xenialpup64 7.5, Bionicpup64 7.9.5. Video advances to (at best) advert and stops, sometimes locking up. Main site I've noticed is afl.com.au (any video in middle of page). Have tried adding extra gtk3 packages, changing about:config, turning off acceleration - no avail. Versions of Palemoon before 28.0 & supplied Light browser work. Any ideas?
EDIT: this is a GTK3 problem. Seamonkey64-2.48 (gtk2) works fine. If only it was secure.
EDIT2: apulse libs are in /usr/lib64 - apulse executable points to /usr/lib/64/apulse folder. When moved there, videos work!
.
EDIT: this is a GTK3 problem. Seamonkey64-2.48 (gtk2) works fine. If only it was secure.
EDIT2: apulse libs are in /usr/lib64 - apulse executable points to /usr/lib/64/apulse folder. When moved there, videos work!
.
Last edited by ozsouth on Fri 02 Nov 2018, 00:50, edited 2 times in total.
Interim delta to 18.06+11-uefi
iso md5 = 29fe9aa0fe97a5db3840f1ff2079be1e lxpupsc64-18.06+11-uefi.iso
Just Slackware64 Current updates to Sat Oct 27 18:22:46 UTC 2018 + reversion to pup-volume-monitor-0.1.15
Later 64-bit kernels (4.19.x) are available
iso md5 = 29fe9aa0fe97a5db3840f1ff2079be1e lxpupsc64-18.06+11-uefi.iso
Just Slackware64 Current updates to Sat Oct 27 18:22:46 UTC 2018 + reversion to pup-volume-monitor-0.1.15
Later 64-bit kernels (4.19.x) are available
Last edited by peebee on Mon 29 Oct 2018, 15:34, edited 2 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Mounted volumes disappear from desktop and pcmanfm panel when attach external drive (pcmanfm bookmarks remain and function though).
Since about k 4.18.10 (through subsequent kernel updates posted and OS updates). Various obvious gui setting changes had no positive effect (pcmanfm/event manager). Tested when new OS 18.06 updates posted (without save folder) and same result. Thought it might be particular to this system but recent load (no save folder) to laptop produced same result.
Checkums matched prior to install. No idea if kernel or OS upgrade specific but sometimes pmount automatically popped up and sometimes not. (Pmount always worked as expected though.)
Reinitializing pup-volume-monitor-starter consistently works for me. (Plug in external drive, wait for volume icons to disappear, reinitialize pup-volume-monitor-starter and all volumes show up and fully functional again in pcmanfm and desktop.)
This isn't a big deal, just a tip for anyone else who has adopted this as their main and experiencing same perplexing issue and is of similar dubious skill level. (I'd gotten really used to letting pcmanfm handle drive mounts/unmounts.) Bear in mind it could still be something weird I've done causing this...
Thanks for keeping so many things updated PeeBee, greatly appreciate your efforts.
Since about k 4.18.10 (through subsequent kernel updates posted and OS updates). Various obvious gui setting changes had no positive effect (pcmanfm/event manager). Tested when new OS 18.06 updates posted (without save folder) and same result. Thought it might be particular to this system but recent load (no save folder) to laptop produced same result.
Checkums matched prior to install. No idea if kernel or OS upgrade specific but sometimes pmount automatically popped up and sometimes not. (Pmount always worked as expected though.)
Reinitializing pup-volume-monitor-starter consistently works for me. (Plug in external drive, wait for volume icons to disappear, reinitialize pup-volume-monitor-starter and all volumes show up and fully functional again in pcmanfm and desktop.)
This isn't a big deal, just a tip for anyone else who has adopted this as their main and experiencing same perplexing issue and is of similar dubious skill level. (I'd gotten really used to letting pcmanfm handle drive mounts/unmounts.) Bear in mind it could still be something weird I've done causing this...
Thanks for keeping so many things updated PeeBee, greatly appreciate your efforts.
Thank you for the report which I have verified....wadmalaw wrote:Mounted volumes disappear from desktop and pcmanfm panel when attach external drive
Problem can be traced back to change to 64-bit pup-volume-monitor-0.1.17 on or about 15-sep-2018.
Have reverted back to pup-volume-monitor-0.1.15 in delta 18.06+11
The dmesg crash with 0.1.17 is:
Code: Select all
pool[7353]: segfault at 40 ip 00007f2127bb54f0 sp 00007f21263b6dd8 error 4 in libpupvm.so.0.0.0[7f2127ba9000+13000]
Code: 40 00 48 8b 05 11 6b 20 00 48 8b 00 48 85 c0 74 e4 ff d0 48 89 df 5b e9 de aa ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 <8b> 47 40 85 c0 74 09 48 8b 07 ff a0 a0 00 00 00 c3 0f 1f 44 00 00
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64