LxPupSc64 - 64bit version of Puppy with the LXDE desktop

[gcmartin]

15.05.01-hybrid.iso booted Live on UEFI system

But, system did NOT pick up the SWAP partition on the PC's internal drive at boot.

Code: Select all

sh-4.2# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq qlen 1000
    link/ether f4:b7:e2:63:c9:a5 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 5c:f9:dd:e2:17:9e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.3/25 brd 192.168.0.128 scope global eth0
       valid_lft forever preferred_lft forever
sh-4.2# free
             total         used         free       shared      buffers
Mem:       3911500       647716      3263784       306452        47020
-/+ buffers:             600696      3310804
Swap:            0            0            0
sh-4.2# uname -a 
Linux LxPup64onDellAIO 4.0.2-EmSee-64 #1 SMP Thu May 7 17:43:02 BST 2015 x86_64 Intel(R) Pentium(R) CPU G2020 @ 2.90GHz GenuineIntel GNU/Linux

Is this an oversight/deliberate?

And, tracking (with finger on touchscreen) not added.

[Dry Falls]

Same here. Kernel modules are not loading consistently, yet it starts right up. After a couple of re-starts, it seemed to improve. Overall, I really like it. Firewall still gets lost between boots (slacko64). Easy to fix (first-run wizard) by moving rc.firewall from /tmp to /etc/rc.d and symlinking /usr/local/firewallstate/firewallstaterun to the startup folder. It doesn't hinder network discovery at all.

Mounted iso and dragged contents to a usb stick. Changed pmedia=cd in grub2 to pmedia=usbflash and that worked really well. Unless pmedia is specified, savedir isn't found. Lighthouse is the same: adding wait for usb doesn't help. It wants the savefile/folder on the hard-drive/partition. Actually, it's another pretty easy fix with an extra line & boot parameter in grub or isolinux.cfg

Links from the browser homepage to help files in usr/doc point to non-existent files.

I didn't see acpid in there. Suspend to ram doesn't work for me, but all the other power management functions are good. It may also be a glitch in the kernel modules.

There's really not much left to do to finalize this puppy. thanks. I'm going to look for that devx.

df

edit. rc.firewall also needs to reside in /etc/init.d.

ps. no change window manager under startlxde. Must log out. I thought I saw a ui text option, but then it went missing.

[Dry Falls]

Started over with clean frugal to hard drive. No more problem with acpi/suspend. First run ram created savefolder within a LxPup64 directory, which threw me for a loop at first. Needed to add psubdir=LxPup64 to grub entry. Otherwise, init cannot find the basefile. Not sure why except LxPup64 system files and grub are on a different partition altogether.

Only moved /tmp/rc.firewall to /etc/init.d after running the wizard and it now starts right up every boot. You might add this to the script.

Found Desktop session settings again. It says "openbox-lxde" but to start from the console, you must enter "xwin startlxde" to return to the default desktop. Curious. Also event manager ui was a trip to find in the menu. I was just used to finding it under "Desktop".

df

[gcmartin]

@PeeBee, or anyone. Have you advice for USB connecting a smartPhone/smartTable to this distro?

Thanks in advance for steps to follow.

[sszindian]

Just wondering? Has anyone had luck getting Google Talk (Gmail phone) working in this 64 bit version? I've run out of things to try (and I've tried a lot) without results.

>>>---Indian------>

[Gooplusplus]

Unlike most Puppy-based distros and most Ubuntu-based distros, LxPup64 is unfortunately not YUMI USB Multiboot friendly. Basically, when booted from YUMI USB, an error is shown stating that puppy_lxpup64_15.05.sfs cannot be found.

I suspect that this sfs file path has been hard-coded somewhere as a semi-fixed path rather than a fully relative one since almost all other Puppy-based distros never had that problem. The one similar exception is the latest Simplicity Netbook 15.4 distro. It fails for the same reason whereas Simplicity Netbook 15.1 worked just fine.

From time to time I post USB Linux Collection torrents. They mostly focus on lightweight distros. I will be posting two new collections (32bit and 64bit) in a week or so. The last one can be found here:

http://www.gooplusplus.com/multiboot-2015-lite-speed/ --- https://kat.cr/usb-multiboot-2015-lite- ... 18268.html

I had planned to add LxPup64 to the forthcoming 64-bit YUMI-based USB collection. Unfortunately, after trying a few tricks to get LxPup64 to work with YUMI despite initial problems, I just could not get it to work.

[peebee]

LxPup64 is unfortunately not YUMI USB Multiboot friendly.

Does this also apply to Fatdog64 and Lighthouse64? LxPup64 iso is a hybrid boot based on the Fatdog64 model.

The one similar exception is the latest Simplicity Netbook 15.4 distro.

Probably because it is just a LxPup64 derivative.....in 64bit version

[Gooplusplus]

Does this also apply to Fatdog64 and Lighthouse64?

Fatdog64 7.01 booted fine even with default isolinux.cfg and grub.cfg

