[opensuse-amd64] SuSe 10.0/64 4Gb memory problem
Hello, Installed 4GB of physical memory, however only 3GB appear; # cat /proc/meminfo MemTotal: 3342628 kB I'm running the 64 bit kernel (Suse 10.0); 2.6.13-15-smp #1 SMP Tue Sep 13 14:56:15 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux ...with two CPU's; # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 37 model name : AMD Opteron(tm) Processor 246 stepping : 1 cpu MHz : 2009.270 <snip> processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 37 model name : AMD Opteron(tm) Processor 246 stepping : 1 cpu MHz : 2009.270 cache size : 1024 KB <snip> Any ideas on how to remedy this? Many thanks, ~James --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
James D. Parra wrote:
Hello,
Installed 4GB of physical memory, however only 3GB appear;
# cat /proc/meminfo MemTotal: 3342628 kB It sounds like you need to go into the BIOS and ask for "Memwhole remapping" and set it to "Software". This happens because PCI takes the address space from 3-4GB (staying under the 32bit boundary) and maps over where memory may be so we want the BIOS to map that memory elsewhere.
-Joachim --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
"Joachim Deguara" <joachim.deguara@amd.com> wrote:
James D. Parra wrote:
Hello,
Installed 4GB of physical memory, however only 3GB appear;
# cat /proc/meminfo MemTotal: 3342628 kB
It sounds like you need to go into the BIOS and ask for "Memwhole remapping" and set it to "Software". This happens because PCI takes the address space from 3-4GB (staying under the 32bit boundary) and maps over where memory may be so we want the BIOS to map that memory elsewhere.
(disclaimer: I work for AMD in the CPU architecture team) Remapping in the BIOS is possible with all current AMD parts: -- First off, some BIOSes have bugs, so test it out before just using it! -- If this is a pre-rev-E part (C0 or CG), then you can perform "Software" remapping, but it slows down memory access a bit on Opteron systems. -- If this is a Rev E or later part, then you can perform "Hardware" remapping as well, which has no performance cost. I'd recommend using the "Hardware" method if you have a Rev E or later Opteron part. -- Erich Stefan Boleyn <erich@uruk.org> http://www.uruk.org/ "Reality is truly stranger than fiction; Probably why fiction is so popular" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
* Erich Boleyn <erich@uruk.org> [03-19-07 14:04]:
"Joachim Deguara" <joachim.deguara@amd.com> wrote:
James D. Parra wrote:
Installed 4GB of physical memory, however only 3GB appear;
# cat /proc/meminfo MemTotal: 3342628 kB
It sounds like you need to go into the BIOS and ask for "Memwhole remapping" and set it to "Software". This happens because PCI takes the address space from 3-4GB (staying under the 32bit boundary) and maps over where memory may be so we want the BIOS to map that memory elsewhere.
(disclaimer: I work for AMD in the CPU architecture team)
Remapping in the BIOS is possible with all current AMD parts: -- First off, some BIOSes have bugs, so test it out before just using it!
-- If this is a pre-rev-E part (C0 or CG), then you can perform "Software" remapping, but it slows down memory access a bit on Opteron systems.
-- If this is a Rev E or later part, then you can perform "Hardware" remapping as well, which has no performance cost.
I'd recommend using the "Hardware" method if you have a Rev E or later Opteron part.
And what to do for non-Opteron? I have AMD Athlon X86_64 4200+ K8 Tridon nForce 4 SLi GA-K8N Ultra-SLi w/4 GB and show 3350428 kB note: I see no provision for remapping memory in the BIOS. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
And what to do for non-Opteron?
The same ("all current AMD parts")
I have AMD Athlon X86_64 4200+ K8 Tridon nForce 4 SLi GA-K8N Ultra-SLi w/4 GB and show 3350428 kB
note: I see no provision for remapping memory in the BIOS.
Then you're out of luck unless you can get a BIOS update that fixes this. However cheap motherboards tend to not care much about the lots-of-memory case unfortunately and they might have saved some dollars by not testing this (that is why it sometimes doesn't work) or not support it at all. -Andi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
* Andi Kleen <ak@suse.de> [03-19-07 20:19]:
Then you're out of luck unless you can get a BIOS update that fixes this. However cheap motherboards tend to not care much about the lots-of-memory case unfortunately and they might have saved some dollars by not testing this (that is why it sometimes doesn't work) or not support it at all.
The Gigabyte mb was not cheeapp. ps: I read the list, please do not cc me. I have no use for more than one copy of the post. Should it become necessary to have one, I'm sure that I can accomplish that on my own. Thanks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
I don't feel like rebooting my machine to check but IIRC Tyan boards have something like "mtrr mapping" and the options are "continuous" and "discrete". I *think* they will do this.... So the question becomes, could this be listed by a non-obvious name? Joe Andi Kleen wrote:
And what to do for non-Opteron?
The same ("all current AMD parts")
I have AMD Athlon X86_64 4200+ K8 Tridon nForce 4 SLi GA-K8N Ultra-SLi w/4 GB and show 3350428 kB
note: I see no provision for remapping memory in the BIOS.
Then you're out of luck unless you can get a BIOS update that fixes this. However cheap motherboards tend to not care much about the lots-of-memory case unfortunately and they might have saved some dollars by not testing this (that is why it sometimes doesn't work) or not support it at all.
-Andi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
"Joe Georger" <jgeorger@ll.mit.edu> wrote on 12:57 20/03/2007 +0100 :
I don't feel like rebooting my machine to check but IIRC Tyan boards have something like "mtrr mapping" and the options are "continuous" and "discrete". I *think* they will do this.... So the question becomes, could this be listed by a non-obvious name?
well mtrr mapping is just a different topic and controls the cache mechanism (write through, write back, non-cacheable, etc) of memory ranges. This is unrelated with the mem hole remapping which can also be called memory hoisting. -Joachim --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Hello, I installed openSuSe 10.2 on a RAID-system. I intend to start linux with lilo a boot-manager on /dev/mapper/nvidia_cddeggfb_part5 as offered during setup. After /sbin/lilo -C /etc/lilo.conf I got the error message: "sorry, don't know how to handle device 0xfd06." Could anyone help me, how to solve this problem? My hardware: Mainboard: MSI K9N ultra CPU: AMD Athlon 64 3500+ Raidcontroller: nForce 570 RAID-Controller Thank you! Regards Wolfgang Bock ****************************************
wolfgang bock wolfgang.bock@wbock.de *************************** ;-) ********
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
* Wolfgang Bock <wolfgang.bock@wbock.de> [070320 14:51]:
Hello,
I installed openSuSe 10.2 on a RAID-system.
I intend to start linux with lilo a boot-manager on /dev/mapper/nvidia_cddeggfb_part5 as offered during setup.
After /sbin/lilo -C /etc/lilo.conf I got the error message: "sorry, don't know how to handle device 0xfd06."
Could anyone help me, how to solve this problem?
Use grub. This is no guarantee, but at least it proved to work on the setups we tested.
Regards
Wolfgang Bock
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Regards, Stefan -- SUSE LINUX Products GmbH GF: Markus Rex, HRB 16746 (AG Nuernberg)) Maxfeldstr. 5 / D-90409 Nuernberg / Phone: +49-911-740 53 - 0 GPG 1024D/91614BBC B226 E3DA 37B0 2170 7403 D19C 18AF E579 9161 4BBC
Hello, installing GRUB doesn't work either. The error message is: ****** grub> setup --stage2=/boot/grub/stage2 (/dev/mapper/nvidia_cddeggfb,4) (/dev/mapper/nvidia_cddeggfb,4) Error 23: Error while parsing number grub> quit **** My menue.ls looks like this: **** # default 0 timeout 8 # title openSUSE 10.2 kernel (/dev/mapper/nvidia_cddeggfb,1)/boot/vmlinuz-2.6.18.2-34-default root=/dev/mapper/nvidia_cddeggfb_part5 vga=0x31a resume=/dev/mapper/nvidia_cddeggfb_part6 splash=silent showopts initrd (/dev/mapper/nvidia_cddeggfb,1)/boot/initrd-2.6.18.2-34-default title Windows rootnoverify (hd0,0) chainloader (/dev/mapper/nvidia_cddeggfb,0)+1 ... **** The partitiontable: Disk /dev/mapper/nvidia_cddeggfb: 164.6 GB, 164696424448 bytes 255 heads, 63 sectors/track, 20023 cylinders, total 321672704 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/mapper/nvidia_cddeggfb1 63 1028159 514048+ 6 FAT16 /dev/mapper/nvidia_cddeggfb2 * 1028160 321669494 160320667+ 5 Extended /dev/mapper/nvidia_cddeggfb5 1028228 32483429 15727601 83 Linux /dev/mapper/nvidia_cddeggfb6 32483493 36692459 2104483+ 82 Linux swap / Solaris /dev/mapper/nvidia_cddeggfb7 36692529 60854219 12080845+ 83 Linux /dev/mapper/nvidia_cddeggfb8 60854283 92325554 15735636 7 HPFS/NTFS .... **** Can anyone help? Regards Wolfgang Bock -----Ursprüngliche Nachricht----- Von: Stefan Fent [mailto:sf@suse.de] Gesendet: Dienstag, 20. März 2007 15:55 An: opensuse-amd64@opensuse.org Betreff: Re: [opensuse-amd64] ... don't know how to handle device 0xfd06 * Wolfgang Bock <wolfgang.bock@wbock.de> [070320 14:51]:
Hello,
I installed openSuSe 10.2 on a RAID-system.
I intend to start linux with lilo a boot-manager on /dev/mapper/nvidia_cddeggfb_part5 as offered during setup.
After /sbin/lilo -C /etc/lilo.conf I got the error message: "sorry, don't know how to handle device 0xfd06."
Could anyone help me, how to solve this problem?
Use grub. This is no guarantee, but at least it proved to work on the setups we tested.
Regards
Wolfgang Bock
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Regards, Stefan -- SUSE LINUX Products GmbH GF: Markus Rex, HRB 16746 (AG Nuernberg)) Maxfeldstr. 5 / D-90409 Nuernberg / Phone: +49-911-740 53 - 0 GPG 1024D/91614BBC B226 E3DA 37B0 2170 7403 D19C 18AF E579 9161 4BBC --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Remapping in the BIOS is possible with all current AMD parts: -- First off, some BIOSes have bugs, so test it out before just using it!
Or rather if your system starts crashing randomly afterwards don't blame Linux but undo that setting. -Andi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
participants (8)
-
Andi Kleen -
Erich Boleyn -
James D. Parra -
Joachim Deguara -
Joe Georger -
Patrick Shanahan -
Stefan Fent -
Wolfgang Bock