LxPupSc64 - 64bit version of Puppy with the LXDE desktop
I think dropping 9 and adding 22 is a good compromise in coverage.
As for the 8265 firmware, as it's newer and considerably larger (2+ MB), maybe wait until it's asked for, as there is now also 9000 series firmware coming out also.
Maybe highlighting gyro's maintenance of the firmware sfs more is also a good compromise.
As for the 8265 firmware, as it's newer and considerably larger (2+ MB), maybe wait until it's asked for, as there is now also 9000 series firmware coming out also.
Maybe highlighting gyro's maintenance of the firmware sfs more is also a good compromise.
I concur - 9 out, 22d in - sounds good. Also, check out this firmware site: http://anduin.linuxfromscratch.org/BLFS/linux-firmware/
Delta +1 provides the updated fdrv and Slackware64 Current updates to Sun Apr 8 22:22:25 UTC 2018
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-previous post: Then . . .
I got a new (basic) laptop - HP 250 G6 Celeron N3060 - appears wireless needs 4.6+ kernel (iwlwifi 3168NGW). Thankful for Peebee.
I got a new (basic) laptop - HP 250 G6 Celeron N3060 - appears wireless needs 4.6+ kernel (iwlwifi 3168NGW). Thankful for Peebee.
Last edited by ozsouth on Wed 25 Apr 2018, 02:05, edited 1 time in total.
Delta +3- BIG rebuild of all Slackware64-Current packages as described for Thu Apr 19 01:04:06 UTC 2018
3ddddf24aa52cad470d79899a1913f74 lxpupsc64-18.04+3.iso
3ddddf24aa52cad470d79899a1913f74 lxpupsc64-18.04+3.iso
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
Both LxPupSc64 and LxPupSc GrubforDos installs on the i5 (sandy bridge) laptops and on the Bay Trail (J1900 CPU) desktops updated to the latest versions (BIG Slackware rebuilds) using the deltas. I haven't done the core 2 duo laptops yet. All md5sums correct, no untoward effects seen, and all lib dirs checked for stray *.la files. None found in either pup.
Cheers,
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.
This is probably the wrong place to ask, but since you (Marv) brought it up, does anyone know why they are stripping the *.la files at slackware and apparrently the other upstream distros in response, so it seems, to the further upstream upgrades to gpg? Most of the version upgrades I've encountered only involve removing the .la file!all lib dirs checked for stray *.la files
Doesn't this mean that if I try to (re)compile an older package from source, it will fail, since a lot of them search for particular .la files. What's this got to do with "security?
df
The changelog peebee linked 2 posts up 'described for...' explained the Slackware folks rationale for it in some detail. I don't know enough to do other than read and try to comprehend.
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.
LxPup64 - 64bit versions of Puppy with the LXDE desktop
Installed to a 32gb flash drive:
System: Host: puppypc28180 Kernel: 4.15.15-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.04
Machine: Device: desktop System: ACER product: Aspire M5620 v: R01-A4 serial: PTS860X0348050CF642700
Mobo: ACER model: G33T-AM v: 1.0 serial: 00000000 BIOS: American Megatrends v: R01-A4 date: 12/19/2007
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) speed/max: 1595/2403 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.19.6 driver: nvidia tty size: 141x27 Advanced Data: N/A for root
Network: Card-1: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Card-2: D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W] driver: rt73usb
Drives: HDD Total Size: 531.6GB (0.4% used)
Works okay so far,
Thanks.
System: Host: puppypc28180 Kernel: 4.15.15-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
Distro: LxPupSc64 18.04
Machine: Device: desktop System: ACER product: Aspire M5620 v: R01-A4 serial: PTS860X0348050CF642700
Mobo: ACER model: G33T-AM v: 1.0 serial: 00000000 BIOS: American Megatrends v: R01-A4 date: 12/19/2007
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) speed/max: 1595/2403 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.19.6 driver: nvidia tty size: 141x27 Advanced Data: N/A for root
Network: Card-1: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Card-2: D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W] driver: rt73usb
Drives: HDD Total Size: 531.6GB (0.4% used)
Works okay so far,
Thanks.
- Attachments
-
- screenshot.jpg
- (30.33 KiB) Downloaded 629 times
Hi Peebee & all,
First, thanks, Peebee, for the Delta +3 upload.
Second, have a question, hope it is not stupid: is it recommended (or necessary) that when applying a delta---specifically when it is noted that it is a 'huge' delta update (as Peebee noted above)---that I should completely delete my 'savefolder' I bring across from deltas +1 & +2 and setup a new, fresh savefolder? Or is it ok to keep using one's savefolder when a big 'update' like this occurs since it is in the same ISO family (18.04)???
Thanks for any hints, or clarification.
First, thanks, Peebee, for the Delta +3 upload.
Second, have a question, hope it is not stupid: is it recommended (or necessary) that when applying a delta---specifically when it is noted that it is a 'huge' delta update (as Peebee noted above)---that I should completely delete my 'savefolder' I bring across from deltas +1 & +2 and setup a new, fresh savefolder? Or is it ok to keep using one's savefolder when a big 'update' like this occurs since it is in the same ISO family (18.04)???
Thanks for any hints, or clarification.
Big - not hugebelham2 wrote:is it ok to keep using one's savefolder when a big 'update' like this occurs since it is in the same ISO family (18.04)???
Existing savefolder should be fine (only possible exception would be if it contains different versions of slackware libs - i.e. if you've installed libs with ppm)
Advice = make backup and try it and see.....
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
Read this on DWW yesterday;
"Slackware is well known as a conservative distribution which rarely introduces sweeping changes. However, the world's oldest surviving Linux distribution introduced some significant changes this week which required a rebuild of the project's software packages: "Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the longest ChangeLog entry in project history). There were two primary motivations for rebuilding everything in the main tree. The first was to switch to the new C++ ABI. The second was to get rid of all the .la files in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly obsolete since things began to use pkg-config instead, but it's not easy to get rid of them unless you do it all at once. If you just take them out of one package, any other packages containing .la files that refer to the removed ones will be broken." How this rebuild will affect users and how to handle the change is covered in Slackware's changelog. "
Comments?
"Slackware is well known as a conservative distribution which rarely introduces sweeping changes. However, the world's oldest surviving Linux distribution introduced some significant changes this week which required a rebuild of the project's software packages: "Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the longest ChangeLog entry in project history). There were two primary motivations for rebuilding everything in the main tree. The first was to switch to the new C++ ABI. The second was to get rid of all the .la files in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly obsolete since things began to use pkg-config instead, but it's not easy to get rid of them unless you do it all at once. If you just take them out of one package, any other packages containing .la files that refer to the removed ones will be broken." How this rebuild will affect users and how to handle the change is covered in Slackware's changelog. "
Comments?
Link above to be read.Sage wrote:Comments?
Shouldn't impact LxPupSc64 unless you are doing something very specialised with it.
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
LxPupSc64-18.06
LxPupSc64-18.06 - iso, devx and kernel sources & headers
- kernel 4.17.0
- Slackware64-Current to Sat Jun 9 16:57:58 UTC 2018
- BUILD_FROM_WOOF='master;1873fb0;2018-06-08 22:06:23 +0800'
No delta from 18.04 (too big).
Lots of changes from both Woof-CE and Slackware64-Current.....PCManFM update to 1.3.0 may cause issues with panels if you've updated them....
- kernel 4.17.0
- Slackware64-Current to Sat Jun 9 16:57:58 UTC 2018
- BUILD_FROM_WOOF='master;1873fb0;2018-06-08 22:06:23 +0800'
No delta from 18.04 (too big).
Lots of changes from both Woof-CE and Slackware64-Current.....PCManFM update to 1.3.0 may cause issues with panels if you've updated them....
Last edited by peebee on Tue 12 Jun 2018, 06:04, 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
LxPupSc64-18.06
Updated from 18.04 +2 on my i5 laptop. Obviously hadn't been in the 64b world for a bit. Standard Grub4Dos install to SSD with 256Mb EXT2 savefile, scrubbed and checked before update. PCManFM panel item needed to be reloaded as noted. No other glitches seen. glxgears FPS excellent, Ath9 WIFI connection preserved. No optical drive on this i5 so no tests of that. It's beat up, was rescued from the parts bin, but wonderous light and somehow my favorite. Mitigation on this i5 as expected. I could load the newest intel microcode and try for spec_store_bypass mitigation but I really distrust the new microcode almost as much as the vulnerability so...I'm running Slimjet 19.0.2.0 64b as an SFS. Downloaded from slimjet, configured as all the run-as-spots and added the missing libs using your chromium64_67.0.3396.79 pepper_30.0.0.113_lx_spot.sfs. Starts and runs smoothly and picks up my shared (32b and 64b) slimjet profile with no problems. Updated that browser at this time as the 64b slimjet I was running was old enough to have conflicts with the 19.0.2.0 version profile from the 32 bit pups.
Long story short-looks good.
Thanks,
Edit: Latest (04/25/2018) intel microcode package loaded. This kernel is configured to allow 'late' loading so it's pretty simple. 'Updated' code confirmed as loaded:No change in spec_store_bypass mitigation seen on this second generation i5.
Code: Select all
Display Specifications:
• Monitor VertRefresh: 60.00 times/s
• Screen Dimensions: 1366x768 pixels (361x203 millimeters)
• Screen Depth: 24 bits (planes)
Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: intel
• Loaded Modules: dbe dri2 dri3 evdev fbdev glx libinput present synaptics
• X.Org version: 1.20.0
OpenGL 2D/3D Rendering:
• Direct Rendering: Yes
• Vendor: Intel Open Source Technology Center
• Renderer: Mesa DRI Intel(R) Sandybridge Mobile
• Version: 3.0 Mesa 18.1.1
VGA controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
• Kernel Driver: i915
• Memory Used by Driver: 1184.00 KB
• Path: /lib/modules/4.17.0-lxpup64/kernel/drivers/gpu/drm/i915/i915.ko
• Description: Intel Graphics
• Video RAM: 256M
Code: Select all
meltdown : Mitigation : PTI
spec_store_bypass : Vulnerable
spectre_v1 : Mitigation : __user pointer sanitization
spectre_v2 : Mitigation : Full generic retpoline
Long story short-looks good.
Thanks,
Edit: Latest (04/25/2018) intel microcode package loaded. This kernel is configured to allow 'late' loading so it's pretty simple. 'Updated' code confirmed as loaded:
Code: Select all
microcode: updated to revision 0x2d, date = 2018-02-07
core: PEBS enabled due to microcode update
Last edited by Marv on Tue 12 Jun 2018, 12:18, edited 1 time in total.
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.
LxPup64 - 64bit versions of Puppy with the LXDE desktop
I installed to a 32gb usb-3.0 flash drive:
video-info-glx 1.5.3 Tue 12 Jun 2018 on LxPupSc64 18.06 Linux 4.17.0-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.20.0
dimensions: 1600x900 pixels (442x251 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.4.0 NVIDIA 340.107
Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Core 0: @2447 1: @2280 2: @2341 3: @2103 MHz
@peebee - would you upload a kernel headers pet please?
video-info-glx 1.5.3 Tue 12 Jun 2018 on LxPupSc64 18.06 Linux 4.17.0-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.20.0
dimensions: 1600x900 pixels (442x251 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.4.0 NVIDIA 340.107
Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Core 0: @2447 1: @2280 2: @2341 3: @2103 MHz
@peebee - would you upload a kernel headers pet please?
- Attachments
-
- screenshot.jpg
- (32.85 KiB) Downloaded 2041 times
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
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