Hi All: I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to SuSE 6.3.- All upgrade went OK, but when I had to reboot I received the following message:
#VFS: Cannot open root device 08:01 #Kernel Panic: VFS: Unable to mount root fs on 08:01
I made all my 'homework'and these are the results: -lilo.conf of the old install and the new one I obtain from Yast differe only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img NEW: line is missing and if I add it by hand, when I run Yast it deletes this line.- -I changed kernels but, if I select the i386 (recomended for 486) I have the above message and if I select the SCSI-Kernel with modules it complains that it's not a Pentium.- I suppose that the problem is in some place of lilo, Yast or the Kernell I select but cannot figure it out.- Can somebody point me in the right way??? Thanks in advance for all your help.- Best Regards Carlos Aguero -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Carlos Alejandro Aguero wrote:
Hi All: I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to SuSE
In this case the term upgrade is not clear. Do you mean that you have installed on top of the old RedHat or you wiped the drive and started over with SuSE?
only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img I could be wrong but is seems that you tried to install SuSE on top of the old RedHat? As far as I know, this will never work, at least not without a lot of work.
above message and if I select the SCSI-Kernel with modules it complains that This is strange/interesting. When I installed my SuSE 6.3 I didn't even see the SCSI choice.
Can somebody point me in the right way??? If you are trying to install SuSE on top of the RedHat installation, give up. If this is wrong and someone else in this group corrects me, then I will have learned something.
I notice your address is .ar which is Argentina? Mind if I ask an off topic question? What sort of high speed internet technology is available for home users in Argentina? Do you have ISDN, DSL or cable modems? Damon Register -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Carlos Alejandro Aguero wrote:
Hi All: I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to
SuSE In this case the term upgrade is not clear. Do you mean that you have installed on top of the old RedHat or you wiped the drive and started over with SuSE?
only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img I could be wrong but is seems that you tried to install SuSE on top of the old RedHat? As far as I know, this will never work, at least not without a lot of work.
above message and if I select the SCSI-Kernel with modules it complains
Damon:
Thanks for your comments and YES y installed on top of RedHat without
cleaning the disk up.-
For this moment, in Argentina we don't have high speed technology for home
users.-
Best Regards
Carlos
----- Mensaje original -----
De: "Damon Register"
This is strange/interesting. When I installed my SuSE 6.3 I didn't even see the SCSI choice.
Can somebody point me in the right way??? If you are trying to install SuSE on top of the RedHat installation, give up. If this is wrong and someone else in this group corrects me, then I will have learned something.
I notice your address is .ar which is Argentina? Mind if I ask an off topic question? What sort of high speed internet technology is available for home users in Argentina? Do you have ISDN, DSL or cable modems?
Damon Register
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
You can't upgrade RHL to SuSE. The underlying technology is just too different. The line in LILO which you are confused over is the one which loads your ramdisk at boot time, and that's what carries the SCSI driver. SuSE is so confused it is not including it. No ramdisk means no SCSI, no SCSI means it can't see your root partition. So it stops dead. It would be a major piece of work to sort out all the problems you've introduced. Much easier to just copy the important files you want somewhere safe (XF86Config, etc) then wipe the disk and start from scratch with SuSE.
I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to SuSE 6.3.- All upgrade went OK, but when I had to reboot I received the following message:
#VFS: Cannot open root device 08:01 #Kernel Panic: VFS: Unable to mount root fs on 08:01
I made all my 'homework'and these are the results:
-lilo.conf of the old install and the new one I obtain from Yast differe only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img NEW: line is missing and if I add it by hand, when I run Yast it deletes this line.-
-I changed kernels but, if I select the i386 (recomended for 486) I have the above message and if I select the SCSI-Kernel with modules it complains that it's not a Pentium.-
I suppose that the problem is in some place of lilo, Yast or the Kernell I select but cannot figure it out.-
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Derek Fountain wrote:
You can't upgrade RHL to SuSE. The underlying technology is just too different. The line in LILO which you are confused over is the one which loads your ramdisk at boot time, and that's what carries the SCSI driver. SuSE is so confused it is not including it. No ramdisk means no SCSI, no SCSI means it can't see your root partition. So it stops dead.
It would be a major piece of work to sort out all the problems you've introduced. Much easier to just copy the important files you want somewhere safe (XF86Config, etc) then wipe the disk and start from scratch with SuSE.
I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to SuSE 6.3.- All upgrade went OK, but when I had to reboot I received the following message:
#VFS: Cannot open root device 08:01 #Kernel Panic: VFS: Unable to mount root fs on 08:01
I made all my 'homework'and these are the results:
-lilo.conf of the old install and the new one I obtain from Yast differe only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img NEW: line is missing and if I add it by hand, when I run Yast it deletes this line.-
-I changed kernels but, if I select the i386 (recomended for 486) I have the above message and if I select the SCSI-Kernel with modules it complains that it's not a Pentium.-
I suppose that the problem is in some place of lilo, Yast or the Kernell I select but cannot figure it out.-
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Well, yeah, that would work... But I can definitely understand not wanting to give up all the configuration you've done (winodow stuff, etc...) I'm sure there's a way to prevent Yast from modifying it... Isn't there a switch in Yast to tell it not to modify your config files? I haven't touched Yast since a few days after I installed... Give me a bit and I'll look. -- --Richard D. Slaughter Richie @ R & W Trucking -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Richard:
Exactly that is the way I would like to go, reconfiguring to be able to
maintain my previous settings.-
I'll give Disabling Yast a try and will come back.-
Best Regards
Carlos
----- Mensaje original -----
De: "Richard Slaughter"
Well, yeah, that would work... But I can definitely understand not wanting to give up all the configuration you've done (winodow stuff, etc...) I'm sure there's a way to prevent Yast from modifying it... Isn't there a switch in Yast to tell it not to modify your config files? I haven't touched Yast since a few days after I installed... Give me a bit and I'll look. -- --Richard D. Slaughter Richie @ R & W Trucking
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
You can't upgrade RHL to SuSE. The underlying technology is just too different. The line in LILO which you are confused over is the one which loads your ramdisk at boot time, and that's what carries the SCSI driver. SuSE is so confused it is not including it. No ramdisk means no SCSI, no SCSI means it can't see your root partition. So it stops dead.
It would be a major piece of work to sort out all the problems you've introduced. Much easier to just copy the important files you want somewhere safe (XF86Config, etc) then wipe the disk and start from scratch with SuSE.
I'm having a bad time with a 486PC that has a SCSI-Adaptec 154x.- It had a RedHat 6.0 Linux working fine, when I decided to upgrade to SuSE 6.3.- All upgrade went OK, but when I had to reboot I received the following message:
#VFS: Cannot open root device 08:01 #Kernel Panic: VFS: Unable to mount root fs on 08:01
I made all my 'homework'and these are the results:
-lilo.conf of the old install and the new one I obtain from Yast differe only in the following line: OLD: initrd=/boot/initrd-2.2.5-15.img NEW: line is missing and if I add it by hand, when I run Yast it deletes this line.-
-I changed kernels but, if I select the i386 (recomended for 486) I have
above message and if I select the SCSI-Kernel with modules it complains
Derek:
Thank you very much for your comments.-
Best Regards
Carlos
----- Mensaje original -----
De: "Derek Fountain"
it's not a Pentium.-
I suppose that the problem is in some place of lilo, Yast or the Kernell I select but cannot figure it out.-
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
caa＠onenet.com.ar -
damon.w.register＠lmco.com -
defiance＠cei.net -
fountai＠nomail.hursley.ibm.com