LxPupSc64 - 64bit version of Puppy with the LXDE desktop
LxPupSc64 - 64bit version of Puppy with the LXDE desktop
13-Jun-2020
Latest LxPupSc64 - Woof-CE build based on Slackware64 Current
but see next post for updates
Feedback welcomed
Cheers
peebee
LxPup64 - a 64bit version of Puppy with the LXDE desktop
Latest LxPupSc64 - Woof-CE build based on Slackware64 Current
but see next post for updates
Feedback welcomed
Cheers
peebee
LxPup64 - a 64bit version of Puppy with the LXDE desktop
- Attachments
-
- Screenshot.png
- (66.7 KiB) Downloaded 25425 times
Last edited by peebee on Sun 14 Jun 2020, 08:07, edited 46 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
Updates
13-Jun-2020
Delta to 20.06+?
ISO md5 = b847e509eaa97805bfaca22fad1c0b91 LxPupSc64-20.06+0-T.iso
Must be applied to: b847e509eaa97805bfaca22fad1c0b91 LxPupSc64-20.06+0-T.iso
Updates are cumulative - only the most recent needs to be applied.
Delta to 20.06+?
ISO md5 = b847e509eaa97805bfaca22fad1c0b91 LxPupSc64-20.06+0-T.iso
Must be applied to: b847e509eaa97805bfaca22fad1c0b91 LxPupSc64-20.06+0-T.iso
Updates are cumulative - only the most recent needs to be applied.
Last edited by peebee on Sun 14 Jun 2020, 08:09, edited 21 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
Cups
Nice... fast... should work out to be a very solid distro! Keep after it!
Just started testing the 64 version, only major problem I encountered so far is 'CUPS' printer setup. It seems it can't find the http://localhost:631 for a setup (using the hplip_64 from the PPM on- hp-1150 410 all-in-one printer)
On with testing.....
>>>---Indian------>
Just started testing the 64 version, only major problem I encountered so far is 'CUPS' printer setup. It seems it can't find the http://localhost:631 for a setup (using the hplip_64 from the PPM on- hp-1150 410 all-in-one printer)
On with testing.....
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Re: LxPup64
Hi VolhoutVolhout wrote:Any chance for UEFI boot on this one ?
Volhout
The question of Puppy & UEFI boot needs much greater brain power than I possess
AFAIK the only "Puppy" that's tackled the problem and got a solution is FatDog64??? But that's significantly different in build techniques to the Woof-CE Puppies that form the base of LxPup.....not even sure that there are any FatDog derivatives.....are there?
There will be a UEFI boot Woof-CE Puppy someday no doubt - but I'll have to rely on cleverer people to produce it.
Cheers
peebee
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
Re: LxPup64
Hello @Volhout
You are not the only one who has had PC loss over the past weeks. I powered off a PC that had been running flawlessly for over a year only to find on my rebooting it a week later that the RAM failed. And cost of RAM replacement exceeds the cost of a newer 64bit PC.
In any event, I have had success helping others in booting LightHouse64 "Mariner" edition oN recent UEFI PCs & laptops.
Its a 2 step process where you first employ a minor UEFI change to recognize the distro on media as valid (this is done ONLY one for either distro),then booting LH64 or FATDOG.
Look at this site as complete details are present. (Dont be afraid of the warning of it not being maintained. The PUP thread is still active and the distro is still a working marvel on 64bits.) And, I might add, I have never installed either a FD or LH64 on any/anyone/s PC as I traditionally run via DVDs with sessions saved to DVD...even on my .64bit laptops.
Here to help
You are not the only one who has had PC loss over the past weeks. I powered off a PC that had been running flawlessly for over a year only to find on my rebooting it a week later that the RAM failed. And cost of RAM replacement exceeds the cost of a newer 64bit PC.
In any event, I have had success helping others in booting LightHouse64 "Mariner" edition oN recent UEFI PCs & laptops.
Its a 2 step process where you first employ a minor UEFI change to recognize the distro on media as valid (this is done ONLY one for either distro),then booting LH64 or FATDOG.
Look at this site as complete details are present. (Dont be afraid of the warning of it not being maintained. The PUP thread is still active and the distro is still a working marvel on 64bits.) And, I might add, I have never installed either a FD or LH64 on any/anyone/s PC as I traditionally run via DVDs with sessions saved to DVD...even on my .64bit laptops.
Here to help
LxPup64
Firewall doesn't survive on reboot or even cold startup!
My Confg: Boot from CD, savefile on HDD.
CD/DVD not showing up in directory-tree (says there are no subfolders... not able to get any info there.
Good so far: Graphics excellent and it's super fast!
>>>---Indian------>
My Confg: Boot from CD, savefile on HDD.
CD/DVD not showing up in directory-tree (says there are no subfolders... not able to get any info there.
Good so far: Graphics excellent and it's super fast!
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Can't get it started. Manual frugal install into own subdirectory /lxpup64, edited menu.lst accordingly, booted, throws error saying it can't find puppy_lxpup64_14.12.sfs. Moved file to root of partition, still the same. Method worked fine for all puppies yet, including slacko64 (actually used the grub-entry of slacko64 and edited the subdir only). Any boot parameters to point the boot process directly to the SFS?
Presumably grub4dos??chiron² wrote:Can't get it started. Manual frugal install into own subdirectory /lxpup64, edited menu.lst accordingly, booted, throws error saying it can't find puppy_lxpup64_14.12.sfs. Moved file to root of partition, still the same. Method worked fine for all puppies yet, including slacko64 (actually used the grub-entry of slacko64 and edited the subdir only). Any boot parameters to point the boot process directly to the SFS?
Works fine for me - this is my menu.lst entry that works for 99% of puppies frugal install on HD:
Code: Select all
title Main (sda2/pupmain)
uuid 91e027f5-cb6e-40fe-964c-76f2e2971845
kernel /pupmain/vmlinuz pmedia=atahd psubdir=pupmain pfix=fsck
initrd /pupmain/initrd.gz
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
Re: Reserved
Some work, some don't.peebee wrote:Not possible to select from multiple savefolders/savefiles if using a usb keyboard
gyro
See updated post#2
@sszindian:
cups - fix pet in post#2
firewall - setup gives errors (also in Slacko64)
cd/dvd - pmount can be used
@gyro: clarified usb keyboard problem in post#2
@Volhout & @gcmartin:
LH64 has taken the Fatdog64 hybrid iso as the basis of an LH64 hybrid iso as I understand it - I guess it might be possible to do similar for LxPup64 but it would be trial and guesswork to work out what needed to be changed unless we can get guidance from Jamesbond and Kirk. I don't have a uefi pc to test on....any volunteers to try this??
@ally - many thanks - hope there are health warnings that this is very much an experimental alpha derivative.....
@sszindian:
cups - fix pet in post#2
firewall - setup gives errors (also in Slacko64)
cd/dvd - pmount can be used
@gyro: clarified usb keyboard problem in post#2
@Volhout & @gcmartin:
LH64 has taken the Fatdog64 hybrid iso as the basis of an LH64 hybrid iso as I understand it - I guess it might be possible to do similar for LxPup64 but it would be trial and guesswork to work out what needed to be changed unless we can get guidance from Jamesbond and Kirk. I don't have a uefi pc to test on....any volunteers to try this??
@ally - many thanks - hope there are health warnings that this is very much an experimental alpha derivative.....
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
Actually, no, just plain grub.It got installed many years ago by openSUSE, and I adapted it to all kinds of puppies.peebee wrote:
Presumably grub4dos??
The psubdir did the trick. Booted straight to X, resolution fine, looks pretty good, and quick. Only problem is, and it was the same with slacko64, it doesn't remember static IP settings, instead gives an error saying unrecognized format and blanks the entry fields for static IP and Gateway. In Network wizard that is. Used Frisbee in Slacko64, but that again gave a behaviour I didn't like.
Stellarium and libre office SFS from Fatdog work.
Code: Select all
mkisofs -iso-level 4 -D -R -o $OUTPUT -b isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table \
-eltorito-alt-boot -eltorito-platform efi -b efiboot.img -no-emul-boot "$tmp_isoroot"
isohybrid -u $OUTPUT
Code: Select all
insmod png
background_image /fatdog.png <<of course change this..
set timeout=10
menuentry "Start LxPup64 Frugal" {
linux (hd0,msdos1)/LxPup64/vmlinuz
initrd (hd0,msdos1)/LxPup64/initrd.gz
}
menuentry "Start LxPup64 " {
linux /vmlinuz
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Hi Ted DogTed Dog wrote:need to borrow isohybrid from FatDog, also efiboot.img
Thanks for investigating this - trying to follow what you are doing!!!
isohybrid v0.12 is included in Slacko64/LxPup64......
I can work on the back_ground image .png
Cheers
peebee
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
I definitely volunteer for testing !!peebee wrote:See updated post#2
@sszindian:
cups - fix pet in post#2
firewall - setup gives errors (also in Slacko64)
cd/dvd - pmount can be used
@gyro: clarified usb keyboard problem in post#2
@Volhout & @gcmartin:
LH64 has taken the Fatdog64 hybrid iso as the basis of an LH64 hybrid iso as I understand it - I guess it might be possible to do similar for LxPup64 but it would be trial and guesswork to work out what needed to be changed unless we can get guidance from Jamesbond and Kirk. I don't have a uefi pc to test on....any volunteers to try this??
@ally - many thanks - hope there are health warnings that this is very much an experimental alpha derivative.....
My PC is UEFI + secure boot, and it boots Fatdog64 (700b2) and *buntu's, but not Proteus, nor Slax.
xsane Scan
The .pet you provided on page#1 got the printer working and print out a test page just fine however, upon trying the scanner (xsane from menu) it appears the scanner drivers configured the scanner properly because all appears on the screen as it should... then does everything right up to the point of displaying the actual scan then 'BANG' everything disappears from the screen?
>>>---Indian------>
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
LxPup64-14.12.01-hybrid.iso
A hybrid iso version of LxPup64-14.12.02 has been uploadedVolhout wrote:Hi PeeBee,
Any chance for UEFI boot on this one ?
Volhout
Couple of small desktop file fixes.
This is a hybrid iso - I've tested that it bios boots ok - Ted Dog has checked that it uefi boots.
Thanks go to Kirk and JamesBond for the uefi booting mechanism from FatDog64 and to Tazoc for showing how this could then be adapted for Lighthouse64. Thanks also to Ted Dog for helping me do the adaptation for LxPup64.
If you need help in installing, try reading the following guides BUT please note that there are significant differences between LxPup64 and FatDog64 and to a lesser extent between LxPup64 and Lighthouse64. In particular any utilities mentioned may not be available in LxPup64.
http://lhpup.org/help/faqs/uefi-harddrive.html
http://lhpup.org/help/faqs/uefi-flashdrive.html
http://distro.ibiblio.org/fatdog/web/fa ... drive.html
Please pay particular attention to any warnings given on how a Windoze 8 pc should be configured before any installation is attempted as doing it incorrectly could brick your computer!!
Ted Dog has reported that his GPT disk isn't being seen in pcmanfm although it can be used for a savefile.
Previous problems as detailed in the 2nd post are all still there.
Cheers & Happy New Year 2015
peebee
Last edited by peebee on Mon 05 Jan 2015, 22:28, 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
secure UEFI boot
Hi PeeBee,
I tried the hybrid iso (burned to USB stick with win32 disk imager) on my Lenovo Flex14 laptop with secure UEFI boot, and LxPup booted to the desktop immediately in correct 1920x1080 resolution !! Perfect !!
Keyboard, sound, and mouse are detected correctly, and so is wired etherent. But wireless is not detected.
The laptop has a intel AC3160 wireless chip. The chip is detected correctly, but the correct firmware cannot be loaded. See attached dmesg output
Apparenly there are multiple versions of this AC3160 chip, and 3 firmware versions are tried, but none work. This is identical to FATDOG700B2.
Tried Lubuntu 14.10 dmesg output to compare, kernel 3.16.0, this works with AC-3160 in my laptop. They use a different interrupt number (63 vs 44) and load firmware version 25.222.9.0 (but I cannot see in LxPup dmesg what version this is).
Not sure if anyone can shed some light....
From GIThub
I have no LED indicator to see if the WIFI module is powered down or up while trying to download firmware, maybe it is a setting in ACPI ?
I tried the hybrid iso (burned to USB stick with win32 disk imager) on my Lenovo Flex14 laptop with secure UEFI boot, and LxPup booted to the desktop immediately in correct 1920x1080 resolution !! Perfect !!
Keyboard, sound, and mouse are detected correctly, and so is wired etherent. But wireless is not detected.
The laptop has a intel AC3160 wireless chip. The chip is detected correctly, but the correct firmware cannot be loaded. See attached dmesg output
Code: Select all
Intel(R) Wireless WiFi driver for Linux, in-tree:
Copyright(c) 2003- 2014 Intel Corporation
iwlwifi 0000:02:00.0: irq 43 for MSI/MSI-X
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-10.ucode failed with error -2
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-9.ucode failed with error -2
iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-3160-9.ucode' failed.
iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-8.ucode failed with error -2
iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-3160-8.ucode' failed.
iwlwifi 0000:02:00.0: no suitable firmware found!
Tried Lubuntu 14.10 dmesg output to compare, kernel 3.16.0, this works with AC-3160 in my laptop. They use a different interrupt number (63 vs 44) and load firmware version 25.222.9.0 (but I cannot see in LxPup dmesg what version this is).
Code: Select all
[ 38.621560] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 38.621564] Copyright(c) 2003- 2014 Intel Corporation
[ 38.621777] iwlwifi 0000:02:00.0: irq 63 for MSI/MSI-X
[ 38.704662] device-mapper: multipath: version 1.7.0 loaded
[ 38.762880] iwlwifi 0000:02:00.0: loaded firmware version 25.222.9.0 op_mode iwlmvm
//
[ 39.084811] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3160, REV=0x164
[ 39.084891] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[ 39.085245] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
//
[ 39.818015] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[ 39.818382] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[ 39.841885] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
//
[ 116.664386] wlan0: authenticate with e0:91:f5:ac:ac:c4
[ 116.667389] wlan0: send auth to e0:91:f5:ac:ac:c4 (try 1/3)
[ 116.669169] wlan0: authenticated
[ 116.669415] iwlwifi 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 116.669933] wlan0: associate with e0:91:f5:ac:ac:c4 (try 1/3)
[ 116.672656] wlan0: RX AssocResp from e0:91:f5:ac:ac:c4 (capab=0x411 status=0 aid=7)
[ 116.673521] wlan0: associated
[ 116.673569] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
From GIThub
Code: Select all
File: iwlwifi-3160-7.ucode
Version: 22.1.7.0
<at> <at> -828,7 +828,7 <at> <at> File: iwlwifi-3160-9.ucode
Version: 25.228.9.0
File: iwlwifi-3160-10.ucode
-Version: 23.10.10.0
+Version: 23.11.10.0