Vanilla Dpup 9.x (x86 and x86_64) (old thread)

[pemasu]

I couldnt figure out how to boot 9.1.latest with grub4dos from hdd install. I copied files inside .img using loopimg script from jafadmin to the hdd, thanks by the way. But I dont know how to configure menu.lst to use frugalify with hdd install. I didnt find info anywhere.

Maybe I am the only fossil still using grub4dos bootloader, but if anyone knows how to use grub4dos bootloader with frugalify, I would be very thankful of the info. Then I could test 9.1.versions

9.0.latest boots fine from hdd using grub4dos. Copying files from .iso was also easier, when I didnt have to use loopimg to acces files. Easypup does not open .img files straight which was my workhorse to configure hdd for vanilla dpup.

Using 9.0.27 now. Compiling wl.ko worked straight. Using wl.ko now for internet connection. Also usb tethering using android phone works automatically by just accepting net streaming from the phone. I used usb tethering before compiling wl.ko.

First time I got bluetooth working in this testbed HP G4 laptop. It needs BCM43142A0-0a5c-216d.hcd firmware which was not included in the firmware sfs. After copying it and several attempts with bluetooth gui and pulseaudio manager I got bluetooth speakers working. Great !

snd_hda_codec_realtek is problematic, without force module removal, the shutdown halts straight and with force removal it still does not shutdown, but at least saving to the folder happens. So clean shutdown or reboot is not possible.

[dimkr]

But I dont know how to configure menu.lst to use frugalify with hdd install. I didnt find info anywhere.

You'll need to copy the kernel command-line from extlinux.cfg to your menu.lst (with modifications, probably).

@rockedge Is there any way to lock this thread and move it to viewforum.php?f=183?

[dancytron]

I used the *.tar version, just pasted it into a directory, and used my normal simplest pupmode=13 grub4dos entry.

Code: Select all

title Puppy Linux Dpup in sda1 dir Dpup
rootnoverify (hd0,0)
kernel /Dpup/vmlinuz pmedia=ataflash psubdir=Dpup
initrd /Dpup/initrd.gz

Is that wrong?

[pemasu]

Dancytron. 9.1.X latest which I downloaded did not have initrd.gz but it had frugalify.

I am now posting from 9.1.5. I downloaded vanilladpup-9.1.5-ext4-2gb-bios.img.gz and extracted the content using loopimg script which loopmounted it.

Grup4dos menu.lst which worked for me is:
title dpup os 9.1.X (sda13)
uuid 86b28755-285e-452b-b76f-15130f6a5aa5
kernel /vmlinuz root=PARTUUID=000732f3-0d init=/frugalify rootfstype=ext4 rootwait rw
initrd /ucode.cpio

I used blkid to identify uuid and partuuid. Otherwise I used included extlinux.cfg as template.

Thanks dimkr. And sorry that I polluted the thread.

[dimkr]

Is that wrong?

@dancytron It should work. The updater and the installer probably won't work, though.

But bear in mind that initrd.gz is unmaintained in the 9.1.x branch - when I look for small and safe bug fixes I can cherry-pick from latest woof-CE into the stable 9.1.x branch, I ignore fixes that go into initrd.gz. In fact, initrd.gz shouldn't even be inside the tarball: this is a bug, and I might fix this soon.

It's impossible to maintain all the complexity inside initrd.gz and fix all the technical debt (for example, inability to add yet another *drv without breaking anything), especially when other woof-CE users resist change.

@pemasu's example is good, that's exactly how you're supposed to use frugalify with your own boot loader (as opposed to, the one installed by the Vanilla Dpup installer, or the one in the prebuilt images).

[Grey]

@dimkr , I'm sorry I'm off topic. But do you happen to know why Fossa is not being built with Woof-ce? Blame rxvt, which does not download (at the last step). Last year, everything worked out. This is schmorp.de died or someone made changes to Woof-ce?

rxvt_ops.gif (26.76 KiB) Viewed 2461 times

[dimkr]

This is schmorp.de died

Maybe - your wget timed out. It could be your internet connection, or schmorp.de. Just try again, it's probably a temporary issue.

