LinuxQuestions.org
Visit Jeremy's Blog.
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 11-28-2009, 06:55 PM   #1
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Rep: Reputation: 16
Cannot boot slackware13, even with the slackware13 created flashdrive


Greetings, all!
My two problems with "slackware 13,"*
stated as simply as possible, are as follows: After the succesful install of slackware13 to my external usb drive (/dev/sdb), I could not: 1) boot said Slackware13 installation with the Slackware13 installation DVD due to kernel panic issues. 2) I cannot boot the system with the usb flashdrive that was created with the Slackware13 installation DVD due to kernel panic issues.
>
Problem origin:
I wanted more of a challenge than the more popular distros, so I installed slackware13 as described in the next few sentences.
I connected a spare external USB drive to my computer, which became /dev/sdb. I partitioned sdb and then installed slackware13 onto it. My reading of slackware13 indicated that I would have to boot into slackware13 first, run the grub config program which would create a /boot/grub/menu.lst. This was and is my plan, but alas, since I cannot boot slackware13, (not even with the flashdrive created by slackware13) I am at a standstill with slackware13.

The goal
Use grub to boot slackware from a connected external USB drive (/dev/sdb). Append grub's menu.lst from /dev/sda to the menu.lst of /dev/sdb, followed by the setup of grub on sdb. Since grub is already installed on /dev/sda, all systems on either /dev/sda or /dev/sdb (the external USB drive is sdb) would then boot sans any problems. This works with everything be it Ubuntu, Suse or Tinycore.

Troubleshooting completed thus far:
--skimmed more than 10 pages of this forum and read several
>
--visited Google
>
--set the flashdrive syslinux config from root=dev/sdb5 to /dev/sdc5, which failed

--set the flashdrive syslinux config from root=/dev/sdb5 to root=UUID=12e44-... which failed
Visited the syslinux wiki, which failed also.
>
--attempted to chainload syslinux after copying it to a bootable partition.
>
--Attempted to make a LILO boot floppy
>
--Attempted a simple install of LILO from the DVD, no luck with the world's most difficult bootloader.
>
Attempted to install LILO to the root of the boot partion, which failed.
>
Wiped the disk, sdb, and then created a multiple partition scheme where sdb1 (a bootable primary partition) was made root. Attempted to install LILO to the the root of sdb1 as per the installer's directions. This failed too.

Other questions:
Does slackware give one the option of where to install lilo if I had to use it?
Would the installation of Lilo on /dev/sdb adversely affect the grub install on /dev/sda?
If absolutely necessary, is it common or possible to successfully chainload lilo using grub?
can I chainload grub with lilo?
Thanks for any help

Last edited by yanfaun; 12-14-2009 at 09:01 PM.
 
Old 11-29-2009, 09:02 AM   #2
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
Some versions of grub will not boot a slackware formatted partition. How did you format the drive? If you formatted it during the install of slackware 13, try installing lilo to the root partition of slackware during the installation and chainload from grub, or try formatting from the distro that you grub is in first, then select no to format the drive during the slackware install, since it is already formated, and boot directly from grub.
 
Old 11-29-2009, 09:55 AM   #3
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 421

Rep: Reputation: 58
To add to what colorpurple wrote, Slackware 13 defaults to ext4 when setting up the disk. From what I read, you need grub2 to support ext4. Sounds like you might have grub/ext4 issue.
 
Old 11-29-2009, 12:14 PM   #4
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by colorpurple21859 View Post
Some versions of grub will not boot a slackware formatted partition. How did you format the drive?...or try formatting from the distro that you grub is in first, then select no to format the drive during the slackware install,

Thanks for the reply!

I formatted everything with a different distro's gparted. I've boot ext4 with legacy grub on other distros. I formatted everything as you suggested before posting because it was easier than using cfdisk, which I use as a last resort.

Quote:
Originally Posted by colorpurple21859 View Post
...try installing lilo to the root partition of slackware during the installation and chainload from grub,
I'd need help installing LILO. It is way alien to me and unintelligible to me even after I read the readme stuff found in the DVD's root file. It fails to install to root, floppy and I will not put LILO on a MBR.

I think I need to learn the grub config & build initrd stuff first because at least that is on my level if I could find it though. Any ideals?
thanks again.
 
Old 11-29-2009, 12:23 PM   #5
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by Chuck56 View Post
To add to what colorpurple wrote, Slackware 13 defaults to ext4 when setting up the disk. From what I read, you need grub2 to support ext4. Sounds like you might have grub/ext4 issue.
Thanks for responding
Oh I wish it were a grub issue then it would be intelligible to me, which is not to say I am a grub expert. Legacy grub has never given me ext4 trouble. Legacy grub boots everything.

My intended course of action (unless advised otherwise)is to:
1) setup everything as ext3
2) learn to setup the grubconfig stuff in Slackware.
3) Run grubconfig install grub and append a menu.lst
>
Does anyone know the location of the grubconfig help file should I fail to find it?
>
Apparently, there is a way to get a shell immediately after installation. Is it ALT-F1
>
well everybody, it's time to finish laundry,reformat some partitions to ext3, copy some help files and reinstall a distro. I should be off line for a couple.
>
Again, thanks for the replies to everybody. I'll all informed of my progress.

Last edited by yanfaun; 11-29-2009 at 12:26 PM.
 
Old 11-29-2009, 02:53 PM   #6
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
slackware's standard install doesn't come with grub installed only lilo, however slackware's grub package is located in /extra/grub on slackware mirrors if you want to install it.
 
Old 11-29-2009, 03:35 PM   #7
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware 12.1, slackware64-current
Posts: 255

Rep: Reputation: 43
I don't get it, why not just add slackware boot entries into menu.lst of already installed grub in /dev/sda - if, of course, there is another distro already installed. Slackware installation DVD can also be used to boot into an installed system - brief how-to is on the first screen of the installer.

(Posted by an unexperienced user)
 
Old 11-29-2009, 05:04 PM   #8
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by colorpurple21859 View Post
slackware's standard install doesn't come with grub installed only lilo, however slackware's grub package is located in /extra/grub on slackware mirrors if you want to install it.


Quote:
Originally Posted by yanfaun View Post
Greetings, all!
My two problems with "slackware 13,"*
stated as simply as possible, are as follows: After the succesful install of slackware13 to my external usb drive (/dev/sdb), I could not: 1) boot the system with the DVD. 2) I cannot boot the system with the usb flashdrive that was created with the Slackware 13 installer.

Thanks for any help
Thanks, color21859[
However, as you can see from the first three lines of my post, which appear as a quote above this sentence, installation is impossible. One must boot before installing things.

To reiterate, slackware13 has never been bootable. LILO now (finally)installs to the root of sdb1, which is bootable partition. However, neither the instllation DVD, nor the syslinux flashdrive (created with Slackware, I might add) will boot this system. Everybody keeps responding with ways to install something when the system has never been bootable be it reiser, ext4 or ext3.
>
I've taken multi-booting and grub for granted until now. I've never had so many problems doing nothing. The exasperatingly incomplete documentation on the DVD is the reason.
>
Thanks, anyway

Quote:
Originally Posted by veeall View Post
I don't get it, why not just add slackware boot entries into menu.lst of already installed grub in /dev/sda - if, of course, there is another distro already installed. Slackware installation DVD can also be used to boot into an installed system - brief how-to is on the first screen of the installer.

(Posted by an unexperienced user)
Veeall
Greetings,
The two-part answer to your question is as follows: 1) It is that simple in distros other than slackware. Were it that simple of a task in slackware, there would not be so many post Google concerning grub and Slackware. 2) Please see the first three lines this post, which I believed you missed despite the 3" bold font that preceded them. For your convenience, they appear at the top of this reply too. We all miss things sometimes.

To any who would post:
Please understand that I need to make an installation of slackware 13 (currently installed on an external usb drive) bootable.
I'd prefer grub, but I'd settle for LILO doing it's job.
Problems:
1) The system claims that LILO was installed to the bootable superblock, yet the system does not boot
2)The bootable syslinux flashdrive, created by Slackware13 fails to function, exiting with err=1 invalid compression.
3) The DVD is incapable of booting hugemap or the similarly named kernel
4) Installing LILO to a usb floppy disk always fails.
>
thanks again for the responses.

