-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: > Hi :) > > some minutes ago I suggested someone in the forums, to document each > step he did or will do, for a bugreport, because he can't install 64 > Studio. I guess for troubles like that, a detailed bugreport is useful > and such a problem easily can be solved. > Appropriate information is more useful than a mountain of information. I love nothing more than to spend my free time sifting through a massive amount of unrelated data to help solve someone else's problem. For those that are not native English speakers that last sentence is an example of sarcasm. I would instead encourage you to promote the idea of smart questions. I know this has been covered extensively in the recent past. I am pretty sure you know my mind on this issue.
> I need to do some jobs, so I installed Windows XP Pro to get a usable > multimedia production workstation. As a side effect I can rule out or > affirm broken hardware, as the cause for unusable Linux multimedia > production workstations. > I think you misunderstand the complicated nature of hardware support under Linux. Sometimes it works great, like all the hardware in my DAW, sometimes not so much. I among others have stable, production, Linux based multimedia workstations. I am very sorry that you have not been able to experience this. Most of this hinges on the vendors doing just a little bit to get their hardware supported. They do not even have to write the drivers themselves. The sad reality is that many manufacturers do nothing or worse actively work against open source drivers. > Until now I only set up the graphics. Using the ATI software, I can > optimize the refresh rates, so everything is fine with my graphics and > monitor. > > When I changed from Suse to 64 Studio with my old NVidia, it was > possible to set up the refresh rates for Suse, while it wasn't possible > for 64 Studio. It wasn't possible to do it such perfect like I can do it > now, with the ATI software for Windows, but it was okay. Today, with my > ATI, Suse and 64 Studio aren't able to set the refresh rates. > I guess I still do no understand this problem. I am pretty sure you can set whatever you want in the xorg.conf file. Of course if you are using the proprietary driver all bets are off, since you/we have only to hope that ATI chose to support the particular feature you are looking for. The proprietary drivers tend to be worse for the open source OSs than for their proprietary counterparts. It is what it is. Or is the complaint that there is no GUI tool to do what you need? > I'm disappointed that bugs like that are often waved aside as something > that can't be. Since I have not been able to replicate the problem with any monitor and video card combination I own or have access to (which is a lot btw), all I can say is that I have no evidence that this bug exists. I will not say that it cannot exist, but I remain sceptical until I can see it myself. All I can suggest is that you try a recent version of Xorg and a recent kernel (so the latest Ubuntu is not a bad start, SuSe is probably OK, though I have not touched SuSe in years). Play around with the xrandr utility. > > Sound wasn't set up, I'll do it within the next days. I can't say if the > audio hardware is or isn't broken. > Probably depends on the driver, which is probably going to be OK for XP. The RME fireface works fine under Windows, but will likely never see support under Linux. So is the hardware broken? I would say that the business plan is broken, but the hardware works fine in some circumstances, such as particular OSs. For me it is useless and the ALSA/FFADO people, the hardware may be considered as broken as there is no easy way to write drivers for it. Keep in mind, one of the driving forces that pushed me to use Linux for my audio work, was an audio interface I used 8 years ago. It was only supported by Windows 98 and there was no driver for 2k/XP (and there never was nor will there be). The hardware itself is fine, but is useless to me. As such I would consider it broken. The point is that saying that hardware is broken may depend on your point of view (ie. context). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklhv/YACgkQwRXgH3rKGfO49wCfTZyJKoJpyFk/i4lANxHaxYaV IEAAoKMNlj67D/FcLw1eO9HPfNZN3Vyh =VCg3 -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
