3.1 .sgn file missing [Solved]
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
3.1 .sgn file missing [Solved]
Just downloaded the new Porteus-LXQT-v3.1-x86_64.iso file and booting fails with porteus-v3.1-x86_64.sgn file missing. Using the same boot parms that I used with the 12/8 version of the .iso file and the .sgn file is in the .iso. Something changed?
-edit-
Corrected .sgn file name.
-edit-
Corrected .sgn file name.
Last edited by Ed_P on 14 Dec 2014, 05:13, edited 2 times in total.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: 3.1 .sgn file missing
nothing has changed, i'm sure it's users fault.
there is no such thing like Porteus-LXQT-v3.1-x86_64.sgn by default so if you added it then you have to use 'sgnfile=' cheatcode correctly.
there is no such thing like Porteus-LXQT-v3.1-x86_64.sgn by default so if you added it then you have to use 'sgnfile=' cheatcode correctly.
Please add [Solved] to your thread title if the solution was found.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
Disregard the posting characters. The actual error msg is all in lowercase characters. "searching for porteus-v3.1-x86_64.sgn" and it isn't being found. No user error, I'm booting the ISO.
I redownloaded the ISO and retried to boot it, same problem.
These all worked yesterday.
-edit-
Corrected .sgn file name.
I redownloaded the ISO and retried to boot it, same problem.
Code: Select all
set ISO31=Porteus-LXQt-v3.1-x86_64.iso
title Porteus 3.1 Always Fresh \n186MB\n %ISO31%
find --set-root /ISOs/%ISO31%
map --heads=0 --sectors-per-track=0 /ISOs/%ISO31% (0xff)
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz from=/ISOs/%ISO31% volume=40
initrd /boot/syslinux/initrd.xz
title Porteus 3.1 Always Fresh +\n186MB\n %ISO31% with networks
find --set-root /ISOs/%ISO31%
map --heads=0 --sectors-per-track=0 /ISOs/%ISO31% (0xff)
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz from=/ISOs/%ISO31% extramod=/porteus3.1/modnetwork volume=40
initrd /boot/syslinux/initrd.xz
title Porteus 3.1 changes=EXIT \n186MB\n %ISO31%
find --set-root /ISOs/%ISO31%
map --heads=0 --sectors-per-track=0 /ISOs/%ISO31% (0xff)
map --hook
root (0xff)
kernel /boot/syslinux/vmlinuz from=/ISOs/%ISO31% changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules volume=40 ramsize=80%
initrd /boot/syslinux/initrd.xz
These all worked yesterday.
-edit-
Corrected .sgn file name.
Last edited by Ed_P on 13 Dec 2014, 20:29, edited 1 time in total.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: 3.1 .sgn file missing
It certainly won't find that. The file to look for is: porteus-v3.1-i486.sgn regardless of what desktop environment you are using. I'm sure if you boot in fresh mode with no extramod or rootcopy stuff you will find it works. I just download a Porteus-LXQt-v3.1-i486 iso and booted from it without any problems."searching for porteus-lxqt-v3.1-x86_64.sgn" and it isn't being found.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
Wrong. https://drive.google.com/file/d/0B1Uj3O ... sp=sharing Booting AF mode. Same results in any other mode also.brokenman wrote:The file to look for is: porteus-v3.1-i486.sgn
I'm happy for youbrokenman wrote: I just download a Porteus-LXQt-v3.1-i486 iso and booted from it without any problems.

And to be clear, the .iso that I downloaded 4 days ago, with the same name, booted, in all modes. How else could I have been able to report this bug: http://forum.porteus.org/viewtopic.php?f=132&t=4120Ed_P wrote:Just downloaded the new Porteus-LXQT-v3.1-x86_64.iso file and booting fails
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: 3.1 .sgn file missing
obviously brokenman knows that it is porteus-v3.1-x86_64.sgn for 64bit arch.
the problem is that your setup looks for:
porteus-lxqt-v3.1-x86_64.sgn
and 'lxqt' string is not present in any sgn file by default.
this is your problem.
next time when booting fails please run 'cat /proc/cmdline' and show us screenshot/photo.
thanks
the problem is that your setup looks for:
porteus-lxqt-v3.1-x86_64.sgn
and 'lxqt' string is not present in any sgn file by default.
this is your problem.
next time when booting fails please run 'cat /proc/cmdline' and show us screenshot/photo.
thanks
Please add [Solved] to your thread title if the solution was found.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
My setup does not look for porteus-lxqt-v3.1-x86_64.sgn it looks for Porteus-LXQT-v3.1-x86_64.iso. Your 12/12/14 Porteus-LXQT-v3.1-x86_64.iso file is looking for porteus-v3.1-x86_64.sgn and not finding it. See the screen shot I posted earlier: https://drive.google.com/file/d/0B1Uj3O ... view?pli=1fanthom wrote:the problem is that your setup looks for:
porteus-lxqt-v3.1-x86_64.sgn
and 'lxqt' string is not present in any sgn file by default.
this is your problem
next time when booting fails please run 'cat /proc/cmdline' and show us screenshot/photo.
thanks


