No not a termination issue as I have checked and my previous
kernel has no problem with the 2 controller setup,
absolutely nothing in the boot logs mentioning any problems
with SCSI devices. In fact on boot up all is recognized till
the boot gets to the point of reading init. I sent 3 e-mails
yesterday describing this in a little more detail. All I am
trying to do is update the stock kernel in RH 6.2 to the
2.2.16-3 with rpm. I use rpm -ivh of course and I make my
initrd image then update lilo for the new kernel and run
/sbin/lilo. Have done this for 2 other SCSI machines with no
hassle. Almost made me a believer in rpm as a usually
compile my kernels on my own. Your saying recompile and
leave out that option. What option? This was an security
update from Red Hat. You say I don't mention the SCSI
controller. You mean the brand? It really has nothing to do
with this as this RPM update was supposed to fix the
following:
------------------------------------
A security bug involving setuid programs is fixed in
this kernel.
Added or updated drivers include:
Updated AMI MegaRAID driver
Updated Acenic Gigabit Ethernet driver
Added Adaptec RAID (aacraid) driver
Updated to latest 3c90x driver from 3Com
Updated agpgart handling for latest Intel 810 chipset
Updated SCSI error handling <<<<<<<**********
----------------------------------
Note the Updated SCSI error handling. I believe my problem
lies there. I am terminated properly or the machine is I
mean:-). I guess I could try another terminator if the
previous is defective. The hard drive is terminated by a
jumper on the tape drive set for termination and the 4 tier
CDrom box is terminated by a hardware termination device. I
don't know how better to terminate it other than getting a
different 50 pin cable for 3 devices for the hard drive/tape
drive and terminating with another 50pin termination device.
I thought the tape drive jumper should terminate just fine.
I have another machine that is much newer as far as mother
board that terminates with a Wangdate tape drive and the rpm
update to 2.2.16-3 was very smooth. I will check termination
again but I don't think that is it. I guess I will have to
go to the 2.2.18 and hope for the best.
Thanks,
Eddie Strohmier
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Dave Wreski
> Sent: Monday, February 05, 2001 1:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SCSI probs with kernel 2.2.16-3
>
>
>
> > Still struggling with this one and I wondered
> if anyone could point me
> > to some list, newsgroup that could help. One of
> the updates to the
> > stock kernel in RH 6.2 (2.2.14-5 I think) was
> Updated SCSI error
> > handling. Well after I updated my kernel with
> an smp 2.2.16-3 kernel
> > rpm my machine is now thrown into an endless
> loop where the console
>
> If you haven't done it before it can be a bit
> tricky, but you could always
> compile your own kernel with that option disabled
> or modify the RH source
> RPM to disable this feature.
>
> It also doesn't help that you don't mention the
> SCSI controller, although
> I'm not sure how much that would help anyway.
>
> > messages relate to trying to access SCSI ID#0,
> resetting SCSI bus and
> > this will go on for days if I allow it or till
> a reset or CTL-ALT-DEL.
> > What was changed to "Update SCSI error
> handling"? My hardware can not
>
> It seems very unlikely that this would be the
> problem. Are you sure
> nothing else has changed? Sounds like
> termination, perhaps?
>
> If you boot from another kernel are you able to
> find anything useful in
> the logs?
>
> > seem to handle it. Would my best course of
> action be to just go to
> > 2.2.18 as I fear this "update" is probably part
> of this kernel also. I
>
> If you can compile your own 2.2.18 that sounds
> like a good next step.
>
> > am not worried to much about this machine with
> the current kernel as
> > it sits behind another firewall machine that is
> SCSI but had no
> > problems with the 2.2.16-3 rpm update.
>
> Well, the vulnerability that was present in
> 2.2.16 was a local
> vulnerability anyway, so a firewall isn't
> necessarily going to protect you
> from it anyway.
>
> > The only thing unique about the problem machine
> is that it is running
> > two SCSI controllers. One feeds the hard drive
> and the other feeds a 4
> > bay CDrom tower. I can not get anything out of
> logs of course because
> > I can not get it to boot. Searching for clues
> as to what could be
> > going on with my usual archives at redhat,
> moongroup, google, etc. has
> > been in vein as I can not find any mention of a
> similar problem.
>
> Perhaps the new kernel is more picky about a
> problem that has always been
> there, such as a termination problem..
>
> dave
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
