> > If your BIOS is doing this (as opposed to
> > you mucking with the settings), I need to get the AMD BIOS
> > developers to talk to your BIOS developers.
> That would be great. Please do that. What's shown above is
> indeed the mtrr settings that come from the bios. I didn't
> change anything. And that's the same on two different PCs
> (both iwth A8V), so it's not that just one PC is broken or
> sth... However, whatever problems I was reporting to ASUS, I
> never got anything helpful back, or a fix in the next release
> etc. They seem to ignore user bug reports, but I guess they
> won't ignore AMD...
What motherboard, BIOS vendor, and BIOS version are you
> > You may want to check if your BIOS has an option for "Discrete" or
> > "continuous" usage of MTRRs. Experiment with both settings - I
> > believe "discrete" should work better in a memory hoisting
> > environmnet.
> Unfortunately not! I read about other mainboards having this
> option in the bios and looked for it carefully, because other
> people reported they could fix the problem with the fglrx
> driver using this setting. Unfortunately, Asus didn't put
> such a setting in their latest release...
They're supposed to have done so, after a huge fuss we had
over these issues last year. After you give me the motherboard
models, BIOS vendor, and BIOS version I can hopefully get
I just upgraded the BIOS of my A8V deluxe to the newest version (1014)
und tried to boot with the Suse 9.3 Live-CD, distributed by the German
If I activate "software memory hole" in the BIOS, I see only 3GB (with
the "free" comand and also inside the BIOS system information) despite
4GB of physical RAM installed.
dmesg says this:
Linux version 126.96.36.199-20a-default (geeko@buildhost) (gcc version 3.3.5
(prerelease) (SUSE Linux)) #1 Wed Mar 23 21:52:37 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable)
BIOS-e820: 00000000bffb0000 - 00000000bffc0000 (ACPI data)
BIOS-e820: 00000000bffc0000 - 00000000bfff0000 (ACPI NVS)
BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved)
BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
Warning only 4GB will be used.
Use a PAE enabled kernel.
3200MB HIGHMEM available.
896MB LOWMEM available.
Just as clarification of terms:
- What is HIGHMEM and LOWMEM and shouldn't they be called the other way
round as the big part is counted from 0x00000000 on?
- Isn't PAE for 32bit OS only (I booted the 64bit version)?
So after all, would a full 64bit installation of 9.3 install a "PAE
enabled kernel", so that I would see all 4GB of installed RAM? Is this a
special choice then or simply the standard kernel?
Thanks in advance for your help!
I am new here;
I have found that if I call an ELF32 Executable program from a php page
loaded by a 64 bit PHP module then I obtain a shared library error,
even if the program does not require the library.
------ cc -o pro -m32 pro.c
then call it from a php page:
$s = "/tmp/pro 2>/tmp/er 1>&2";
echo "$s : ";
echo `cat /tmp/er`;
// just to test that it works...
$s = "ls -al /tmp 2>/tmp/er 1>&2";
echo "$s : ";
echo `cat /tmp/er`;
issuee? Error?Bug? my fault???
Hints? I cannot recompile at 64 all my programs ...
We have 3 computers with Asus A8V motherboard.
1 has no raid and uses the on board Marvell Gigabit ethernet....
NO problems (driver sk98lin loaded)
2 with raid 0 , when Marvell Gigabit ethernet is used (sk98lin driver)
System locks up
3 with raid 1, when Marvell Gigabit ethernet is used (sk98lin driver)
system locks up
So the right drivers are used, but on the systems with raid (VIA VT8237)
the system will hang sooner or later (but within minutes).
| Dr. Wilko Keegstra priv.phone: +31594514153,+31610477915|
| Groningen University email: W.Keegstra(a)rug.nl |
| Dept.of Biophys.Chemistry |
| Nijenborgh 4 phone: +31503634224 |
| 9747 AG GRONINGEN fax : +31503634800 |
| The Netherlands |
Root can run firefox ok but regular users can't. They get the
/opt/MozillaFirefox/lib/firefox-bin: symbol lookup error:
/opt/MozillaFirefox/lib/firefox-bin: undefined symbol: gdk_threads_lock
This occurs on both 1.0.6 and 1.0.7 suse amd64 9.3
Anyone seen this or fixed this before?
I'm have 64-bit (obviously right?) SuSE 9.2 installed on a Compaq Persario
laptop. I am trying to get an external keyboard hooked up to it because I'm
used to using the "natural" style keyboards and while i'm at my desk I'ld
like to type on that. There is no ps/2 port on this laptop just USB, just an
FYI. I can't seem to figure out how to get SuSE to recognize the keyboard,
its not automatically detected at boot and nor can I find anything in Yas or
in a google search to help me figure out how to do this. Anyone know?
Sam Six EDD, Inc.
> I had the CPU frequency scaling working fine on my AMD
> Turion-based laptop running SuSE 9.3 and then suddenly it
> started to freeze every now and again.
> So I tried to reboot and now powersave still does not work.
> These are the starup messages after reboot:
> Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: Found 1
> AMD Athlon 64 / Opteron processors (version 1.00.09e)
> Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 0 : fid 0xa
> (1800 MHz), vid 0x4 (1450 mV)
> Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 1 : fid 0x8
> (1600 MHz), vid 0x6 (1400 mV)
> Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 2 : fid 0x0
> (800 MHz), vid 0x16 (1000 mV)
> Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: failing
> init, change pending bit set
> Sep 24 20:23:07 fullyautomatix [powersave]: WARNING in Function
> getSupportedSleepStates; line 21: Could not open
> /proc/acpi/sleep file to evaluate supported sleeping states
> Any idea what could cause this?
We've started seeing this internally in AMD QA. The bit
that the processor uses to indicate that it is in the
process of changing frequencies (aka the pending change
bit) is not clearing. The powernow-k8 driver cannot
change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best
guess is that the problem is not software related. We've
reported the problem to the AMD hardware debug team and
they're investigating. I'll put out a patch when we have
I've been experiencing an annoyance since I built this box. Every once
in a while, a few times per day, the video goes blank for a couple of
seconds and then comes back as if nothing happened. I'm using the
nvidia-supplied drivers and the digital video output. Any clues?
uname -a : Linux lbox 188.8.131.52-21.7-default #2 Tue Jun 21 14:21:54 PDT
2005 x86_64 x86_64 x86_64 GNU/Linux
27: PCI(AGP) 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.273]
Unique ID: VCu0.Hj+k_rvGEWB
Parent ID: vSkL.CP+qXDDqow8
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "nVidia GeForce FX 5200 (0x0322)"
Vendor: pci 0x10de "nVidia Corporation"
Device: pci 0x0322 "GeForce FX 5200 (0x0322)"
Memory Range: 0xf6000000-0xf6ffffff (rw,non-prefetchable)
Memory Range: 0xe0000000-0xefffffff (rw,prefetchable)
Memory Range: 0xf7800000-0xf781ffff (ro,prefetchable,disabled)
IRQ: 193 (2076818 events)
I/O Ports: 0x3c0-0x3df (rw)
Driver Info #0:
XFree86 v4 Server Module: nv
Driver Info #1:
XFree86 v4 Server Module: nvidia
3D Support: yes
Color Depths: 16
Config Status: cfg=yes, avail=yes, need=yes, active=unknown
Attached to: #11 (PCI bridge)
Primary display adapter: #27