XFCE-13.37 Stick Boot

[Atip]

For the first time I am trying to boot from a flash drive.

I followed the instructions in README-UsbInstall and when I am booting I get:

Code: Select all

Could not find kernel image: linux
boot:

What could be amiss or what should I enter after "boot:"?

[Shador]

Ok, it can't find the kernel image to load "linux". Not very surprising as it's looking for the wrong image.

Did you get any errors during installation from install-on-USB.sh? Can you please run ls -lR /media/<YOUR STICK>? Post the output. Also upload the output (RESULTS.txt) of the boot_info_script (root) somewhere. It's in the package boot-info-script.

[Atip]

Ok, it can't find the kernel image to load "linux". Not very surprising as it's looking for the wrong image.

Did you get any errors during installation from install-on-USB.sh? Can you please run ls -lR /media/<YOUR STICK>? Post the output. Also upload the output (RESULTS.txt) of the boot_info_script (root) somewhere. It's in the package boot-info-script.

Thanks!

I did not get any errors from install-on-USB.sh

[A-DATA UFD]$ ls -IR
README-UsbInstall ldlinux.sys salix-xfce-13.37-32.live
boot packages salixlive

Without the -I flag all packages are listed which is quite a long list.
For ./boot:
_dev_sdb.mbr.201202121216 eltorito.img install-on-USB.cmd
_dev_sdb.mbr.201202121216.0810 g2ldr install-on-USB.sh
_dev_sdc.mbr.201202121204 g2ldr.mbr mt86p
_dev_sdc.mbr.201202121227 grub syslinux.exe
_dev_sdc.mbr.201202121227.0820 grub.cat vmlinuz
_dev_sdc.mbr.201202131451 grub2-linux.img
_dev_sdc.mbr.201202131451.0820 initrd.xz


Sorry, I can't find anywhere a package boot-info-script or locate such a name.

[JRD]

Do you install it on a fat32 partition?

[Shador]

[A-DATA UFD]$ ls -IR
README-UsbInstall ldlinux.sys salix-xfce-13.37-32.live
boot packages salixlive

You must have omitted the R switch here or you used a lower-case r instead which is not the same.

Without the -I flag all packages are listed which is quite a long list.
For ./boot:
_dev_sdb.mbr.201202121216 eltorito.img install-on-USB.cmd
_dev_sdb.mbr.201202121216.0810 g2ldr install-on-USB.sh
_dev_sdc.mbr.201202121204 g2ldr.mbr mt86p
_dev_sdc.mbr.201202121227 grub syslinux.exe
_dev_sdc.mbr.201202121227.0820 grub.cat vmlinuz
_dev_sdc.mbr.201202131451 grub2-linux.img
_dev_sdc.mbr.201202131451.0820 initrd.xz

I want just the output of ls -lR <path to your stick>. It's a long list but if you post it in code tags or upload it to some pastebin, it's fine.

Sorry, I can't find anywhere a package boot-info-script or locate such a name.

It's definitely there, but maybe your mirror had not synced yet when you tried as I just added it yesterday:

Code: Select all

# LANG=C slapt-get --search boot-info-script
boot-info-script-0.60-noarch-1ab [inst=yes]: boot-info-script (script for troubleshooting booting problems)

That's the executable (just boot_info_script as root should be enough, mind the different spelling compared to the package name '-' vs '_'):

Code: Select all

# egrep 'bin/.+' /var/log/packages/boot-info-script-0.60-noarch-1ab 
usr/sbin/boot_info_script

Do you install it on a fat32 partition?

The RESULTS.txt of boot_info_script should contain exactly that information.

[Atip]

Have lately very bad intermitted Internet connection.

OK, in my linux box Salix Fluxbox-13.37 "ls -IR" outputs only directories and files in / as reported,
whereas "ls -R" lists directories and all files recursively. I do have O'Reilly, Linux in a Nut Shell.

I still could not find boot-info-script where you indicated, however, found it in sourceforge as
boot_info_script060.zip.

Here is the output as pertaining to

Code: Select all

============================= Boot Info Summary:===============================

 => Lilo is installed in the MBR of /dev/sda.
 => Syslinux MBR (3.00-3.35) is installed in the MBR of /dev/sdb.
 => No boot loader is installed in the MBR of /dev/sdc.

