Re: Intel Core2 Dual/Quad - i386 or amd64?
On Wednesday 26 March 2008 12:08:35 Alexander Hall wrote:
[EMAIL PROTECTED] wrote:
It appears that the wireless driver your Thinkpad requires
wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG
is not supported in OpenBSD/amd64. See
http://www.openbsd.org/amd64.html
That is not true. Both wpi(4) and iwn(4) are in amd64 GENERIC.
The web page needs an update though.
Ok, I thought it seemed a little strange, but who was I to question the
docs? :)
Thanks for the update.
I have corrected this, http://www.openbsd.org/{i386,amd64}.html should now
correctly reflect what each arch can do wrt Intel wirless.
Regards
Johan M:son
Re: Intel Core2 Dual/Quad - i386 or amd64?
Matthew Szudzik wrote I have two computers I'm considering going amd64 on: 1. My Thinkpad X61s (1GB RAM) It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html and Another thing to keep in mind is that there are some OpenBSD packages and ports that only run on i386. In particular, any software that requires Linux emulation (such as the opera-flashplugin) will not run on amd64. These are important issues that I did not think of. I will probably not need java on our server but it seems I could compile jdk1.6 and 1.7 natively if so. I would prefer not running linux blobs on the server anyway... :-) All in all, I now aim to run amd64 on the server but the wireless issue (which I assume is correct, though I have not verified it), will prevent me from running it on the laptop. Thank you for your replies! /Alexander
Re: Intel Core2 Dual/Quad - i386 or amd64?
It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html That is not true. Both wpi(4) and iwn(4) are in amd64 GENERIC. The web page needs an update though. Damien
Re: Intel Core2 Dual/Quad - i386 or amd64?
[EMAIL PROTECTED] wrote: It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html That is not true. Both wpi(4) and iwn(4) are in amd64 GENERIC. The web page needs an update though. Ok, I thought it seemed a little strange, but who was I to question the docs? :) Thanks for the update.
Re: Intel Core2 Dual/Quad - i386 or amd64?
On Wed, Mar 26, 2008 at 10:23:56AM +0100, Alexander Hall wrote: Matthew Szudzik wrote I have two computers I'm considering going amd64 on: 1. My Thinkpad X61s (1GB RAM) It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html and Another thing to keep in mind is that there are some OpenBSD packages and ports that only run on i386. In particular, any software that requires Linux emulation (such as the opera-flashplugin) will not run on amd64. These are important issues that I did not think of. I will probably not need java on our server but it seems I could compile jdk1.6 and 1.7 natively if so. I would prefer not running linux blobs on the server anyway... :-) All in all, I now aim to run amd64 on the server but the wireless issue (which I assume is correct, though I have not verified it), will prevent me from running it on the laptop. Thank you for your replies! I have an x61s, it dual boots i386 and amd64. Both works fine. So in that case don't worry about device support. :) -0- -- Too clever is dumb. -- Ogden Nash
Re: Intel Core2 Dual/Quad - i386 or amd64?
Owain Ainsworth wrote: I have an x61s, it dual boots i386 and amd64. Both works fine. So in that case don't worry about device support. :) Yeah I realized that (and installed amd64 on an usb stick just to test). :-) Thanks, /Alexander
Re: Intel Core2 Dual/Quad - i386 or amd64?
On 2008 Mar 25 (Tue) at 19:48:02 + (+), Matthew Szudzik wrote: : I have two computers I'm considering going amd64 on: : : 1. My Thinkpad X61s (1GB RAM) : :It appears that the wireless driver your Thinkpad requires : : wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 : :is not supported in OpenBSD/amd64. See : : http://www.openbsd.org/amd64.html : I use it daily in amd64. -- For an idea to be fashionable is ominous, since it must afterwards be always old-fashioned.
Re: Intel Core2 Dual/Quad - i386 or amd64?
On 2008 Mar 26 (Wed) at 10:23:56 +0100 (+0100), Alexander Hall wrote: Matthew Szudzik wrote I have two computers I'm considering going amd64 on: 1. My Thinkpad X61s (1GB RAM) It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html and Another thing to keep in mind is that there are some OpenBSD packages and ports that only run on i386. In particular, any software that requires Linux emulation (such as the opera-flashplugin) will not run on amd64. These are important issues that I did not think of. I will probably not need java on our server but it seems I could compile jdk1.6 and 1.7 natively if so. I would prefer not running linux blobs on the server anyway... :-) All in all, I now aim to run amd64 on the server but the wireless issue (which I assume is correct, though I have not verified it), will prevent me from running it on the laptop. wpi works in amd64 mode, no need to worry about that :). Thank you for your replies! /Alexander -- Keep grandma off the streets -- legalize bingo.
Intel Core2 Dual/Quad - i386 or amd64?
What is the recommended architecture to use for Intel's Core2 (Dual/Quad) processors? I have two computers I'm considering going amd64 on: 1. My Thinkpad X61s (1GB RAM) cpu0: Intel(R) Core(TM)2 Duo CPU L7300 @ 1.40GHz (GenuineIntel 686-class) 1.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR real mem = 1029984256 (982MB) avail mem = 987660288 (941MB) (full dmesg below) 2. Our new server (hopefully delivered to us tomorrow) - Intel Core2 Quad Processor (Q6600) - 4GB (4 * 1GB) ECC RAM (dmesg not available) I've found the following (likely incomplete) list of things that may affect the choice, or might be affected by it, are: - Memory (4GB limit) - W^X - 64-bit instructions /Alexander Thinkpad X61s dmesg follows (HARDY = GENERIC.MP + all acpi + bluetooth) - - - - - - OpenBSD 4.3-current (HARDY) #15: Tue Mar 18 21:58:48 CET 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/HARDY cpu0: Intel(R) Core(TM)2 Duo CPU L7300 @ 1.40GHz (GenuineIntel 686-class) 1.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR real mem = 1029984256 (982MB) avail mem = 987660288 (941MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/02/07, BIOS32 rev. 0 @ 0xfdc80, SMBIOS rev. 2.4 @ 0xe0010 (63 entries) bios0: vendor LENOVO version 7NET25WW (1.06 ) date 07/02/2007 bios0: LENOVO 766929G acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT ASF! SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpi device at acpi0 from table DSDT not configured acpi device at acpi0 from table FACP not configured acpi device at acpi0 from table SSDT not configured acpi device at acpi0 from table ECDT not configured acpi device at acpi0 from table TCPA not configured acpimadt0 at acpi0 table APIC addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU L7300 @ 1.40GHz (GenuineIntel 686-class) 1.40 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: duplicate apic id, remapped to apid 2 acpi device at acpi0 from table MCFG not configured acpihpet0 at acpi0 table HPET: 14318179 Hz acpi device at acpi0 from table SLIC not configured acpi device at acpi0 from table BOOT not configured acpi device at acpi0 from table ASF! not configured acpi device at acpi0 from table SSDT not configured acpi device at acpi0 from table SSDT not configured acpi device at acpi0 from table SSDT not configured acpi device at acpi0 from table SSDT not configured acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus -1 (EXP3) acpiprt6 at acpi0: bus -1 (EXP4) acpiprt7 at acpi0: bus 5 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpicpu1 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T5247 serial 620 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpidock0 at acpi0: GDCK: not docked (0) bios0: ROM list: 0xc/0x1! 0xd/0x1000 0xd1000/0x1000 0xe/0x1! cpu0: unknown Enhanced SpeedStep CPU, msr 0x0615082506000825 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1600 MHz (1292 mV): speeds: 1600, 1200 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c vga1 at pci0 dev 2 function 0 Intel GM965 Video rev 0x0c wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xe000, size 0x800 Intel GM965 Video rev 0x0c at pci0 dev 2 function 1 not configured em0 at pci0 dev 25 function 0 Intel ICH8 IGP M AMT rev 0x03: apic 2 int 20 (irq 11), address 00:16:d3:ca:1a:1f uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: apic 2 int 20 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: apic 2 int 21 (irq 11) ehci0 at pci0 dev 26 function 7 Intel 82801H USB rev 0x03: apic 2 int 22 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27
Re: Intel Core2 Dual/Quad - i386 or amd64?
Alexander Hall wrote: What is the recommended architecture to use for Intel's Core2 (Dual/Quad) processors? I have two computers I'm considering going amd64 on: ... I've found the following (likely incomplete) list of things that may affect the choice, or might be affected by it, are: - Memory (4GB limit) - W^X W^X is available on most OpenBSD platforms, including i386 and amd64. - 64-bit instructions as a user, you don't execute instructions directly, so this is mostly just bigger is better hype, the same reason people get excited about seeing all their cores in their dmesg on an app that a 100MHz Pentium could do just fine on. Most of the same apps work on i386 as on amd64, you really don't care what instructions are being executed (or how many bits are in 'em) to make them run. http://www.openbsd.org/faq/faq12.html#amd64Intel To be honest, most users probably won't see a difference. Me? I'd probably go with amd64, as practically speaking, i386 is slowly moving into the legacy category. I say probably, because I would very possibly forget and accidentally install i386 on it. :) Ok, based on the fact that I did that today already, let's say I'd SUGGEST going with amd64, even though I'd probably forget and go with i386 myself. :) Nick.
Re: Intel Core2 Dual/Quad - i386 or amd64?
On Tue, Mar 25, 2008 at 03:22:38PM -0400, Nick Holland wrote: Me? I'd probably go with amd64, as practically speaking, i386 is slowly moving into the legacy category. This coming from Nick 2.8-CURRENT Just Finished Compiling On My 68020-based Mac Holland... :) Gord
Re: Intel Core2 Dual/Quad - i386 or amd64?
I have two computers I'm considering going amd64 on: 1. My Thinkpad X61s (1GB RAM) It appears that the wireless driver your Thinkpad requires wpi0 at pci2 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 2 is not supported in OpenBSD/amd64. See http://www.openbsd.org/amd64.html
Re: Intel Core2 Dual/Quad - i386 or amd64?
Nick Holland wrote: Alexander Hall wrote: What is the recommended architecture to use for Intel's Core2 (Dual/Quad) processors? I have two computers I'm considering going amd64 on: ... I've found the following (likely incomplete) list of things that may affect the choice, or might be affected by it, are: - Memory (4GB limit) - W^X W^X is available on most OpenBSD platforms, including i386 and amd64. From http://openbsd.org/amd64.html: (Some Intel processors lack support for important PAE NX bit, which means those machines will run without any W^X support -- it is thus safer to run those machines in i386 mode). From my dmesg, i can see a PAE, but I do not know if that's the PAE NX bit... - 64-bit instructions as a user, you don't execute instructions directly, so this is mostly just bigger is better hype, the same reason people get excited about seeing all their cores in their dmesg on an app that a 100MHz Pentium could do just fine on. Most of the same apps work on i386 as on amd64, you really don't care what instructions are being executed (or how many bits are in 'em) to make them run. Yeah, I was just thinking it would make me to use the CPU cycles more efficiently. I wouldn't expect anything drastic though. http://www.openbsd.org/faq/faq12.html#amd64Intel And I even searched the FAQ... How could I miss this? Please accept my apologies. :-d To be honest, most users probably won't see a difference. Me? I'd probably go with amd64, as practically speaking, i386 is slowly moving into the legacy category. I say probably, because I would very possibly forget and accidentally install i386 on it. :) Ok, based on the fact that I did that today already, let's say I'd SUGGEST going with amd64, even though I'd probably forget and go with i386 myself. :) Ok, thanks! /Alexander
Re: Intel Core2 Dual/Quad - i386 or amd64?
Nick Holland wrote: Ok, based on the fact that I did that today already, let's say I'd SUGGEST going with amd64, even though I'd probably forget and go with i386 myself. :) Weren't there some problems with interrupt performance on amd64? Maybe that's fixed already.
Re: Intel Core2 Dual/Quad - i386 or amd64?
I have two computers I'm considering going amd64 on: Another thing to keep in mind is that there are some OpenBSD packages and ports that only run on i386. In particular, any software that requires Linux emulation (such as the opera-flashplugin) will not run on amd64. Doing a quick grep of the OpenBSD 4.2 ports tree, I've come up the following list of packages and ports that run on i386 but not amd64. /usr/ports/archivers/rar/Makefile:ONLY_FOR_ARCHS= i386 sparc /usr/ports/audio/gogo/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/audio/rio500/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/audio/wmtune/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/chinese/rxvt-big5/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/chinese/xcin25/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/ald/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/jad/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/jdk/1.3/Makefile:ONLY_FOR_ARCHS= arm i386 powerpc sparc /usr/ports/devel/jdk/1.3-linux/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/jdk/1.4/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/nasm/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/prc-tools/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/devel/py-psyco/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/freebsd_lib/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/ines/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/mastergear/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/emulators/redhat/Makefile.inc:ONLY_FOR_ARCHS=i386 /usr/ports/emulators/snes9x/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/emulators/vgb/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/vmware/3/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/wine/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/zsnes/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/emulators/fedora/Makefile.inc:ONLY_FOR_ARCHS=i386 /usr/ports/games/adom/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/games/quake2/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/graphics/cqcam/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/graphics/win32-codecs/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/lang/clisp/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/lang/ezm3/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/lang/gcc/3.3/Makefile:ONLY_FOR_ARCHS=alpha i386 m68k sparc sparc64 powerpc vax /usr/ports/lang/gcc/3.4/Makefile:ONLY_FOR_ARCHS=alpha i386 m68k sparc sparc64 powerpc vax /usr/ports/lang/gcc/4.0/Makefile:ONLY_FOR_ARCHS=alpha i386 m68k sparc sparc64 powerpc vax /usr/ports/lang/gcc/4.1/Makefile:ONLY_FOR_ARCHS=alpha i386 m68k sparc sparc64 powerpc vax /usr/ports/lang/gprolog/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/lang/pm3/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/lang/smlnj/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/lang/tendra/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/lang/jamvm/Makefile:ONLY_FOR_ARCHS= i386 powerpc arm /usr/ports/lang/scheme48/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/math/maple/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/math/maple-share/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/math/wingz/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/misc/dnetc/Makefile:ONLY_FOR_ARCHS= i386 m68k sparc /usr/ports/misc/tpwireless/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/net/cvsup/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/net/dss/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/net/libst/Makefile:ONLY_FOR_ARCHS= alpha i386 sparc /usr/ports/net/openafs/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/net/pdnsd/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/net/ser/Makefile:ONLY_FOR_ARCHS= i386 sparc /usr/ports/palm/isilo/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/palm/pose/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/print/acroread/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/security/l0phtcrack/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/sysutils/libretto-config/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/sysutils/perfd/Makefile:ONLY_FOR_ARCHS= i386 macppc sparc zaurus /usr/ports/sysutils/tphdisk/Makefile:ONLY_FOR_ARCHS=i386 /usr/ports/sysutils/wdsetup/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/sysutils/wmapm/Makefile:ONLY_FOR_ARCHS= arm i386 macppc /usr/ports/sysutils/xbatt/Makefile:ONLY_FOR_ARCHS= arm i386 macppc sparc /usr/ports/sysutils/grub/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/www/mod_frontpage/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/www/opera/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/www/opera-flashplugin/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/x11/asapm/Makefile:ONLY_FOR_ARCHS= arm i386 macppc /usr/ports/x11/gatos-bin/Makefile:ONLY_FOR_ARCHS= i386 /usr/ports/x11/xfce4/xfce4-battery/Makefile:ONLY_FOR_ARCHS= arm i386 powerpc sparc /usr/ports/x11/gnustep/gnustep.port.mk:ONLY_FOR_ARCHS= i386
