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

[dimkr]

I found it very interesting for those who want to use only browsers, or install only the programs they like.

This is exactly the audience I was targeting. Average internet users spend most of their time in the browser today, and most people don't need many pre-installed applications - for example, those who access YouTube, Spotify and Netflix through the browser don't need a music player and a video player. That's why there's a pre-installed and pre-configured browser, but only a basic set of applications, like a file manager, a text editor and an archive manager.

[Duprate]

Perfect! You can also listen to your songs that are on HDD by sending the .mp3 file to firefox! I just couldn't get the brightness control to work (SCT brightness), I installed it but it didn't work. This program is included in Fred's DebianDog Bullseye. It also works for me on FatDog64 and Slacko64. The SCT helps a lot when browsing the internet, because of the pages with a white background. It's good for anyone who has vision problems. It makes the eyes less tired.... If you have any ideas.....

[dimkr]

If you have any ideas.....

Yes - go to Setup -> Graphics / Screen and click Change to X.Org. That should make SCT work.

[Duprate]

Thanks! It worked ...

[ronriel]

Hi @dimkr ,
Somehow I can't set resolution to the default 1920x1080. I have nvidia gt1030 card. I do not have this issue with other recent puppies though.
Do I need to install an nvidia driver? Thanks.

[dimkr]

@ronriel Maybe - I don't know.

But before you try to install drivers, like @Duprate - go to Setup -> Graphics / Screen. If the Change to X.Org button appears, this is a bug, because it shouldn't.

[OscarTalks]

Hello dimkr,

Posting this to thank you for developing Vanilla Dpup
The Debian Pups have been my personal favourites for some time. I still use personal remasters of Dpup Wheezy and Dpup Stretch at home.
I have downloaded the 64bit .iso (and devx) of 9.0.6 and am testing it as a manual frugal install to HDD. All seems good so far. I watched an old episode of "Department S" via a streaming website in Firefox and there was no tearing of the image. I will probably try some compiling in the next few days. I will also check out the 32bit version as I do still play around with older hardware quite a lot. I think that was always one of Puppy's big selling points so good to still have the x86 option even though I know it is on its way out now.

[baloss]

Hello all,
I tried several ways to install this dpup to an usb stick in linux (dd command, stickpup, frugalpup) but always failed. I don't know what I am doing wrong. Is there an easy method to get it done or easy instructions to follow? Thank you.
Hardware: Lenovo ThinkPad T430s

[dimkr]

@baloss Actually I don't know - I always do the partitioning manually, and install manually.

Maybe you should try FrugalPup - you can find it in the forums.

[baloss]

Hello dimkr, how do you do a manual installation if you don't mind my asking? Maybe there are instructions posted somewhere. I tried that as well, but it did not work as expected. Thanks.

[MagicZaurus]

I tried to boot Dpup Vanilla 9.0.6 X86 from a USB and observe 2 problems.

1) Anyone knows what is happening during boot after this line is shown.

Code: Select all

probing edd (edd=off to disable)... ok

It is staying with this message for like 30-60 seconds. Probing EDD has passed already as there is a 'ok'. So the question is what comes after that.

2) After that it starts to look for the puppy_vanilladpup_9.0.6.sfs, but it crashes as the sfs cannot be found. It is looking for the sfs on SDA1, which is the internal hard disk, but the sfs is on SDB1 (USB-Stick). I suspect this kernel has problems to correctly identify the drives.

I'm not exactly sure if the above 2 problems are related. It could be that after Probing EDD, probing of some hardware fails and this is why the USB-Stick doesn't get recognized, later on. vmlinuz and initrd.gz are getting loaded from SDB1, but then it seems that after that SDB1 is not available anymore.

Usually I use BionicPup32 and it boots fine without any problems from USB on this machine. I can also boot the downloaded ISO of Dpup in a VirtualBox VM. So the ISO itself should be fine. However even in the VirtualBox VM boot I observe the long wait after Probing EDD.

[dimkr]

2) After that it starts to look for the puppy_vanilladpup_9.0.6.sfs, but it crashes as the sfs cannot be found.

I don't think it's related to the kernel, it's more likely to be a Puppy init script bug. USB boot works for me, and the x86 kernel has support for mass storage devices, like the x86_64 one.

Is it the first boot, or only after saving?

[MagicZaurus]

Now I set

Code: Select all

pupsfs=sdb1:/dpup/puppy_vanilladpup_9.0.6.sfs

and during boot it now looks at sdb1 for the sfs, but it crashes with

Code: Select all

mount: mounting /dev/sdb1 on /mnt/pdrv failed: Invalid argument
sdb1 on /mnt/pdrv as vfat mount failed.

The long wait after Probing EDD is still there, but seems to be not related and something else.

This is at first boot. So far not managed to reach the desktop.

[dimkr]

What is the file system on sdb1?

[MagicZaurus]

It's vfat and also recognized as vfat when I check /tmp/probedpartition.log after the boot crashes and drops to the terminal.

Later I will try the mount from the terminal and see if any more information from there.

I think the responsible line in mountpartition is this.

Code: Select all

mount -t $MNT_FS -o $VFAT_OUT_PARAM $MNT_DEV $MNT_DIR ;

