1:57 p.m.
On 28/06/2020 15:30, Max Rees wrote:
On Sun Jun 28 07:52 PM, Fungi4All wrote:
> https://forum.obarun.org/viewtopic.php?pid=6152#p6152
>
> I have tried to help someone on a forum of another distro how to
> install Adelie but he keeps having problems. He tried to subscribe
> here but for three days he is getting an automated response that his
> messages are awaiting moderation. Could a moderator for the list take
> a look at held messages? Thanks.
I've notified the people who are able to look at the queue; hopefully
those messages can be released soon. To fix this for the future I think
we will try to have more people able to look at the queue.
We've added more people who are able to process the queues, so hopefully
this won't happen again in the future.
It sounds like they were using the experimental Horizon ISO, which
has a
few known defects in the various versions. From what I understand, EFI
was not working in the 20200618 version because of a typo in what
filesystem type the EFI system partition was supposed to be, and the
20200623 version (or earlier) may have issues on some BIOS setups.
Your understanding is correct; I haven't yet had a chance to debug the
BIOS issue.
For firmware, Adélie doesn't ship any in the official repos, but
APK
Fission does. We're hoping that future ISOs we ship will include
firmware from APK Fission with a clear user choice as to whether it's
used or not. It sounds like when they tried to manually install firmware
they put it in the wrong location - it needs to be /lib/firmware, not
/usr/lib/firmware.
I have not yet read the link but yes, that is definitely wrong. I
believe that the 20200623 ISO uploaded to distfiles is firmware-enabled,
but I'm not fully sure.
For VirtualBox, support is still very much a work-in-progress,
mainly
because the developers don't really have machines that can run it handy.
I think the latest development here is that the vboxvideo X driver isn't
being loaded automatically, so it has to be manually configured. I think
this is what causes the "freezing" effect on boot. If this is configured
then BIOS boot in VB should work. We will have to think of some way to
make this happen automatically.
The latest development is that the VirtualBox DRM driver will not work
with VBox 6.x for console. You need to modprobe.blacklist=vmwgfx to
make it boot. It will work fine for X11, but you'd have to either start
X blind or add sddm to the default runlevel.
However, for X11 to work properly, you need to manually create an
/etc/X11/xorg.conf.d/10-modules.conf with at least
Section "Module"
Load "vbe"
Load "vgahw"
Load "shadow"
Load "shadowfb"
EndSection
in it.
I'm not sure why Horizon was not able to re-use the empty
partition; I
will try to look into this when I have time.
"failed to get the canonical path of /boot/grub" sounds like they either
did not have one of /boot, /dev, /proc, and /sys mounted inside their
chroot, or some combination thereof.
It is great to get feedback on these experimental ISOs, but when users
get frustrated they have to remember that they are experimental. The
official RC2 images will be more stable.
That's correct, and that's why these aren't RC2 images, and that's why
they have "EXPERIMENTAL" in all caps as the first word of the image ;)
I realise that many people are impatient with how long it has taken us
to get this far. We are impatient as well. However, quality releases
take time.
Best,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org