Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Upgraded my SuSE 7.0 to Linux 2.4.0
Message
Information générale
Forum:
Linux
Catégorie:
Distribution (called 'distros') specific issues
Divers
Thread ID:
00461164
Message ID:
00463174
Vues:
16
>It also required an upgrade of modutils to modutils-2.4 first.
>
>I compiled using gcc 2.95.2 with no problems in compiling. However, my OSS sound driver required an update to the "Linux-2.4 (UP)" version. I installed it but it failed with a seg fault. 4Front is working on a fix that should be out in a week or two.
>
>Other than that Linux 2.4 is neat! Fast! Combine with ReiserFS my box boots faster than it ever has. Somewhere around 15-20 seconds to a login prompt. ReiserFS is now a part of my kernel, along with my NCR53c810 driver and my Boomerang NIC driver. Everything else is a module or not installed.
>
>The guys did a good job!

AN UPDATE:
Sadly, I could not get the SuSE Linux 2.4.0 kernel work properly with the
OSS Linux 2.4 (UP) driver. 4Front is working with the SuSE kernel for a fix but SuSE is generating new kernels faster than popcorn. I began on the 5th with the -6.tgz and gave up the day before yesterday, the 10th trying to get sound in the -18.tgz SuSE kernel.

Also, in the -18.tgz, I had tried to remove a lot of stock modules for services and hardware that I never use or don't have. All compiles were clean with the exception of one, but NONE would boot. So, I went back to the initial .config and got a clean compile and a good boot.

BUT!!!!! --- Disaster struck. I usually leave my box on 24/7. After getting a clean compile and boot on the 9th, I left my box on with KDE2 up and running and went to bed. In the morning I began my daily download of suse-email and Kmail appeared hung trying to connect. Checking ifconfig, I could see that the NIC and local host appeared to be running fine and were not reporting errors.

Then I discovered that any app that opens any file cannot close it, resulting in that file being zeroed out (zero length). I couldn't recompile the kernel because make menuconfig wasn't able to save the .config file!

I rebooted to my 2.2.16 kernel and striped 2.4.0 off my box. Then I reinstalled my 2.2.x OSS drivers and all is well in the garden again!

It may be just me and my stupidity, but I don't think the SuSe 2.4.0 was/is ready for prime time.

I guess I wait till they release SuSE 7.1. I'm happy with SuSE but I've been reading about Debian lately.... choice is a wonderful thing! 8-)
Nebraska Dept of Revenue
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform