[Fwd: Possible problem with isofs and CONFIG_NOHIGHMEM]
Posted this to the fsdevel list, but didn't get any bites!
After a search through the FAQ to see if this was a known issue, I thought I should report it!
Just brought my system up to 1G of ram (1.2GHz Athlon, Abit KT7MB, 1GB RAM, Adaptec 29160N, eepro100, SndBlstr Live) and thought I should recompile the kernel to allow for "HIGHMEM" (4GB.) After the compile, I noticed I couldn't mount any CD's. For some reason the ISO9660 driver was getting stomped.
I have ISO9660 compiled as a module, but it seems to be hosed with the HIGHMEM setting in the kernel. Changed HIGHMEM back to "off" and ISO9660 support came back.
Any reason why?
Thanks for your response,
David Christensen
Possible problem with isofs and CONFIG_NOHIGHMEM 2.4.17
Repost, no response from first post!
Quoted 22 lines · David Christensen
Posted this to the fsdevel list, but didn't get any bites!
After a search through the FAQ to see if this was a known issue, I thought I should report it!
Just brought my system up to 1G of ram (1.2GHz Athlon, Abit KT7MB, 1GB RAM, Adaptec 29160N, eepro100, SndBlstr Live) and thought I should recompile the kernel to allow for "HIGHMEM" (4GB.) After the compile, I noticed I couldn't mount any CD's. For some reason the ISO9660 driver was getting stomped.
I have ISO9660 compiled as a module, but it seems to be hosed with the HIGHMEM setting in the kernel. Changed HIGHMEM back to "off" and ISO9660 support came back. Kernel version = 2.4.17 stock.
Any reason why?
Thanks for your response,
David Christensen