Hello from the Eighth Doctor
Is anyone seeing this when trying to boot a custom 2.6.11 kernel, based on the
source from the Slackware-current collection?

First I install the "generic" 2.6.11 kernel, and modules. It boots correctly, never
mind the wrong setting for the mice. Everything within reason works.

Then I decide what I need to do to make a "custom" kernel using the same source
code. I turn on, or turn off those things. I then follow the whole process that the 2.6
kernels have chosen for creating such kernels.

However when the system then boots the kernel, it exhibits a panic about the time
I normally see the udev process startup normally on the generic one. At first I
thought it meant I needed to install the next number release. Found it, built it using
the same methods used for building others, and installed the package. It works for
the generic, it does not work for the custom. Now it panics again at udev, and even
at hotplug. I can't present the panics here because the system doesn't properly boot
after them.

I'm thinking I should also upgrade hotplug from the same -current collection as well.

Also, I am going to make available the resultant collection available via ftp download
from my site, via appointment only, regardless.
----
Gregg drwho8 atsign att dot net
"This signature does not exist."

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Eighth Doctor wrote:
> Hello from the Eighth Doctor
> Is anyone seeing this when trying to boot a custom 2.6.11 kernel, based on the
> source from the Slackware-current collection?
>
> First I install the "generic" 2.6.11 kernel, and modules. It boots correctly, never
> mind the wrong setting for the mice. Everything within reason works.
>
> Then I decide what I need to do to make a "custom" kernel using the same source
> code. I turn on, or turn off those things. I then follow the whole process that the 2.6
> kernels have chosen for creating such kernels.
>
> However when the system then boots the kernel, it exhibits a panic about the time
> I normally see the udev process startup normally on the generic one. At first I
> thought it meant I needed to install the next number release. Found it, built it using
> the same methods used for building others, and installed the package. It works for
> the generic, it does not work for the custom. Now it panics again at udev, and even
> at hotplug. I can't present the panics here because the system doesn't properly boot
> after them.
>
> I'm thinking I should also upgrade hotplug from the same -current collection as well.
>
> Also, I am going to make available the resultant collection available via ftp download
> from my site, via appointment only, regardless.
> ----
> Gregg drwho8 atsign att dot net
> "This signature does not exist."
>
I have all the -currents FTP from the -current directory directly from
slackware. Used gFTP and took 24 hours to do with a 1.5MB Downstream,
seems the site was hit with others doing the same thing. I have all the
Files and burnt them to 3 CD's. Yes 3 CD's I have a few extra more
recent things on them too. The newer Apache, PHP and more. I as of yet,
have not tried to do the 2.6.11.X Kernel again as this system is stable
and I don't want to have to go back through and reinstall all that again
if it crashes, and it has. The Kernels have Depreciated items and
disabling the Links to them, they disable other things and the list goes
on. I have posted the Error Messages and found they are just bad
programming. I am going to wait now, till the 2.6.12 comes out and it
should have these depreciated items removed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCc2nhSmxUFLwQOoMRAiX5AJ41Iz+T+leNz3JZRf+Fjx 1tgKzvIACfX1Fm
EoHv5QX7SVcDuPG7iAlWuOM=
=a56A
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"BenneJezzerette" <jennifer755@cox.net> wrote in message
news:4%Pce.670$Fa1.214@fed1read02...
> I have all the -currents FTP from the -current directory directly
> from slackware. Used gFTP and took 24 hours to do with a 1.5MB
> Downstream, seems the site was hit with others doing the same
> thing. I have all the Files and burnt them to 3 CD's. Yes 3 CD's

How is this relevant to the original post?!?! Everyone knows that
slackware is released on multiple cds, 4 in the case of 10.1.

The OP was asking about a specific problem of booting with a custom
compiled kernel of 2.6.11.

>I have a few extra more
> recent things on them too. The newer Apache, PHP and more. I as of
> yet, have not tried to do the 2.6.11.X Kernel again as this system
> is stable and I don't want to have to go back through and reinstall
> all that again if it crashes, and it has.

