woof-CE needs you

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

#1021 Post by Billtoo »

mavrothal wrote:If X tried to start and failed should produce a /var/log/Xorg.0.log file. Also the /initrd/tmp/dmesg.txt file could be informative and maybe the /initrd/tmp/bootinit.log file
@norgo had success with his testing branch iso so I burned the one from
my new woof-CE testing branch (yesterday afternoon) to a DVD and tried
it on a pc with intel graphics (X wouldn't start on my HP ATI Radeon)
and it works.
I'm booting from the DVD with a save file on the hard drive.

# inxi -bw
System: Host: puppypc27878 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: Acer model: Aspire X3950 serial: U02C120500059
BIOS: American Megatrends v: P01-A3 date: 05/05/2010
CPU: Dual core Intel Core i3 540 (-HT-MCP-) speed/max: 1333/3067 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 144x40 Advanced Data: N/A for root
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 532.1GB (4.0% used)
Weather: Conditions: 68 F (20 C) - Partly Cloudy Time: August 3, 8:46 AM EDT
Info: Processes: 179 Uptime: 3 min Memory: 288.0/5997.2MB Client: Shell (bash) inxi: 2.3.8
#
I'll try booting the DVD on the Gateway which has Nvidia graphics and
see how that goes.

EDIT: The DVD boots to the desktop on the Gateway but the resolution is wrong and the mouse is dead,ctrl-alt-backspace does nothing.

So recent commits have caused problems with Radeon and Nvidia graphics on my hardware.
Attachments
screenshot.jpg
(31.78 KiB) Downloaded 1367 times

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1022 Post by sc0ttman »

Have built a slacko pup (32-bit, kernel 4.4, which is number 24 in the list during woof build)

It boots from CD and USB, all the way to desktop on a Dell Optiplex GX-something, which has on-board Intel gfx, and also boots to desktop on my main PC (with AMD radeon 7750 gfx) ..

Am using it now.. Works very nicely..

This is from the /etc/DISTRO_SPECS

Code: Select all

BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'
inxi - bw

Code: Select all

System:    Host: puppypc28490 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slak Puppy 6.9.11
Machine:   Device: desktop Mobo: ASRock model: FM2A75 Pro4 serial: E80-37025800032
           BIOS: American Megatrends v: P2.40 date: 07/11/2013
CPU:       Quad core AMD Athlon X4 750K (-MCP-) speed/max: 1400/3400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
           Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           tty size: 211x64 Advanced Data: N/A for root
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 2016.6GB (4.9% used)
Weather:   Conditions: 68 F (20 C) - Mostly Cloudy Time: August 3, 3:58 PM BST
Info:      Processes: 190 Uptime: 1:26 Memory: 563.8/16171.5MB Client: Shell (bash) inxi: 2.3.8 
For reference, the previous errors (now gone in 6e9bb39?) were "missing xorgwizard-automatic, line 113 of xwin" in one very recent build, and missing "FreeSans" font errors in a slightly older one... I had those errors on both machines mentioned above, and in a VM.

... Now some general observations..

1. Is the missing fonts message that prevented my desktop loading up (in previous builds) related to not including pTheme?

2. JWM is crap at working out 2 monitors, and moving them around is a real pain - compared to the drag and drop UI that Xfce provides.. Any way round this? Zarfy, maybe?

3. Does the Universal Pup Installer insist on overwriting the MBR of every drive/disk that uses GRUB? (or is it just me?)... Seems every time I try to use the Universal Installer, it insists I replace my MBR with mbr.bin (or other).. Can the Universal installer not work out I have a working GRUB, just leave the MBR?

4. IIRC, the Grub4DosConfig app doesn't backup the menu-adv.lst file, only the menu.lst file..

5. Where is the documentation about adding new petbuilds and pet packages to Woof? I want to create a new branch and make it build an Xfce pup (ideally... baby steps)..

6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..

7. How does having an Fdrv and a Ydv affect the zdrv-cutter thing? .. It that still a thing? Can't find it in my newly woofed pup..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

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

woof-CE needs you

#1023 Post by Billtoo »

I did a fresh install of woof-CE testing branch then a new build:

# inxi -bw
System: Host: puppypc4675 Kernel: 4.4.80-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: laptop System: Acer product: Aspire 7740 v: Rev serial: LXPNX02012004098672000
Mobo: Acer model: Aspire 7740 v: Rev serial: LXPNX02012004098672000
BIOS: Phoenix v: V1.15 date: 12/25/2009
Battery BAT0: charge: 44.0 Wh 100.0% condition: 44.0/44.0 Wh (100%)
CPU: Dual core Intel Core i5 M 430 (-HT-MCP-) speed/max: 1199/2267 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]
Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 131x37 Advanced Data: N/A for root
Network: Card-1: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe driver: tg3
Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 540.0GB (1.9% used)
Weather: Conditions: 68 F (20 C) - Overcast Time: August 10, 9:25 AM EDT
Info: Processes: 187 Uptime: 1:22 Memory: 222.1/3902.9MB Client: Shell (bash) inxi: 2.3.8
#

