I tried booting the install cd with my pc in uefi mode (secure boot off) but all the graphics were distorted and jammed in top half of laptop display (intel graphics). I never had this issue before with Slackware but was usually in MBR mode in BIOs.

Does Slackware just run better in MBR mode? I don't care whether EFI or not (I have no idea if one is 'better').

[EDIT] Just tried it with USB, the "welcome to Grub" appears, then the menu, I select the boot with huge.s and then the graphics distort and I can read nothing. The laptop is in UEFI mode right now. I will search some more, I read about eLilo...

[Edit 2] Just found this in the slackware docs wiki.
I guess that answers that...

Thanks.

John

Are you leaving (or dual-booting) Windows 8 or 10? Just want to make sure you are also doing a full shutdown because Windows is becoming notorious for entering hibernation instead of actually shutting down, especially on laptops. Trying to boot Linux while Windows is still technically running (in hibernation) can cause problems.

While in UEFI settings, another thing to disable is Fast Boot if you see it there.

And finally, to me your trouble sounds like a video driver problem, rather than UEFI and hard drive settings (MBR vs GPT). But let us know how you're doing with it and if you run into other issues.

Cheers!

Windows has been gone a while. I have been mostly using debian/ubuntu based distros and wanted to go back to slackware. I never had that issue before and used Slackware before on the same PC and it booted fine (always in legacy bios before though) but when I tried uefi mode the graphics went weird. I switched to legacy BIOS mode and it booted right up perfectly.

I have not tried it on the laptop I am using now yet soon though.

Well, I continue to learn new things here. I would not have guessed that Legacy BIOS versus UEFI would have made a video difference, but there's no arguing with your success.

1 members found this post helpful.

I have been using EFI and elilo on a Surface Pro 3 i5 (Intel graphics) for many Slackware 14.2 installation tests and have not had any graphics problems. I deleted the Windows partitions.

Yeah, it worked fine on my Lenovo, it was the somewhat older Dell that had an issue but that is sorted now.

Hi
Yes, I think this post is relevant, because the discussion seems not to be closed and that I am in the same situation.
My hardware is an ASRock BEEBOX N3000. Processor is Celeron, with Intel Graphics part.
I installed Slackware64-14.2 on a USB stick and installation process goes fine until the reboot on new system.
After entering user and password, I have access to my files.
Then, I shift starting level to 4 and everything goes right.
Now I use slackpkg to get the upgrades via http://nephtys.lip6.fr mirror. But when I reboot the upgraded system freezes on the access. Either there is no action of the keyboard (impossible to enter the code user and password or, if the run level is 4, the opening of the dialog screen does not happen, randomly (if the screen is obtained, there is no keyboard action)).
I installed all packets, except emacs, kde and kdei, source codes and games. My disk manager is xfce.
I repeated the installation process with the same result.
Best regards
Jean-Claude

Hello/Salut Jean-Claude,
There is nothing in your post that would lead to this assumption, as I see nothing about BIOS or UEFI in it.
Better make your own thread with a more meaningful title next time.

Do you really mean that the system was installed on an USB stick, or using an USB strict as installation media?

Which exact commands did you type?

And, more importantly, which exact mirror did you uncomment in /etc/slackpkg/mirrors? Please copy and paste the full line in your next post. I ask because I am suspecting that the line ends in current/ not 14.2/ and this could explain that.

Did you also run slackpkg, and was the system working before?

A bientôt,

My guess would be that you upgraded the kernel but forgot to update your boot loader by running either lilo or eliloconfig before rebooting. Another possiblility is that you have a mismatch between the kernel version and the installed kernel-modules.

Hi!
Answer to laprjns:
I follwed the setup procedure. I did not ask to install Lilo, because there is an EFI partition on my main disk. Si I ask for installation of Elilo. Everythig was OK.
The problem appears when I upgrade the packages. At login (in console) the keyboard is ineffective.
Answer to Didier Spaier:
1-I will open a thread in Newbie forum.
2-the USB stick was installed following instruction in usb-and-pxe-intallers directory. I add the directory slackware64 part of the slackware64-14.2 distribution.
3-the commands were: slackpkg update gpg --- slackpkg update --- slackpkg upgrade-all.
4-the line in /etc/slackpkg/mirrors is: "http://nephtys.lip6.fr/pub/linux/distributions/slackware/slackware64-14.2/"
5-after the freeze, I do a complete identical reinstallation and ask for upgrade. Same situation.
I open a thread in newbie forum.
Thank you for all. Very useful, I am learning a lot.
BR
Jean-Claude

After upgrading the packages, and BEFORE rebooting the computer you need to run eliloconfig to update the bootloader.

The package upgrade that you did included a new kernel and kernel-modules. If the boot loader is not updated before rebooting then on reboot the boot loader loads the old kernel, which then loads the new kernel-modules. This mismatch of kernel and kernel-modules results in your keyboard driver to not work properly.

1 members found this post helpful.

Hi laprjns!
I tested my USB installer on another computer, a laptop FUJISTSU-SIEMENS, LIFEBOOK Eseries, a rather old machine. Everything works fine until Desktop. It remains some questions with the terminal emulation in X software, but this is another question.
It is a dual boot machine with Windows Vista.
I choose to not install emacs, sources, KDE and KDEI, tetex and games. Arrived to lilo installation, I asked for manual installation and add windows entry. Afterwards I installed upgrades.
The differences between the two machines are:
1- LIFEBOOK has not an EFI motherboard,
2- the video system of the other machine is different.
The question seems linked to the lilo/elilo soft.
I did not use the command eliloconfig. I will do.
This is my next test.
Thanks for help
BR
Jean-Claude

Hi That's it! Just run eliloconfig...
BR
Jean-Claude

it's a toss up, depends on what you prefer.

I did it and it works perfectly. This was the problem, in that case....