On Wednesday 10 August 2005 10:35 am, Gil Weber wrote: <snip>
To me, that indicates that SaX2 is grabbing configuration data that it *thinks* is appropriate but isn't, so when it goes out to initialize the hardware it can't communicate with it and aborts.
But it happens even when I do an absolutely clean install.
I've seen bad data in the components database before, so it wouldn't surprise me. This is definitely worth checking into. Also, when you do a 'clean' install, have you tried booting into rescue mode and recursively deleting all the files and directories in the target partition(s) first? I just recently had a problem with the system acting like it was picking up old data and corrupting /my/ freshly installed 9.3... as though the rather fast format performed during installation wasn't enough. (This is just a working hypothesis and could be specific to my hardware, so don't hold me to it.) - Carl