Running from a 32gb SDHC card on Acer laptop.

Works good, thanks for the fix.
******************************************************************
EDIT:
Same woof-CE version,new build:

# inxi -bw
System: Host: puppypc12471 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko 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
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.18.3 driver: nvidia tty size: 163x30 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 31.9GB (10.3% used)
Weather: Conditions: 75 F (24 C) - Mostly Cloudy Time: August 17, 11:49 AM EDT
Info: Processes: 193 Uptime: 51 min Memory: 690.0/8097.6MB Client: Shell (bash) inxi: 2.3.8
#

Works well so far.
Attachments
screenshotaug17.jpg
(77.05 KiB) Downloaded 919 times
screenshot.jpg
(94.62 KiB) Downloaded 1108 times
Last edited by Billtoo on Thu 17 Aug 2017, 15:56, edited 1 time in total.

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1024 Post by Sailor Enceladus »

sc0ttman wrote:6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..
If Ctrl-Left and Ctrl-Right are the keys that switch you to a different virtual window I've always found that shortcut just annoying. I'll be playing a game and the desktop will randomly switch to a different one where my game isn't on instead of doing what it's suppose to inside the game. I think it was Tahrpup that had this issue, as I remember the "pink square" moving left and right when my screen disappeared. Might have been Alt-Left/Right though, haven't experienced the issue for a while now.

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

#1025 Post by belham2 »

The Slacko64-6.9.9.9 frugal-install the I use a few times a week has started to display helter-skelter behavior (freezing screens, programs randomly refusing to open, etc) . Don't understand as everything was running great for a few months, with no new add-ons (or anything) have been applied to this latest release. Only thing that has changed is that I like to plug the USB drive that has all these frugal-installs into many of my different machines here-----and this new Slacko64-6.9.9.9 does not like this one bit.

Sure is a stark contrast on things when I throw Sailor E's slacko 5.7 build (into any machine) and everything just stinking runs like wildfire, no matter what I've thrown at it, I can't even get it to hiccup (and I've been doing crazy qt stuff with it, lol). Maybe I need newer systems to reliably run all of Micko's later creations; makes me sad :cry: Wife won't be having any of that soon, unfortunately. My newest hardware is 6 yrs old (i3 laptop), and the others are 8-19 yrs old (the oldest being a Pentium 2.0 I try to keep going, lol, and it does have a 1GB of ram, in its defense of staying relevant).

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

woof-CE needs you

#1026 Post by Billtoo »

I did a new build using the Aug 10th woof-CE:

# inxi -bw
System: Host: puppypc21732 Kernel: 4.9.44 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 139x36 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 500.1GB (10.8% used)
Weather: Conditions: 70 F (21 C) - Mostly Cloudy Time: August 19, 10:51 AM EDT
Info: Processes: 158 Uptime: 4 min Memory: 262.1/4025.6MB Client: Shell (bash) inxi: 2.3.8
#

It wouldn't boot to the desktop on a computer with radeon graphics but
it did on this pc with intel graphics.

Seems that the fix only applied to the 4.4 kernel and not the 4.9
kernel.

It's working okay apart from that.
Attachments
screenshot.jpg
(127.29 KiB) Downloaded 799 times

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

woof-CE needs you

