Unable to install KL to Lenovo Ideapad laptop

Moderator: Forum moderators

User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

@wiak I think I am retrieving from the GitLab repo. And I do a daily git pull just in case of an update or addition. I don't store the initrd-latest.gz because of exactly this issue.

The ISO boot stanza is this:

menu.lst

Code: Select all

set distname=KLV-Spectr
set revision=RT
set savepart=Persistence
set savedir=Sessions
set bootlabel=QEMU

#
# menu.lst
#
#color NORMAL            HIGHLIGHT       HELPTEXT       HEADING
#       f/b               f/b              f/b           f/b
color light-gray/black yellow/red cyan/black light-blue/black

timeout 10
default 0

# 0.4.6a
graphicsmode -1 800 600
splashimage /boot/splash.jpg

# FOR BOOTING FROM CDROM:

title %distname%-%revision% (LABEL, RAM0 no persistence)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=RAM0 net.ifnames=0
 initrd /initrd.gz
  
title %distname%-%revision% (LABEL, RAM2 save on demand to %savepart%_%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=LABEL=%savepart%=/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz 

title %distname%-%revision% (LABEL, direct saves to %savepart%_%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=LABEL=%savepart%=/%savedir%/%distname%-%revision% net.ifnames=0
 initrd /initrd.gz

title %distname%-%revision% (LABEL, RAM2 save on demand to sda1/%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=/mnt/sda1/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz

title %distname%-%revision% (LABEL, direct saves to sda1/%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=/mnt/sda1/%savedir%/%distname%-%revision% net.ifnames=0
 initrd /initrd.gz

title %distname%-%revision% (LABEL, RAM2 save on demand to %bootlabel%_%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=LABEL=%bootlabel%=/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz 

title %distname%-%revision% (LABEL, direct saves to %bootlabel%_%savedir%)
 kernel /vmlinuz w_bootfrom=LABEL=%distname%=/ w_changes=LABEL=%bootlabel%=/%savedir%/%distname%-%revision% net.ifnames=0
 initrd /initrd.gz
 
# EXTRAS, for example, /mnt/sr0 w_copy2ram:

title %distname%-%revision% (/mnt/sr0 RAM0 no persistence w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0 w_changes=RAM0 net.ifnames=0 w_copy2ram
 initrd /initrd.gz
 
title %distname%-%revision% (/mnt/sr0 RAM2 save on demand to %savepart%_%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=LABEL=%savepart%=/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0 w_copy2ram
 initrd /initrd.gz

title %distname%-%revision% (/mnt/sr0 direct saves to %savepart%_%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=LABEL=%savepart%=/%savedir%/%distname%-%revision% net.ifnames=0 w_copy2ram
 initrd /initrd.gz
 
title %distname%-%revision% (/mnt/sr0 RAM2 save on demand to sda1/%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=/mnt/sda1/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0 w_copy2ram
 initrd /initrd.gz

title %distname%-%revision% (/mnt/sr0 direct saves to sda1/%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=/mnt/sda1/%savedir%/%distname%-%revision% net.ifnames=0 w_copy2ram
 initrd /initrd.gz
 
title %distname%-%revision% (/mnt/sr0 RAM2 save on demand to %bootlabel%_%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=LABEL=%bootlabel%=/%savedir%/%distname%-%revision% w_changes1=RAM2 net.ifnames=0 w_copy2ram
 initrd /initrd.gz

title %distname%-%revision% (/mnt/sr0 direct saves to %bootlabel%_%savedir% w_copy2ram)
 kernel /vmlinuz w_bootfrom=/mnt/sr0  w_changes=LABEL=%bootlabel%=/%savedir%/%distname%-%revision% net.ifnames=0 w_copy2ram
 initrd /initrd.gz
 
title
  root

title Help - Boot Params
  configfile /boot/grub/menu_phelp.lst

title
  root
  
# Boot from Partition Boot Sector

title Boot first hard drive (hd0,0)
  root (hd0,0)
  chainloader +1 || chainloader /grldr || chainloader /bootmngr

title
  root

# additionals

title Grub4Dos commandline\n(for experts only)
  commandline

title Reboot computer
  reboot

title Halt computer
  halt

loopback.cfg

Code: Select all

set distname=KLV-Spectr
set revision=RT
set savepart=Persistence
set savedir=Sessions
set bootlabel=SG2D

loadfont /boot/grub/font.pf2

# https://help.ubuntu.com/community/Grub2/Displays
color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black

### loopback.cfg: All work with SG2D
menuentry "${distname}-${revision} (RAM0 no save persistence)" {
    linux /vmlinuz w_bootfrom=${iso_path} w_changes=RAM0 net.ifnames=0
    initrd /initrd.gz
}

menuentry "${distname}-${revision} (RAM2 save on demand to ${savepart}_${savedir})" {
    linux /vmlinuz w_bootfrom=${iso_path} w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
    initrd /initrd.gz
}

menuentry "${distname}-${revision} (direct saves to ${savepart}_${savedir})" {
    linux /vmlinuz w_bootfrom=${iso_path} w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} net.ifnames=0
    initrd /initrd.gz
}

menuentry "${distname}-${revision} (RAM2 save on demand to ${bootlabel}_${savedir})" {
    linux /vmlinuz w_bootfrom=${iso_path} w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
    initrd /initrd.gz
}

menuentry "${distname}-${revision} (direct saves to ${bootlabel}_${savedir})" {
    linux /vmlinuz w_bootfrom=${iso_path} w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} net.ifnames=0
    initrd /initrd.gz
}

menuentry "Shutdown" {
	halt
}

menuentry "Reboot" {
	reboot
}

grub.cfg

Code: Select all

set distname=KLV-Spectr
set revision=RT
set savepart=Persistence
set savedir=Sessions
set bootlabel=Ventoy

insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc

loadfont /boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep

insmod efi_gop
insmod efi_uga

insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm

insmod ext2
insmod f2fs
insmod ntfs
insmod exfat

insmod loopback
insmod iso9660
insmod udf

background_image /boot/splash.png
set timeout=10

loadfont /boot/grub/font.pf2


color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black

# First five entries usefully work with Ventoy

menuentry "${distname}-${revision} (${bootlabel} RAM0 no persistence)" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=RAM0 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} RAM2 save on demand to ${savepart}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} direct saves to ${savepart}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} net.ifnames=0
 initrd /initrd.gz
}
  
menuentry "${distname}-${revision} (${bootlabel} RAM2 save on demand to ${bootlabel}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} direct saves to ${bootlabel}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} net.ifnames=0
 initrd /initrd.gz
}

menuentry "Shutdown" {
	halt
}

menuentry "Reboot" {
	reboot
}
User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

@wiak I replaced the KLV-Spectr-RT ISO with the correct one now.
https://rockedge.org/kernels/data/ISO/K ... Spectr/RT/

@Clarity Please download this version and test on Ventoy :ugeek:

geo_c
Posts: 2876
Joined: Fri Jul 31, 2020 3:37 am
Has thanked: 2197 times
Been thanked: 871 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by geo_c »

wiak wrote: Fri Oct 20, 2023 8:47 am

Rather I'd say try one of the KLA distros, which no-one seems to have found any fault with, or KLV-Airedale which has been out for a while. Only thing I'd worry about with KLV-Airedale choice is that it also tends to be getting released with RT kernel, which may not boot for some people if my machine is anything to go by. So maybe best start choice would be either KLA-OT2baseCE as produced by Sofiya, or KLA-XFCEbase, which has never given me any problems.

I'll tell you what I keep installed because it has always run extremely reliably and boots on everything is KLV-Airedale-SR2, which came with a standard type kernel, Void Linux kernel 6.3.12

I always maintain my KLV-Airedale-sr2 just in case I run into a machine that doesn't like the real time kernel (though I have had no problems with the RT kernel myself on 5 different machines,) and because I have set the SR2 up so well that it makes no sense to ever stop using it. It's just like F96 in that I will keep it around for a long time.

There are just a couple of manual tweaks to be done in SR2, like this simple command to start the firewall automatically on bootup: -ln -s /etc/sv/ufw /var/service

and actually that's all I have logged for manual tweaks. I don't think I even had to set the timezone manually, but that might need to be done also.

Anyway SR2 works very well. All my machines have 2 separate installs of KLV-Airedale, both SR-2 and RT.

To my knowledge, the available KLVs running RT kernels are Airedale, Spectr, Bspwm, and Awesome.

geo_c
Old School Hipster, and Such

User avatar
fredx181
Posts: 3037
Joined: Tue Dec 03, 2019 1:49 pm
Location: holland
Has thanked: 367 times
Been thanked: 1290 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by fredx181 »

geo_c wrote:

I always maintain my KLV-Airedale-sr2

@rockedge I think it would be good if you post topic about a new KL release that you mention on top the exact changes compared with older version(s).
(often not clear to me)

User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

KLV-Airedale-sr6 is using Void Linux kernel 6.5.7_1 and the 01firmware from 6.1.38-rt13 because it's compact. The Void Linux 6.5.7 01firmware I have available but is 220 M or more.

KLV-Spectr-beta3 ALSO available right now for download and is equipped with the Void Linux kernel 6.5.7_1 as well. The RT versions are more experimental.

Both are stable responsive and efficient OS's and use pipewire audio

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

rockedge wrote: Sat Oct 21, 2023 3:28 pm

@Clarity Please download this version and test on Ventoy :ugeek:

I've tested this latest: It traps in both Ventoy and SG2D.

I also downloaded SR6 and spectr vb3. All continue to trap on boot.

So far of all downloaed from last week, only XFCEpodman boots from each ISO file boot methods I've tested; namely QEMU, and bare-metal (Ventoy + SG2D)

User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

@Clarity I am not sure why these will not boot on Ventoy. They use the exact same loopback.cfg, menu.lst, grub.cfg code that is in KLV-Airedale-sr2 which is reported to boot in Ventoy. Only the set revision variable has a different value.

grub.cfg

Code: Select all

set distname=KLV-Airedale
set revision=sr6
set savepart=Persistence
set savedir=Sessions
set bootlabel=Ventoy

insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_dfly
insmod part_dvh
insmod part_gpt
insmod part_msdos
insmod part_plan
insmod part_sun
insmod part_sunpc

loadfont /boot/grub/font.pf2
set gfxmode=800x600
set gfxpayload=keep

insmod efi_gop
insmod efi_uga

insmod all_video
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
insmod jpeg
terminal_output gfxterm

insmod ext2
insmod f2fs
insmod ntfs
insmod exfat

insmod loopback
insmod iso9660
insmod udf

background_image /boot/splash.png
set timeout=10

loadfont /boot/grub/font.pf2


color_normal=cyan/black
#menu_color_highlight=black/light-gray
menu_color_highlight=yellow/red
menu_color_normal=light-gray/black

# First five entries usefully work with Ventoy

menuentry "${distname}-${revision} (${bootlabel} RAM0 no persistence)" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=RAM0 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} RAM2 save on demand to ${savepart}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} direct saves to ${savepart}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${savepart}=/${savedir}/${distname}-${revision} net.ifnames=0
 initrd /initrd.gz
}
  
menuentry "${distname}-${revision} (${bootlabel} RAM2 save on demand to ${bootlabel}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} w_changes1=RAM2 net.ifnames=0
 initrd /initrd.gz
}