Why would you need to reinstall? You just reboot from cd, cp
vmlinuz.old and System.old (if you compiled you own kernel, or
reinstall the kernel packages if you're using slack packages) and run
lilo. Then reboot. No need to reinstall your system.

> The Kernels have Depreciated items and
> disabling the Links to them, they disable other things and the list
> goes on. I have posted the Error Messages and found they are just
> bad
> programming.

So disable them? I'm sure PV wouldn't put out a kernel package with
stuff enabled/disabled that would break things or cause system
instability. In any event, I prefer to reconfigure and recompile my
own kernel and IME generally the best rule is to compile in only that
which you need and disable everything else. If something is
deprecated, then the problem isn't with the kernel not including
this, but software not being maintained.

Have you emailed the kernel errors to linus et al? (though I would
suspect they'd just be ignored since you're using an outdated version
of the kernel) Please don't complain about bad programming and having
reported bugs if you haven't actually reported them to the respective
maintainers - chances are they'll either already be fixed, or would
be had they been properly reported. Millions of people around the
world use the linux kernel and find it extremely stable and
well-programmed. (With regards to the 2.6 kernel, numerous benchmarks
have shown it to be more responsive and generally more stable - sorry
for lack of references here, if u want to know more try google)

> I am going to wait now, till the 2.6.12 comes out and it
> should have these depreciated items removed.

Incidentally, since 2.6.11 was released there have been 8 further
kernel versions released.... 2.6.11.1, 2.6.11.2, 2.6.11.3, 2.6.11.4,
2.6.11.5, 2.6.11.6, 2.6.11.7 and upon checking this morning I notice
2.6.11.8 has been released. (as well as 3 2.6.12 release candidates,
although of course these are not strictly "stable" yet)

To the Eighth Doctor...

On the original point, can you provide us with some output from
dmesg, /var/log/messages, as well as the actual errors you are
seeing. I had issues with 2.6.11.7 on my gf's laptop - I used make
oldconfig from 2.6.7 and for some reason it just refused to boot the
new kernel. You may also want to post some info on your .config file.
Perhaps back up this file, do a make mrproper and rebuild again and
see if that fixes the problem.

Martin

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1 - not licensed for commercial use: www.pgp.com

iQA/AwUBQnPhw0VuUD0svAWDEQKYVgCfbjNdMJUWY/u57ToBd0xByT9RKaMAoKDh
vy+2FsPYL+hXEzInjvFsgwDa
=msC1
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin J. Green wrote:
> "BenneJezzerette" <jennifer755@cox.net> wrote in message
> news:4%Pce.670$Fa1.214@fed1read02...
>
>>>I have all the -currents FTP from the -current directory directly
>>>from slackware. Used gFTP and took 24 hours to do with a 1.5MB
>>>Downstream, seems the site was hit with others doing the same
>>>thing. I have all the Files and burnt them to 3 CD's. Yes 3 CD's
>
>
> How is this relevant to the original post?!?! Everyone knows that
> slackware is released on multiple cds, 4 in the case of 10.1.
>
First and foremost, this is from the FTP Slackware-current

> The OP was asking about a specific problem of booting with a custom
> compiled kernel of 2.6.11.
>
>
>>>I have a few extra more
>>>recent things on them too. The newer Apache, PHP and more. I as of
>>>yet, have not tried to do the 2.6.11.X Kernel again as this system
>>>is stable and I don't want to have to go back through and reinstall
>>>all that again if it crashes, and it has.
>
>
> Why would you need to reinstall? You just reboot from cd, cp
> vmlinuz.old and System.old (if you compiled you own kernel, or
> reinstall the kernel packages if you're using slack packages) and run
> lilo. Then reboot. No need to reinstall your system.
>
I have fixed many of the errors, but then something I missed seems to
make it go crazy. Yes I have a Burned CD or secondary HDD to make sure
of certain problems that I may need to restore.

>
>>>The Kernels have Depreciated items and
>>>disabling the Links to them, they disable other things and the list
>>>goes on. I have posted the Error Messages and found they are just
>>>bad
>>>programming.
>
>
> So disable them? I'm sure PV wouldn't put out a kernel package with
> stuff enabled/disabled that would break things or cause system
> instability. In any event, I prefer to reconfigure and recompile my
> own kernel and IME generally the best rule is to compile in only that
> which you need and disable everything else. If something is
> deprecated, then the problem isn't with the kernel not including
> this, but software not being maintained.
>
Ok the errors - intermodule.c - filed a BUG and the person that
maintains it told me it's not a bug. Disabling Modules fixes it, but
then I lose access to other features, such as IPv6 support.

> Have you emailed the kernel errors to linus et al? (though I would
> suspect they'd just be ignored since you're using an outdated version
> of the kernel) Please don't complain about bad programming and having
> reported bugs if you haven't actually reported them to the respective
> maintainers - chances are they'll either already be fixed, or would
> be had they been properly reported. Millions of people around the
> world use the linux kernel and find it extremely stable and
> well-programmed. (With regards to the 2.6 kernel, numerous benchmarks
> have shown it to be more responsive and generally more stable - sorry
> for lack of references here, if u want to know more try google)
>
I went to the site that is mentioned in one of the files, and posted
that bug, and tried to send Linus a copy, but the e-Mail was bad and I
got it directly from the README files.

>
>>>I am going to wait now, till the 2.6.12 comes out and it
>>>should have these depreciated items removed.
>
>
> Incidentally, since 2.6.11 was released there have been 8 further
> kernel versions released.... 2.6.11.1, 2.6.11.2, 2.6.11.3, 2.6.11.4,
> 2.6.11.5, 2.6.11.6, 2.6.11.7 and upon checking this morning I notice
> 2.6.11.8 has been released. (as well as 3 2.6.12 release candidates,
> although of course these are not strictly "stable" yet)
>
Yes I understand that many releases have come, and someone even told me
to go to 2.6.9, I looked at 2.6.0 and 2.6.10 and felt limited. Now I
have to check the 2.6.11.8 out, thank you.

Top Note: I did the following Make Clean - Make mrproper - make - make
install - make modules_install did the lilo thing and for some reason,
the make install puts the VmLinuz and System.map into the ./ not just
/root, but the top most of the file tree. How do I know this? Because I
made changes to lilo to see that and it came up. I had 98% Usability out
of it.

> To the Eighth Doctor...
>
> On the original point, can you provide us with some output from
> dmesg, /var/log/messages, as well as the actual errors you are
> seeing. I had issues with 2.6.11.7 on my gf's laptop - I used make
> oldconfig from 2.6.7 and for some reason it just refused to boot the
> new kernel. You may also want to post some info on your .config file.
> Perhaps back up this file, do a make mrproper and rebuild again and
> see if that fixes the problem.
>
> Martin
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCc6KwSmxUFLwQOoMRAo19AJ9Jgn+T5RNKL2eg4RIMZY Z5dZVwQQCgytrU
IyMLUNJTVm+WjgXBFn6ajAE=
=p8bS
-----END PGP SIGNATURE-----

"BenneJezzerette" <jennifer755@cox.net> wrote in message
news:iyTce.838$Fa1.817@fed1read02...

> First and foremost, this is from the FTP Slackware-current

> I have fixed many of the errors, but then something I missed seems to
> make it go crazy. Yes I have a Burned CD or secondary HDD to make sure
> of certain problems that I may need to restore.

Well, what are they - post us some detailed info and there'll almost
certainly be someone here who can suggest a fix? IME the best way to learn
is to break it and fix it all again, that way you get to understand it

> Ok the errors - intermodule.c - filed a BUG and the person that
> maintains it told me it's not a bug. Disabling Modules fixes it, but
> then I lose access to other features, such as IPv6 support.
>
> I went to the site that is mentioned in one of the files, and posted
> that bug, and tried to send Linus a copy, but the e-Mail was bad and I
> got it directly from the README files.

What is the bug?

a quick google shows me several links to patches/fixes in 2.6.11* and
2.6.12-rc* kernels...

http://www.google.co.uk/search?hl=en...ermodule&meta=

Do you *really* need ipv6? Bear in mind that it's not exactly in widespread
use and there aren't even many isps that can give u a direct ipv6 connection
(though you can of course use a tunnel over ipv4) - it's largely scientific
atm. On the other hand, I do have ipv6 working fine on my server (tunneled)
without problems.

>>>>I am going to wait now, till the 2.6.12 comes out and it
>>>>should have these depreciated items removed.
>>
> Yes I understand that many releases have come, and someone even told me
> to go to 2.6.9, I looked at 2.6.0 and 2.6.10 and felt limited. Now I
> have to check the 2.6.11.8 out, thank you.

Bear in mind that whether deprecated items are included or not - the end
result is the same; if you compile without then you don't get them (as
opposed to compiling when they're not there - ultimately u don't get them in
the final binary).

> Top Note: I did the following Make Clean - Make mrproper - make - make
> install - make modules_install did the lilo thing and for some reason,
> the make install puts the VmLinuz and System.map into the ./ not just
> /root, but the top most of the file tree. How do I know this? Because I
> made changes to lilo to see that and it came up. I had 98% Usability out
> of it.

Quick kernel compile guide..

untar kernel tarball in /us/src
cd linux-<version)

