Puppy Linux Discussion Forum

I can't get Safer to boot because of video problem; screen goes black and announces that the resolution/freq is out of range. I tried to use the force xorg dialog function and tell it to use radeon driver and the proper 1366x768 res but no joy, same result. This isn't a 'direct' boot from USB ...

For me, V 1.0.99 works fine for 5.7, not for 6.0.


Well, as The King said to Anna, "'Tis a puzzlement". 6.0 works fine under Ventoy .99 for me. Here's what I did:

1) Installed Ventoy on my 2nd internal drive.
2) Burned EasyOS 6.0 to my 64G USB flashdrive using usbimager.
3) Booted the Ventoy ...

Just reporting a positive in EasyOS 6:

I dl/ed xkbset_0.8-1_amd64.deb from debian's site (us.debian.org/debian/pool/main/x/xkbset) and installed.

It works just fine. I like sticky keys, so I use it to turn on sticky keys, no twokeys, no latchlock, no expiry.

I also learned about what Scarth Gap ...

For me, V 1.0.99 works fine for 5.7, not for 6.0.


I wrote the easyos6 to a 1G stick w/ Rufus and the boot process was able to modify the USB to suit itself and booted fine. I was expecting that easy wouldn't like the way rufus writes an .img, but it was able to fix what it didn't like. After ...

HarveyH wrote: Sat Jun 08, 2024 11:22 pm

The *newest* version of Ventoy, 1.0.99 works fine.

For me, V 1.0.99 works fine for 5.7, not for 6.0.

measter wrote: Tue Dec 13, 2022 10:28 pm

In EasyOS & Ub-based Puppy I've used a Debian package for xkbset to use for enabling sticky keys, but I don't know what to use for S15Pup 64.

Well, I'll be 'doggone'

The xkbset .deb installed and works just fine, as is.

In EasyOS & Ub-based Puppy I've used a Debian package for xkbset to use for enabling sticky keys, but I don't know what to use for S15Pup 64.

I see the it has an accessibility toolkit installed by default, but that isn't what I'm looking for.

measter wrote: Mon Aug 08, 2022 6:14 pm

Ventoy problem
Current Ventoy 1.0.79 (Jul 28) + either EasyOS 4.3 or 4.3.3 boot fails after kb layout option then creating a snapshot results in error: Cannot find easy.sfs

Any advice on how to get Easy to work w/ Ventoy? No help so far from the Ventoy forum.

halpad wrote: Tue Aug 09, 2022 1:56 pm

Do I(can I) skip many versions to the latest, or should I do other versions first(pain)?

I'm not particularly experienced w/ Easy OS either, but based on what experience I have, I would start from scratch; brand new install.

There's too much difference from the past.

Ventoy problem
Current Ventoy 1.0.79 (Jul 28) + either EasyOS 4.3 or 4.3.3 boot fails after kb layout option then creating a snapshot results in error: Cannot find easy.sfs

Previous problem w/ 4.0 was related to 'size' and resolved w/ a truncate command expansion. The error report was different ...

measter wrote: Sun Aug 07, 2022 5:22 pm

Error cannot find easy.sfs.

Oops. I just realized that this thread is for the 32bit; I'm talking 64. I'll take this somewhere else.

Ventoy again.

Using my previous v. of Ventoy and Easy 4.3.2 -- Error cannot find easy.sfs. This is not the same as the size problem, but I tried the truncate command anyway. No joy. Repeated for a different stick w/ Ventoy. Same.

There was a newer Ventoy 1.0.79 released Jul 28 so I updated. Same ...

BarryK wrote: Thu Jun 30, 2022 12:20 am

I have just discovered something: in Pup-Advert-Blocker, the checkbox "Mvps.org" does not work.
It is supposed to populate /etc/hosts, but nothing there.

There is still a mvps.org hosts file. It was last updated 2021 Mar.

It is at https://winhelp2002.mvps.org/hosts.txt

Most linux distros fail to recognize that BCM wifi 'out of the box' on a live boot which I can most easily solve by connecting to ethernet and installing a BCM package from the repo/s.bcmwl-kernel-source which package when run accesses other related packages to aid its installation with the ...

Ventoy 1.0.76 + tweaked Easy OS 4.0:

# truncate -s 2G easy-4.0-amd64.img

... works.

Thanks.

