woof-CE needs you

[Billtoo]

What is a Belpup? (Edit: Ah, a Trisquel 7)
It runs ok. Most mainstream apps need the huge icu4c library so indeed may need recompiling as you suggested.

On a related note, I'm surprised that no one tries to biuld a T2 puppy (racy-like) yet.

Trisquel7 works well and it's easy to build, going to do another with a different kernel in hopes of the ati proprietary driver pets in tahrpup will work.

I think that T2 stuff is too difficult for me + not many applications availabe, the ones I like (kdegames) at least

[cthisbear]

Boot menu...my thoughts.

http://murga-linux.com/puppy/viewtopic. ... 512#869512

Chris.

[01micko]

Boot menu...my thoughts.

http://murga-linux.com/puppy/viewtopic. ... 512#869512

Chris.

Thoughts?

yes it is in need of change. It is s#*thouse.

Need a vesamenu and forget the help pages.

[ASRI éducation]

OK, I'll try to do that.
If I can better understand how git works (in this domain I am a novice)...

You may find this post useful in GIT understanding for anyone; novice or experienced, user or developer.
Hope this is helpful

A good git giude: https://rogerdudler.github.io/git-guide/

@ gcmartin and scOttman
Thank you to both for these informations.

In addition to that, I used:
- Help of github.com https://help.github.com/
- A tutorial proposed by dekani (a user of Puppy/ASRI edu) https://github.com/dekani/Puppy/blob/ma ... entGit.pdf

I started tests using the application smartgithg (v7.0.3).
I think I will now be able to participate (modestly) to the development of Woof-CE.

Regards,

[cimarron]

Today's XKCD:

[peebee]

$PATH still contains /usr/X11R7/bin

which doesn't exist anymore.....

[mavrothal]

$PATH still contains /usr/X11R7/bin

which doesn't exist anymore.....

Any older (popular) pets that use it?

[Bert]

Reposted from the programming thread:

Hi all,

Here's my problem: this code used to work in all Puppies and still works fine in Puppy Precise and Fatdog:

urxvt --geometry 80x20+2+0 -hold -e wget -h

Now, in Tahr the terminal is a short flash and then closes.
The -hold parameter is not recognized, nor is the geometry.

Running my little script (pwget) from Geany, I notice another urxvt anomaly I never saw before:

Code: Select all

urxvt: Can't locate utf8_heavy.pl in @INC (@INC contains: /usr/lib/urxvt /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /usr/share/perl/5.18/utf8.pm line 17.

To my untrained eye some stuff is missing from woof-ce. Or the urxvt is a new version with new parameter settings.
Thanks to anyone able to shed some light.
Bert

[peterw]

Hi All
Thanks starhawk. I was deleting apostraphes, etc trying to get it accepted.

I would describe myself as an enthusiastic dabbler and over the years, I have tried to build a Puppy with woof and never succeeded. What follows is a description of how I have just succeeded. I have given a verbatim log of what I did so that anyone else who has an interest, but is not an expert, (as I am definitely not) can follow and have a go. Looking at the post there is a need for some detail on this since it is not easy to find and follow some of the cryptic explanations.

By way of an explanation, my interest was re-awakened in woof-ce since I have an Acer C720 chromebook (Intel Processors) and want to get the Cypress touch pad and the lid closing switch to work with Puppy other than Fatdog. To do this I think I need to recompile the kernel with enabled options for these features. It so happens that during the woof-ce procedure I had to use a pre-compiled kernel and so I have not yet reached my objective.

Using woof-CE cloned 5-11-2015

The log bellow has bold text and that is what I typed into a terminal.

