SEO

I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
11 DVD, and at the boot prompt I selected "huge26.s". The
installation works fine on my 360G SATA disk, but after the install my
kernel is 2.4.33.3. At the very end of the installation, it asked
which kernel to use, and I selected the default since (from what I
understood) the default kernel was the one I booted (huge26.s) and the
one I want.
I searched Usenet a bit, and even found some posts mentioning
"installing modules afterwards".

This post:

http://groups.google.com/group/alt.o...d5e9e5228a04d/

Mentions installing more packages from the DVD:

kernel-generic-2.6.17.13-i486-1.tgz
kernel-modules-2.6.17.13-i486-1.tgz
kernel-source-2.6.17.13-noarch-1.tgz

Why wouldn't all this occur from the installation itself, since I
selected 'huge26.s'? Does it even matter what I select at boot, since
I'll have to install packages after?
Since this appears to be a manual process, what about lilo/grub?

Is there a good reason why this doesn't all take care of itself since
I indicated my intention of using the 2.6 kernel?

On Thu, 03 May 2007 12:43:35 -0700, jessica6_2000 wrote:

> I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
> 11 DVD, and at the boot prompt I selected "huge26.s". The
> installation works fine on my 360G SATA disk, but after the install my
> kernel is 2.4.33.3. At the very end of the installation, it asked
> which kernel to use, and I selected the default since (from what I
> understood) the default kernel was the one I booted (huge26.s) and the
> one I want.
> I searched Usenet a bit, and even found some posts mentioning
> "installing modules afterwards".
>
> This post:
>
> http://groups.google.com/group/alt.o...d5e9e5228a04d/
>
> Mentions installing more packages from the DVD:
>
> kernel-generic-2.6.17.13-i486-1.tgz
> kernel-modules-2.6.17.13-i486-1.tgz
> kernel-source-2.6.17.13-noarch-1.tgz
>
> Why wouldn't all this occur from the installation itself, since I
> selected 'huge26.s'? Does it even matter what I select at boot, since
> I'll have to install packages after?
> Since this appears to be a manual process, what about lilo/grub?
>
> Is there a good reason why this doesn't all take care of itself since
> I indicated my intention of using the 2.6 kernel?
>
I don't know exactly where you went wrong, but in any case, tweaking the
kernel after install is easily done, especially since your install was
mostly successful. Do note however, that you probably don't want the
huge26.s kernel from setup. I I would try 2.6.17.13 from extra first. Then
perhaps, upgrade to a kernel from -current after that is working.

For example, 2.6.21.1
http://tinyurl.com/2ovyt5

Plus modules, here:
http://tinyurl.com/2ocr2p

If you are unfamiliar with upgrading a kernel, then do some work at the
fundamental level first. For example, install a new kernel and its
modules. In other words, use installpkg, not upgradepkg.

Fix bootloader...
If you are using lilo, then follow the usual drill. I use grub myself.

--
Douglas Mayne

jessica6_2000@yahoo.com wrote:
> I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
> 11 DVD, and at the boot prompt I selected "huge26.s". The
> installation works fine on my 360G SATA disk, but after the install my
> kernel is 2.4.33.3. At the very end of the installation, it asked
> which kernel to use, and I selected the default since (from what I
> understood) the default kernel was the one I booted (huge26.s) and the
> one I want.
> I searched Usenet a bit, and even found some posts mentioning
> "installing modules afterwards".
>
> This post:
>
> http://groups.google.com/group/alt.o...d5e9e5228a04d/
>
> Mentions installing more packages from the DVD:
>
> kernel-generic-2.6.17.13-i486-1.tgz
> kernel-modules-2.6.17.13-i486-1.tgz
> kernel-source-2.6.17.13-noarch-1.tgz
>
> Why wouldn't all this occur from the installation itself, since I
> selected 'huge26.s'? Does it even matter what I select at boot, since
> I'll have to install packages after?
> Since this appears to be a manual process, what about lilo/grub?
>
> Is there a good reason why this doesn't all take care of itself since
> I indicated my intention of using the 2.6 kernel?

This is all well-documented in the RELEASE_NOTES in the root directory
of your DVD...

Eric

jessica6_2000@yahoo.com wrote:
> I'm trying to install Slackware 11 with the 2.6 kernel. I'm
> using the 11 DVD, and at the boot prompt I selected "huge26.s".
> The installation works fine on my 360G SATA disk, but after the
> install my kernel is 2.4.33.3. At the very end of the
> installation, it asked which kernel to use, and I selected the
> default since (from what I understood) the default kernel was the
> one I booted (huge26.s) and the one I want. I searched Usenet a
> bit, and even found some posts mentioning "installing modules
> afterwards".

Follow the instructions you should find in the 2nd CD of slackware
11, in /extra/linux-2.6.17.13/README.initrd

On May 3, 1:13 pm, Eric Hameleers <a...@penguin1.dyndns.org> wrote:
> jessica6_2...@yahoo.com wrote:
> > I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
> > 11 DVD, and at the boot prompt I selected "huge26.s". The
> > installation works fine on my 360G SATA disk, but after the install my
> > kernel is 2.4.33.3. At the very end of the installation, it asked
> > which kernel to use, and I selected the default since (from what I
> > understood) the default kernel was the one I booted (huge26.s) and the
> > one I want.
> > I searched Usenet a bit, and even found some posts mentioning
> > "installing modules afterwards".
>
> > This post:
>
> >http://groups.google.com/group/alt.o...rowse_thread/t...
>
> > Mentions installing more packages from the DVD:
>
> > kernel-generic-2.6.17.13-i486-1.tgz
> > kernel-modules-2.6.17.13-i486-1.tgz
> > kernel-source-2.6.17.13-noarch-1.tgz
>
> > Why wouldn't all this occur from the installation itself, since I
> > selected 'huge26.s'? Does it even matter what I select at boot, since
> > I'll have to install packages after?
> > Since this appears to be a manual process, what about lilo/grub?
>
> > Is there a good reason why this doesn't all take care of itself since
> > I indicated my intention of using the 2.6 kernel?
>
> This is all well-documented in the RELEASE_NOTES in the root directory
> of your DVD...
>
> Eric

Ok, as I feared. It appears I'd need to do quite a bit-- most of
which I'm not familiar. I'll just go with the 2.4 until 2.6 REALLY is
part of the standard Slackware installation without extra package
installs, rebuilding, and kernel recompiles.

I like Slackware because it doesn't install a bunch of mysterious
daemons like other distributions, and it's easy to secure. So I'm
sticking with it.

Since I selected "huge26.s" at the boot:, is that going to cause
problems with my 2.4 kernel that really is installed?

Thanks to all those that replied!

jessica wrote :

> At the very end of the installation, it asked which kernel to use, and
> I selected the default since (from what I understood) the default
> kernel was the one I booted (huge26.s) and the one I want.

In the root of your DVD there's a file named RELEASE_NOTES and I quote:
"After the packages have installed and you've reached the menu where you
are prompted to select a kernel to install, BE CERTAIN to install
huge26.s or test26.s (whichever one you used to install) or there's a
chance that your machine will be unable to boot with the stock sata.i
kernel that you'll end up with."
>
> Is there a good reason why this doesn't all take care of itself since
> I indicated my intention of using the 2.6 kernel?
>
The modules are installed from the RAM-disk the Slackware install DVD
boot into. My guess is that P.V. felt that the RAM-disk would become
much to big if it should hold 3 sets of modules.
--
Thomas O.

This area is designed to become quite warm during normal operation.

On Thu, 03 May 2007 12:43:35 -0700, jessica6_2000 wrote:

> I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the

Ooooh. A Slack chick. Are you a dumb blond?

Are you a hottie?

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

