April 2007 - 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] Seeking help about /var
by Sheo Shanker Prasad 26 Apr '07

26 Apr '07

I will greatly help any tutorial about what is in /var set of directories, specifically the /var/tmp/kdecache which has accumulated a lot of files. How can I delete the unnecessary files? Best regards. Sheo (Sheo S. Prasad) Creative Research Enterprises 6354 Camino del Lago Pleasanton, CA 94566, USA Voice Phone: (+1) 925 426-9341 Fax Phone: (+1) 925 426-9417 e-mail: ssp(a)CreativeResearch.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 2

Re: [opensuse-amd64] Printing woes under 10.2
by Constantine 'Gus' Fantanas 24 Apr '07

24 Apr '07

Thank you for your suggestion. I will look into it. When I get the garbled printout --at least in some cases where I retained the initial sheet, I do see %!PS-Adobe-3.0 printed (most probably out of Firefox), so maybe the filter is not prepared for it. I need to investigate what initialization string kghostview outputs. Maybe the filter expects PS- Adobe 3.1. I think trapping the output of kghostview (which works) may solve the mystery. CF David Gluss wrote: > Yes, that's the issue. > > I used to know how the queue worked, but I believe that the filters > would still look for a particular set of characters at the beginning > of the print job to decide what to do. So that if the job begins with > #%PS-Adobe, for example, a postscript filter would be invoked; that > is the string used by e.g. enscript (see /etc/enscript.cfg). Maybe > the filter looks for PS-Adobe-3.0 and Netscape is printing PS-Adobe-3.1 > or some such? > > > David Gluss > 408 866 4125 x307 > -----Original Message----- > From: Constantine 'Gus' Fantanas [mailto:fantanas@innocent.com] > Sent: Saturday, April 21, 2007 11:36 AM > To: David Gluss > Cc: opensuse-amd64(a)opensuse.org > Subject: Re: [opensuse-amd64] Printing woes under 10.2 > > David Gluss wrote: > >> >> Doesn't the Laserjet have a built-in Postscript interpreter? >> >> DG >> >> > --I don't know. If it does have a built-in Postscript interpreter, that > should not mean that foomatic-rip is totally bypassed. Am I correct? > Foomatic-rip should decide to basically do nothing, but foomatic-rip > should still be invoked. Now, if foomatic-rip at work behaves the way > it does at home when I try to print a file from within Firefox or > Acrobat Reader (getting the arguments garbled and passing raw PS > commands to the printer), that would conceal the problem I am having > because the printer at work understands Postscript. So, the SuSE 10.2 > at work may still have the same problem, but I am lucky because the > printer understands Postscript. Interesting theory! In such a case, > analyzing the pertinent configuration files from work would probably not > solve my problem at home. > > CF > >> -----Original Message----- >> From: Constantine 'Gus' Fantanas [mailto:fantanas@innocent.com] >> Sent: Thursday, April 19, 2007 9:21 PM >> To: Klaus Singvogel; opensuse-amd64(a)opensuse.org >> Subject: Re: [opensuse-amd64] Printing woes under 10.2 >> >> Hi, >> >> I have no news because I was tied up with work and have not been able >> to try your suggestions. I am planning to do something about this >> issue over the weekend. I remember facing the same problem when I >> tried to print a PDF file from inside Acrobat Reader; again no problem >> > > >> when the file was opened with and printed from kghostview. >> >> One other thing I would like to mention is that at work I have set up >> a Linux server for a lab. It runs 64-bit OpenSuSE 10.2 on an Intel >> Core 2 Duo. I don't have any problem printing at work. Sure, the >> printer is different (Laserjet at work vs. my 8450 Inkjet at home), >> but my problems at home seem to be related to the arguments passed to >> and/or parsed by the foomatic filter, not with the PPD file. The >> major difference I see between the two machines (aside from the >> processors) is that on my machine at home I started with SuSE 9.1, >> then upgraded to 9.2, 9.3, 10.0, skipped 10.1 and, finally, upgraded >> to 10.2. On the machine at work, I started with OpenSuSE 10.1 and >> then upgraded to 10.2. So,I begin to suspect that something may have >> not been updated right on my machine at home, where I see the problem. >> >> Since I have access to the lab server at work, I will compare the >> configuration files for CUPS and foomatic-rip between the two >> machines, as well as firefox settings. Something has GOT to be >> > different! > >> CF >> ......... >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org >> >> >> >> > > > -- > Running 64-bit Linux on AMD64 > > > > -- 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 1