menuentry "${distname}-${revision} (${bootlabel} direct saves to ${bootlabel}_${savedir})" {
 linux /vmlinuz w_bootfrom=/${distname}-${revision}.iso w_changes=LABEL=${bootlabel}=/${savedir}/${distname}-${revision} net.ifnames=0
 initrd /initrd.gz
}

menuentry "Shutdown" {
	halt
}

menuentry "Reboot" {
	reboot
}
User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

@Clarity I checked that all the files that worked on earlier versions are present in sr6. Repackaged the ISO so I hope it works or you can point out what the errors are or what's missing. KLV-Airedale-sr6

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

@rockedge
I'm right now downloading all of your most recent above indicated:

KLV-Spectr-RT.iso
KLV-Spectr-beta3.iso
KLV-Airedale-sr6.iso

and I'll double check their FR initrd version and try them on my Ventoy stick.

I expect all will be fine now and we are seeing the trees from the wood, so don't worry about it. Anything wrong will likely be minor and I'll let you know if any further issues. Clarity seems to suggest still not working. We will see.

Anyway it is a good wake up call. Though the current FRmake_initrd.sh is not causing the issue with wrong version of FR initrd being downloaded I should edit that script to be downloading from gitlab firstrib rather than my owncloud occasional backing store. There may be other scripts I don't know about that continue to download from owncloud since that used to be main place I used, but you'll remember I had a few temporary moments when owncloud wasn't working for me (usually with iso upload issues but once or two you were making minor fixes and I couldn't access it); at that stage I was in process of tidying up gitlab firstrib site. Moments like these could result in out-of-sync type issues, though I haven't been able to identify that. So useful wake up call in that I will update that FRmake_initrd.sh script anyway despite it not being a current culprit.

