About News Download Docs Forum Bugs Contact

Forum

Information

Tools

Resources

All posts created by stealth

Submitted by stealth 30 Sep, 2021 00:49 #

How about trying vga=ask, vga=normal and vga=771 in /etc/lilo.conf?

As well as append="video=640x480" OR append="nomodeset i915.modeset=0" under the kernel image section.

Have a sourcerous day!

Edited 30 Sep, 2021 02:22
Submitted by stealth 29 Sep, 2021 14:56 #

flux_control on #sourcemage also suggested this:

<flux_control> Stealth: My guess would be display issues.
<flux_control> I haven't checked the chroot kernel config in a while, but if it includes a whole bunch of different display drivers (likely, in order to support different hardware combinations), it's possible that the kernel is wrongly autodetecting and (via userland) autoloading kernel modules that are blanking the display.
<flux_control> There should be a kernel bootparam to force the display to old but gold standard vga 80x25.
<flux_control> The other things I can think of immediately are that possibly (depending on hw and how the user is booting) the kernel is switching to a serial console as the default console output which they wouldn't see unless they connected to it, or that there's possibly even a hw issue.
<flux_control> Stealth: I took one last glance at the forum post. They mentioned initramfs. I would also recommend trying to boot the kernel config without the initramfs (it should crash if the initramfs is needed for something), and even if they get the same result that way, they should check the initramfs if *that* is loading kernel modules or whatever too.
<flux_control> An initramfs is like a whole other OS loaded before the real OS, so the problem could either be there or the real root OS loaded after. It's not clear at what point the display dropped, as in how far the kernel loaded.
<flux_control> If it was the initial "uncompressing kernel image BLAH ..." and then the display immediately dropped that's very different from going blank after loading wlan drivers, for example

Have a sourcerous day!

Submitted by stealth 29 Sep, 2021 14:16 #

I would double check the modules in use when you loaded the system that was used to install SMGL and compare configuration to compiled-in modules / initramfs. Could be some specific controller driver (like vmd) or FB driver.

I would also check another kernel compiled with the config of Arch or Void if they boot successfully.

Have a sourcerous day!

Edited 29 Sep, 2021 14:25
Submitted by stealth 06 Sep, 2021 16:12 #

cast -r

Have a sourcerous day!

Submitted by stealth 11 Aug, 2021 04:21 #

Hi!

The recent chroot image extracts up to 900MB.

Have a sourcerous day!

Submitted by stealth 11 Aug, 2021 04:19 #

Hi!

If you're asking about the i686 chroot image, then yes, we keep it in sync with x86_64 one, and have no plans of deprecating it for now.

Have a sourcerous day!

Submitted by stealth 26 Jul, 2021 15:11 #

Good to see some activity here :)

Have a sourcerous day!

Submitted by stealth 28 Jun, 2021 02:16 #

I would avoid mounting ESP on /boot.

Recently our chroot installation guide was updated with some notes re:UEFI and disk layout.

tl;dr use /boot for kernels and mount EFI system partition under /boot/efi.

Have a sourcerous day!

Edited 28 Jun, 2021 04:02
Submitted by stealth 20 Mar, 2020 03:15 #

Just a place to say hi for new users.

Yeah, good point. I think it can be as small as a sticky topic in General Chatter.

Have a sourcerous day!