Slackware 11 installs but won't boot - help!
tin...@isbd.co.uk
It has an Abit AB9 Pro motherboard, two 320Gb disks and an Intel Core
2 Duo processor. The disks are SATA and so is the CD/DVD drive. I
have turned on AHCI in the BIOS so the disks are seen as SCSI disks by
Slackware.
The installation proceeds and completes absolutely normally with no
problems at all. I am using the 2.6.18 kernel by selecting test.s at
the start of the installation.
When the installation finishes and it says "hit CTRL/ALT/DEL to start
the system" it doesn't start. I get the Lilo menu (with just a single
"Linux" entry) but when you hit enter or it times out absolutely
nothing happens, the screen goes blank and there is no disk activity
at all. The same happens if you try and boot after turning the system
on, Lilo menu appears, then nothing.
Is this something to do with selecting the test.s kernel? Do I need
some kernel parameters to actually run with this kernel? It all
worked perfectly without any parameters during installation though.
(The default 2.4.33 kernel doesn't seem to recognise my SATA disks by
the way)
--
Chris Green
Olive
First, you can boot your system from the CD. I would suggest to try to
boot with the huge2.6 kernel, so mention something like huge2.6 noinitrd
root=/dev/<your root device> (the exact command is mentioned in the
welcome message when you insert the CD); if you have been able to
install, your system will boot with the same kernel you used for
installation. Once the system is booted, you can install the kernel you
just used to boot the system (present in the kernel directory of the CD)
and don't forget to install the modules in /extra if you used a 2.6
kernel (I assume you know how to install a kernel: put it in /boot and
configure lilo accordingly). If you want to use another 2.6 kernel than
the huge2.6 one; you will have to make an initrd as documented in
/boot/README.initrd (alternatively, recompile your kernel with
everything you need to boot builtin).
Hope that it helps,
Olive
tin...@isbd.co.uk
> tin...@isbd.co.uk wrote:
> >
> > The installation proceeds and completes absolutely normally with no
> > problems at all. I am using the 2.6.18 kernel by selecting test.s at
> > the start of the installation.
> >
> > When the installation finishes and it says "hit CTRL/ALT/DEL to start
> > the system" it doesn't start. I get the Lilo menu (with just a single
> > "Linux" entry) but when you hit enter or it times out absolutely
> > nothing happens, the screen goes blank and there is no disk activity
> > at all. The same happens if you try and boot after turning the system
> > on, Lilo menu appears, then nothing.
> >
>
> boot with the huge2.6 kernel, so mention something like huge2.6 noinitrd
> root=/dev/<your root device> (the exact command is mentioned in the
> welcome message when you insert the CD); if you have been able to
> install, your system will boot with the same kernel you used for
> installation.
Well I *thought* I had installed the same kernel as was being used
during the installation (though I must admit the dialogue that asks
you which kernel you want to install is a little confusing so I might
have got it wrong).
> Once the system is booted, you can install the kernel you
> just used to boot the system (present in the kernel directory of the CD)
> and don't forget to install the modules in /extra if you used a 2.6
> kernel (I assume you know how to install a kernel: put it in /boot and
> configure lilo accordingly).
I'm OK with the lilo bit. However I'm wondering about the modules,
how does one know which modules are necessary? When a kernel is used
as the install kernel does it use modules and, if so, does it install
the modules it uses? As I said I installed using the 2.6.18 kernel so
would prefer to go with that, presumably I can find the corresponding
modules in /test.
> If you want to use another 2.6 kernel than
> the huge2.6 one; you will have to make an initrd as documented in
> /boot/README.initrd (alternatively, recompile your kernel with
> everything you need to boot builtin).
>
I will eventually be compiling a kernel as I want SMP support and I
don't think the 2.6.18 kernel has that.
> Hope that it helps,
>
Yes, it does, thanks very much. I'll hopefully be able to try some or
all of this out this evening.
--
Chris Green
Olive
For the modules you will have to install the modules packages which
contains all modules. With a little luck the hotplug will load the
modules necessary for your hardware automatically. If it does not you
will have to put the additional modules in /etc/rc.d/rc.modules (put
modprobe <your needed module> , one line per needed module) (at this
point you will have to google or read the documentation in
/usr/src/linux to know which modules you need). If your system load
automatically modules that cause problems; you will have to put them in
/etc/hotplug/blacklist.
There is a problem when your kernel need modules to access your drive or
root filesystem because the kernel need to be able to read your
filesystem in order to load modules. The solution is to boot with an
initrd (see man mkinitrd and /boot/README.initrd): basically lilo give
an initrd to the kernel containing the necessary modules. The kernel
boot into it load the necessary modules and then boot your root
filesystem. Another solution is to compile everything necessary to
access your root filesystem builtin so the kernel does not need modules
to boot. The huge26 kernel contains almost every driver builtin, so it
will boot everywhere but it is too big. Other 2.6 kernel contain only a
basic IDE driver for the hard disk and the ext2 filesystem.
Olive
Ralph Alvy
> Well I *thought* I had installed the same kernel as was being used
> during the installation (though I must admit the dialogue that asks
> you which kernel you want to install is a little confusing so I might
> have got it wrong).
That dialogue has been thoroughly confusing since the first time I installed
Slackware. I used the 2.6.18 kernel during installation, and when that
dialogue appeared, I chose the option to find the kernel on the CD again.
That worked fine.
tin...@isbd.co.uk
> > Once the system is booted, you can install the kernel you
> > just used to boot the system (present in the kernel directory of the CD)
> > and don't forget to install the modules in /extra if you used a 2.6
> > kernel (I assume you know how to install a kernel: put it in /boot and
> > configure lilo accordingly).
>
> I'm OK with the lilo bit. However I'm wondering about the modules,
> how does one know which modules are necessary? When a kernel is used
> as the install kernel does it use modules and, if so, does it install
> the modules it uses? As I said I installed using the 2.6.18 kernel so
> would prefer to go with that, presumably I can find the corresponding
> modules in /test.
>
> > If you want to use another 2.6 kernel than
> > the huge2.6 one; you will have to make an initrd as documented in
> > /boot/README.initrd (alternatively, recompile your kernel with
> > everything you need to boot builtin).
> >
> I will eventually be compiling a kernel as I want SMP support and I
> don't think the 2.6.18 kernel has that.
>
wrong during the 2.6.18 install but anyway what I just did was to
install the 2.6.17 kernel which went smoothly *and* booted OK
afterwards. Then I simply copied the 2.6.18 kernel from the CD to
/boot and added it to the lilo configuration and that boots OK too.
So all I need to do now is install the 2.6.18 kernel source and build
a kernel with networking (and rather less bloat) and I can then
actually get around to configuring my system.
Thanks for all the help.
--
Chris Green
Eef Hartman
> Well I *thought* I had installed the same kernel as was being used
> during the installation (though I must admit the dialogue that asks
> you which kernel you want to install is a little confusing so I might
> have got it wrong).
As far as I know with _any_ 2.6 kernel you have to install, BY HAND,
the corresponding "kernel-modules" package, before you can reboot.
Setup does NOT do that for you.
But I haven't tried it myself, yet (and probably won't, we normally
UPGRADE, do not do blank installs, so we've always already have GOT a
2.6 kernel to fall back on at reboot).
> would prefer to go with that, presumably I can find the corresponding
> modules in /test.
On the CD's, /testing-2.6.18 on Cd 4, and the modules package should
be called kernel-modules-2.6.<version>-i?86-*.tgz
> I will eventually be compiling a kernel as I want SMP support and I
> don't think the 2.6.18 kernel has that.
There is a 2.6.17 kernel with smp support in /extra (on the CD's: CD #2).
That one also needs "its own" modules package.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M....@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
tin...@isbd.co.uk
> tin...@isbd.co.uk wrote:
> > Well I *thought* I had installed the same kernel as was being used
> > during the installation (though I must admit the dialogue that asks
> > you which kernel you want to install is a little confusing so I might
> > have got it wrong).
>
> As far as I know with _any_ 2.6 kernel you have to install, BY HAND,
> the corresponding "kernel-modules" package, before you can reboot.
> Setup does NOT do that for you.
>
and it then booted OK from the hard disk. Similarly the test26.s
kernel also booted without having installed the "kernel-modules"
package.
I don't see why they'd need "kernel-modules" as they are both huge
(hence the name) kernels which have everything bar the kitchen sink
compiled into them.
> On the CD's, /testing-2.6.18 on Cd 4, and the modules package should
> be called kernel-modules-2.6.<version>-i?86-*.tgz
>
Yes, I've found that now (I hadn't originally downloaded the source
CDs) and have installed all the headers, modules and source for the
2.6.18 kernel.
--
Chris Green
Eef Hartman
> Yes, I've found that now (I hadn't originally downloaded the source
> CDs) and have installed all the headers, modules and source for the
> 2.6.18 kernel.
See other discussions about installing the kernel-headers (or the
README _in_ the same dir), in general, DON'T install them unless
you want to recompile glibc too. They are normally the "version
of the kernel headers the C library was compiled WITH", the kernel
itself has its OWN version of them in the kernel-source package.
The kernel-headers package is only to compile application software,
that is using the standard library calls to interface WITH the kernel.
The sources, of course, are only needed when you want to customize
the kernel itself, OR are installing third-party kernel drivers
(like NVidia) that will need them. Note that THOSE don't use the
kernel-headers, they get the ones from "the running kernel-version
sources" itself.
tin...@isbd.co.uk
> tin...@isbd.co.uk wrote:
> > Yes, I've found that now (I hadn't originally downloaded the source
> > CDs) and have installed all the headers, modules and source for the
> > 2.6.18 kernel.
>
> See other discussions about installing the kernel-headers (or the
> README _in_ the same dir), in general, DON'T install them unless
> you want to recompile glibc too. They are normally the "version
> of the kernel headers the C library was compiled WITH", the kernel
> itself has its OWN version of them in the kernel-source package.
> The kernel-headers package is only to compile application software,
> that is using the standard library calls to interface WITH the kernel.
>
clarified it somewhat for me, thanks.
> The sources, of course, are only needed when you want to customize
> the kernel itself, OR are installing third-party kernel drivers
> (like NVidia) that will need them. Note that THOSE don't use the
> kernel-headers, they get the ones from "the running kernel-version
> sources" itself.
This is what I will be doing as I have at least two things that need a
custom compiled kernel.
--
Chris Green
tin...@isbd.co.uk
> Eef Hartman <E.J.M....@math.tudelft.nl> wrote:
> > tin...@isbd.co.uk wrote:
> > > Yes, I've found that now (I hadn't originally downloaded the source
> > > CDs) and have installed all the headers, modules and source for the
> > > 2.6.18 kernel.
> >
> > See other discussions about installing the kernel-headers (or the
> > README _in_ the same dir), in general, DON'T install them unless
> > you want to recompile glibc too. They are normally the "version
> > of the kernel headers the C library was compiled WITH", the kernel
> > itself has its OWN version of them in the kernel-source package.
> > The kernel-headers package is only to compile application software,
> > that is using the standard library calls to interface WITH the kernel.
> >
> Yes, I have read the warning and was aware of the issue but you have
> clarified it somewhat for me, thanks.
>
to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
problems?
I can recompile kernels to my hearts content then in
/usr/src/linux/linux-2.6.18 but the 'outside' world will see what was
there before I installed any of the 2.6.18 kernel packages.
--
Chris Green
Eef Hartman
> If I leave (well restore actually) /usr/src/linux as a symbolic link
> to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
> problems?
No, the kernel-headers package installs in /usr/include/linux and
/usr/include/asm-i386 (which will linked to /usr/include/asm),
so will be available even if NO kernel sources at all have been installed.
The /usr/src/linux _link_ is just to provide a default "kernel source"
link for some (older) drivers (the newer ones use the link from
/lib/modules/<kernel version>/source (cq build), which is installed
by the kernel-modules package.
tin...@isbd.co.uk
> tin...@isbd.co.uk wrote:
> > If I leave (well restore actually) /usr/src/linux as a symbolic link
> > to /use/src/linux/linux-2.4.33 is that sufficient to prevent any
> > problems?
>
> No, the kernel-headers package installs in /usr/include/linux and
> /usr/include/asm-i386 (which will linked to /usr/include/asm),
> so will be available even if NO kernel sources at all have been installed.
>
re-install the 2.4.33 one.
> The /usr/src/linux _link_ is just to provide a default "kernel source"
> link for some (older) drivers (the newer ones use the link from
> /lib/modules/<kernel version>/source (cq build), which is installed
> by the kernel-modules package.
OK, thanks for all the info.
--
Chris Green
Eef Hartman
> Ah, so i really ought to uninstall the 2.6.18 headers package and
> re-install the 2.4.33 one.
Just "upgradepkg" it, using the 2.4.33 kernel-headers tgz file.
Essentially upgradepkg will replace any package with "another version" of
the same, so the real name should have been "replacepkg" <grin>.
>> The /usr/src/linux _link_ is just to provide a default "kernel source"
PS: it will normally point to "the last source" package you've installed
(you CAN install more than one of those:
lrwxrwxrwx 1 root root 14 2006-10-06 14:47 linux -> linux-2.6.16.7
drwxr-xr-x 15 root root 1024 2005-10-31 11:24 linux-2.4.31
drwxr-xr-x 20 root root 1024 2006-04-25 11:44 linux-2.6.16.7
drwxr-xr-x 20 root root 1024 2006-09-07 11:38 linux-2.6.17.8
on my own (10.2) system).
We've made a script that will set the link at each reboot to
"the source of the current bootup kernel", from which you can see
I'm currently running 2.6.16.7
The 2.6.17 one will probably be replaced with the one from Slack 11
but all of these are "custom" kernels, not the distributed binaries.
tin...@isbd.co.uk
> tin...@isbd.co.uk wrote:
> > Ah, so i really ought to uninstall the 2.6.18 headers package and
> > re-install the 2.4.33 one.
>
> Just "upgradepkg" it, using the 2.4.33 kernel-headers tgz file.
>
> Essentially upgradepkg will replace any package with "another version" of
> the same, so the real name should have been "replacepkg" <grin>.
>
--
Chris Green
Chick Tower
> But I haven't tried it myself, yet (and probably won't, we normally
> UPGRADE, do not do blank installs, so we've always already have GOT a
> 2.6 kernel to fall back on at reboot).
> We've made a script that will set the link at each reboot to "the
> source of the current bootup kernel", ....
Eef slipped a couple of times in this thread and used the royal "we".
Therefore, it should be apparent to all that Eef Hartman's alter ego is
none other than (drum roll, please)...Realto Margarino!
--
Chick Tower
For e-mail: aols . sent . towerboy AT xoxy . net
Glyn Millington
> In the past, Eef Hartman wrote:
>
>> But I haven't tried it myself, yet (and probably won't, we normally
>> UPGRADE, do not do blank installs, so we've always already have GOT a
>> 2.6 kernel to fall back on at reboot).
>
>> We've made a script that will set the link at each reboot to "the
>> source of the current bootup kernel", ....
>
> Eef slipped a couple of times in this thread and used the royal "we".
> Therefore, it should be apparent to all that Eef Hartman's alter ego is
> none other than (drum roll, please)...Realto Margarino!
We don't believe a word of it! We are impressed though - the next Da
Vinci Code is on da way....
cordially yours
Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.org/ The Official Source :-)
STFW http://groups.google.com/groups?hl=en&group=alt.os.linux.slackware
JFGI http://jfgi.us/
Eef Hartman
> Eef slipped a couple of times in this thread and used the royal "we".
> Therefore, it should be apparent to all that Eef Hartman's alter ego is
> none other than (drum roll, please)...Realto Margarino!
We, in this context, means "our group here at the university".
I'm not the only system manager, although I _am_ the only one
replying in this group.
And I most certainly object to being compared to rm, unlike that
idiot I do try to give usefull replies.....
notbob
> Eef slipped a couple of times in this thread and used the royal "we".
> Therefore, it should be apparent to all that Eef Hartman's alter ego is
> none other than (drum roll, please)...Realto Margarino!
Rat Dog Dick, you ain't.
nb
Michael Black
> Chick Tower <c.t...@deadspam.com> wrote:
>> Eef slipped a couple of times in this thread and used the royal "we".
>> Therefore, it should be apparent to all that Eef Hartman's alter ego is
>> none other than (drum roll, please)...Realto Margarino!
>
> We, in this context, means "our group here at the university".
> I'm not the only system manager, although I _am_ the only one
> replying in this group.
>
> And I most certainly object to being compared to rm, unlike that
> idiot I do try to give usefull replies.....
That's the problem with witch hunts, in their attempt to track
down those they perceive as a danger, the people doing it often
take down the innocent.
Michael
Charles Shannon Hendrix
> That's the problem with witch hunts, in their attempt to track
> down those they perceive as a danger, the people doing it often
> take down the innocent.
Witch hunts can be good or bad depending on how pursued, but the idiots
that cause them, like rm and all his aliases, are the real problem.
It's too bad you have to have a jackass like that in nearly every group.
--
shannon "AT" widomaker.com -- [Don't you see that the whole aim of Newspeak
is to narrow the range of thought? In the end we shall make thoughtcrime
literally impossible, because there will be no words in which to express
it. -- 1984, George Orwell ]]
Realto Margarino
> And I most certainly object to being compared to rm, unlike that
> idiot I do try to give usefull replies.....
Where did they find you? And the word is taught as "useful" at the
Universities from which I graduated.
cordially, as always,
rm
Realto Margarino
> Witch hunts can be good or bad depending on how pursued, but the
> idiots that cause them, like rm and all his aliases, are the real
> problem.
All his aliases? What on earth are you talking about?
> It's too bad you have to have a jackass like that in nearly every
> group.
And we've got you. We're thrilled. Now go back to sleep until you
have another opportunity to call somebody some names.
cordially, as always,
rm
+Witch Hunter+
Michael Black wrote:
>That's the problem with witch hunts, in their attempt to track
>down those they perceive as a danger, the people doing it often
>take down the innocent.
The person who confused Eef Hartman with Realto Margarino (Chick Tower)
was wrong; he had no evidence. That doesn't make those of us who *do*
have solid evidence wrong as well.
From WHOIS:
justlinux.ca
Just Linux
The education of philistines everywhere.
Realto Margarino
964 College Street
Toronto ON N3S 2G5 Canada
416-538-2192
dran...@hotmail.com
For those who are wondering who the "cordially, as always" troll
is, here is the evidence, step by step. He made the error of
starting out using his real identity and then changing things
slowly over time in order to hide -- allowing us to track him
through the changes.
Here is Roger Maynard's very first post.
http://groups.google.com/group/rec.sport.baseball/msg/07bfda4d65110fe6?dmode=source
Note the sig: cordially, as always, rm
Note the server: ramsey.cs.laurentian.ca
Note the name: Roger Maynard
Note the email address: may...@ramsey.cs.laurentian.ca
Here is his last post before losing his Laurentian University account:
http://groups.google.com/group/rec.sport.baseball/msg/bb70011aae694ebc?dmode=source
Note the server: ramsey.cs.laurentian.ca
Note the name: Roger Maynard
Note the email address: may...@ramsey.cs.laurentian.ca
And here he is with his brand new interlog.com account,
http://groups.google.com/group/rec.sport.hockey/msg/a23d985ca7191843?dmode=source
Note the new server: gold.interlog.com
Note the new email address: r...@interlog.com
Note the same old name: Roger Maynard
Note the same old content: the same flames to the same newsgroups,
continueing the same conversations using the same name.
Here is where Roger Maynard discovers morphing to avoid killfiles.
http://groups.google.com/group/rec.sport.baseball/msg/9d632c4604cd905a?dmode=source
http://groups.google.com/group/rec.sport.baseball/msg/fb0553c525315834?dmode=source
http://groups.google.com/group/alt.smokers/msg/230faedfe0295460?dmode=source
http://groups.google.com/group/alt.smokers/msg/62159002e085978a?dmode=source
http://groups.google.com/group/alt.smokers/msg/ba7814965bcccbf3?dmode=source
http://groups.google.com/group/rec.sport.hockey/msg/3dd217e391807f98?dmode=source
(In that last one he introduces his "Ronald Matthews" morph that he uses
to this day)
Note the same old server: gold.interlog.com
Note the same old sig: cordially, as always, rm
Note the same old content: the same flames to the same newsgroups,
continueing the same conversations using the same name.
Here he starts his "use the initials R and M" morphs:
http://groups.google.com/group/rec.sport.hockey/msg/8b81086071c13ec2?dmode=source
http://groups.google.com/group/rec.sport.hockey/msg/e57a5d6ab4b48506?dmode=source
http://groups.google.com/group/rec.sport.hockey/msg/7231a0af1557a403?dmode=source
http://groups.google.com/group/alt.smokers/msg/65fabfdcd2b41fd5?dmode=source
Note the same old server: gold.interlog.com
Note the same old sig: cordially, as always, rm
Note the same old content: the same flames to the same newsgroups,
continueing the same conversations using the same name.
And here he introduces his "Realto Margarino" morph:
http://groups.google.com/group/alt.smokers/msg/56f4171f92d05fa6?dmode=source
Note the same old server: gold.interlog.com
So we see a series of posts from the same account at the same ISP,
starting with the same Roger Maynard name and sig that was used at
Laurentian University, morphing through some random names, settling
down to names such as Ronald Matthews, Ronald McDonald, Rasmussen
Milos and Rosie Matsushita, then we see Realto Margarino - all with
the same email address, same path and same NNTP-Posting-Host.
In this series of posts we see the same "cordially, as always, rm"
sig, the same phrasing, the same newsgroups and the same enemies.
And here we are ten years later watching him follow the exact same
pattern with slightly improved morphing skills, and still using
Ronald Matthews and Realto Margarino as his favorite morphs.
Roger Maynard has been making as many people as possible miserable
for over ten years, devoting thousands of hours to annoying people
who never did him a bit of harm.
Google food:
Roger Maynard cordially, as always, rm troll Realto Margarino Ronald
Matthews Roger Maynard cordially, as always, rm troll Realto Margarino
Ronald Matthews Roger Maynard cordially, as always, rm troll Realto
Margarino Ronald Matthews Roger Maynard cordially, as always, rm troll
Realto Margarino Ronald Matthews Roger Maynard cordially, as always,
rm troll Realto Margarino Ronald Matthews Roger Maynard cordially, as
always, rm troll Realto Margarino Ronald Matthews Roger Maynard cordially,
as always, rm troll Realto Margarino Ronald Matthews Roger Maynard
cordially, as always, rm troll Realto Margarino Ronald Matthews Roger
Maynard cordially, as always, rm troll Realto Margarino Ronald Matthews