(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[musher0]

We now have a public alpha!
~~~~~~~~~~~~~~;
Hello all. (But for people in the know only. Thanks.)

After having mumbled so much against it, I finally tried the Woof-CE process in
the hope of creating an upgrade to pemasu's series of Dpup Wheezies.

My goal for now is to have a base for the echinus wm and various supporting
scripts I've written, and see how to integrate echinus with the ROX environment
within a stable Puppy.

In the longer term, I might be looking at woofing a DPup Jessie, but I'm not
promising anything. I'm trying to stick to this immediate goal of making Puppy work
with a tiling/dynamic window manager.

Now to my problem:
It's really fabulous to have all the recent additions to ppm, pfind, etc., in a Puppy
build, and it looks great. Edit: Pupsaves get created without a hassle, and this
pup jumps right into X without having to issue "xwin" at the initial black console.

However the ethernet card and the sound card are not recognized. The retrovol
panel and alsamixer are kaput. And there is nothing for any network set-up script
to set up: no eth0, nothing. Both windows come up literally blank.

~~~~~~~~~~~ (Edited)
I do not wish to go public with this draft. If you need a copy of the iso to answer
me, ask me through PM, please. If I send you the URL's, when commenting,
please always keep in mind that this is a "mongrel", a draft in need of
improvements, on the way to perhaps becoming a Puppy distro, but not there yet.
I appreciate the interest, but PLEASE DO NOT REVIEW IT AS A FINISHED
PRODUCT. In particular, I like to work with certain apps configured a certain way.
Please realize that those will not be the final settings: they are there temporarily to
speed up my work (hopefully). Many thanks for your understanding.
~~~~~~~~~~~

I asked that the "huge" kernel 3.14.56-tahr-noPAE be incorporated instead of the
default Debian one. Can that be the source of the problem?

Is there a way to incorporate sound and network drivers after the construction, or
maybe it's simply a "juncture" script or program that's missing? I'm saying this
because I've seen lots of drivers in the zdrv.sfs. (Sort of a tree list is attached.)

In any case, any and all suggestions towards a solution will be appreciated.

I'll be back later with some screen captures of the woof construct. In the
meantime, you can get an idea of the work already done on the echinus
environment here. Mutatis
mutandis! The newly woofed Dpup-Wheezy is nicer! (Paragraph edited.)

Thanks in advance. BFN.

[puppyluvr]

Hello,
Sounds like missing kernel firmware/modules.
What does "lsmod" show?

[musher0]

[musher0]

@puppyluvr :

lsmod (un)report attached, plus a couple of others.

Thanks again.

BFN.

[gcmartin]

You may want to post your WOOFCE ISO somewhere, say, on your drive.google.com (make sure you share it public so we can pull it) so community can review. Your sysinfo report shows the hardware is present, but...

[musher0]

[puppyluvr]

Hello,
lsmos showed no modules.
Look in etc/modules and lib/modules and lib/firmware.

[unicorn316386]

My first thought when reading the title: I wonder if musher0 used a different kernel than the default.

[musher0]

[musher0]

Hello all.

As a test, while waiting for the results of someone who kindly offered to test my
"mongrel", I created an iso with the new puppy.sfs but with the original Dpup Wheezy
kernel, initram, and zdrv, and the result was the same as described above : no
ethernet card and no sound card recognition.

I'm no expert, but it sounds logical that the problem would lie within the newly created
puppy sfs. If it's not in the kernel, it's not in the zdrv, the puppy sfs is probably missing
a config somewhere, a "hinge" of some sort between the kernel and the modules.

True or false?

If you have a hunch, don't hesitate to present it, that's what forums are for!!!

BFN.

[gcmartin]

I know of WOOFCE being done for TahrPUP and Slacko versions. I was not aware of DPUP version generation in WOOFCE.

I am NO user of WOOFCE as of yet, but, when generating your PUP, does it use the old PUP versions to create a brand new PUP ISO? And, your PUP's size suggest that there may be other efforts at play, as you process your build.

Curious in the build procedure you used, as, it might reflect what went wrong and at which step in the process.

[musher0]

Hello gc.

As you can see from the attached, there's a number of distros a Puppy can get
its source packages from, including arch, debian, etc. (See the menu in the middle
of the pciture.)

That was my first experience with the Woof-CE. It is normal, I think, not to get
everything we want on first try. And maybe it was my sense of adventure who chose
the "huge kernel"!

Anyway, in the picture, a bit underneath the distro list, partially hidden, there's a
box where you can choose the kernel. Maybe I should retry and choose the default
Debian kernel shown by default. And see what that more conservative choice
produces.

There's also a "kernel options" tab (a bit to the right), and maybe that's where this
apprentice got confused. I must say the doc is not as precise as it could or should be
for first-time users.

In any case, you can't learn to swim if you don't jump in the water, can you?

Thanks for helping me view this from a different angle.

BFN.

[gcmartin]

@Musher0 you have brought all of us to an good point in time. Your efforts beg an obvious question.

As intuitive as the developer(s) made this, it would be nice to have a sample set of screens which leads to a complete distro.

As a sample, it leads and helps to be able to match, at a glance, the build process which works and the effort we put trying to imagine with no guidelines in existence.

Maybe there is a sample somewhere which can be a beginner's guide-post.

Those who have plowed their way to any success, will say "its obvious". But, most of us know, this is never true. Too many people who will miss the intent the author presents. But, a guide could reduce the number who will miss as they have a working reference to fall back on to assist in understanding. (Yes, I know there will always be a few...)

You are opening our eyes to a need in Puppyland ... again.

[musher0]

Hi gc.

Thanks again for your positive attitude. We need more like you! Have you
registered with a cloning program yet ???!!!

That said. Listen to this!

I am writing this from a factory-fresh DPup Wheezy-3.5.2.9x running from DVD.

Encouraged by your suggestion, I redid about half of the Woof-CE process (the
Wheezy files had already been downloaded last time) and I rebuilt the "mongrel"
with the regular debian-provided kernel. This regular Debian kernel Is already in
the Woof-CE as a pet archive.

Now get this: while rebuilding, I noticed that there is a place in the "running
questionnaire" where Barry asks if you want the modules erased from the main
sfs and packed separately in zdrv.sfs. And he goes on saying that the modules
won't be in the main pup at boot, you will be able to recall them at first boot with
the command:

[unicorn316386]