Development of DPup Buster-7.9.0.1

[musher0]

Hello all.

Picking up from this page, so as not to disturb
the flow in the thread there.

~~~~~~~~~~~~~

I built a DpupBuster following 666philb's recipe, but I cannot go farther
than the opening config panel at 1st boot.

Various issues I tried to compensate:
-- I have constructed an adrv with the reportedly missing progs in
ERROR2create text. (Please see at bottom of this post.)

-- I found everything: abiword and gnumeric and the goffice libs, pkgs,org
has for Debian Buster.

-- The missing pets: f2fs, 01micko's netmon_wce, etc. in previous pet
repos at ibiblio.

-- palemoon I have decided to make into its own sfs. Palemoon is not
everybody's choice. An independent sfs, people can choose not to load
and use whatever else they prefer.

-- I took the liberty of including the latest links browser as a stand-in
browser, disguised as /usr/local/bin/defaulthtmlviewer.

-- I'l make this adrv available upon request.

-- the only prog I could not include in this adrv is osmo, since the latest
version is GTK3. I cannot build anything GTK3 on this DPupStretch that
has only GTK2. So the newest osmo will have to be built on the new
DPupBuster.

-- isolinux is reported missing. So I was stuck with no iso to speak of:
I created one that doesn't boot, hehe.

-- I was able to boot directly from HD in a distinct directory. That is when
I found out that I could go no farther than the opening config panel.
Is the absence of Xdialog causing that? (Although it is in the adrv.)

-- I tried booting with pfix=nox. In the initial black console, I am told that
my cf (Canadian-French) keyboard is non-existent.

Maybe the people at woof-CE can check that? (And double-check if all
other keyboards have been included as well?) Funny thing is, it appears in
.../woof-out_x86_x86_debian_buster/sandbox3/rootfs-complete/lib/keymaps/cf.gz.

~~~~~~~~~~~~~

Any help appreciated. Conversely, offering same.

Also, I do not want to steal anybody's show. I saw that at least 9 people
have downloaded 666philb's recipe.

If someone is more advanced than I am on building this DPup Buster, I'll
take a step back: I'm definitely better at re-mastering than I am at
"direct woofing".

This attitude to avoid the development of the DPupBuster becoming as
erratic as the development of the DPupStretch became 2 years ago.

IHTH. BFE.

~~~~~~~~~~~~~

ERROR: 'abiword' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build abiword.

ERROR: 'cdrtools' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build cdrtools.

ERROR: 'f2fs-tools' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build f2fs-tools.

ERROR: 'firewallstatus' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build firewallstatus.

ERROR: 'gnumeric' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build gnumeric.

ERROR: 'goffice' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build goffice.

ERROR: 'gtkhash' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build gtkhash.

ERROR: 'netmon_wce' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build netmon_wce.

ERROR: 'osmo' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build osmo.

ERROR: 'palemoon' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build palemoon.

ERROR: 'syslinux_xenial' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build syslinux_xenial.

ERROR: 'Xdialog' package does not exist.
You will need to find a matching package and place in packages-pet,
or packages-deb-buster as appropriate.
Do it, then rerun this script and choose to build Xdialog.

[musher0]

HI guys.

I changed the video card from a radeon RV250 to a NVidia Mx4400. On
the strength of a 2011 post of a member here that the radeon was
freezing hsi Puppy desktop. No joy.

Incidentally, I chanced upon it on the newegg site. Over 10 years later,
this card is now worth 203 USD! I didn't pay that much at the time, only
99 CAD. I couldn't believe it.

I think I'll let a couple of days flow by, perhaps a couple of weeks. As I
mentioned elsewhere, the screen of my dual core portable went grey, so
I dusted off my trusted 3100+ single core Acer Aspire workhorse. A
trusted workhorse, yes, except it takes over 10 minutes to squash a
puppy system. Until I replace or repair my portable dual-core.

That, plus no clues in sight about the hang.

TWYL.

[666philb]

hi musher0

i think that you've taken my advice and removed tahr & xenial repos from the build. now you have a list of the missing apps, re-add tahrs & xenials repos and you should get a working build that you can use to build the missing apps.

Xdialog is the missing package that is probably causing all your problems.

you could try 01mickos petbuilds for some of the missing stuff https://github.com/puppylinux-woof-CE/p ... slacko_142

or even add dpup busters native abiword & gnumeric which are gtk3
but i would recommend the petbuilds for a working samba package

[musher0]

