November 2006 - openSUSE AMD64 - openSUSE Mailing Lists

IOMMU...PCI memory hole...MTRR...I give up.
by David W. Hankins 26 May '07

26 May '07

I have an MSI K8D-Master-F motherboard with two Opteron 244's. It recently got retasked as a desktop machine due to another system's failure...I thought the little ATI Rage built into the motherboard would make more than a sufficient 2d desktop type framebuffer, and as far as other stuff inside this box... this should be a pretty kick ass, high performance workstation. But I can literally watch the screen redraw if I switch virtual desktops. Painfully slow. Thinking this was just some crippled built-in video bug, I threw in an old nVidia card we had lying around in one of the regular PCI slots. Slightly slower, if you can believe it. I think this: mtrr: type mismatch for e5000000,1000000 old: uncachable new: write-combining And of course this: $ cat /proc/mtrr reg00: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1 reg01: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1 Has something to do with it (and may also explain why I'm getting less than stellar performance out of other PCI devices, such as the RAID array that has a 128MB memory region the driver directly reads and writes on). The above is with the nVidia PCI card inserted, the built-in ATI card would also emit a similar mtrr rejection message, just the address is different, and the system would only list 512MB uncachable without the nVidia. Also notice that there's 4GB installed in this machine, in 2 2GB DIMMs installed in one bank together. And yet the BIOS map: BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable) BIOS-e820: 00000000bfff0000 - 00000000bffff000 (ACPI data) BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS) BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved) Lists nothing beyond the 4GB mark where that memory might reasonably have been moved to. Assuming this is just a neglectful BIOS, I tried setting 'mem=4G' and 'memmap=1G@4G' kernel options, to define the 1GB 'hole' I presume is being placed here, and which got me this added line to dmesg: user: 0000000100000000 - 0000000140000000 (usable) But still only 3GB available. To add even more insult to rising injury, I noticed while looking through dmesg that the IOMMU is being disabled. It appears the value being advertised by the CPU's: CPU 0: aperture @ 1b80000000 size 128 MB Is being rejected because it lies (WELL) above the 4GB mark. I've been going through archives and I'm not finding anything that looks like actionable advice. The latest BIOS MSI's webpage lists for this motherboard is 1.1: already installed. It has no option for 'pci hole: software'. The only options I'm finding are memory bank interleaving (which I tried disabling), and 'Disabled/Best-Fit/Absolute' settings for the IOMMU, as well as its aperture size (128M, which I might increase if it would be used rather than ignored...). One post in the archive that matched on motherboard make and model looks confused to me, because he refers to his BIOS as AWARD 2.0, but the only BIOS MSI puts out for this board is AMI (versioned 1.1). In summary what I'd like to know is: 1) Where is the 'go fast' button? re: pci video that's slower than even isa video should be (and presumably similar performance problems on other PCI devices). 2) How do I get the last 25% of my memory back? 3) How do I get the system to put the IOMMU somewhere in the range it stole under 4G (so Linux can use it)? Can Linux move this on its own accord? Thanks in advance for any and all help. -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins

5 13

[opensuse-amd64] Trouble with Kernel of the Day
by Constantine 'Gus' Fantanas 28 Nov '06

28 Nov '06

I am running 64-bit SuSE 10 on a Presario R3240 laptop (AMD64-based). I installed the rpm for the the latest _x64 kernel of the day (KOD), 2.6.18.2, dated Nov. 25. (The rpm saved me some manual labor from redirecting the link to '/usr/src/linux'.) During boot, the system crashes. Here is part of the messages I am getting, ending with the crash: . . . fsck succeeded. Mounting root device read-write. Mounting root /dev/hda6. kjournald starting. Commit interval 5 seconds. EXT3 FS on hda6, internal journal. EXT3-fs: mounted filesystem with ordered data mode. /bin/run-init: opening console: No such file or directory Kernel panic - not syncing: Attempted to kill init! And then the system just hangs. Here is the part of the /boot/grub/menu.lst which is pertinent to this: title Linux-2.6.18.2-20061125183539-preemptible root (hd0,5) kernel /boot/vmlinuz-2.6.18.2-20061125183539-preemptible root=/dev/hda6 vga= 0x317 selinux=0 resume=/dev/hda7 splash=silent showopts idebus=66 initrd /boot/initrd-2.6.18.2-20061125183539-preemptible This section of /boot/grub/menu.lst was created using 'INSTALL_PATH=/boot make install', which is SuSE's well-thought shortcut to the drudgery of copying system map files manually. I enabled full preemption. I had no problems with full preemption with 2.6.16. Could anybody shed some light on what I may be doing wrong? TIA for your time. -- Running 64-bit Linux on AMD64 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 2