Okay, download of these isos is now done and I will tranfer them to my Ventoy stick as a quick verification more generally and will report back once I've done all that. Any remaining issues would likely be small now and Ventoy per se, just a less-used-by-most facility anyway; nothing to worry about - almost all resolved now I'm sure. One last thing I would suggest is that we always indicate versionrevision in any iso name - so that RT one might be better named with end of -RTxy where x is most recent version and y most recent release (for example -RT001rc2). We certainly need to be careful getting same into grub.cfg, menu.lst and loopback.cfg so: release part of these would then be RT001rc2 (i.e. in the grub configs: set revision=RT001rc2, but RT at the moment is working fine anyway). But okay for now: I'll just check these isos in Ventoy and report back as I said.

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

wiak wrote: Sun Oct 22, 2023 1:02 am

@rockedge
...
KLV-Spectr-RT.iso
KLV-Spectr-beta3.iso
KLV-Airedale-sr6.iso

The newly released KLV-Swayland iso ( KLV_SwayBASE-002rc3.iso) has also been tested as booting and running well from Ventoy. Comes with Wayland Sway, labwc, pipewire, wofi, Waybar, Firefox and lots more.
Mod(Windows key)+d for wofi application launcher; Mod+Enter for quick sakura terminal; Mod+Shift+b for browser firefox; Mod+Shift+s for logout gui; Mod+Shift+q for close a window; Mod+mouse-right-button-drag to resize windows (tiled or otherwise); Mod+f for fullscreen window; Escape key to Cancel most things...
Temporary download here: viewtopic.php?p=100390#p100390

@rockedge
I have now downloaded all of the above and checked their FR initrd version; all are fine and latest.

I also put them all onto my Ventoy /BOOTISOS folder and tested. All booted fine for me in Ventoy.

If Clarity is still having problems using these with Ventoy then a different problem and not a fault of the isos themselves now.

For Clarity case could be firmware/hardware related, but that is why normal frugal installs are more flexible really - since up to the user to swap to different kernel/modules/firmware combination in such cases really. Anyway, it is not Ventoy issue - that is now working fine thanks for all of above.

NOTE: KLV-Spectr-RT does not boot on my newest laptop (in Ventoy or normal frugal install), but that is just firmware-missing issue on my newer machine so nothing to worry about.

I haven't tested Qemu (no time, just going out), but I am not expert on using that anyway, and I did check the needed iso/boot/grub/menu.lst files for each of above, which looks fine so I don't expect any issue there either.

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

Sorry for the delay. Visiting company.

Here's my scenario - I started fresh:

The bootable USBs

  • I got out 4 32GB sticks from the pile I have.

  • I downloaded Ventoy v1.0.96 script from their site

  • Ventoy allows the user to create any of 4 different boot USB sticks for the varied PC types.

I created a single USB for each PC types for testing, as follows.

.

MSDOS

GPT

No Secureboot

USB #1

USB #3

Secureboot

USB #2

USB #4

