On Feb 19, 2008 5:10 PM, Kevin K <kkutzko@teksavvy.com> wrote:> I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb.Siding with most of the group (go amd64), I'll add my own comment: Using PAE to access 4G of RAM (because 4G shows up as 2.5 to 3.5 gig, depending on the motherboard) under i386 is a reasonable solution, IMHO. Maybe even 6 gig or 8 gig... if you're trying to extend the life of an ia32 server. But with amd64 supporting ia32 binaries well, it seems the only reason left might be drivers --- except ... are there _any_ drivers that support PAE and _not_ amd64? I'm using amd64 on my laptop (which has 4gig) because the only driver I care about (the nvidia binary driver) doesn't work under either PAE or amd64 (and ... it also doesn't support 8xxx series mobile chipsets ... so I'm screwed anyways) . I'd be curious to know if anyone's still hedging their bets by making their machine dual-boot i386/amd64 --- and how they configure it. Have you thought about sharing /usr or parts of it? Installed ports can seemingly mess things up.
On Wed, Feb 20, 2008 at 01:41:30PM -0500, Zaphod Beeblebrox wrote:>I'd be curious to know if anyone's still hedging their bets by making their >machine dual-boot i386/amd64 --- and how they configure it. Have you >thought about sharing /usr or parts of it? Installed ports can seemingly >mess things up.I dual-boot my laptop (actually triple-boot if you include 7.x) and have all 3 filesystem trees visible. I have my 6.x/amd64 paths setup to see the 6.x/i386 executables. Mostly it works OK but I have run into a couple of problems when building a 6.x/amd64 port and the port build process had found a 6.x/i386 version of a dependency - which causes the port build to fail at some later point. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080221/fd2468cb/attachment.pgp
On Wed, 2008-02-20 at 13:41 -0500, Zaphod Beeblebrox wrote:> On Feb 19, 2008 5:10 PM, Kevin K <kkutzko@teksavvy.com> wrote: > > > I have a box that we recently installed 16GB of RAM on. The box is i386 > > FreeBSD 6.2. It only recognizes 4gb. > > > Siding with most of the group (go amd64), I'll add my own comment: > > Using PAE to access 4G of RAM (because 4G shows up as 2.5 to 3.5 gig, > depending on the motherboard) under i386 is a reasonable solution, IMHO. > Maybe even 6 gig or 8 gig... if you're trying to extend the life of an ia32 > server. > > But with amd64 supporting ia32 binaries well, it seems the only reason left > might be drivers --- except ... are there _any_ drivers that support PAE and > _not_ amd64? >We use this system while we slowly port our 32 bit code to 64 bit. There are some outstanding unresolved issues running 32 bit binaries on 64 bit (or at least, on 6.2-RELEASE-p8). http://www.mail-archive.com/freebsd-stable@freebsd.org/msg94092.html This should be fixed, although I've not tested whether 7.0 (and the change to gcc 4.2.1) might fix this anyway. Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080226/0153bf47/attachment.pgp