On Saturday 23 June 2007 10:52, Duncan wrote: > Let me know how this goes [...] as I'd like to follow it too.
Well, after quite a bit more work, I'm still none the wiser. I've built a new installation from scratch without the ~amd64 key word, and I've tried many combinations of kernel parameters. Once or twice I thought I'd found it: for instance, it seemed that removing I2C completely caused the faulty behaviour to appear, but then putting it back in didn't correct it. The new system is as independent of the original as possible. The old one was on /dev/hd[a,b] and the new is on /dev/sda, which is a SATA disk. I've changed the BIOS to boot from SATA first, though I couldn't hide the old disks completely - the IDE optical disks /dev/hd[c,d] were then hidden as well. I started with a genkernel kernel, remembering to enable SATA in it first ;-) , then switched to compiling manually, progressively stripping out all the extraneous modules and inbuilt features until I had a reasonably well tuned kernel. it works just fine. I also reverted the BIOS to an optimised set of defaults and changed one thing at a time to reach (what I think is) the optimum for me. The system is working as it should. Soon I'll erase the old partitions - when I'm sure I don't need anything else off them. So I can't put a case together to raise a bug report, and I'll have to accept just-one-of-those-things. -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list