[opensuse-amd64] OpenSuSE and MS-Novell deal.
by Jose Luis Ricardo Chavez 19 Nov '06

19 Nov '06

Many of us have surely heard about it and its possible harmful consequences to OSS, so, many people is already migrating from SuSE Linux to different distros like Ubuntu. In my case, I have been using OpenSuSE recently, I like this distribution very much and find it difficult to migrate but have to do so if necessary. The question is, to what extent do Novell have control on the OpenSuSE distribution? Is it also covered by the MS-Novell deal? Thanks for your answers. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

11 15

This list will be migrated to opensuse-amd64@opensuse.org
by Henne Vogelsang 11 Nov '06

11 Nov '06

Hi, as announced a while ago on the big lists [1] we will move this list to the new mailinglist server. We have also decided to rename it while moving it. All this will happen this friday (2006.11.10). I cant say exactly at which time but i will send a short heads-up mail right before we are doing it. This means a few things for you. 1. This list, suse-amd64(a)suse.com, will be renamed to opensuse-amd64(a)opensuse.org This means that mails to you will come from the new address and for posting you also have to send mail to opensuse-amd64(a)opensuse.org. The old list adress will still work but is depreceated. I will turn it off in the future (with notice). 2. Your subscription will get transfered to the new listserver. No action on your part is required to continue reciving mails from this list. 3. Because of the renaming the mailinglist headers will change. If you filter for headers in your mail setup please adopt your setup accordingly. New headers will look like this: Delivered-To: opensuse-amd64(a)lists4.opensuse.org Mailing-List: contact opensuse-amd64+help(a)opensuse.org; run by mlmmj X-Mailinglist: opensuse-amd64 List-Post: <mailto:opensuse-amd64@opensuse.org> List-Help: <mailto:opensuse-amd64+help@opensuse.org> List-Subscribe: <mailto:opensuse-amd64+subscribe@opensuse.org> List-Unsubscribe: <mailto:opensuse-amd64+unsubscribe@opensuse.org> List-Owner: <mailto:opensuse-amd64+owner@opensuse.org> 4. Mails will originate from the new server. If you accepts listmails only from the listserver adopt your setup accordingly. The mails will originate from DNS: lists4.suse.de IP: 195.135.221.135 5. The webarchive of this list is then located at http://lists.opensuse.org/opensuse-amd64/ 6. We are using a new mailinglist manager on the new server. This means some aspects of using the list changed. Some features are dropped and some new features are added. For a complete list check out this post: http://lists.opensuse.org/opensuse-announce/2006-08/msg00005.html 7. If you have any problems at all with the new setup please dont hesitate to contact me! Henne [1] http://lists.suse.com/archive/suse-linux-e/2006-Nov/1464.html http://lists.suse.com/archive/suse-linux/2006-Nov/0440.html -- ml-admin

3 2

[opensuse-amd64] unsubscribe
by Daniel H. Latshaw 10 Nov '06

10 Nov '06

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] Re: [owner] Heads up! Migration around 12:30 GMT
by Henne Vogelsang 10 Nov '06

10 Nov '06

Hi, > by 12:35 everything should be migrated. It is now. If you encounter any problem let me know! Henne -- Henne Vogelsang, Core Services "Rules change. The Game remains the same." - Omar (The Wire) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

32bit version of rrdtool
by Ciro Iriarte 04 Nov '06

04 Nov '06

Anybody tried to install the rrdtool package from the 32bit distro?, any version?, i need to update rrd files with x86_64 and x586 distro at the same time, anybody know if it will work? (there's no rrdtool-32bit package), i'm currently using sles9, but i think this list is the most apropiate. Thanks in advanced. Ciro

1 0

Major chornic compile problem
by Dan Sawyer 02 Nov '06

02 Nov '06

Hey all - Has anyone run into a major compile stumbling block because of a poorly-compiled libx11.a? Even when building programs with then --enable-static flag in suse 10.1 64bit I get this error on almost everything. I've searched for weeks, but haven't been able to find a fix anywhere online, and I'm very reluctant to attempt to hand-complie Xorg. Here's the error: ve/usr/lib64/gcc/x86_64-suse-linux/4.1.0/../../../../x86_64-suse-linux/bin/ld : /usr/lib64/libX11.a(ChProp.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib64/libX11.a: could not read symbols: Bad value collect2: ld returned 1 exit status --- ANY help at all would be much appreciated. Thanks! -Dan Sawyer ArtisticWhispers Productions

7 9