| View previous topic :: View next topic |
| Author |
Message |
jzono1
Tux's lil' helper
Joined: 01 Feb 2004
Posts: 128
|
 Posted: Sat Apr 21, 2007 3:23 pm Post subject: 64GB x86_64 kernel config wanted |
 |
|
Hey!
My DFI board is stubborn with 4GB of ram - it puts half above 4GB; and thus I think i need a 64GB highmem enabled kernel, thing is, I can't find that option in menuconfig 
Anyone know how to find that option, or got a working x86_64 kernel with 64GB ram support that I could borrow the config from? |
|
| Back to top |
|
 |
IQgryn
l33t
Joined: 05 Sep 2005
Posts: 764
Location: WI, USA
|
| Posted: Sat Apr 21, 2007 4:22 pm Post subject: |
|
|
| Code: | Symbol: HIGHMEM64G [=n]
Prompt: 64GB
Defined at arch/i386/Kconfig:510
Depends on: <choice> && X86_CMPXCHG64
Location:
-> Processor type and features
-> High Memory Support (<choice> [=y]) |
(found by typing "/HIGHMEM" in menuconfig) |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Sat Apr 21, 2007 4:44 pm Post subject: |
|
|
But that's only for i386 "Defined at arch/i386/Kconfig:510": does it apply if you are running x86_64 in 32-bit mode?
jzono1: are you running in 64-bit mode? If so there should be no need to specify 4G or 64G as to x86_64 it all looks the same.
Could it be a BIOS setting?
Does it really matter if 2G is above the 4G mark if it is all virtual anyway?
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
jzono1
Tux's lil' helper
Joined: 01 Feb 2004
Posts: 128
|
| Posted: Sat Apr 21, 2007 5:41 pm Post subject: |
|
|
Yup, I'm running in 64bit mode.
It doesn't show up there.
There's a bios setting for memory hole remapping but it doesn't change anything. Without limiting memory to the first 2GB of adresses, it fails miserably, everything gives general protection faults. |
|
| Back to top |
|
|
wynn
Advocate
Joined: 01 Apr 2005
Posts: 2421
Location: UK
|
| Posted: Sat Apr 21, 2007 6:21 pm Post subject: |
|
|
From what I know about x86_64, there is no 4G/64G as there is no need for it. It was a workaround for i386 to use more memory than can be mapped linearly into the 4G architecture address space.
Could you give more details of your DFI board and perhaps the beginning of a boot in /var/log/messages? Like this | Code: | Apr 21 18:57:06 greyarea syslog-ng[4774]: syslog-ng version 1.6.11 starting
Apr 21 18:57:06 greyarea Linux version 2.6.20-gentoo-r6 (wynn@greyarea) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #1 PREEMPT Mon Apr 16 09:16:54 BST2007
Apr 21 18:57:06 greyarea Command line: vga=0x31a
Apr 21 18:57:06 greyarea BIOS-provided physical RAM map:
Apr 21 18:57:06 greyarea BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Apr 21 18:57:06 greyarea BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Apr 21 18:57:06 greyarea BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
Apr 21 18:57:06 greyarea BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable)
Apr 21 18:57:06 greyarea BIOS-e820: 00000000bffb0000 - 00000000bffc0000 (ACPI data)
Apr 21 18:57:06 greyarea BIOS-e820: 00000000bffc0000 - 00000000bfff0000 (ACPI NVS)
Apr 21 18:57:06 greyarea BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved)
Apr 21 18:57:06 greyarea BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
Apr 21 18:57:06 greyarea end_pfn_map = 1048576 |
It's 3G, not 4G and the "BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable)" shows it running linearly from 1 megabyte (0x0000000000100000) to 3071 megabytes (0x00000000bffb0000).
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details. |
|
| Back to top |
|
|
jzono1
Tux's lil' helper
Joined: 01 Feb 2004
Posts: 128
|
| Posted: Sun Apr 22, 2007 11:52 am Post subject: |
|
|
It's the Infinity 975X/G. It's suposed to support up to 8GB of ram, and it uses the 975X chipset. With an older bios I had it booting without problems with 4GB of ram, but that bios refuses to boot if I use the eSATA controller, and it's not useable for eventual overclocking When I booted with that bios, the mtrrs looked kinda more normal.
Messed up mtrr's:
| Code: |
crashforsk jo # cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
reg01: base=0x100000000 (4096MB), size=2048MB: write-back, count=1
reg02: base=0x80000000 (2048MB), size=2048MB: uncachable, count=1
reg03: base=0x00f00000 ( 15MB), size= 1MB: uncachable, count=1
reg04: base=0x7ff00000 (2047MB), size= 1MB: uncachable, count=1
|
Start of dmesg:
| Code: |
crashforsk jo # head -n 20 /var/log/dmesg
12 14 15)
[ 52.873041] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 11 12 14 *15)
[ 52.873461] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 *10 11 12 14 15)
[ 52.873873] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 7 9 10 11 12 14 15)
[ 52.874288] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
[ 52.874759] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
[ 52.875232] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 *9 10 11 12 14 15)
[ 52.875638] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 52.875682] pnp: PnP ACPI init
[ 52.878104] pnp: PnP ACPI: found 15 devices
[ 52.878250] SCSI subsystem initialized
[ 52.878311] libata version 2.20 loaded.
[ 52.878361] usbcore: registered new interface driver usbfs
[ 52.878422] usbcore: registered new interface driver hub
[ 52.878481] usbcore: registered new device driver usb
[ 52.878565] PCI: Using ACPI for IRQ routing
[ 52.878602] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 52.878707] Bluetooth: Core ver 2.11
[ 52.878775] NET: Registered protocol family 31
[ 52.878812] Bluetooth: HCI device and connection manager initialized
|
|
|
| Back to top |
|
|
|
Kernel & Hardware
