no 5.5 boot with syslinux 5.01
no 5.5 boot with syslinux 5.01
extlinux.conf entries like:
label precise 5.5
kernel /LINUXes/precise/vmlinuz
append initrd=/LINUXes/precise/initrd.gz psubdir=/LINUXes/precise pkeys=de
Message after loading vmlinuz and initrd.gz: related sfs-file cannot be found !
Even if it is in / !
No problems with syslinux-4.05 !
Lupu 528 works even with syslinux-5.01 !
label precise 5.5
kernel /LINUXes/precise/vmlinuz
append initrd=/LINUXes/precise/initrd.gz psubdir=/LINUXes/precise pkeys=de
Message after loading vmlinuz and initrd.gz: related sfs-file cannot be found !
Even if it is in / !
No problems with syslinux-4.05 !
Lupu 528 works even with syslinux-5.01 !
Hi, karl! Thanks for immediate response.
Sadly pmedia=usbflash makes no difference.
My syslinux folder contains:
extlinux.conf ldlinux.sys libutil.c32 ldlinux.c32 libcom32.c32 vesamenu.c32.
Maybe something is missing?
Other distros can boot with syslinux 5.01:
KNOPPIX_V7.0.4CD-2012-08-20-EN partedmagic_2013_01_29 Porteus-XFCE-v1.2-i486 SalineOS-1.6-i386 systemrescuecd-x86-3.3.0 xubuntu-12.04-desktop-i386
Sadly pmedia=usbflash makes no difference.
My syslinux folder contains:
extlinux.conf ldlinux.sys libutil.c32 ldlinux.c32 libcom32.c32 vesamenu.c32.
Maybe something is missing?
Other distros can boot with syslinux 5.01:
KNOPPIX_V7.0.4CD-2012-08-20-EN partedmagic_2013_01_29 Porteus-XFCE-v1.2-i486 SalineOS-1.6-i386 systemrescuecd-x86-3.3.0 xubuntu-12.04-desktop-i386
I do not believe that this is a syslinux issue. Once you get to the "sfs not found" situation, syslinux is no longer running.
I set up a Precise 5.5 flash drive using your "/LINUXes/precise/vmlinuz" setup and it worked correctly.
If there are any other Precise components on your hard drive, temporarily rename/remove them.
I set up a Precise 5.5 flash drive using your "/LINUXes/precise/vmlinuz" setup and it worked correctly.
If there are any other Precise components on your hard drive, temporarily rename/remove them.
hi, rcrsn51!rcrsn51 wrote:I do not believe that this is a syslinux issue. Once you get to the "sfs not found" situation, syslinux is no longer running.
I set up a Precise 5.5 flash drive using your "/LINUXes/precise/vmlinuz" setup and it worked correctly.
If there are any other Precise components on your hard drive, temporarily rename/remove them.
No, no other Precise components anywhere.
After havin used a 16 GB USB stick,
I installed syslinux 5.01 on an 4GB SD card and still Precise 5.5 does not boot.
The code in initrd.gz is a little confusing .
Just an idea : Because i normally would boot with psubdir=precise without a slash, it might be
psubdir=LINUXes/precise
in your case .
Just an idea : Because i normally would boot with psubdir=precise without a slash, it might be
psubdir=LINUXes/precise
in your case .
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
Hi, Karl!Karl Godt wrote:The code in initrd.gz is a little confusing .
Just an idea : Because i normally would boot with psubdir=precise without a slash, it might be
psubdir=LINUXes/precise
in your case .
No, psubdir=LINUXes/precise does not succeed either.
Changing from ext4 to vfat and installing syslinux 5.01 makes no difference.
Now I deleted all other distros in /LINUXes,
only /LINUXes/precise remained, containing: initrd.gz puppy_precise_5.5.sfs vmlinuz.
/syslinux contains: extlinux.conf ldlinux.sys libutil.c32 ldlinux.c32 libcom32.c32 vesamenu.c32
No other folders.
extlinux.conf entry is reduced to:
label precise
kernel /LINUXes/precise/vmlinuz
append initrd=/LINUXes/precise/initrd.gz
After loading vmlinuz and initrd.gz, now suddenly this appears:
Dumping last lines of /tmp/bootinit.log ...
ls: /lib/keymaps//L*.gz: No such file or directory
Dumping last lines of kernel log ...
<6> [ 3.045993] NET: Registered protocol family 17
<5> [ 3.045999] Registering the dns-resolver key type
<6> [ 3.046015] Using IPI No-shortcut mode
<6> [ 3.046506] Freeing unused kernel memory: 360k freed
Pausing for 60 seconds
Loading drivers needed to access disk drives. done
Searching for Puppy files ...... puppy_precice_5.5.sfs not found.
Dropping out to initial-ramdisk console ...
Then I moved initrd.gz puppy_precise_5.5.sfs vmlinuz to /,
deleted the folder /LINUXes/precise and reduced the extlinux.conf entry to:
label precise
kernel /vmlinuz
append initrd=/initrd.gz
The same message lines as above appear again.
Downloaded iso again from nluug, md5sum check positive.rcrsn51 wrote:Are you sure that you have good copies of the core Puppy files? I would download the ISO again and extract the three files from it.
But it is the same problem:
now I used /dev/sda1 with ext4 to install syslinux 5.01:
cat mbr.bin > /dev/sda
./extlinux -s --install /mnt/sda1/syslinux
syslinux.conf:
label lupu528
kernel /LINUXes/lupu/vmlinuz
append initrd=/LINUXes/lupu/initrd.gz psubdir=/LINUXes/lupu pkeys=de
label precise 5.5
kernel /LINUXes/precise/vmlinuz
append initrd=/LINUXes/precise/initrd.gz psubdir=/LINUXes/precise pkeys=de
lupu528 boots perfectly, precise 5.5 not:
Loading drivers needed to access disk drives. done
Searching for Puppy files ...... puppy_precice_5.5.sfs not found.
Dropping out to initial-ramdisk console ...
Acer Extensa 5635Z, Intel Pentium T4500 (2.3 GHz, 800 MHz FSB), Intel GMA 4500M Up to 1695 MB DVMT, 15,6" (1366x768) LED LCD, 4 GB Memory, 500 GB HDD, DVD, Acer Nplify(TM) 802.11b/g/n, Windows 7 deleted.
Recent Puppies have a new procedure that speeds up the search for its files. But with some hardware, it works too well.
Some distros, like Fatdog, have a "waitusb" option that slows down the boot procedure. It may be possible to add this to Precise.
1. Install the editinit-1.0.pet below.
2. Go onto the flash drive and open the folder containing the Precise initrd.gz.
3. Open a terminal and type the command: editinit.
4. Line 153 says "#1202015 internationalize....." (To turn on line numbering in Leafpad, look under Options.)
5. In the space ABOVE, insert the line
6. Save, exit and reboot.
Some distros, like Fatdog, have a "waitusb" option that slows down the boot procedure. It may be possible to add this to Precise.
1. Install the editinit-1.0.pet below.
2. Go onto the flash drive and open the folder containing the Precise initrd.gz.
3. Open a terminal and type the command: editinit.
4. Line 153 says "#1202015 internationalize....." (To turn on line numbering in Leafpad, look under Options.)
5. In the space ABOVE, insert the line
Code: Select all
sleep 5
- Attachments
-
- editinit-1.0.pet
- (454 Bytes) Downloaded 520 times
Last edited by rcrsn51 on Tue 16 Apr 2013, 16:49, edited 1 time in total.
Super, now find out about supported commands and detected partitions and log files: ls /bin; ls /sbin; probepart_init; for i in /tmp/*; do e3 $i; doneDropping out to initial-ramdisk console ...
Had an E5230 2GHz, which was quite good to compile kernels using Pup*Lupu*-5.1.1 kernel 2.6.33.2 as frugal to HDD . Unfortunately dead, has special CPU so not P4 compatible though P4 fits into the socket.Acer Extensa 5635Z, Intel Pentium T4500 (2.3 GHz, 800 MHz FSB), Intel GMA 4500M Up to 1695 MB DVMT, 15,6" (1366x768) LED LCD, 4 GB Memory, 500 GB HDD, DVD, Acer Nplify(TM) 802.11b/g/n, Windows 7 deleted.
Yes its is right, PSUBDIR= shows up 13x in current /init and gets a preceding / if not given as i look into current woof2 of 2013-04-02, opposite to 4.3 /init , which has only one PSUBDIR= match and does not put a slash anywhere .No, psubdir=LINUXes/precise does not succeed either.
Well, I did it, but to no effect.rcrsn51 wrote:Recent Puppies have an "improved" procedure that speeds up the search for its files. But with some hardware, it works too well.
Some distros, like Fatdog, have a "waitusb" option that slows down the boot procedure. It may be possible to add this to Precise.
1. Install the editinit-1.0.pet below.
2. Go onto the flash drive and open the folder containing the Precise initrd.gz.
3. Open a terminal and type the command: editinit.
4. Line 153 says "#1202015 internationalize....." (To turn on line numbering in Leafpad, look under Options.)
5. In the space ABOVE, insert the line6. Save, exit and reboot.Code: Select all
sleep 5
Well, all files are included in precise55boot.tar.gz attached.Karl Godt wrote:Super, now find out about supported commands and detected partitions and log files: ls /bin; ls /sbin; probepart_init; for i in /tmp/*; do e3 $i; doneDropping out to initial-ramdisk console ...
- Attachments
-
- precise55boot.tar.gz
- (1.19 KiB) Downloaded 481 times
I have 2 mp3 players : One boots fine, the other says farewell to the BIOS after some seconds .
As a workaround i would first try to
again
anf if that fails
which i use when i boot with the wrong pdev1=sdbX or psubdir=XXX.d parameter.
As a workaround i would first try to
Code: Select all
cd /
/init
anf if that fails
Code: Select all
mount -t proc none /proc
mount -t sysfs none /sys
cd /
pdev1=sdb1 psubdir=XXY.d ./init
I am presuming at this point is that "precice" as spelled above is a typo in the message above not in any of the configuration files.wiejetzt Yesterday, at 06:54 wrote: Pausing for 60 seconds
Loading drivers needed to access disk drives. done
Searching for Puppy files ...... puppy_precice_5.5.sfs not found.
Dropping out to initial-ramdisk console ...
I once had an issue with unetbootin not changing "pmedia=cd" to "pmedia=usbflash" and by the way if you use a USB HD it may want pmedia=usbhd
Pressing F2 and F3 at boot gives the options and advanced options, you may want to try
puppy pupsfs=sdc1:/puppy_precise_5.5.sfs
at the boot: prompt, where sdc1: is the device suggested in the F3 help. (it may be sda1 or sda2 on your system)
I tested both methods and both stopped at the same point:Karl Godt wrote:I have 2 mp3 players : One boots fine, the other says farewell to the BIOS after some seconds .
As a workaround i would first try toagainCode: Select all
cd / /init
anf if that failswhich i use when i boot with the wrong pdev1=sdbX or psubdir=XXX.d parameter.Code: Select all
mount -t proc none /proc mount -t sysfs none /sys cd / pdev1=sdb1 psubdir=XXY.d ./init
Loading 'de' keyboard layout ... done
Loading drivers needed to access disk drives. done
Searching for Puppy files... done
Loading the 'puppy_precise_5.5.sfs' main file... copying to ram.. done
Setting up the layered filesystem ... done
Performing a 'switch_root' to the layered filesystem...# .
yeah, /sbin/switch looks like this :
It is mounted it seems .
Now look at the output of
commands . Maybe needs a
Will activate my testbox to reproduce it. It's nice weather here Can take some hours ..
echo "Puppy is out for a walk .. "
Dunno for now whats happen to /sbin/init inside the precise-5.5.sfs .#!/bin/sh
#if have dropped to a shell in initramfs, type 'exec switch' to keep going.
sync
umount /proc/bus/usb
umount /sys
umount /proc
#now using cpio archive for initramfs 'initial ramdisk'...
exec switch_root /pup_new /sbin/init
It is mounted it seems .
Now look at the output of
Code: Select all
mount
df
Code: Select all
cd /initrd/pup_rw
./sbin/init
echo "Puppy is out for a walk .. "
Hi, Peterm321!Peterm321 wrote:I am presuming at this point is that "precice" as spelled above is a typo in the message above not in any of the configuration files.wiejetzt Yesterday, at 06:54 wrote: Pausing for 60 seconds
Loading drivers needed to access disk drives. done
Searching for Puppy files ...... puppy_precice_5.5.sfs not found.
Dropping out to initial-ramdisk console ...
I once had an issue with unetbootin not changing "pmedia=cd" to "pmedia=usbflash" and by the way if you use a USB HD it may want pmedia=usbhd
Pressing F2 and F3 at boot gives the options and advanced options, you may want to try
puppy pupsfs=sdc1:/puppy_precise_5.5.sfs
at the boot: prompt, where sdc1: is the device suggested in the F3 help. (it may be sda1 or sda2 on your system)
Yes, "precice" is a typing error, I do not know a way to cut and paste at this stage.
I tried in /syslinux/extlinux.conf:
Code: Select all
label precise-pupsfs
kernel /LINUXes/precise/vmlinuz
append initrd=/LINUXes/precise/initrd.gz pupsfs=sda1:/LINUXes/precise/puppy_precise_5.5.sfs pkeys=de
Code: Select all
Loading 'de' keyboard layout ... done
Loading drivers needed to access disk drives. done
Searching for Puppy files... done
Loading the 'puppy_precise_5.5.sfs' main file... copying to ram.. done
Setting up the layered filesystem ... done
Performing a 'switch_root' to the layered filesystem...
[ 9.542677] Kernel panic - not syncing: Attempted to kill init!
[ 9.542752] Pid 1, comm: switch_root Not tainted 3.2.29 #1
[ 9.542783] Call Trace:
[...] [...] ? ...
[...] [...] ? ...
[...] [...] ? ...
[...] [...] ? ...
Karl Godt wrote: Now look at the output ofcommands . Maybe needs aCode: Select all
mount df
Will activate my testbox to reproduce it. It's nice weather hereCode: Select all
cd /initrd/pup_rw ./sbin/init
Code: Select all
#pwd
/
#mount
mount: no /proc/mounts
#df
Filesystem 1K-blocks Used Available Use% Mounted on
df: /proc/mounts: No such file or directory
#cd /initrd/pup_rw
/bin/sh: cd: can't cd to /initrd/pup_rw
#cd /initrd
/bin/sh: /initrd not found