woof-CE needs you

News, happenings
Message
Author
Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1001 Post by Sailor Enceladus »

I tried making a template for squashfs-tools (3), but every time I run ./2createpackages and type squashfs-tools, woof-CE ignores my template and just extracts the pet without running it. I tried both using FIXUPHACK and an executable pinstall.sh. The packages-slacko/squash-tools_manual shows what it's supposed to do, does anyone know why the template is ignored?

(the reason why I made this is because sfs-converter expects mksquashfs3, unsquashfs3, mksquashfs4, and unsquashfs4 all to exist to work - see /usr/local/sfsconvert/func. At some point it looks like there was a script that fixed this in 3builddistro).
Attachments
Screenshot.png
(12.36 KiB) Downloaded 733 times
woof-out_folder.tar.gz
what could be missing here...
(117.04 KiB) Downloaded 132 times

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

#1002 Post by Sailor Enceladus »

I got the template to work, by copying lines 854-871 into line 278 in 2createpackages. Guessing there is a better way though..

User avatar
rufwoof
Posts: 3690
Joined: Mon 24 Feb 2014, 17:47

#1003 Post by rufwoof »

mavrothal wrote:You might be interested in the woof-next branch of woof-CE.
Is building a "puppy" much closer to upstream (with apt-get and everything!) which you may prefer.
Thanks mavrothal. Only just got woof-CE to work for me for the first time (tried some years back with no success). Tahr 6.0.6 is working great and looking good for me so I'm content to stick with that. I had been trying out freebsd where you can build everything from source or just download pre-build binaries using pkg install (which is like Debian's apt-get install), but I'm ditching that as its just too time intensive to get things going (lots of reading, nothing pre-configured after you install ...etc.). Very nice looking though and works great when it is all running ok.

I have been booting both debian jessie and freebsd as my main primary boot choices. Debian Jessie's a long term keeper for me, however tahr pup is so neat that its tending to becoming the grub4dos menu.lst default boot :) (Especially since I've now managed to get woofce to work for me as expected).

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#1004 Post by BarryK »

Sailor Enceladus wrote:I tried making a template for squashfs-tools (3), but every time I run ./2createpackages and type squashfs-tools, woof-CE ignores my template and just extracts the pet without running it. I tried both using FIXUPHACK and an executable pinstall.sh. The packages-slacko/squash-tools_manual shows what it's supposed to do, does anyone know why the template is ignored?

(the reason why I made this is because sfs-converter expects mksquashfs3, unsquashfs3, mksquashfs4, and unsquashfs4 all to exist to work - see /usr/local/sfsconvert/func. At some point it looks like there was a script that fixed this in 3builddistro).
I don't know if it is still the case with woof-CE, but the templates only work on packages from the host distro, not on PETs.
PETs are expected to be already optimised and split up into _DEV etc.
[url]https://bkhome.org/news/[/url]

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

woof-CE needs you

#1005 Post by Billtoo »

I did a build yesterday, burned the iso to a DVD and booted from it.
Used the puppy installer to a 32gb flash drive.

# inxi -b
System: Host: puppypc20509 Kernel: 4.4.78-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: 150x41 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 31.5GB (10.7% used)
Info: Processes: 180 Uptime: 1:17 Memory: 274.9/8097.6MB Client: Shell (bash) inxi: 2.3.8
#

Updated PPM,applied the update notices with PPM,installed latest
Firefox and others with PPM + added Smplayer and Smtube.
Added proprietary Nvidia driver.

Working well so far.

*****************************************************************
EDIT: I did a second build with a different kernel.
# inxi -b
System: Host: puppypc21521 Kernel: 4.9.39-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
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
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: 161x36 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: 1126.5GB (0.8% used)
Info: Processes: 195 Uptime: 6:31 Memory: 321.9/8091.6MB Client: Shell (bash) inxi: 2.3.8
#
It works well.
Attachments
screenshot2.jpg
(39.39 KiB) Downloaded 261 times
screenshot.jpg
(90.39 KiB) Downloaded 371 times

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

