[KLUG Members] Pervasive problems continued.

[Adam Bultman]

I'm currently loading linux onto the IDE bigfoot (shudder).  The newest 
kernel I built excluded SCSI support, so that's a plus.  I imagine it's 
why I got the different error.  

I'll yank the SCSI card from the box tonight, although windows has been SO 
complainy recently I'm afraid.  It's taken to this attitude "I'm not 
playing with ANYONE else, so screw it".  Since Christmas, I've rebuilt the 
machine over half a dozen times.  Any time I make any changes, it pukes.  
This most recent install is pretty happy, so we'll see.



On Wed, 30 Jan 2002, Patrick Stockton wrote:

> It's sounding more and more like it's your SCSI controler.  Does your
> motherboard have onboard IDE?  Do you have an IDE hard drive you can throw
> in there?
> 
> If you remove the SCSI controler and get the same errors at least you know
> it's not the controler or the drive.
> 
> Patrick
> 
> ----- Original Message -----
> From: "Adam Bultman" <adamb@glaven.org>
> To: <members@kalamazoolinux.org>
> Sent: Wednesday, January 30, 2002 10:56 AM
> Subject: Re: [KLUG Members] Pervasive problems continued.
> 
> 
> > Well, I booted from a boot CD, got in, re-compiled the 2.4.7-10 kernel,
> > and got a different error message! Huzzah! This time, I get a swap error,
> > 4 of 'em, and then a hard crash. Oh, well.  Slackware, here I come.
> >
> > adam
> >
> >
> > On 29 Jan 2002, Bryan J. Smith wrote:
> >
> > > On Tue, 2002-01-29 at 18:32, Adam Bultman wrote:
> > > >
> > > > Well, I tweaked a few settings, and it still bails.  I'm ready to
> > > > thoroughly blame the SCSI drive.  The errors are something to the
> extent
> > > > of Attempting to kill init, and it will give me a stack trace, some
> memory
> > > > values, and other information, with one line containing the word
> "Aieee!"
> > > > (no kidding).  It's scrolls too fast, and since it catches all other
> info,
> > > > I can't really read it, nor do I wish to explain it here.  I'm going
> to
> > > > try slackware, since it owns anyway.  I'm sure I'll complain here if
> it
> > > > fails... ;)
> > >
> > > What controller?  I've got a mile long history of Adaptec problems,
> > > usually due to BIOS-drivers being out of sync, as well as Adaptec's
> > > non-direct Linux support (and virtual no support before 1998).  Many
> > > Adaptec products (until the last year or two) didn't have EEPROMs
> > > on-board.  So I usually pulled my hair out trying to find the right
> > > driver for the right board-BIOS combo.
> > >
> > > I finally stopped using Adaptec completely as of late 1998.  No problems
> > > since.  Symbios Logic gets the call.  #1 reason why?  The are an
> > > OEM-focused company, which means they don't hide their specs.  Adaptec
> > > produces their own products, so they don't share their specs easily.
> > >
> > > This is the same reason why I hate Promise too versus most other ATA
> > > controller vendors, who are OEM-focused.
> > >
> > > -- Bryan
> > >
> > >
> >
> > --
> > Adam Bultman
> > adamb@glaven.org
> >
> >
> > _______________________________________________
> > Members mailing list
> > Members@kalamazoolinux.org
> > 
> 
> _______________________________________________
> Members mailing list
> Members@kalamazoolinux.org
> 
> 

-- 
Adam Bultman
adamb@glaven.org