I am almost certain this is not a Suse issue, but I thought I might inquire
just in case.
As stated before, I have a Tyan K8W motherboard with 4Gb of DDR400 memory
running Suse 9.0 AMD64 with the patch kernel.
The BIOS registers 4Gb of memory, but the operating system only shows ~2.5
Gb of addressable memory (and starts swopping when it hits this limit). Any
clue what is causing this?
Since the Opteron memory controller is integral to the CPU, is this a
fundamental problem with 244s or could it still be in the BIOS?
Additionally, if I enable ECC in the BIOS I encounter unpredictable
failures. How can this be? I thought Opterons ONLY work with registered ECC
memory. Could BIOS settings be incompattible with the memory controller?
Has anybody with a K8W updated to the 2885101i BIOS beta revision? Does it
do any of the things it purports to fix:
* Add DDR400 display support.
* Add AMD Errata 86 fix
* Open HT frequency options
* Update CPU module to fix the CPU APIC Version error
* Replace IORR with MTRR for AGP Aperture memory
* Update Silicon Image Option ROM to version 5.0.31
(from tyan )
Thanks for your patience!
PS. Thanks also to previous correspondents regarding the ATI driver issue
(it doesnt yet exist for 64bit linux)
Need info in a hurry? Use MSN Search! http://search.msn.co.za/
As far as I know, this is supposed to work with little or no problems for
AMD64bit. (i.e. Suse 9.0 supports the 9600 series)
Currently I have the following system running:
Thunder K8W + 2x 244's + 4Gb of DDR400 + Twin SATA HDDs
Booted of the patch disk and everything is ran smoothly first time...
except the graphics driver which does not give 3D support.
Now before I go and flash the BIOS or start running diagnostics, is there
something I am missing?
Eugene de Villiers
Entertainment venues, star gossip and more - find it with MSN Search!
> This should be fixed as soon as all mirrors pick up the new path...
> We unfortunatly gave it a wrong name :-(
and by now, what should we enter in YOU?
Server Name: ftp.suse.de ?
I managed to install 9.0 with the new boot iso.
However, I can't make YOU get updates as it thinks my system is SuSE
Since there's no update directory of that name, it can't find the
directory.3 and aborts.
How do I fix this?
Just curious what other 64-bit AMD processors get in /proc/cpuinfo (like
Opteron and FX):
mine (plain old Athlon64) generates:
model name : AMD Athlon(tm) 64 Processor 3200+
All inputs appreciated...
On Wed, 28 Jan 2004 01:49:34 +0100
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004(a)gmx.net> wrote:
> The nic timer interrupt programming been fixed since forcedeth 0.22
> although various testers have confirmed that disabling the timer interrupt
> since 0.14 already fixed the storms for them.
Thanks for the correction. I guess we'll still need to wait a bit
for it to settle down, although it seems to look mostly good.
> If you want a SUSE kernel with forcedeth support, try either 2.6.x from
> or download forcedeth.o for k_athlon-2.4.21-166 from
Note the name of the list. A 32bit driver is unlikely to work.
>However, some odd things began to pop up: gftp
>(which I love) crashes. I tried to reinslall from the rpms
>on the CDs of the non-64 bit version of suse 9.0,
>which I also have. (I thought maybe the dvd disc was corrupted.)
>It failed too. xftp crashes. (The text-based ftp however works.)
>Another program I use a lot, kdvi (kde's dvi previewer for latex
>also crashes:-(. I've recently been having problems wth kmail,
>and had to switch over to mozilla. I'm not sure if that's related though.
I've had similar problems, though I do not use these programs -- the only
one I remember offhand was xscreensaver crashing [and taking X with it].
I know SUSE does not recommend this, but I fixed the problem in every case
by downloading the source and recompiling. Also, switching to a 2.6.x kernel
fixed a lot of strange crashes and kernel panics. If you're going to compile
source yourself, you'll need to be aware of the following changes to the
`./configure && make && make install` process:
* run `./configure --prefix=/usr/local --libdir=/usr/local/lib64
* after this, edit ./libtook and add "/lib64 /usr/lib64 /usr/local/lib64"
to sys_lib_search_path_spec and to sys_lib_dlsearch_path_spec
There is probably a way to do that last one automatically, but I've been too
lazy to look for it ;)
Check out the coupons and bargains on MSN Offers!
I've just finished downloading the kernelsources for 193 to find them to be
a package of 2.4.21 and lots of patches, rather than the usual kernel with
Now, I tried using the script suggested by the README.SuSE file...
for p in $(./guards $(./arch-symbols)<series.conf); do
patch -d /usr/src/linux-2.4.21/ -p1 < $p || break;
to apply the patches, but I did notice quite a lot of chunks flying past
that weren't patching properly (by the looks of it).
And on compile, when it gets to the mm section...
In file included from /usr/src/linux-2.4.21/include/linux/highmem.h:6,
/usr/src/linux-2.4.21/include/asm/pgalloc.h: In function `pmd_populate':
/usr/src/linux-2.4.21/include/asm/pgalloc.h:21: warning: suggest parentheses
around + or - inside shift
/usr/src/linux-2.4.21/include/linux/highmem.h:72: warning: suggest
parentheses around + or - inside shift
mmap.c: In function `unmap_fixup':
mmap.c:857: error: `ADDR_LIMIT_3GB' undeclared (first use in this function)
mmap.c:857: error: (Each undeclared identifier is reported only once
mmap.c:857: error: for each function it appears in.)
make: *** [mmap.o] Error 1
make: Leaving directory `/usr/src/linux-2.4.21/mm'
make: *** [first_rule] Error 2
make: Leaving directory `/usr/src/linux-2.4.21/mm'
make: *** [_dir_mm] Error 2
Is it me doing something wrong, or is there a problem with the patches in
I was trying to install SUSE9 for AMD64 on tyan K8W board with SIL-3114
before recent ISO Patch. After unhappy attempt to use RAID1 there came
reproducible terrible sounds from one of two HDDs (like if damaged
HDD-head hits the clipper), then in order to get
somehow into a RAID setup I've disconnected one
HDD and get into RAID setup successfully.
I've deleted RAID1 Set (having only one of two HDDs attached)
and prooved that PC passes RAID report screen OK. Then I've found
that I can't apply easily the same procedure for a second HDD,
RAID Controller hangs badly and after several minutes of
hanging i get into RAID1 setup and can't delete RAID1 Set from
this HDD. Well, there's no bad sounds anymore after deleting
RAID1 set just from first HDDs (BTW, interesting why?).
So, I hope it is a problem of SIL-3114, and not the
problem of HDD.
Here I've found a new RAID BIOS for SIL-3114:
but there is no any instuction on how to write it...
(I don't want to crash BIOS of my motherboard)
any good links?
have anyone tried this BIOS already?
thanks a priori.
BioVisioN AG, Hannover
On Tue, 27 Jan 2004 02:03:00 -0800
"David O'Brien" <obrien(a)FreeBSD.org> wrote:
> On Sat, Jan 24, 2004 at 05:39:34PM +0100, Andi Kleen wrote:
> > Maybe it didn't work reliably. The latest 9.0 update kernel has a
> > Silicon Image driver, please try it.
> What [simple] procedure can one use to install SL 9.0 on a Tyan Thunder
> K8W that has only SATA drives?