Thanks for your reply, 666philb.

Yes I have applied the restrictions you suggested in the other thread.

~~~~~~~~~~

Since it appears that Xdialog is the culprit, will someone have the charity
of providing an already "puppy-built" Xdialog for this DPup Buster 32 bit?

As I said, I am experiencing a hardware setback ATM. So please spare me
the following "administrative run-around":

Code: Select all

./Xdialog.petbuild 
./Xdialog.petbuild: ligne 4: ../func: No such file or directory
./Xdialog.petbuild: ligne 5: ../build.conf: No such file or directory
./Xdialog.petbuild: ligne 44: retrieve : commande introuvable
./Xdialog.petbuild: ligne 45: extract : commande introuvable
mv: cannot stat 'Xdialog': No such file or directory
./Xdialog.petbuild: ligne 30 : cd: Xdialog-2015.08: No such file or directory
./Xdialog.petbuild: ligne 31: ./configure: No such file or directory

For that's what it looks like.
And this what trying to compile it the usual way looks like:

Code: Select all

checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
./configure: line 8631: syntax error near unexpected token `1.2.0,'
./configure: line 8631: `  AM_PATH_GTK(1.2.0, ,'

Thanks for your understanding.

~~~~~~~~~~

BFN.

[musher0]

Hello all.

What is the prefix for this DPup's pupsave file? TIA.

Developing fom a pupsave might be the best shortcut. When satisfied with
the results, "pour" selected contents of the pupsave in the puppy sfs
directory / template.

I know, this is a rebel's road... I never was for "purity". It's generally a pain.
Mother Nature says: "Mixed breeds make stronger individuals."

BFN

[musher0]

Hello all.

Passing the hand to whoever has more resiliency / more talent..

I just resquashed the main dpupbuster sfs incorporating Xdialog and
netmon_wce from peebee's UpupBionic-32, thinking the versions were
close enough. Then tried to boot into DPupBuster-32.

The netmon utility was accepted (that error went away), but UPupBB's
Xdialog did not melt the freeze.

I'm making available at the augras.eu Puppy repo, the add-on sfs I have
assembled for DPupBuster. Also the devx. Hopefully making those
available can save some research / development time to the person(s)
picking up this development after me. URL: All of my preliminary work
on DpupBuster-32 is in this Internet dir:
http://augras.eu/puppy_linux/?dir=mushe ... pBuster-32
md5 sums are attached.

Good luck.

[musher0]

Hello all.

I got an improvement with the attached 32-bit compilation of
Xdialog-2015.08 from the FATdog repo. I included it in the unsquashed
main sfs and resquashed. (Sorry for using a proven re-mastering
technique!)

At least I was able to get to xorgwizard and try to use it. I say "try"
because it was to no avail: all options offered in xorgwizard end you
up on a frozen mouse AND keyboard on the 1st boot panel.

So I went to look at /etc/X11/xorg.conf. That configuration file, my friends,
has the keyboard and mouse commented out. The one called
xorg.conf-auto-pc doesn't, but it is not the active one. The joke is that
if you make it active, the mouse and keyboard will become commented
out when you type < xwin >. No kidding.

As I said, this Buster really needs a more resilient, a more stubborn and/
or a more talented dev than I.

While I was in the CLI part of DPupBuster, I ordered myself a pupsave
file. Pupsave files in DPupBuster are called
"dpupbustersave-PuppyDevelopmentIsAPainInTheB.?fs"

I also temporarily changed my MarbleMouse to a run-of-the-mill mouse,
and rebooted. Nah. Nothing. Still a big freeze.

Also, on purpose, I included echinus as the WM and edited
/etc/windowmanager accordingly. The Buster Pup does react to this file,
the familiar jwm taskbar was absent from the desktop. So this Buster is
not still-born, it shows sign of life. But IMO, it badly needs a copy-edit of
Xorg, and whatever else is related to it, at the woof-CE level.

(I know nothing about X.org and get eczema just thinking about learning it.
So I'm out. There are more interesting things to try out: the fish shell, for
example.)

BTW, using kernel 4.1.30-xenial_PAE with this. I'm sure some wise guy is
going to tell me it's the wrong kernel to use with the Buster?

Adios! I've done my share, spending two days on this; now it's your turn.

[musher0]

Hi.

The same freeze ocurs when switching to EmSee's 4.4.1 kernel stored at
archive.org, here.

Maybe I should get rid of X.org and do a CLI only DPupBuster. The initial
black console works fine on it. What do you think? Well, there has never
been a CLI Puppy!

BFN.

[musher0]

Hello all.

I brought back in the Buster the earlier version of the ROX-Filer from
DPupStreth, and the Buster still freezes at the same place. So it's not the
kernel, it's not the ROX environment. What is it?

666philb said that I should redo the job uncommenting the non-Debian repos.
I'm being a Thomas, here: how does he know that this freeze bug would go
away if I uncommented those repos?

Phil, did you create a prototype of the Buster, that you're keeping
to yourself? I'm all for learning new things, but this is pushing it.

BFN.

[musher0]

Hello all.

Short status report:

Thanks to josejp2424 for providing me via PM with a 4.19.20 kernel to test.
Unfortunately, this kernel did not solve the "congelacion" problem any
better than Emsee's kernel 4.4 did. However José is telling me that he is
doing further work on this kernel. One good thing that I did find out using
José's kernel is that it boots fine to "nox", and it does not seem to slow
down this 12-year old workhorse.

Thanks also to scsijon who suggested that pcur might be interfering.
This I still have to check.

As for me, I am beginning to think that the Xorg provided may be faulty,
since the "congelacion" is happening just after the < xwin > command
has brought me to the desktop. I started doing research on Xorg, but
phew, what a mountain to climb.

Or perhaps a missing kernel module?

BFN.

[musher0]

Fun, fun, fun!

Out of thoroughness, I thought I'd do a 2nd run, as PhilB suggested above.

Code: Select all

/3builddistro-Z
./DISTRO_PET_REPOS: ligne 22: z : commande introuvable
./DISTRO_PET_REPOS: ligne 22: https://distro.ibiblio.org/puppylinux/Packages-puppy-bionic-official: No such file or directory
./DISTRO_PET_REPOS: ligne 22: z : commande introuvable
./DISTRO_PET_REPOS: ligne 23: z : commande introuvable
./DISTRO_PET_REPOS: ligne 23: https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE/testing/woof-distro/x86/ubuntu/xenial/Packages-puppy-xenial-official: No such file or directory
./DISTRO_PET_REPOS: ligne 23: z : commande introuvable
./DISTRO_PET_REPOS: ligne 24: z : commande introuvable
./DISTRO_PET_REPOS: ligne 24: https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE/testing/woof-distro/x86/ubuntu/Packages-puppy-tahr-official: No such
file or directory
./DISTRO_PET_REPOS: ligne 24: z : commande introuvable

Transl.: « commande introuvable » means "command cannot be found".

That is what I get doing a 2nd run for a re-build. I just love this part:

./DISTRO_PET_REPOS: ligne 23: https://raw.githubusercontent.com/puppy ... l-official: No such file or directory

Isn't that the repo PhilB suggest that I skip the 1st time? Well, the 2nd
time around, it turns out it does not exist!!! Yippee!

Stopping development of this DPupBuster here before it really turns into
a bust. (Pun intended.)

~~~~~~~~~~~~~~
Anyway, not all is lost. Anybody interested will find some sfs' created
as a side production of this experiment. In particular, I uploaded at my ftp
site at augras.eu (pls see URL a couple of posts sbove), an AbiGnumGoff.sfs,
that contains abiword, gnumeric and the goffice support files. They come
straight from the Debian Buster repo at pkgs.org.

I'm unable to test them since I have no working DPupBuster (hehe), but if
a valiant soul is willing to do the test, please go ahead.

~~~~~~~~~

Also I uploaded there an sfs of the current Palemoon seated at /opt,
but with the necessary symlink in /usr/bin and a *.desktop file. Any takers?

~~~~~~~~~~~~~~

BFN.

[musher0]

Hello people.


Excellent news : Puppy now has a Buster! Please see attached capture.

My hunch was right: Xorg was crippled.
The un-funny thing is... the cause was human.
How can I say this nicely?... 666philb, next time you provide a woof-CE
recipe, please make sure your _00build.conf file DOES NOT ERASE Xorg's
mouse and keyboard drivers from the sandbox3/rootfs-complete dir!!!

(...)
# rm -r usr/lib/xorg/modules/input/kbd_drv.so
# rm -r usr/lib/xorg/modules/input/mouse_drv.so # Modif. : musher0
(...)

So I restored the xorg keyboard and mouse drivers, and on next boot I
gracefully landed on the DPupBuster desktop.

It's still missing:
-- sound
-- internet detection
-- jwm's xdgmenu creator, which is why I am using the echinus WM ATM.

Probably a long way to go, lots of testing ahead, but we do have a
working prototype! Yay!

UPDATE --
Puppyists may even shortly have two DPupBusters to choose from. Yep.
I just received a PM from our very competent and hard-working colleague
josejp2424 asking me to test HIS DPupBuster.

This I like: choice for Puppyists! LONG LIVE PUPPYLINUX!

BFN.

[foxpup]

Excellent news : Puppy now has a Buster! Please see attached capture.

Congrats musher0!
Remember this?

Passing the hand to whoever has more resiliency / more talent..

You're very persistent! But with Latin temperament.

Maybe I should get rid of X.org and do a CLI only DPupBuster. The initial
black console works fine on it. What do you think? Well, there has never
been a CLI Puppy!

That would be special! Has there really never been one? maybe from technosaurus or Iguleder/dima... ?
And since you like different wm.

[musher0]

Thanks for the compliment, foxpup!

But there is indeed more resilient and competent than me... The dev who
is already at DPupBuster-7.0.9 version 2... Please see attached capture.

This is a very polished Puppy. I tried a bit of everything on it: geany,
copying, mounting partitions, playing some music. Writing this message
from it, actually.

Let's all ask José to make it available to us as soon as he is comfortable
with publishing it.

BFN.

[rufwoof]

Maybe I should get rid of X.org and do a CLI only DPupBuster. The initial black console works fine on it. What do you think? Well, there has never been a CLI Puppy!

exit X

I've recently modified my initrd to contain mc, nice command line file manager with a integral text editor. Attached is a actual console snap taken using fbgrab

I'm chroot'ing the main desktop rather than switch-root'ing, so I can exit the chroot to re-enter back into that init layer as/when desired. A trick I've added is to mount my sda3 partition within init, so it can't be mounted nor the mount point seen within the main gui desktop. To copy/move files from sda3 you have to use the likes of that init layer mc file manager.

[musher0]

Hi rufwoof.

My remark was a "spur of the moment" thing. If you want to develop a
CLI DPupBuster, go right ahead, you're probably the best-prepared and
best-qualified for the task.

~~~~~~~~~~

@all:
Back to José's work, the only negative I found is that it seems unable to
save the sessions on the DVD. (Or was it my disc?)

Now that José has come up with a wonderful distro, what's the point of me
hedging on and banging my head on a problem-ridden prototype?

I suggest / vote that José's DPupBuster-7.9.0.2 become the official
representative Puppy for this series, that 01micko write a press release
for DistroWatch saying so, that José's DPupBuster be referenced on the
official Puppy sites, and so on.

Remember, folks, my main interest is under-advertised, little-known
window managers that I feel have potential. I'll do it if I have to, it's ok,
but I don't really enjoy building Pups.

BFN.

[musher0]

Hello all.

Great news!

josejp2424 has officially released DPupBuster-7.9.0.2 this
evening. Please see here for download info and more.

Enjoy!

[musher0]

Hello all.

Chugging along with copy-editing / development of DPupBuster-7.9.0.1.

I don't have internet card nor sound card detection. Therefore, no sound, no Internet on this prototype.

However lspci says that this machine has two ethernet cards:

#### No Internet
lspci | grep net
00:0a.0 Ethernet controller: D-Link System Inc DGE-530T \
Gigabit Ethernet Adapter (rev 11) (rev 11)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. \
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
/lib/modules/4.19.20buster/kernel/drivers/net/ethernet/realtek/8139cp.ko

The REALTEK RTL-8139 module is in the modules dir. at /lib.
How do I activate it? TIA.

And one sound card:

#### No sound
lspci | grep audio
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)

in this case, I could find no VIA subdirectory in the /lib/modules.
Any insight appreciated.

BFN.

[musher0]

Hello all.

Slowly ploughing ahead.

I never noticed this until I needed it: BK has placed in /etc/rc.d a file called
MODULESCONFIG. It includes, among other possibilities, an ADDLIST string
that is read by the BootManager. You can use it if ever some of your
hardware is not recognized at boot.

Do read the interesting explanations in that file for the ADD and other
possibilities: they might come in handy some day.

I added the names of my sound card driver and ethernet card driver to
the ADD string. That solved it for the Internet connection, but it's not
enough for the sound card. Apparently, this is a known repulsion (?)
problem between Debian and ALSA: Debian seems to prefer apulse ?

More later.