[64studio-users] Where can I find the boot messages? And a boot curio

Icemouse ralf.mardorf at alice-dsl.net
Sun Aug 5 11:00:31 BST 2007


I'm sorry if this mail should have been send more then one time, my 
provider has got troubels with the server.

Hi :)

I need to read the boot messages but can't find a file like
/var/log/boot.msg. Maybe there's an information about a wrong chipset,
because I've problems with my NVIDIA. While scrolling I can read
something about a wrong chipset for Intel 800/900 graphic-cards or
something like this.

Not a problem but something remarkable, that might has something to do
with the shared swap:

Booting Suse 10.2
Running jackd -R -d alsa | qjackctl
Jack failed

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Jack failed

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Everything is fine

Rebooting Suse 10.2
Didn't use Jack

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Jack failed

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Everything is fine.

Rebooting XP-MCE ;)
Nearly killed my speakers :O

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Everything is fine

Rebooting another Suse, 10.1
Didn't use Jack

Rebooting 64 Studio 2.0 32-bit
Running jackd -R -d alsa | qjackctl
Everything is fine

Rebooting Suse 10.2
Didn't use Jack

Rebooting 64 Studio 2.0 32-bit
Jack failed
$ jackd -v -R -d alsa | qjackctl
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
JACK compiled with System V SHM support.
server `default' registered
Warning: no locale found: /usr/share/locale/qjackctl_de_DE.UTF-8.qm
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x805a0e8 fd = -1
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
cannot load driver module alsa
starting server engine shutdown
freeing shared port segments
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
no message buffer overruns
cleaning up shared memory
cleaning up files
unregistering server `default'

Rebooting 64 Studio 2.0 32-bit
Jack is/was running fine :)

Greetz,

Ralf




More information about the 64studio-users mailing list