On Wed, 3 Mar 1999, Paul W. Abrahams wrote in response to Wybo Dekker:
Glad you asked! You're not the only one - I got the same thing when I compiled the 2.2.1 kernel and tried to run it. I certainly hope someone responds to this.
Did you know that you also have to replace referenes to your /dev/cua devices by references to /dev/ttyS devices? (Doing so doesn't affect this problem, though.)
Paul, I gathered from earlier postings that you have the 5.3 distribution. Did you have to upgrade your versions of libc, ppp, binutils, etc as described in the CHANGES document that comes with the kernel? If so, where did you get the upgrades? What particular directories etc. at the SuSE site if you got any there? I recently downloaded a number of upgrades from the 6.0 and 6.0 evaluation directories at the SuSE ftp site and installed them at one fell swoop in preparation for upgrading to 2.2.1. I couldn't boot afterwards so I have since uninstalled them and replaced them with the versions on my 5.1 CD. I'd like to try again, upgrading one utility/set of libraries at a time this time around <g> so if anything breaks isolating and replacing the offending upgrade will be easier. Thanks, Jesse - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>