LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-03-2018, 12:42 PM   #16
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 335
Blog Entries: 2

Rep: Reputation: 144Reputation: 144

Quote:
Originally Posted by brobr View Post
Yes you are right; the GPT filesystem leaves the MBR intact; you can have both with GPT: booting lilo from MBR with bios set to legacy OR efi with bios set to uefi but then -normally- you need a EFI partition. When I was changing over my system from lilo to uefi booting I came in the weird situation that I could boot either way depending on those bios settings. So maybe the OP needs to check how this is set up (press F1 or F2 during boot to get in the bios). All conditions for uefi needs to be there for the Slackware installer at the time to use uefi for booting instead of lilo. Since then grub came along and I never lookied into that as refind/elilo or lilo did the job.

As it looks that grub is set to boot the computer, can the OP change some settings for grub to make this happen correctly? Could it be possible that the bios is set to efi, then the bootloader used is grub that needs to find the new kernel (in say the /boot folder and not a specific EFI-partition - refind is able to do something like this; I dunno about grub) but is not yet set to do so (after the semi-controlled kernel upgrade)?

Maybe easiest is to wipe the system and do a complete 14.2-reinstall and upgrade from /patches


PS I was not aware of the 3-page prelude to this (a lot of effort in there @bassmadrigal!), thus swap (and not EFI) will be sda1 and / sda2 in:
from dmesg
from lsblk
Macbooks do not have a bios menu that can be accessed.
 
Old 08-03-2018, 02:40 PM   #17
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 507

Rep: Reputation: 124Reputation: 124
OK, is also, as explained here -but in 2006, the 'openfirmware' no longer accessible/used, say with commands described here; or holding down the Option/Alt-key during boot to get to a boot-menu, or is that only working when OSX is installed?
 
Old 08-05-2018, 06:02 AM   #18
l0f4r0
Member
 
Registered: Jul 2018
Location: Paris
Distribution: MacOS, Slackware
Posts: 62

Original Poster
Rep: Reputation: 13
Quote:
Originally Posted by khronosschoty View Post
Look for something like a /sys/firmware/efi after you boot into the install media
Code:
Originally Posted by https://itsfoss.com/check-uefi-or-bios
The easiest way to find out if you are running UEFI or BIOS is to look for a folder /sys/firmware/efi. The folder will be missing if your system is using BIOS.
I don't have anything like /sys/firmware/efi. All I have in the 'firmware' folder is acpi/, dmi/ and memmap/
Then, I don't understand as it seems contradictory with https://support.apple.com/en-us/HT201518#macbook...

Quote:
Originally Posted by bassmadrigal View Post
s/he
He

Quote:
Originally Posted by brobr View Post
PS I was not aware of the 3-page prelude to this (a lot of effort in there @bassmadrigal!)
Yeah, thanks again bassmadrigal!

Quote:
Originally Posted by brobr View Post
OK, is also, as explained here -but in 2006, the 'openfirmware' no longer accessible/used, say with commands described here; or holding down the Option/Alt-key during boot to get to a boot-menu, or is that only working when OSX is installed?
Your 'as explained here -but in 2006' link doesn't work. Did you mean http://blandname.com/category/bios/?
Anyway, it seems that Open Firmware was used in the Mac PowerPC era, but mine was shipped with an Intel processor so I think it doesn't use Open Firmware.
I've tried to press alt/option key nonetheless during boot time. Without the install DVD, it prompts absolutely nothing (black screen) while with the install DVD it prompts 'Windows' (?? - which launches the DVD boot: 'boot' prompt) and 'EFI boot' (which launches GRUB).

Last edited by l0f4r0; 08-05-2018 at 08:15 AM. Reason: Add boot options with Alt command+install DVD inserted
 
Old 08-05-2018, 08:09 AM   #19
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 507

Rep: Reputation: 124Reputation: 124
Quote:
I don't have anything like /sys/firmware/efi.
Maybe because you have a pre-retina model and therefore also without an EFI-partiton; which would mean that the lilo-route discussed before was the way to go. It just seems that grub is the bottleneck and that the slackpkg upgrade removed your working kernel/modules but did not repair the route to call the new ones. When you boot up via the DVD and as described mount the local discs under /mnt can you check what is set for grub (in /mnt/etc)
 
Old 08-05-2018, 08:26 AM   #20
l0f4r0
Member
 
Registered: Jul 2018
Location: Paris
Distribution: MacOS, Slackware
Posts: 62

