Puppy Linux Discussion Forum

[ab12]

Hi,

Has anybody else had this problem. When I boot xerus64-8.3.1 from a fresh boot it sticks on the line creating zram. However, when booted from a reboot from any other distro on the the thumb-drive, it boots flawlessly. I've tried several xerus64 installations, i.e full and frugal, but does the same thing every time.

Many thanks for any advice or solutions on the matter.

[Philh]

How did you install it.
What format is your partition you installed to.

my grub
title Quirky Xerus64 8.3 frugal in sdb1 dir xer648v3
uuid DA72-4947
kernel /xer648v3/vmlinuz rw
initrd /xer648v3/initrd.q

I dont know if you need rootwait added.
vmlinuz rootwait rw

[ab12]

Thanks for your response Philh.

Standard installation from DVD iso image
Partition format ext2

Grub supplied by Xerus during installation, cut and paste into Grub4dos, two options supplied, used both:

title Quirky Xerus64 8.3 frugal in sdb7 dir xerus64-8.3
find --set-root --ignore-floppies /xerus64-8.3/initrd.q
kernel /xerus64-8.3/vmlinuz rootwait rw
initrd /xerus64-8.3/initrd.q

title Quirky Xerus64 8.3 frugal in sdb7 dir xerus64-8.3
uuid 15187091-8ec2-4191-9d71-3d1d63a285de
kernel /xerus64-8.3/vmlinuz rw
initrd /xerus64-8.3/initrd.q

Both of these setups will boot on reboot from another puppy.

[Philh]

If you look in /boot/initrd-tree you could check the install_specs match your installation.
Maybe copy the Q_ID to your xerus64-8.3 folder though it shouldnt need it.
Have you tried a different usb port.
My flash drive is fairly slow but it boots ok.
Maybe try adding qfix=fsck to the kernel line.
But apart from that I dont know.

[Leon]

[ab12]

Thanks for your responses. Tried them all, but no luck!

[lp-dolittle]

unsure whether this thread is still active, I would like to put up for discussion the following issue

Running Quirky Xerus 8.3 final (frugal installation on an ext4 formatted partition), I wanted to download the recent Xenialpup64-7.5-uefi.iso, as well as the Xenialpup32-7.5-uefi.iso. Confused by the fact that the download-manager unexpectedly disappeared while downloading, I repeatedly restarted the download of Xenialpup32-7.5-uefi.iso, and finally realised that several download processes had been interrupted or were running simultaneously. In order to avoid corrupted data transfer, I decided to stop downloading, deleted the notifications in the download manager protocol and shot down Quirky Xerus 8.3, choosing the 'save' option.
To my surprise, next booting resulted in the QuickSetup first-run screen! All previous settings had disappeared. The QuirkyXerus64-8,3 folder and its sub-folders were still present, but the PPM showed no more entries (all previously downloaded pets and all the related data were lost!).

Any suggestion? Can anybody explain this reaction? Which was the relevant faulty manipulation that caused the data loss? Is there an unrecognised security risk?

thank you for feedback

[Leon]

[lp-dolittle]

Thank you, Leon, for your response.

My actual problem is/was not the download. There was enough space, everything ok. My question relates to the data loss. I cannot figure out which of my manipulations made the installed pets (inclusive the related data) disappear. I do not know how to evoke this effect if I wanted to do it intentionally.
What happened in the mentioned situation (cancelled download after deletion of the fully or partially downloaded new iso-files) when I shot down Quirky Xerus 8.3 using the save option? Why did my manipulations affect the PPM?

kind regards

[BarryK]

Quirky Xerus x86_64 version 8.4 is out!

Blog announcement here:

http://bkhome.org/news/201802/quirky-xerus-x8664-version-84-released.html

Have fune!

[Billtoo]

I installed to a 32gb SDHC card:

