LinuxQuestions.org
Review your favorite Linux distribution.
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 05-09-2010, 04:52 PM   #16
rg3
Member
 
Registered: Jul 2007
Distribution: Fedora
Posts: 527

Rep: Reputation: Disabled

Quote:
Originally Posted by Richard Cranium View Post
(Frankly, I find the CLI for slackroll annoyingly complicated, but you can do a lot with it.)
I think that's my fault . In the next upgrade I'll remove the pb-search feature as the Package Browser is probably doomed by now, and I think I'm definitely reorganizing the help text so that it's actually useful by grouping commands and putting the important things first.
 
Old 05-10-2010, 01:25 AM   #17
saulgoode
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 288

Rep: Reputation: 155Reputation: 155
Quote:
Originally Posted by vigi View Post
I have two questions relating to this topic, I am hoping to get some help with.

1; grub will not charnload lilo or grub2 on my system.

I am using grub legacy as a boot manager on a separate 100MB ext2 partition; and booting slackware and ubuntu directly; however I have not been able to chainload lilo or grub2 ubuntu.The other peculiarity is Slackware will not boot with a uuid entry from my grub.
The slackware with lilo is on the /root ext4 fs sdb6 partition.
It is possible that the version of GRUB you are using is incapable of handling the Inode size used in your Slackware root partition (I assume you meant /dev/root and not /root).

I have never used GRUB to any great extent but I have heard that it is only able to handle filesystems with an Inode size of "128". The Slackware default Inode size is typically set to "256".

You can find out the Inode size of your /dev/root partition by running the following (edit: this may not work with ext4, but there should be a similar dumpfs command available):
'dumpe2fs /dev/root | grep 'Inode size:'

Last edited by saulgoode; 05-10-2010 at 01:31 AM.
 
Old 05-10-2010, 02:57 AM   #18
vigi
Member
 
Registered: May 2009
Location: australia
Distribution: slackware
Posts: 187

Rep: Reputation: 30
saulgoode, I tend to agree the problem is with grub as the common denominator. I may try a different version of grub, however as my system is working I will leave it for the moment.
 
Old 05-10-2010, 10:50 AM   #19
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841
If you can boot directly but you cannot chainload then it would likely have very little to do with the inode size...
 
Old 05-11-2010, 11:04 AM   #20
pg99
Member
 
Registered: May 2008
Location: UK
Distribution: Slackware
Posts: 73

Rep: Reputation: 18
Quote:
Originally Posted by Richard Cranium View Post
Of course, if you are using grub then you can interactively figure out what menu.lst changes you should make. I've lost track of the number of times that I've forgotten to run lilo or forgot to update the *bleeping* lilo.conf file. Even if I screw up changing menu.lst, I can still fix it via grub's interactive boot facility. Grub's great!
That is exactly why I use grub over lilo. If I mess up the mkinitrd, like I usually do, I can just go to the grub command-line, change the kernel to huge and have another go! No need to reach for the disks.
 
Old 05-11-2010, 01:11 PM   #21
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,069

Rep: Reputation: 160Reputation: 160
Quote:
Originally Posted by pg99 View Post
That is exactly why I use grub over lilo. If I mess up the mkinitrd, like I usually do, I can just go to the grub command-line, change the kernel to huge and have another go! No need to reach for the disks.
To me "always add a new entry in lilo.conf instead of changing the old entry" is easier to remember than the overkilling grub commands.

If you really need a filesystem driver with the boot loader, syslinux is an advanced tool.
 
Old 05-11-2010, 05:21 PM   #22
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,719

Rep: Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067Reputation: 2067
Quote:
Originally Posted by guanx View Post
To me "always add a new entry in lilo.conf instead of changing the old entry" is easier to remember than the overkilling grub commands.
Right. And you've NEVER forgot to upgrade lilo.conf. Good for you!

The rest of us (well, those who use GRUB) are more than happy to be able to boot their systems when they DO forget to update lilo.conf correctly.

I don't think that you've ever used GRUB or you would not make such an idiotic argument.
 
