woof-CE needs you

Message

Billtoo · #916 Post by **Billtoo** » Fri 19 May 2017, 02:05

I did a fresh woof-CE install and build using the rationalise branch:

# inxi -b
System: Host: puppypc4639 Kernel: 4.4.68 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.1
Machine: Device: desktop System: Hewlett-Packard product: HPE-410f serial:
Mobo: FOXCONN model: 2AB1 v: 1.00 BIOS: American Megatrends v: 6.02 date: 07/21/2010
CPU: Hexa core AMD Phenom II X6 1045T (-MCP-) speed/max: 800/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 137x48 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 1000.2GB (10.3% used)
Info: Processes: 196 Uptime: 50 min Memory: 353.6/7985.1MB Client: Shell (bash) inxi: 2.3.8
#

Video-Info 1.5.1 - Thu 18 May 2017 on Slacko64 Puppy 6.9.9.1 - Linux 4.4.68 x86_64

Chip description:
0.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 5570]
X Server: Xorg Driver used: radeon
X.Org version: 1.18.3
dimensions: 3840x1080 pixels (1016x285 millimeters)
depth of root window: 24 planes
Added applications with PPM + compiled Smplayer,Smtube,and Audacious + Google Chrome as an SFS.

It's working well so far.

Billtoo · #917 Post by **Billtoo** » Fri 19 May 2017, 12:32

New woof-CE install and new build:

# inxi -b
System: Host: puppypc27461 Kernel: 4.4.68 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.1
Machine: Device: desktop System: Hewlett-Packard product: p7-1246s serial:
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: 136x36 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: 3000.6GB (2.1% used)
Info: Processes: 181 Uptime: 1:08 Memory: 418.4/11973.6MB Client: Shell (bash) inxi: 2.3.8
#

Video-Info 1.5.1 - Fri 19 May 2017 on Slacko64 Puppy 6.9.9.1 - Linux 4.4.68 x86_64

Chip description:
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

X Server: Xorg Driver used: nvidia
X.Org version: 1.18.3
dimensions: 3840x1080 pixels (1414x392 millimeters)
depth of root window: 24 planes

Works good so far.

Billtoo · #918 Post by **Billtoo** » Sat 20 May 2017, 20:30

Woof-CE build, not the latest woof-CE but close (may 19th rationalise
branch)

# inxi -b
System: Host: puppypc4267 Kernel: 4.4.68 x86_64 (64 bit) Desktop: JWM 2.3.2 Distro: Slacko64 Puppy 6.9.9.1
Machine: Device: desktop System: Hewlett-Packard product: 200-009 serial:
Mobo: Hewlett-Packard model: 2B38 v: 1.02 serial:
UEFI [Legacy]: AMI v: 80.03 date: 12/15/2014
CPU: Dual core Intel Celeron 2957U (-MCP-) speed/max: 900/1400 MHz
Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 115x42 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom Limited BCM43142 802.11b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 1032.2GB (5.2% used)
Info: Processes: 160 Uptime: 27 min Memory: 160.1/1853.4MB Client: Shell (bash) inxi: 2.3.8
#

It's working well on this HP mini desktop.

Lassar · #919 Post by **Lassar** » Tue 23 May 2017, 19:56

Billtoo, what puppy are you running woof-ce in?

Woof-ce does not work in tahrpup64.

Got it to work some in precise puppy.

But it wouldn't make a iso.

All it would do, is to make is a sfs.

What is the best puppy to run woof-ce in?

belham2 · #920 Post by **belham2** » Tue 23 May 2017, 20:22

Lassar,

Also posted this in your other misplaced thread (under Projects). I just ran through the exact standard woof-CE build for Xenial x86_64 using the 4.9.15 kernel, and despite a few errors showing up when looking for packages (of which I did nothing to correct), woof-build kept going and produced a bootable ISO and devx. In fact, I am booting from it right now.

