helloSystem / ISO

helloSystem Live and installation ISO
https://github.com/helloSystem/
BSD 3-Clause "New" or "Revised" License
806 stars 58 forks source link

Issues with FreeBSD 13 based builds #198

Closed probonopd closed 2 years ago

probonopd commented 3 years ago

We started doing FreeBSD 13 based builds again, mainly to see what is and is not yet working for us in FreeBSD 13.

This ticket is here to collect all such issues. Once all are solved, we may start consider using FreeBSD 13 as the base for the next release.

Positive

Showstoppers

Issues

TargetGalaxy commented 3 years ago

"How can we prevent the FreeBSD 13 bootloader from changing the screen resolution? On an UEFI based system (Acer Revo RL85) where the resolution was correct in FreeBSD 12, the FreeBSD 13 bootloader seemingly tries to be smart and change the resuolution with the effect that it is no longer the native resolution of the screen"

You can add exec="mode 0" to /boot/loader.conf

grahamperrin commented 3 years ago

Showstoppers?

No sound on HDMI on Nvidia GPU …

Which driver?

Which release at the time?

Have you tested with the more recent release in ports?

There are also the releases from NVIDIA, which can be built and installed without reference to FreeBSD ports.

… a different font on the non-graphical console. How can we get back the orginal …

Given helloSystem avoidance of non-graphical consoles, this should not be a show-stopper.

Can you provide screenshots of what's required and what's different?

If not screenshots (from a virtual machine): photographs.

… Some packages are significantly larger … git-lite

Is any particular size a show-stopper? If so, why?

py37-lxml

Not specific to FreeBSD 13.⋯: given the switch to 3.8 https://cgit.freebsd.org/ports/tree/UPDATING?id=210ee04dd3c3f2e82cd3130e412866a182066859#n8 as the default for python3 and python, more than four months ago, I recommend focusing instead on py38⋯.

Issues

https://sourceforge.net/projects/scribus/files/scribus-devel/1.5.6.1/scribus-1.5.6.1-linux-x86_64.AppImage/download?target=_blank … lead to a bad kernel crash and instant reboot

Superior version 1.5.7_5 is packaged for FreeBSD:13:amd64:

Some AppImages …

Please identify another.

Thanks.

grahamperrin commented 3 years ago

Some AppImages reproducably lead to a bad kernel crash and instant reboot

With the given image: not reproducible.

Can you provide steps to reproduce? Maybe in a separate issue (to not over-complicate this issue). Thanks.

probonopd commented 2 years ago

Why is the 0.7.0 build ~500 MB larger with FreeBSD 13?

image

probonopd commented 2 years ago

0G35 cannot boot on non-EFI systems:

CD Loader 1.2

Bulding the boot loader arguments Looking up /BOOT/LOADER... File not found Looking up /boot/loader... File not found Boot failed

The file seems to be there...

Here is the same system booted on a UEFI based machine:

image

What is going on?

grahamperrin commented 2 years ago

What is going on?

FreeBSD 13.0-RELEASE based experimental 0.7.0 build · Discussion #229 · helloSystem/hello

probonopd commented 2 years ago

Can you provide screenshots of what's required and what's different?

In VirtualBox, I get none of the FreeBSD fonts at all, but the BIOS ("MS-DOS") font.

On different real machines, I get various ("random") font sizes for the console text during boot.

Here someone seems to have the same issue (too large text compared to 12.x):

https://twitter.com/kaevans91/status/1452133650439548936/

image

probonopd commented 2 years ago

Relevant discussion on ISO sizes and compression: https://github.com/helloSystem/hello/discussions/229#discussioncomment-1529104

probonopd commented 2 years ago

https://forums.FreeBSD.org/threads/from-12-2-to-13.79837/post-506493

in loader.conf: screen.font="8x16" will reduce the font size and make it appear the same size as VT 1024x768 font size from FreeBSD 12.2.

So, in /boot/loader.conf:

# Make font size same as it was before FreeBSD 13
screen.font="8x16"

Check /boot/fonts to see which fonts are available.

One more thing fixed!

probonopd commented 2 years ago

network:/// stays empty

Why? How can this be debugged?

On FreeBSD 13 we get:

FreeBSD% ps ax | grep gvfs
2565  -  I     0:00,04 /usr/local/libexec/gvfsd
2677  -  S     0:00,08 /usr/local/libexec/gvfsd-trash --spawner :1.38 /org/gtk/gvfs/exec_spaw/0
2766  -  I     0:00,03 /usr/local/libexec/gvfs-mtp-volume-monitor (gvfs-mtp-volume-mon)
2768  -  I     0:00,03 /usr/local/libexec/gvfs-gphoto2-volume-monitor (gvfs-gphoto2-volume)
2769  -  S     0:00,06 /usr/local/libexec/gvfsd-computer --spawner :1.38 /org/gtk/gvfs/exec_spaw/1
3101  -  I     0:00,02 /usr/local/libexec/gvfsd-metadata
3107  -  I     0:00,04 /usr/local/libexec/gvfsd-network --spawner :1.38 /org/gtk/gvfs/exec_spaw/2
3110  -  I     0:00,02 /usr/local/libexec/gvfsd-dnssd --spawner :1.38 /org/gtk/gvfs/exec_spaw/4

gvfs is one of the remaining non-FreeBSD-native parts in the system that is complex, fragile, and under-documented. We should consider to replace it with something more robust. Our Zeroconf application is a start for browsing the network, but we would need to implement e.g., FUSE based mounting of SSH/SFTP shares. And possibly someone cares still abot Windows Network?

image

probonopd commented 2 years ago

Network works now:

image

Don't ask me why. But I am glad that it does.

probonopd commented 2 years ago

...and with that: No more showstoppers. If nothing new pops up, then helloSystem 0.7.0 will be based on FreeBSD 13-RELEASE.

Feel free to comment here if you think there are still showstoppers.