can suse 9.3 be forced to use kernel from 9.0, 2.4.21-99-default?
Hello all I think i need help from people that understand more then i how suse has designed the boot system I have a promise card, sx4000, for ide raid Please, no need to discuss about the merits or demerits of the card, or even the company , because that will not solve the actual problem (the mistake is already made ) The thing is that the card works well under suse 9.0 using default kernel from install cds (2.4.21-99-default), using one module that is available from promise site I have been trying to use suse 9.3 and that same kernel but without success. To perform the testing process i have been using vmware machines, even without the proper fasttrak module, because the problems arise before that becomes an issue. If i install suse 9.3, clone the proper line in grub or lilo, reboot to test, and then try to install the rpm of the default kernel from suse 9.0 The package installs clean, the lilo or grub gets modified, but the system will not boot the kernel 2.4.x, resulting in kernel panic , like unable to mount root in dev:08:02 or similar. Is the system unable to locate the proper initrd, althought it is there and the boot configuration is good ???? why ??? If i install suse 9.0 and then try to upgrade to suse 9.3, keeping the proper line under llilo or grup, the system will not boot with the old kernel, even if the vmlinuz-2.4.21-99-default, and the equivalent initrd-2.4.21-99-default are there, the proper /lib/modules/......... files are there, and the grup line is there, like it should ..... Why is so dificult to use a kernel 2.4.x on suse 9.3 ?? is it impossible ????? I keep a copy of /etc under /etc.copia/ and /boot under /boot.copia/, from suse 9.0 I even generated modprobe.conf from the old modules.conf, using some information that read from http://portal.suse.com/sdb/en/2004/02/migrating_to_26.html , before the upgrade Still the old 2.4.x kernel will not boot Do i have to force the upgrade to keep some packages from the suse 9.0 version ?? (besides the kernel , of course ) Can anybody point me out ?? Many many thanks Yours truly André
On Tuesday 30 August 2005 00:28, Andre Ramos wrote:
The package installs clean, the lilo or grub gets modified, but the system will not boot the kernel 2.4.x, resulting in kernel panic , like unable to mount root in dev:08:02 or similar.
This is a little like saying Hamlet's soliloquy was: "Should I kill myself" or similar. Without the exact error messages given out it is impossible to say what goes wrong. In brief, the system should definitely be able to boot, assuming the 2.4 kernel series had support for your hardware, but there are a number of programs that have been modified in order to work with the ideas of the 2.6 series, like the move from /proc to /sys, dbus/hal and other changes. So while the system should boot up, it probably won't work very well from that point on
Do i have to force the upgrade to keep some packages from the suse 9.0 version ?? (besides the kernel , of course )
I suspect you need to keep 9.0 on there
First of all thank you all for your attention. I know that the information i provided is scarce, however the problem is easy to replicate, and i thought that more people had already seen it before. The reason that caused the problem is hardware, the promise ide raid sx4000, for wich i only had a precompiled module for kernel 2.4.21-286-default, the original kernel from suse 9.0. However lots of things improve with new versions of suse, therefor the interest in migrating to suse 9.3. But the kernel needs to be kept back. What i was "complaining" about was : 1. install suse 9.0 on standard vmware machine, on standard vmware scsi disk (forget the raid for the testing phase) 2. boot standard kernel, with no problems what so ever 3. boot suse 9.3 install cd and upgrade, keeping the old kernel, and adding also the new one 4. reboot 5. the system boots ok with new 9.3 kernel 6. the system will not boot the old kernel, even if the proper vmlinuz, initrd and /lib/modules/2.4... are in place and lilo.conf is correct. WHY ?? What has been done the makes it so dificult (impossible for my level of knowledge) to boot suse 9.3 with an older kernel.....? I supose many other people have hardware problems that force the to keep older kernels. Can they migrate to suse 9.3 ?? Or not ? But................ in my case, help came, that provided me with a module for my hardware. It came from Mr Per Krogh Nielsen . He also posted recently about it on this list, under the subject "Re: fastrak module for suse 9.3 kernel" He sent me his module for the kernel that installs by default under suse 9.3, and IT WORKS ! Therefor i now use suse 9.3 with the most recent kernel from updates, using a kernel module for promise FastTrak SX4000 compiled following the help from Per Krogh Nielsen , and the problem is gone. I will of course provide that module to those that may need it. The problem maybe gone, but ....still it was not solved out to use a older kernel on suse 9.3. Many thanks to you all, once more. Community thinking realy helps! Yours André -----Mensagem original----- De: Sandy Drobic [mailto:suse-linux-e@japantest.homelinux.com] Enviada: segunda-feira, 29 de Agosto de 2005 23:45 Para: suse-linux-e@suse.com Assunto: Re: [SLE] can suse 9.3 be forced to use kernel from 9.0, 2.4.21-99-default? Andre Ramos wrote:
Hello all
I think i need help from people that understand more then i how suse has designed the boot system
I have a promise card, sx4000, for ide raid
Please, no need to discuss about the merits or demerits of the card, or even the company , because that will not solve the actual problem (the mistake is already made )
The thing is that the card works well under suse 9.0 using default kernel from install cds (2.4.21-99-default), using one module that is available from promise site
So, what problem are you trying to solve? You are talking at length what you are doing but you don't tell anything about the problem that decided you to upgrade. For what it's worth, I think you are trying to solve the wrong problem. Instead of trying to make Suse 9.3 accept the old kernel, which does not provide the libraries that many programs of that version expect, try to install recent versions of the programs you want to use, that are compiled for Suse 9.0. Sandy -- -----Mensagem original----- De: Anders Johansson [mailto:andjoh@rydsbo.net] Enviada: segunda-feira, 29 de Agosto de 2005 23:44 Para: suse-linux-e@suse.com Assunto: Re: [SLE] can suse 9.3 be forced to use kernel from 9.0, 2.4.21-99-default? On Tuesday 30 August 2005 00:28, Andre Ramos wrote:
The package installs clean, the lilo or grub gets modified, but the system will not boot the kernel 2.4.x, resulting in kernel panic , like unable to mount root in dev:08:02 or similar.
This is a little like saying Hamlet's soliloquy was: "Should I kill myself" or similar. Without the exact error messages given out it is impossible to say what goes wrong. In brief, the system should definitely be able to boot, assuming the 2.4 kernel series had support for your hardware, but there are a number of programs that have been modified in order to work with the ideas of the 2.6 series, like the move from /proc to /sys, dbus/hal and other changes. So while the system should boot up, it probably won't work very well from that point on
Do i have to force the upgrade to keep some packages from the suse 9.0 version ?? (besides the kernel , of course )
I suspect you need to keep 9.0 on there -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 08 September 2005 23:10, Andre Ramos wrote:
WHY ?? What has been done the makes it so dificult (impossible for my level of knowledge) to boot suse 9.3 with an older kernel.....?
The difference between the 2.4 and the 2.6 kernel is too great. They also introduced an enormous amount of changes in hotplugging and other hardware related activities that are kernel bound. It's simply a case that too much happened to retain compatibility. The big mistake here IMNSHO was in calling 9.0 9.0. It should have been 8.3, because it doesn't have a whole lot in common with the other 9.x releases. The differences in some cases are quite drastic. But I'm glad you got your problem solved through other means
Andre Ramos wrote:
Hello all
I think i need help from people that understand more then i how suse has designed the boot system
I have a promise card, sx4000, for ide raid
Please, no need to discuss about the merits or demerits of the card, or even the company , because that will not solve the actual problem (the mistake is already made )
The thing is that the card works well under suse 9.0 using default kernel from install cd’s (2.4.21-99-default), using one module that is available from promise site
So, what problem are you trying to solve? You are talking at length what you are doing but you don't tell anything about the problem that decided you to upgrade. For what it's worth, I think you are trying to solve the wrong problem. Instead of trying to make Suse 9.3 accept the old kernel, which does not provide the libraries that many programs of that version expect, try to install recent versions of the programs you want to use, that are compiled for Suse 9.0. Sandy
participants (3)
-
Anders Johansson -
Andre Ramos -
Sandy Drobic