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.

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.

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?

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?

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.

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:

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%

Sound state not preserved across boots.
Significant delay in drawing backgrounds and window content for numerous applications. (The windows themselves snap right open but are then blank for some time, Some apps open with window and background drawn but no content.
This does not apply to all apps. For instance Iron browser snaps right open and speeds across the information highway effortlessly.)
GUI freezes with any real hint of multitasking. This will occur most often when more than one window is created by an application during the completion of a specific task such as updating the package manager or setting up the network from first boot setup dialogue.
Processes often complete in the background after a period of time and the GUI unfreezes and everything appears normal.
Occasionally a hard reset is required when the GUI freezes.
Although the Iron browser will run very effeciently it will also freeze the GUI during similar circumstances such as download dialogue at mediafire opening and prompting the download location window from the browser while slinging a pop under ad into the mix

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum