I tried to install my vmware 4 on my suse 9.0/amd64 system. After installing I fail to configure vmware.
The error message is:
"The kernel defined by this directory of header files does not have the same
address space size as your running kernel."
The output is like this:
sepia:~ # vmware-config.pl
Making sure VMware Workstation's services are stopped.
Stopping VMware services:
Virtual machine monitor done
Trying to find a suitable vmmon module for your running kernel.
None of VMware Workstation's pre-built vmmon modules is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
The kernel defined by this directory of header files does not have the same
address space size as your running kernel.
What is the location of the directory of C header files that match your running
Any experience, any suggestions ?
thanks a lot.....
Yesterday I successfully installed SuSE 9.0 on my Athlon64 system (Shuttle
AN50R). Today I wanted to install and run the Borland Kylix 3 RAD IDE. The
install process went fine, however when running the Delphi IDE / the Delphi
command line compiler I always get following errors in my messages log:
Jan 9 18:53:18 linux kernel: delphi general protection rip:5699028a
Jan 9 18:42:52 linux kernel: dcc: segfault at 0000000000000000 rip
0000000000000000 rsp 0000000000000000 error 14
As I know that this software runs fine on SuSE 9.0 non AMD64 (even when using
the 2.6.x kernel) I can not quite understand why it fails on the AMD64
version when other 32bit programs are running fine..
JFYI: Till now it seems that even programs produced by Kylix will fail to run
on SuSE 9.0 AMD64.
Any ideas how to solve this issue?
> and by now, what should we enter in YOU?
> in particular:
> Server Name: ftp.suse.de ?
> Directory: ???
> Authentication: ??
never mind :)
Server Name: ftp.suse.com
I'm glad to announce that we have made a bootable CD with a new kernel
that supports various SATA drivers. This should help everybody with
an AMD64 system with SATA harddisks to install the 9.0/AMD64 DVD on
such a system.
We have done some tests on those systems that we have access and are
finally happy with the results since all these systems are
The kernel contains some extra patches which were not in the
I'll make also an optional kernel update via YOU available the next
days for those that are interested in just the kernel.
Download from a mirror of ftp.suse.com. The ISO is
The kernel RPMs are in a subdirectory on the server if you're just
interested in those.
If you encounter problems, please discuss it on this mailing list.
P.S. Here're the release notes:
This PatchCD contains the current 2.4.21 kernel with all security
updates and especially updates to support SATA controllers. If you
like to install on a new system with SATA harddisks, burn the ISO
image on a CD and boot from it. The CD will ask for the 9.0/AMD64 DVD
and continue with the installation with an updated kernel.
For existing systems which do not require SATA use should use YOU to
get the latest kernel instead if you require these bug fixes and
The kernel update contains:
- support for VIA SATA controller
- support for Promise SATA controllers 2037x, 20319, 20621
- support for Silicon Image (SIL) SATA controllers 3112 and 3114
- better support for Tyan S2885 AGP
- the 32-bit Borland Kylix IDE and programs should work now
Note that we do not have access to all those systems and do not
guarantee that it works. Those that we have, have been tested briefly
Just a note about SATA disks: The 2.4 kernel names disks as /dev/hdx,
the 2.6 kernel might name them /dev/sdx, so in case you update your
system, be careful.
Please report any problems to the mailing list suse-amd64(a)suse.com.
Have a lot of fun!
The SUSE Linux AMD64 team
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
I am a engineer/programmer (fortran,C++) with some experience in system
admin, but not nearly to the level of the people on this list. I'm
looking into buying a new computer system and would like the opinion of
someone on this list how difficult they think it would be to set up with
Suse. I've used numerous versions of Mandrake before and am now
looking to try something better. I've never compiled a kernel or added a
patch before, but would not be afraid to try it. Mostly, I'm worried
about 3D accelerated video card support for some of the graphics intense
applications I run.
OK, here's the computer (from www.hypersonic-pc.com). It's an AMD64
laptop system for about $3100.
1 Type II PCMCIA PC Card Slot
4 USB 2.0 ports, 1 Mini IEEE 1394 Firewire port, and 1 Parallel port
Built-in 3-in-1 Media Card Reader for SD/SM/MMC
HyperSense™ Advanced Remote Diagnostics
Aviator AX6 in Metallic Silver with Graphite Accents
3400+ AMD Athlon™ 64 DTR Processor w/ PowerNow!™ Tech. (800MHz FSB)
VIA K8T800 + VT8235 Chipset Mobile Motherboard for AX6
512MB PC3200 DDR400 RAM SODIMM
512MB PC3200 DDR400 RAM SODIMM
ATI Radeon Mobility 9600 Pro 64MB (w/ TV Out)
Guaranteed No Dead Pixels
60GB 7200rpm Ultra ATA Hard Disk Drive w/ 8MB Cache
8X DVD / 24X-10X-24 CD-R/W Combo Drive w/ Recording Software
15.1" SXGA+ High Contrast Active Matrix LCD Display (1400x1050)
Built-in Sound Blaster Compatible Audio (AX6)
Integrated 10/100 Fast Ethernet Controller
Internal 802.11a+b+g Triband Wireless Mini PCI Network Adapter
Integrated V.92 56K Fax/Data Modem
MS Windows XP Professional SP1 CD & Manual Pre-Installed & Configured
Targus USB Mobile Port Replicator with Ethernet
1Year 24/7 Toll-Free Tech Support Platinum Service & Lifetime Support
Any insights you have would be appreciated. Thanks again.
Ryan P. Starkey, Ph.D.
Faculty Research Scientist
Reusable Launch Vehicle Institute
Department of Aerospace Engineering
University of Maryland, College Park
College Park, MD, 20742-3015
phone: (301) 405-7248
fax: (301) 314-9001
pc: Suse9, 2.4.21-178-smp, on Tyan Thunder K8S
I have just noticed in /var/log/messages that I have, at boot, a bunch of:
mtrr: type mismatch for fd000000,400000 old: uncachable new: write-combining
mtrr: size and base must be multiples of 4 kiB
mtrr: size: 0x800 base: 0xfd000000
Should I worry about?
I use the machine just a number crunching with apparently no problem
CNR-IMM, Sez. Bologna
Via P.Gobetti 101
I-40129 Bologna, Italy
Tel:(+39)-051-639 9179 Fax:(+39)-051-639 9216
> On 32bit it will likely work (but no guarantees, check with ATI)
even for 32bit version Ryan could obtain the whole range of
admin's experience trying to install 3D acceleration
for ATI RADEON 9600 PRO ...
Details on installation http://www.gmpf.de/
For me it was really unpleasant :(
>Do a head -30 /var/log/boot.msg
dm(229) head -30 /var/log/boot.msg
Loaded 14927 symbols from /boot/System.map-2.4.21-193-smp.
Symbols match kernel version 2.4.21.
Loaded 117 symbols from 5 modules.
klogd 1.4.1, log source = ksyslog started.
<4>Bootdata ok (command line is root=/dev/sda2 vga=0x31a desktop
<4>Linux version 2.4.21-193-smp (root(a)x86_64.suse.de) (gcc version 3.3.1
(SuSE Linux)) #1 SMP Wed Jan 21 18:41:44 UTC 2004
<6>BIOS-provided physical RAM map:
<4> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
<4> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
<4> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
<4> BIOS-e820: 0000000000100000 - 000000009fff0000 (usable)
<4> BIOS-e820: 000000009fff0000 - 000000009ffff000 (ACPI data)
<4> BIOS-e820: 000000009ffff000 - 00000000a0000000 (ACPI NVS)
<4> BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
<4>kernel direct mapping tables upto 10100000000 @ 8000-d000
<6>Scanning NUMA topology in Northbridge 24
<3>Node 0 using interleaving mode 1/0
<6>No NUMA configuration found
<6>Faking a node at 0000000000000000-000000009fff0000
<4>Bootmem setup node 0 0000000000000000-000000009fff0000
<7>ACPI: have wakeup address 0x10000002000
<4>Scan SMP from 0000010000000000 for 1024 bytes.
<4>Scan SMP from 000001000009fc00 for 1024 bytes.
<4>Scan SMP from 00000100000f0000 for 65536 bytes.
<6>found SMP MP-table at 00000000000ff780
<4>hm, page 000ff000 reserved twice.
<4>hm, page 00100000 reserved twice.
<4>hm, page 000f9000 reserved twice.
Hmm, very strange, no sizes reported.
Why is it using SMP and not NUMA for memory sharing? Is there a NUMA version
of the 193 kernel I could use?
Entertainment venues, star gossip and more - find it with MSN Search!
another datapoint - see below
> On Thu, 29 Jan 2004 16:19:57 +0000
> "Eugene de Villiers" <edevilliers(a)hotmail.com> wrote:
> [cc'ing back to suse-amd. Please keep discussions there]
> > >Do a head -30 /var/log/boot.msg
> > >
> > dm(229) head -30 /var/log/boot.msg
> > Inspecting /boot/System.map-2.4.21-193-smp
> > Loaded 14927 symbols from /boot/System.map-2.4.21-193-smp.
> > Symbols match kernel version 2.4.21.
> > Loaded 117 symbols from 5 modules.
> > klogd 1.4.1, log source = ksyslog started.
> > ok
> > <4>Bootdata ok (command line is root=/dev/sda2 vga=0x31a desktop
> > splash=silent)
> > <4>Linux version 2.4.21-193-smp (root(a)x86_64.suse.de) (gcc
> version 3.3.1
> > (SuSE Linux)) #1 SMP Wed Jan 21 18:41:44 UTC 2004
> > <6>BIOS-provided physical RAM map:
> > <4> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> > <4> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> > <4> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> > <4> BIOS-e820: 0000000000100000 - 000000009fff0000 (usable)
> > <4> BIOS-e820: 000000009fff0000 - 000000009ffff000 (ACPI data)
> > <4> BIOS-e820: 000000009ffff000 - 00000000a0000000 (ACPI NVS)
> > <4> BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
> > <4>kernel direct mapping tables upto 10100000000 @ 8000-d000
> > <6>Scanning NUMA topology in Northbridge 24
> > <3>Node 0 using interleaving mode 1/0
> > <6>No NUMA configuration found
> > <6>Faking a node at 0000000000000000-000000009fff0000
I have seen the above 2 lines where for some reason the BIOS could use a DIMM (in my case I reckon it is a faulty DIMM slot). If that CPU has no usuable DIMMs I get the above message.
In my case I solved it by moving the 2 DIMMs up from slots 0/1 to slots 2/3 on that CPU.
> > <4>Bootmem setup node 0 0000000000000000-000000009fff0000
> > <7>ACPI: have wakeup address 0x10000002000
> > <4>Scan SMP from 0000010000000000 for 1024 bytes.
> > <4>Scan SMP from 000001000009fc00 for 1024 bytes.
> > <4>Scan SMP from 00000100000f0000 for 65536 bytes.
> > <6>found SMP MP-table at 00000000000ff780
> > <4>hm, page 000ff000 reserved twice.
> > <4>hm, page 00100000 reserved twice.
> > <4>hm, page 000f9000 reserved twice.
> > Hmm, very strange, no sizes reported.
> > Why is it using SMP and not NUMA for memory sharing? Is
> there a NUMA version
> > of the 193 kernel I could use?
> The kernel is NUMA. It cannot access the northbridge of the
> second CPU,
> so NUMA support is turned off. That's some hardware problem
> at your side,
> maybe the second CPU or the motherboard are broken or not
> correctly plugged in.
> Check the List-Unsubscribe header to unsubscribe
> For additional commands, email: suse-amd64-help(a)suse.com
I am running an S2885 board with 8 GB of memory, and the system sees the whole lot, and I am able to load a 7.9 GB volume into a visualization app with no problems. I have a BIOS version 101k, loaded the update 193 kernel today, along with the 5332 AMD64 driver from Nvidia, and haven't seen any problems yet.
This combination seems to have fixed a whole raft of problems that I was seeing. Before the mtrr patch (which looks like it is included in the 193 update source code), I would start swapping as soon as the buffer cache filled up, instead of reclaiming space from buffer cache. It also cleared up problems with memory mapping that was causing the nvidia driver to hang on a system with large memory. In addition, I no longer see any mention of APIC version errors in boot.log.
I have enabled ECC, and haven't seen any stability issues yet, but I am only using PC2700 memory. One of our system builders told me that they have seen a lot of problems with 400 MHz memory, even on what is supposedly certified to work. Something to do with the signal, and the length of the connections to the DIMM slots being on the ragged edge of what is possible (I am not an EE, so don't have a clue if this is valid or not )
Advanced Systems Group
Visualization Systems Support
10300 Town Park Dr.
Houston, Texas 77072
-----"Eugene de Villiers" <edevilliers(a)hotmail.com> wrote: -----
From: "Eugene de Villiers" <edevilliers(a)hotmail.com>
Date: 01/28/2004 05:59PM
Subject: [suse-amd64] missing memory
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/
Check the List-Unsubscribe header to unsubscribe
For additional commands, email: suse-amd64-help(a)suse.com