| 1 |
You do a straight 32bit install on your amd64. The amd64 is 32bit |
| 2 |
capable. I don't know whether to call your precessor an athlon or maybe |
| 3 |
a generic x86 processor. It is the same as running Windows 2000/XP on |
| 4 |
this processor. The OS thinks it has a 32bit CPU. Only you are limited |
| 5 |
to 32bit limitation on hardware, mainly memory and possibly harddrive, I |
| 6 |
don't know. |
| 7 |
|
| 8 |
Also, have you only tried the ~amd64 kernels? Stick with the non "~" |
| 9 |
software for a stable/production machine unless you absulutely need a |
| 10 |
newer version in that is marked "~". The "~" before the amd64 or x86 or |
| 11 |
any other platform means this version has not been completely tested and |
| 12 |
thus is unstable. Many times, it is stable just needs to be verified. |
| 13 |
Other times, especially when dealing with hardware or assembly |
| 14 |
programming or sloppy programming, it isn't stable. If you are running |
| 15 |
~amd64, I would suggest backing off to the stable amd64 and rebuild with |
| 16 |
that. It will give you slightly older version but more tested |
| 17 |
versions. I am sure others can point in the correct direction for |
| 18 |
rebuild your system if needed, let more experieced wiser minds help |
| 19 |
where they can. |
| 20 |
|
| 21 |
Good Luck and let us know how it goes one way or the other, |
| 22 |
JCS |
| 23 |
|
| 24 |
Mark Knecht wrote: |
| 25 |
|
| 26 |
>Hi, |
| 27 |
> I'm very unclear about this idea. I've built my new AMD64 machine |
| 28 |
>using the Gentoo 64-bit setup. The kernel I emerge uses the ~amd64 to |
| 29 |
>I think I get a full 64-bit kernel. (Please excuse me on this issue. |
| 30 |
>I'm a bit of a "follow instructions, not necessarily understand the |
| 31 |
>whole thing" kind of guy on this one, and I definitely feel like I |
| 32 |
>don't get what's up with 64-bit operation so far...) As far as I know |
| 33 |
>everything on my machine is supposed to run in 64-bit mode, as far as |
| 34 |
>I know. |
| 35 |
> |
| 36 |
> Anyway, this machine is an AMD64 using a NForce4 motherboard. At |
| 37 |
>this point, running a kernel with the processor being an AMD64 |
| 38 |
>processor, I'm unable to run the machine with no xruns using Jack. Any |
| 39 |
>disk activity seems to be the main cause of xruns on this machine. |
| 40 |
>I've tried the AMD64 64-bit Gentoo kernel as well as ck-sources. |
| 41 |
>Neither has worked well at all for me. I continue to get xruns and |
| 42 |
>haven't been able to figure out how to configure the machine to work |
| 43 |
>well. Bummer. |
| 44 |
> |
| 45 |
> Since I've had great results on all of my older 32-bit machines in |
| 46 |
>the past using gentoo-sources with no modifications I'd like to try |
| 47 |
>running that on this machine to see if the xruns are a platform issue, |
| 48 |
>such as the chipset, etc.) or whether they are cuased by operating in |
| 49 |
>64-bit mode. However, I am completely unable to figure out for myself |
| 50 |
>if I can run a 32-bit kernel when everything else - glibc, xrog-x11, |
| 51 |
>qt, gnome, apps, etc., have been compiled as 64-bit capable. Is this |
| 52 |
>allowed, or will the machine not work running a 32-bit kernel at this |
| 53 |
>point? |
| 54 |
> |
| 55 |
> Sorry if this question sounds brain dead but I'm not a CS/IT |
| 56 |
>person. I'm a hardware guy and in my world 64-bit is real different |
| 57 |
>than 32-bit. If I build a kernel for a Athlon will it work with all |
| 58 |
>the existing libraries that work with 64-bit? |
| 59 |
> |
| 60 |
>Thanks in advance, |
| 61 |
>Mark |
| 62 |
> |
| 63 |
> |
| 64 |
> |
| 65 |
|
| 66 |
-- |
| 67 |
gentoo-amd64@g.o mailing list |
Archives