LxPupSc64 - 64bit version of Puppy with the LXDE desktop

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

LxPup64 - 64bit versions of Puppy with the LXDE desktop

#196 Post by Billtoo »

I installed to a 32gb flash drive:

System: Host: puppypc13087 Kernel: 4.15.7-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.03
Machine: Device: desktop System: Gateway product: FX6860 serial: PTGCEP2002121069349200
Mobo: Gateway model: FX6860 serial: 109726660000629
BIOS: American Megatrends v: P01-A3 date: 04/19/2011
Battery hidpp__0: charge: N/A condition: NA/NA Wh
hidpp__1: charge: N/A condition: NA/NA Wh
CPU: Quad core Intel Core i7-2600 (-HT-MCP-) speed/max: 1614/3401 MHz
Graphics: Card: NVIDIA GF110 [GeForce GTX 560 Ti OEM]
Display Server: X.org 1.19.6 driver: nvidia tty size: 117x27 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 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: 3032.1GB (0.1% used)
Weather: Conditions: 25 F (-4 C) - Partly Cloudy Time: March 5, 3:52 AM EST
Info: Processes: 178 Uptime: 49 min Memory: 443.8/16027.6MB Client: Shell (bash) inxi: 2.3.8

I added kpat + the proprietary Nvidia driver.
Added "intel_pstate=disable" no quotes to the kernel line of the
menu.lst file.

Thanks.
Attachments
screenshot.jpg
(42.01 KiB) Downloaded 773 times

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

LxPup64 - 64bit versions of Puppy with the LXDE desktop

#197 Post by Billtoo »

I installed to the hard drive of my HP desktop:

System: Host: puppypc11697 Kernel: 4.15.7-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.03
Machine: Device: desktop System: Hewlett-Packard product: HPE-410f serial: MXX0370KF3
Mobo: FOXCONN model: 2AB1 v: 1.00 BIOS: American Megatrends v: 6.02 date: 07/21/2010
Battery hidpp__0: charge: N/A condition: NA/NA Wh
hidpp__1: charge: N/A condition: NA/NA Wh
CPU: Hexa core AMD Phenom II X6 1045T (-MCP-) speed/max: 799/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
Display Server: X.org 1.19.6 drivers: ati,radeon (unloaded: modesetting,vesa) FAILED: fbdev
tty size: 127x38 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL810xE PCI Express Fast Ethernet controller driver: r8169
Drives: HDD Total Size: 1031.7GB (0.6% used)
Weather: Conditions: 34 F (1 C) - Overcast Time: March 7, 12:27 AM EST
Info: Processes: 148 Uptime: 40 min Memory: 383.2/7981.2MB Client: Shell (bash) inxi: 2.3.8

Installed some applications with PPM + compiled a few (thanks for
providing the devx and kernel source)

It's working well,
Thanks.
Attachments
screenshot.jpg
(75.79 KiB) Downloaded 703 times

Terry H
Posts: 708
Joined: Sun 29 Mar 2009, 16:48
Location: The Heart of Muskoka, ON Canada

#198 Post by Terry H »

Haven't used any LX Pup's for a while, so seeing a new final release for LXPupSC64, thought it was a good opportunity to re-acquaint myself with the LXDE Puppy variant. A new manual frugal install to a SanDisk Ultra 32 GB Flash Drive using UEFI booting.

Everything appears to be working fine on Dell Latitude 3350 (Core i3-5005U 8GB RAM) laptop. Only issue seems to be reported Graphics failure in inxi output shown below. I have no idea what it is reporting, everything runs fine, glxgears executes successfully.

Thank you, well done peebee, congratulations on another great addition to the kennel.

Code: Select all

# inxi -Fxz
System:    Host: puppypc2226 Kernel: 4.15.7-lxpup64 x86_64 (64 bit gcc: 7.3.0) Desktop: LXDE (Openbox 3.6.1)
           Distro: LxPupSc64 18.03
Machine:   Device: laptop System: Dell product: Latitude 3350
           Mobo: Dell model: 0KVTCC v: A00 UEFI: Dell v: A10 date: 06/29/2017
Battery    BAT0: charge: 59.0 Wh 123.3% condition: 47.9/59.0 Wh (81%)
           model: Samsung SDI DELL 6C0FN58 status: Full
CPU:       Dual core Intel Core i3-5005U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 7984
           clock speeds: max: 2000 MHz 1: 1185 MHz 2: 1292 MHz 3: 1223 MHz 4: 1291 MHz
Graphics:  Card: Intel HD Graphics 5500 bus-ID: 00:02.0
           Display Server: X.org 1.19.6 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           tty size: 134x35 Advanced Data: N/A for root
Audio:     Card-1 Intel Wildcat Point-LP High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Broadwell-U Audio Controller driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.15.7-lxpup64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 03:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Intel Wireless 7265 driver: iwlwifi bus-ID: 04:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 530.9GB (0.6% used)
           ID-1: /dev/sda model: TOSHIBA_MQ01ACF0 size: 500.1GB
           ID-2: /dev/sdb model: Ultra_Fit size: 30.8GB
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 139 Uptime: 6 min Memory: 332.5/7886.5MB Init: SysVinit runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.8 