Please look at the screen shot I posted above.
BTW The Porteus-LXQt-v3.1-x86_64.iso file dated 12/8/14 doesn't have the problem. So I suspect the problem is tied to your EFI change, and this isn't an EFI machine.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: 3.1 .sgn file missing
Way to ask for help. Not.I'm happy for younow try the one I downloaded.
You led us down the garden path thinking that the .sgn string was wrong (you have edited your first post). I downloaded a version to test it (arch difference is of no consequence) and found nothing wrong. I won't be chasing this ghost.My setup does not look for porteus-lxqt-v3.1-x86_64.sgn it looks for Porteus-LXQT-v3.1-x86_64.iso.
Then how could you suspect that any EFI change is related?and this isn't an EFI machine.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: 3.1 .sgn file missing
If it doesn't boot how do I run a command?
maybe you could read messages posted on the screen when porteus fails to boot? last sentence is crucial
anyway - i have just setup booting from the ISO and it works perfectly well for me:
i have downloaded the ISO right now. maybe your one is corrupted? did you check md5sum?
maybe you could read messages posted on the screen when porteus fails to boot? last sentence is crucial
anyway - i have just setup booting from the ISO and it works perfectly well for me:
Code: Select all
root@porteus:/home/guest# cat /proc/cmdline
quiet from=Porteus-LXQT-v3.1-x86_64.iso
root@porteus:/home/guest# cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: UUID="ac8d44b2-3518-4bab-b56c-d98d98816f1d" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: LABEL="Porteus-Kiosk" TYPE="iso9660"
/dev/sda3: UUID="6559f0c1-8648-4008-bb52-b4abdfec029f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda4: LABEL="stuff" UUID="120a9458-07c9-4e50-a9ec-894ad115e101" TYPE="ext4"
# Booting device:
/mnt/sda4
# Porteus data found in:
/mnt/isoloop/porteus
# Changes are stored in:
memory
# Non standard /rootcopy dir:
none
# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-lxqt.xzm
/mnt/isoloop/porteus/base/04-firefox.xzm
Please add [Solved] to your thread title if the solution was found.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: 3.1 .sgn file missing
Look at your 'set' option in your config (your second post) above and then look at the name of the ISO in the link that you asked me so nicely to download. Could user error possibly be the problem?
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
Hey I had a smilie. I was being nice. Honest.brokenman wrote:Way to ask for help. Not.I'm happy for younow try the one I downloaded.
Apparently but that wasn't my intent. I couldn't remember the exact name of the .sgn file and thought it was the same as the name of the .iso file. I was wrong. Sorry.You led us down the garden path thinking that the .sgn string was wrongMy setup does not look for porteus-lxqt-v3.1-x86_64.sgn it looks for Porteus-LXQT-v3.1-x86_64.iso.
The fixes that were going to be included in the 12/12/14 file noted here: http://forum.porteus.org/viewtopic.php? ... 771#p29762Then how could you suspect that any EFI change is related?and this isn't an EFI machine.
If so I'm not seeing it. I am booting the ISO I downloaded. If I spelled/keyed it wrong I wouldn't be booting at all. The parms are a copy of the ones I use for 2.1 and 3.0 and 3.0 still boots ok. It's what I'm using now. And they work for the 12/8/14 download with the same name.brokenman wrote:Look at your 'set' option in your config (your second post) above and then look at the name of the ISO in the link that you asked me so nicely to download. Could user error possibly be the problem?
fanthom wrote:If it doesn't boot how do I run a command?
maybe you could read messages posted on the screen when porteus fails to boot? last sentence is crucial

Thank you fanthom. And now you see why reading isn't good for me.
Wow!!anyway - i have just setup booting from the ISO and it works perfectly well for me:

I did not check the md5sum. Don't know how actually, but i did consider the file could be corrupted and downloaded it a 2nd time, using a different OS even, but same results.i have downloaded the ISO right now. maybe your one is corrupted? did you check md5sum?
Thanks guys. I'm still learning. And I am trying to help.
- brokenman
- Site Admin
- Posts: 6105
- Joined: 27 Dec 2010, 03:50
- Distribution: Porteus v4 all desktops
- Location: Brazil
Re: 3.1 .sgn file missing
There is a difference in capital T on the end of LXQt. I don't know what filesystem you are booting from but this may be the problem.If so I'm not seeing it.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Wear your underpants on the outside and put on a cape.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
Good eyes Mr. brokenman. Very good eyes. Yes, the 12/8 download downloaded with a lower case "t" and the update 12/12 file had an uppercase "T". The files are stored on a NTFS file system and Grub4DOS is indeed case sensitive (I believe it's Linux based) so why it didn't balk I don't know. I will try a "T" and see if it helps. Thanks.brokenman wrote:There is a difference in capital T on the end of LXQt. I don't know what filesystem you are booting from but this may be the problem.If so I'm not seeing it.
@fanthom This is the debug shell screen: https://drive.google.com/file/d/0B1Uj3O ... sp=sharing as run under my QEMU virtual machine.
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: 3.1 .sgn file missing
Wow!! And we have a solution.brokenman wrote:There is a difference in capital T on the end of LXQt. I don't know what filesystem you are booting from but this may be the problem.

Congratulations

