-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: > >> 64 Studio is default. >> >> For a lot of your posts this was not the case. Do not lump those self >> imposed problems in with the default install of 64Studio. > > That's true, but at the moment I'm also not fine with the default 64 > Studio. I'm able to run an unstable heavy setup and maybe it will be > possible to get a stable, but simple setup. I remember that my old > hardware was stable with 64 Studio 2.1rc1, but there were not enough > resources to make music, now there are enough resources, but more than > enough crashes too. > >>>> My main machine runs openSUSE, and the JAD distro worked fine on >>>> that, >>> JAD comes with enlightenment 17 by default and enlightenment 17 isn't >>> stable. Or is there a new JAD released, not using enlightenment? >> I have never used these, but I am pretty sure you are not limited to >> E17. I would be more than surprised to find out that E17 was the _only_ >> choice. > > JAD is a real Suse, so you can use all Suse repositories. I think there > will be no other distro having such a great offer for software like Suse > and community repositories for Suse will offer. But you must have much > experience and good luck when using them, because they are most times > the newest of the new. That must not be bad, e.g. the actual svn of > Hydrogen, default for Suse repositories, comes with the patch, that will > sync Ardour and Hydrogen when using Jack transport, but for WM/DEs the > latest versions can be full of pitfalls. I only wonder that JAD should > be without troubles, while the default install comes with e17, a very > interesting DE, but also one that isn't stable, so it's a stupid choice > for a DAW and nobody can say JAD will be stable by default. You have to > change the DE and we were writing about not to change default installs.
E17 has been stable for me for more than a year. YMMV. > >> If you are building a new version then make a >> .deb package out of it. It will supersede your installed version. Of >> course if there are a lot of dependencies that need updating, this may >> not be an option. > > I'm not able to build a package for Debian, here Suse has a big > advantage, instead of "make install" most times "checkinstall" is fine, > not instead of all "make install"s and not when compiling with exotic > compilers, but for most cases. "checkinstall" builds a RPM, a package > for Suse. > Your choice. The howto is pretty easy to follow. >>> I'll [...] look for a new BIOS update >> RT apps are really demanding, and can often expose bugs in the BIOS or >> in the drivers themselves. I personally experienced this with my laptop. > > There seems to be very often updates for my BIOS, since today I've got > the latest, but didn't run audio applications today. Unfortunately > there are no comments about Linux or my hardware for the updates. > >>> It might be interesting if somebody else has an ASUS M2A-VM HDMI, I >>> especially bought the ASUS, because my old mobo is an ASRock, and I >>> won't by an ASRock again. >> I have this board and it sucks. It plays DVDs and and xvids for the TV, >> running a vanilla install of Windows XP. > > I can't say something about this board and Windows by own experiences, It sucked under linux, and it sucks a little less under windows. > because I don't have a Windows. I disabled HDMI and I know that > Cinelerra is fine with Suse 11.0, but I don't know anything about xvids > for TV etc., the integrated graphics sucks, but there's still the PCIex > slot for a graphic card. > > Isn't this board fine with Linux DAW applications or rt kernels? > >> Quite simply, I gave up trying >> to make it work properly. It is the reason I now avoid AMD/ATI. Soon I >> can ditch my HP laptop from hell (nVidia chipset, AMD CPU, and two years >> of pain that I will not get back). In the face off all this, my 939 >> based AMD machines run flawlessly. If buying new there can be only >> Intel :) >> >> It is almost stable under windows too. Low latency work blue screens >> it, (memtest came up clean btw). > > I won't have enough money for a new mobo for a long time, resp. I will > spend 50,- EUR for a graphic card, maybe still this year. I don't think > I'll get a better mobo including a Linux compatible graphics for around > 50,- EUR. > That is unfortunate. The MB is more important than the video card. Intel is currently the better choice, especially with integrated Intel video (it works out of the box). I remember saying as much when you were looking to purchase. > My ASRock was fine with Windows but not with Linux and all people say > that ASUS should be good for Linux, also someone from the list mentioned > this board, because of the price and because I needed better hardware > for Linux. Maybe you were the one :D. The problem is, that nobody knows > which hardware will be fine with Linux, unless it's oldish hardware, > that than might not have enough resources for Linux in the near future > or it is Intel hardware and not everybody has the money to buy Intel > hardware. With all things being equal, the chipset is more important than the name on the sticker. I do tend to buy ASUS motherboards, but I also pay attention to the chipsets on the particular board I am buying. >>> It seems to be, that my hardware isn't broken and I'm using the >>> default >> Yes it is. It is broken by design. > > Is this the answer to the question above? "Isn't this board fine with > Linux DAW applications or rt kernels?" I have had nothing but trouble with this chipset. So I avoid it. I recommend others do the same. I did not try an RT kernel with it, it was a headache on a standard kernel. Best to avoid it if you can. > That might also be an explanation for the reason why a Linux compatible > controller I bought and gave back by warranty, but with loss of money, > wasn't compatible with Linux for my hardware. Not sure. > So I bought hardware that wasn't fine for a Linux DAW and spend again > money for hardware that also isn't fine for Linux DAWs? > Yes, you bought a motherboard that does not work very well. I was not using it for a DAW and I had a lot of problems. That is why I gave it away. > Thank you :), I hope the latest BIOS update has solved the troubles :S, > if not Bill Gates seems to have good luck, resp. if so, it's to consider > which way I'll go, if there isn't another way for me, than to use > Windows. Bill Gates shouldn't benefit from my suffering. It will take a combination of BIOS patches and support from newer kernels to solve your problems. It could be a while. If you really are impatient you may wish to learn how to patch and compile your own kernel. Otherwise, wait. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIvG6swRXgH3rKGfMRAgclAJ4i/Ef4UE0UAo1mhZGwgwp1zNMtfgCgq6ns 7KMvbW1fenJXqnJHZnpIUSs= =E27s -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
