> > judging from past email, i'm guessing that your ide device > > is 27c4, which was missing from 9load. i put up a corrected cd. > > if you can ftpfs from your mostly-installed machine and > > get just 9load.bz2, it's in the same directory. > > > > ; i=9atom.iso.bz2 sha1sum $i && ls -l $i > > cb7bdb9bcaebaf5e54d5a76c672dba52f90eb55a 9atom.iso.bz2 > > --rw-r--r-- M 176 quanstro quanstro 88211681 Aug 11 17:13 9atom.iso.bz2 > > > thanks erik!!! I can now boot. I am now at the > init starting /bin/rc stage it seems to stall there. I think its > just the ip/ipconfig issue should be easy to fix.
> just a note. i am getting > ide: caught missed irq several times shoul i be concerned? what's going on: i replaced the sleep in sdata.c with a loop that checks for i/o completion every second. i/o should never be outstanding for 1 second, so this will never fire unless your disk is very sick, or you're missing interrupts. after 10 missed irqs, it has mercy on you and checks every 50ms. this will seem very slow. the pureists are probablly going to choke at this trick. i don't blame them. but on the other hand, i want to give folks a chance to recover their systems if ide acts up. this is something to be concerned about. once you boot up, there are a number of things to try. /dev/irqalloc for your kernel should have an extra final entry that counts the number of interrupts on each vector. i would expect that number would be 0, given your symptoms. here are a few things you can look at - is your southbridge recognized? - you might want to try turning dma on, on the wild theory that it worked well enough during installation. - you might want to try turning mp interrupts on. unfortunately, i forgot to add the nomp device which allow one to inspect the mp interrupts before trying them. failing any of those things, send me your pci output. this setup should work. - erik