Yes, but with the inevitable corporate shake up that will occur in
ATi's management at the upper levels because of the buyout, things
will have to change.
It's not like their drivers or their attitude towards GNU/Linux could
get any worse.
http://airlied.livejournal.com/31180.html
On 8/16/06, M
Am Mittwoch, 16. August 2006 10:44 schrieb Matteo Vescovi:
> On 08/16/2006 06:56 AM, Hans wrote:
> > I one time got 600FPS (ATI radeon X700), but after a restart of x-server,
> > I got 50 FPS again. So I think, something does prevent the speed.
> >
> > Could you send me your /etx/X11/xorg.conf ?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/2006 03:24 AM, Robert Isaac wrote:
> That might change, though, now that AMD owns ATi. They _might_
> release specs :-)
http://news.com.com/2061-10791_3-6104655.html
Mmhh, it seems like it won't change so soon. :-(
Take care.
mfv
- --
Ma
Am Dienstag, 15. August 2006 21:57 schrieb Matteo Vescovi:
> Hi Hans,
>
> On 08/15/2006 02:38 PM, Hans wrote:
> > It seems, that in last kernel 2.6.17 this problem is solved. I read the
> > documentation of the kernel, and (as you wrote), these timers just
> > misbehave if you have a chipset of ATI
It gives that ATI sucks! :-)
That's all.
That might change, though, now that AMD owns ATi. They _might_
release specs :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/15/2006 11:23 PM, Lennart Sorensen wrote:
> But my pathetic GF6200 is getting 1250fps... What gives?
It gives that ATI sucks! :-)
That's all.
> Len Sorensen
mfv
- --
Matteo Vescovi
System Administrator
Studio Vescovi Progettazioni
-BEGIN
On Tue, Aug 15, 2006 at 09:57:43PM +0200, Matteo Vescovi wrote:
> Here fglrx 8.27.10 is working fine... about 480 fps, not 600 but that's
> not bad.
> Your situation sounds strange.
But my pathetic GF6200 is getting 1250fps... What gives?
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Hans,
On 08/15/2006 02:38 PM, Hans wrote:
> It seems, that in last kernel 2.6.17 this problem is solved. I read the
> documentation of the kernel, and (as you wrote), these timers just misbehave
> if you have a chipset of ATI. This is the case on
Am Dienstag, 15. August 2006 15:14 schrieb Lennart Sorensen:
> On Tue, Aug 15, 2006 at 06:27:32AM +0200, Hans wrote:
> > Sorry, I maybe did not ask correctly. It is not the problem, that the
> > time is not shown correctly. The background is, that other timings are
> > running in double speed, too
On Tue, Aug 15, 2006 at 09:22:43AM +0200, Koen Vermeer wrote:
> /usr/src/linux-source-2.6.17/Documentation/kernel-parameters.txt says:
> disable_timer_pin_1 [i386,x86-64]
> Disable PIN 1 of APIC timer
> Can be useful to work around chipset bug
On Tue, Aug 15, 2006 at 06:27:32AM +0200, Hans wrote:
> Sorry, I maybe did not ask correctly. It is not the problem, that the time is
> not shown correctly. The background is, that other timings are running in
> double speed, too (i.e. keyboard clock and some other). This is a known
> problem on
Am Dienstag, 15. August 2006 10:51 schrieb Matteo Vescovi:
> Hi Hans!
>
> On 08/15/2006 06:27 AM, Hans wrote:
> > Sorry, I maybe did not ask correctly. It is not the problem, that the
> > time is not shown correctly. The background is, that other timings are
> > running in double speed, too (i.e. k
Hi Hans!
On 08/15/2006 06:27 AM, Hans wrote:
Sorry, I maybe did not ask correctly. It is not the problem, that the time is
not shown correctly. The background is, that other timings are running in
double speed, too (i.e. keyboard clock and some other). This is a known
problem on AMD mobile pro
Op di, 15-08-2006 te 06:27 +0200, schreef Hans:
> My
> question aimed to an technical answer, if the commands "disable_timer_pin_1"
> and "noapictimer" are doing the same, or if they both solve the mentioned
> problem in different ways.
/usr/src/linux-source-2.6.17/Documentation/kernel-paramete
Am Montag, 14. August 2006 22:22 schrieb Lennart Sorensen:
> On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote:
> > ntp-simple couldn't be easier to install & use and will keep your system
> > time synchronized with the national time servers. I also would recommend
> > ntpdate if you shu
On Monday 14 August 2006 03:13 pm, Gnu-Raiz wrote:
> On Monday 14 August 2006 14:40, Mike Reinehr wrote:
> > On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote:
> > > On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote:
> > > > Hello !
> > > > Just an easy question:
> > > >
> > > > Is there a diff
On Monday 14 August 2006 14:40, Mike Reinehr wrote:
> On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote:
> > On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote:
> > > Hello !
> > > Just an easy question:
> > >
> > > Is there a difference between "disable_timer_pin_1" and
> > > "noapictimer" at s
On Monday 14 August 2006 03:22 pm, Lennart Sorensen wrote:
> On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote:
> > ntp-simple couldn't be easier to install & use and will keep your system
> > time synchronized with the national time servers. I also would recommend
> > ntpdate if you shu
On Mon, Aug 14, 2006 at 02:40:58PM -0500, Mike Reinehr wrote:
> ntp-simple couldn't be easier to install & use and will keep your system time
> synchronized with the national time servers. I also would recommend ntpdate
> if you shut your system down frequently. Ntpdate will set the time on boot,
On Monday 14 August 2006 01:40 pm, Gnu-Raiz wrote:
> On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote:
> > Hello !
> > Just an easy question:
> >
> > Is there a difference between "disable_timer_pin_1" and
> > "noapictimer" at startup in grub ? If yes, what is the difference
> > ?
> >
> > (Thi
On Monday 14 August 2006 11:07, Hans-J. Ullrich wrote:
> Hello !
> Just an easy question:
>
> Is there a difference between "disable_timer_pin_1" and
> "noapictimer" at startup in grub ? If yes, what is the difference
> ?
>
> (This command is needed to get the clock running correct)
>
> regards
>
>
Hello !
Just an easy question:
Is there a difference between "disable_timer_pin_1" and "noapictimer" at
startup in grub ? If yes, what is the difference ?
(This command is needed to get the clock running correct)
regards
Hans
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
22 matches
Mail list logo
