Wow... I'm starting to get a little frustrated with the whole state of 64-bit computing. I'm not sure if the problem lies in the Linux kernel or ATI's drivers, but I'm guessing the latter. Of course, it could be that I've commented out that Save64BitBar code that was causing the driver to fail to load at all.
Has anyone managed to get a 64-bit Linux machine working with 4GB of RAM?
If I try to boot with >3.6GB enabled (mem=3600M, maxmem=3600M - not sure which of these options is used), I get a hard lockup when starting the X server now. My machine reports about 3.6GB in 32-bit as well.
I saw a similar problem with my SATA controller (it would advertise 64-bit DMA but could only handle 32-bit). I imagine that this could be a similar problem, but as ATI's drivers are just blobs I'm somewhat constrained in how much I can fiddle here.
I'm excited for the day when device manufacturers have access to 64-bit + >4GB machines! At least I can say that my experience under Linux was a little less painful than my brief Windows 64-bit experiments.
Has anyone managed to get a 64-bit Linux machine working with 4GB of RAM?
If I try to boot with >3.6GB enabled (mem=3600M, maxmem=3600M - not sure which of these options is used), I get a hard lockup when starting the X server now. My machine reports about 3.6GB in 32-bit as well.
I saw a similar problem with my SATA controller (it would advertise 64-bit DMA but could only handle 32-bit). I imagine that this could be a similar problem, but as ATI's drivers are just blobs I'm somewhat constrained in how much I can fiddle here.
I'm excited for the day when device manufacturers have access to 64-bit + >4GB machines! At least I can say that my experience under Linux was a little less painful than my brief Windows 64-bit experiments.
Comment