[PlanetCCRMA] Re: From zero to DAW in 2 hours !

Bal Dobe baldobe2000 at yahoo.de
Fri Feb 17 17:37:01 PST 2006 

So the Ram appears to be ok, no errors after about 50mins.

Lets try and figure out the Kernel Panic Problem:

Ccrma boot
I have booted up into FC4 ccrma
Uname -r 

Gives me 2.6.12-0.21.rdt.rhfc4.ccrma

If I now type 

Init 6

I get:

A whole load of characters in a dos like screen and finally 

Kernel Panic - not syncing: Fatal Exception in interrupt.

The only way to move forward is hit the reset button.

There appears to be nothing like oops in the /Var/log/messages file.

Non ccrma boot.
If I boot into FC 4

Uname -r 

Gives me 2.6.11-1.1369_FC4
If I now type 

Init 6

I get:

Bash: init: command not found.

So to logout I do desktop>logout>logout>

At the login screen I do shutdown and I then get

A whole load of characters in a dos like screen which I normally get and
then  I get:

[<c0103c0e>] common_interrupt+0x1a/0x20

and the only way out is to hit the reset button.

> After this is done I get the kernel error. 

"Wait, at this point you have _not_ installed the Planet CCRMA kernel
(that would be "apt-get install planetccrma-core-edge" followed by a
reboot to try it out) and you have not installed the Planet CCRMA
packages (that would be "apt-get install planetccrma-audioapps", or one
of the other meta packages). If that is all you did you have just
upgraded mostly Fedora Core packages."

I only rebooted the machine twice.

"# PART 1
#
#   For installing Planet CCRMA I basically followed
#   http://ccrma.stanford.edu/planetccrma/software/installtwosix.html
#   But here is the more compact break down for MY personal actions
#

# install CCRMA version of apt
rpm -Uvh
http://ccrma.stanford.edu/planetccrma/apt/rpms/apt-0.5.15cnc6-4.rhfc4.ccrma.
i386.rpm

# install GPG key for verifying packages
rpm --import
http://ccrma.stanford.edu/planetccrma/RPM-GPG-KEY.planetccrma.txt


# update apt package lists
apt-get update

# install CCRMA kernel and ALSA drivers
apt-get install planetccrma-core-edge

# reboot in to new kernel
# (note, if you run this as a script, it will NOT automatically #  pick up
where it leaves off after this :) "

init 6   {first reboot} everything ok with no kernel error.


"# PART 2
#  I raised volume levels on mixer and tested sound
alsamixer    play /usr/share/sounds/KDE_Startup_new.wav

# install all cool audio/video apps
apt-get install planetccrma-audiovideoapps

# At THIS point qjackctl, ardour, etc is working.

# make sure EVERYTHING is up to date
apt-get update
apt-get dist-upgrade

Now do the second reboot and this is when the kernel error occurred.

Hope that clarifies.

Bal.




-----Original Message-----
From: Fernando Lopez-Lezcano [mailto:nando at ccrma.Stanford.EDU] 
Sent: Saturday, February 18, 2006 1:07 AM
To: Bal Dobe
Cc: 'David Slimp'; planetccrma at ccrma.Stanford.EDU
Subject: RE: PlanetCCRMA] Re: From zero to DAW in 2 hours !

On Sat, 2006-02-18 at 00:45 +0000, Bal Dobe wrote:
> Fernando,
> 
> Thanks for your time and comments on this issue.
> 
> OK lets try and think this through logically, please bear with me on this
I
> am relatively new to  Linux and am still learning.
> 
> Kernel Panic problem;
> FC4 installs on my machine fine, I can also install all the ccrma
audiovideo
> apps.  Following David's instructions DAW in 2 hours I do not get an error
> at the first reboot,via init 6
> 
> So I install FC4:
> 
> "just have auto partitioning.... don't select "selinux".
> .. everything just very generic.

(selinux is probably not related to the problem you are having)

> start the GUI, but don't change to KDE
> for now... just do an "init 6" and see if you get that same error.
> Hopefully you'll reboot just fine."
> 
> I was able to reboot after the FC4 install.
> 
> Then I did the planet ccrma installs
> 
> "Log in again, and only upgrade the FC4 stuff first:
> rpm -Uvh
> http://ccrma.stanford.edu/planetccrma/apt/rpms/apt-0.5.15cnc6-4.rhfc4.cc
> rma.i386.rpm
> rpm --import
> http://ccrma.stanford.edu/planetccrma/RPM-GPG-KEY.planetccrma.txt
> apt-get update
> apt-get upgrade"
> 
> After this is done I get the kernel error. 

Wait, at this point you have _not_ installed the Planet CCRMA kernel
(that would be "apt-get install planetccrma-core-edge" followed by a
reboot to try it out) and you have not installed the Planet CCRMA
packages (that would be "apt-get install planetccrma-audioapps", or one
of the other meta packages). If that is all you did you have just
upgraded mostly Fedora Core packages. 

> The problem is repeatable, it has happened several times now.

Sorry, I'm still unclear on exactly when the problem is happening. 
The important thing is: which kernel are you running just before you get
the kernel panic? (if it is a kernel panic). 

To find out which kernel you are running type: "uname -r" _before_
triggering the problem. As I said before it is unlikely that the problem
is ram (specially after you have tested it with memtest86). 

If the kernel printed by uname contains the string "rhfc4.ccrma" in the
release part then it is a Planet CCRMA kernel, otherwise you are still
running the Fedora Core kernel. 

Just a quick question: when the kernel panic happens the machine goes
completely catatonic, right? And the only option you are left with is
the reset button or a power cycle? Just to make sure it is indeed a
kernel panic (or a similar kernel problem). After you reboot from it you
may find traces of the problem in the system log (/var/log/messages),
search for the word "Oops" there. 

> RAM problem.
> Surely bad ram is bad ram so FC4 should not be able to work not just FC4
> ccrma, or am a mistaken?
> 
> I am doing a memtest86 on my machine at the moment, the machine is over a
> year old and was thoroughly tested continuously for about 2 days, upon
being
> built. No Ram errors were found. There are still no errors after 30 mins
and
> one pass.

Then probably the ram is fine. 

First we have to determine what kind of problem you are having, and
under which kernel. If it is indeed a kernel problem triggered by a bug
somewhere in it the solution is, sorry, don't run that kernel :-)

-- Fernando


> If this is the problem, how can I fix it? Buy new ram, how do I know that
> will work? Can I just buy more ram and continue to use the ram I have in
> conjunction with the new ram?
> 
> As you can see I seriously hope that it is not a ram issue.
> 
> Alternative solutions.
> 
> Load FC4 on another HDD?
> Could the problem be the HDD?  I have three HDDs in the machine and I am
> only using linux on one Maxtor 200Gig drive?  I also have a Seagate,
should
> I try and do a reinstall on the Seagate drive and see if that makes any
> difference?
> 
> If it works on the Seagate then I would be happy to move all of my windows
> applications to the Maxtor 200G drive and use the Seagate for linux.
> 
> Reinstall FC3 and ccrma for FC3?
> Should I try and install FC3 an do a ccrma install on that?  Can I install
> that on one of my other partitions without upsetting the FC4 install?
> Remember I had problems with the sound on the FC3 install.
> 
> Is the FC3 ccrma install more stable albeit with latency not as good as
FC4?
> I am happy to wait for FC4 to be sorted out and use FC3 in the meantime.
> Could I leave my FC4 install and start using a FC3 ccrma kernel?
> 
> Hope that somebody can help.



__________ NOD32 1.1413 (20060217) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 10788 bytes
Desc: not available
URL: <https://cm-mail.stanford.edu/pipermail/planetccrma/attachments/20060217/ba9e47eb/attachment.bin>

More information about the PlanetCCRMA mailing list