sdb1:
__________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 4.02 debian-20101014
...........>eq.r>.......W0.....0...~.k...~...f...M.f.f....f..8~....>2}
    Boot sector info:   Syslinux looks at sector 472 of /dev/sdb1 for its
                       second stage. SYSLINUX is installed in the directory.
                       No errors found in the Boot Parameter Block.
    Operating System:  Windows 98
    Boot files:        /ldlinux.sys /IO.SYS /MSDOS.SYS /COMMAND.COM



sdc1:
__________________________________________________________________________
    
    File system:       vfat
    Boot sector type:  SYSLINUX 3.84 3.84
    Boot sector info:   Syslinux looks at sector 2720696 of /dev/sdc1 for
    its
                       second stage. No errors found in the Boot Parameter
                       Block.
    Operating System:
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg /ldlinux.sys

Now if you want the entire RESULTS.txt files and as well the total output of "ls -R" in a file
you will have to tell my how and where to upload. I do not see a feature of file attachment here.

I compared the output of "ls -R > media-R' with the *.iso file and they are identical except
in file media-R there is an entry on the top, guess the date when created.

Code: Select all

 /media/disk-1/boot:
_dev_sdc.mbr.201202151511

[Shador]

As I said upload it to some pastebin site like pastebin.com .org whatever.

Regarding the directory listing On all linux machines I've tried so far ls -lR (lower-case Lima upper-case Romeo) works as ecpected, i.e. produces a recursive directory lisitng in the long format. Maybe you're usung a shell other than bash, customized simething else or didn't run it on Salix?
But let's just hope everything perfect, right?

Regarding boot-info-script, it definitely is there. Maybe you forgot to update the local cache (slapt-get -u)? Or your mirror is just terribly out of sync, in that case try salix.enialis.net. Or you're not running 13.37. If you don't believe me it's there have a look here: http://salix.enialis.net/x86_64/13.37/PACKAGES.TXT

Anyway the way you called it is perfectly fine too. Coud you just make the WHOLE, COMPLETE and ORIGINAL output available to me.
Before running boot_info_script please rerung install-on-USB.sh and post the COMPLETE output too.

[Atip]

As I said upload it to some pastebin site like pastebin.com .org whatever.

Regarding the directory listing On all linux machines I've tried so far ls -lR (lower-case Lima upper-case Romeo) works as ecpected, i.e. produces a recursive directory lisitng in the long format. Maybe you're usung a shell other than bash, customized simething else or didn't run it on Salix?
But let's just hope everything perfect, right?

lower-case Lima, that's it. All the time I read it and it shows, somewhat, what you sent as upper-case (ls -lR ), however,
not "L" instead more like | moved up sticking out over the R. My lower-case "i". My upper-case "L"
First problem solved. Will get to the others tomorrow.

[Atip]

I uploaded RESULTS.txt to uploadbud.com

Here is the output of install-on-USB.sh

Code: Select all

Warning: lilo is not available on your system.
  We recommend installing it, as it allows the USB to boot more
  reliable accross different machines.
Do you want to continue without lilo? [y/N] 

Warning: syslinux+grub2 is about to be installed in /dev/sdc
on partition /dev/sdc1
Do you want to continue? [y/N] 

Backing up mbr of /dev/sdc to
'/media/disk-1/boot/_dev_sdc.mbr.201202170940'...
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.000155096 s, 3.3 MB/s
Installing syslinux...
Do you want to overwrite the MBR loader (first 440 bytes)
of the disk? Recommended unless you know the code in there
already does what you want. [y/N] 

1+0 records in
1+0 records out
1 byte (1 B) copied, 0.00684433 s, 0.1 kB/s
Setting bootable flag of /dev/sdc1...
Information: You may need to update /etc/fstab.  

When asked I always said "y"

Lilo is available on my system and is what I use only.

Regards

[Shador]

Lilo is available on my system and is what I use only.

Are you sure you have the lilo binary/package installed and it's in your PATH? What's the output of "which 'lilo'" on that system?

I uploaded RESULTS.txt to uploadbud.com

Now try to download the file yourself. Did you manage to? A link to the file would be nice.
Anyway, if we get it working with lilo, which it probably does, we don't need that anymore.