> > 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
using?
> > 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
this resolved.
-Mark Langsdorf
AMD, Inc.
Hi,
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
magazine c't.
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 2.6.11.4-20a-default (geeko@buildhost) (gcc version 3.3.5
20050117
(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!
Ciao
Siegbert
Hi all,
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.
practical example:
compile this
====== pro.c
#include <stdio.h>
main()
{
printf("Hello world\n");
}
------ cc -o pro -m32 pro.c
then call it from a php page:
========= r.phtml
<?php
$s = "/tmp/pro 2>/tmp/er 1>&2";
echo "$s : ";
$rrr=exec($s);
echo `cat /tmp/er`;
echo "<hr>";
// just to test that it works...
$s = "ls -al /tmp 2>/tmp/er 1>&2";
echo "$s : ";
$rrr=exec($s);
echo `cat /tmp/er`;
?>
---- http://localhost/r,phtml
issuee? Error?Bug? my fault???
Hints? I cannot recompile at 64 all my programs ...
Thanks,
regards,
Ric
Greetings
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?
TIA&Cheers
uname -a : Linux lbox 2.6.11.4-21.7-default #2 Tue Jun 21 14:21:54 PDT
2005 x86_64 x86_64 x86_64 GNU/Linux
hwinfo --gfxcard:
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)"
Revision: 0xa1
Driver: "nvidia"
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
Extensions:
Options:
Config Status: cfg=yes, avail=yes, need=yes, active=unknown
Attached to: #11 (PCI bridge)
Primary display adapter: #27
Hello,
I am trying to install SUSE 9.3 on Asus SK8N motherboard running
Opteron. I use the built-in Promise SATA controller with two disks in
IDE mode.
I was able to perfectly run SuSE 9.1 on this system for a long, long
time. Now, with SuSE 9.3 I am not even able to get through the
installation. It seems that the disk access causes the installation to
hang sooner or later. When files are being copied the installation just
freezes.
It seems that this problem is not specific to SUSE. Any other distro
with 2.6 kernel that I tried freezes in the same way as SUSE.
Does anyone have a success story installing SUSE 9.3 on a similar setup?
And also, is there some way that I can save kernel messages during
installation?
Thanks,
Marcin Zalewski
Hello everyone:
Just to bring you up to speed, I'm running SuSE 9.3
professional in 64-bit mode on an AMD 64 laptop. Recently I was
experiencing problems with YaST (Yet another System Tool) as I couldn't
install additional software packages. YaST couldn't 'see' the DVD and
would report:
ERROR (InstSrc: E_no_instsrc_on_media)
[ /media.1/media ]
This file ( /media.1/media ) contains text identifying the
make and model of the software (SuSE 9.3, DVD 1). Somehow this file was
corrupted on the laptop and this was preventing YaST from 'seeing' the
DVD. However, after a clean install, everything worked. So, I assumed
that the problem was with the YaST update packages and, on the next
update, I avoided all of the YaST patches only to have the problem
re-surface on the next reboot.
After reading my posts, another user suggested I attempt
another upgrade but not to upgrade the Linux kernel. This seems to have
solved the problem. I did a fresh install - everything worked. I even
used YaST's 'Check Media' program on the DVD - it got a clean bill of
health. I then did an upgrade but I DID NOT upgrade the LINUX KERNEL.
Well, after the upgrade and a re-boot - everything is working
correctly. And YaST's Media Check gave the DVD another clean bill of
health.
So, there must be some sort of incompatibility problem
between my machine and the kernel upgrade. Hope this helps. In
closing, I would like to thank all of you who helped to solve this
problem. It was a dilly.
Cheers,
Mike
I have an Acer 5002 WLMI laptop, and I am trying to get the wireless
working.
I have already installed ndis
ndiswrapper-1.1-4
km_ndiswrapper-1.1-4
I am not too sure what I should do next.
lspvi -v shows this about my card.
0000:00:0b.0 Network controller: Broadcom Corporation: Unknown device 4318
(rev 02)
Subsystem: AMBIT Microsystem Corp.: Unknown device 0312
Flags: fast devsel, IRQ 4
Memory at e2000000 (32-bit, non-prefetchable) [size=8K]
can someone please help?
TIA
Laurent GUERBY wrote:
> On Fri, 2005-08-19 at 20:47 -0700, Pierre Patino wrote:
>
>>I ran the test as you suggested. The result is the same -- 1.8GHz. Where
>>did the 200MHz go? According to the BIOS settings, the powersaving
>>feature is disabled.
>
>
> Try something that really sucks cpu :)
>
> $ cat /proc/cpuinfo | grep MHz
> $ md5sum /dev/zero &
> $ sleep 1
> $ cat /proc/cpuinfo | grep MHz
> $ kill %1 # or whatever
>
> On my Athlon 64 3000+ cpuinfo goes from 1 GHz to 2 GHz.
>
> Does your BIOS report at boot the right Opteron model?
>
> The only problem with frequency I have with SuSE 9.3 is
> that when I suspend to disk my laptop, after I resume
> frequency is stuck at the lowest possible frequency
> and I cannot seem to change it until I reboot,
> but this is a Centrino 1.7 GHz so not amd64 :).
>
> Laurent
>
>
OK, new BIOS for TYAN K8E. AMD Athlon 64 3000+ Socket 939 is rated for 1.8MHz. This checks out.
Previous BIOS reported 1.0GHz. This puzzle has been "solved".
On ASUS K8VSE-Deluxe, the AMD Athlon 64 3000+ Socket 754 is rated at 2.0GHz. This also checks out.
Note to self: RTFM!
-----Original Message-----
From: Ryan Biltz [mailto:rbiltz@ncmir.ucsd.edu]
Sent: Monday, August 29, 2005 7:07 PM
To: suse-amd64(a)suse.com
Subject: [suse-amd64] only root can access NTFS removable media??
Hello All,
I was happy to see that NTFS is supported out of the box with SuSE 9.3.
However it seems only root is able to access the file system. I plugged
in an external USB HD (NTFS) of mine while logged in as a normal user.
The removable media icon showed up on the file browser but when i click
to open and explore within it gave me an access denied error. When I
log in as root I am able to browse and access the files. Also I am
unable to modify any of the files or write new ones. Acts like a CD. I
know there is no Write support for NTFS yet but I was hoping to at least
have the ability to read my files as a normal user and not have to be
root to access them. Is there a way to do this? Thanks for any Info.
-ryan
Ryan,
You should only mount NTFS read-only for now. Go here to learn more:
http://linux-ntfs.sourceforge.net/info/ntfs.html
Towards the bottom of the FAQ are links to projects that are attempting
NTFS read/write, but this is dangerous for the filesystem (work in
progress), use at own risk. A better recommendation, format the
external drive as FAT32 instead if you don't need NTFS for anything
since Windows and Linux can both read/write FAT32.
As for mounting the NTFS for normal users:
http://linux-ntfs.sourceforge.net/info/ntfs.html#4.10
You'll need to make some changes to the partition name that they use
since you're mounting it as usb and not hda1 per their examples. Here
is what is in my /etc/fstab for my ntfs partition:
/dev/hda1 /windows ntfs ro,umask=0222,noauto,user,exec 0
0
John
Hello All,
I was happy to see that NTFS is supported out of the box with SuSE 9.3.
However it seems only root is able to access the file system. I plugged
in an external USB HD (NTFS) of mine while logged in as a normal user.
The removable media icon showed up on the file browser but when i click
to open and explore within it gave me an access denied error. When I
log in as root I am able to browse and access the files. Also I am
unable to modify any of the files or write new ones. Acts like a CD. I
know there is no Write support for NTFS yet but I was hoping to at least
have the ability to read my files as a normal user and not have to be
root to access them. Is there a way to do this? Thanks for any Info.
-ryan