The USBs have the same identical internal layout from Ventoy.

  • Partition #1 is labeled Ventoy

  • its filesystem format for the partition from Ventoy is exFAT

  • and I created a folder on the partition named BOOTISOS.

The following shows the partition contents for each USB stick:

My Ventoy exFAT partition #1.jpg
My Ventoy exFAT partition #1.jpg (30.99 KiB) Viewed 3745 times

I have 2 Intel PCs that I am using for testing: an i7 NUC connected to TV and a desktop connected to a VGA.

My ISO file's checksum md5's match what is published for each downloaded ISO file on the BOOTISOS folder.

Any one of these sticks allows booting attempts of each distro on the stick that is found by Ventoy and presented. I have found no difference in behavior of EACH USB stick. Thus KL boot failures are identical no mater which stick is booted.

I always attempt a boot of any ISO from the list that Ventoy presents. If any ISO fails in its launch from Ventoy, I

  1. reboot

  2. launch SG2D ISO from the Ventoy list
    HIt the Enter key on SG2D's 1st screen

  3. when I get SG2D's ISOs found list, I scroll to the offending ISO used from Ventoy's list and allow that ISO file to be launched.

I cannot deduce why the KLs are failing when launched from Ventoy's menu and SG2D's menu; while the WoofCE PUPs are, now, booting from both Ventoy's menu as well as SG2D's menu.

In all tests, I make NO changes to any boot stanzas allowing each distro to boot its top line stanza on its own.

If anyone can spot something overlooked here, please alert me. This info published in the thread is identical to the approaches used since KL's ISO booting became available.

There is only 1 difference between the NUC and the desktop PC: NUC has no internal drive and NO Persistence partition on any connected storage; while the desktop PC has an internal drive with a Linux partition labeled "Persistence" containing folder Sessions.

And, for all past uses, I merely download the ISO to the BOOTISOS folder and boot the USB to select the downloaded ISO.

Can you spot anything that I could be not doing or doing such that the ONLY KL that boots is KL's XFCEpodman I would be grateful to know?

Time permitting, I will create a video of a USB booting failures for review.

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

Clarity wrote: Sun Oct 22, 2023 6:16 am

Can you spot anything that I could be not doing or doing such that the ONLY KL that boots is KL's XFCEpodman I would be grateful to know?

Time permitting, I will create a video of a USB booting failures for review.

I have always said thus far that we expect Linux format for all KL distro installation; in the past you were using a Linux format Clarity (per the Ventoy image you used to provide on the forum), so you should have indicated you were no longer reformatting. My own Ventoy disk has that Ventoy partition with /BOOTISOS in it reformated as Linux ext format (in my case I think its simply ext2, but doesn't matter - it isn't exFAT).

It may be that KLA-XFCEpodman included exFAT support; I would have to check that.

Longer term we will look into exFAT support since that isn't likely to be difficult to include more generally.

Of course the issue may be something else, but I doubt it.

Whether KL/FR baulks on putting iso in exFAT I actually don't know since I haven't tried it, but I expect it may well crash out finding that on trying to boot (except for that KLA podman release which, if it has exFAT support will be able to mount the partition the isos are being stored in).

Anyway, yes, send in your boot failure screen - maybe that will show error as it happens.

Note that it is usual for temporary error on trying to mount partition when using Ventoy - that's just a warning since the FR initrd keeps trying and generally managed to mount assuming has the appropriate format support in the distro.

EDIT: So I booted KLA-XFCEpodman and sure enough exfatprogs is installed, so that's probably why it worked in Ventoy on exFAT partition:

Code: Select all

└># pacman -Ss exFAT
community/exfat-utils 1.4.0-1
    Utilities for exFAT file system
community/exfatprogs 1.2.0-1 [installed]
    exFAT filesystem userspace utilities for the Linux Kernel exfat driver

EDIT2: NOTE that I would still recommend reformatting Ventoy partition to Linux format since that also allows persistence folder to work back to the ventoy usb stick (via RAM2 mode); far from everybody would create an external (say on fast hard drive) and main thing needed is simple small persistence save of the likes of wifi connection info - can't do that without an image savefile on exFAT format as far as I'd understand it, and that is a complexity beginners would never be able to handle... easier to provide special Ventoy image that uses Linux format in practice. Pity Ventoy uses exFAT, but I guess they are more interested in supporting mass Windows audience? Nevertheless, exfatprogs seems to be a pretty small install so I recommend we include that in KL builds. I haven't actually tried RAM2 save on demand persistence with Ventoy using exFAT, but I'd be really surprised if that worked (more likely only first boot option RAM0 for no persistence works, Clarity?).

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

@Clarity
So I had a more detailed look. I downloaded the new Ventory tar.gz and ran the script and made a new Ventoy usb stick with its first partition exFAT.

In fact all of the following KL distros of my own that I tried booted successfully from the /BOOTISOS folder in RAM0 (no persistence) mode:

KLA-XFCEpodman-1.1.iso
KLV_SwayBASE-002rc3.iso
KLU-jam-XFCEbase-1.1.iso

The difference was that if I also tried to boot them using persistence to the Ventoy Sessions folder (last menu choice) the last two failed with kernel panic, whereas KLA podman still booted (but didn't successfully save persistence session thereafter).

Neither my Sway nor my KLU-jam distro includes exFAT support and thus when trying to boot in persistence mode they crash because they are unable to mount the Ventoy partition.

As I suspected, because KLA podman does include exFAT support it was able to write a Sessions folder automatically and didn't crash out trying. However, the reason persistence didn't work is that by default FirstRIb distros use save folder and that can only work on Linux formatted partitions. What happened was that Ventoy/Sessiond/KLA-XFCEpodman-1.1/upper_changes folder was auto-created, but the actual rsync save couldn't work to exFAT (because the initrd detects it is not Linux format and thus wouldn't work with symlinks).