Original Poster
Rep: Reputation: 13
Quote:
Originally Posted by brobr View Post
When you boot up via the DVD and as described mount the local discs under /mnt can you check what is set for grub (in /mnt/etc)
Under etc I have the following folder related to 'grub': grub.d which contains the following files:
  • 00_header
  • 10_linux
  • 20_linux_xen
  • 30_os-prober
  • 40_custom
  • 41_custom
  • README
 
Old 08-05-2018, 09:09 AM   #21
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 507

Rep: Reputation: 124Reputation: 124
I have the same but grub is not used at my end (efi with elilo/refind). I have no experience with grub but to me it seems these scripts control its sequence.
Is there anything in (/mnt)/boot/grub? (Empty at my end); what does (/mnt)/etc/default/grub say?

Last edited by brobr; 08-05-2018 at 09:11 AM.
 
Old 08-05-2018, 09:57 AM   #22
l0f4r0
Member
 
Registered: Jul 2018
Location: Paris
Distribution: MacOS, Slackware
Posts: 62

Original Poster
Rep: Reputation: 13
Quote:
Originally Posted by brobr View Post
Is there anything in (/mnt)/boot/grub? (Empty at my end); what does (/mnt)/etc/default/grub say?
There is nothing in (/mnt)/boot/grub.
Attached is the output of (/mnt)/etc/default/grub.
Attached Files
File Type: txt grub.txt (926 Bytes, 4 views)
 
Old 08-05-2018, 10:07 AM   #23
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 335
Blog Entries: 2

Rep: Reputation: 144Reputation: 144
Some possible ways forward:

Try making a refit or refind boot usb or dvd, and using that to boot the Slackware install media.

Do you still have OSX available for booting? If you do then figure out how to use the 'bless' utility to 'bless' grub or elilo to boot osx like found here
 
Old 08-05-2018, 11:12 AM   #24
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 507

Rep: Reputation: 124Reputation: 124
Well, with respect to grub, I have the same here; so it seems unused. Still, somehow your system is recognized (by the installer DVD) as efi:
Quote:
I've tried to press alt/option key.. during boot time. ....with the install DVD it prompts 'Windows' (?? - which launches the DVD boot: 'boot' prompt) and 'EFI boot' (which launches GRUB).
If the DVD uses grub, it could see it as efi because of the GPT partition
Also, when booting normally you get grub because being there with the GPT, it assumes efi, as illustrated here. As only the first bits are there and can be used the boot halts midway. So grub seems to have been installed; as grub or grub2? - but grub runs into a dead end (no /boot/grub/grub.config etc)

Best maybe to read up on grub(2) and consider whether you want/can repair it.

As far as I can tell, you need to get rid of grub (if ever installed), or use something else than the installer-DVD to boot as suggested by khronosschoty. If you want to boot without using a startup disc/usb it looks the lilo reinstall did not work. As also found with DuckDuckGo, you could consider something like this

EDIT Sorry for the many changes, but khronosschoty's post made me wonder whether grub only appears when trying to boot the system using the install-DVD

Last edited by brobr; 08-05-2018 at 11:41 AM.
 
Old 08-05-2018, 11:49 AM   #25
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 507

Rep: Reputation: 124Reputation: 124
Quote:
with the install DVD it prompts 'Windows' (?? - which launches the DVD boot: 'boot' prompt)
Maybe this is the way to go; non-efi windows uses MBR; did you try something like this at that boot prompt:


Quote:
In a pinch, you can boot your system from here with a command like:

boot: huge.s root=/dev/sda1 rdinit= ro

In the example above, /dev/sda1 is the / Linux partition.
EDIT: Well you've been doing that already according to your first post.

Last edited by brobr; 08-05-2018 at 11:57 AM.
 
Old 08-05-2018, 12:11 PM   #26
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,421

Rep: Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181
Forget about lilo. You just need to refresh /boot/grub/grub.cfg to mention the new kernel, and there's no need to edit it by hand:
  • Start the installer from the DVD
  • As soon as you are logged in as "root, type:
    Code:
    mount /dev/sda2 /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    chroot /mnt
    grub-mkconfig -o /boot/grub/grub.cfg
  • Type "exit" then "reboot"
Then grub should allow you to start Slackware with the new kernel.

To ease things, next time you upgrade the kernel, just type as root:
Code:
grub-mkconfig  -o /boot/grub/grub.cfg
before rebooting.

PS instead of grub-mkconfig you could run eliloconfig, but that would fail as you have no file /sys/efi/firmware. Maybe eliloconfig could be modified to run even if this file is not found, with the limitation that then it woildn't be able to write a boot entry in the firmware's boot menu. However this change is probably not worthwhile, as they are not so many EFI able machines missing it.