Old 05-11-2010, 10:20 PM   #23
vigi
Member
 
Registered: May 2009
Location: australia
Distribution: slackware
Posts: 187

Rep: Reputation: 30
Have tried lilo and see no problem with it as a loader, however as a boot manager I prefer grub.. it is more flexible and forgiving. I have had no trouble with legacy grub until ext4 and grub2 came on the scene. I think my present minor problems with respect to chainloading are just transitional compatibility problems until Grub2 takes over.
 
Old 05-12-2010, 03:04 AM   #24
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,069

Rep: Reputation: 160Reputation: 160
Quote:
Originally Posted by Richard Cranium View Post
Right. And you've NEVER forgot to upgrade lilo.conf. Good for you!
... // snip
I don't think that you've ever used GRUB or you would not make such an idiotic argument.
If you read carefully, you can find out that my opinion is: DO FORGETTING to update lilo.conf cannot harm. Even if you use GRUB, my suggestion "to leave the old kernel untouched until you can confirm the new kernel working" is common sense for serious Linux users.

BTW, For your information, I've been using lilo, ntldr, grub, and syslinux variants not only for testing. I also have heard some people complaining about grub on a USB flash disk loading the wrong stage2 sometimes. If things go wrong in the boot loader, and in a random way that you may not be aware of it in the beginning, then nothing is secure.
 
Old 05-12-2010, 04:43 PM   #25
pg99
Member
 
Registered: May 2008
Location: UK
Distribution: Slackware
Posts: 73

Rep: Reputation: 18
Quote:
Originally Posted by guanx View Post
To me "always add a new entry in lilo.conf instead of changing the old entry" is easier to remember than the overkilling grub commands.

If you really need a filesystem driver with the boot loader, syslinux is an advanced tool.
It's got nothing to do with adding or changing lines in lilo.conf or menu.lst. For example if the stock slackware kernel is updated then lilo.conf or menu.lst don't need to change because kernel is still vmlinuz, but I still need to make an initrd and if I mess that up I'm screwed with lilo but not with grub. That's why *I* like grub and will continue to use it. You can use whatever you like.
 
Old 05-12-2010, 05:10 PM   #26
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,069

Rep: Reputation: 160Reputation: 160
Quote:
Originally Posted by pg99 View Post
It's got nothing to do with adding or changing lines in lilo.conf or menu.lst. For example if the stock slackware kernel is updated then lilo.conf or menu.lst don't need to change because kernel is still vmlinuz, but I still need to make an initrd and if I mess that up I'm screwed with lilo but not with grub. That's why *I* like grub and will continue to use it. You can use whatever you like.
I do not intend to meddle in your choice. You can find that I started my post with "To me". Use of double-asterisk to emphasis yourself is unnecessary.

For general discussion, refer technically to my last two replies. What I would really like to know is: Is it true that "grub sometimes loads the wrong stage2"? I use syslinux for removable devices. If someone can confirm this grub-bug to be true, then it's a big security hole.
 
Old 05-14-2010, 09:21 AM   #27
barjac
LQ Newbie
 
Registered: May 2010
Location: Rossendale UK
Distribution: Mandriva
Posts: 15

Rep: Reputation: 1
Quote:
however I cannot understand why the chainloading of grub2-ubuntu or lilo-slackware does not work.
No, grub2 is a pain, but it can be done like this for Ubuntu:-

Code:
title Ubuntu 9.10
root (hd1,4)
kernel /boot/grub/core.img
I can not figure out yet how to get into Slakware 13 though.
Mainly I think because I can see no option in the installer to put the bootloader in the root.
I don't want to overwrite the MBR as I have many systems all of which chainload from one grub (legacy). I have never used lilo.
The installer allows the bootloader installation to be skipped (until later) but does not offer any options later. (full DVD install)
I can see that Slackware is going to be a challenge!

I am not new to Linux, just Slackware.
 
Old 05-14-2010, 05:38 PM   #28
vigi
Member
 
