Gregory's Server@Suiseiseki I insist that it is acceptable. Sure the kernel won't work by itself, but that is not what my point was. This device is not usable because there is no support for the hardware it has *in the kernel*. No init can change that.
|
9 comments
 @Suiseiseki I didn't mention any login prompt. The fact that framebuffer works doesn't imply login prompt, it doesn't even imply you can access built-in storage and mount the root partition, right? You need to read the root partition for init to run. Find me one time when framebuffer worked but not login. @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. init (and so is framebuffer mode I think) runs after initrd. I think initrd is also optional unless I'm mixing things. @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. @iska @Suiseiseki Then a lot of other shit happens, agetty or something similar gets started and you get the login prompt. At last! I thought you see the panic in grub's console, at least at this stage. |
You just claimed it booted up into a framebuffer.
If Linux doesn't have drivers for the hardware you're trying it with, it simply won't boot (although generic drivers leave much to be desired).
If you got into a framebuffer login prompt, that is perfectly usable, as you can use emacs (rms prefers framebuffer emacs), nano and a bunch of other GNU tools just fine.
The only reason why I use Xorg, is because Xorg lets me use lots of terminals on multiple monitors, and it can display UTF-8 (for ใงใ).
You just claimed it booted up into a framebuffer.
If Linux doesn't have drivers for the hardware you're trying it with, it simply won't boot (although generic drivers leave much to be desired).