#1027 Post by Billtoo »

I did a fresh install of woof-CE rationalise branch (aug 20th) and a
new build:

# inxi -bw
System: Host: puppypc32216 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 2000/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 162x40 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 562.5GB (9.9% used)
Weather: Conditions: 63 F (17 C) - Clear Time: August 20, 2:53 AM EDT
Info: Processes: 162 Uptime: 1:17 Memory: 685.1/4026.6MB Client: Shell (bash) inxi: 2.3.8
#

Fewer things to update when Updates notices - Slackware bugfixes is
run.
Firefox 52.3.0 ESR is included and works well.

No problems so far.
*************************************************************************
EDIT: I've done a fresh install of woof-CE testing branch (aug 20th) and a build:

# inxi -bw
System: Host: puppypc6136 Kernel: 4.9.44 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 158x35 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 562.5GB (10.2% used)
Weather: Conditions: 73 F (23 C) - Partly Cloudy Time: August 20, 1:34 PM EDT
Info: Processes: 152 Uptime: 1:53 Memory: 208.5/4025.6MB Client: Shell (bash) inxi: 2.3.8
#
The result is pretty much the same as the rationlise branch, it's working well.
Attachments
screenshot.jpg
(94.78 KiB) Downloaded 693 times
screenshot.jpg
(104.2 KiB) Downloaded 738 times

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1028 Post by sc0ttman »

Hi guys,

Is it the expected/desired behaviour that the ~/.packages/builtin_files/pkgname files ONLY contain dirs (not the actual files of the package) whenever the pkg is in ADRV?