That report of Ventoy 1.0.76 + EasyOS 4 could have been more complete.

Populating: /mnt/ventoy2/easyof/release/easy-4.0
initrdcp: write error: No space left on device
This copy failed: cp /mnt/ventoy1/initrd /mn/ventoy2/easyos/releases/easy-4.0/initrd
Attempting to copy again...
cap:write error: No ...

Ventoy live boot problem again.

I don't know what the first screen said, but the second screen starts about mkmod -m then finding drives can't read '/etc/fstab' no such file or directory.

Error: BOOT_FS=' ' Boot filesystem is incorrect

I don't know if it is a Ventoy or EasyOS vs Ventoy problem ...

BarryK:
I was wondering if anyone still wants an email client.

I use a mail/news agent to communicate on usenet where it is useful to help resolve problems by being able to C&P from such as Easy into a usenet msg.

I recently resolved a difficult problem w/ the current LXLE focal and Claws ...

Ventoy live boot problem again.

I don't know what the first screen said, but the second screen starts about mkmod -m then finding drives can't read '/etc/fstab' no such file or directory.

Error: BOOT_FS=' ' Boot filesystem is incorrect

I don't know if it is a Ventoy or EasyOS vs Ventoy problem ...

If you want to do it without writing the img file to a usb-stick... more complicated, it is going to tax my brain right now. let's see...

Increase the file to 2G, then increase the second partition to fill the img file:

# truncate -s 2G easy-3.4.7-amd64.img
# WKG_PARTNUM=2
# Wstart=1310720 ...

No offense to either @measter and certainly NOT @BarryK: BUT, shouldn't Barry be the one addressing this. You may want to confer privately with him on this as it does affect his distro's design...this is not a Ventoy problem as I review this; even though I fully recognize that community's ...

Thanks for the replies by Clarity & jan


Oops. When I was thanking Clarity & jan, I was 'missing' BarryK's input on the next page. Thanks much BarryK.


For the time being, I'm just going to use the Easy 3.4.7 I have on the independent USB, not on the Ventoy multiboot USB. I'm carrying on my ...

Thanks for the replies by Clarity & jan

For the time being, I'm just going to use the Easy 3.4.7 I have on the independent USB, not on the Ventoy multiboot USB. I'm carrying on my 'campaign' on the Ventoy forum in the Ventoy forum thread that solved the dax problem w/ the ventoy CI tweak. Ventoy ...

It may be useful to someone to know how Ventoy works. It puts a little bitty linux on a USB and then the user can write .iso/s or .img/s or any number of different formats to the USB and the Ventoy boot gives a boot menu to multiboot whatever format has been written there. Here is one page where ...

I have a 4G USB stick that I wrote Easy 3.4.7 to w/ Win Etcher. That works just fine So, Easy is able to do whatever it needs to do on that little stick.

The problem seems to be that on a stick w/ even more 'spare room', the 16G Ventoy stick, Easy can't find a place to do whatever it does ...

The error you see is very logical.
As easy is made to write to a partition on an usb drive that is grown at first start.
The initial partition in the .img file is very small and easy is not made to grow the image file .
You could make the image bigger ( something like dd if=/dev/zero bs=1M count ...

This is a continuation of the same Ventoy problem, now w/ a different stick, more room, different Easy 3.4.5

One-time only operation, creating a snapshot of EasyOS
This will allow future follback with the Easy Version Control Manager
Populating: /mnt/ventoy2/easyos/releases/easy-3.4.5
initrd ...

I tried a different boot method and got a different error.

I don't remember the exact words of the boot option, but it was to copy easy to ram & disable drives

Boot-partition: ventoy1 Working-partition: ventoy2
Copying easy.sfs to ram, then mounting
mount: mounting /dev/loop0 on /easy_ro/easy_sfs ...

This is one view of the Ventoy USB I'm using, using fdisk:

Model: General USB Flash Disk (scsi)
Disk /dev/sdc: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 15.6GB 15.6GB primary boot
2 15.6GB 15.6GB 33 ...

Since the ventoy problem has evolved for me, I'll start a new topic.

From the earlier Ventoy problem thread:

Easy OS wouldn't boot on the current Ventoy release 1.0.74 as described in the ./dax/dax.ko not found thread (I don't know how to link threads).

There are evolutionary dev of Ventoy ...