[PlanetCCRMA] (Slightly OT) CCRMA ate my machine!!

Fernando Pablo Lopez-Lezcano nando@ccrma.Stanford.EDU
Thu Mar 4 18:35:03 2004

> OK, not exactly true, but as it happened while playing with audio bits
> I'm hoping someone else on the list has experienced something similar.
> I posted to the list a week or so ago about problems with fluidsynth
> connecting to JACK.  With the package updates yesterday I decided to
> update my machine (a laptop, Toshiba Satellite TE2000) to see if the
> problem was still there.  It was.  I noticed rosegarden had updated. 
> Interested in just checking the version, I started it with nothing else
> running.  The result? The sequencer crashed.  No big deal I thought. 
> Having checked the version (which is all I wanted to do and hadn't
> seemed to change) I started up JACK to go back to my "real" problem.  Or
> tried to.  Now I was getting an assertion on startup (either by qjackctl
> or directly).  I can't tell you what it is, keep reading and you'll get
> an idea why :(
> OK, reboot the machine an see if it goes away.  I don't know as now the
> machine won't boot with any of the 4 kernels I have on the machine. 
> Each stops with "cannot open initial console".  And I can't get it to go
> any further.  Of course I can emergency boot from CD, but nothing looks
> out of place and I don't know enough as to where to start looking.
> Suggestions? Pointers?

Ouch... I'm sorry...... I've never seen this happen. All kernels??

A bit of googling got me this:

When in the boot process do you get that message?
In the thread somebody says:

"make initrd manually after kernel image install and then run
grub-install, that should do it."

But I'm not sure what that would fix as I don't understand what is
really happening. What other messages do you see around the "cannot open
initial console" message?

-- Fernando