New installation of 64Studio--Noted problems I need assistance with.
Hello all, I just recently installed 64Studio and I originaly had Ubuntu Studio. I mad e the move here because I read all the reviews on 64Studio and supposedly it is a more refined and overall better operating system than Ubuntu Studio. At any rate today is my first day poking around and checking things out. I have found many problems right off the bat. I am hoping there is a quick solution for each. First things first. This is my system: Dell Dimension 4600 P5 2.8ghz, and 1.5gig ram. Two hard drives, one 80gig IDE (Windows drive) and one SATA 500gig drive (64Studio and storage). I have a Sound Blaster Live installed (Dell OEM) and I do have a firewire interface. The problems I noticed are these: 1) No matter what I type in forums whether it is spelled correctly or incorrectly, I get a red line underneath it. So something is wrong with the systems spell checking. 2) Jack doesn't seem to be working properly. When I click on connections I notice nothing listed for the audio device. However under the MIDI connections there are devices listed. If I push start on Jack, I get this in Jack's message console: 20:54:33.671 Patchbay deactivated. 20:54:33.765 Statistics reset. JACK tmpdir identified as [/dev/shm] 20:54:33.849 MIDI connection graph change. 20:54:33.982 MIDI connection change. 20:54:37.310 Startup script... 20:54:37.310 artsshell -q terminate JACK tmpdir identified as [/dev/shm] can't create mcop directory Creating link /home/geo/.kde/socket-64studio. 20:54:37.590 Startup script terminated with exit status=256. 20:54:37.592 JACK is starting... 20:54:37.594 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p512 -n4 20:54:37.601 JACK was started with PID=4574 (0x11de). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 48000 creating alsa driver ... hw:0|hw:0|512|4|48000|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 512 frames, buffer = 4 periods ALSA: final selected sample format for capture: 16bit little-endian ALSA: got smaller periods 2 than 4 for capture ALSA: cannot configure capture channel cannot load driver module alsa no message buffer overruns 20:54:37.708 JACK was stopped successfully. 20:54:37.710 Post-shutdown script... 20:54:37.712 killall jackd jackd: no process killed 20:54:37.926 Post-shutdown script terminated with exit status=256. 20:54:39.623 Could not connect to JACK server as client. Please check the messages window for more info. JACK tmpdir identified as [/dev/shm] 3) Next problem...I cannot access my Windows hard drive. There are two partitions on that drive and if I select either one, I get this message: "Unable to mount selected volume: I click on details and get this: libhal-storage.c 1401 : info: called libhal_free_dbus_error but dbuserror was not set. process 4607: applications must not close shared connections - see dbus_connection_close() docs. this is a bug in the application. error: device /dev/hda1 is not removable error: could not execute pmount I found all these problems in less than a half hour within 64Studio. Thusfar I am a bit disappointed that for being a more refined OS over Ubuntu Studio that I found all these problems already. Supposedly the Sound Blaster Live should be recognized by the system and I can get it to play sound within 64Studio, but Jack doesn't seem to see it because it's Ins/Outs do not appear on Jack's connection list. So I am gathering that this is causing the error message and why Jack shuts down. But the question is why is it happening in the first place. Anyway, if someone could give me assistance in solving these issues, I would appreciate it very much. Thank You, Geo