Example, I built a woof Slacko with Abiword and Gnumeric in the ADRV... and now their respective ~/.packages/builtin_files/* contain only this:

# cat ~/.packages/builtin_files/gnumeric
/usr
/usr/bin
/usr/lib
/usr/share
/usr/share/applications
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/16x16
/usr/share/icons/hicolor/16x16/apps
/usr/share/icons/hicolor/22x22
/usr/share/icons/hicolor/22x22/apps
/usr/share/icons/hicolor/24x24
/usr/share/icons/hicolor/24x24/apps
/usr/share/icons/hicolor/32x32
/usr/share/icons/hicolor/32x32/apps
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/pixmaps


Is that a bug?

Also, why don't the built-in pkg file lists contain full file paths on each line, like in the ~/.packages/*.files of user installed packages? Is there a reason?

Seems very "pre-woof" .... Would make more sense if user pkgs and built-in pkgs listed their files in the same format...

I'm trying to write a command line package manager for puppy, and finding out the contents of built-in packages becomes very messy indeed because of these 2 problems -> when a file is in two packages (/usr/bin/gnumeric and /etc/file/gnumeric), trying to work out which pkg the file comes from starts to be a real pain if any of those files come from a pkg that lives in the ADRV..

(Sorry if this is the wrong place to post! ... And thanks for all the great work on puppy and woof-CE!)

EDIT: BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'
Last edited by sc0ttman on Mon 21 Aug 2017, 18:04, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1029 Post by sc0ttman »

On my woofed 32-bit slacko ... BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'


Youtube-dl fails as it can't find Python3 interpreter after install .. PPM reports no missing deps.. (as does my pkg manager).. the repo db dependency entries might need fixing..?

Code: Select all

#  youtube-dl 
bash: /usr/bin/youtube-dl: /usr/bin/python3: bad interpreter: No such file or directory
Package file: youtube-dl-2016.08.22-i586-1salix.txz (2.1MB)
From salix repo
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1030 Post by Sailor Enceladus »

belham2 wrote:Sure is a stark contrast on things when I throw Sailor E's slacko 5.7 build (into any machine) and everything just stinking runs like wildfire, no matter what I've thrown at it, I can't even get it to hiccup (and I've been doing crazy qt stuff with it, lol).
Thanks Belham! I'm using it as my main OS too. I tried making another 14.0 build at commit 5506 with kernel 3.18.66. Might upload it later, although this one is missing a few more deps that will probably need to be resolved or re-added to adrv first.
sc0ttman wrote:Seems very "pre-woof"
I think that's a little harsh since the adrv feature is still pretty new. Your feedback is possibly useful though.

P.S. Are you planning on making a new Puppy Arcade? That seems to be a quite popular puppy still and a neat concept. :)

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#1031 Post by sc0ttman »

sc0ttman wrote:Seems very "pre-woof"
I think that's a little harsh since the adrv feature is still pretty new. Your feedback is possibly useful though.

P.S. Are you planning on making a new Puppy Arcade? That seems to be a quite popular puppy still and a neat concept. :)
I'm one of the worst offenders for producing 'pre-woof' mess... So no offence intended obvs..

And I will possibly do it, If I make a new one, I will use some sleek frontend like EmuStation as a frontend to my frontend (Rom-Loader) ... That will do away with the old-school, clunky GTK interface, but will retain all the features of Rom-Loader (custom configs per ROM, etc) .. Just needs better bluetooth gamepad support for PS3, PS4, XBOX360 etc ... But I doubt anyone is interested by now and I'm waiting on a job application, so dunno whats next .. Depends.. We will see..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#1032 Post by bigpup »

belham2 wrote:The Slacko64-6.9.9.9 frugal-install has started to display helter-skelter behavior (freezing screens, programs randomly refusing to open, etc) . Don't understand as everything was running great for a few months, I like to plug the USB drive that has all these frugal-installs into many of my different machines here-----and this new Slacko64-6.9.9.9 does not like this one bit.

Maybe I need newer systems to reliably run all of Micko's later creations. My newest hardware is 6 yrs old.
The newest Linux 4 series kernels do seem to be a little buggy.
Finding one that is well bug fixed is an issue.
01micko has said, it has been one of the issues, he has been trying to overcome, in final releasing Slacko 7.0
Linux kernel 4 series seems more about providing support for the newer or newest hardware and not trying to support old hardware.

Example:
I have a very new computer with latest hardware.
Any of the Puppies using kernel 3 versions just do not have full 100% support for the hardware.
Kernel 4 versions do give me 100% hardware support.

The latest Puppy versions including Slacko 6.9.9.9 can easily change to using a different (older) kernel.
The ability is built in.

In a console enter:

Code: Select all

change_kernels
This is the program to use to change to using a different kernel.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

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

woof-CE needs you

#1033 Post by Billtoo »

I did a build from the woof-CE testing branch of Aug 20th, it's running
on my Acer touchscreen laptop:

# inxi -bw
System: Host: puppypc27047 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: laptop System: Acer product: Aspire V5-571P v: V2.17 serial: NXM49AA03531512EC36600
Mobo: Acer model: Aspire V5-571P v: V2.17 serial: NBM491100831501E946600
UEFI [Legacy]: Phoenix v: V2.17 date: 02/27/2013
Battery BAT0: charge: 20.1 Wh 99.0% condition: 20.3/25.0 Wh (81%)
CPU: Dual core Intel Core i3-3227U (-HT-MCP-) speed/max: 800/1901 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 113x35 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom Limited BCM43228 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 500.1GB (6.7% used)
Weather: Conditions: 66 F (19 C) - Mostly Cloudy Time: August 24, 1:29 PM EDT
Info: Processes: 180 Uptime: 1:28 Memory: 218.6/5865.7MB Client: Shell (bash) inxi: 2.3.8
#

The touchscreen works, no problems so far.
Attachments
screenshot.jpg
(109.29 KiB) Downloaded 381 times

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#1034 Post by wiak »

Single script to auto-build an official woof-CE pup:

http://www.murga-linux.com/puppy/viewto ... 541#965541

wiak

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#1035 Post by wiak »

saintless wrote:
peebee wrote:I'm not sure it's that simple (but that may be my lack of understanding) as I think the kernel has to be built with all the patches for aufs - this is what kernel-kit in woof-ce does to build the Puppy kernels.......
Hi peebee.

The standard Debian/Ubuntu kernel should have all patches needed to boot with aufs. Debian-live also uses aufs (and also options to boot with unionfs and now overlayfs).
But seems someone already did this in woof-ce even without aufs:
https://github.com/puppylinux-woof-CE/w ... 81958a516e
Yes, the woof-CE 3builddistro-Z script sources support/kernel_pkg.sh if kernel provided comes packaged as a pet, deb, tgz, or txz:

Code: Select all

case "$KERNEL_TARBALL_URL" in *.pet|*.deb|*.tgz|*.txz) KPKG=yes  ;; esac

if [ "$KPKG" = "yes" ] ; then
	# kernel pet/deb/txz/tgz
	. ../support/kernel_pkg.sh
and the controlling _00build.sh contains:

Code: Select all

## Kernel tarball URL
## avoid being asked questions about downloading/choosing a kernel
#KERNEL_TARBALL_URL=xxx
where xxx can be a link to say a debian package kernel such as:

http://http.us.debian.org/debian/pool/m ... 1_i386.deb

The contents of that end up being copied into Puppy z drive (which I presume can be read by Puppy initrd (I haven't checked that). However, the initrd-progs/0initrd/sbin/not_a_huge_kernel_stuff code you refer to doesn't seem to be sourced by the 3builddistro-Z script as yet so aufs will not be working with such a kernel (the kernel contents are themselves extracted in kernel_pkg.sh and moved into the z drive):

Code: Select all

case $KERNELPKG in
	*.pet)
		rm -f $KERNELPKG
		KERNPKGNAMEONLY="`basename $KERNELPKG .pet`"
		rm -rf $KERNPKGNAMEONLY
		cp ../kernel_pkgs/${KERNELPKG} ./
		pet2tgz $KERNELPKG
		tar -xf $KERNPKGNAMEONLY.tar.?z
		rm -rf zdrv/
		mv -f $KERNPKGNAMEONLY zdrv/
		;;
	#*.txz|*.tgz) #TODO
	*.deb)
		dpkg-deb -x ../kernel_pkgs/${KERNELPKG} zdrv 1>/dev/null
		;;
esac

mv -f zdrv/etc/modules/firmware.dep zdrv/etc/modules/firmware.dep.${KERNELVER}
I haven't actually tested if what I say is correct, but that is my reading of the current woof-CE-testing scripts situation. I'm certainly looking forwards to the code currently being stored in not_a_huge_kernel_stuff being implemented since woof-CE stretch building users seem to do a lot of fluffing about finding kernels to use when it would be so much more convenient (and secure maybe) to be able to simple use a stock kernel in Puppy like you have suggested Toni.

wiak

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

woof-CE needs you

#1036 Post by Billtoo »

Updated earlier post.

New slacko64 build (rationalise branch) installed to a 32gb usb-3.0
flash drive:

# inxi -bw
System: Host: puppypc20758 Kernel: 4.4.85 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.9
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial: MXX232077R
Mobo: Foxconn model: 2ADA v: 1.00 BIOS: AMI v: 7.12 date: 06/07/2012
CPU: Quad core Intel Core i5-3550 (-MCP-) speed/max: 1600/3301 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.18.3 driver: nvidia tty size: 148x36 Advanced Data: N/A for root
Network: Card-1: Ralink RT5390 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: 2031.9GB (0.7% used)
Weather: Conditions: 72 F (22 C) - Partly Cloudy Time: August 30, 1:41 PM EDT
Info: Processes: 189 Uptime: 1 min Memory: 217.9/11973.6MB Client: Shell (bash) inxi: 2.3.8
#

video-info-glx 1.5.3 Wed 30 Aug 2017 on Slacko64 Puppy 6.9.9.9 Linux 4.4.85 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

X Server: Xorg Driver: nvidia
X.Org version: 1.18.3
dimensions: 1920x1080 pixels (707x392 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.69

Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Core 0: @1600 1: @1600 2: @1600 3: @1600 MHz

Works well so far.
*****************************************************************
EDIT:
I now have the new build installed on my HP i3 desktop as well.
# uname -ra
Linux puppypc21093 4.4.85 #1 SMP Wed Aug 30 11:13:58 EDT 2017
x86_64 Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz GenuineIntel GNU/Linux
#
Attachments
install2.jpg
(48.52 KiB) Downloaded 518 times
screenshot.jpg
(84.73 KiB) Downloaded 524 times

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

Slacko 700s--please fix it, Micko ;-(

#1037 Post by belham2 »

I did a woof-CE build (testing branch) two nights ago, of Slacko64-6.9.9.9 with the latest big kernel offered in woof-CE. Hoping things have changed and/or been corrected in the Slacko distro new (700) edition since the last time (a few months ago) I and others reported problems with it. Everything seems fine until you put these latest Slacko(s) through their paces. Then, once again, the dreaded 'random freezing' hits and you are cooked. And dejected that it still exists.

On 3 different machines now, I am experiencing the same random freeze ups that I experienced several months ago with this new version of Slacko 700. Something is wrong and I hope/wish Micko has time to figure it out. When you are putting Slacko thru paces like having two terminals open, copying stuff from one directory to another, moving windows around on the desktop and/or laptop, etc, etc, all of sudden from out of left field this all will cause the OS to freeze up. It has done this now on AMD and Intel machines I own, each systems with copious RAM and SSD space where other, more stable pups and ddogs run like wild ponies. It is the exact same symptoms Sailor E. reported months back, and I also reported about (in the main Slacko thread) months back. I find it hard to believe, that anyone else who puts the newest Slacko OS (32 or 64 bit) thru heavy desktop work-related paces, doesn't experience this same thing.

It's kind of not good---aren't Slacko Pups supposed to be the heir apparent to Barry's works? All I can say is that this Puppy OS is failing, and the problems reported are not getting fixed. Compared to other pup distros and especially the Debian Dogs, it is alarming watching this happen. Even Barry's Easy Linux, a brand new work-in-progress, is more stable than Slacko 700 (6.9.9.9).

I understand people have lives, and developers cannot dedicate time to keeping things up. But Sailor and I and others have been reporting this stuff with Slacko 700 for months now. Not days, Not weeks. But months. This all is NOT a good image for Puppy Linux to put forth. Slacko Puppy is supposed to be the flagship for Puppy Linux. Maybe it is best for woof-CE to just pull these latest Slacko editions out of woof-CE until they can properly get fixed...because as things stand, nothing is getting addressed ;-/

Count this puppyland user out of Slackos for the forseeable future until fixes are put in place...because when Slacko randomly freezes like it is often wont to do, all your work is immediately lost---especially if you're operating on a "save-only-at-shutdown" mode. The previous versions (both 32 and 64 bit) don't have this problem---I never experienced it once in either earlier edition. But in 700? It is blatant. And bad.

And disappointing.... :(

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

#1038 Post by Billtoo »

@belham2

I imagine you did but just in case, did you update PPM and then check for bugfixes?
Attachments
bugfixes.jpg
(92.15 KiB) Downloaded 416 times

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

#1039 Post by belham2 »

Billtoo wrote:@belham2

I imagine you did but just in case, did you update PPM and then check for bugfixes?

Hi Bill,

Maybe I did something wrong with respect to the bug fixes focusing on "xorg-server". Can you look at my pic below? After updating PPM, was I supposed to not only re-install "xorg-server-1.18.3" (which I assumed I was supposed to do) but also install the other 3 xorg-server-related items brought back in PPM? The bugfix popup box is not clear, as it only says, and I quote:

Open the Puppy Package Manager (PPM) and find the packages in the list below and update them if you wish. :?: The packages are from Official Slackware packages. Your compatible Slackware version is:
slackware64-14.2


Was (referencing the pic below) I supposed to install the other 3 too? If so, it sure would be nice if the Bugfix Notification popup was clear about this. Also, overall with that popup, what is with it saying "....if you wish"? If I wish? What the heck is that?!! If there are problems in Slacko 700, shouldn't the popup tell us users exactly what to do instead of saying "...if you wish"? :roll:

Thank you for replying and any help with the whether the other 3 "xorg-" items in the pic below are also required to be installed.
Attachments
bugfix-popup-is-unclear--are-all-these xorgs-supposed-to-be-installed.png
(132.52 KiB) Downloaded 377 times

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

#1040 Post by Billtoo »

Hi,

I installed all 4 of the files, dragging and dropping the 1st on into the package manager, then clicking on it brought up the others so I clicked on them too.

That bugfix just showed up recently, my rationalise branch also had an rvxt and makesfs (I think that was it) update as well.

Post Reply