Yes, I agree that upgrading the kernel is much to hard and klugie. I tried both 2.4.2 kernels using YaST to get the rpms and also the modutil-2.4.2-14 (that's version x-4 and x-5) and they both hosed my config. finally got 2.4.2-4GB to boot up by copying the rc.config.old to rc.config and everything works, except it won't deal with the nvidia GF2 drivers and kernel mod. I've tried to load the drivers using both the SuSE/YaST method in the FAQ and nVidia's methods (rpm -Uhv NVIDIA_GLX-0.9-769.suse71.i386.rpm --nodeps --force and rpm -Uhv NVIDIA_kernel-0.9-769.suse71.i386.rpm --force, which worked great with the 2.2.18 and 2.4.0-4GB kernels) but it says after issueing the command "switch2nvidia_glx" and then "gears" it says that the '/dev/nvidiaactl' is not present - even though it is. The old 2.4.0-4GB and the 2.4.0-SuSE will boot also but but the nic and sound fails and I get a "kernel can't find map" in the xconsole. I've tried to reinstall the nic and sound setup but both YaST and YaST2 fails saying it can't update the modules. The old kernel/systems are pretty much hosed and I'm not experience enough to know just what files, links, symlinks, etc needs taken care of to get the old kernel and system configs to work properly. And yes I read all the FAQ's kernel docs, manuals, etc. I have never had so much problems, especially seeing the I used SuSE rpms, YaST and followed the instruction to do this. The part I find ironic and unsettling is that according to the SuSE support terms any 2.4.x kernels can't be supported. It makes you wonder, since they were the first to release the 2.4 kernel, that this was more a marketing ploy to boost sales. If I hadn't heard so many horrer stories about RedHat I would have used that distro, but I thought that SuSE would be nice. At this rate I might give RH with the new 2.4 kernel a try, they claim to support it. And, like it or not, almost all new software/packages are made for RH before almost any other distro. I'm gonna go into Winblows to play some UT or CounterStrike so I can shoot things so I can vent my frustrations before I wipe everything off and re-install SuSE yet ONE MORE TIME! On Monday 23 April 2001 12:19 pm, David Benfell wrote:
On Wed, Apr 18, 2001 at 04:56:17PM -0400, Mark Hounschell wrote: Brooklyn Linux Solutions CEO wrote:
Well
It didn't work
The new kernal with the new tools booted, couldn't load any modules and then gave me a login prompt. The prompt authenicated me, and then dumped me back into a login prompt.....why - I have no idea. /var/log/messages said nothing.
Did you install the util-linux? How did you configure it.
The question which pops into my mind is this: Does the util-linux source package install by default into /usr/local? If so, that could be a problem.
The modules thing could be because the 2.4+ kernel Makefile removes all the exsisting modules first. So if you had say alsa installed by doing the make_isntall you wiped out the alsa modules and would have to reinstall them. That holds true for any modules that were there before the make modules_isntall.
Did you upgrade modutils?
Your login problem sounds like you didn't configure the util-linux correctly or didn't install them (not sure).
This is what sucks about suse. Why should upgradiong the kernel be so damn hard.
make dep make bzlilo make modules make modules_install
FINISH
I'm not sure what bzlilo does. But if it replaces the the current kernel image in the lilo configuration, that's bad. It's better to do
make dep bzImage modules modules_install
and edit /etc/lilo.conf by hand, preserving the current images as boot options.
If the kernel says I need new utils-linux .... document on the site how to do this damn upgrade!!
This has nothing to do with SuSE. If you want to upgrade a kernel you should READ the doc in /usr/src/linux/Documentation before you start. Upgrading a kernel is the same no matter where you got it from. The documentation is again in /usr/src/linux/Documentation. See the changes file. It tells you even where to get whats required. Any package you have to upgrade first will have it's own documentation read it too.
Mark's response here is completely correct. When you decide to upgrade packages from source, you're somewhat on your own. This has never stopped me.
One of the really good things about SuSE is that its build environment is NOT broken. So you can build packages from source, usually with a minimum of fuss.
---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="us-ascii"; name="Attachment: 2" Content-Transfer-Encoding: 7bit Content-Description: ----------------------------------------