Slackware on UEFI
I just bought a Acer Aspire M5 481t-6617 ultrabook and I cant stand this win8 bullshit, so my first option is my desktop distro (slack)..
I could not find any information on the model itself about drivers on the linux kernel and Im not sure if the stuff the comes with it will work properly on slack (and his vanilla(?) kernel), keyboard backlights, webcam, dvd drive, the wierd keyboard, the touchpad... but I dont care, I'll deal with that later.. Now on the bios I saw that there is UEFI and it is enabled, so Im thinking only desabling it and putting on legacy boot would do the trick for me? should I try to run slack under uefi? I found this http://docs.slackware.com/howtos:sla..._uefi_hardware but to be honest, Im scared of trying.. Anyone can tell me their experiences with the uefi thing and theres a way to know for sure the if features on the ubook will work ? ps: sorry for being a noob |
The features are all likely to work fine. If you have Windows 8 and want to keep it, start by hitting (windows key) + X, select the disk management program, and resize the windows drive to make some free space for the Slackware installation. Boot the x86_64 Slackware install disc under the legacy boot mode and with Secure Boot turned off (probably you'll want to leave it off anyway). The installer handles GPT fine, so make your partitions using cgdisk. If you made a swap partition, run mkswap on it before running setup, and then proceed to install as usual. Skip the LILO installation.
Last step is probably the tricky one, but not too bad. It might be easier to do from the installed system than from the installer since you'll have network access there. Leave the machine in legacy boot mode for now, reboot the install disc, and use it to boot the installed system. Then, find the EFI boot partition. This is a smallish FAT partition with an EFI directory that contains a Boot and Microsoft directory. Make a slackware directory in there, and put your kernel (and initrd if you use one) in it. Download the elilo sources, and install the prebuilt 64 bit EFI elilo binary in /efi/slackware/. elilo.efi is a good name to give it. Last, you need an elilo.conf config file. The syntax is similar to lilo.conf. Here's an example I'm using here (still giving a few errors yet, but it works): Code:
prompt That's what I've got so far. Hope it helps. |
This is a good news!
A good point for Slackware. |
thats awesome volkerdi, thank you !
I'll try it out on the weekend, need to do some research on how to find the EFI boot partition but this looks like its gonna be way easier than I thought... Still dont think some of the features will work tho.. Anyway, much appreciated ! |
I will note here luz...it may not be so easy. The SecureBoot can be disabled and still prevent it from booting to a CD.
In most cases it means looking up the manufacturer's info on the specific make and model and find out if the BIOS can be changed to allow CD boots or if you have to re-flash the bios to something that will allow it. I've already seen this problem a few times. It isn't fun.. |
Doing a bare metal install the slackware64-14.0 dvd booted and installed automagically on an AsRock Z77 Extreme4 without any modifications to UEFI. Then I simple made a efi partition as PV describes and it was easy-peasy from there.
John |
Quote:
Funny story. On the UEFI I'm testing with, until the kernel loads the KMS video driver and initializes the framebuffer console, there's no video. So when my tests began, I was running blind. I spent a couple of days trying to boot an installation from a GPT stick with an EFI partition, the huge kernel, and elilo. Every time it would hang, and since there wasn't any video yet I was left to guess why. First I thought the elilo.conf had a bug somewhere, then considered that maybe the huge kernel was too big (ran into that with LILO a few years back). I could get the huge kernel to boot the installer, and could get generic+initrd to boot the installation. I booted the installer (which still doesn't have the video support) and typing with no video tried to mount the root partition on /mnt, and run "touch /mnt/tmp/kilroy" just to prove I'd been there. When I checked on the system, it wasn't there. That's when it occured to me that the huge kernel was probably giving /dev/sda to the USB stick. I booted the installed system again with the huge kernel but this time pulled the stick out as soon as the kernel loaded, and the system booted fine that time. :) Probably time to move the USB modules out of the huge kernel... or maybe even get rid of that thing, finally. |
Quote:
Of course assuming that auto-loading of the needed modules works. This is true for my laptop but I must admit that this is a very small sample of your users base ;) |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
I heard a rumour that Pat's dropping the huge kernel? Can anyone enlighten me?
cheers, |
Member Response
Hi,
I think eguh kernel is now the default. :) |
Quote:
Mais c'est un peu passé de mode ;) Reference |
All times are GMT -5. The time now is 08:15 AM. |