block-major-135 and Kernel questions

[AuntieParticle]

>
>
> On Tue, 2003-11-25 at 09:29, AuntieParticle wrote:
>
>>> I got the old kernel removed just fine. Thanks.
>>> 
>>> More on the "modprobe: modprobe can't locate module block-major-135" 
>>> problem: I have noticed that it's not just  block-major-135 but a whole 
>>> list of block-major-XXX. I am unable to read all the numbers because 
>>> they go by so quickly. Is there some sort of boot log I can refer to so 
>>> that I can read the errors at a speed at which my eyes can focus. I have 
>>> also noticed that they happen right after the "Checking for new 
>>> Hardware" section of the boot. So I am wondering if FC1 is just not 
>>> happy about not finding any new hardware  I have tried out my printer, 
>>> CD-RW, and Zip drive and everything works just fine in FC1 once it boots 
>>> all the way. I am just very curious about the errors.
>>    
>>
>
># dmesg | less
>
>Will show you the kernel boot log.
>
>As someone else mentioned, it seems that stopping the 'smartd' service
>(for monitoring SMART compliant hard drives) will stop this spam. It's
>all harmless though.
>
> -- Chris Kloiber Red Hat, Inc.
>
 To follow up:

All I found not commented out in smartd was the follow:

/dev/hda -H -m root at localhost.localdomain

I wasn't sure if that could have anything to do with the errors. I am 
still rather a newbie at linux. So I just left it as it was.

I did have some success with adding the following to /etc/modules.conf :

alias block-major-135 off
alias block-major-134 off
alias block-major-133 off
alias block-major-132 off
alias block-major-131 off
alias block-major-130 off
alias block-major-129 off
alias block-major-128 off
alias block-major-71 off
alias block-major-70 off
alias block-major-69 off
alias block-major-68 off
alias block-major-67 off

All the errors are gone now.

Thanks,
AP