[SoaS] Problem with Mirabelle and USB Boot

Marc Karasek marckarasek at gmail.com
Thu Jul 1 17:13:52 EDT 2010


plug the usb stick in.  Open the usb and you will see a folder called 
syslinux.  Inside the folder is the syslinux.cfg file.  You can edit 
this in notepad, it is a text file.



On 7/1/2010 5:11 PM, Anurag Goel wrote:
> I am using the windows version. Still have not been able to fix the 
> problem. How can I modify a .cfg file on windows? Moreover, where do I 
> change root=LABEL=FEDORA and overlay=LABEL=FEDORA?
>
> Thanks,
> Anurag
>
> On Fri, Jul 2, 2010 at 2:33 AM, Marc Karasek <marckarasek at gmail.com 
> <mailto:marckarasek at gmail.com>> wrote:
>
>     Is that the Linux USB creator?  I know the windows version does not.
>
>
>
>
>     On 7/1/2010 5:00 PM, Anurag Goel wrote:
>>     I'm using the Fedora Live USB creator. Doesn't that name the
>>     stick "FEDORA" by default?
>>
>>     -Anurag
>>
>>     On Fri, Jul 2, 2010 at 2:21 AM, Marc Karasek
>>     <marckarasek at gmail.com <mailto:marckarasek at gmail.com>> wrote:
>>
>>         OK,
>>
>>         To prevent it name the sticks Fedora prior to putting the
>>         image on them.  (This step should be added to the online
>>         instructions.)
>>
>>         Now, if you did not change the name and need to modify the
>>         syslinux.cfg, change the following lines: (you will have a
>>         different UUID#)
>>
>>           append initrd=initrd0.img root=live:UUID=3D4E-8E71
>>         rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet  rhgb
>>         rd_NO_LUKS rd_NO_MD
>>
>>           append initrd=initrd0.img root=live:UUID=3D4E-8E71
>>         rootfstype=vfat rw liveimg overlay=UUID=3D4E-8E71 quiet  rhgb
>>         check
>>
>>         to
>>
>>           append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat
>>         rw liveimg overlay=LABEL=FEDORA quiet  rhgb rd_NO_LUKS rd_NO_MD
>>
>>           append initrd=initrd0.img root=LABEL=FEDORA rootfstype=vfat
>>         rw liveimg overlay=LABEL=FEDORA quiet  rhgb check
>>
>>         I tested this fix and it works.
>>
>>         Marc
>>
>>         On 7/1/2010 4:46 PM, Anurag Goel wrote:
>>>         Hi,
>>>
>>>         I'm in the process of making sticks for our pilot in Delhi.
>>>         I'm running into the same problem as described. Can someone
>>>         please elaborate on how to resolve this problem.
>>>         Specifically, how can I modify syslinux.cfg to prevent this
>>>         problem.
>>>
>>>         Thanks,
>>>         Anurag
>>>
>>>         On Mon, Jun 28, 2010 at 10:10 PM, Marc Karasek
>>>         <marckarasek at gmail.com <mailto:marckarasek at gmail.com>> wrote:
>>>
>>>             I will check that on the sticks I have already made.
>>>
>>>             For future reference, it seems if the stick is already
>>>             named : FEDORA
>>>             and you put a live image on it, it works out of the box.
>>>             If you have it named something else then put the image
>>>             on it, change the
>>>             name to FEDORA, this still fails w/o the cahnge to the
>>>             cmd line.
>>>
>>>             Marc
>>>
>>>             On 6/28/2010 11:55 AM, Sebastian Dziallas wrote:
>>>             > On Mon, Jun 28, 2010 at 4:54 PM, Marc
>>>             Karasek<marckarasek at gmail.com
>>>             <mailto:marckarasek at gmail.com>>  wrote:
>>>             >
>>>             >> I am trying to put together some sticks for shipping
>>>             to Uganda.
>>>             >>
>>>             >> I am using the latest usb creater and image
>>>             (Mirabelle Fedora13)
>>>             >>
>>>             >> I followed the instructions, but when I tested the
>>>             sticks on a notebook,
>>>             >> I got the error:
>>>             >> no root device found
>>>             >> sleeping forever
>>>             >>
>>>             >> In following a few google links, this seems to be
>>>             lined to the root= and
>>>             >> overlay= options on the kernel cmd line.
>>>             >> I looked at what the default was and it had a UUID#
>>>             in both of these
>>>             >> places.
>>>             >>
>>>             >> I named the stick FEDORA (I remembered this used to
>>>             be part of the
>>>             >> instructions in the past), changed the cmd line to
>>>             >> root=LABEL=FEDORA and overlay=LABEL=FEDORA and it worked.
>>>             >>
>>>             >> The problem is I need to make this foolproof, I do
>>>             not need them to be
>>>             >> having to edit cmd lines each time they boot.  (The
>>>             place it is going
>>>             >> they have never seen a computer, so it has to be
>>>             foolproof).
>>>             >>
>>>             >> Should I just change the name of the USB stick to
>>>             match the UUID# or is
>>>             >> this a bug in the image?
>>>             >>
>>>             >> Marc
>>>             >>
>>>             > Hi Marc,
>>>             >
>>>             > thanks for your email and welcome to the list! :)
>>>             >
>>>             > There should be a syslinux directory on the usb key
>>>             when you plug it
>>>             > into a machine (and don't boot from it, that is).
>>>             Inside of that
>>>             > directory, there's a file called syslinux.cfg which
>>>             contains all the
>>>             > arguments applied at boot. You should be able to make
>>>             the change
>>>             > there, which will persist then.
>>>             >
>>>             > Let us know how it goes!
>>>             >
>>>             > Cheers,
>>>             > --Sebastian
>>>             >
>>>             >
>>>             >> _______________________________________________
>>>             >> SoaS mailing list
>>>             >> SoaS at lists.sugarlabs.org
>>>             <mailto:SoaS at lists.sugarlabs.org>
>>>             >> http://lists.sugarlabs.org/listinfo/soas
>>>             >>
>>>             > _______________________________________________
>>>             > SoaS mailing list
>>>             > SoaS at lists.sugarlabs.org <mailto:SoaS at lists.sugarlabs.org>
>>>             > http://lists.sugarlabs.org/listinfo/soas
>>>             >
>>>             _______________________________________________
>>>             SoaS mailing list
>>>             SoaS at lists.sugarlabs.org <mailto:SoaS at lists.sugarlabs.org>
>>>             http://lists.sugarlabs.org/listinfo/soas
>>>
>>>
>>>
>>>
>>>         -- 
>>>         Anurag Goel
>>>
>>>
>>>         _______________________________________________
>>>         SoaS mailing list
>>>         SoaS at lists.sugarlabs.org  <mailto:SoaS at lists.sugarlabs.org>
>>>         http://lists.sugarlabs.org/listinfo/soas
>>>            
>>
>>         _______________________________________________
>>         SoaS mailing list
>>         SoaS at lists.sugarlabs.org <mailto:SoaS at lists.sugarlabs.org>
>>         http://lists.sugarlabs.org/listinfo/soas
>>
>>
>>
>>
>>     -- 
>>     Anurag Goel
>>
>>
>>     _______________________________________________
>>     SoaS mailing list
>>     SoaS at lists.sugarlabs.org  <mailto:SoaS at lists.sugarlabs.org>
>>     http://lists.sugarlabs.org/listinfo/soas
>>        
>
>     _______________________________________________
>     SoaS mailing list
>     SoaS at lists.sugarlabs.org <mailto:SoaS at lists.sugarlabs.org>
>     http://lists.sugarlabs.org/listinfo/soas
>
>
>
>
> -- 
> Anurag Goel
>
>
> _______________________________________________
> SoaS mailing list
> SoaS at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/soas/attachments/20100701/d22ad397/attachment-0001.htm 


More information about the SoaS mailing list