do make menuconfig (from the command line)
OR make xconfig (in x windows)

(once you have a fully customised .config file, every time u upgrade ur
kernel u can copy .config and do make oldconfig)

Go through the options with a fine toothcomb. I assume you know your
hardware - choose *only the options you need* and unselect everything else.

make bzImage (note that's case sensitive)

make modules

Now edit Makefile with your favourite editor, there's a line that looks
like...

#export INSTALL_PATH=/boot

uncomment it and save the file.

now make install
make modules_install

run lilo and you should be good to go

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin J. Green wrote:
> "BenneJezzerette" <jennifer755@cox.net> wrote in message
> news:iyTce.838$Fa1.817@fed1read02...
>
>
>>First and foremost, this is from the FTP Slackware-current
>
>
>>I have fixed many of the errors, but then something I missed seems to
>>make it go crazy. Yes I have a Burned CD or secondary HDD to make sure
>>of certain problems that I may need to restore.
>
>
> Well, what are they - post us some detailed info and there'll almost
> certainly be someone here who can suggest a fix? IME the best way to learn
> is to break it and fix it all again, that way you get to understand it
>
>
>>Ok the errors - intermodule.c - filed a BUG and the person that
>>maintains it told me it's not a bug. Disabling Modules fixes it, but
>>then I lose access to other features, such as IPv6 support.
>>
>>I went to the site that is mentioned in one of the files, and posted
>>that bug, and tried to send Linus a copy, but the e-Mail was bad and I
>>got it directly from the README files.
>
>
> What is the bug?
>
4505 on osdi, and the owner of the intermodule.c closed it saying ti is
to be fixed in up coming releases.

>
> Quick kernel compile guide..
>
> untar kernel tarball in /us/src
> cd linux-<version)
>
> do make menuconfig (from the command line)
> OR make xconfig (in x windows)
>
> (once you have a fully customised .config file, every time u upgrade ur
> kernel u can copy .config and do make oldconfig)
>
> Go through the options with a fine toothcomb. I assume you know your
> hardware - choose *only the options you need* and unselect everything else.
>
> make bzImage (note that's case sensitive)
>
> make modules
>
> Now edit Makefile with your favourite editor, there's a line that looks
> like...
>
> #export INSTALL_PATH=/boot
>
> uncomment it and save the file.
>
> now make install
> make modules_install
>
> run lilo and you should be good to go
>
>

I have been editing the install.sh and makefile.sh to reflect the proper
areas to place what files. /boot rather than /root or / as it were. I
have the 2.6.11.8 and am slowly this time, working through the setup to
make all the right choices. I know my hardware pretty good. AMD k6-2 500
256MB System Ram VIA Chip set with a VIA IDE Controller and an nVidia
GeForce 2 MX 400 AGP2X 64MB card. Logitech trackman marble optical (not
made any more) Sony Display (uses xorgsetup to get the best resolution)
Creative Labs Sound blaster Live 24Bit, Slackware 10.1 -current and I do
all my Kernel builds from the CLI not KDE or any other Window Manager. I
have a hardware book for my main board too, so I can't make too many
mistakes, unless I close my eyes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCc8iJSmxUFLwQOoMRAnXnAJ9P6nwKtLLB2V4jUjs4Vu c5sNPYogCfXfbZ
+7yErbyqx7oz8hoNmalVGqo=
=WQBm
-----END PGP SIGNATURE-----

BenneJezzerette wrote:

> 4505 on osdi, and the owner of the intermodule.c closed it saying ti is
> to be fixed in up coming releases.

well, where's the problem then? Get the new release

> I have been editing the install.sh and makefile.sh to reflect the proper
> areas to place what files. /boot rather than /root or / as it were. I
> have the 2.6.11.8 and am slowly this time, working through the setup to
> make all the right choices. I know my hardware pretty good. AMD k6-2 500
> 256MB System Ram VIA Chip set with a VIA IDE Controller and an nVidia
> GeForce 2 MX 400 AGP2X 64MB card. Logitech trackman marble optical (not
> made any more) Sony Display (uses xorgsetup to get the best resolution)
> Creative Labs Sound blaster Live 24Bit, Slackware 10.1 -current and I do
> all my Kernel builds from the CLI not KDE or any other Window Manager. I
> have a hardware book for my main board too, so I can't make too many
> mistakes, unless I close my eyes.

ooh, why do I hear alarm bells! See the other thread on manually changing
paths - AFAIK the only thing you need to change is the INSTALL_PATH (works
the same way as DESTDIR) everything else *should* be ok.

Incidentally, you're fine compiling within KDE (though it may be slightly
slower given KDE or whatever is running at the same time) - it won't affect
the ultimate finished article. OTOH, I've been using make menuconfig for so
long that I fear I've become addicted, in that I just can't bring myself to
use make xconfig :P

