Are there special slackware Kernel Patches? I'm using Version 10.0 and
am having trouble with my kernel compiled from scratch. (Booting is
stuck on udev). If so where might I find them?
Thanks,
Joe

Dnia Sun, 07 Aug 2005 11:30:41 -0700, CPUFreak91 napisa³(a):

> Are there special slackware Kernel Patches? I'm using Version 10.0 and
> am having trouble with my kernel compiled from scratch. (Booting is
> stuck on udev). If so where might I find them?

Slackware uses vanilla, i.e. unpatched kernels. If your problem is that
your machine is stuck on udev starting, then the problem is probably in
kernel config file. Try to use default Slackware config.

--
Maciej Bliziñski http://automaciej.blogspot.com
GCS/MU d- s++:- a- C+++ UL++ P++ L+++ W++ N++ w-- PGP+ !tv b+ h r++

CPUFreak91 wrote:
> Are there special slackware Kernel Patches?

No.

If you download the kernel directly from kernel.org and use the config
you should find in /boot/config, your compile should result in exactly
the same kernel as Slackware ships with.

~Mik

--
Ceston atque Cungulum Parvissimos Minutissimos Natatorios Flavors Occelatos
// Itsy Bitsy Teeny Weenie Yellow Polka Dot Bikini

From "Pop-Cultural Latin" by Henry Beard

On Sun, 07 Aug 2005 11:30:41 -0700, CPUFreak91 wrote:

> Are there special slackware Kernel Patches? I'm using Version 10.0 and
> am having trouble with my kernel compiled from scratch. (Booting is
> stuck on udev). If so where might I find them?
> Thanks,
> Joe

your problem is, almost certain, in old udev version. try compiling and
upgrading newer udev & hotplug (ie from current?) using slackbuild
scripts. and be certain compilation of udev went right - scroll up and
check for nasty errors (warnings are mostly ok).

Well I got past the udev problem (don't know how) but now it's stuck on
SCSI... I think I know how to fix that.

CPUFreak91 wrote:
> Well I got past the udev problem (don't know how) but now it's stuck on
> SCSI... I think I know how to fix that.

Never mind.. I can't fix it. I get this message: Attached SCSI generic
sg0 at scsi0, channel0, id0, lun0, type0.

It sticks for exactly 2 minutes 14 seconds (I timed it) and then
continues booting. Does anyone know why this does this?
Thanks,
CPUFreak91

"CPUFreak91" <cpu.crazy@gmail.com> wrote:
> CPUFreak91 wrote:
>> Well I got past the udev problem (don't know how) but now it's stuck on
>> SCSI... I think I know how to fix that.
>
> Never mind.. I can't fix it. I get this message: Attached SCSI generic
> sg0 at scsi0, channel0, id0, lun0, type0.
>
> It sticks for exactly 2 minutes 14 seconds (I timed it) and then
> continues booting. Does anyone know why this does this?
> Thanks,
> CPUFreak91

What kind of SCSI devices do you have?

What kind of SCSI deviced did you compile support for in your kernel?

What does /proc/scsi/scsi say?

What does the next line say when you boot? About 2 minuts sounds like it
could be sendmail having a problem with a misconfigured hostname.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc7(at)uthyres.com Examples of addresses which go to spammers:
info@k-soft.se info@k-software.biz info@webrider.ru root@localhost

I don't have any SCSI devices. I don't have /prom/scsi/scsi compiled
into the kernel (I don't have SCSI support compiled into the kernel
either).

Sendmail is not set up to run at boot. IT never took more than 20
seconds when it was configured. Thanks for trying to help so far. :-)

In alt.os.linux.slackware, CPUFreak91 dared to utter,
> I don't have any SCSI devices. I don't have /prom/scsi/scsi compiled
> into the kernel

Man that sounds too much like high-school again. I had a scsi scsi
prom. :^)

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

"CPUFreak91" <cpu.crazy@gmail.com> wrote:
>>> Never mind.. I can't fix it. I get this message: Attached SCSI generic
>>> sg0 at scsi0, channel0, id0, lun0, type0.

> I don't have any SCSI devices.

Your kernel seems to think different as it tries to mess with some generic
scsi stuff.

>> What kind of SCSI deviced did you compile support for in your kernel?
>
>> What does /proc/scsi/scsi say?

> I don't have /prom/scsi/scsi compiled into the kernel (I don't have SCSI
> support compiled into the kernel either).

If you didn't compile SCSI support into the kernel it must have been
loaded as a module. If you didn't edit any startup script to load that
module it probably was loaded by hotplug. Try to find out which module it
is and try to blacklist that module as you don't have any SCSI things.

Useful places to look:

/proc/scsi/scsi (note the spelling)
/proc/modules (you could also use lsmod)

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc7(at)uthyres.com Examples of addresses which go to spammers:
info@k-soft.se info@k-software.biz info@webrider.ru root@localhost