Email or username:

Password:

Forgot your password?
r2t3 :tor: :wireshark: :artix: :bitcoin: 📈 🌕 :chad2:'s posts Post Back to profile
Top-level
Iska :emacs_thinking:​ :guix:

@m0xee @Suiseiseki

You need to read the root partition for init to run. Find me one time when framebuffer worked but not login.

16 Jul 2022 at 12:59 | Wall-to-wall | Open on mstdn.starnix.network
6 comments
m0xEE replied to Iska :emacs_thinking:​ :guix:

@iska @Suiseiseki There is this thing called initrd. Yeah, if you go into nitpicking mode, you can pretend you didn't understand what I was talking about.
Just do dd if=/dev/random of=the-block-device-you-have-your-real-root-partition-on and see how framebuffer works, but you still get no login prompt 😄

16 Jul 2022 at 13:05 | Open on social.librem.one
Iska :emacs_thinking:​ :guix: replied to m0xEE

@m0xee @Suiseiseki

init (and so is framebuffer mode I think) runs after initrd. I think initrd is also optional unless I'm mixing things.

16 Jul 2022 at 13:17 | Open on mstdn.starnix.network
m0xEE replied to Iska :emacs_thinking:​ :guix:

@iska @Suiseiseki It sure does! the bootloader reads initrd image and just passes it to the kernel. Kernel doesn't know shit about most file systems at this point. The init itself is in initrd image (so initrd comes first), so are the filesystem modules. Init inserts filesystem modules (and the modules required for the block devices to work) into the kernel then mounts the real root filesystem, now that it has the proper filesystem support and has the block device accessible.

16 Jul 2022 at 13:23 | Open on social.librem.one
m0xEE replied to m0xEE

@iska @Suiseiseki Then a lot of other shit happens, agetty or something similar gets started and you get the login prompt. At last!
Thing is, if real root filesystem is not accessible: block device is not accessible, filesystem is not supported or it is damaged — you won't get the login prompt. But you will still see the errors in *framebuffer* console.

16 Jul 2022 at 13:26 | Open on social.librem.one
Iska :emacs_thinking:​ :guix: replied to m0xEE

@m0xee @Suiseiseki

I thought you see the panic in grub's console, at least at this stage.

16 Jul 2022 at 13:27 | Open on mstdn.starnix.network
翠星石 replied to Iska :emacs_thinking:​ :guix:
@iska You won't see anything in grub's console, as grub is no longer running when Linux is launched.
He mentioned that Linux booted, and stuff about networking, which strongly implied that the login prompt worked, but of course he didn't actually say what occurred.
Linux does output logs to framebuffer during early boot and so you can boot up just Linux (with no rootfs) and watch it panic(), but it's a incredible stretch to say the computer can "boot linux" - when booting didn't finish.
@iska You won't see anything in grub's console, as grub is no longer running when Linux is launched.
He mentioned that Linux booted, and stuff about networking, which strongly implied that the login prompt worked, but of course he didn't actually say what occurred.
16 Jul 2022 at 13:35 | Open on freesoftwareextremist.com
Go Up