Will try to figure it out. I see that you put a lot of effort in building this dpup and so I want to test and provide some feedback.

[MagicZaurus]

On the terminal mounting /dev/sdb1 also fails with Invalid Argument. It seems vfat filesystem is not available to the mount command.

I then did a modprobe vfat, as I read this in the busybox forum.

Code: Select all

modprobe vfat
modprobe: can't change directory to '5.10.0' : No such file or directory

So it seems the vfat module not able to load and therefore cannot mount the drive to boot.

[Duprate]

Hi, dimkr! Using Dpup, now at version 9.0.7. Working great for me. Installed on an ext4 partition; Boot EFI; Initrd Overlayfs (wiak); Kernel 5.14.13-lxpup (peabee). In just a few days of testing, he has already acquired the status of candidate for "my battle system". Small, it has only what is necessary. Each person uses it as it is or adds whatever else is needed! Perfect for my needs...

[dimkr]

Like 9.0.6 and 9.0.7, 9.0.8 will fix severe issues: https://github.com/puppylinux-woof-CE/w ... 4?closed=1.

The most bizarre issue, which makes some games unplayable, is https://github.com/puppylinux-woof-CE/w ... ssues/2534.

[linuxunix]

Hello, the terminal I use to install xfce on this system cannot be transparent
https://forum.xfce.org/viewtopic.php?id=4087
Like the problem here, I repeatedly set up and installed a lot of software packages, but it doesn’t work.
Can't be transparent, do you know what caused it?

[dimkr]

@linuxunix Try to switch to X.Org: https://github.com/puppylinux-woof-CE/w ... se-of-xorg

EDIT: this is what I see. When using Xwayland (the default), Cage takes care of compositing, so window managers with support for compositing can't do that. This means DEs like Xfce and KDE work, compositing is present (= no tearing when dragging windows and scrolling in the browser, etc') but compositing is not handled by the window manager.

[linuxunix]

If use X.Org instead, the terminal will not be transparent. You can try any terminal, but none of them will be transparent. The terminal under FossaDog can be transparent.

[Duprate]

Hi, dimkr! I updated to version 9.0.8. Related to video, Xwayland is better in image quality, but only with Xorg is it possible to run some programs. Xwayland is the future, but it still needs to be refined. For now, it is up to each one to make their own personal choice and accept the losses that each one brings. I found Dpup great to use on an Intel NUC that only has 32Gb of internal storage and 2Gb of RAM. I use it connected to a TV for streaming, and in this case Xwayland is better. I am satisfied with the results and following your work!

[peebee]

Suggestion:
Missing features and utilities in x86 that a Puppy Linux user would expect to be included?.......

GParted
md5 checksum checker by right click
Clipboard manager in systray
PupSysInfo

[peebee]

I have been able to add the LXDE desktop to x86 9.0.8........HOWEVER

1. the following additional dependencies have to be satisfied compared to other Pups:
libexif12 libstartup-notification0 libxres1

2. the 5.10 kernel exhibits a very specific and very peculiar problem - a crash occurs when doing an sfs-load of an xz compressed sfs with a blocksize of 1024K - the crash does not occur if another kernel is substituted (e.g. 5.4) nor with 5.10 if the blocksize is 512K. This 5.10 peculiarity is also seen in Slacko-8 with the 5.10 kernel so it is kernel related rather than Vanilla DPup specific. The crash does not occur in the ordinary boot of Vanilla DPup - only in the LXDE enhanced version. The relevant lines of dmesg output for the crash are below.

Screenshot.png (66.23 KiB) Viewed 1048 times

Code: Select all

[    0.000000] Linux version 5.10.0 (5.10.74-kernel-kit@6890b7908721) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Mon Oct 18 00:16:23 UTC 2021
[   66.262394] vmap allocation for size 1052672 failed: use vmalloc=<size> to increase size
[   66.262403] mount-FULL: vmalloc: allocation failure: 1048576 bytes, mode:0xcc0(GFP_KERNEL), nodemask=(null),cpuset=/,mems_allowed=0
[   66.262615] SQUASHFS error: Failed to initialise xz decompressor
[   66.262986] squashfs image failed sanity check

[dimkr]

This "crash" is an out-of-memory condition.

How much RAM do you have? Are you aware of the fact larger block sizes require more memory during decompression, and slow down decompression?

[peebee]

Only happens with kernel 5.10 from github.......all other kernels are fine........lots of memory:

Memory Allocation:
Total RAM: 7962 MB

p.s. Slacko8 is slightly different in that it needs a "larger" sfs to trigger the crash than Vanilla-DPup which crashes on a very small test sfs.

p.p.s. tried kernel 5.10 in ImpishPup32 - same crash

[dimkr]

@peebee If it's a 32 bit kernel and CONFIG_VMSPLIT_3G is set, the kernel has only 1 GB of virtual memory. You should look at /proc/meminfo, not at the physical amount of RAM you have.

[peebee]

So 5.10 should not be used for 32 bit builds???

[dimkr]

So 5.10 should not be used for 32 bit builds???

I'm trying to help you, and instead of helping me help you, you're being sarcastic.

[peebee]

So 5.10 should not be used for 32 bit builds???

I'm trying to help you, and instead of helping me help you, you're being sarcastic.

Was an honest question.....