[opensuse-amd64] Printing woes under 10.2
by Constantine 'Gus' Fantanas 23 Apr '07

23 Apr '07

After upgrading to SuSE 10.2 from 10.0 (both 64 bit), I have not been able to get my printer to print from firefox (32 bit) or thunderbird (64 bit). It was working perfectly under SuSE 10.0. The printer is an HP8450 inkjet, which uses the same drivers as the HP8400 inkjet (strangely enough, linuxprinting.org lists this printer as a laser printer; maybe there is an HP8450 laser, but mine is inkjet). The printer prints the test page from inside YAST perfectly well. And it also prints the test page from inside the CUPS administration tool (http://127.0.0.1:631) without any problem, even the fine radial lines 1 degree apart. It also works fine from inside openoffice. But when I try to print from inside firefox or Thunderbird, it seems it wants to print the Postscript instructions rather than executing them. The printer is connected through ethernet. YAST says that the PPD file is "HP8400 Photosmart Foomatic/hpijs (recommended)", and the connection is direct TCP port printer at socket://192.168.xxx.xxx:9100 (nmap also shows ports 80 and 139 open and I know port 80 is open because I can talk to that printer at that port through the browser). In YAST, I have marked "Share Printer" and "Do Local Filtering." Since the release notes of SuSE 10.2 mention drastic changes in CUPS, I used YAST to erase it and reinstall it. But the result is still the same: it prints Postscript instructions (and I rush to to turn it off to save paper). Since the printer prints fine from inside YAST, CUPS administrator, and OpenOffice, I must be doing something wrong. Any ideas? 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

4 11

[opensuse-amd64] slow floppy after upgrade to opensuse 10.2
by Joe Georger 19 Apr '07

19 Apr '07

Hey all, I upgraded from Suse 9.3 to openSuse 10.2 (both x86_64) on my dual Opteron box and now the floppy drive is writing at about 1k/sec. It is mounted in the /etc/fstab with /dev/fd0 /media/floppy auto noauto,user,sync 0 0 Any ideas or help? Thanks, Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

4 6

[opensuse-amd64] Debugging 32bit programs on 64bit systems
by Stephen Williams 19 Apr '07

19 Apr '07

I have a dual opteron system running suse 10.1, and I'm trying to debug a program compiled with gcc -m32. Unfortunately, gdb cannot find any symbols and I can't even get a useable stact trace out of it. Is there a gdb32 or some trick with gdb so that I can do the debugging I need to do? Thanks, -------------------------------------- Protect yourself from spam, use http://sneakemail.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] 4GB memory problem with OpenSuSe 10.2
by Peter Trifonov 11 Apr '07

11 Apr '07

Hello, I have got a PC based on GIGABYTE GA-965P-S3 motherboard (Intel P965 chipset, Core 2 Duo CPU) with 4GB memory. There are two problems with it: 1. OpenSuSe 10.2 x86-64 hangs during boot process with message "agpgart: detected an Intel 965G chipset". I managed to work around this problem by specifying mem=4096M boot option. 2. After the system has started, it reports that there is just 3.43Gb memory available. I was not able to find any options in BIOS related to memory hole remapping. Anyway, Windows XP x64 sees 4094 Megabytes. Is there any way to allow Linux to see all 4Gb of memory? With best regards, P. Trifonov --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

4 9

[opensuse-amd64] conflicting types for ‘__s64’
by Frank Steiner 11 Apr '07

11 Apr '07

Hi, I'm trying to recompile the util-linux.src.rpm from SLES 10 (or SuSE 10.1), currently 2.12r-35.6, but I end up with In file included from /usr/include/asm/types.h:4, from /usr/include/asm-x86_64/byteorder.h:4, from /usr/include/asm/byteorder.h:4, from /usr/include/linux/cdrom.h:14, from mount_guess_fstype.c:51: /usr/include/asm-x86_64/types.h:22: error: conflicting types for ‘__s64’ /usr/include/blkid/blkid_types.h:18: error: previous declaration of ‘__s64’ was here /usr/include/asm-x86_64/types.h:23: error: conflicting types for ‘__u64’ /usr/include/blkid/blkid_types.h:19: error: previous declaration of ‘__u64’ was here make[1]: *** [mount_guess_fstype.o] Error 1 Looks like blkid_types.h is not chosing the "long long" type that asm-x86_64/types.h defines, but I'm not familiar enough with C to understand why. Can someone give me a hint? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 2