video-info-glx 1.5.3 Fri 9 Feb 2018 on Quirky Xerus64 8.4 Linux 4.14.17 x86_64
0.0 VGA compatible controller: NVIDIA Corporation ION VGA (rev b1)
oem: NVIDIA
product: MCP79 Board - hornet-0 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.18.4
dimensions: 1440x900 pixels (373x231 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: ION/integrated/SSE2
OpenGL core profile version string: 3.3.0 NVIDIA 340.106

Intel(R) Atom(TM) CPU 330 @ 1.60GHz
Core 0: @1599 1: @1599 2: @1599 3: @1599 MHz

I needed to use NVIDIA-Linux-x86_64-340.106.run --no-unified-memory to
get the proprietary driver to compile.

That's it so far,
Thanks.

[Leon]

Hello Barry,

Congratulations and thank you very much for another Quirky.

I made a manual frugal install of Quirky 8.4 to USB flash drive by keeping a savefile from Quirky 8.3 and everything works perfectly.

Thank you for upgrading a kernel. Version 4.14.17 is patched against Meltdown vulnerability according to
https://github.com/speed47/spectre-meltdown-checker/blob/master/spectre-meltdown-checker.sh

For me Quirky 8.3 was “the lucky build” that I was searching for to replace my previous distro for everyday use, fast and rock solid Dpup Wheezy 3.5.2.8 created back in 2013 by forum member pemasu.

Every new release that I tried, that was created after Dpup Wheezy 3.5.2.8 and based on Woof-CE toolkit, had a bug that obviously became a feature and is a show stopper for my frugal installs on vfat and fat32 partitions.
The bug was described in 2015 by forum member “keyboard”.
http://murga-linux.com/puppy/viewtopic.php?t=96177&start=345&sid=4d0fba6e7baf3cf2561094a5a3645d8e

Quirky became a distro that we, old fans of manual frugal install was waiting for, because:

- Work at flash speed even on older computers.
- Saving session is optional.
- Having no worries about a savefile running out of space.
- Having just one single savefile with no need for additional sfs files.
- I can installed it and booted even from 1 GB Canyon USB flash drive made back in 2006, with enough additional free space for save data out of the savefile on one single vfat partition.
- Hard disk can be spinned down to minimize the power use and heat generated by the hard disk.
- It works from every computer I had a chance to install to, from more then 10 years old laptops to newer ones like Gigabyte BRIX Mini-PC.
- It is compatibile with Ubuntu Xerus Xenial Repositories and security updates with Long Term Support.

This distro is really a pleasure to use.

[ETP]

Hi Barry,

Thanks for 8.4 which seems to improve upon 8.3 and is very responsive with a low memory footprint.
The 8GB image was installed to a 32GB USB3 stick using using 7-Zip and Win32diskimager in Win10.

In addition to the upgrades mentioned above by @Leon I have witnessed no ethernet connection
problems caused by the link detection & DHCP changes in earlier kernels.

A couple of minor issues that have been reported previously, do however persist:

1. An error is logged due to the now unneeded presence of <Include>/root/.jwm/jwmrc-personal</Include>

2. A possible issue for NVIDIA/nouveau users was the lack of Direct Rendering - i.e. hardware acceleration.
That was also evident in Chrome which I subsequently installed and was resolved using PKGget Package Manager
to install the MESA VDPAU acceleration drivers:

mesa-vdpau-drivers_17.2.4|Mesa VDPAU video acceleration drivers
libllvm5.0_5.0-3|Modular compiler and toolchain technologies runtime library

3. Volume level is not preserved across reboots and always defaults to zero. That is a pain if running an
automatic startup sound and/or an Internet connection alarm as I do.
The script /etc/init.d/aumix is strange in that the comments at lines 17 & 18 state that it does not work
with alsa but the body of the script seems to have disabled provision to do so.

As a temporary fix I placed the following simple script in /root/Startup to set a safe level of 55%

[Leon]

[roadkill13]

Full install: