Dave Phillips
2006-11-21 12:44:33 UTC
Greetings:
First, I apologize if this message is sent to the wrong group(s). I'm
not sure which is the preferred forum for reporting user-level
experiences with 64Studio.
Next, I want to send compliments to Daniel and Free for 64Studio. I've
been using it more & more, it looks as if it will soon replace my aging
Demudi installation as the default system here at Studio Dave. Nice
work, my compliments to the chefs. :)
Re: nVidia video: I discovered that the on-board nVidia chipset includes
only 64 MB video RAM, which I believe was why I couldn't get any decent
performance from the kernel nv driver. To be blunt, the Debian Way of
installing nVidia's own driver simply sucks, and I'll be going back to
using nVidia's installer when I receive my new video card. Meanwhile the
vesa mode works well, except that dragging a window in GNOME is
surprisingly s-l-o-w. Is GNOME so bloated that it causes this behavior
on an AMD64 3200 ?! Or is it a driver issue ?
Next question: What about tuning drives with hdparm on a 64-bit system ?
Does 64Studio automatically optimize drive performance or is that
something I need to do myself ?
How do I ensure that the snd-virmidi module gets loaded at boot ?
I've set up a complete build environment and have been compilling
various applications. The latest bleeding-edge DOSemu can now be built
for native 64-bit mode, I've been having fun running Voyetra's Sequencer
Plus Gold with it. How strange: a 16-bit DOS MIDI app running on a
64-bit Linux machine. I love it. I also built Leonard Ritter's Aldrin,
it works fine. Ditto for Ardour2.
I'm having trouble building 64-bit Csound5, the build fails at a problem
with FLTK :
g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -Wall
-g -gstabs -O2 -fPIC -DLINUX -DPIPES -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK
-DBETA -DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H
-DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I.
-IH -I/usr/local/include -I/usr/include -I/usr/X11R6/include
-Iinterfaces -I/usr/include/freetype2
frontends/fltk_gui/CsoundGlobalSettings.cpp
frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
'CsoundGlobalSettings::CsoundGlobalSettings()':
frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler error:
output_operand: invalid expression as operand
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
Preprocessed source stored into /tmp/ccDt1tHZ.out file, please attach
this to your bugreport.
scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
scons: building terminated because of errors.
If any C++ gurus out there have any suggestions for a fix I'd love to
hear 'em. Cs5 builds and runs without trouble in 32-bit mode, but it
should build for 64-bits too. John Fitch has compiled for AMD64, but he
stated that he used GCC3, I'm using GCC4.
So, I'm very pleased with 64Studio. Thanks again to the developers, and
I hope to make more reports soon.
Best,
dp
First, I apologize if this message is sent to the wrong group(s). I'm
not sure which is the preferred forum for reporting user-level
experiences with 64Studio.
Next, I want to send compliments to Daniel and Free for 64Studio. I've
been using it more & more, it looks as if it will soon replace my aging
Demudi installation as the default system here at Studio Dave. Nice
work, my compliments to the chefs. :)
Re: nVidia video: I discovered that the on-board nVidia chipset includes
only 64 MB video RAM, which I believe was why I couldn't get any decent
performance from the kernel nv driver. To be blunt, the Debian Way of
installing nVidia's own driver simply sucks, and I'll be going back to
using nVidia's installer when I receive my new video card. Meanwhile the
vesa mode works well, except that dragging a window in GNOME is
surprisingly s-l-o-w. Is GNOME so bloated that it causes this behavior
on an AMD64 3200 ?! Or is it a driver issue ?
Next question: What about tuning drives with hdparm on a 64-bit system ?
Does 64Studio automatically optimize drive performance or is that
something I need to do myself ?
How do I ensure that the snd-virmidi module gets loaded at boot ?
I've set up a complete build environment and have been compilling
various applications. The latest bleeding-edge DOSemu can now be built
for native 64-bit mode, I've been having fun running Voyetra's Sequencer
Plus Gold with it. How strange: a 16-bit DOS MIDI app running on a
64-bit Linux machine. I love it. I also built Leonard Ritter's Aldrin,
it works fine. Ditto for Ardour2.
I'm having trouble building 64-bit Csound5, the build fails at a problem
with FLTK :
g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -Wall
-g -gstabs -O2 -fPIC -DLINUX -DPIPES -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK
-DBETA -DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H
-DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I.
-IH -I/usr/local/include -I/usr/include -I/usr/X11R6/include
-Iinterfaces -I/usr/include/freetype2
frontends/fltk_gui/CsoundGlobalSettings.cpp
frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
'CsoundGlobalSettings::CsoundGlobalSettings()':
frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler error:
output_operand: invalid expression as operand
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
Preprocessed source stored into /tmp/ccDt1tHZ.out file, please attach
this to your bugreport.
scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
scons: building terminated because of errors.
If any C++ gurus out there have any suggestions for a fix I'd love to
hear 'em. Cs5 builds and runs without trouble in 32-bit mode, but it
should build for 64-bits too. John Fitch has compiled for AMD64, but he
stated that he used GCC3, I'm using GCC4.
So, I'm very pleased with 64Studio. Thanks again to the developers, and
I hope to make more reports soon.
Best,
dp