Registered: May 2009
Location: australia
Distribution: slackware
Posts: 187

Rep: Reputation: 30
Smile

[QUOTE=barjac;3968425]No, grub2 is a pain, but it can be done like this for Ubuntu:-

Code:
title Ubuntu 9.10
root (hd1,4)
kernel /boot/grub/core.img
-----------------------------
It works for ubuntu grub2 - thank you.

Regarding lilo, I find it easier to skip the lilo offers during installation and boot slackware with my grub legacy boot manager directly; then run liloconfig from within slackware to install lilo to the partition root.
 
Old 05-14-2010, 08:49 PM   #29
saulgoode
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 288

Rep: Reputation: 155Reputation: 155
Quote:
Originally Posted by barjac View Post
I can not figure out yet how to get into Slakware 13 though.
Mainly I think because I can see no option in the installer to put the bootloader in the root.
GRUB basically offers two options for booting Slackware: chainloading lilo or letting GRUB handle everything.

If you let GRUB handle the (Slackware) bootup then you need to manually modify your GRUB configuration to specify two things: the location of the Slackware kernel image (vmlinuz) and Slackware's root partition (so that the Slackware kernel can find init). The Slackware kernel image can be located anywhere as long as GRUB can find it (i.e., GRUB is able to mount the filesystem).

If you decide to chainload lilo then you just need to install lilo's loader to the Slackware partition's boot sector and chain load lilo within GRUB. You can install the lilo loader using liloconfig and choosing the "expert" option -- when you "Begin" a new lilo header the third question you are asked whether to install to the "root superblock", a floppy, or to the MBR. Choose the "root superblock" option (this is the boot sector of the Slackware partition). You will then have to manually modify your GRUB configuration to chainload the Slackware partition.

Regardless which method you use, you will need to manually modify your GRUB configuration because this is not performed by the default Slackware installation.



Note: if you want GRUB to present multiple Slackware kernels in its menu then you must let GRUB handle the Slackware bootup. If you chainload and want to have multiple kernels available, the user will need to be presented with a LILO menu so that the kernel image can be selected.
 
Old 05-15-2010, 05:16 AM   #30
barjac
LQ Newbie
 
Registered: May 2010
Location: Rossendale UK
Distribution: Mandriva
Posts: 15

Rep: Reputation: 1
Quote:
Originally Posted by saulgoode View Post
GRUB basically offers two options for booting Slackware: chainloading lilo or letting GRUB handle everything.
Thanks - that all makes sense.
I can boot to a text log-in using
Code:
title Slackware 13
root (hd1,9)
kernel /boot/vmlinuz-huge-2.6.29.6 root=/dev/sdb10 ro
If I log in as user and run startx it drops to a black screen for ever.
If I run liloconf as root it appears to be broken. The screen for selecting the root partition will not scroll down to reveal the partition I need.
I also notice some errors during boot about missing magic numbers in some file headers, so I am now suspecting the install media.
I did not find a checksum for the .iso, but as I used .torrent I was fairly sure it was OK.
If I try to boot with
Code:
title Slackware 13
root (hd1,9)
kernel /boot/vmlinuz
Which from your post should be enough, it ends in kernel panic.
I will try a re-install if I can find the md5 for the .iso.
 
  


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
[SOLVED] LILO fails when run from live CD after installing Slack (skipped LILO during setup) sysfce2 Linux - Newbie 7 08-04-2009 12:16 AM
Dual-boot Slack/Ubuntu-install slack over XP-help with weird partition layout & lilo? linus72 Slackware 2 05-23-2009 10:03 AM
WinXP/Slack (LILO) Casket Linux - Newbie 7 10-16-2005 07:42 AM
Lilo with 2 Windows+Slack? nivek7 Linux - Software 3 08-27-2004 04:37 PM
LILO, WinXP and Slack 9.0 - need help flame Slackware - Installation 4 02-08-2004 03:33 PM

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

All times are GMT -5. The time now is 03:03 AM.

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
Open Source Consulting | Domain Registration