I'm in a similar situation to rkelsen: http://www.linuxquestions.org/questi...2/#post4888222
but with some differences.
I've acquired a samsung hybrid ultrabook/tablet (XE700T1C-A02AU, the Australian build of the so-called smart pc pro), with win8 pre-installed...of course. My original plan was to keep win8 there (at least for the time being) but dual-boot it with 32-bit
I shrunk the win8 partition, created a new partition for slackware and a separate one for swap, all from inside win8.
Next I looked into booting the install disk. Under the advanced boot settings in the uefi setup there are 3 choices: uefi only, csm (compatability support module, i.e. legacy) only or both.
Choosing ``both uefi and csm'' (also works under csm-only of course), I was able to boot up the install disk, after changing the boot order priority. I used mkswap, ran setup and managed to perform all of the installation properly except lilo (I'd seen warnings about it at slackdocs) and so created a USB boot stick.
Now it boots and works fine, but I am dependent on the bootstick. It boots under csm/legacy, not uefi. If I leave the boot setup at ``uefi and csm'' I have to have the bootstick in there or win8 boots *and* the boot setup forgets that setting. If I set it to ``csm only'' and I forget to insert the bootstick, it just opens up the uefi setup menu (reminding me to insert the bootstick and reboot). This is fine so long as I don't want to boot win8, but it is still far from ideal.
If I were happy to get slackware to boot with uefi, the info in some earlier posts would probably get me out of trouble. However as Pat noted:
Originally Posted by volkerdi
Yes. This is just information for the people who want to brick their Samsung laptops now.
So it may be a bit dangerous for me to try to boot into slackware using uefi, although I have seen on some other webpages that not *all* samsung laptops are problematic, only some. But there is sufficient confusion to convince me to remain cautious and hold off from doing this for now.
So it would seem I should be booting under csm, i.e. convert the disk from GPT to MBR. It is not clear (to me at least) how to implement this. There is some good general info at rodsbooks.com/gdisk/mbr2gpt.html#gpt2mbr
but it is still a bit unclear what I need to do in my situation. I would like to keep the win8 there if I can (there is a samsung win8 app that does mathematical handwriting recognition!!...no open source version exists AFAIK). Unfortunately, it seems I can't make a ``recovery disk''; there are some hidden and recovery partitions on the disk which need to stay there, presumably under GPT, for the ``power-up-with-volume-up-pressed'' recovery procedure to work. I don't know enough about it but I think that even if I use win8 to create a backup or even a factory image, if I wipe the disk clean there may be no (easy) way to recover my (samsung-specific, with custom e.g wacom tweaks) win8. I could perhaps keep the hidden/recovery partitions there even if I convert from GPT to MGR, although I don't know how exactly (and maybe this is pointless anyway?).
As far as I can tell, I should use gdisk (from inside slackware, as root) to change the disk from GPT to MBR, using the `r' command to take me to the recovery/transformation menu. Then I can either use `g' to convert it to MBR, or maybe even `h' to create a hybrid GPT/MBR disk, although this looks *way* beyond my comfort zone. Since there are more than 4 partitions, some will be made logical so long as there is an empty sector (or something) at the beginning of the partition. So using `g' may mean I lose some of these. I can perhaps keep them all using `h'. I don't know.
I am suitably unsure that I thought I would try to ask someone who actually knows what they are doing before I blunder in and possibly ruin everything. My apologies if I have omitted any vital info on this, my first LQ post.
Thanks in advance,