On Wed, Aug 23, 2006 at 08:50:15AM -0400, Dykema, Erik wrote: > 1) The AMD64 arch (which would be preferrable in this case as the processor > is emt64 capable) is > not built using the 2.6.17 kernel, so I had to use the i386 arch.
It looks like 2.6.17 udebs are in sid for amd64, but d-i is not yet configured to use them. > 2) Even though the installer runs the .17 kernel, it still installs the .16 > kernel. If you install testing, it will pull the latest kernel from testing which is still 2.6.16 - 2.6.17 is in unstable. Frans/Frederik: can this be switched over now? > Using the build for i386, I was able to install very cleanly, and > reboot, at which point the USB > messages started spewing again. By hitting ctrl-c a few times, I was able to > get to a login > prompt, and can access the machine, although I am typing blind. Now I am > downloading and > compiling a new kernel, which should work. You should be able to use the exiting 2.6.17 build in unstable. > So, at this point, I would say that the i386 arch installer daily-build > is working great, but > the kernel needs that patch from .17 to fix the HP problem. This will affect > many present, and > all future, models of HP servers; any which use the iLO 2 chip: including all > of their new Blade > servers. The plan is to either ship etch with 2.6.17 or 2.6.18 so this won't be a problem. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