jessica6_2000@yahoo.com wrote:
> On May 3, 1:13 pm, Eric Hameleers <a...@penguin1.dyndns.org> wrote:
>> jessica6_2...@yahoo.com wrote:
>>> I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
>>> 11 DVD, and at the boot prompt I selected "huge26.s". The
>>> installation works fine on my 360G SATA disk, but after the install my
>>> kernel is 2.4.33.3. At the very end of the installation, it asked
>>> which kernel to use, and I selected the default since (from what I
>>> understood) the default kernel was the one I booted (huge26.s) and the
>>> one I want.

Nope "default" is 2.4.33.3 - I have always needed to specify which kernel I wanted
off the cd1 (or dvd).

>>> I searched Usenet a bit, and even found some posts mentioning
>>> "installing modules afterwards".
>>> This post:
>>> http://groups.google.com/group/alt.o...rowse_thread/t...
>>> Mentions installing more packages from the DVD:
>>> kernel-generic-2.6.17.13-i486-1.tgz
>>> kernel-modules-2.6.17.13-i486-1.tgz
>>> kernel-source-2.6.17.13-noarch-1.tgz

This was explained in during the installation an in several txt files. You are
required to complete the installation manually.

>>> Why wouldn't all this occur from the installation itself, since I
>>> selected 'huge26.s'? Does it even matter what I select at boot, since
>>> I'll have to install packages after?

Anything in /extra and /testing is a *manual* process and won't be automatically
installed. This is Slackware and PV has good reasons for it.

>>> Since this appears to be a manual process, what about lilo/grub?
>>> Is there a good reason why this doesn't all take care of itself since
>>> I indicated my intention of using the 2.6 kernel?
>> This is all well-documented in the RELEASE_NOTES in the root directory
>> of your DVD...
>>
>> Eric
>
> Ok, as I feared. It appears I'd need to do quite a bit-- most of
> which I'm not familiar. I'll just go with the 2.4 until 2.6 REALLY is
> part of the standard Slackware installation without extra package
> installs, rebuilding, and kernel recompiles.
>
> I like Slackware because it doesn't install a bunch of mysterious
> daemons like other distributions, and it's easy to secure. So I'm
> sticking with it.
>
> Since I selected "huge26.s" at the boot:, is that going to cause
> problems with my 2.4 kernel that really is installed?
>
> Thanks to all those that replied!
>
It really isn't all that hard to load the new kernel. And 2.6 is a lot faster than
2.4 (esp on my Pentium 266MMX Thinkpad). Sometimes people in these ng will rag on you
for being a clueless noob or to RTFM instead of just giving a simple knowledgeable
answer. They forget they were clueless noobs at on time.

For example,

1. install packages from /extra/kernel-2.6.17.13
2. Check symlinks in /boot to make sure they point to the new kernel. installpkg
should have copied the appropriate files.

root@samwise:~# ls -l /boot
total 8924
lrwxrwxrwx 1 root root 37 2007-04-29 11:23 README.initrd ->
/usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r-- 1 root root 708439 2007-04-30 22:58 System.map-ewk-2.6.17.13
-rw-r--r-- 1 root root 629105 2006-09-01 00:51 System.map-ide-2.4.33.3
-rw-r--r-- 1 root root 1101492 2007-04-29 12:29 System.map-ide-2.6.17.13
-rw-r--r-- 1 root root 512 2007-04-29 12:31 boot.0300
-rw-r--r-- 1 root root 37462 2007-04-30 22:04 config-ewk-2.6.17.13
-rw-r--r-- 1 root root 41810 2006-09-01 00:51 config-ide-2.4.33.3
-rw-r--r-- 1 root root 62900 2007-04-29 12:29 config-ide-2.6.17.13
-rw-r--r-- 1 root root 5032 2006-08-07 23:34 diag1.img
-rw------- 1 root root 80384 2007-05-01 00:36 map
-rw-r--r-- 1 root root 1624250 2007-04-30 22:58 vmlinuz-ewk-2.6.17.13
-rw-r--r-- 1 root root 1313255 2006-09-01 00:51 vmlinuz-ide-2.4.33.3
-r-------- 1 root root 3476293 2007-04-29 12:29 vmlinuz-ide-2.6.17.13
root@samwise:~#