Last edited by Didier Spaier; 08-05-2018 at 12:29 PM.
 
Old 08-05-2018, 12:52 PM   #27
l0f4r0
Member
 
Registered: Jul 2018
Location: Paris
Distribution: MacOS, Slackware
Posts: 62

Original Poster
Rep: Reputation: 13
Quote:
Originally Posted by Didier Spaier View Post
Forget about lilo. You just need to refresh /boot/grub/grub.cfg to mention the new kernel[...]
I clarify that I have no /boot/grub/grub.cfg file at this point. Don't know if it's normal...

Quote:
Originally Posted by Didier Spaier View Post
[...]and there's no need to edit it by hand:
  • Start the installer from the DVD
  • As soon as you are logged in as "root, type:
    Code:
    mount /dev/sda2 /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    chroot /mnt
    grub-mkconfig -o /boot/grub/grub.cfg
  • Type "exit" then "reboot"
Then grub should allow you to start Slackware with the new kernel.
Anyway, I've run your command which output no error.
Problem is that it doesn't seem to change anything after reboot... (GRUB launches and, after choice 1 'Slackware 14.2 huge.s kernel', displays "Loading huge.s kernel and installer initrd. Please wait..." but makes apparently nothing) :'(

EDIT: Additionally, things continue to look *weird*...
  • 1] with the install DVD inserted:
    • a] if I press no key, then GRUB is launching with the dead-end mentioned above
    • b] if I press the 'C' key, then I can either (see my first point):
      • i] type "huge.s root=/dev/sda2 rdinit=ro"
      • ii] or type nothing but <ENTER>, select my keymap, login as root, chroot and so on...
  • 2] without the install DVD inserted: my MacBook displays the icon of a missing folder (black folder with a question mark inside) on a grey background and does nothing.
*weird* because 1]a] seems to be launched with an optical drive noise so it seems that it boots on the DVD. Then I don't know what makes a difference between 1]a] and 1]b] since I thought the purpose of pressing the 'C' key was indeed to boot on the DVD at startup. And if this is not the case (if 1]a] doesn't use the DVD) then I do not know the difference with 2]...

Last edited by l0f4r0; 08-05-2018 at 01:12 PM.
 
Old 08-05-2018, 01:07 PM   #28
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,421

Rep: Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181
Did you remove the DVD before rebooting ?
 
Old 08-05-2018, 01:12 PM   #29
l0f4r0
Member
 
Registered: Jul 2018
Location: Paris
Distribution: MacOS, Slackware
Posts: 62

Original Poster
Rep: Reputation: 13
Quote:
Originally Posted by Didier Spaier View Post
Did you remove the DVD before rebooting ?
Please see my last edit on #27

Last edited by l0f4r0; 08-05-2018 at 01:14 PM.
 
Old 08-05-2018, 03:19 PM   #30
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,421

Rep: Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181Reputation: 3181
The installer uses syslinux in case of legacy booting, but grub in case of EFI booting

So I assume that that when you boot with the DVD inserted, if you don't press the 'C' key the firmware is in EFI mode, that's why you see the GRUB menu of the installer, but if you press 'C' instead the firmware is in Legacy mode, so you see the Syslinux menu of the installer.

What confirms that is that this boot menu:
Code:
GNU GRUB version 2.00
Slackware 14.2 huge.s kernel
Slackware 14.2 huge.s kernel (use KMS console)
Detect/boot any installed operating system
is the one displayed by the installer in case the firmware is in EFI mode, not menus displayed by grub after installation (as your thought initially). This just tells us that this grub version doesn't work with your machine for some reason.

So, your best bet is to just use the same steps as in my previous post but after:
Code:
chroot /mnt
instead of typing
Code:
grub-mkconfig   -o /boot/grub/grub.cfg
type:
Code:
lilo t -v
and if that seems OK:
Code:
lilo
Then, remove the DVD and reboot, pressing C if need be.
 
  


Reply

Tags
boot loader, lilo, macbook, slackware 14.2


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Hard drive standby time impossible to set in hdparm BlackTornado Linux - Server 4 03-06-2013 07:23 AM
can you install Linux on an external hard drive on a Macbook? hedpe Linux - Newbie 1 07-28-2011 02:21 AM
Macbook - transfer hard drive to new desktop di5cord Linux - Hardware 9 06-08-2011 02:58 AM
External Hard Drive Won't Mount on Karmic, Macbook 2,1 vanessa1 Linux - Newbie 2 01-31-2010 02:53 PM
Running Ubuntu Live CD on a Macbook with a busted hard drive samsom Linux - Laptop and Netbook 2 06-07-2009 11:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration