LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 09-05-2012, 03:00 PM   #16
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,424
Blog Entries: 2

Rep: Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996Reputation: 3996

Quote:
Originally Posted by arubin View Post
Well the nvidea driver install failed. Couldnt find the file.
Sorry, but we aren't mind readers. To help you we need to know what exactly you have done and which exact error message(s) you got.
 
Old 09-05-2012, 03:20 PM   #17
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
Sorry when I tried to install the nvidea-driver from sbopkg, sbopkg could not find the nvidea bz2 file it was looking for. I the tried doing it manually by running the NVIDIA installer downloaded from the Nvidea site and that worked.

Alan
 
Old 09-05-2012, 03:22 PM   #18
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Have you tried simply doing:

Code:
grub-mkconfig -o /boot/grub/grub.cfg
You may need to rename your initrd or patched /etc/grub.d/10_linux to find it.
 
1 members found this post helpful.
Old 09-05-2012, 04:04 PM   #19
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
Thanks. That does give me a grub menu but the menu will not boot. It stalls at mounting /dev/sda2

I presume grub.cfg needs editing. It does not look right. Initrd is being loaded for huge (perhaps that does not matter) but what about insmod est2? I am running on ext4.

Quote:
menuentry 'Slackware-13.37.0 GNU/Linux, with Linux 2.6.37.6 huge' --class slackware-13.37.0 --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set=root 61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6
echo 'Loading Linux 2.6.37.6 ...'
linux /boot/vmlinuz-huge-2.6.37.6 root=UUID=61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6 ro
echo 'Loading initial ramdisk ...'
### initrd /boot/initrd-2.6.37.6
}
menuentry 'Slackware-13.37.0 GNU/Linux, with Linux 2.6.37.6 (recovery mode)' --class slackware-13.37.0 --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set=root 61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6
echo 'Loading Linux 2.6.37.6 ...'
linux /boot/vmlinuz-huge-2.6.37.6 root=UUID=61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-2.6.37.6
}
menuentry 'Slackware-13.37.0 GNU/Linux, with Linux 2.6.37.6' --class slackware-13.37.0 --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set=root 61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6
echo 'Loading Linux 2.6.37.6 ...'
linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6 ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-2.6.37.6
}
menuentry 'Slackware-13.37.0 GNU/Linux, with Linux 2.6.37.6 (recovery mode)' --class slackware-13.37.0 --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set=root 61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6
echo 'Loading Linux 2.6.37.6 ...'
linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=61c5fbf6-4a4e-42dd-a6f0-f566e4900fe6 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-2.6.37.6
}

Last edited by arubin; 09-05-2012 at 04:09 PM.
 
Old 09-05-2012, 04:32 PM   #20
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
Sorry. Ignore the above. I was an idiot and had created an initrd for ext3 instead of ext4.

So I now have a functioning system and my initial question is solved.

Thanks everyone.

Last edited by arubin; 09-06-2012 at 01:05 AM.
 
Old 09-06-2012, 12:28 AM   #21
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by arubin View Post
created an ext3 for ext3 instead of ext4.
Did you mean "created an initrd for ext3 instead of ext4"?

As a side note for anyone else needing to install on a GPT/UEFI system I ran a quick test last night and indeed it seems you can use the EFI capable install CD/DVD of another distro to bootstrap the Slackware installer, as I hypothesized earlier. Before I went to bed last night I setup VirtualBox to simulate an EFI system (there is an option to do this) and then did the following:

1. Booted from an openSUSE 12.2 x86_64 install DVD (which I already had because it just came out and I have been meaning to test it )
2. Switched to a virtual terminal
3. Brought up the network
4. Used wget to fetch the initrd.img from the slackware64-current/isolinux directory of a nearby mirror
5. Unpacked this into a newly created directory (using zcat and cpio)
6. Chrooted into that directory (after first using mount to bind /dev, /sys and /proc from the host system and copying over /etc/resolv.conf)
7. Setup the $PATH and other variables needed to run the installer (by sourcing the chooted system's profile, i.e. ". /etc/profile")
8. Partitioned with gdisk
9. Started Slackware's setup script and performed a network install using the nearby mirror

Since it got late I stopped there but so far so good. My intention tonight would be to try finishing this off with the following steps:

10. Exit the install chroot and then chroot into Slackware
11. Fetch, compile and install Grub2 (and dependencies), then configure it
12. Reboot into Slackware 14.0RC4

Whilst I have yet to do steps 10-11, I don't foresee any major obstacles, since I already did the seemingly 'hard' parts. In summary, the two things that complicate install of Slackware on GPT/EFI are the lack of official EFI-capable install media and boot loader. The provided setup tools and kernel support GPT/EFI.

P.S. I tried it this way to see what was possible. However a better/neater way would be to do what rwebber did and make your own EFI-capable Slackware install media (copy the contents of the Slackware install DVD [or USB], create a new "efi/boot" directory and add to this the elilo.efi program and an appropriately configured elilo.conf, pointing at the huge kernel+initrd from the install media).

Last edited by ruario; 09-06-2012 at 03:32 AM. Reason: Clarified my postscript.
 
Old 09-06-2012, 03:14 AM   #22
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
Quote:
Did you mean "created an initrd for ext3 instead of ext4"?
Yes of course. In all the hassle of re-booting and tweaking I end up writing nonsense.

I will try and summarise what I did in a few days for the list but I will be away from my home PC for a few days. My next problem is very poor and intermittent ethernet connectivity which I suspect is a driver issue (see thread below).
 
Old 09-11-2012, 02:20 AM   #23
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by ruario View Post
Since it got late I stopped there but so far so good. My intention tonight would be to try finishing this off with the following steps:

10. Exit the install chroot and then chroot into Slackware
11. Fetch, compile and install Grub2 (and dependencies), then configure it
12. Reboot into Slackware 14.0RC4
Ok, it took a few nights before I had the time to finish this off but last night I had a spare moment to give it a go. However rather than setup Grub2, I decided to use Elilo, since it was less work then fetching and compiling Grub2 (also I hadn't tried Elilo yet and wanted to give it a try).

I mounted and switched into the the UEFI System Partition (a FAT32 filesystem you have to create during install, if not already present. You just need to make it big enough to hold your kernel(s) and associated files. Use gdisk to create it with type code EF00 and format with mkdosfs). There I created the directory structure ./EFI/BOOT and placed three files in it. Firstly an elilo.conf that looked like this:

Code:
prompt
timeout=50
default=huge

image=vmlinuz-huge-3.2.28
  label=huge
  read-only
  root=/dev/sda2
(Note: I have the UEFI System Partition as the first partition on the disk, hence root is on /dev/sda2)

Then I copied over vmlinuz-huge-3.2.28 alongside elilo.conf. Finally I downloaded elilo-3.14-all.tar.gz, extracted elilo-3.14-x86_64.efi and moved it into the UEFI System Partition next to the other two files but renamed to BOOTX64.EFI (./EFI/BOOT/BOOTX64.EFI is the name and path of the "default" bootloader on x86_64 UEFI System Partitions).

Upon reboot, Slackware started up. I then made an appropriate initrd.gz and copied this, along with vmlinuz-generic-3.2.28 over to the UEFI System Partition as well (in the same directory as the other two files). Next I tweaked the elilo.conf to look like this:

Code:
prompt
timeout=50
default=generic

image=vmlinuz-generic-3.2.28
  label=generic
  initrd=initrd.gz
  read-only
  root=/dev/sda2

image=vmlinuz-huge-3.2.28
  label=huge
  read-only
  root=/dev/sda2
The next reboot, brought Slackware up with the Generic kernel instead. Done!

P.S. Anyone else wanting to test all of this can use VirtualBox if you don't have an EFI-based machine. There is an option using EFI for booting rather than BIOS in the guest configuration.
 
Old 09-11-2012, 02:43 AM   #24
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
As a further side note, yet another way to install Slackware on EFI hardware would be to do the following:

1. Boot with another distro's EFI-capable install media
2. Do all the partitioning and formatting of your hard disk (including creating the UEFI System Partition if needed)
3. Mount the UEFI System Partition
4. On the UEFI System Partition, under the ./EFI/BOOT/ directory, copy over elilo-3.14-x86_64.efi (renamed to BOOTX64.EFI), bzImage and initrd.img.
5. In the same directory create an elilo.conf that looks like this:

Code:
prompt
timeout=50
default=install

image=bzImage
  label=install
  initrd=initrd.img
  append="load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s"
6. Reboot into the Slackware install environment from your hard disk
7. Unless you want to do an network install, insert a Slackware64 install DVD (this will be found later by the setup script)
8. Perform the install with two small alternations: don't format the UEFI System Partition; don't do the automatic lilo configuration.
9. Before rebooting, chroot into the new install, and make an initrd.gz.
10. Copy over vmlinuz-huge-3.2.28, vmlinuz-generic-3.2.28 and the initrd.gz into the ./EFI/BOOT/ directory on the UEFI System Partition.
11. Change the elilo.conf to something like the following (adjusting the root= values to match your own configuration:

Code:
prompt
timeout=50
default=generic

image=vmlinuz-generic-3.2.28
  label=generic
  initrd=initrd.gz
  read-only
  root=/dev/sda2

image=vmlinuz-huge-3.2.28
  label=huge
  read-only
  root=/dev/sda2

image=bzImage
  label=install
  initrd=initrd.img
  append="load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s"
12. Reboot into Slackware.

Last edited by ruario; 09-11-2012 at 02:57 AM. Reason: fixed broken link
 
Old 09-11-2012, 02:53 AM   #25
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
The following are great sources of information on booting Linux on UEFI-based systems:

Archwiki's Unified Extensible Firmware Interface
Archwiki's UEFI Bootloaders
Rod Smith's Managing EFI Boot Loaders for Linux
 
Old 09-11-2012, 03:34 AM   #26
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
The easiest way to make your own Slackware EFI-capable install media would be to create a USB boot disk. Partitioning it with a GPT partitioning scheme and include a UEFI System Partition (FAT32 filesystem, created with gdisk, using type code EF00, at least 50Mb and formatted with mkdosfs). Add a ./EFI/BOOT/ directory structure to this partition, into which place BOOTX64.EFI (extract elilo-3.14-x86_64.efi from elilo-3.14-all.tar.gz and rename it), bzImage, initrd.img and an elilo.conf that looks like this:

Code:
prompt
timeout=50
default=install

image=bzImage
  label=install
  initrd=initrd.img
  append="load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 SLACK_KERNEL=huge.s"
With this disk you should be able to boot into the Slackware install environment.

Last edited by ruario; 09-11-2012 at 04:45 AM.
 
Old 09-11-2012, 03:53 AM   #27
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
@arubin: Since you got this working and there are various options in this thread, you might want to mark the thread as solved. It will help other people searching for a solution to this.
 
Old 09-11-2012, 05:20 AM   #28
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
ruario - I marked this solved last week.
 
Old 09-11-2012, 05:33 AM   #29
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,806

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by arubin View Post
ruario - I marked this solved last week.
opps! Shame on me!
 
Old 09-11-2012, 05:58 AM   #30
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
My summary of how got my system going.

My PC has

sda SSD 120GB
sdb hard drive 1TB

I had originally partitioned the disks using Windows
to

sda1 ready for slackware14
sda2 for slackware 13.37
sda3 data

sdb1 Windows Boot UEFI
sdb2 small Windows hidden partition
sdb3 main Windows installation
sdb4 swap
sdb5 /var
sdb6 /home
sdb7 /shared windows Linux data

I prefered to prepare the original partition scheme with Windows because I believe that Windows positions the partitions correctly for SSDs without any hassle.

I installed Slackware 13.37 to sda2. The first time I attempted the installation I tried LILO. This was a mistake. LILO froze. I did the installation again omitting LILO.

At this stage I could only boot into Slackware by using the installation DVD or USB.

I was advised that I needed a small FAT partition on sda for GRUB2. I found that there were 3MB spare at the end of sda. So sda4 was partitioned and labelled EF00.

I created a Grub2 installation package on my old PC using the slackbuild and installed that by booting with the DVD and chrooting into my new installation.
Quote:
grub-install /dev/sda
Created initrd.gz as advised in the README and named that initrd-2.6.37.6.gz as advised by ruario

Then

Quote:
grub-mkconfig -o /boot/grub/grub.cfg
Configure the UEFI/BIOS to boot off the SSD.

Can then boot straight into GRUB2 then slackware
 
  


Reply


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
Slackware and Grub2 - getting a UEFI mb running linuxbird Slackware 16 12-13-2012 08:40 AM
Help Creating UEFI A MENU For My Bootable (BIOS/UEFI) CDROM ssenuta Linux - Hardware 0 08-27-2012 09:11 PM
[SOLVED] Boot Loader Problem on Slackware64 13.37 (UEFI & GPT disk) ack_iix Slackware 22 07-12-2012 06:02 PM
[SOLVED] Slackware 13.37 - gdisk choices, MBR, GPT or Blank GPT CFet Slackware - Installation 3 04-01-2011 04:46 PM
[SOLVED] Installing Slackware with GPT partition table Skaperen Slackware 15 02-23-2011 01:37 PM


All times are GMT -5. The time now is 10:40 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration