Hi, Does anyone have a recipe for booting the 2.4.17 kernel(or any vanilla kernel) in SuSE 7.3, and successfully loading ext3 as the root file system? I suppose you can't use the mk_initrd script then? When I try to load the 2.4.17 from Lilo at bootup I just get a black screen. In Grub I get "VFS: Kernel Panic Unable to mount root fs". Regards, Jostein
El Tue, 15-01-2002 a las 11:01, Jostein Berntsen escribi?: Hi, Does anyone have a recipe for booting the 2.4.17 kernel(or any vanilla kernel) in SuSE 7.3, and successfully loading ext3 as the root file system? I suppose you can't use the mk_initrd script then? When I try to load the 2.4.17 from Lilo at bootup I just get a black screen. In Grub I get "VFS: Kernel Panic Unable to mount root fs". Regards, Jostein Besides a possilbe misconfiguration of kernel sources, probably you are missing quantity of Initial RAM Disk (initrd) at kernel config at Block devices/RAM disk support/Default RAM Disk size ---->>> put 64000. And as "root fs", I think ext3 is still a bit unstable; try using Reiserfs if you want to use a real Journalling file system. Regards, Alejandro. -- 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/faq and the archives at http://lists.suse.com ALEJANDRO ORTEGA PÁEZ - Adm. Sistemas - aortega@nostracom.com
Alejandro Ortega Páez wrote:
El Tue, 15-01-2002 a las 11:01, Jostein Berntsen escribi?:
Hi,
Does anyone have a recipe for booting the 2.4.17 kernel(or any vanilla kernel) in SuSE 7.3, and successfully loading ext3 as the root file system? I suppose you can't use the mk_initrd script then?
When I try to load the 2.4.17 from Lilo at bootup I just get a black screen. In Grub I get "VFS: Kernel Panic Unable to mount root fs".
This has been asked before. There is a bug in the suse mk_initrd that prevents it front booting to ext3. There is a fix: http://sdb.suse.de/en/sdb/html/ext3_rootfs_73.html -- $|=1;while(1){print pack("h*",'75861647f302d4560275f6272797f3');sleep(1); for(1..16){for(8,32,8,7){print chr($_);}select(undef,undef,undef,.05);}}
zentara wrote:
This has been asked before. There is a bug in the suse mk_initrd that prevents it front booting to ext3.
There is a fix: http://sdb.suse.de/en/sdb/html/ext3_rootfs_73.html
I knew I had seen something on this on the list, but couldn't remember the URL. Now I have a question. My / is ext3, which I setup when I installed. I knew there was some problem with mk_initrd, but couldn't find the new one. I have used YOU, which updated the package aaa_base, where rpm -qf /sbin/mk_initrd told me it was from. I just downloaded the one from the ftp site above, and diff shows there are differences between these scripts. My confusion arises since I have since upgraded the kernel (and switched back and forth to fix some glitches), and of course run mk_initrd several times (but I believe I had already updated aaa_base before running it the first time), and it worked like a champ. So is it a case of "don't fix what ain't broke", the aaa_base-2001.10.19-1 already fixed it (then why the differences), or the one above is an older 'fix'. I am curious as to whether I should replace my mk_initrd script, especially since I have an ext3 /. TIA for any help. :-) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871
Joe & Sesil Morris (NTM) wrote:
zentara wrote:
This has been asked before. There is a bug in the suse mk_initrd that prevents it front booting to ext3.
There is a fix: http://sdb.suse.de/en/sdb/html/ext3_rootfs_73.html
I knew I had seen something on this on the list, but couldn't remember the URL.
Ha! BAD excuse ;-) Go to the much publicized SuSE support database (sdb.suse.de) and search for the keyword... no need to remember any URLs, the SDB is accessible from our homepage(s), printed many times in the documentation, and is also in several places in the online help system. Michael
Michael Hasenstein wrote:
Joe & Sesil Morris (NTM) wrote:
I knew I had seen something on this on the list, but couldn't remember the URL.
Ha! BAD excuse ;-) Go to the much publicized SuSE support database (sdb.suse.de) and search for the keyword... no need to remember any URLs, the SDB is accessible from our homepage(s), printed many times in the documentation, and is also in several places in the online help system.
Agreed, bad excuse ;-) . Problem was I was in the middle of installing, updating, tweaking, and general "having fun..." :-) . Problem is, that doesn't answer my question. Why is the mk_initrd in ftp://ftp.suse.com/pub/people/snwint/initrd/mk_initrd different than the mk_initrd in the aaa_base update for 7.3 (installed by YOU)? My / is ext3, and the one in the aaa_base update worked fine when I updated to 2.4.16, but is the one in snwint/initrd newer or better? Diff says they are different. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871
Joe & Sesil Morris (NTM) wrote:
Agreed, bad excuse ;-) . Problem was I was in the middle of installing, updating, tweaking, and general "having fun..." :-) . Problem is, that doesn't answer my question. Why is the mk_initrd in ftp://ftp.suse.com/pub/people/snwint/initrd/mk_initrd different than the mk_initrd in the aaa_base update for 7.3 (installed by YOU)? My / is
Because one is an official update the company "SuSE" provides and the other location is the *PRIVATE* ftp directory of some SuSE employee (which just happens to be on the same server, but it's makred "people", right)?
ext3, and the one in the aaa_base update worked fine when I updated to 2.4.16, but is the one in snwint/initrd newer or better? Diff says they are different.
Well, look at the diff and see if this is worse or better than the original, and if you cannot read shell scripts and diffs well enough (which is of course okay, just trying to help you establish what to do about it) you should leave all .../people/... ftp directories alone because this is where our developers communicate with "the community", and they generally don't even try to accomodate the general public for their coding snapshots. They typically use this area to let other (non SuSE but also off-site SuSE people) access some special hack for testing. By the way, just look at the timestamp, which one is newer... not sufficient, but a good starting point to establish if it's even worth looking at something. Michael
Joe & Sesil Morris (NTM) wrote:
zentara wrote:
This has been asked before. There is a bug in the suse mk_initrd that prevents it front booting to ext3.
There is a fix: http://sdb.suse.de/en/sdb/html/ext3_rootfs_73.html
I knew I had seen something on this on the list, but couldn't remember the URL. Now I have a question. My / is ext3, which I setup when I installed. I knew there was some problem with mk_initrd, but couldn't find the new one. I have used YOU, which updated the package aaa_base, where rpm -qf /sbin/mk_initrd told me it was from. I just downloaded the one from the ftp site above, and diff shows there are differences between these scripts. My confusion arises since I have since upgraded the kernel (and switched back and forth to fix some glitches), and of course run mk_initrd several times (but I believe I had already updated aaa_base before running it the first time), and it worked like a champ. So is it a case of "don't fix what ain't broke", the aaa_base-2001.10.19-1 already fixed it (then why the differences), or the one above is an older 'fix'. I am curious as to whether I should replace my mk_initrd script, especially since I have an ext3 /. TIA for any help. :-)
I've never used YOU, so I can't help there. But just make a backup of the mk_initrd that you have now, then copy the patched one in it's place. If there is a problem, restore the old one. It will only affect you if you roll your own kernel, and need to do a mk_initrd. Others have used this to boot ext3, and none have complained about it. It is just a slightly patched mk_initrd. -- $|=1;while(1){print pack("h*",'75861647f302d4560275f6272797f3');sleep(1); for(1..16){for(8,32,8,7){print chr($_);}select(undef,undef,undef,.05);}}
participants (5)
-
Alejandro Ortega Páez -
Joe & Sesil Morris (NTM) -
Jostein Berntsen -
Michael Hasenstein -
zentara