Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use
From: tinnews on 11 Oct 2006 04:10
I'm trying to install Slackware 11 on an 'empty' new system.
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
From: Olive on 11 Oct 2006 08:44
tinnews(a)isbd.co.uk wrote:
> I'm trying to install Slackware 11 on an 'empty' new system.
> 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)
>
>


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


From: tinnews on 11 Oct 2006 09:14
Olive <oesser(a)noemail.org> wrote:
> tinnews(a)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.
> >
>
> 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.

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
From: Olive on 11 Oct 2006 10:06
tinnews(a)isbd.co.uk wrote:
> Olive <oesser(a)noemail.org> wrote:
>> tinnews(a)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.
>>>
>> 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.
>
> 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.

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
From: Ralph Alvy on 11 Oct 2006 11:22
tinnews(a)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).

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.
 |  Next  |  Last
Pages: 1 2 3
Prev: gtk-gnutella
Next: Slack 11 'dnsmasq: failed to create listening socket: Address already in use