So I am not sure what's wrong on your end, but there isn't any problem per se right now in Xenials, Tahrs, and/or Slackos (I've done all, and Billtoo has done even more). Make sure you are following the simple build steps, and make sure your build partition is "bare", and is at least 8GB or more.

Here are pics of your pkg-spec Xenial build I just did (p.s. not sure why you are wanting to do a "woof-CE" build of Xenail64 when it's version is still on 7.0.7 and Phil has already moved on to & released 7.0.8.4 in the project section):

Billtoo · #921 Post by **Billtoo** » Tue 23 May 2017, 20:38

I built Slacko-6.9.9.1 this morning from Slacko-6.9.6.7.
I've installed it to my macmini.

▶—— BASE SYSTEM ——◀

PC Manufacturer: Apple Inc.
Product Name: Macmini6,1

Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Max Speed: 2500 MHz
Current Speed of Core 0:2000 MHz, 1:2501 MHz, 2:1400 MHz, 3:1700 MHz
Max Speed: 2500 MHz
Current Speed of Core 0:2000 MHz, 1:2501 MHz, 2:1400 MHz, 3:1700 MHz
Max Speed: 2500 MHz
Current Speed of Core 0:2000 MHz, 1:2501 MHz, 2:1400 MHz, 3:1700 MHz
Max Speed: 2500 MHz
Current Speed of Core 0:2000 MHz, 1:2501 MHz, 2:1400 MHz, 3:1700 MHz

Frequency governor : ondemand
Freq. scaling driver : acpi-cpufreq

Phys 0 (coretemp) : +55.0 C (high = +87.0 C, crit = +105.0 C)
Core 0 (coretemp) : +53.0 C (high = +87.0 C, crit = +105.0 C)
Core 1 (coretemp) : +55.0 C (high = +87.0 C, crit = +105.0 C)

Memory Allocation:
Total RAM: 16112 MB
Used RAM: 1941 MB
Free RAM: 14171 MB
Buffers: 152 MB
Cached: 1608 MB
Total Swap: 12040 MB
Free Swap: 12040 MB

Actual Used RAM: 181 MB Used - (buffers + cached)
Actual Free RAM: 15931 MB Free + (buffers + cached)

Linux Kernel: 4.1.39-pae (i686)
Kernel Version: #1 SMP Tue May 23 10:13:21 EDT 2017
PAE Enabled: Yes

Distro: Slacko Puppy 6.9.9.1
Window Manager: JWM v2.3.2
Desktop Start: xwin jwm

It's working okay so far.

@Lassar

I sent you a PM.

Lassar · #922 Post by **Lassar** » Wed 24 May 2017, 03:14

I am positive that woof-ce does not work from a tahrpup64 live cd.

Booted up tahrpup64 6.05 cd.

Followed the readme file to a T.

Created a bare 10 GB partition.

Installed git from the puppy manager.

Cloned woof-ce using git.

Installed devx sfs module. Also tried it without the devx sfs module.

Did ./merge2out script from woof-ce.

Changed to the woof-out directory.

Followed all the command line scripts.

./0setup
./1download
./2createpackages
./3builddistro

Where it fails is in the ./3builddistro script

It does not create a iso, not even a sfs file.

So since woof-ce does not work in tahrpup64 live cd, what live cd does it work in?

Sailor Enceladus · #923 Post by **Sailor Enceladus** » Wed 24 May 2017, 04:17

Lassar wrote:chroot: can't execute 'echo': No such file or directory
ERROR: could not 'chroot' into sandbox3/rootfs-complete
This means that something is incomplete, perhaps a library
needed by bash. Check it out. Have to exit script now.

I think, in your woof-out*/packages-xenial64/busybox/bin folder, there should be a shortcut called "echo", which gets copied into rootfs-complete. If this file doesn't exist, perhaps it's because you formatted your 10GB woof-ce partition with something that can't create Linux shortcuts (FAT32 maybe? I normally use ext4 or ext2).

Billtoo · #924 Post by **Billtoo** » Wed 24 May 2017, 16:08

Lassar wrote:I am positive that woof-ce does not work from a tahrpup64 live cd.

Where it fails is in the ./3builddistro script

It does not create a iso, not even a sfs file.

So since woof-ce does not work in tahrpup64 live cd, what live cd does it work in?

I built xenialpup64 this morning in Tahrpup64-6.0.6.

I created a work directory and loaded the devx, opened a terminal in the work directory and entered the commands in the terminal one at a time as they completed.

Maybe you need to install Tahrpup64 to the hard drive and run it instead of running it from the live cd?

That's your Kodi pet that I installed in this Tahrpup64 a few weeks ago.

belham2 · #925 Post by **belham2** » Wed 24 May 2017, 16:56

Lassar wrote:I am positive that woof-ce does not work from a tahrpup64 live cd.

Booted up tahrpup64 6.05 cd.

Followed the readme file to a T.

Created a bare 10 GB partition.

Installed git from the puppy manager.

Cloned woof-ce using git.

Installed devx sfs module. Also tried it without the devx sfs module.

Did ./merge2out script from woof-ce.

Changed to the woof-out directory.

Followed all the command line scripts.

./0setup
./1download
./2createpackages
./3builddistro

Where it fails is in the ./3builddistro script

It does not create a iso, not even a sfs file.

So since woof-ce does not work in tahrpup64 live cd, what live cd does it work in?

Hey Lassar,

Tell me if this picture below looks familiar to you? I am right now in a Tahrpup64-Live-CD 6.0.5CE (burned last summer) on a computer with only ram, 8GB of it, and a 16GB usb 2.0 added afterwards for the Xenialpup64-7.0.8.4 build attempt (someone was busy last night at woof, the small xenial build errors I saw yesterday are no longer there ). Still, does this look familiar, Lassar, appearing in the ./3builddistro-Z step after you've chosen your kernel and it tries to do its thing?....

Sailor Enceladus · #926 Post by **Sailor Enceladus** » Wed 24 May 2017, 17:11

belham2, before you delete it, can you take an image of the packages-xenial64/busybox/bin folder and maybe sandbox3/rootfs-complete/bin? I wanna see

belham2 · #927 Post by **belham2** » Wed 24 May 2017, 18:22

Sailor Enceladus wrote:belham2, before you delete it, can you take an image of the packages-xenial64/busybox/bin folder and maybe sandbox3/rootfs-complete/bin? I wanna see

On yee orders, Captain, here be thar images!

belham2 · #928 Post by **belham2** » Wed 24 May 2017, 19:21

Sailor,

Just to followup, I cannot get the build to get past that error point when I am using the Live-CD. I even created a savefile, stored it on the USB used for builds, then re-booted the Tahr64-6.0.5CE Live-CD, and it's just like Lassar says: it stops everytime with "chroot" error, saying it cannot chroot into 'sandbox/rootfs-complete'.

But, get this, I just quickly stuck everything (savefile included) in a frugal folder, booted Tahr64-6.0.5CE up, used the same build USB I had been using when trying to do it "live", and the build sailed right thru ./3builddistro-Z and created a bootable ISO & DEVX of Xenial64-7.0.8.4.

Weird stuff. Have any clues what would be going on when a build is tried from a "live" CD and using a storage device attached for the build? I've got plenty of RAM and storage space, so it can't be those things. Plus, I used ext4. I'm clueless other than thinking it's a permissions problem even before we reach the ./3builddistro-Z step. But where though...Live-CDs are run as root, so......???

Sailor Enceladus · #929 Post by **Sailor Enceladus** » Wed 24 May 2017, 19:27

Wow belham! Interesting, so echo DOES exist... that's even stranger than I thought.

I added this to merge2out in the meantime, it seems to kill VFAT and NTFS attempts dead before you can begin

Code: Select all

#!/bin/bash
#BK nov. 2011

[ -d ./woof-arch ] || [ -d ./woof-code ] || [ -d ./woof-distro ] || exit

# test: make sure permissions and symlinks will work first
EXTWARN="echo Please build Woof-CE on a linux filesystem - ie. EXT4, not"
rm -f linuxtest1
rm -f linuxtest2
ln -s merge2out linuxtest1 2> /dev/null
if [ ! -f linuxtest1 ] ; then
  $EXTWARN VFAT
  exit
fi
cp merge2out linuxtest2
if [ ! `ls -l linuxtest2 | head -c10` = "-rwxr-xr-x" ] ; then
  $EXTWARN NTFS
  exit
fi

Lassar · #930 Post by **Lassar** » Thu 25 May 2017, 01:28

It is weird, that it won't work from a live cd.

You are right, I think someone has been busy working on woof-ce.

Now the tahr64-6.0.5 live cd, running the ./3builddistro script, almost gets to the end, before it hits a critical error.

Code: Select all

Cannot open '../woof-output-xenialpup64-7.0.8.4-uefi/xenialpup64-7.0.8.4-uefi.iso'

https://paste.ee/p/LyQFx

I have xubuntu on my computer, and don't want to mess around with boot issues by installing puppy linux.

Hopefully, this problem will get fixed, so I can get working on a Kodipup lite iso.

mavrothal · #931 Post by **mavrothal** » Thu 25 May 2017, 08:18

Lassar wrote: Now the tahr64-6.0.5 live cd, running the ./3builddistro script, almost gets to the end, before it hits a critical error.
Code: Select all
Cannot open '../woof-output-xenialpup64-7.0.8.4-uefi/xenialpup64-7.0.8.4-uefi.iso'
https://paste.ee/p/LyQFx

It would appear that you do not have grubx64.efi in your sandbox3/rootfs-complete (hint-> "Can't find Grub2" in the output - did you includ it?)
As a result support/uefi_cd.sh fails to build the ISO image and then there is nothing to burn.
3builddistro may need a test that uefi_cd.sh exited without errors before proceeding further, though.
You may want to raise an issue in woof-CE about it.

01micko · #932 Post by **01micko** » Thu 25 May 2017, 10:48

mavrothal wrote:
Lassar wrote: Now the tahr64-6.0.5 live cd, running the ./3builddistro script, almost gets to the end, before it hits a critical error.
Code: Select all
Cannot open '../woof-output-xenialpup64-7.0.8.4-uefi/xenialpup64-7.0.8.4-uefi.iso'
https://paste.ee/p/LyQFx
It would appear that you do not have grubx64.efi in your sandbox3/rootfs-complete (hint-> "Can't find Grub2" in the output - did you includ it?)
As a result support/uefi_cd.sh fails to build the ISO image and then there is nothing to burn.
3builddistro may need a test that uefi_cd.sh exited without errors before proceeding further, though.
You may want to raise an issue in woof-CE about it.

I'm pretty sure we've killed this one stone cold dead.. 23ec192, efd0a66, 2ed6bf1..

mavrothal · #933 Post by **mavrothal** » Thu 25 May 2017, 16:07

01micko wrote: I'm pretty sure we've killed this one stone cold dead

At the end woof-CE will be so foolproof, even <name in your mind> will be able to build a puppy

The downside is that no one will be releasing any puppy then...

belham2 · #934 Post by **belham2** » Thu 25 May 2017, 16:56

mavrothal wrote:
01micko wrote: I'm pretty sure we've killed this one stone cold dead

At the end woof-CE will be so foolproof, even <name in your mind> will be able to build a puppy
The downside is that no one will be releasing any puppy then...

Cant you guys leave a few things broken and messed up on purpose in woof, to deter the fly-by-night build attempters? It ain't no fun when there's nothing to fix going through easy 3 or 4 steps and suddenly a fully working ISO/OS is staring ya in the face. When there's nothing to fix, when no reason to try & flex some grey matter, it's like the magic is gone and one's feeling of participating in that 'puppy-mysterious-building' magic or experience is eqaully gone... God I hate progress sometimes

Oh well, guess not. Heading up to ask my android-robot in the Out house what I'm eating tonight and what time I'm being tucked in.

Sailor Enceladus · #935 Post by **Sailor Enceladus** » Thu 25 May 2017, 17:49

belham2 wrote:Cant you guys leave a few things broken and messed up on purpose in woof, to deter the fly-by-night build attempters? It ain't no fun when there's nothing to fix going through easy 3 or 4 steps and suddenly a fully working ISO/OS is staring ya in the face. When there's nothing to fix, when no reason to try & flex some grey matter, it's like the magic is gone and one's feeling of participating in that 'puppy-mysterious-building' magic or experience is eqaully gone... God I hate progress sometimes Oh well, guess not. Heading up to ask my android-robot in the Out house what I'm eating tonight and what time I'm being tucked in.

Your post reminds me of this thread

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

woof-CE needs you

woof-CE needs you

woof-CE needs you

woof-CE needs you

In which puppy's does woof-ce work in?

Re: In which puppy's does woof-ce work in?

woof-CE needs you

woof-CE needs you