Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4554 - CONFIG_HIGHMEM mis-configuration
|
DetailsI suspect CONFIG_HIGHMEM4G=y and CONFIG_HIGHMEM64G=y are exclusive, and the first one found is used. I've not confirmed this, however, they are both set to y in the current kernel config file and zcat /proc/config.gz | grep reports that 64G is NOT ENABLED. I've built a kernel now with a single edit to the current config "#CONFIG_HIGHMEM4G=y", leaving CONFIG_HIGHMEM64G=y, and I now have my full 4GB back.
Thank you. |
This task depends upon
Comment by Tobias Powalowski (tpowa) -
Wednesday, 03 May 2006, 07:21 GMT
ups ok jsut missed this for .13 kernel, but i guess kernel .14 is coming soon.