If you're feeling like living dangerously, try 2.6.12-RC3

On Sun, 01 May 2005 03:21:28 +0100, "Martin J. Green" <martin.green@NOSPAM.firstinternetservices.com> wrote:

>If you're feeling like living dangerously, try 2.6.12-RC3

2.6.12-rc3-mm2, -mm1 gone overnight -- some people just can't
keep up )

To the other poster: install.sh hasn't changed for ten years because
one may write their very own ~/bin/installkernel script which gets
called from there. Distros hook the /sbin/installkernel option.

So for 2.6: 'make && make install && make modules_install' if you
have custom installkernel script, or:

replacing 'make install' with 'INSTALL_PATH=/boot make install'
avoids editing kernel build scripts.

See: 'make help' for details

--Grant.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Grant Coady wrote:

> 2.6.12-rc3-mm2, -mm1 gone overnight -- some people just can't
> keep up )

:P

What is -mm? I know -ac is Alan Cox's patches, but what is -mm?

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFCdGNgRW5QPSy8BYMRAs6yAKDdXTDy0t8DBTVBq4LcYE Go9+dBGwCg9YdQ
Q1zcB15VHRaAmo5ugbrRAyg=
=mf1G
-----END PGP SIGNATURE-----

In article <4273e1b7$1_1@mk-nntp-2.news.uk.tiscali.com>,
martin.green@NOSPAM.firstinternetservices.com says...
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>"BenneJezzerette" <jennifer755@cox.net> wrote in message
>news:4%Pce.670$Fa1.214@fed1read02...
>> I have all the -currents FTP from the -current directory directly
>> from slackware. Used gFTP and took 24 hours to do with a 1.5MB
>> Downstream, seems the site was hit with others doing the same
>> thing. I have all the Files and burnt them to 3 CD's. Yes 3 CD's
>
>How is this relevant to the original post?!?! Everyone knows that
>slackware is released on multiple cds, 4 in the case of 10.1.
>
>The OP was asking about a specific problem of booting with a custom
>compiled kernel of 2.6.11.
>
>>I have a few extra more
>> recent things on them too. The newer Apache, PHP and more. I as of
>> yet, have not tried to do the 2.6.11.X Kernel again as this system
>> is stable and I don't want to have to go back through and reinstall
>> all that again if it crashes, and it has.
>
>Why would you need to reinstall? You just reboot from cd, cp
>vmlinuz.old and System.old (if you compiled you own kernel, or
>reinstall the kernel packages if you're using slack packages) and run
>lilo. Then reboot. No need to reinstall your system.
>
>> The Kernels have Depreciated items and
>> disabling the Links to them, they disable other things and the list
>> goes on. I have posted the Error Messages and found they are just
>> bad
>> programming.
>
>So disable them? I'm sure PV wouldn't put out a kernel package with
>stuff enabled/disabled that would break things or cause system
>instability. In any event, I prefer to reconfigure and recompile my
>own kernel and IME generally the best rule is to compile in only that
>which you need and disable everything else. If something is
>deprecated, then the problem isn't with the kernel not including
>this, but software not being maintained.
>
>Have you emailed the kernel errors to linus et al? (though I would
>suspect they'd just be ignored since you're using an outdated version
>of the kernel) Please don't complain about bad programming and having
>reported bugs if you haven't actually reported them to the respective
>maintainers - chances are they'll either already be fixed, or would
>be had they been properly reported. Millions of people around the
>world use the linux kernel and find it extremely stable and
>well-programmed. (With regards to the 2.6 kernel, numerous benchmarks
>have shown it to be more responsive and generally more stable - sorry
>for lack of references here, if u want to know more try google)
>
>> I am going to wait now, till the 2.6.12 comes out and it
>> should have these depreciated items removed.
>
>Incidentally, since 2.6.11 was released there have been 8 further
>kernel versions released.... 2.6.11.1, 2.6.11.2, 2.6.11.3, 2.6.11.4,
>2.6.11.5, 2.6.11.6, 2.6.11.7 and upon checking this morning I notice
>2.6.11.8 has been released. (as well as 3 2.6.12 release candidates,
>although of course these are not strictly "stable" yet)
>
>To the Eighth Doctor...
>
>On the original point, can you provide us with some output from
>dmesg, /var/log/messages, as well as the actual errors you are
>seeing. I had issues with 2.6.11.7 on my gf's laptop - I used make
>oldconfig from 2.6.7 and for some reason it just refused to boot the
>new kernel. You may also want to post some info on your .config file.
>Perhaps back up this file, do a make mrproper and rebuild again and
>see if that fixes the problem.
>
>Martin
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP 8.1 - not licensed for commercial use: www.pgp.com
>
>iQA/AwUBQnPhw0VuUD0svAWDEQKYVgCfbjNdMJUWY/u57ToBd0xByT9R
KaMAoKDh
>vy+2FsPYL+hXEzInjvFsgwDa
>=msC1
>-----END PGP SIGNATURE-----
>
>
Hello from the Eighth Doctor
Well I'll see what I can do, but I'm not making any promises. I think the problem
lays in with the udev system. I've got the latest ones here, which are not the version
that's traveling with current. I have made packages of them, and can provide binary
packages. As for source, that's a different story.
---
Gregg drwho8 atsign att dot net