(old)Puppy Linux Discussion Forum

I installed to a 32gb sdhc card:

I loaded the devx and kernel sources,black listed nouveau, but when I
run NVIDIA-Linux-x86_64-340.107.run it gives an error "signal caught
extraction failed" or something close to that.
When I xwin back to the desktop report-video shows vesa as the
driver.

video-info-glx 1.5.3 Wed 19 Sep 2018 on Easy Beaver 0.9.3 Linux 4.18.8 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: vesa
X.Org version: 1.19.6
dimensions: 1920x1080 pixels (508x286 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5

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

It's connected to a 32" TV via hdmi and I think I'll need the proprietary driver
for sound from the TV speakers.

Thanks.

I started from scratch and installed to a 32gb SDHC card:

System: Host: EASYPC27242 Kernel: 4.18.8 x86_64 bits: 64 Desktop: JWM git-1685 Distro: Quirky 0.9.3 beaver64
Machine: Device: desktop System: Acer product: Aspire R3610 serial: PTSCX0205302001AC12700
Mobo: Acer model: FMCP7A-ION-LE serial: U020102009703
BIOS: American Megatrends v: P01-A4 date: 11/03/2009
CPU: Dual core Intel Atom 330 (-MT-MCP-) speed/max: 1599/1600 MHz
Graphics: Card: NVIDIA ION VGA
Display Server: X.Org 1.19.6 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: NVAC version: 3.3 Mesa 18.0.5
Network: Card-1: NVIDIA MCP79 Ethernet driver: forcedeth
Card-2: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Drives: HDD Total Size: 192.1GB (1.6% used)
Weather: Conditions: 60 F (15 C) Time: September 19, 12:17 PM EDT
Info: Processes: 125 Uptime: 27 min Memory: 164.5/1494.3MB Client: Shell (bash) inxi: 2.3.56

The nouveau driver is working okay with xine to play a movie dvd but
have to use external speakers for sound.

Thanks.

I did a fresh install to a flash drive using EasyDD on my Dell Optiplex 745 USFF.

System: Host: QUIRKYPC30632 Kernel: 4.18.8 x86_64 bits: 64
Desktop: JWM git-1685 Distro: Quirky 8.7 beaver64
Machine: Device: laptop System: Dell product: OptiPlex 745 serial: JR9TYD1
Mobo: Dell model: 0GW726 serial: ..CN6986179L0353.
BIOS: Dell v: 2.6.6 date: 06/26/2011
CPU: Dual core Intel Pentium Dual E2180 (-MCP-) cache: 1024 KB
clock speeds: max: 1788 MHz 1: 1744 MHz 2: 1788 MHz
Graphics: Card: Intel 82Q963/Q965 Integrated Graphics Controller
Display Server: X.Org 1.19.6
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1280x1024@60.02hz
OpenGL: renderer: Mesa DRI Intel 965Q version: 2.1 Mesa 18.0.5
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.18.8
Network: Card: Broadcom Limited NetXtreme BCM5754 Gigabit Ethernet PCIE
driver: tg3
IF: eth0 state: up speed: 1000 Mbps duplex: full
mac: 00:1a:a0:6c:73:4b
Drives: HDD Total Size: 515.8GB (0.5% used)
ID-1: /dev/sda model: WDC_WD5000AAKX size: 500.1GB
ID-2: USB /dev/sdb model: Cruzer_Blade size: 15.7GB
Partition: ID-1: / size: 6.3G used: 2.2G (35%) fs: ext4 dev: /dev/sdb2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 99 Uptime: 50 min Memory: 583.7/3872.7MB
Client: Shell (bash) inxi: 2.3.56

I updated the package manager, installed a couple of packages including Chromium 69. Everything is working well at the moment.

It is interesting that Xorg now defaults to using the modesetting driver, not the intel driver (when your PC has intel video). I did see a post about that somewhere.

You would have to run the Xorg Wizard to change to the intel driver.

scsijon sent me an email, the 4.18.8 kernel has a security flaw. I am compiling 4.18.9 right now.

There was another email with some bug reports, one of them was that the youtube downloader doesn't work. Will check that out. Looks like a bugfix release is coming very soon!

Note about youtube downloader, it uses youtube-dl, which is a python script. It has to be upgraded every now and again, as youtube.com people move the goal posts, to foil downloaders.

It can happen that after a while the mouse is freezing and the system dead (unable to use any key). So I returned to Quirky Xerus64 8.6

BarryK wrote:It is interesting that Xorg now defaults to using the modesetting driver, not the intel driver (when your PC has intel video). I did see a post about that somewhere.

You would have to run the Xorg Wizard to change to the intel driver.

It is the same in UpupBB.

Thank you very much Barry for sharing your work. Only one question.
Do you plan to build the devx pet for Beaver?
Thank you!

In my previous post I reported that I was able to install Quirky Beaver 8.7 to flash drive using the EasyDD utility. It has been working very well. I decided to download the ISO and used it do a full install to the sda1 hard drive as I have done with Quirky installs in the past. I used the Quirky universal installer to do so.

Installation appeared to proceed normally. When I attempted to boot to the hard drive installation it stalled early in the process. At the point where a dialogue states "setting root to hd0,0" the process hangs. The description of the file system that normally follows that statement was displayed but the boot process stopped at that point.

I decided to try again with an alternate install using the *.usfs.xz image and the provided installation script. The same thing happened when I used this method. The boot process stalled at the same spot.

The md5sum is correct for each download.

Finally I did a frugal install using the Quirky universal installer to the same hdd partition.

Success. I am able to boot a frugal install from sda1 but I cannot boot a full install from the same partition.

I have been able to boot 8.5 and 8.6 versions from full hdd installs on this box. Can I do something to fix this?

EDIT:

I booted into 666philb's new Bionicpup64 and ran grub4dos from that installation. I noticed that it returned a different uuid number for sda1 than was generated at installation. I tried booting to a full hdd install at that point. The boot process stalled at a similar point in the process and displayed the following message:

@ Barry

thank you for the new release and for still providing quirky.iso files!!

Using my live-flash stick (Xerus64-8.6; see page 55 of this thread) for several weeks now, I'm still fascinated with this option's versatility. Especially the easy way in which the save-function - when quirky is running in live-usb mode - can be used to very efficiently create “RAM-snapshots“, at any moment as well as at every reboot/shutdown, has stimulated my fantasy.

Finally, although being not more than an interested layman who is vastly lacking specific knowledge in this field, I would like to put up for discussion the following idea/question:

How far could the above-mentioned “RAM-snapshots“ be considered pragmatic “container equivalents“ if they were saved onto an encrypted partition on the live-flash stick which optionally can be removed or inserted, depending on what it currently is thought to serve as (removed for security reasons; inserted during saving processes and while booting/rebooting)?

I'm thinking of a variety of individually/arbitrarily configured “RAM-snapshots“ which are stored in the encrypted partition and, depending on the user's wish, can be copied/moved onto the working partition, in order to replace there the currently running variant and to be the automatically selected option at next boot. This procedure, admittedly is ungainly in so far as it requires rebooting to switch “containers“, but it potentially also might have advantages because, this way, some of your current EasyOS security-problems maybe could be avoided/circumvented. If I'm right, every containerised variant could be stored in a quirky folder which contains its specific s_sfs, q.sfs, s.sfs and Q_ID.

Moreover, as compared to a full install of EasyOS onto a flash stick, the above quirky variant could drastically increase the stick's durability since the read/write processes can be optimally reduced.

apologies, in the case my question is too embarrassing!

kind regards

In regard to my previous post (2 above this) it occurred to me to remove the uuid from the menu.lst entry altogether. I replaced the grub4dos generated entry with this one.

title Quirky Beaver64 8.7 (sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro

It worked. Problem solved.

I am still curious as to why grub4dos configuration generated one uuid on installation to hdd from the flash drive install of Quirky and another uuid was generated by grub4dos configuration when run from 666philb's BionicPup64 on another partition.

lluamco wrote:Thank you very much Barry for sharing your work. Only one question.
Do you plan to build the devx pet for Beaver?
Thank you!

I was a bit slow in uploading it. It should be there now.

Note, Quirky Beaver 8.7.1 will be released in about an hour after this post.

lp-dolittle wrote:apologies, in the case my question is too embarrassing!

Not at all embarassing! I read all suggestions, and think about it, even if many times I don't reply. Sometimes, there is a new angle to think about, that I file away, mentally.

roadkill13 wrote:In regard to my previous post (2 above this) it occurred to me to remove the uuid from the menu.lst entry altogether. I replaced the grub4dos generated entry with this one.

title Quirky Beaver64 8.7 (sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro

It worked. Problem solved.

I am still curious as to why grub4dos configuration generated one uuid on installation to hdd from the flash drive install of Quirky and another uuid was generated by grub4dos configuration when run from 666philb's BionicPup64 on another partition.

Hmmm, yes. I don't know. Will postpone investigating that for awhile, want to rush out Quirky Beaver 8.7.1, with important fixes.

At least, you have identified a manual fix, that others can apply, thanks for that.

Reneetje wrote:It can happen that after a while the mouse is freezing and the system dead (unable to use any key). So I returned to Quirky Xerus64 8.6

I have been using 8.7 for awhile, it hasn't happened to me. Mouse and keyboard freezing seems like a Xorg problem -- is any app running at the time, like the web browser?

I am at the mercy of Ubuntu, just using their DEB packages. The only really significant change from 8.6 that is my doing is the kernel, 4.18.8 compiled by me.

On a usb stick, it is possible to substitute the kernel and modules from 8.6, find out if that is the cause.
'vmlinuz' would go into the first partition, /lib/modules and /lib/firmware into the second.

Version 8.7.1 is out, see blog post:

http://bkhome.org/news/201809/quirky-be ... eased.html

I installed to a 64gb sandisk flash drive:

System: Host: QUIRKYPC21340 Kernel: 4.18.9 x86_64 bits: 64 Desktop: JWM git-1685
Distro: Quirky 8.7.1 beaver64
Machine: Device: desktop System: HP product: 260-p029 serial: CNV6240BWP
Mobo: HP model: 81B4 v: 01 serial: PFPSK0BWJ301LW UEFI [Legacy]: AMI v: F.04 date: 05/10/2016
CPU: Dual core Intel Core i3-6100T (-MT-MCP-) speed/max: 1015/3101 MHz
Graphics: Card: Intel HD Graphics 530
Display Server: X.Org 1.19.6 driver: intel Resolution: 1600x900@60.00hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) version: 4.5 Mesa 18.0.5
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
Drives: HDD Total Size: 1061.7GB (1.2% used)
Weather: Conditions: 74 F (23 C) Time: September 22, 1:06 AM EDT
Info: Processes: 141 Uptime: 4 min Memory: 138.9/3873.7MB Client: Shell (bash) inxi: 2.3.56

I updated petget and installed some applications.

Seems to be working okay so far,
Thanks.

Maybe me but using the command
gunzip --stdout beaver64-8.7.1-8gb.img.gz | dd of=/dev/sdb bs=1M
does not work because the image I downloaded was xz not gz.
Is this a typo and should I just correct it? If I am confused I guess others might be as well.

The compressed .img file has been further compressed into a .gz file. Right click and 'extract here' to provide the compressed .img file. Suggest you ignore that 'dd-' stuff the gurus use and install USB Image Writer, which contrary to some commentary, IS available for Linux, is graphical and is (fool?)proof even for YT; it runs well out of Mint, MX and other majors, but would avoid Arch-based stuff like Manjy if you're not too confident.

Hi Sage

Thanks for the quick reply. The problem is that the instructions here: http://distro.ibiblio.org/quirky/quirky ... nstall.htm are not in agreement with compressed image file you download. I think the instructions need clarification.

I was using Fatdog to write the image to the USB and it obviously failed. I have used xz instead of gunzip in the command and that does something to the USB but does not write a good image and you need to reformat the USB afterwards. I will look at Image Writer and see if I can install it in a Puppy. Barry has a utility to make writing the USB easy but that also refers to gz nor xz.

Hopefully, Barry reads this post and corrects me or the instructions. Quirky is to good for potential users to be put off because of queries such as this.

peterw wrote:Hi Sage

Thanks for the quick reply. The problem is that the instructions here: http://distro.ibiblio.org/quirky/quirky ... nstall.htm are not in agreement with compressed image file you download. I think the instructions need clarification.

I was using Fatdog to write the image to the USB and it obviously failed. I have used xz instead of gunzip in the command and that does something to the USB but does not write a good image and you need to reformat the USB afterwards. I will look at Image Writer and see if I can install it in a Puppy. Barry has a utility to make writing the USB easy but that also refers to gz nor xz.

Hopefully, Barry reads this post and corrects me or the instructions. Quirky is to good for potential users to be put off because of queries such as this.

peterw,
Yes, you are correct, I uploaded the usb flash stick image file with xz compression, it should have been gz compression, for compatibility with the instructions.

Actually, easydd can handle either, however, the various Windows image writer apps only understand zip or gz compression.

So, I have recompressed the file, now *.img.gz, it is uploading right now.

A much bigger file, 601MB, but have to pay that price for it to work with the Windows apps. Watching it upload...

...yep, done. It is now at ibiblio.org:

http://distro.ibiblio.org/quirky/quirky ... ver-8.7.1/