Hi, Tried to install testing (Etch) with debian-testing-i386-netinst.iso dated 13 July 2005, but after the boot: prompt I get the message "Could not find kernel image: /install/2.6/linux". I looked on the CD, and there is a directory /install/2.6 with the files vmlinuz (size 1170484, fits a 2.6 kernel) and initrd.gz in it. Mind you, /install also has a vmlinuz (size 816590, fits a 2.4 kernel) and an initrd.gz. I tried boot: install26, boot: linux26 (that works for the Sarge installer); and repeated all this with boot: expert and expert26 -- everytime the same message.
What does work is boot: install24 -- but I'm not waiting for a 2.4 kernel. Out of curiosity, I also checked the Sarge (stable) debian-31r0a-i386-netinst.iso (which last week gave me an effortless install on an old A22e ThinkPad) -- and something is strange here: the /install directory here has the 2.4-sized vmlinuz, and the /install/2.6 directory the 2.6-sized vmlinuz. Yet, now the 2.4 kernel is the default, located in /install; and you have to boot: linux26 to get the optional kernel, located in /install/2.6/. Now, I wonder, should the 2.6 vmlinuz for the testing installer not be in /install (it being the default kernel), and should not the optional 2.4 vmlinuz be in a directory /install/2.4? Is there a trick with boot: parameters to let the installer find the right 2.6 kernel? Please help me out here, as I'm eager to get going with Etch on my way to Sid. -- H.A.J. Koster "Behavioral axioms are right, but agents make mistakes..." (attributed to L.J. Savage) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]