Re: kernel 2.1.129 on Alpha Miata

[Jeff DeMaagd <jdemaa17 calvin edu>]

I have a similar system, but I've had no drive problems.  The only problem
I have is getting the built-in tulip chip to work on 2.1.129. Maybe Loic's
patches don't work on exp. kernels?

As for the keyboard locking out on you, I had to 'correct' the sound
configuration on 2.0.35.  Don't ask, I have no clue why....

What compiler?  egcs-1.1 and up seem to have a bit of trouble generating
totally stable code.  They won't compile a certain module in 2.0.36, and
the X SVGA server trashes the console, the only fix is a soft boot.

JRDM

Some comments on what others wrote (some clipping):

> Hey... I'm running RH5.2 with 2.0.35 and I'm having some similar 
> problems too... see below...
> 
> >	Has anyone gotten the 2.1.129 kernel to run successfully on the Alpha
> >PWS Miata?  I tried to use it and there are some real problems:
> >
> >	1) takes forever to mount local partitions
> 
> I've had this problem since day one when I installed RH5.2... at first I 
> thought it might be a problem with my SCSI... but now that I'm not the 
> only one.... hmmm... anyways.. yes, it takes about 2 to 3 minutes just 
> to mount my root partition.... on a similar Intel system, it takes less 
> than 10 seconds.....

It would help to know if you've tried RH5.1, and make sure you are sure
the SCSI system is connected and terminated correctly.  Do you have a
QLogic or Adaptec SCSI?  The Qlogic ones gave me trouble.  I heard they
are better, but at that time, Linux's support for it & PWS wasn't good.

> >	3) does something bad so that after I ctrl-alt-del and go back to milo
> >and run a good kernel, the keyboard is disabled and the cd-rom flakes.
> 
> Yup, I've also had this problem since day one.... if I reboot from 
> MILO... my system hangs during boot... if I cold boot it (reset 
> switch)... I'm fine.... My system is total SCSI... 

My situation isn't as severe that I remember, but I get some similar
problems on a soft (warm) reset of an experimental kernel.

> >	These behaviors seem odd since the kernel is supposed to be reasonably
> >stable...

Ditto.