jd7654
Posts: 296
Joined: Mon 06 Apr 2015, 16:10

Re: LxPup64 - 64bit versions of Puppy with the LXDE desktop

#199 Post by jd7654 »

Very nice Peebee.

Tested on Acer Cloudbook 14, older Braswell N3060 netbook, booted UEFI on USB flash. Everything worked except wifi/network.

Running OK on this machine: Xubuntu, Easy, Fatdog, StretchDog, XenialPup. But Slacko64 6.9.9.9 did not work, hangs with many errors on boot.
LxPupSc64 booted fine to the desktop, great job whatever you fixed.
But wifi card not recognized so no network. I manually copied over newer /lib/firmware/iwlwifi-3160-17.ucode file that is in all the above working OS, rebooted and then LxPupSc64 saw the network and is now working fine.

Suggest to add the newer iwlwifi-3160-17 firmware, although this is an older machine, still see this cheap/slow platform being sold today amazingly.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#200 Post by peebee »

Delta to LxPupSc64-18.03+2

.iso md5 = 4459de2d1056c200875a70d902f7770b lxpupsc64-18.03+2.iso

- Slackware64-Current updates to Fri Mar 16 02:29:29 UTC 2018
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

LxPup64 - 64bit versions of Puppy with the LXDE desktop

#201 Post by Billtoo »

Manual frugal install to a usb-3.0 SSD:

video-info-glx 1.5.3 Fri 16 Mar 2018 on LxPupSc64 18.03 Linux 4.15.7-lxpup64 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

X Server: Xorg Driver: nvidia
X.Org version: 1.19.6
dimensions: 3840x1080 pixels (1049x292 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.42

Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1668 1: @1756 2: @1634 3: @1620 MHz

Installed kpat,vlc,gkrellm, with PPM + compiled smplayer/smtube.

One problem is that using the up-arrow key triggers the mtpaint
screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)

Also installed the newest Nvidia proprietary driver (Mar 12th)

Thanks.
Attachments
screenshot.jpg
(31.18 KiB) Downloaded 427 times

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: LxPup64 - 64bit versions of Puppy with the LXDE desktop

#202 Post by peebee »

Billtoo wrote:One problem is that using the up-arrow key triggers the mtpaint screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
Hi @Billtoo

I don't see that problem on either of my test pc's. Anybody else seeing it??

Can you give more details of your setup so I can try to duplicate? My installs are to hdd but that shouldn't make a difference....

Is the problem there on 1st pristine frugal install with nothing added?

Is it mtpaint triggered?? It should be TAS.....
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Re: LxPup64 - 64bit versions of Puppy with the LXDE desktop

#203 Post by Billtoo »

peebee wrote:
Billtoo wrote:One problem is that using the up-arrow key triggers the mtpaint screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
Hi @Billtoo

I don't see that problem on either of my test pc's. Anybody else seeing it??

Can you give more details of your setup so I can try to duplicate? My installs are to hdd but that shouldn't make a difference....

Is the problem there on 1st pristine frugal install with nothing added?

Is it mtpaint triggered?? It should be TAS.....

Hi peebee

I can't swear to it but I'm pretty sure the problem is there on a
pristine frugal install.
Yes, mtpaint is triggered,if you were to hold the up-arrow down for a
couple of seconds you might see 10 or more in the tray (see screenshot)

This was a problem on one of radky's dpup's (I think) caused by
PupControl, he had a fix for it but I can't remember what it was.

It's a problem on my hard drive install of your first release but I
didn't report it at that time.
Attachments
up-arrow.jpg
(44.11 KiB) Downloaded 378 times

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#204 Post by peebee »

The fact that it's mtpaint suggests that the openbox config is getting overwritten....

or defaultscreenshot has been changed....

Does the PrintScreen key do anything?

see /root/.config/openbox/rc.xml

should say:

<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#205 Post by Billtoo »

peebee wrote:The fact that it's mtpaint suggests that the openbox config is getting overwritten....

or defaultscreenshot has been changed....

Does the PrintScreen key do anything?

see /root/.config/openbox/rc.xml

should say:

<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
Here's the /root/.config/openbox/rc.xml

PrintScreen doesn't appear to do anything.
Attachments
rc.xml.gz
(25.36 KiB) Downloaded 271 times

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#206 Post by peebee »

You have:
<keybind key="0x6F">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Print Screen</name>
</startupnotify>
<command>mtpaint -s</command>
</action>
</keybind>

in rc.xml so it has been overwritten....

Run xev in a terminal
press Up Arrow
should see:
keycode 111 (keysym 0xff52, Up)

Stop xev with cntrl-c
Run xev again
press PrintScreen
should see:
keycode 107 (keysym 0xff61, Print)
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#207 Post by Billtoo »

peebee wrote:You have:
<keybind key="0x6F">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Print Screen</name>
</startupnotify>
<command>mtpaint -s</command>
</action>
</keybind>

