Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Owain Ainsworth wrote: Enabling bigmem=1: Also, from sys/arch/amd64/amd64/machdep.c: /* Tweakable by config(8) */ How? That diff was never commited. Config needs to know about it before it can change it. I did a similar config(8) patch for when PAE was in the same situation, so if someone desperately wants to make his/her config bigmem-aware and wants a hint on how to turn a random int on from config(8): http://people.su.se/~jj/obsd/config-pae.diff
Re: : : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Wed, Dec 17, 2008 at 07:34:07PM +0100, Markus Hennecke wrote:
Raimo Niskanen schrieb:
[config description]
But how to find a bigmem parameter I do not know, I have
no amd64 system. Try 'help' in the config editor.
And, as pointed out before:
If you search the archives, you'll find the clue you need to enable it
on your own system.
See also:
config(8)
options(4)
boot_config(8)
boot_i386(8)
boot(8)
So I read all that before and now I have to out me as plain stupid. I
still have no clue how to set bigmem to 1 using config(8). And as you
can see in this thread, it looks like I am not alone. Either I read over
it on more than one occasion, or there is no documentation describing it.
Sorry about that. I could only give you some pointers on how to use
UCK(config(8)) and have no amd64 system myself, so I deemed it probably
futile for me to try to find the bigmem parameter.
Then I assumed the rest of the clues _would_ be in the archives
but did not search myself. They still might be in the archives
but a later post in this thread suggests you can not do this with
config(8). You probably will have to compile a kernel.
I have searched the 4.4 kernel source tree and found:
$ find sys -type f | xargs grep -i bigmem
sys/arch/amd64/amd64/machdep.c:int bigmem = 1;
sys/arch/amd64/amd64/machdep.c: if (bigmem)
sys/arch/amd64/amd64/machdep.c: printf(Bigmem = %d\n, bigmem);
sys/arch/amd64/amd64/machdep.c: if (!bigmem (e1 = (1UL32))) {
sys/arch/amd64/amd64/machdep.c: } else if (bigmem (e1 = (1UL32)))
{
The revision of the file is 1.81 so that was just
before the release. In the cvsweb
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/amd64/machdep.c
it says bigmem was set to 0 for the release of 4.4, and it still is
(revision 1.85).
I can also not find a documented way to tweak it from config(8)
as it is stated on the comment line before int bigmem = 0;.
It is probably daft simple or untrue. But changing the line to
int bigmem = 1; in the source code will certainly do the trick.
Kind regards,
Markus
--
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Enabling bigmem=1: -real mem = 3734757376 (3561MB) -avail mem = 3624775680 (3456MB) +real mem = 4271632384 (4073MB) +avail mem = 4148350976 (3956MB) Also, from sys/arch/amd64/amd64/machdep.c: /* Tweakable by config(8) */ How? 2008/12/16 Toni Mueller openbsd-m...@oeko.net: Hello, On Mon, 15.12.2008 at 15:47:06 +0100, Paul de Weerd we...@weirdnet.nl wrote: On Mon, Dec 15, 2008 at 10:40:44PM +0800, C. Soragan Ong wrote: | I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is the | dmesg Well, all memory is found (see the spdmem entries in your dmesg), but these messages suggest that he has 4GB of RAM installed in his machine, right? not all of it is supported by the default kernel. You'll have to enable bigmem and compile a new kernel yourself. I thought that 4GB of RAM *are* supported in the default kernel? But apart from that, I'm having a quite similar problem with a completely different machine. It turns out that very much RAM is eaten, depending on various BIOS settings. I haven't figured out how to tune it, but currently I'm losing some 700+MB this way (really AWFUL!). I have found out that enabling PXE eats some 20MB per NIC on which it is enabled, though. Kind regards, --Toni++
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Thu, Dec 18, 2008 at 2:01 AM, Stephan A. Rickauer stephan.ricka...@ini.phys.ethz.ch wrote: On Wed, 2008-12-17 at 14:52 -0500, Ted Unangst wrote: On Tue, Dec 16, 2008 at 7:43 AM, C. Soragan Ong sora...@guox.net wrote: so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) the only permanent way to set that is to change the source and recompile. Is there a non-permanent way? boot -d, then change it in ddb before continuing.
Re: : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Thu, Dec 18, 2008 at 09:32:57AM -0500, Ted Unangst wrote: On Thu, Dec 18, 2008 at 2:01 AM, Stephan A. Rickauer stephan.ricka...@ini.phys.ethz.ch wrote: On Wed, 2008-12-17 at 14:52 -0500, Ted Unangst wrote: On Tue, Dec 16, 2008 at 7:43 AM, C. Soragan Ong sora...@guox.net wrote: so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) the only permanent way to set that is to change the source and recompile. Is there a non-permanent way? boot -d, then change it in ddb before continuing. Right then, to conclude... It seems the comment /* Tweakable by config(8) */ in sys/arch/amd64/amd64/machdep.c is in error. The variable can not be changed from config(8), neither before kernel compilation nor on a compiled kernel. And it can also not be changed from UKC via boot -c. But it can certainly be changed by editing the line in sys/arch/amd64/amd64/machdep.c to int bigmem = 1; and then compiling a kernel. And it can be temporarily changed via boot -d as stated above by Ted. Objections, anyone? -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Thu, Dec 18, 2008 at 08:30:48PM +0900, Jordi Beltran Creix wrote: Enabling bigmem=1: -real mem = 3734757376 (3561MB) -avail mem = 3624775680 (3456MB) +real mem = 4271632384 (4073MB) +avail mem = 4148350976 (3956MB) Also, from sys/arch/amd64/amd64/machdep.c: /* Tweakable by config(8) */ How? That diff was never commited. Config needs to know about it before it can change it. -0- -- There is a green, multi-legged creature crawling on your shoulder.
Re: : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Tue, Dec 16, 2008 at 08:43:46PM +0800, C. Soragan Ong wrote: so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) Ok. No, you run something like config -e /bsd -o /bsd.new. This will put you in an interactive editor that takes the kernel /bsd, enables you to modify parameters in it, and writes a new kernel /bsd.new with modified parameters. Then you use that new kernel instead. You can also invoke config (or rather UKC) when booting and try modifying some parameters temporarily for that boot. But how to find a bigmem parameter I do not know, I have no amd64 system. Try 'help' in the config editor. And, as pointed out before: If you search the archives, you'll find the clue you need to enable it on your own system. See also: config(8) options(4) boot_config(8) boot_i386(8) boot(8) Regards, Soragan On Tue, Dec 16, 2008 at 5:49 PM, Stephan A. Rickauer stephan.ricka...@ini.phys.ethz.ch wrote: On Mon, 2008-12-15 at 07:39 -0800, Chris Kuethe wrote: no. the config program can do this without a recompile. I also would like to learn how to do that since we have a couple of 'big' amd64 machines I could test on. Cheers, -- Stephan A. Rickauer --- Institute of Neuroinformatics Tel +41 44 635 30 50 University / ETH Zurich Sec +41 44 635 30 52 Winterthurerstrasse 190 Fax +41 44 635 30 53 CH-8057 ZurichWebwww.ini.uzh.ch -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Raimo Niskanen schrieb: [config description] But how to find a bigmem parameter I do not know, I have no amd64 system. Try 'help' in the config editor. And, as pointed out before: If you search the archives, you'll find the clue you need to enable it on your own system. See also: config(8) options(4) boot_config(8) boot_i386(8) boot(8) So I read all that before and now I have to out me as plain stupid. I still have no clue how to set bigmem to 1 using config(8). And as you can see in this thread, it looks like I am not alone. Either I read over it on more than one occasion, or there is no documentation describing it. Kind regards, Markus
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Tue, Dec 16, 2008 at 7:43 AM, C. Soragan Ong sora...@guox.net wrote: so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) the only permanent way to set that is to change the source and recompile.
Re: : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Wed, Dec 17, 2008 at 1:34 PM, Markus Hennecke markus-henne...@markus-hennecke.de wrote: So I read all that before and now I have to out me as plain stupid. I still have no clue how to set bigmem to 1 using config(8). And as you can see in this thread, it looks like I am not alone. Either I read over it on more than one occasion, or there is no documentation describing it. You can't set random variables using config.
Re: : OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
yeah, that was my mistake. i could've sworn i've set bigmem that way to avoid a recompile... i'll shut up now. On Wed, Dec 17, 2008 at 11:50 AM, Ted Unangst ted.unan...@gmail.com wrote: On Wed, Dec 17, 2008 at 1:34 PM, Markus Hennecke markus-henne...@markus-hennecke.de wrote: So I read all that before and now I have to out me as plain stupid. I still have no clue how to set bigmem to 1 using config(8). And as you can see in this thread, it looks like I am not alone. Either I read over it on more than one occasion, or there is no documentation describing it. You can't set random variables using config. -- GDB has a 'break' feature; why doesn't it have 'fix' too?
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Wed, 2008-12-17 at 14:52 -0500, Ted Unangst wrote: On Tue, Dec 16, 2008 at 7:43 AM, C. Soragan Ong sora...@guox.net wrote: so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) the only permanent way to set that is to change the source and recompile. Is there a non-permanent way?
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Mon, 2008-12-15 at 07:39 -0800, Chris Kuethe wrote: no. the config program can do this without a recompile. I also would like to learn how to do that since we have a couple of 'big' amd64 machines I could test on. Cheers, -- Stephan A. Rickauer --- Institute of Neuroinformatics Tel +41 44 635 30 50 University / ETH Zurich Sec +41 44 635 30 52 Winterthurerstrasse 190 Fax +41 44 635 30 53 CH-8057 ZurichWebwww.ini.uzh.ch
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
so let say put set bigmem=1 into /etc/boot.conf will activate the bigmem? correct me if i am wrong, i am new with openbsd :) Regards, Soragan On Tue, Dec 16, 2008 at 5:49 PM, Stephan A. Rickauer stephan.ricka...@ini.phys.ethz.ch wrote: On Mon, 2008-12-15 at 07:39 -0800, Chris Kuethe wrote: no. the config program can do this without a recompile. I also would like to learn how to do that since we have a couple of 'big' amd64 machines I could test on. Cheers, -- Stephan A. Rickauer --- Institute of Neuroinformatics Tel +41 44 635 30 50 University / ETH Zurich Sec +41 44 635 30 52 Winterthurerstrasse 190 Fax +41 44 635 30 53 CH-8057 ZurichWebwww.ini.uzh.ch -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Hi All, I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is the dmesg OpenBSD 4.4 (GENERIC.MP) #1812: Tue Aug 12 17:22:53 MDT 2008 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3073273856 (2930MB) avail mem = 2979676160 (2841MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (68 entries) bios0: vendor American Megatrends Inc. version 0702 date 05/07/2008 bios0: ASUSTeK Computer INC. M2N-VM HDMI acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC MCFG OEMB HPET NVHD acpi0: wakeup devices PS2K(S4) PS2M(S4) UAR1(S4) NSMB(S4) USB0(S4) USB2(S3) US15(S4) US12(S3) NMAC(S5) P0P1(S4) HDAC(S4) BR10( S4) BR11(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 3000.77 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX, FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 3000.28 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX, FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins acpihpet0 at acpi0: 2500 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus 2 (BR10) acpiprt3 at acpi0: bus 3 (BR11) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB cpu0: PowerNow! K8 3000 MHz: speeds: 3000 2800 2600 2400 2200 2000 1800 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 NVIDIA MCP67 Memory rev 0xa2 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA MCP67 Host rev 0xa2 nviic0 at pci0 dev 1 function 1 NVIDIA MCP67 SMBus rev 0xa2 iic0 at nviic0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5 spdmem1 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-6400CL5 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 (irq 11), version 1.0, legacy support ehci0 at pci0 dev 2 function 1 NVIDIA MCP67 USB rev 0xa2: apic 2 int 10 (irq 10) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 4 function 0 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 (irq 11), version 1.0, legacy support ehci1 at pci0 dev 4 function 1 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 (irq 11) usb1 at ehci1: USB revision 2.0 uhub1 at usb1 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 pciide0 at pci0 dev 6 function 0 NVIDIA MCP67 IDE rev 0xa1: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 90422D2 wd0: 16-sector PIO, LBA, 4028MB, 8249472 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) azalia0 at pci0 dev 7 function 0 NVIDIA MCP67 HD Audio rev 0xa1: apic 2 int 11 (irq 11) azalia0: /usr/src/sys/dev/pci/azalia.c/1348 invalid PCM format: 0x azalia0: codec[s]: Realtek ALC883, NVIDIA/0x0067, using Realtek ALC883 audio0 at azalia0 ppb0 at pci0 dev 8 function 0 NVIDIA MCP67 PCI rev 0xa2 pci1 at ppb0 bus 1 re0 at pci1 dev 6 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), apic 2 int 11 (irq 11), address 00:06:4f:63:93: 3a rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 3 re1 at pci1 dev 7 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB (0x1000), apic 2 int 11 (irq 11), address 00:06:4f:63:93: 35 rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 3 pciide1 at pci0 dev 9 function 0 NVIDIA MCP67 SATA rev 0xa2: DMA pciide1: using apic 2 int 15 (irq 15) for native-PCI interrupt nfe0 at pci0 dev 10 function 0 NVIDIA MCP67 LAN rev 0xa2: apic 2 int 10 (irq 10), address 00:22:15:00:75:11 ukphy0 at nfe0 phy 1: Generic IEEE 802.3u media interface, rev. 6: OUI 0x001374, model 0x0001 ppb1 at pci0 dev 11 function 0 vendor NVIDIA, unknown product 0x0562 rev 0xa2 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 NVIDIA MCP67 PCIE rev 0xa2 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA MCP67 PCIE rev 0xa2 pci4 at ppb3 bus 4 ppb4 at pci0 dev 14 function 0 NVIDIA MCP67 PCIE rev 0xa2 pci5 at ppb4 bus 5 ppb5 at pci0 dev 15 function 0 NVIDIA MCP67 PCIE rev 0xa2 pci6 at ppb5 bus 6 ppb6 at pci0 dev 16 function 0 NVIDIA MCP67 PCIE rev 0xa2 pci7 at ppb6 bus
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Mon, Dec 15, 2008 at 10:40:44PM +0800, C. Soragan Ong wrote: | Hi All, | | I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is the | dmesg Well, all memory is found (see the spdmem entries in your dmesg), but not all of it is supported by the default kernel. You'll have to enable bigmem and compile a new kernel yourself. Note that this was disabled shortly before 4.4 was tagged in cvs because of some problems. If you search the archives, you'll find the clue you need to enable it on your own system. Cheers, Paul 'WEiRD' de WEerd | OpenBSD 4.4 (GENERIC.MP) #1812: Tue Aug 12 17:22:53 MDT 2008 | dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP | real mem = 3073273856 (2930MB) | avail mem = 2979676160 (2841MB) | mainbus0 at root | bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f400 (68 entries) | bios0: vendor American Megatrends Inc. version 0702 date 05/07/2008 | bios0: ASUSTeK Computer INC. M2N-VM HDMI | acpi0 at bios0: rev 0 | acpi0: tables DSDT FACP APIC MCFG OEMB HPET NVHD | acpi0: wakeup devices PS2K(S4) PS2M(S4) UAR1(S4) NSMB(S4) USB0(S4) USB2(S3) | US15(S4) US12(S3) NMAC(S5) P0P1(S4) HDAC(S4) BR10( | S4) BR11(S4) SLPB(S4) | acpitimer0 at acpi0: 3579545 Hz, 24 bits | acpimadt0 at acpi0 addr 0xfee0: PC-AT compat | cpu0 at mainbus0: apid 0 (boot processor) | cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 3000.77 MHz | cpu0: | FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX, | FFXSR,LONG,3DNOW2,3DNOW | cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line | 16-way L2 cache | cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative | cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative | cpu0: apic clock running at 200MHz | cpu1 at mainbus0: apid 1 (application processor) | cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+, 3000.28 MHz | cpu1: | FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX, | FFXSR,LONG,3DNOW2,3DNOW | cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line | 16-way L2 cache | cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative | cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative | ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins | acpihpet0 at acpi0: 2500 Hz | acpiprt0 at acpi0: bus 0 (PCI0) | acpiprt1 at acpi0: bus 1 (P0P1) | acpiprt2 at acpi0: bus 2 (BR10) | acpiprt3 at acpi0: bus 3 (BR11) | acpicpu0 at acpi0 | acpicpu1 at acpi0 | acpibtn0 at acpi0: SLPB | acpibtn1 at acpi0: PWRB | cpu0: PowerNow! K8 3000 MHz: speeds: 3000 2800 2600 2400 2200 2000 1800 1000 | MHz | pci0 at mainbus0 bus 0: configuration mode 1 | NVIDIA MCP67 Memory rev 0xa2 at pci0 dev 0 function 0 not configured | pcib0 at pci0 dev 1 function 0 NVIDIA MCP67 Host rev 0xa2 | nviic0 at pci0 dev 1 function 1 NVIDIA MCP67 SMBus rev 0xa2 | iic0 at nviic0 | spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5 | spdmem1 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-6400CL5 | iic1 at nviic0 | ohci0 at pci0 dev 2 function 0 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 | (irq 11), version 1.0, legacy support | ehci0 at pci0 dev 2 function 1 NVIDIA MCP67 USB rev 0xa2: apic 2 int 10 | (irq 10) | usb0 at ehci0: USB revision 2.0 | uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 | ohci1 at pci0 dev 4 function 0 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 | (irq 11), version 1.0, legacy support | ehci1 at pci0 dev 4 function 1 NVIDIA MCP67 USB rev 0xa2: apic 2 int 11 | (irq 11) | usb1 at ehci1: USB revision 2.0 | uhub1 at usb1 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 | pciide0 at pci0 dev 6 function 0 NVIDIA MCP67 IDE rev 0xa1: DMA, channel 0 | configured to compatibility, channel 1 configured | to compatibility | wd0 at pciide0 channel 0 drive 0: Maxtor 90422D2 | wd0: 16-sector PIO, LBA, 4028MB, 8249472 sectors | wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 | pciide0: channel 1 ignored (disabled) | azalia0 at pci0 dev 7 function 0 NVIDIA MCP67 HD Audio rev 0xa1: apic 2 | int 11 (irq 11) | azalia0: /usr/src/sys/dev/pci/azalia.c/1348 invalid PCM format: 0x | azalia0: codec[s]: Realtek ALC883, NVIDIA/0x0067, using Realtek ALC883 | audio0 at azalia0 | ppb0 at pci0 dev 8 function 0 NVIDIA MCP67 PCI rev 0xa2 | pci1 at ppb0 bus 1 | re0 at pci1 dev 6 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB | (0x1000), apic 2 int 11 (irq 11), address 00:06:4f:63:93: | 3a | rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 3 | re1 at pci1 dev 7 function 0 Realtek 8169 rev 0x10: RTL8169/8110SB | (0x1000), apic 2 int 11 (irq 11), address 00:06:4f:63:93: | 35 | rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 3 | pciide1 at pci0 dev 9 function 0 NVIDIA MCP67 SATA rev 0xa2: DMA | pciide1: using apic 2 int 15 (irq 15) for native-PCI interrupt | nfe0 at pci0 dev 10
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Chris Kuethe schrieb: On Mon, Dec 15, 2008 at 6:47 AM, Paul de Weerd we...@weirdnet.nl wrote: You'll have to enable bigmem yes. and compile a new kernel yourself. no. the config program can do this without a recompile. I have seen the comment in machdep.c, but it looks like I am to stupid to figure out how to do it that way. This seems to be an excellent occasion to enlighten me, could you tell me how to change it with config? Kind regards, Markus
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Mon, Dec 15, 2008 at 6:47 AM, Paul de Weerd we...@weirdnet.nl wrote: You'll have to enable bigmem yes. and compile a new kernel yourself. no. the config program can do this without a recompile. -- GDB has a 'break' feature; why doesn't it have 'fix' too?
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Hello, On Mon, 15.12.2008 at 15:47:06 +0100, Paul de Weerd we...@weirdnet.nl wrote: On Mon, Dec 15, 2008 at 10:40:44PM +0800, C. Soragan Ong wrote: | I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is the | dmesg Well, all memory is found (see the spdmem entries in your dmesg), but these messages suggest that he has 4GB of RAM installed in his machine, right? not all of it is supported by the default kernel. You'll have to enable bigmem and compile a new kernel yourself. I thought that 4GB of RAM *are* supported in the default kernel? But apart from that, I'm having a quite similar problem with a completely different machine. It turns out that very much RAM is eaten, depending on various BIOS settings. I haven't figured out how to tune it, but currently I'm losing some 700+MB this way (really AWFUL!). I have found out that enabling PXE eats some 20MB per NIC on which it is enabled, though. Kind regards, --Toni++
Re: OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
On Mon, 15 Dec 2008 22:40:44 +0800 C. Soragan Ong sora...@guox.net wrote: Hi All, I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is the dmesg OpenBSD 4.4 (GENERIC.MP) #1812: Tue Aug 12 17:22:53 MDT 2008 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3073273856 (2930MB) avail mem = 2979676160 (2841MB) [...] Here http://marc.info/?l=openbsd-miscm=122349979023721w=2 are my bigmem test results a little while ago. If you decide to try it out, it might be useful to the developers if you report your results.