trying woof

#1006 Post by sc0ttman »

I've tried to build a 32-bit Slacko 6.9.9.9, using kernel 4.4 (choice number 24 in the Kernel chooser)..

I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.

I also used an older one from a few weeks back.. Both times I have not been able to boot to X .. I get a 'no screens found message'..

The latest Woof-CE snapshot gave me a 'xorgwizard-automatic not found' error (line 117 of xwin I think), and the second and third builds I did using slightly older Woofs did not have this error message, but they still could not boot to X ..

I tried every option in xorgwizard, and am able to get a desktop on other pups on the same hardware..

Any ideas?
[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

#1007 Post by Billtoo »

@sc0ttman

Try the rationalise branch, it's the one that I used last.

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

#1008 Post by sc0ttman »

Billtoo wrote:@sc0ttman

Try the rationalise branch, it's the one that I used last.
ok will do, cheers
[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
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

Re: trying woof

#1009 Post by mavrothal »

sc0ttman wrote:I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.
6.9.9.9 was build with woof 126 commits earlier than the current snapshot.
It shouldn't, but something may have broken the slacko build since.
Try to clone the entire git repo and then

Code: Select all

git checkout 762210b829267e394fe69ae109adf9587dcdf39a #the commit 6.9.9.9 was build from
Or if you do not want to clone the entire git browse to the said commit and download from there.
If this builds OK file a bug in github
BTW, rationalize is just 14 commits behind testing. No other difference. If this works that narrows down the bug a lot.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1010 Post by norgo »

The day before yesterday I built a Slacko 6.9.9.9 RC3 too ( testing branch of 2017-07-31 ) and also chose kernel 4.4.70 PAE

Everything went without problems and Distro is working great.
Thanks for this awesome work.

# inxi -b
System: Host: puppypc28875 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: ASRock model: H87 Pro4 serial: M80-xxxxxxxxxxx
BIOS: American Megatrends v: P1.90 date: 12/06/2013
CPU: Quad core Intel Core i7-4770S (-HT-MCP-) speed/max: 800/3101 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 163x52 Advanced Data: N/A for root
Network: Card: Intel Ethernet Connection I217-V driver: e1000e
Drives: HDD Total Size: 2000.4GB (0.1% used)
Info: Processes: 190 Uptime: 1:17 Memory: 505.5/15863.1MB Client: Shell (bash) inxi: 2.3.8
Attachments
screenshot_800x500.jpg
Slacko 700 RC3
(91.39 KiB) Downloaded 470 times

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

#1011 Post by Billtoo »

I did a fresh install of woof-CE then did a build using the rationalise branch.
I get the same result as sc0ttman, x won't start.

EDIT:
Last night I did a build on another pc where woof-CE was installed jul15th,using the rationalise branch.
Boots to the desktop no problem.

Here's the build that was done on the jul15 woof-CE install,
rationalise branch:

# inxi -b
System: Host: puppypc12281 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: Gateway model: FX6860 serial: 109726660000629
BIOS: American Megatrends v: P01-A3 date: 04/19/2011
CPU: Quad core Intel Core i7-2600 (-HT-MCP-) speed/max: 1600/3401 MHz
Graphics: Card: NVIDIA GF110 [GeForce GTX 560 Ti OEM]
Display Server: X.org 1.18.3 driver: nvidia tty size: 124x27 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: 2031.9GB (0.0% used)
Info: Processes: 220 Uptime: 3 min Memory: 193.4/16192.6MB Client: Shell (bash) inxi: 2.3.8
#
Attachments
jul15woof-CE.jpg
(42.47 KiB) Downloaded 418 times

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1012 Post by mavrothal »

DISTRO_SPECS should show exactly which woof branch and commit a puppy is build from. This info (assuming no "manual" post processing) is much more specific than date or commit number, and more helpful when try to track down potential problems.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

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

#1013 Post by Billtoo »

mavrothal wrote:DISTRO_SPECS should show exactly which woof branch and commit a puppy is build from. This info (assuming no "manual" post processing) is much more specific than date or commit number, and more helpful when try to track down potential problems.
This is the jul15th woof-CE install:

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='rationalise;7a95a9e;2017-06-28 19:41:26 +1000'

*******************************************************************************************

This is from the woof-CE install done this morning, X failed to start.

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1014 Post by mavrothal »

It would appear that there are several X related commits and also several package template related commits between the "good" and the "bad" builds.
If you have the opportunity you may want to try building from ed23309c and/or ffd2229 and hopefully narrow down the range a bit more.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1015 Post by norgo »

Here the DISTRO_SPECS of my Slacko:

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

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

#1016 Post by Billtoo »

I did a new install of woof-CE testing branch and did a new build, it
has the same problem as the rationalise branch in that X won't start.

#One or more words that identify this distribution:
DISTRO_NAME='Slacko Puppy'
#version number of this distribution:
DISTRO_VERSION=6.9.9.9
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='slackware'
#Prefix for some filenames: exs: slackosave.2fs, slacko-6.9.9.9.sfs
DISTRO_FILE_PREFIX='slacko'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='14.2'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_DB_SUBNAME='slacko14.2'
DISTRO_TARGETARCH='x86'
BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'

So I did a fresh install of woof-CE with both testing and rationalise
branchs and neither one will built a working slacko 32bit.

Oh my :(

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1017 Post by norgo »

@Billtoo

when I understand this correctly, your used rationalise and my used testing branch became merged and are absolutely identical

BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

I remember that a while ago the 20-intel.conf file has been added to /etc/X11/xorg.conf.d

Driver and acceleration method are defined for card0

Your computer has two graphics cards ( intel and nvidia )
Which card is card0 and which is card1 ?
In case that nvidia is card0, this could become a problem.

Could you delete /etc/X11/xorg.conf.d/20-intel.conf and try to boot for test please.
It's only a guess, but could be the reason.

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

#1018 Post by Billtoo »

norgo wrote:@Billtoo

when I understand this correctly, your used rationalise and my used testing branch became merged and are absolutely identical

BUILD_FROM_WOOF='rationalise;bdab886;2017-07-29 17:54:31 +0800'
BUILD_FROM_WOOF='testing;bdab886;2017-07-29 17:54:31 +0800'

I remember that a while ago the 20-intel.conf file has been added to /etc/X11/xorg.conf.d

Driver and acceleration method are defined for card0

Your computer has two graphics cards ( intel and nvidia )
Which card is card0 and which is card1 ?
In case that nvidia is card0, this could become a problem.

Could you delete /etc/X11/xorg.conf.d/20-intel.conf and try to boot for test please.
It's only a guess, but could be the reason.
Hi,

I installed the latest woof-CE (rationalise branch) this morning to a new work directory on
my Gateway i7 hard drive, did a build and X wouldn't run.

The Gateway only has 1 graphics card as far as I know, Nvidia 560 ti.
I downloaded the kernel source sfs from ibiblio and the proprietary
driver from the Nvidia site and compiled it, have to blacklist the
nouveau kernel module and reboot first.

**********************************************************************

I installed the latest woof-CE (testing branch) this afternoon to a new
work directory on my HP Phenom II, AMD 6 core processor, did a build and X wouldn't run.

The rationalise branch install that did work on the Gateway was built
in the jul15 work directory on the HP hard drive (different partition too)

It seems that both branchs were updated on the same day, neither will
build a working 32 bit slacko.

Bill

User avatar
norgo
Posts: 388
Joined: Fri 13 Nov 2015, 17:19
Location: Germany
Contact:

#1019 Post by norgo »

I used the compare feature at github page and got the message nothing to compare, because both are identical.
In my case this version is working like a charm.

I'm quite sure that your i7 has a graphics chip included ;-)
Of course I don't know the hardware of your HP computer.
As I mentioned, it's only a guess and actual easy to test.

greetings

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1020 Post by mavrothal »

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
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

Post Reply