(AFAIK, fossa64 was built using a heavily modified woof-CE, with many changes not integrated into woof-CE as we know it today. And it was long ago, so you can't really reproduce fossa64, if that's what you're trying to do. The "fossa64" in woof-CE is far from the real thing.)

(You can get a snapshot of what woof-CE can build from https://github.com/puppylinux-woof-CE/w ... #artifacts)

[pemasu]

kernel /vmlinuz root=PARTUUID=000732f3-0d init=/frugalify rootfstype=ext4 rootwait rw modprobe.blacklist=snd_hda_codec_realtek ( this is one row in menu.lst )

Blacklisting the realtek sound module fixed the hanging during shutdown process. Now I get clean shutdown/reboot. And sound still works.

[OscarTalks]

Is there a bug with the setup GUI tools for mouse cursor acceleration?
Same was happening in Void32
Opening Menu > Setup > Puppy setup > Mouse/Keyboard > Adjust mouse sensitivity
The GUI is set to Acceleration=2.00 (and Threshold=4)
This seems to be stuck on 2.00
Is it still supposed to write the settings to /root/.xset.sh and then the GUI reads back the setting from there, or is there some other mechanism?
It does write something to that file when I try to change acceleration, but it looks wrong
The old pupx script (which used to do this) now only brings up the screensaver control.

[pemasu]

9.1.5 version, hdd install. Kernel source sfs from here: https://github.com/vanilla-dpup/release ... el-kit.sfs
Downloaded and inserted to the root of the partition among other vanilladpup sfs`s.
When inserted there and rebooting, booting just hangs. Removing kernel source sfs and booting, no problem, it boots okays. I did redownload the kernel source sfs and same problem.
Now I dont know how to install kernel source sfs. Help needed.

[dimkr]

Now I dont know how to install kernel source sfs. Help needed.

The kernel sources SFS is broken - see https://github.com/puppylinux-woof-CE/w ... 1024880314.

[pemasu]

This should do the trick:
$ unsquashfs kernel_sources-5.10-kernel-kit.sfs
$ rm kernel_sources-5.10-kernel-kit.sfs
$ mv squashfs-root/lib squashfs-root/usr/
$ mksquashfs squashfs-root kernel_sources-5.10-kernel-kit.sfs

Yep. Vanilladpup 9.1.5 booted after that, kernel source sfs loaded.

Compiling wl.ko...
make[1]: *** /lib/modules/5.10.0/build: Tiedostoa tai hakemistoa ei ole. Seis.
make: *** [Makefile:165: clean] Virhe 2

Yeah, it seems this puppy has finnish locale included. Anyway...error due to build symlink is wrong.
Build and source symlinks were broken. After fixing them like /usr/lib/modules/5.10.0/build, the wl.ko compiled successfully and posting using wifi. I get my android phone off the laptop.

Huoh. I should stop posting...anyway. I tried to install battery tray app, which can suspend when battery percent is 5, and...vattery-acpitool ( needed to hack the source to get it compile, vattery-0.7.5 grabbed from fatdog repo, vattery-0.7.5 source from arch repo ( compiled after that ) does not show battery icon ( red or blue ) on jwm tray. App still works ie suspends using appropriate command. I can right click the empty tray app icon place and open the app and insert the suspending command. I wonder is it due to jwm version or what that Vattery icon does not show at the tray ?

I then compiled cbatticon, grabbed missing icons from Deviant Art repo and created script to Startup for suspending: "cbatticon -l 10 -r 5 -c acpitool -s"

Ah. Read this changelog post: viewtopic.php?p=48365#p48365
I changed the header of this post accordingly. Problem fixed at woof-ce level.

[darry19662018]

Running Pups again for awhile. Had to swap kernel to 4.19.23 from Pfeco's Beowulfpup. Series 5 kernels don't boot on my Compaq CQ61.
Very nice like the BBwireless app.

[dimkr]

9.1.6 and 9.0.28 will be out soon, with a very nice list of fixes. Please use http://forum.puppylinux.com/viewforum.php?f=183 for bug reports and questions.

[OscarTalks]

Was testing 9.1.7 fresh install to a USB flash drive
System crashed to a black screen with nothing responding and requiring a hard power-off.
Not sure where to look for any further clues. Just mentioning it in case anyone else experiences anything similar.
Wonder if it was the screensaver in Xwayland kicking in after 10 minutes of mouse inactivity and doing much more than blank the screen?

I had just written it to the USB using gunzip and dd
Did a couple of steps but left screensaver activated (which I would usually turn off)
Was watching a live stream on YouTube in Firefox, when it all suddenly died including the sound.
I have a feeling something similar happened before a couple of versions ago.
Did the power-off, booted again, seemed OK, turned off the screensaver and all was well after that.

[retiredt00]

Is there a kernel change recompile in 9.1.7?
Kernel still reports as 5.10.0 but modules I have compiled in 9.1.4 and earlier fail with:

Code: Select all

~$ modprobe wl
modprobe: ERROR: could not insert 'wl': Exec format error

~$ dmesg | tail
[  182.855137] wl: disagrees about version of symbol module_layout
[  732.966508] wl: disagrees about version of symbol module_layout

~$ modinfo wl
filename:       /lib/modules/5.10.0/kernel/drivers/net/wireless/wl.ko
license:        MIXED/Proprietary
alias:          pci:v*d*sv*sd*bc02sc80i*
depends:        cfg80211
retpoline:      Y
name:           wl
vermagic:       5.10.0 SMP mod_unload modversions 
parm:           passivemode:int
parm:           wl_txq_thresh:int
parm:           oneonly:int
parm:           piomode:int
parm:           instance_base:int
parm:           nompc:int
parm:           intf_name:string

[dimkr]

Is there a kernel change recompile in 9.1.7?

Nope, the kernel is built with the same configuration.

How did compile this driver? What packages did you install before and how?

[retiredt00]

Is there a kernel change recompile in 9.1.7?

Nope, the kernel is built with the same configuration.

How did compile this driver? What packages did you install before and how?

The wl driver was compiled from Debian non-free source in 9.1.4 and installed through ‘make install”
Was running OK through 9.1.5
After doing the “simple update” to 9.1.7 (that hang tried to update the non-existing initrd.gz on a frugalified installation) the wl module was unusable with the above errors
Running ‘depmod -a’ did not change things
Something that might be relevant is that rebooting after the (hung) installation did not ask if I want to update to 9.1.7 though the 9.1.7 SFSs where used.
So something might got broken there.

Packages installed nothing major but given that synaptics reports all packages as “manual install” I can not be more specific.

[Ramachandra Iyer]

How to install google chrome. Google chrome not found Synaptic Package Manager.

[pemasu]

~$ modprobe wl
modprobe: ERROR: could not insert 'wl': Exec format error

I got this error also after updating from 9.1.5 to 9.1.7. I just recompiled wl.ko again. I dont have 9.1.5 dpup anymore, but tried wl.ko compile from dpup 9.0.27 ( 5.10.0 kernel ) and also same exec format error in dpup 9.1.7.

[Grey]

This is schmorp.de died

it's probably a temporary issue.

I still can't build anything. Not a single distro (slacko15.0 has just been interrupted at the very end). Maybe because there's http in this schmorp.de. In any case, it is impossible to get iso, although everything worked before.
PS. What is the most "beautiful" way to deal with this? Edit /woof/woof-CE/woof-code/rootfs-petbuilds/rxvt-unicode/petbuild ?

[dimkr]

PS. What is the most "beautiful" way to deal with this? Edit /woof/woof-CE/woof-code/rootfs-petbuilds/rxvt-unicode/petbuild ?

Download the files into petbuild-sources/rxvt-unicode, from a different source.

[dancytron]

Is that wrong?

@dancytron It should work. The updater and the installer probably won't work, though.

But bear in mind that initrd.gz is unmaintained in the 9.1.x branch - when I look for small and safe bug fixes I can cherry-pick from latest woof-CE into the stable 9.1.x branch, I ignore fixes that go into initrd.gz. In fact, initrd.gz shouldn't even be inside the tarball: this is a bug, and I might fix this soon.

It's impossible to maintain all the complexity inside initrd.gz and fix all the technical debt (for example, inability to add yet another *drv without breaking anything), especially when other woof-CE users resist change.

@pemasu's example is good, that's exactly how you're supposed to use frugalify with your own boot loader (as opposed to, the one installed by the Vanilla Dpup installer, or the one in the prebuilt images).

Is it your intent to not to fully support manual frugal installs in grub4dos or is that on the "to do" list?

[dimkr]

Is it your intent to not to fully support manual frugal installs in grub4dos or is that on the "to do" list?

This is not on my TODO list. My focus is ext4 images with frugalify and without initrd.gz. I can't test all possible installation types, partitioning layouts and boot loaders. Puppy's init script and installers are a huge can of worms - they generate too many issues for me to fix, and most of them take time to reproduce.

If someone wants to create a Vanilla Dpup derivative with ISO releases - you're more than welcome. It should be very easy to do, and super easy to automate (see https://github.com/vanilla-dpup/release ... /workflows).

[dancytron]

Is it your intent to not to fully support manual frugal installs in grub4dos or is that on the "to do" list?

This is not on my TODO list. My focus is ext4 images with frugalify and without initrd.gz. I can't test all possible installation types, partitioning layouts and boot loaders. Puppy's init script and installers are a huge can of worms - they generate too many issues for me to fix, and most of them take time to reproduce.

If someone wants to create a Vanilla Dpup derivative with ISO releases - you're more than welcome. It should be very easy to do, and super easy to automate (see https://github.com/vanilla-dpup/release ... /workflows).

Not ISO releases, .tar files are fine.

I understand this is a cutting edge experiment that can't support everything, so don't take it as a complaint, but you are cutting out a huge part of the user base if you don't support a multiboot frugal install on Windows 7 and older hardware. Better to say that clearly in the 1st post so people don't waste their time on a crippled version.

[dimkr]

Better to say that clearly in the 1st post so people don't waste their time on a crippled version.

I have limited time, and can't support every possible use case.

If you want ISO releases and don't want to build a Vanilla Dpup ISO yourself, you can use 9.0.x.

[dancytron]

Better to say that clearly in the 1st post so people don't waste their time on a crippled version.

I have limited time, and can't support every possible use case.

If you want ISO releases and don't want to build a Vanilla Dpup ISO yourself, you can use 9.0.x.

I understand. We all have limited time.

I'm just suggesting you put something in the top post so people know what's supported and what isn't before they download it.

[williwaw]

I have limited time, and can't support every possible use case.

If you want ISO releases and don't want to build a Vanilla Dpup ISO yourself, you can use 9.0.x.

Understandable.

Is this to say manual frugal installs are not possible with 9.1? I have tried various permutations of stanzas for both Grub4dos and rEFInd. Seems that my frugal partition (sda3) is not found in spite of being present and reported as being looked for. Perhaps a hardware issue, as an .img dd'd to a dedicated disk boots ok.

I find frugal installs useful if for no other reason than testing without maintaining separate disks just for vanilla. Whether I extract the frugal from an iso, tar or .img, I cannot seem to get a workable boot stanza that works with frugalify.

If anyone else has had success with 9.1, loaded by grub4dos or rEFInd please share your refind.conf or menu.lst
tx

[Ramachandra Iyer]

After some trail and error method, I have able to boot from internal hard disk (using complete sda7 partition) through refind.conf. on separate ESP fat partition.(640MB). My hard disk partition as follows.

sda1 8:1 0 260M 0 part
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 840.1G 0 part /mnt/sda3
├─sda4 8:4 0 571M 0 part
├─sda5 8:5 0 50G 0 part /initrd/mnt/dev_save
├─sda6 8:6 0 640M 0 part
└─sda7 8:7 0 40G 0 par

I have not checked internal hard disk partition of SSD NVME. ( new generation internal harddisk)

[dimkr]

I cannot seem to get a workable boot stanza that works with frugalify.

Just take the kernel command-line from efilinux.cfg or extlinux.cfg, and copy it as-is.