Last edited by yanfaun; 11-29-2009 at 05:36 PM. Reason: Clarity
 
Old 11-29-2009, 06:20 PM   #9
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
When you chainload from grub to lilo it doesn't work or do you get to the lilo prompt and it dosen't boot slackware?
 
Old 11-29-2009, 06:51 PM   #10
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by colorpurple21859 View Post
When you chainload from grub to lilo it doesn't work or do you get to the lilo prompt and it dosen't boot slackware?
No, you see, LILO does not function, period. It does not boot, period. Nothing boots. For me to consider chainloading, LILO would have to boot slackware. It does not, period.
Since the install of LILO returned no errors, I can only assume that it installed successfully. I think a prompt indicated as much. I would successfully chainload if LILO ever functioned. Dido for the syslinux flashdrive & booting from install DVD
Thanks
again
 
Old 11-29-2009, 07:28 PM   #11
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
so neither one of these grub entries work:
to chainload:
rootnoverify (hd1,0) #or maybe (hd1)
chainloader +1
or directly from grub
root (hd1,1)
kernel /boot/vmlinuz root=/dev/sdb1 #or maybe root=/dev/hdb1

Last edited by colorpurple21859; 11-29-2009 at 07:37 PM.
 
Old 11-29-2009, 07:36 PM   #12
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by colorpurple21859 View Post
so neither one of these grub entries work:
to chainload:
rootnoverify (hd1,0) #or maybe (hd0)
chainloader +1
or directly from grub
root (hd1,1)
kernel /boot/vmlinuz root=/dev/sda1 #or maybe root=/dev/hda1
There would be no point in chainloading that which cannot boot on its own. Remember that LILO does not function despite the fact that is installed.
 
Old 11-29-2009, 07:58 PM   #13
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,344

Rep: Reputation: 184Reputation: 184
on the system you have on your internal harddrive mount the slackware partition and copy /boot/vmlinuz-huge-smp-2.6.?-smp from the slackware partition to the /boot of the system on your internel hardrive. Point your grub to the file and set the /dev/root of the kernel line to the external harddrive.
 
Old 11-29-2009, 10:39 PM   #14
yanfaun
Member
 
Registered: Nov 2009
Distribution: Arch Linux
Posts: 123

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by colorpurple21859 View Post
on the system you have on your internal harddrive mount the slackware partition and copy /boot/vmlinuz-huge-smp-2.6.?-smp from the slackware partition to the /boot of the system on your internel hardrive. Point your grub to the file and set the /dev/root of the kernel line to the external harddrive.
I'll give this a shot tomorrow then report back although I have misgivings.
My BIOS (excluding Slackware & this post) has consistently booted sdb, which is an external USB hard drive, be it tinycore, BSD or anything in between.
Thanks again
 
Old 11-30-2009, 05:35 AM   #15
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware 12.1, slackware64-current
Posts: 255

Rep: Reputation: 43
Code:
Were it that simple of a task in slackware, there would not be so many post Google concerning grub and Slackware.
My scenario has always been like that:
I have two slackware versions on different partitions, when i install new version i do not install lilo nor grub instead i'm going to populate my existing menu.lst with new boot entries. I guessed this to be simplest workaround to your problem also if this another grub is capable of booting an ext4 partition.

I can't see why 'booting with slack dvd' method doesn't work(?).
 
  


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
cant install slackware13.0 lemon09 Slackware 23 11-27-2009 10:54 AM
vmware slackware13 guest with lvm root -> no boot :-( cosmonate Slackware 2 11-17-2009 06:04 AM
[SOLVED] Slackware13 64, Virtualbox, USB (again) Domine Slackware 27 11-15-2009 01:17 AM
DHCP doesn't work on slackware13.0 zyli2006 Slackware 26 09-11-2009 11:38 PM
[SOLVED] Slackware13 permissions problem alexiy Slackware 4 09-04-2009 04:49 AM


All times are GMT -5. The time now is 09:32 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