Can samsung smart pc pro UEFI-boot a 32-bit slackware installation?
This may be a dumb question, but I've installed regular 32-bit slackware-current (about a month ago) using CSM/BIOS mode on a samsung smart pc pro. I didn't install (e)lilo, but rather was (CSM-)booting using the usb bootstick made during setup. Since elilo and other uefi-friendly updates have been made to slackware-current (including the newer kernel with the samsung-uefi-booting-bricking-because-of-terrible-firmware issue workarounds) I've tried to set it up to uefi-boot.
Now I've tried setting up elilo and it starts, seems to find the kernel, but then shuts down and the machine resets. It occurs to me that it may be simply because it's a 32-bit system. Is this the case? I should add that I was prompted to ask this because of the following comment on another post: Quote:
Thanks in advance, Michael |
From https://wiki.archlinux.org/index.php...tions_for_UEFI
Quote:
|
Thanks for the reference but adding the single "noefi" kernel command-line parameter did not fix the problem.
Interestingly though, after reading this on another post: Quote:
I wonder if anything else is needed - can I simply run the 32-bit system with a slackware64 kernel and forget about it? Or will I run into problems e.g. if I start trying to compile software? I guess, thinking about it Alien Bob's multilib stuff is just replacement glibc libraries etc, no change to the kernel, so I guess this is (partly) what is meant when he says slackware64 is "multilib ready"; so there probably should be no problem. Cheers, Michael |
All times are GMT -5. The time now is 06:33 AM. |