Quirky Xerus 8.6 (Aug. 16), Beaver 8.7.1 (Sept. 21), 2018
Took a fast look on 8.1.5 iso
As mentioned it fails. I believe that this is because the kernel does not have AUFS, so the mounting of the layered filesystem fails and there is nothing to switch_root to.
I guess the kernel has overlayfs now, but the mount call in the init still has aufs.
As mentioned it fails. I believe that this is because the kernel does not have AUFS, so the mounting of the layered filesystem fails and there is nothing to switch_root to.
I guess the kernel has overlayfs now, but the mount call in the init still has aufs.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@Tex Dog,
The scripts only work on Linux systems, and not all of them. We have determined that they work under Fatdog 710 with those added efi files, and under Quirky Werewolf 7.4, which already has them built in.
I have no idea what you are doing with W10.
@Sage,
This was obviously a release candidate rather than a true release. We are trying to fix this without waiting for BarryK, a limited commodity who is concentrating on ARM versions these days.
We now have two working ways to install this to flash drives, so I don't believe the system itself is broken, just one means of setting it up. Until we have the fix for the ISO file, we just need to warn people against using it.
The scripts only work on Linux systems, and not all of them. We have determined that they work under Fatdog 710 with those added efi files, and under Quirky Werewolf 7.4, which already has them built in.
I have no idea what you are doing with W10.
@Sage,
This was obviously a release candidate rather than a true release. We are trying to fix this without waiting for BarryK, a limited commodity who is concentrating on ARM versions these days.
We now have two working ways to install this to flash drives, so I don't believe the system itself is broken, just one means of setting it up. Until we have the fix for the ISO file, we just need to warn people against using it.
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Oh dear. I didn't test the ISO, just assumed it would work.
I have removed the ISO from Ibiblio, the alternatives are still there.
Probably the easiest way to install is with the *.img.xz file, just "dd" it to a flash stick. Instructions are online.
Yeah, once you get it going, it seems to be working very well.
Right now, have limited time to work on it. I am working on a Slackware-based Quirky, following that line of thought right now.
I have removed the ISO from Ibiblio, the alternatives are still there.
Probably the easiest way to install is with the *.img.xz file, just "dd" it to a flash stick. Instructions are online.
Yeah, once you get it going, it seems to be working very well.
Right now, have limited time to work on it. I am working on a Slackware-based Quirky, following that line of thought right now.
[url]https://bkhome.org/news/[/url]
I 'm not sure how you install in a flash drive, but if you install in a flash by extracting and copying the q.sfs then is should work because you do not use the initrd.q/init anymore (is like a full install). If you just dd the ISO to a flash than should also fail because you go again through the initrd.q.prehistoric wrote:@mavrothal,
Can that explain why the ISO fails, but installations to flash drives derived from the ISO file work? At this point I am confused.
If true this would narrow the search for a fix considerably.
But I would give it a couple of days, I'm sure that BK will issue a new ISO soon with corrected init or kernel
(ooops see above
)== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@mavrothal,
I've confirmed your analysis by trying to reproduce the success reported above by dangerfirebob. I was able to use the universal installer in Quirky Werewolf 7.4 to install from the Xerus 8.1.5 ISO. My problem was that this approach got as far as the Quirky boot screen, but failed to find the vmlinuz kernel file.
Adding the kernel file from the ISO works, I'm using it now. Also confirmed that including the initrd.q causes failure. There is, of course, no need for the q.sfs file if the partition containing the same information is directly mounted.
I think this isolates the problem pretty clearly.
@BarryK, this is not an emergency. You've already taken action to stop use of the defective ISO. Those who want to experiment have means to use the system with the alternative setup.
I've confirmed your analysis by trying to reproduce the success reported above by dangerfirebob. I was able to use the universal installer in Quirky Werewolf 7.4 to install from the Xerus 8.1.5 ISO. My problem was that this approach got as far as the Quirky boot screen, but failed to find the vmlinuz kernel file.
Adding the kernel file from the ISO works, I'm using it now. Also confirmed that including the initrd.q causes failure. There is, of course, no need for the q.sfs file if the partition containing the same information is directly mounted.
I think this isolates the problem pretty clearly.
@BarryK, this is not an emergency. You've already taken action to stop use of the defective ISO. Those who want to experiment have means to use the system with the alternative setup.
Yes, of course. Such minimal skills as I possess are limited to testing and reporting. Testing is difficult for a distro that doesn't boot! This Forum attracts a majority of IT professionals, maybe a handful of advanced hobbyists and a lot of hangers-on like me who are keen to see the technology out in the field, although HW is my speciality. I read all the detailed coding discussion, but not sure what most of it means. I also follow instructions very well if they are detailed - most are not. Since HW is what I understand, I can report that the world is still running a vast number of 32bit machines with slow encroachment of 64bit ones. Non-specialist cannot be persuaded to move to newer kit if their present stuff is working! And, whether experts on this Forum like it or not, most of the great unwashed run with a CD/DVD drive available. Notwithstanding, many abandoned a laptop because someone in the family dropped it, stepped on it, grasped it across the screen, snapped the lid/hinge(s) and certainly aren't going to pay half as much as it's worth for a new screen and half as much again to have it fitted. Others have decamped to cheap Android tablets. Where are they going to archive their precious family photos? The 'cloud'? That is a by-word for someone else's server, just as likely to fail, or the company go bust. CD/DVD s might last 100yrs, but the jury's out on flash memory. HD s are old technology, but SSD s are hardly flavour of the month with strim and other issues abounding....obviously a release candidate...
- ain't gonna happen!Those who want to experiment have means to use the system with the alternative setup.
Hi Sage,
I have an older Acer Chomebook (3years I think) that I use quite a
lot.
It has an ethernet port and a 300+ GB hard drive, the newer Chromebooks
don't have ethernet ports or internal hard drives (they have 16 or 32
GB ssd).
Like any laptop they aren't droppable but if looked after they work
well.
I was given a bluetooth speaker this xmas and it works great with this
chromebook, much better than headphones or ear buds.
Anyhow, I love my Chromebook
I have an older Acer Chomebook (3years I think) that I use quite a
lot.
It has an ethernet port and a 300+ GB hard drive, the newer Chromebooks
don't have ethernet ports or internal hard drives (they have 16 or 32
GB ssd).
Like any laptop they aren't droppable but if looked after they work
well.
I was given a bluetooth speaker this xmas and it works great with this
chromebook, much better than headphones or ear buds.
Anyhow, I love my Chromebook
http://murga-linux.com/puppy/viewtopic. ... 021#924021
Yes, Chromebooks are interesting because they can be cheap! Doubtless you are aware of the above thread. I reckon there's a good future for hardware & SW conversions of that sort of kit. Only catch is avoiding the add-on costs if one needs to plug-in HW from previous incarnations or proprietary stuff. [Was caught out recently by a unit with a USB -C 3.1. Wasn't advertised as Apple. Genuine converter to regular USB was listed, by Apple, at ~fifty quid! ] Stories of folks spending fortunes on eg interseries connectors/ADC boards/&co for RPi s.
Yes, Chromebooks are interesting because they can be cheap! Doubtless you are aware of the above thread. I reckon there's a good future for hardware & SW conversions of that sort of kit. Only catch is avoiding the add-on costs if one needs to plug-in HW from previous incarnations or proprietary stuff. [Was caught out recently by a unit with a USB -C 3.1. Wasn't advertised as Apple. Genuine converter to regular USB was listed, by Apple, at ~fifty quid! ] Stories of folks spending fortunes on eg interseries connectors/ADC boards/&co for RPi s.
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@Sage,
Hey! I'm the one claiming to be prehistoric. Even I use flash drives.
As for problems with SSDs, I built a system with a 64 GB SSD some years ago. I wasn't sure how long it would last, but I set it up as a cache for the hard drive, so it is read-mostly. User files constantly being modified generally go to the hard drive. I recently replaced that hard drive, but that SSD keeps on ticking.
The owner was wondering about getting a replacement for something this old, but I have 120 GB and 240 GB SSDs standing by. No need to pay more for obsolete components.
I have yet to hear a complaint from anyone whose laptop drive I've replaced with an SSD.
You need to compare new problems with older alternatives.
Hey! I'm the one claiming to be prehistoric. Even I use flash drives.
As for problems with SSDs, I built a system with a 64 GB SSD some years ago. I wasn't sure how long it would last, but I set it up as a cache for the hard drive, so it is read-mostly. User files constantly being modified generally go to the hard drive. I recently replaced that hard drive, but that SSD keeps on ticking.
The owner was wondering about getting a replacement for something this old, but I have 120 GB and 240 GB SSDs standing by. No need to pay more for obsolete components.
I have yet to hear a complaint from anyone whose laptop drive I've replaced with an SSD.
You need to compare new problems with older alternatives.
-
dangerfirebob
- Posts: 21
- Joined: Fri 13 Jun 2014, 19:07
- Location: Sicily
Ah, sorry prehistoric I was not clear enough about the process I used to get to Xerus 8.1.5
a quirky experience.
Limited success truly because now the touchpad on my HP mini does not work and I have to use a usb mouse due to a missing synaptic driver dependency that seems impossible to install: xorg-input-abi-22
I will keep using this distro for a while, it seems really good all round and the HP mini touchpad is not anything special anyway + I was getting a lot of usb power failings with Xerus 8.0 probably a hardware fault, time will tell.
I went from Quirky Werewolf 7.4 to Xerus 8.0. and then used puppy package manger to upgrade to Xerus 8.1.5prehistoric wrote:
I've confirmed your analysis by trying to reproduce the success reported above by dangerfirebob. I was able to use the universal installer in Quirky Werewolf 7.4 to install from the Xerus 8.1.5 ISO. My problem was that this approach got as far as the Quirky boot screen, but failed to find the vmlinuz kernel file.
a quirky experience.Limited success truly because now the touchpad on my HP mini does not work and I have to use a usb mouse due to a missing synaptic driver dependency that seems impossible to install: xorg-input-abi-22
I will keep using this distro for a while, it seems really good all round and the HP mini touchpad is not anything special anyway + I was getting a lot of usb power failings with Xerus 8.0 probably a hardware fault, time will tell.
-
prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@dangerfirebob,
Thanks to a misunderstanding we now have a third way to install Quirky Xerus 8.1.5.
I interpreted your post to mean you used Quirky Werewolf to install to a flash drive using the ISO image for Xerus 8.1.5, even though that was defective.
I then looked at the result, and decided the main problem was a missing vmlinuz file, which I added. Do not add the initrd.q file. This is not necessary if it is directly mounting the partition with the filesystem, and contains an error.
I've just tested the resulting flash drive installation on another machine which just happens to be an HP Elitebook 6930p.
The mini-touchpad works fine on this, and is reported as a Synaptics Touchpad by hwinfo.
Thanks to a misunderstanding we now have a third way to install Quirky Xerus 8.1.5.
I interpreted your post to mean you used Quirky Werewolf to install to a flash drive using the ISO image for Xerus 8.1.5, even though that was defective.
I then looked at the result, and decided the main problem was a missing vmlinuz file, which I added. Do not add the initrd.q file. This is not necessary if it is directly mounting the partition with the filesystem, and contains an error.
I've just tested the resulting flash drive installation on another machine which just happens to be an HP Elitebook 6930p.
The mini-touchpad works fine on this, and is reported as a Synaptics Touchpad by hwinfo.
-
dangerfirebob
- Posts: 21
- Joined: Fri 13 Jun 2014, 19:07
- Location: Sicily
vlc player not working after upgrade
@prehistoric
I'm glad you got it working, I just reinstalled Quirky Xerus 8.0 after discovering that the Vlc player was not working and Xine wouldn't install codecs properly. As far as I can see my Xerus 8.1.5 was fatally corrupted.
With the Xerus 8.0 installation I had to manually add the vmlinuz file too, I also added the q.sfs file for luck, not sure whats in there! programs maybe.
The service pack upgrade to Xerus 8.1.5 is strange, there is a long wait time for it to complete, maybe I didn't wait long enough, I ended up with a lot of missing stuff. I'm not going to use that recommended upgrade again after my experience. Sounds like a fresh installation from the iso is better.
Quirky Xerus 8.0 with the Xine media player working fine again on this little HP mini.
I'm glad you got it working, I just reinstalled Quirky Xerus 8.0 after discovering that the Vlc player was not working and Xine wouldn't install codecs properly. As far as I can see my Xerus 8.1.5 was fatally corrupted.
With the Xerus 8.0 installation I had to manually add the vmlinuz file too, I also added the q.sfs file for luck, not sure whats in there! programs maybe.
The service pack upgrade to Xerus 8.1.5 is strange, there is a long wait time for it to complete, maybe I didn't wait long enough, I ended up with a lot of missing stuff. I'm not going to use that recommended upgrade again after my experience. Sounds like a fresh installation from the iso is better.
Quirky Xerus 8.0 with the Xine media player working fine again on this little HP mini.
I'm in the process of installing Quirky Xerus 8.1.5 on an Intel Compute Stick.
I bought the bottom of the range model that ships with Ubuntu because I could not bear the idea of paying a license fee to that bunch in Seattle for their detestable OS.
Wrote the QX815 image onto a microSD card, inserted the card into the stick, changed the boot order and booted into Quirky rather than Ubuntu. It's my first 'adventure' with anything UEFI.
But using Gparted to look at the Quirky partitions on the card and the Ubuntu partitions on the stick I see a small issue which, fortunately, should not be difficult to resolve.
The two Quirky partitions at 512Mb and 6.64Gb add up to 7.14Gb and that is slightly larger than the 7.12Gb internal memory of the stick with it's four Ubuntu partitions.
So it appears that I will have to shrink the QX815 image slightly in order to transfer Quirky to the internal memory of the stick.
I bought the bottom of the range model that ships with Ubuntu because I could not bear the idea of paying a license fee to that bunch in Seattle for their detestable OS.
Wrote the QX815 image onto a microSD card, inserted the card into the stick, changed the boot order and booted into Quirky rather than Ubuntu. It's my first 'adventure' with anything UEFI.
But using Gparted to look at the Quirky partitions on the card and the Ubuntu partitions on the stick I see a small issue which, fortunately, should not be difficult to resolve.
The two Quirky partitions at 512Mb and 6.64Gb add up to 7.14Gb and that is slightly larger than the 7.12Gb internal memory of the stick with it's four Ubuntu partitions.
So it appears that I will have to shrink the QX815 image slightly in order to transfer Quirky to the internal memory of the stick.
I used option 2 in Barry's install instructions
to make a bootable USB stick. It would boot up when I made some changes
to my BIOS to boot from a USB hard drive.
An unusual thing I noticed is that PLOP boot manager won't work with
USB stick. I think it's the result of the unusual formating of the stick
as explained in in Barry's blog.
to make a bootable USB stick. It would boot up when I made some changes
to my BIOS to boot from a USB hard drive.
An unusual thing I noticed is that PLOP boot manager won't work with
USB stick. I think it's the result of the unusual formating of the stick
as explained in in Barry's blog.
__________________________Unique Linux install method Posted on 24 Dec 2016, 9:44 by admin
After looking around, I can't find this method of installing Linux to a UEFI-computer described anywhere else.
The idea came to me from thinking what the UEFI-firmware does at bootup. It scans looking for ESP fat partitions. It will find the main one, for booting Windows, and it will find one on, say, a plugged-in USB drive.
The UEFI-setup then offers what it finds as candidates to boot from. So, I thought, if I create another ESP fat partition on the internal hard drive, won't the UEFI-firmware discover that also, and offer it as a candidate?
Yes, it does. It is interesting that it is named "Android-IA", which indicates that the firmware is probably designed to handle dual-boot Windows-Android. So, finding another ESP-fat partition on the same internal drive, it assumes hey that must be Android.
Just found a little issue about 'aumix' / 'PNMixer 0.5.1' .
I'm using HDA Intel with a Realtek ALC 1200 chip.
My problems are:
a) Moving the VOL slider to 100% doesn't boost the sound all the way up.
b) At each reboot VOL gets reseted to 0% - no sound.
Looking at 'urxvt alsamixer' gives some enlightenment.
slider VOL changes the 'Master' level from 0 to 100%, which is o.k.
slider Spkr changes the 'Beep' level from 0 to 100%, so this one equals the motherboard speaker, which is o.k.
slider Line changes the 'Line' level from 0 to 100%, which is o.k.
slider Pcm2 changes the 'Headphone' level from 0 to 100%, which is odd
slider IGain doesn't change anything
slider Digital1 turns 'S/PDIF' on or off
Problem a) is easy to solve - change 'urxvt alsamixer' slider 'Front' from 56% to 100%. -Solved-
Problem b) the 'aumix' data file gets written to /file/.aumixrc and to /root/.aumixrc. They are setup to the right levels but 'VOL' is still 0% after reboot.
If you open 'urxvt aumix -> file -> Load From /file/aumixrc' after reboot the VOL becomes 100%. This means that PNMixer works fine.
Ah! If you disable PNMixer in the 'Startup' the alsamixer value for 'Master' will still be set to 0% after reboot.
Has somebody the same problem?
I'm using HDA Intel with a Realtek ALC 1200 chip.
My problems are:
a) Moving the VOL slider to 100% doesn't boost the sound all the way up.
b) At each reboot VOL gets reseted to 0% - no sound.
Looking at 'urxvt alsamixer' gives some enlightenment.
slider VOL changes the 'Master' level from 0 to 100%, which is o.k.
slider Spkr changes the 'Beep' level from 0 to 100%, so this one equals the motherboard speaker, which is o.k.
slider Line changes the 'Line' level from 0 to 100%, which is o.k.
slider Pcm2 changes the 'Headphone' level from 0 to 100%, which is odd
slider IGain doesn't change anything
slider Digital1 turns 'S/PDIF' on or off
Problem a) is easy to solve - change 'urxvt alsamixer' slider 'Front' from 56% to 100%. -Solved-
Problem b) the 'aumix' data file gets written to /file/.aumixrc and to /root/.aumixrc. They are setup to the right levels but 'VOL' is still 0% after reboot.
If you open 'urxvt aumix -> file -> Load From /file/aumixrc' after reboot the VOL becomes 100%. This means that PNMixer works fine.
Ah! If you disable PNMixer in the 'Startup' the alsamixer value for 'Master' will still be set to 0% after reboot.
Has somebody the same problem?
When i tried running the latest Blender app I got the following error
_________________________________________________
I will do a test with an old version of blender which doesn't require opengl 2.1
__________________________________________________
Fatdog 64 will run Blender app nicely# ./blender
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
Error! Blender requires OpenGL 2.1 to run. Try updating your drivers.
#
_________________________________________________
I will do a test with an old version of blender which doesn't require opengl 2.1
__________________________________________________