LxPupSc64 - 64bit version of Puppy with the LXDE desktop

[Billtoo]

Hardinfo seems to be broken.

Hi Billtoo

Hardinfo is there and works - its in the menu under System -> System -> System Profile and Benchmark (Porteus hangover I guess).

Cheers
peebee

Hi peebee

Hardinfo works until I ask it to generate a report which causes it to crash.

Thanks

[peebee]

Hi peebee

Hardinfo works until I ask it to generate a report which causes it to crash.

Thanks

Please install:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... x86_64.pet
and see if that still crashes.

CORRECTED link 24-may-15

Thanks

[Billtoo]

Hi peebee

Hardinfo works until I ask it to generate a report which causes it to crash.

Thanks

Please install:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 86-s14.pet
and see if that still crashes.

Thanks

I downloaded and compiled hardinfo-0.5.1.tar.gz from sourceforge.
It generates a report okay.

Thanks

[cthisbear]

Thanks mate....

Chris.

[cthisbear]

Ze olde >>>puppy lxpup64_15.05 sfs not found >> problem.

Gee! never seen that.

I only experienced it once with one ttuuxxx release of

2.14x ...should have investigated it more.

:::::::::

I normally name Pups in lowercase...

so I have LxPup64 named as >>> lxpup64

Looking at this I solved my Lucid 529 newer release from
continuing the same behaviour as >> LxPup64.

http://murga-linux.com/puppy/viewtopic. ... 2&start=15

from mikeslr ..... pmedia=ataflash

so my working Lucid is now.

title Lucid529 2015 (sdc1/lucid529)
find --set-root --ignore-floppies /lucid529/initrd.gz
kernel /lucid529/vmlinuz pmedia=ataflash psubdir=lucid529 pfix=fsck
initrd /lucid529/initrd.gz

Any other Lucid is pmedia=usbflash
Two other Lucids on this usb ...never had a problem before.

:::::

So I first tried modifying

title LxPup 64 2015 (sdc1/lxpup64)
find --set-root --ignore-floppies /lxpup64/initrd.gz
kernel /lxpup64/vmlinuz pmedia=usbflash psubdir=lxpup64 pfix=fsck
initrd /lxpup64/initrd.gz

No...fails to find the sfs.

Re-worked it to cheat like Lucid.

title LxPup 64 2015 (sdc1/lxpup64)
find --set-root --ignore-floppies /lxpup64/initrd.gz
kernel /lxpup64/vmlinuz pmedia=ataflash psubdir=lxpup64 pfix=fsck initrd /lxpup64/initrd.gz

Same result.

I even copied the >>> puppy lxpup64_15.05 sfs
into the root of the usb.

Suggestions....

Chris.

[peebee]

Ze olde >>>puppy lxpup64_15.05 sfs not found >> problem.
Suggestions....
Chris.

Hi Chris

Just tried booting from a usb stick - I had no problems - stick was fat32 formatted - subdirectory was called puppy - contents (4 files) were:

Code: Select all

initrd.gz  puppy_lxpup64_15.05.sfs  vmlinuz  zdrv_lxpup64_15.05.sfs

menu.lst entry was:

Code: Select all

title Puppy
  find --set-root --ignore-floppies /puppy/initrd.gz
  kernel /puppy/vmlinuz  pmedia=usbflash psubdir=puppy pfix=fsck
  initrd /puppy/initrd.gz

[cthisbear]

OK!

" stick was fat32 formatted - subdirectory was called puppy "

Is fat32..but I will rename files.

Chris.

[cthisbear]

Failed to boot with the above changes.

I should read my own replies though.

Decided for a laugh to use one of the rear ports.

Booted...posting from it now.

I will redo my menu list with the original settings
just to see if it boots.

::::::::::::;;;;

" I should read my own replies though."

Don't you hate it that you forget the basics sometimes....aghhhhhh!!!!!!!!!!

Thanks mate....Chris.

::::::::

I still can't get these 2 Pups on this particular usb to complete booting
on a Dell laptop and a 2.5 dual core Gigabyte desktop.

Both Puppies refuse to see the sfs files.

Just tested a 2014 Super Lupu on the dual core..it boots.
no problems from the same usb....

[GoneSouth]

Peebee where do I find a devx for this
or do I have to goto PPM

[peebee]

Peebee where do I find a devx for this
or do I have to goto PPM

http://www.murga-linux.com/puppy/viewto ... 253#785253

[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.