However, save persistence can be 'made' to work by simply creating a savefile with extension .ucimg in that now created Ventoy/Sessiond/KLA-XFCEpodman-1.1/ folder so on next boot the FR initrd notices the existence of a .ucimg savefile and uses it... But, yes, that .ucimg savefile needs to be created manually first, which is a much more difficult job than simply using a normal frugal installation (though as I've earlier pointed out a normal frugal install can in fact be made on a Ventoy disk since Ventoy included simple provision for that - but not as simple as simply dropping in an iso of course).

Nevertheless, you can, as you know use save folder persistence to any Linux formatted partition elsewhere if it has LABEL Persistence - the second and third grub menu choices Ventoy presents.

There is no easy way to get persistence back to the Ventoy usb stick in practice; you need exFAT support in the distro AND you need a .ucimg savefile manually created in the relevant Sessions folder subdirectory for the FirstRib-based distro you are trying to boot. Unfortunately, it would be a great deal of effort modifying the FR initrd further such than a .ucimg file was auto-created (Puppy does do that sort of thing though because it started out using savefiles by default). Frankly, I do not recommend savefiles anyway; so best is to save persistence to a Linux formatted partition elsewhere that has LABEL "Persistence" - that just works and is automatic and probably will work for all the three distros mentioned above despite two of them not including exFAT support - I haven't yet tried that theory, but so far all I expected has turned out to be the case for Ventoy exFAT. If a person really wants a more versatile Ventoy usb stick I would still recommend them to re-format that first partition as Linux format.

My own view, overall, is: yes, I like Ventoy for quick iso booting tests that don't require any effort from me, BUT, I would never bother with an exFAT Ventoy stick and wish Ventoy themselves would provide script for Linux format use since the problem is then actually solved better, but I understand they really targetting the MSwindows market for their product and hence using exFAT since Windows can write isos to that.

EDIT: Forgot to say that I think the reason some other KL distros didn't boot in RAM0 mode on that exFAT Ventoy was more likely to be firmware related than anything else, but I haven't had time to look into that further; certainly the ones I tried earlier that booted fine on my Ventoy Linux formatted partition failed for exFAT case yet KLV-Swayland did boot in RAM0 no persistence mode despite not having exfatprogs installed in their main root filesystem.
EDIT2: Tested also now using KLV_SwayBASE with second Linux formatted usb stick labelled Persistence. Save folder persistence then worked as expected with auto-creation of a Sessions folder inside that second stick. More tests are needed for other KL distros to be sure what their issue is, but they were certainly booting fine previously from Linux-formatted Ventoy usb-stick (the one I'm surprised about it that KLV-SwayBASE is booting (in RAM0 no persistence mode) despite I 'think' not having exFAT support, which I'll have to double-check really.
EDIT3: Ah, I think it is because the kernel used in KLV-SwayBASE (which is from Vanilla Dpup) has exFAT driver support and probably that isn't in the kernels rockedge is using in some other KL distros - probably best to check that and include it I'd think. If using official Void Linux kernels it may be that is a module that needs loaded by the FR initrd so that would need a small tweak for that to work, but easier with huge kernel type.
EDIT4: For my own use, which is really my only interest in Ventoy, I immediately reformat the exFAT first partition with Linux format (and e2label it Ventoy). Of course Windows can't read that usb stick, but I don't myself have that need anyway. The only way to properly keep exFAT would be to make sure distro has exFAT kernel driver AND also a savefile created, and whist Puppy Linux does auto-create a savefile as its legacy method, KL/FirstRib does not auto-create the required .ucimg savefile; could it, yes of course, but at increased FR initrd complexity for what I see as very limited useful purpose, sorry - but someone interested to do so can easily modify w_init plugin to do exactly that during first save. Alternatively use a Linux formatted partition with LABEL "Persistence" elsewhere on the system and that is supported out-of-the-box in most KL/FirstRib isos (a Sessions folder is auto-created on that during use with separate subdirectory for each distro release).
EDIT5: By the way, on my new Ventoy usb stick, but now with first partition back to Linux reformatted, latest KLV-Airedale-sr6 is booting fine and save persistence also working straight back to the Ventoy stick as I said. My only recommendation would be that we do include exFAT driver support in the future builds, but I have to check FR initrd and probably slightly modify it to allow for that when non-hugekernel being used (huge kernel should include exFAT if possible). I don't intend providing auto-savefile creation at all, so best way for exFAT Ventoy user to have persistence is to have that external Linux formatted Persistence labelled partition. Note that I find that persistence is very slow on first boot maybe because using old usb 2.0 stick, but seems okay on reboot thereafter EDIT6: No, still painfully slow... (not sure why - maybe needed a lot of browser profile info written to it first time round). Definitely all users of Linux would be better off using Linux format Ventoy partition anyway (since will most always work whereas no guarantee all Linux distros will have exFAT support...).

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

@wiak I have a full real time kernel 6.5.2-rt8 with both AUFS and Overlayfs built in. I checked the kernel configuration for 6.5.2-rt8:

Code: Select all

# DOS/FAT/EXFAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_FAT_DEFAULT_UTF8 is not set
CONFIG_EXFAT_FS=y
CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_NTFS3_FS=y
# CONFIG_NTFS3_64BIT_CLUSTER is not set
CONFIG_NTFS3_LZX_XPRESS=y
CONFIG_NTFS3_FS_POSIX_ACL=y
# end of DOS/FAT/EXFAT/NT Filesystems

Code: Select all

# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_PROC_CHILDREN=y
CONFIG_PROC_PID_ARCH_STATUS=y
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_TMPFS_XATTR=y
# CONFIG_TMPFS_INODE64 is not set
# CONFIG_HUGETLBFS is not set
CONFIG_MEMFD_CREATE=y
CONFIG_ARCH_HAS_GIGANTIC_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_EFIVAR_FS=m
# end of Pseudo filesystems

CONFIG_MISC_FILESYSTEMS=y
CONFIG_ORANGEFS_FS=m
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_ECRYPT_FS=m
# CONFIG_ECRYPT_FS_MESSAGING is not set
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
# CONFIG_EFS_FS is not set
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_FS_XATTR is not set
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
# CONFIG_UBIFS_FS is not set
CONFIG_CRAMFS=m
CONFIG_CRAMFS_BLOCKDEV=y
CONFIG_CRAMFS_MTD=y
CONFIG_SQUASHFS=y
# CONFIG_SQUASHFS_FILE_CACHE is not set
CONFIG_SQUASHFS_FILE_DIRECT=y
CONFIG_SQUASHFS_DECOMP_SINGLE=y
# CONFIG_SQUASHFS_CHOICE_DECOMP_BY_MOUNT is not set
CONFIG_SQUASHFS_COMPILE_DECOMP_SINGLE=y
# CONFIG_SQUASHFS_COMPILE_DECOMP_MULTI is not set
# CONFIG_SQUASHFS_COMPILE_DECOMP_MULTI_PERCPU is not set
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZ4=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
CONFIG_SQUASHFS_ZSTD=y
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=y
CONFIG_OMFS_FS=m
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_PSTORE=y
CONFIG_PSTORE_DEFAULT_KMSG_BYTES=10240
CONFIG_PSTORE_DEFLATE_COMPRESS=y
CONFIG_PSTORE_LZO_COMPRESS=y
CONFIG_PSTORE_LZ4_COMPRESS=y
CONFIG_PSTORE_LZ4HC_COMPRESS=y
# CONFIG_PSTORE_842_COMPRESS is not set
CONFIG_PSTORE_ZSTD_COMPRESS=y
CONFIG_PSTORE_COMPRESS=y
CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT=y
# CONFIG_PSTORE_LZO_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_LZ4_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_LZ4HC_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_ZSTD_COMPRESS_DEFAULT is not set
CONFIG_PSTORE_COMPRESS_DEFAULT="deflate"
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_PMSG is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_PSTORE_BLK is not set
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
# CONFIG_EROFS_FS is not set
# CONFIG_VBOXSF_FS is not set
CONFIG_AUFS_FS=y
CONFIG_AUFS_BRANCH_MAX_127=y
# CONFIG_AUFS_BRANCH_MAX_511 is not set
# CONFIG_AUFS_BRANCH_MAX_1023 is not set
# CONFIG_AUFS_BRANCH_MAX_32767 is not set
CONFIG_AUFS_SBILIST=y
CONFIG_AUFS_HNOTIFY=y
CONFIG_AUFS_HFSNOTIFY=y
CONFIG_AUFS_EXPORT=y
CONFIG_AUFS_INO_T_64=y
CONFIG_AUFS_XATTR=y
# CONFIG_AUFS_FHSM is not set
# CONFIG_AUFS_RDU is not set
# CONFIG_AUFS_DIRREN is not set
# CONFIG_AUFS_SHWH is not set
# CONFIG_AUFS_BR_RAMFS is not set
# CONFIG_AUFS_BR_FUSE is not set
# CONFIG_AUFS_BR_HFSPLUS is not set
CONFIG_AUFS_BDEV_LOOP=y
# CONFIG_AUFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
CONFIG_NFSD=y
# CONFIG_NFSD_V2 is not set
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_KRB5_CRYPTOSYSTEM=y
# CONFIG_RPCSEC_GSS_KRB5_ENCTYPES_DES is not set
CONFIG_RPCSEC_GSS_KRB5_ENCTYPES_AES_SHA1=y
# CONFIG_RPCSEC_GSS_KRB5_ENCTYPES_AES_SHA2 is not set
# CONFIG_SUNRPC_DEBUG is not set
# CONFIG_CEPH_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
# CONFIG_CIFS_UPCALL is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG is not set
# CONFIG_CIFS_DFS_UPCALL is not set
# CONFIG_CIFS_SWN_UPCALL is not set
# CONFIG_SMB_SERVER is not set
CONFIG_SMBFS=y
CONFIG_CODA_FS=m
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
CONFIG_NLS_CODEPAGE_863=m
# CONFIG_NLS_CODEPAGE_864 is not set
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
CONFIG_NLS_CODEPAGE_932=m
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
CONFIG_NLS_UTF8=y
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
# CONFIG_UNICODE is not set
CONFIG_IO_WQ=y
# end of File systems

This is the relevant configuration in 6.1.38-rt13 which indicates that the exFat support is supplied by module and not built in as in 6.5.2-rt8

Code: Select all

# DOS/FAT/EXFAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_FAT_DEFAULT_UTF8 is not set
CONFIG_EXFAT_FS=m
CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_NTFS3_FS=y
# CONFIG_NTFS3_64BIT_CLUSTER is not set
# CONFIG_NTFS3_LZX_XPRESS is not set
# CONFIG_NTFS3_FS_POSIX_ACL is not set
# end of DOS/FAT/EXFAT/NT Filesystems
User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

rockedge wrote: Sun Oct 22, 2023 4:55 pm

This is the relevant configuration in 6.1.38-rt13 which indicates that the exFat support is supplied by module and not built in as in 6.5.2-rt8

Yes, any distro using any kernel build without exFAT built in wouldn't be able to boot from Ventoy exFAT store. Well..., at least not without including that module inside the FR initrd and loading it during initrd loading, which adds complexity (not huge-enough kernel in other words). Probably best to always include exFAT in hugekernel builds - does it increase kernel size much I wonder?

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

User avatar
rockedge
Site Admin
Posts: 6518
Joined: Mon Dec 02, 2019 1:38 am
Location: Connecticut,U.S.A.
Has thanked: 2725 times
Been thanked: 2611 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by rockedge »

wiak wrote:

Probably best to always include exFAT in hugekernel builds - does it increase kernel size much I wonder?

I think it would be a good idea to include it. It should be an acceptable minimal increase in size. I forgot the reason I started to include exFAT in the kernels I compiled after 6.1.38-rt13

Tomorrow I can attempt to rebuild 6.1.38-rt13 or try out 6.5.2-rt8 that has the exFat support built in already.

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

Good Morning. A song that I play all the time is "Its A Beautiful Morning" by the Young Rascal. You developers ARE this forum's 'YOung Rascals'.

@rockedge I believe you may have started because for many recent years, pre-formatted storage (USBs) are shipped as ExFAT. Thus these could be immediately used by MS and MACs but not by forum distros...until some started to include exFAT of recent in the running OSes. Also Samsung preformatted storage was shipping with F2FS and, again, MS and MACs were capable and thanks to Barry, IIRC that was added in his and other forum OSes as well.

In my past, I had always modified Ventoy's ISO partition (#1) before use because of my fondness for using Linux formats for Linux OSes. It was my personal way to ensure that in booting to desktops that the running Linux OSes would recognize them.

It wasn't until I tested use of OOTB Ventoy creates, that I discovered this behavior.

With the upcoming efforts in adding exFAT for boot discovery, this issue will disappear into the past.

Today, I will take my 4 exFAT Ventoy sticks and I will create other sticks by modifying the partition #1 filesystems to other familiar Linux/MS/MAC filesystems to insure the booting process goes expected.

@wiak THANKS for your efforts to insure KL's will match ALL known OSes to have this capability in boot discovery!

I will provide any updates to testing results as I find them. This will be done to report successful use of KLs in booting no matter the current industry standard OOTB filesystems that manufacturers are shipping for purchase by customers to use for storage. I will test these USB sticks on my Intel as well as my AMD rigs for KLs and other forum distros.

All of my rigs are very old with the newest 2 being that AIO AMD and NUC of 2016. Other test rigs currently range from 2008 to 2013

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

This may not be relevant, but in this published archve from Barry where he describes "The intial ramdisk" it

Code: Select all

shows:#!/bin/ash
#(c) Copyright 2006 Barry Kauler, www.puppylinux.com
PATH="/bin:/sbin"
KERNVER="`uname -r`"

#Boot param PMEDIA= usbflash|usbhd|usbcd|ideflash|idehd|idecd|idezip|satahd|scsihd|scsicd
#unionfs layers:            RW            RO1             RO2              PUPMODE
#PUPSFS only:               tmpfs                         pup_xxx.sfs      5
#PDEV1 has puppy:           tmpfs         PDEV1*                           3
#PDEV1 has puppy, no tmpfs: PDEV1                                          2
#PDEV1, PUPSFS:             tmpfs         PDEV1*          pup_xxx.sfs      7
#unionfs layers:            RW            RO1             RO2              PUPMODE
#found PUPSFS, PUPSAVE:     tmpfs         pup_save.3fs*   pup_xxx.sfs      13
#PUPSAVE(multi), PUPSFS:    tmpfs         folders(tmpfs2) pup_xxx.sfs      13+64 = 77
#PUPSAVE, PUPSFS, no tmpfs: pup_save.3fs                  pup_xxx.sfs      12
 
fsfunc() #f.s. type param passed in
{
 FSTYPE="$1"
 [ "$FSTYPE" = "Ext2" ] && FSTYPE="ext2"
 [ "$FSTYPE" = "ReiserFS" ] && FSTYPE="reiserfs"
 [ "$FSTYPE" = "Ext3" ] && FSTYPE="ext3"
 [ "$FSTYPE" = "FAT16" ] && FSTYPE="vfat"
 [ "$FSTYPE" = "FAT32" ] && FSTYPE="vfat"
 [ "$FSTYPE" = "NTFS" ] && FSTYPE="ntfs"
 [ "$FSTYPE" = "ISO9660" ] && FSTYPE="iso9660"
}

I am sure this has been updated to accomodate exFat, Ext4, and F2FS

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

I don't know anything about it really but I've heard grub2 can't boot from f2fs if f2fs using extra_attr, which are needed for some nice features so not sure we should include that for boot support. I'll look into it more including to see if most hugekernels including driver for that.

It's a different matter being able to access f2fs after boot.

However, I note that huge kernels built for Puppy Linux include inbuilt driver for f2fs so any KL using these would boot if boot loader does support f2fs

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

wiak wrote: Mon Oct 23, 2023 9:34 pm

... f2fs ...

Ventoy does NOT list ISO files on its F2FS partition.

SG2D does with no issues as the ISO files it finds on its FSFS partition, will boot.

User avatar
wiak
Posts: 4074
Joined: Tue Dec 03, 2019 6:10 am
Location: Packing - big job
Has thanked: 65 times
Been thanked: 1204 times
Contact:

Re: Unable to install KL to Lenovo Ideapad laptop

Post by wiak »

Clarity wrote: Wed Oct 25, 2023 3:16 am
wiak wrote: Mon Oct 23, 2023 9:34 pm

... f2fs ...

Ventoy does NOT list ISO files on its F2FS partition.

SG2D does with no issues as the ISO files it finds on its FSFS partition, will boot.

It doesn't matter, Clarity, the last time any work done on SGD2 github was Dec 2022. I consider Ventoy its successor, and even if anyone else thinks differently nevertheless I am not supporting both and have chosen to support Ventoy only.

Of course others can use SGD2 for whatever they wish; good luck to them, but I will not be responding to any posts about SGD2 success or failure. Frankly, there are more important development matters to proceed with and maintain. Even Ventoy is secondary (actually lower than that) in my own list of priorities, but since I do occasionally use it I am likely to keep it working on my own KL releases - but no such guarantee on the behalf of others who are free to maintain their own work to the extent they want.

Quick and short reports on Ventoy with new releases are therefore welcomed by me, but SGD2 should not be included since that wastes time. What you use yourself is up to yourself, but really no interest in SGD2 at all here whether it can be used to successfully boot distros Ventoy can't, or not - rather I implore users to prefer normal frugal install first, and only if they can't manage that to try Ventoy; beyond that is not something I want to use my own dev time on at all. Straight iso booting via loopback ability of GRUB2 is a simple alternative of course (though again, checking save persistence works is vital).

Qemu is a different matter since that is run inside a host distro, and is definitely supported, so short reports on that are always welcome.

In all cases, I am only interested really to know if save persistence works. Simply being able to boot to the desktop without save persistence is all but irrelevant to me so hopefully my comments will help to keep feedback reports focussed, relevant and thus short and to the point; with as little repeated information as possible since that becomes exhausting and distracting, which I'm sure we all agree.

Anyway, I don't consider it up to me what other people do or don't or report or don't report or develop or not develop, but I'm just letting you know what I'll read and respond to, or not; efficiency is important and so focus and good organisation is important even for hobby distros such as this one. But whatever... each to their own is the only forum rule really. Use and enjoy whatever you like that is provided, create what you will for others - that's open source - there is no other commitment given or expected from anyone.

https://www.tinylinux.info/
DOWNLOAD wd_multi for hundreds of 'distros' at your fingertips: viewtopic.php?p=99154#p99154
Αξίζει να μεταφραστεί;

Clarity
Posts: 3807
Joined: Fri Jul 24, 2020 10:59 pm
Has thanked: 1609 times
Been thanked: 519 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by Clarity »

I am only reporting what I have found working. I am not seeking support for any of the ISO file boot launchers.

My last few days has been, when time permits, reviewing filesystems along with these launchers to have some better understanding of their OOTB filesystems behaviors of the partitions the ISO files reside. And to understand what the distros are seeing when the distro sets up on desktop when successfully booted.

I am hopeful to produce something intelligent and useful much beyond what has been done with the 3 boot-launchers on the forum.

Your work and the work of the others in the KL arena has been useful to the extreme leading to better understandings we have in QEMU, AND these Boot Launchers since 2019. Particularly in booting to desktop directly from the ISO file, quickly after download.

I feel we are very close to having enough information that any user/member can take the findings that is being documented and run with a comfort level that they dont need our assistance to get up and going, over and over in their future, due to work and study being presented.

"I believe I can see the end of the tunnel and I think there is light shining there." :idea:

AQUAR
Posts: 46
Joined: Fri Jun 25, 2021 12:09 pm
Has thanked: 26 times
Been thanked: 10 times

Re: Unable to install KL to Lenovo Ideapad laptop

Post by AQUAR »

I empathize with Gnimmelf, as I am a nooby myself and have a hard time coming to grips with new ways of doing things.
For those familiar with "linux things" there is often a lack of recognition that it is actually much harder than it looks to those that are new to such things.
I used to create Markow RMA models for complex systems - easy for me but a hell of a hard time to explain the knowledge and the process needed.

I wanted to try KLV-Airedale myself to see if the much later kernel would solve a screen resolution issue with a Nvidia Gt 103 graphics card.
Only to find out that the normal way I install a puppy onto a USB drive (using RUFUS and a fat32 formatted USB stick) doesn't work because of the sophisticated stanza approach to boot it.
Rather than try to understand all just to see if the resolution problem is still present (it is!) I just used the initrd from fossapup and renamed the various files accordingly to boot this version.

Seems to have some familiar microsoft windows feel to it. But alas very low screen resolution with the VESA driver in play. Ahwell
Interestingly from the dmesg log, nouveau probe fails differently than before (error 2 instead of error 38) something to look into.

Post Reply

Return to “How-To”