Difference between revisions of "Bering-uClibc 5.x - User Guide - Appendices - Upgrading from Bering-uClibc 3.x"

From bering-uClibc
Jump to: navigation, search
(UPgrade)
 
 
Line 10: Line 10:
  
 
==General Q&A==
 
==General Q&A==
;What happened to <tt>/dev/hda</tt>? : It is now an emulated SCSI disk, so <tt>/dev/sda</tt> instead.
+
;LEAF Bering-uClibc does not boot with the message:
 +
LINUXRC: Switch_root into newfs...
 +
can't run '/etc/init.d/rcS': No such file or directory
 +
 +
Please press Enter to activate this console.
  
 +
This will be the case, if you upgrade your CF/HD with LEAF Bering-uClibc packages, without updating Syslinux from (previous version) 3.x to syslinux 4.x. LEAF Bering-uClibc 5.x needs support for multiple initrd files (initrd and initmod), which is supported in Syslinux versions 4.0 and above.
 +
 +
<!--
 
==Changes in syslinux.cfg==
 
==Changes in syslinux.cfg==
 
<code class="filename">initrd.lrp</code> has been splitted in a kernel independent part <code class="filename">initrd.lrp</code> and a kernel dependent part, <code class="filename">initmod.lrp</code> with the modules needed in the first part of the boot process.
 
<code class="filename">initrd.lrp</code> has been splitted in a kernel independent part <code class="filename">initrd.lrp</code> and a kernel dependent part, <code class="filename">initmod.lrp</code> with the modules needed in the first part of the boot process.
 
Therefor <code class="filename">initmod.lrp</code> must be added to the initrd option in <code class="filename">syslinux.cfg</code>:
 
Therefor <code class="filename">initmod.lrp</code> must be added to the initrd option in <code class="filename">syslinux.cfg</code>:
  DEFAULT linux initrd=/initrd.lrp,/initmod.lrp
+
  DEFAULT linux initrd=initrd.lrp,initmod.lrp
In some occassions the ''/'' raises and error and you'll have to remove it:
+
In some occassions the missing ''/'' raises an error and you'll have to add it:
  append initrd=initrd.lrp,initmod.lrp
+
  append /initrd=initrd.lrp,/initmod.lrp
 
+
-->
  
 
----
 
----

Latest revision as of 17:44, 3 April 2013

Appendices - Upgrading from Bering-uClibc 4.x
Bering-uClibc 5.x - User Guide Next


General Q&A

LEAF Bering-uClibc does not boot with the message
LINUXRC: Switch_root into newfs...
can't run '/etc/init.d/rcS': No such file or directory

Please press Enter to activate this console.

This will be the case, if you upgrade your CF/HD with LEAF Bering-uClibc packages, without updating Syslinux from (previous version) 3.x to syslinux 4.x. LEAF Bering-uClibc 5.x needs support for multiple initrd files (initrd and initmod), which is supported in Syslinux versions 4.0 and above.



Up Next