Lighhouse64 6.02 failed with the same error.

I took another look at Simplicity and found that the 32 bit (based on LX Pup Tahr) worked but the 64 bit version (based on LxPup64) failed.

[Dry Falls]

Might have something to do with the fact that there is still no standardization among 64bit efi machines. And because the firmware might say it can enable legacy boot, it doesn't mean it actually does. And even if the hybrid function on fatdog, lxpup64 and lighthouse is (and they are!) correct and proper, it can be a real pain in the but to set up the box to accept 'foreign' certificates in the first place.

[gcmartin]

I thought LxPUP64 was more of a Slacko64 derivative than FD which in turns brings the user friendliness that is seen. Same as found in @LightHouse64.

In any event, on my PCs, thus far, I have not run into any issues in using them on both BIOS and UEFI PCs. But, I do run Live DVDs (not that this add/subtracts from the problem).

Question
Which PC manufacturer is showing UEFI/EFI problems?

Maybe someone might offer ideas to address the problem.

[Gooplusplus]

Might have something to do with the fact that there is still no standardization among 64bit efi machines.

In my case, I have been testing on a non-efi PC (Lenovo Y470 0855-2HU notebook).

I see that Simplicity has released 15.7 Beta but won't release the 64 bit Desktop version due to problems that need to be fixed. Is this related?

http://simplicitylinux.org/2015/06/simp ... available/

UPDATE: No, not related other than being based on LxPup64.

Simplicity 15.7 final Desktop and Netbook 64-bit both fail
Simplicity 15.7 final Desktop and Netbook 32-bit both pass

[sszindian]

LxPup64-15.05.01

Using Chromium browser:
Version 43.0.2357 Puppy Linux 64 (64-bit)

Gmail Phone 'Now Connects' and works through your Gmail (US only I believe) WITHOUT INSTALLING ANY PLUG-INS (it appears Chromium now includes the needed plug-in... anyway it works for me!)

(1) However... you have to setup 'Retrovol' (it is NOT configured OOTB in LxPup64) by right/clicking the speaker in the 'Tray' (select: Configure Window) then select 'Hardware' put most of the items in the Right/Hand Window over in the Left/Hand Window... Select the 'APPLY' at the bottom then exit.

(2) Right/Click the Speaker icon in the Tray again... select 'Full Window'... make sure all the appropriate boxes are 'checked' and the blue-bars are set to where you want them (volume etc)

Go into Gmail and make a call!!! (Mic or Speaker-mic required)

>>>---Indian------>

[Dry Falls]

these work for LxPup64-15.05.01:

sox-14.4.1-x86_64-1.txz
wavpack-4.60.1-x86_64-1.txz from slackware in ppm

[Dry Falls]

also symlink /usr/local/firewallstate/firewallstate to /root/Startup and cp rc.firewall to /etc/init.d.

Added this line to /root/Startup/1-lxde-startup.sh:

Code: Select all

swapon /dev/sda*

replace sda* with your swap drive/partition. A line could be added to the init file which finds and loads the swap prior to xwin, but this does the job in the mean time.

df

[peebee]

these work for LxPup64-15.05.01:

Hi df

What problem does retrovol_tray-jl64.pet solve?

Thanks

[Dry Falls]

What problem does retrovol_tray-jl64.pet solve?

Actually, there is no problem until you go tinkering and break it. Specifically, I installed FbBox-2.0_64Bit for some familiar apps, some of which are redundant, but LXPup64 generally runs better with it than even Slacko64. Unfortunately, its retrovol sets up a version conflict which I only just discovered this morning. It's wmchanger works under jwm but not lxde. Must log out to prompt to change wm from lxde to any other. My kde/xfce addon works almost as well ootb under lxpup as under lighthouse.

It's all in the spirit of fun with experimentation, but I'm finding lxpup64 very versatile. I think it's rapidly becoming my new drug, er, dog of choice.

df

[peebee]

EXPERIMENTAL - use with care

A version of LxPup64 based on TahrPup64-6.0.3.8 is available from later posts.

Stemsee's 4.1.6 kernel is used.
The iso is a normal bios iso not a hybrid uefi.

Please check the TahrPup64 thread from this post to see if any problems have already been reported.

Known LxPup specific problems are:
- the trash can is not working - see below

[Tote]

Cool! this; A version of LxPup64 based on TahrPup64-6.0.3.5 is available to download: just downloaded, manual frugal install, works ootb, T61 Thinkpad. Still playing, I'm easily pleased! Many thanks!

[peebee]

LxPupTahr64-15.09.02 Fixed the disappearing menu problem.

The lack of Trash is because gvfs is not starting.

Error message from /usr/libexec/gvfsd is:

Failed to connect to the D-BUS daemon: Could not connect: No such file or directory (g-io-error-quark, 1)

I can't work out how to fix at the moment I'm afraid....

[peebee]

LxPupTahr-15.09.3 was based on tahrpup64-6.0.3.7 - no longer available