> Adrian, > Can you test a pre-release of the 2.6.18-3 build to confirm that > this is fixed? 2.6.18-3 seems to be working fine.