On Thu, May 30, 2002 at 08:38:23PM -0400, Chad Leigh -- Shire. Net LLC wrote:
On Thursday, May 30, 2002, at 08:31 , Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it
wouldnt
run XFree. Everything worked well besides X. Since a workstation
Someone mentioned this MTRR problem earlier, I even tried a patch but it was
unsuccessful. I think I'll make a new try with FreeBSD 4.6, maybe things
will be more successful then.
On Thu, May 30, 2002 at 05:53:07PM -0700, Jordan K Hubbard wrote:
I'll bet you wouldn't have any trouble running
On Thu, May 30, 2002 at 09:16:25PM -0400, Scott wrote:
At 10:26 2002/05/31 +0930, Greg 'groggy' Lehey wrote:
On Friday, 31 May 2002 at 2:31:32 +0200, Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides
On Tue, Jun 18, 2002 at 05:24:38PM -0400, Scott Robbins wrote:
On Tue, Jun 18, 2002 at 10:17:57PM +0200, Morsal Rodbay wrote:
Someone mentioned this MTRR problem earlier, I even tried a patch but it was
unsuccessful. I think I'll make a new try with FreeBSD 4.6, maybe things
will be more
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
nothing wrong with the hardware which means it's a FreeBSD issue.
To
On Thursday, May 30, 2002, at 08:31 , Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it
wouldnt
run XFree. Everything worked well besides X. Since a workstation
without X
is useless I was forced to switch to WinXP and it's very stable so
there is
Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
nothing wrong with the hardware which means
On Thu, 2002-05-30 at 19:31, Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
nothing wrong
I'll bet you wouldn't have any trouble running -stable on it. There was a problem
with MTRR support which still needs a little fixing in order to shut down properly but
that's nowhere near as bad as X not running. Fix should be in FreeBSD 4.6 as well.
- Jordan
On Thursday, May 30, 2002, at
On Friday, 31 May 2002 at 2:31:32 +0200, Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
nothing wrong with the hardware which means
At 10:26 2002/05/31 +0930, Greg 'groggy' Lehey wrote:
On Friday, 31 May 2002 at 2:31:32 +0200, Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced
Jordan K Hubbard wrote:
I'll bet you wouldn't have any trouble running -stable on it. There
was a problem with MTRR support which still needs a little fixing in
order to shut down properly but that's nowhere near as bad as X not
running. Fix should be in FreeBSD 4.6 as well.
The MTRR
I haven't read the AMD errata docs so I can't comment on that, but it
appears to be an issue with AMD CPUs and certain support chipsets, I
believe the early VIAs. Reading the cvs logs for the MTRR support
code will certainly yield more detailed information (and author
attribution) than I've
Frank Mayhar writes:
Morsal Rodbay wrote:
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt
run XFree. Everything worked well besides X. Since a workstation without X
is useless I was forced to switch to WinXP and it's very stable so there is
nothing wrong with
Lehey
Sent: Friday, December 28, 2001 2:40 AM
To: FreeBSD Questions; FreeBSD Hackers
Subject: Does FreeBSD have a problem with some AMD processors?
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey stood up and spoke:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP
It seems Greg Lehey wrote:
Information that could be interesting is (here my values):
Processor:AMD Duron 850
Motherboard: ECS K7VZA
Memory: 1 128 MB SIMM, 100 MHz.
What FreeBSD version are you using ? I have put a fix for the 686b
southbridge bug in -current, but it is
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP 1700. Last
On Fri, 28 Dec 2001 11:57:44 +0100, Nils Holland wrote:
Now, I have found a lot of similar stories on the web. I guess some
mainboard manufacturer's (and even VIA as a chipset manufacturer) seem to
care very little about quality assurance. That's actually sad: AMD's best
processors aren't worth
Greg,
Do not forget to check your power supply make/model. If you search on google
for AMD's recommended hardware list, double check you're power supply is
listed for your cpu.
I had the unfortunate experience of having a power supply explode and catch
on fire, because I read the model number
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP 1700. Last
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP 1700. Last
Munish Chopra wrote:
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an
On Fri, Dec 28, 2001 at 02:46:12PM -0600, Glenn Johnson stood up and spoke:
As far as I can tell though if I set the memory clock to
100MHz the problem goes away completely, or at least I have not observed
it happen yet.
So it's PC133 RAM but only works properly at 100 Mhz? Well, I guess I
It seems Glenn Johnson wrote:
I have had this exact problem. I have an Epox 8KTA board with a
1GHz Athlon (Thunderbird) with 256MB of PC-133 memory. I would
consistently get random errors, usually during a compilation, using
the default BIOS settings. After fiddling with some of the BIOS
On Fri, Dec 28, 2001 at 11:12:40PM +0100, Søren Schmidt stood up and spoke:
From what I can tell the newest Epox BIOS for the 8kta3 does *not*
install the 686b fix when it doesn't detect a SBLive! sound card,
nice but not good enough :/
There are many information on the 686B bug available
On Fri, Dec 28, 2001 at 02:46:12PM -0600, Glenn Johnson wrote:
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a
On Fri, Dec 28, 2001 at 11:12:40PM +0100, Søren Schmidt wrote:
It seems Glenn Johnson wrote:
I have had this exact problem. I have an Epox 8KTA board with a
1GHz Athlon (Thunderbird) with 256MB of PC-133 memory. I would
consistently get random errors, usually during a compilation,
On Fri, 28 Dec 2001 22:47:58 +0100, Nils Holland wrote:
On Fri, Dec 28, 2001 at 02:46:12PM -0600, Glenn Johnson stood up and spoke:
As far as I can tell though if I set the memory clock to
100MHz the problem goes away completely, or at least I have not observed
it happen yet.
So it's PC133
On Friday, 28 December 2001 at 13:23:50 +0100, Søren Schmidt wrote:
It seems Greg Lehey wrote:
Information that could be interesting is (here my values):
Processor:AMD Duron 850
Motherboard: ECS K7VZA
Memory:1 128 MB SIMM, 100 MHz.
What FreeBSD version are you using ? I
On Friday, 28 December 2001 at 6:21:04 -0800, Keith Simonsen wrote:
Greg,
Do not forget to check your power supply make/model. If you search on google
for AMD's recommended hardware list, double check you're power supply is
listed for your cpu.
This wouldn't explain why it works fine under
On Friday, 28 December 2001 at 14:46:12 -0600, Glenn Johnson wrote:
On Fri, Dec 28, 2001 at 06:10:09PM +1030, Greg Lehey wrote:
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a
On Friday, 28 December 2001 at 23:12:40 +0100, Søren Schmidt wrote:
It seems Glenn Johnson wrote:
It is really hard for me to say if this is FreeBSD specific because I do
not tend to stress the system much when I have Linux running. My wife
has an identical system running Windows 98SE and
On Sat, 29 Dec 2001, Greg Lehey wrote:
This is a Duron, so it has a 100 MHz memory clock anyway.
Greg
Not necessarily; athlons durons use ddr clocking, so the processors are
200 or 266, effectively. Most motherboards let you set the memory bus to
either 100 or 133, independent of
I've been using AMD processors almost exclusively in my main work
machines for over 4 years, and I've been very happy with them. I'm
currently running a K6/233, a K6/333, an Athlon 750, a Duron 850 and
an Athlon XP 1700. Last August, though, I bought a machine which gave
me a lot of trouble,
36 matches
Mail list logo
