slacko-700 rc3
Delete it and download:
http://distro.ibiblio.org/puppylinux/Pa ... n-official
0setup should do this for you.....
http://distro.ibiblio.org/puppylinux/Pa ... n-official
0setup should do this for you.....
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
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
I tried a Slacko64 build with the latest woof-CE when at my parents for Easter on my dad's Core2Duo laptop. Here's the iso:
http://www.mediafire.com/folder/y13kxdldb9i9d/x86_64
It seems to be working ok so far on it, I didn't need anything from puppy-common this time either. These comments also apply to it:
http://www.mediafire.com/folder/y13kxdldb9i9d/x86_64
It seems to be working ok so far on it, I didn't need anything from puppy-common this time either. These comments also apply to it:
- The adrv has Firefox 52.7.3esr and Abi/Gnumeric
- chose Original Pup as the default theme, and gnome-mplayer as the default music player
- kernel has firmware-140621-cut, if you are missing any drivers/functionality there's instructions on how to swap kernels here
@Sailor
I installed to the hard drive of my Acer desktop:
System: Host: puppypc14078 Kernel: 4.4.126 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.9
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: 1603/2403 MHz
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 500.1GB (3.6% used)
Info: Processes: 184 Uptime: 1:08 Memory: 419.4/7984.8MB Client: Shell (bash) inxi: 2.3.8
X Server: Xorg Driver: nvidia
X.Org version: 1.18.3
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.5.0 NVIDIA 384.130
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1870 1: @1603 2: @1870 3: @1870 MHz
I installed applications with PPM,installed the proprietary Nvidia
driver, and compiled Smplayer/Smtube.
Works great,
Thanks.
Edit: I've done 2 more hard drive installs, pc1 has newer intel graphics, pc2 has ati radeon graphics.
It's working well on both new installs.
I installed to the hard drive of my Acer desktop:
System: Host: puppypc14078 Kernel: 4.4.126 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.9
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: 1603/2403 MHz
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 500.1GB (3.6% used)
Info: Processes: 184 Uptime: 1:08 Memory: 419.4/7984.8MB Client: Shell (bash) inxi: 2.3.8
X Server: Xorg Driver: nvidia
X.Org version: 1.18.3
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.5.0 NVIDIA 384.130
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1870 1: @1603 2: @1870 3: @1870 MHz
I installed applications with PPM,installed the proprietary Nvidia
driver, and compiled Smplayer/Smtube.
Works great,
Thanks.
Edit: I've done 2 more hard drive installs, pc1 has newer intel graphics, pc2 has ati radeon graphics.
It's working well on both new installs.
- Attachments
-
- screenshot.jpg
- (95.54 KiB) Downloaded 2213 times
slacko hangs on i5 machine
I installed it on my dualcore and it works very nice.Sailor Enceladus wrote:I tried a Slacko64 build with the latest woof-CE when at my parents for Easter on my dad's Core2Duo laptop. Here's the iso
I also installed it on my i5 laptop.
Startup seems to hang there between loading modules and starting X. It comes through eventually. I send you xerrs.log and my system specs in case you want to look into this.
When I try to startup with the savefile, it really hangs.
I have not yet tried to switch kernels. I may go for the 4.9.30 from 01micko and see wat happens.
- Attachments
-
- errs+sys.zip
- (4.49 KiB) Downloaded 156 times
I switched kernel and zdrv and now it runs very nicely.ozsouth wrote:@Foxpup - last time I had that happen, missing firmware was the culprit.
You could be right ozsouth, but I don't know which. It may be a kernel specific driver that needs compiling. Is there an easy way to know? Can I see it in some log file?
On my dualcore this slacko with the original kernel has now effectively replaced a heavily remastered Tahr 6.0.2 as my main workhorse.
Is slacko not ready for a release? Wouldn't it be nice if slacko, dpup (radky) and upupBB (peebee) released all together !?
Slacko 700 RC3 K4.4.70-PAE
Here the 32 bit version of Slacko 700 RC3 snapshot for testing.
Used kernel version K 4.4.70-PAE
BUILD_FROM_WOOF='testing;6d5d2531;2018-04-05 13:45:04 +0300'
Looks really good, didn't find seriously errors up to now except these blemishes
- pkeys=de will be ignored ( I'm using ISOBOOTER )
- empty tables of contents of developer tools remain in packages/builtin_files ( 0 byte files )
- menu entry xcalc present but application not installed
slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso
size: 281 M
md5: 16d38a00df3318e93a979463f9d150a9
Many thanks for this great Distro
Used kernel version K 4.4.70-PAE
BUILD_FROM_WOOF='testing;6d5d2531;2018-04-05 13:45:04 +0300'
Looks really good, didn't find seriously errors up to now except these blemishes
- pkeys=de will be ignored ( I'm using ISOBOOTER )
- empty tables of contents of developer tools remain in packages/builtin_files ( 0 byte files )
- menu entry xcalc present but application not installed
slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso
size: 281 M
md5: 16d38a00df3318e93a979463f9d150a9
Many thanks for this great Distro
Re: Slacko 700 RC3 K4.4.70-PAE
Do you answer 'y' or 'n' to the isobooter "splash screen" question?norgo wrote:- pkeys=de will be ignored ( I'm using ISOBOOTER )
Answering 'n' means it boots using the files in the iso rather than booting the iso itself.
Then adding boot parameters in "menu.lst" should work.
gyro
Re: Slacko 700 RC3 K4.4.70-PAE
Hello gyro,gyro wrote:Do you answer 'y' or 'n' to the isobooter "splash screen" question?
Answering 'n' means it boots using the files in the iso rather than booting the iso itself.
Then adding boot parameters in "menu.lst" should work.
yes I'm using isobooter with "splash screen" and "menu.lst" contains already the boot parameter pkeys=de
here a snippet of my "menu.lst"
Code: Select all
title SLACKO 32 700 RC3 K4.4.70-PAE 2017-12-10 DEVELOPMENT
partnew (hd0,3) 0x00 (hd0,0)/slacko-700-RC3_k4.4.70-PAE_2017-12-10.iso
map --heads=0 --sectors-per-track=0 (hd0,0)/slacko-700-RC3_k4.4.70-PAE_2017-12-10.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz pmedia=cd psavemark=2 pfix=ram pkeys=de
initrd /initrd.gz
title SLACKO 32 700 RC3 K4.4.70-PAE 2018-04-05 DEVELOPMENT
partnew (hd0,3) 0x00 (hd0,0)/slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso
map --heads=0 --sectors-per-track=0 (hd0,0)/slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz pmedia=cd psavemark=2 pfix=ram pkeys=de
initrd /initrd.gz
title SLACKO 64 700 RC3 K4.9.30
partnew (hd0,3) 0x00 (hd0,0)/slacko64-6.9.9.9-uefi-k4.9-FF-LO.iso
map --heads=0 --sectors-per-track=0 (hd0,0)/slacko64-6.9.9.9-uefi-k4.9-FF-LO.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz pmedia=cd psavemark=2 pfix=ram intel_pstate=disable pkeys=de
initrd /initrd.gz
Re: Slacko 700 RC3 K4.4.70-PAE
Norgo, thank you for this new build. Now I have a recent slacko32 as well to test with.norgo wrote:Here the 32 bit version of Slacko 700 RC3 snapshot for testing.
Used kernel version K 4.4.70-PAE
BUILD_FROM_WOOF='testing;6d5d2531;2018-04-05 13:45:04 +0300'
Looks really good, didn't find seriously errors up to now except these blemishes
- pkeys=de will be ignored ( I'm using ISOBOOTER )
- empty tables of contents of developer tools remain in packages/builtin_files ( 0 byte files )
- menu entry xcalc present but application not installed
I have installed yours on my dualcore PC and found it works well
I took kernel sources and devx from micko's build and compiled the 304.137 nvidia driver for my graphic card.
I use pkeys=be-latin1. It is all right on the prompt (nox) but it has to be setup again for X (be), as in most Puppies. No problem.
I install frugally by copying the Puppy files into a directory and adding lines to the menu.lst for grub4dos.
Confirmation on the other blemishes.
Hello foxpup,
thank you for feedback.
update:
My search for the reason of pkeys issue ends up here
Seems to be a feature now
thank you for feedback.
update:
My search for the reason of pkeys issue ends up here
Seems to be a feature now
see:norgo wrote:Hello foxpup,
thank you for feedback.
update:
My search for the reason of pkeys issue ends up here
Seems to be a feature now
https://github.com/puppylinux-woof-CE/w ... dd2d476e2e
fixes for keymap-set and xkbconfigmanager
improve symbiotic relationship and throw xorgwizard-automatic into the mix
hopefully this fixes the pkeys= issue reported by @peabee
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
@peebee
hey peebee you already knew this.
I only read your post at github today, thank you for report.
I patched slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso by the changes of commit d553a8c for test.
slacko-700-RC3_k4.4.70-PAE_2018-04-05_d553a8c-patched.iso
size: 281 M
md5: a7bed9a8abad39a4874c0e8ed3cd7cbb
Up to now no problems at all.
wdlkmpx you are awesome !
hey peebee you already knew this.
I only read your post at github today, thank you for report.
I patched slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso by the changes of commit d553a8c for test.
slacko-700-RC3_k4.4.70-PAE_2018-04-05_d553a8c-patched.iso
size: 281 M
md5: a7bed9a8abad39a4874c0e8ed3cd7cbb
Up to now no problems at all.
wdlkmpx you are awesome !
ifactive
Frisbee in /usr/sbin/ifactive should be changed to all lower case in script ('Frisbee' -> 'frisbee') to work with the frisbee installed in Slacko64. Also, sections on frisbee-tray might be removed, as it's not present or used in this version. If this is part of woofCE, someone should commit the change. If it was just lifted out of lighthouse for this build, just change the script.
Here's the fixed one (still has ref to frisbee-tray):
Here's the fixed one (still has ref to frisbee-tray):
- Attachments
-
- ifactive.gz
- fakegz
- (3.23 KiB) Downloaded 199 times
64 bit kernel
I've made a 64bit Slacko compatible 4.9.94 kernel via Puppy kernel-kit, with the cutdown firmware option. Is Spectre/Meltdown mitigated. Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both.
See: http://murga-linux.com/puppy/viewtopic. ... 955#989955
.
See: http://murga-linux.com/puppy/viewtopic. ... 955#989955
.
Last edited by ozsouth on Wed 02 May 2018, 00:16, edited 5 times in total.
I 've replaced with this and now Puppy knows about the pkeys from the kernel options. So that works well.norgo wrote:I patched slacko-700-RC3_k4.4.70-PAE_2018-04-05.iso by the changes of commit d553a8c for test.
wdlkmpx you are awesome !
I am also running the slacko64 from Sailor on this dualcore PC. I've lost the keyboard and the mouse twice now. First time I reinstalled, but I did not keep the pupsave. Second time I have kept the pupsave; I can drag out some logs if someone wants them to look at it.
Beginning of april I've also reported trouble with be-latin1 on this PC and UpupBionic. In the end I reinstalled and further ignored it.
Maybe all this has to do with this commit d553a8c?
I've made Broadcom wl drivers for Slacko64 kernels 4.4.126 & 4.9.94 see: http://murga-linux.com/puppy/viewtopic. ... 271#990271
I've made a 64bit Slacko compatible 4.14.35 kernel via Puppy kernel-kit, with the no firmware option. Will need an fdrv for firmware. Is Spectre/Meltdown mitigated. Have swapped it into Slacko64 6.9.9.9 and LxpupSc64 18.03. Works ok in both.
See: http://murga-linux.com/puppy/viewtopic. ... 461#990461
See: http://murga-linux.com/puppy/viewtopic. ... 461#990461
differences in iso`s
slacko64-6.9.9.9-uefi-k3.16-PM-LO.iso 2017-Jun-13 02:58:11 353M
slacko64-6.9.9.9-uefi-k4.4-FF-LO.iso 2017-Jun-13 03:16:07 367M
slacko64-6.9.9.9-uefi-k4.9-FF-LO.iso 2017-Jun-13 02:22:36 368M
Hi there could anyone eksplain whats the difference between these 3 iso`3
and maybe how long to final 7.0 slacko?
kindly Gnimmelf
slacko64-6.9.9.9-uefi-k4.4-FF-LO.iso 2017-Jun-13 03:16:07 367M
slacko64-6.9.9.9-uefi-k4.9-FF-LO.iso 2017-Jun-13 02:22:36 368M
Hi there could anyone eksplain whats the difference between these 3 iso`3
and maybe how long to final 7.0 slacko?
kindly Gnimmelf
-
- Posts: 6
- Joined: Sat 11 Jun 2016, 19:04
G'day Gnimmelf, and et al.,
I will have a go at my interpretation based on my experience with each. They are versions of Slacko64 6.9.9.9 using different kernels and with different browsers and features.
PM = Pale Moon, FF = Firefox, LO = Libre Office
The kernel versions are significant if you intend to compile additional software specific for that distribution beyond what was already provided.
Typically if you intend to simply use it as is then you are good to go. Otherwise if you intend further customization then you will need to know the specific kernel used to assemble the appropriate elements to compile software for additional utility.
Now as to the highly anticipated release of Slacko 7, well that is better answered by those diligently contributing their efforts to produce Slack 7.
Cheers to ya! Hope this helps a bit.
I will have a go at my interpretation based on my experience with each. They are versions of Slacko64 6.9.9.9 using different kernels and with different browsers and features.
PM = Pale Moon, FF = Firefox, LO = Libre Office
The kernel versions are significant if you intend to compile additional software specific for that distribution beyond what was already provided.
Typically if you intend to simply use it as is then you are good to go. Otherwise if you intend further customization then you will need to know the specific kernel used to assemble the appropriate elements to compile software for additional utility.
Now as to the highly anticipated release of Slacko 7, well that is better answered by those diligently contributing their efforts to produce Slack 7.
Cheers to ya! Hope this helps a bit.