As you can see, I have the default 2.4 and 2.6 kernels loaded as well as my
recompiled custom kernel. I deleted the original symlinks to just boot into any of
the kernels should that be necessary (such as i screwed up the compile and I had some
initial issues with 2.6 and udev)

3. Configure lilo.conf:

root@samwise:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
install=menu
menu-title="Slackware Linux 11.0"
menu-scheme=wb:Yb:wb:Yb
prompt
timeout = 150
default=linux2617ewk
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.33.3
root = /dev/hda1
label = linux2433
append = "acpi=off apm=on"
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz-ide-2.6.17.13
root = /dev/hda1
label = linux2617
append = "pci=noacpi pci=conf1"
read-only
image = /boot/vmlinuz-ewk-2.6.17.13
root = /dev/hda1
label = linux2617ewk
append = "pci=noacpi pci=conf1"
read-only
# Linux bootable partition config ends

(A note to old thinkpad users: with 2.4 acpi doesn't work but apm kinda does. under
2.6 pci=noacpi was needed so that CDROM detection didn't crash the OS, pci=conf1 was
needed to see the 3COM NIC in the PCMCIA slot [see man lspci])

When you edit lilo.conf, don't forget to run lilo as root:

root@samwise:~# lilo
Added linux2433
Added linux2617
Added linux2617ewk *

if you used the vmlinuz, etc, symlinks and just edited them to point to the new
kernel, you still need to run lilo.

3. Check to make sure modules where installed:

root@samwise:~# ls -l /lib/modules
total 12
drwxr-xr-x 4 root root 4096 2007-04-29 11:22 2.4.33.3/
drwxr-xr-x 3 root root 4096 2007-04-29 19:05 2.6.17.13/
drwxr-xr-x 3 root root 4096 2007-05-01 00:29 2.6.17.13ewk2/
root@samwise:~#

4. Check/edit symlink to rc.modules:

root@samwise:~# ls -l /etc/rc.d
total 240

----------snip--------------

lrwxrwxrwx 1 root root 20 2007-04-29 19:11 rc.modules -> rc.modules-2.6.17.13*
-rwxr-xr-x 1 root root 25553 2006-09-01 02:31 rc.modules-2.4.33.3*
-rwxr-xr-x 1 root root 28539 2007-04-29 22:28 rc.modules-2.6.17.13*

----snip------------

root@samwise:~#

After awhile, when you are comfortable with 2.6, you can remove all the 2.4 stuff
(removepkg kernel-ide-2.4.33.3-i486-1.tgz and so forth) to free up space.

Enjoy.

<jessica6_2000@yahoo.com> wrote:
>Ok, as I feared. It appears I'd need to do quite a bit-- most of
>which I'm not familiar. I'll just go with the 2.4 until 2.6 REALLY is
>part of the standard Slackware installation without extra package
>installs, rebuilding, and kernel recompiles.

It's good (from a geek standpoint) to know how to do kernel builds. You
learn quite a bit about the various subsystems just by going through the
configuration. Also, you might increase the responsiveness of your
desktop system with well-chosen options.

Once everything is up and running, grab the latest kernel, unpack it,
and "make xconfig" (or menuconfig for console mode) to see how
configuring the kernel works. There's a README and a Documentation
directory with everything you ever wanted to know.

It is a time-consuming process, though.

-Beej

In <pan.2007.05.04.04.15.03.886191@lan.invalid>, Dan C wrote:

> On Thu, 03 May 2007 12:43:35 -0700, jessica6_2000 wrote:
>
>> I'm trying to install Slackware 11 with the 2.6 kernel. I'm using the
>
> Ooooh. A Slack chick. Are you a dumb blond?
>
Are you?

> Are you a hottie?

What good is a post like yours in the beginning of the 21st century. Pity.

Good luck anyways
Franz