in rc.xml so it has been overwritten....

Run xev in a terminal
press Up Arrow
should see:
keycode 111 (keysym 0xff52, Up)

Stop xev with cntrl-c
Run xev again
press PrintScreen
should see:
keycode 107 (keysym 0xff61, Print)
I chose Switch LXDE <-> JWM desktop environments from the setup menu and the up-arrow problem is gone.

Gave it a new background.

Edit: I had the same problem on my hard drive install of RC1
Linux puppypc11697 4.15.7-lxpup64 #1 SMP Thu Mar 1 07:25:15 +08 2018 x86_64 AMD Phenom(tm) II X6 1045T Processor AuthenticAMD GNU/Linux
#
Turning it into Slacko64 RC3 with an updated kernel isn't the fix you want but it is working well.
Attachments
screenshot3.jpg
(70.91 KiB) Downloaded 322 times
screenshot2.jpg
(34.04 KiB) Downloaded 348 times
Last edited by Billtoo on Sat 17 Mar 2018, 11:10, edited 1 time in total.

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

#208 Post by ozsouth »

Tried current update & previous. Frugal on hdd. Arrow keys just move cursor as expected. Toshiba laptop C665D cpu AMD E-450.
Edit: PrtSc brings up 'Take a Shot'. With the latest version - just booted up & no settings changed.
Last edited by ozsouth on Sat 17 Mar 2018, 21:11, edited 1 time in total.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#209 Post by belham2 »

Billtoo wrote:
peebee wrote:The fact that it's mtpaint suggests that the openbox config is getting overwritten....

or defaultscreenshot has been changed....

Does the PrintScreen key do anything?

see /root/.config/openbox/rc.xml

should say:

<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
Here's the /root/.config/openbox/rc.xml

PrintScreen doesn't appear to do anything.

@Billtoo, Peebee:

This was the exact problem I reported (and what I did to fix it) to peebee almost a half year ago:

http://murga-linux.com/puppy/viewtopic. ... 7aa6b8602c

Surprised to see it is still occurring in many iterations of other OSes with lxde. Maybe the offending rc.xml code needs removed from rc.xml permanently, so it doesn't infect lxde-rc.xml (and anything else)? That was how I fixed it back then.

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

THEME Set Switcher is the issue

#210 Post by ozsouth »

Tried 2 other pcs with LxPupSc64-18.03+2 on usb ext2. No issue - each time booted up and closed Quick start, Welcome & Theme Switcher unchanged.
** THEN ** - I changed the THEME SET via Switcher - billtoo & belham2's issues began. THEN I reverted to original blue theme - all OK again. Repeated with all 3 non-original blue sets. SUGGESTION - scrub Theme Set Switcher, or at least remove it from Startup.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: THEME Set Switcher is the issue

#211 Post by peebee »

ozsouth wrote:Tried 2 other pcs with LxPupSc64-18.03+2 on usb ext2. No issue - each time booted up and closed Quick start, Welcome & Theme Switcher unchanged.
** THEN ** - I changed the THEME SET via Switcher - billtoo & belham2's issues began. THEN I reverted to original blue theme - all OK again. Repeated with all 3 non-original blue sets. SUGGESTION - scrub Theme Set Switcher, or at least remove it from Startup.
Thanks ozsouth - I know what I need to fix now....
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#212 Post by peebee »

Delta to LxPupSc64-18.03+3

.iso md5 = 56a23bc7ef2780038824d5f850f1806b lxpupsc64-18.03+3.iso

- fixes the Theme Setter
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#213 Post by peebee »

LxPupSc64 currently has ffmpeg-2.8.11 from slacko6414.2 (ffmpeg-2.8.11-x86_64_s700)

My suspicion is that this needs rebuilding/updating as for instance:
aplay /usr/share/sounds/2barks.au
is giving errors....as are some websites....

Anybody else noticed sound problems??

The problem is I don't think I've got the right compiling environment available....
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#214 Post by Marv »

peebee wrote:LxPupSc64 currently has ffmpeg-2.8.11 from slacko6414.2 (ffmpeg-2.8.11-x86_64_s700)

My suspicion is that this needs rebuilding/updating as for instance:
aplay /usr/share/sounds/2barks.au
is giving errors....as are some websites....

Anybody else noticed sound problems??

The problem is I don't think I've got the right compiling environment available....
I hadn't noticed any problems on either the i5 or the core 2 duo. Just startup sound, some news type web pages and aplay. On both machines aplay returns

Code: Select all

# aplay /usr/share/sounds/2barks.au 
Playing Sparc Audio '/usr/share/sounds/2barks.au' : Mu-Law, Rate 8000 Hz, Mono
# 
Cheers,
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.

ozsouth
Posts: 858
Joined: Fri 01 Jan 2010, 22:08
Location: S.E Australia

#215 Post by ozsouth »

I get the same aplay result as Marv, on i3-2310m, celeron 1019y & amd e-450. I note ffmpeg compiled with different gcc to kernel (5.3.0 vs 7.3.0) - irrelevant?

Post Reply