Please revise the installer to add vmd to modules

General system
61
1 Like
62

just build a test ISO with vmd enabled… :wink:

2 Likes
63

My question is why this isn’t dealt with by the kernel?

Always a valid option.

1 Like
64

?

65

Hmm… this implies it should be loaded when the device is detected - does it need to be compiled-in the kernel to be loaded at boot time?

If so, it’s probably worth a “feature request” to the Arch kernel maintainers… :thinking:

66

it seems it needs to be loaded manually to work:

m  =  loadable module (can install and uninstall as you wish)
67

This should be on a bit safer side:

sed -i 's|^\([ ]*modules = \)\[\]$|\1["vmd"]|' $_reponame/src/modules/initcpiocfg/main.py

EDIT: already added this to calamares_current/PKGBUILD.

EDIT2: a related fix should be made to run_before_squashfs.sh?

# get default mkinitcpio.conf (possible patching it here)
wget https://raw.githubusercontent.com/archlinux/mkinitcpio/master/mkinitcpio.conf
patch -u mkinitcpio.conf -i /root/mkinitcpio.patch
sed -i 's/^MODULES=()$/MODULES=(vmd)/' mkinitcpio.conf  # <=== this
68

not working because calamares initcpiocfg module is overwriting the lines with its own defaults.
So I needed to change that … and in the real world… it would be the ideal solution to build the kernel with the module loaded automatically…
But for the time being I can patch calamares to do load module per default, and also set mkinitcpio.conf to use ()

2021-10-24_02-34
2021-10-24_02-341922×1077 250 KB

1 Like
69

I would like to get users with such hardware!

P.M. me or @ricklinux for testing this implementation if you have time and space to help us here :vulcan_salute:

70

spoiler alert – IT’S FIXED!!

I just installed the D3V iso and first boot, no problem. Only cleanup might be needed is it picked up about 9-10 entries for POP OS on ‘keep’ for efi/boot partition, I full wiped and created part table 2 days ago so it’s impossible it’s picking up OLD installs, right?? https://imgur.com/a/CBmXYjE

GREAT WORK ON THIS FELLAS!!!

71

I am not sure what that is a picture of but it is probably EFI entries. Those are not stored on the disk. If you do a lot of installs you need to clean up your EFI entries once in a while. You can do this with efibootmgr

1 Like
72

That’s your personal “codename” ? :grinning: for the dev-test iso with vmd enabled?

73

Here is the log from @d3viant6 for the vmd test ISO in case you didn’t get it properly.

https://clbin.com/srV6W

74

So ISO works for this device?

75

As far as i know he installed it and hopefully the log shows something if it’s the correct log.

76

There is this error:

11:44:00 [2]: void LoaderQueue::dataArrived()
    WARNING: unable to fetch netinstall package lists.
    ..  Netinstall reply error:  QNetworkReply::ContentNotFoundError
    ..  Request for url:  "https://gitlab.com/endeavouros-filemirror/EndeavourOS-calamares/-/raw/main/netinstall.yaml"  failed with:  "Error transferring https://gitlab.com/endeavouros-filemirror/EndeavourOS-calamares/-/raw/main/netinstall.yaml - server replied: Not Found"

So netinstall.yaml file was not found under
https://gitlab.com/endeavouros-filemirror/EndeavourOS-calamares

Should be in
https://gitlab.com/endeavouros-filemirror/files/EndeavourOS-calamares

77

yes a typo in the netinstall module… but no error as it will take the fallback from filesystem on ISO.
and fixed already:
https://github.com/endeavouros-team/EndeavourOS-calamares/blob/1ad4b2ed1c0707a7694d35237d37f3a01bc6106d/calamares/modules/netinstall.conf#L9

https://github.com/endeavouros-team/EndeavourOS-calamares/commit/b3090e5fb546cc9642e2d3d25d772a9afaea2b34

1 Like
78

Otherwise the log looks OK.

79

interesting part is if system boots into installed system … :grinning:

1 Like
80

That’s what he said.

1 Like