1. The machine that I used was my one with the most RAM. It is a dual core atom processor machine with 3GB of RAM (don't laugh) and 1.7GB of SWAP. I had a 26GB partition with distro that I didnt use. I did a full install of a 64 bit Puppy Tahr to it. I have read that you need 3GB of space and another source recommended a 10GBG partition for this task and I suspect that a frugal installation will not be good enough? My 26GB should be more than enough.
uname -a shows it has a kernel of 3.14.54 and is for a x86_64 machine.

2. I had already downloaded the devx file. Using PPM got the kernel sources-3.14.54_6.0.3.9.sfs and loaded them. The kernel sources took hours to load.
kernel sources-3.14.54_6.0.3.9.sfs and
devx_tahr 64_6.0.3.9.sfs
After installation free shows 0.4GB of RAM is used and no SWAP usage.

3. I already had git account and signed in . It is many years since I have tried and failed to get woof working. Searched for woof-CE and went to page. Top right gives an option to fork. Select it and you will get
a response your-user-name/woof-CE

4. To do the above I was following a procedure outlined by mavrothal .
http://murga-linux.com/puppy/viewtopic. ... 755#866755
Mavrothal says you have to configure the git and clone it. How to do this was solved by using gyros instructions. The references given by mavrothal I found difficult to comprehend.
http://www.murga-linux.com/puppy/viewtopic.php?t=90822

5. I created a directory* woof-CE in my applications and opened a terminal in it. I typed git and the response confirmed that the devx had the git programme in it.
* I now believe that creating a woof-CE directory was an unnecessary step since the cloned woof comes in it own directory.

6. In the terminal in your woof-CE directory:
git init
git config --global user.email <your email address for your git account>
git config --global user.name <your user name for your git account>
git config --global http.sslverify false
git clone https://<user name>@github.com/<user name>/woof-CE.git

And a clone of the woof-CE will be downloaded to your woof-CE directory.
At this point I realised that I need not have created a woof-CE diectory because the cloned woof-CE already comes in a directory.

Further terminal work:

git remote add origin https://<user name>@github.com/<user name>/woof-CE.git
cd woof-CE
git checkout testing

And it responds with Branch testing set up to track remote branch testing from origin. Switched to a new branch testing

I assume that it means that I have the original woof-CE and a copy that I can play with?

6. The PC was then switched off for a while. I managed to re-read.
http://murga-linux.com/puppy/viewtopic.php?t=101174
and realised that I had forgot iguleder had given instructions on building the distro. I used his instructions for this part:

./merge2out

Answers that I gave to selections from the script are:
3 which selects the x86_64 host machine
3 which selects the x86_64 target machine
I was trying to build a Tahr Puppy, however, the only option presented was 1 slackware64. I chose it.
2 compatable distro version 14.1
Enter to agree selections
Get warning about files that will be deleted,etc.
Enter to continue
script appears about workarounds.
Enter to continue
script about fixing workarounds, pet packages, etc, and exits.

Exploring the file system we find that as well as woof-ce directory we now have a directory woof-out_x86_64_86_64_slackware64_14.1

7. Open a terminal in the new directory woof-out_x86_64_86_64_slackware64_14.1

./0setup

This results in a large list of files with an option to accept them or the recommended option to reject them. I chose to accept them.
s Enter
Option Enter to continue taken

This results in a large list of files with an option to accept them or the recommended option to reject them. I chose to accept them.
s Enter
Option Enter to continue taken

This results in a large list of files with an option to accept them or the recommended option to reject them. I chose to accept them.
s Enter
Option Enter to continue taken

Option to include check of pet files which takes long time
s Enter

Warning Given about 915 resolution file. Decided to cancel check
x Enter

Warning Given about Pup-Kview file. Decided to cancel check
x Enter

Then 4 times Enter for package data base and then it downloaded many many files
Get line saying. Finished, successfully and telling me that 0setup log is in /var/woof/0setup_fail_report_no
and in the woof gui, tab Downloads dbs, click the REPORT button to retrieve log
Enter to finish script

8.
./1download

Programme downloads files and a 1download control panel appears.
As you can imagine this takes awhile. The amount downloaded was about 400MB at speeds ranging from 20kb/s to 400kb/s depending on the repository. In addition, each download has to connect with the sites which also takes time. After it finishes.
Enter to quit

9.
./2createpackages

Checking syntax
Option to build all pkgs or type generic name of one pkg.
Enter to build all pkgs

Processing takes place. About 1.8GB of Ram used and no swap. top does not show much cpu activity (some processes took about 3%) but can hear hard drive is busy.
Left it to get on with it overnight. Started midnight finished 6 hours later.

Warning: errors were logged to file ERROR-2CREATE PACKAGES

Enter to exit
Looking at directory I can see that the error files are there.

10.
./3builddistro-Z

Option about whether we want an iso or image file. And that we need at least 4GB of space for image.

Enter only for iso

Given choice on frisbee

Yes

Got END of pinstall.sh script which is good.
Enter

Option given to do a thorough dependency check which takes a long time

c Enter to do it at 06:20

Less than an hour later it had finished. There was a very long list of files that were not used. The options were Press c then enter to exit or to ignore problem press Enter to ignore them. I suspect that the finally iso will be smaller if I press c and Enter, but I am not particularly concerned about size for this activity.

Enter

A list of 14 kernels were given. Various slacko and tahr ones. I think I had already selected a slacko64 build and so went with option 12

12

Confirmation wanted that I had made this choice

Enter

Kernel downloaded (41MB)

Option given to select default languages

Enter for default

It then replaces init, test chroot, find invalid symlinks, etc. And putting item in sandbox

gtkdialog box comes up allowing us to select default themes. Changed guitar to slack64.

OK on box

Rox-Filer font size script runs
typed mono 12

x-org script gives us the option to move maybe tricky drivers to alternate-drivers.

Enter to accept

script about stripping binaries

Enter which strips the binaries

Next the programme stops asking us to confirm Kernel Mode Setting is OK for various video drivers.

Enter
Enter
Enter

PPM gui selection

Enter for classic

Enter to accept Fontsize selection
Enter to not run firefox as spot

After a while we get to the point where we have 234MB written and are asked if we want to burn it to CD

s Enter to not burn it
Enter to build devx

Warning about not having Bacon Compiler
Enter

Script finished
Enter to exit

And we have woof-output-slacko64-5.9.1 directory with the iso and devx and md5sums text in it.

I manual created a frugal install into a directory and edited by menu.1st.

The distro booted up with video. Many of the programmes worked and I suspect that with a little help from forum members the others would as well (missing libraries maybe). If I wanted to, I could check those error logs.

Of course this does not address the problem of putting changes into woof-ce.

[starhawk]

peterw, your URL text has an invalid character...

EDIT: looks fixed

[Terry H]

@peterw. Thanks for taking the time to post all the above information. It's inspiring to all other enthusiastic dabblers who have failed in the past, to have another try with woof-ce.

[musher0]

Hi, all.

I second Terry H's comment.
Very well done, peterw!
A thousand thanks for this.

BFN.

musher0

[mavrothal]

Thanks @peterw
However, it appears there is a problem somewhere and you are building from a much older version-point/commit of woof-CE.
Two indications of that. You did not see the 64bit Tahr entry in merge2out (is there on current woof-CE) and you build slacko64-5.9.1, while yesterday was 6.0.9.5 and 01micko is uploading 6.1.0.1 ISO in ibiblio right now.

I'm not sure if this is because of the way you generated your local git or something else was done.
In general you do not need to initiate a local git in order to clone a remote.
Just fork and clone your fork locally.
But what you did should not generate the role-back of the git-tree.
Maybe you had an older woof fork and cloned that locally?

[01micko]

Hmmm.. the git disaster of 19 days ago!

[mavrothal]

Hmmm.. the git disaster of 19 days ago!

[01micko]

Well at least @peterw got a sane (ish) puppy from a broken woof! ..And at least we managed a timely recovery..

[peterw]

Hi All

Terry H and musher0. Thank you for the thanks. We can hope that it helps others to use woof-ce to remaster their Puppy, although I have not taken that step yet. I think that it would be helpful if woof-ce had options to pull down packages to build a basic Puppy and a full one. Then people could practise remastering much easier. I am just thinking aloud since I don't know how easy that would be.

I gather from 01micko and mavrothal post that the git woof-ce that I used had defects and that it is now corrected? I would like to know if it has been!

The fact that it did not all go as well as it should have done is not a problem for my objective since what I actually want is get my chrome book touch pad working. I have been looking at a DOTconfig file which shows me what was compiled in the kernel, I think. I need to do some more reading but it does not appear to have the Chrome Book Platforms included in it. When I have looked at a Fedora list this is what I find:

line 5688

CONFIG_CHROME_PLATFORMS=y

CONFIG_BCMA=m
CONFIG_BCMA_BLOCKIO=y
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
CONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not set
CONFIG_BCMA_DRIVER_GMAC_CMN=y
CONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set

# CONFIG_GOOGLE_FIRMWARE is not set
# CONFIG_INTEL_MID_PTI is not set
CONFIG_IOMMU_SUPPORT=y
# CONFIG_IOMMU_IO_PGTABLE_LPAE is not set
# CONFIG_IOMMU_IO_PGTABLE_LPAE_SELFTEST is not set

I will read up how to compile the kernel for Puppy and give that a go. If some one is really nice they may read this and include it in their next kernel you never know. If I have anything to add about kernel compiling I will address it to that forum topic coming back to this one if I succeed with the task.

Many thanks
peterw

[mavrothal]

I gather from 01micko and mavrothal post that the git woof-ce that I used had defects and that it is now corrected?

Between October 19-21 the woof-CE git tree was a bit messed up. If you forked back then it may explain your outdated woof tree. If not, you may have some other problem with your fork or local clone.

I have been looking at a DOTconfig file which shows me what was compiled in the kernel, I think. I need to do some more reading but it does not appear to have the Chrome Book Platforms included in it.

Depending on the kernel version that you are trying to build CHROME_PALTFORMS may or may not be activated in the DOTconfig . However this option is only so other related options will be available for selection. Is not adding anything to the kernel by itself.

However touchpad issues may relate to kernel drivers or firmware or the xserver input modules/library.
If you have a puppy running in your chromebook see if the hardware info shows your touchpad and if there are any related errors in dmesg and Xorg.log
If you have another Linux running on your chromebook (Fedora?) try to compare notes.

[peterw]

Hi mavrothal

I have attached the files for two of the OS's that are on my Acer C720 Chromebook

Slacko64 with a kernel 4.1.11
You will notice that the cypress touch pad is not mentioned. There are no errors mentioned.

Ubuntu with a kernel 4.0.8-hgb
The touch pad is recognised and works well. It is a cypress one.

By way of an explanation. The cypress touch pad was reintroduced into the kernel at about 3.17. Since then most distros work fine with it: Ubuntus and Fedoras all work fine. When working with a Puppy I have to have a usb mouse. Others in Puppy have the same problem and usb mouse solution. In addition the lid close switch does funny things in Puppy.

I pulled my woof-ce on the 5 November and so should not have the problems that are mentioned.

To clean up git perhaps I need to to delete my PULL. Can this be done?

peterw

[mavrothal]

Slacko64 with a kernel 4.1.11
You will notice that the cypress touch pad is not mentioned. There are no errors mentioned.

The cypress touchpad driver is present in this kernel
try

Code: Select all

modprobe cyapatp

and then see if the touchpad works or if there are any errors appearing. You may need to restart X but I would first try without.

If this fails to produce anything of value, try

Code: Select all

for x in $(udevadm trigger --dry-run --verbose ) ; do udevadm info --query=all --path=$x >> udev_output.txt ; done 

and see if the touchpad is recognised there.

Regarding your git fork and clone I would say delete everything and start afresh.
Of interest there is now the rk3288 branch which is specific for chromebooks. You may want to give it a try.