Porteus 3.2rc3 bug - sidebar

Technical issues/questions of an intermediate or advanced nature.
User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Porteus 3.2rc3 bug - sidebar

Post#1 by Ed_P » 14 Jun 2016, 19:01

Porteus Cinnamon x86_64 with initrd (1).xz

Code: Select all

Starting init script ......
sh: 0: unknown operand
^searching for porteus........sgn file
^device not ready yet? delaying 1 seconds

Porteus data not found.
 :
 :
Note, I did rename the initrd (1).xz download as initrd.xz

How I recreated the ISO file.

Code: Select all

guest@porteus:~$ make-iso.sh
bash: make-iso.sh: command not found
guest@porteus:~$ make_iso.sh
bash: make_iso.sh: command not found
guest@porteus:~$ ./make_iso.sh
bash: ./make_iso.sh: No such file or directory
guest@porteus:~$ /mnt/live/mnt/isoloop/porteus/make_iso.sh
Target ISO file name [ Hit enter for /mnt/live/mnt/porteus.iso ]: /mnt/sda5/ISOs/Porteus-Cinnamon-v3.2rc3X-x86_64.iso
Setting input-charset to 'UTF-8' from locale.
3.01a16 (x86_64-unknown-linux-gnu)
Scanning ../.
Scanning .././boot
Scanning .././boot/docs
Scanning .././boot/syslinux
Excluded by match: .././boot/syslinux/isolinux.boot
Scanning .././porteus
Scanning .././porteus/base
Scanning .././porteus/modules
Scanning .././porteus/optional
Scanning .././porteus/rootcopy
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
Size of boot image is 4 sectors -> No emulation
mkisofs: Read-only file system. Error opening boot image file '.././boot/syslinux/isolinux.bin' for update.
guest@porteus:~$ isomaster
ISO Master warning: failed to open config file for reading, trying to create

(isomaster:2936): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
mangling
remangled 'PORTEUS_INSTAL' -> 'POR~GVIN'
opening '/mnt/sda5/ISOs/Porteus-Cinnamon-v3.2rc3X-x86_64.iso' for writing
writing blank at 0
writing terminator at 9800
sorting 9660
writing primary directory tree at A800
sorting joliet
writing supplementary directory tree at 11800
writing 9660 path tables at 18800
writing joliet path tables at 19800
writing files at 1A800
writing long NMs at FBF4800
writing pvd at 8000
writing svd at 9000
freeing memory


Quitting
guest@porteus:~$ 
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2rc3 bug - sidebar

Post#2 by Bogomips » 14 Jun 2016, 19:40

@ Ed
  • md5sum checked ok?
  • Use GUI Isomaster, It's as easy as pie:
    1. boot > syslinux
    2. Remove initrd.xz
    3. Add test initrd.xz
    4. Save to new iso filename
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#3 by Ed_P » 14 Jun 2016, 19:56

No. Don't know how to check md5sum. (besides I was using another OS at the time. ;-) )

Actually I did use IsoMaster. Check the log I posted. It did indicate an error but I don't think it was serious.

BTW Is there a Linux app to make a file contiguous? I use Auslogics DiskDefrag in Windows to make the ISOs contiguous.
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2rc3 bug - sidebar

Post#4 by Bogomips » 14 Jun 2016, 21:06

Code: Select all

md5sum  /Path/to/initrd.xz
Checking agaist a file: viewtopic.php?f=39&t=5822&p=46070#p46070

Noticed an error, something to do with porteus.cfg. But really there should be no error, as porteus.cfg not touched. Can understand if happened with removing initrd.xz, otherwise there should be no error, And this you got using the GUI? Can you try again and see if the error occurs once more?
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2rc3 bug - sidebar

Post#5 by Bogomips » 14 Jun 2016, 21:41

Another Test (32 bit) booting from USB and using porteus.cfg.

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet initrd=rc3/initrd.xz from=/tmp/iso/rc3/i586/Porteus-KDE-v3.2rc3-i586.iso rootcopy=UUID:b173/rcpy extramod=/dev/sda5/black cliexec=mount~--bind~/home/guest/p9/tmp~/tmp copy2ram ramsize=30% noauto delay=10 BOOT_IMAGE=vmlinuz

guest@porteus:~$ cat /var/log/porteus-iso-data
/mnt/sda10//tmp/iso/rc3/i586/Porteus-KDE-v3.2rc3-i586.iso
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 5436
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus 3.2rc3 bug - sidebar

Post#6 by brokenman » 15 Jun 2016, 02:21

I've used the idea from your initrd.xz Bogomips. It will put the entry into /var/log/porteus-livedbg.

ISO=/path/to/booted/file.iso

Thanks
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#7 by Ed_P » 15 Jun 2016, 05:09

Bogomips wrote:

Code: Select all

md5sum  /Path/to/initrd.xz

Code: Select all

guest@porteus:~$ md5sum /mnt/sda5/porteus32rc3boot/boot/syslinux/initrd.xz
7e2b5b43a2808e23ad58ad58f6ab4a35  /mnt/sda5/porteus32rc3boot/boot/syslinux/initrd.xz
guest@porteus:~$ 
Can't do much more with 3.,2 at this point. Everytime I boot it now it requires a GUI logon to guest. Replying guest/guest just seems to loop the logon screen again. Logging on as root/toor works. But I didn't have this logon screen before and now I'm getting it even with the original unchanged 3.2 rc3 ISO. Somehow my save.dat file is now screwed up.
Noticed an error, something to do with porteus.cfg. But really there should be no error, as porteus.cfg not touched. Can understand if happened with removing initrd.xz, otherwise there should be no error, And this you got using the GUI? Can you try again and see if the error occurs once more?
When I initially tried replacing the initrd file with IsoMaster I got an error because the file was already there. I had to delete it first then add the new version.

It's late. Going to bed. Will work on this tomorrow.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#8 by Ed_P » 15 Jun 2016, 15:14

@Bogomips

Ok. When I boot like so:

Code: Select all

guest@porteus:~$ ./bootdev.sh
System Memory:   173M
Boot device:   /mnt/isoloop
Boot device format: ???????
Boot folder:   ????
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v3.2rc3-x86_64.iso
OS:       Porteus-v3.2rc3
ARCH:     x86_64
Kernel:   Linux porteus 4.6.1-porteus 
Cmdline:  quiet from=/ISOs/Porteus-CINNAMON-v3.2rc3-x86_64.iso extramod=/porteus3.2/Modules;/porteus3.2/modsavedat
^C
guest@porteus:~$ ls /mnt/sda5/porteus3.2/Modules
firefox-47.0b9-x86_64-1.xzm*
flashplayer-plugin-11.2.202.621-x86_64-1alien.xzm*
guest@porteus:~$ ls /mnt/sda5/porteus3.2/modsavedat
porteussave.dat.xzm*
guest@porteus:~$ 
32rc3 boots ok. :good: The porteussave.dat.xzm file is a normal changes=EXIT file that I created with 3.2rc3 earlier for my network settings and a couple of sh scripts in the /home/guest/ folder that I then copied and renamed as a module.

When I copy the porteussave.dat.xzm file back to the changes folder and rename it back to just porteussave.dat and boot with these options:

Code: Select all

extramod=/porteus3.2/Modules changes=EXIT:/porteus3.2/changes/porteussave.dat
I get a GUI logon screen for guest. :shock: I never had that before. And entering a password of "guest" simply reboots to the logon screen. If I change the logon from guest to root I am able to boot. :%)

I do not believe the situation is tied to your initrd.xz module.

I am going to rebuild the rc3 ISO with your initrd.xz module and retry it. I will use IsoMaster since the make_iso.sh script didn't work well for me.

Back later.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#9 by Ed_P » 15 Jun 2016, 17:40

If you use the Cinnamon file manager Nemo and click on an ISO file it opens IsoManager. :good:

Rebuilt the ISO with your initrd.xz, booted it and got:

Code: Select all

(hd0,4)
Map......
Error 60: File  
for drive emulation must be in one contiguous area.[/code]
Booted to Windows and defraged the ISO file.

Rebooted the modified ISO and got:

Code: Select all

Starting init script...
sh: 0: unknown operand
Searching for  porteus.......sgn file
And then it booted. :good:

Code: Select all

guest@porteus:~$ cat /var/log/porteus-iso-data
/mnt/sda5//ISOs/Porteus-CINNAMON-v3.2rc3X-x86_64.iso
guest@porteus:~$ ./bootdev.sh
System Memory:   173M
Boot device:   /mnt/isoloop
Boot device format: 
Boot folder:   ????
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v3.2rc3X-x86_64.iso
OS:       Porteus-v3.2rc3
ARCH:     x86_64
Kernel:   Linux porteus 4.6.1-porteus 
Cmdline:  quiet from=/ISOs/Porteus-CINNAMON-v3.2rc3X-x86_64.iso extramod=/porteus3.2/Modules;/porteus3.2/modsavedat
^C
guest@porteus:~$ 
:)

Hopefully this means that with your code the Boot Device operand in 3.2 will reflect the actual device again. :)
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2rc3 bug - sidebar

Post#10 by Bogomips » 15 Jun 2016, 17:42

brokenman wrote:I've used the idea from your initrd.xz Bogomips. It will put the entry into /var/log/porteus-livedbg.
ISO=/path/to/booted/file.iso
md5sum of Updated Initrd:
e27023acc78169b3304d6469521dddcd initrd_rc3.xz
  • Cinnamon 64 bit

    Code: Select all

    guest@porteus:~$ cat /proc/cmdline 
    quiet from=/dev/sda10/tmp/iso/rc3/x86_64/Porteus-CINNAMON-v3.2rc3-x86_64.iso copy2ram ramsize=30% noauto timezone=Europe/London volume=30% rootcopy=/dev/sda4/cin64rcp  guiexec=Prolog/pmx_rc3.sh cliexec=mount~--bind~/home/guest/p9/tmp~/tmp
    
    guest@porteus:~$ cat /var/log/porteus-livedbg 
    # Recognized devices:
    ...
    /dev/sdb1: UUID="23B9-F6C2" TYPE="vfat" 
    /dev/sdb2: UUID="3cedaa92-6cfd-4f71-8994-54ab948be7cc" TYPE="ext2" 
    /dev/sdc1: UUID="ab55fc94-4882-417b-b173-7f159944fa9b" TYPE="ext2" 
    /dev/sdc2: UUID="30e88aba-c81c-49ea-9e9b-d23edd56b578" TYPE="ext4" 
    
    # Booting device:
    /mnt/isoloop
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    /dev/sda4/cin64rcp
    
    # Modules activated during boot time:
    /memory/copy2ram/000-kernel.xzm
    /memory/copy2ram/001-core.xzm
    /memory/copy2ram/002-xorg.xzm
    /memory/copy2ram/003-cinnamon.xzm
    
    ISO=/mnt/sda10/tmp/iso/rc3/x86_64/Porteus-CINNAMON-v3.2rc3-x86_64.iso
    
  • KDE5 32 bit

    Code: Select all

    guest@porteus:~$ cat /proc/cmdline
    quiet initrd=rc3/initrd.xz from=/tmp/iso/rc3/i586/Porteus-KDE-v3.2rc3-i586.iso rootcopy=UUID:b173/rcpy extramod=/dev/sda5/black cliexec=mount~--bind~/home/guest/p9/tmp~/tmp copy2ram ramsize=30% noauto delay=10 BOOT_IMAGE=vmlinuz
    
    guest@porteus:~$ cat /var/log/porteus-livedbg 
    # Recognized devices:
    ...
    /dev/sdb1: UUID="23B9-F6C2" TYPE="vfat" 
    /dev/sdb2: UUID="3cedaa92-6cfd-4f71-8994-54ab948be7cc" TYPE="ext2" 
    /dev/sdc1: UUID="ab55fc94-4882-417b-b173-7f159944fa9b" TYPE="ext2" 
    /dev/sdc2: UUID="30e88aba-c81c-49ea-9e9b-d23edd56b578" TYPE="ext4" 
    
    # Booting device:
    /mnt/isoloop
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    UUID:b173/rcpy
    
    # Modules activated during boot time:
    /memory/copy2ram/000-kernel.xzm
    /memory/copy2ram/001-core.xzm
    /memory/copy2ram/002-xorg.xzm
    /memory/copy2ram/003-kde5.xzm
    /memory/copy2ram/blacklist.xzm
    /memory/copy2ram/h3x.xzm
    
    ISO=/mnt/sda10//tmp/iso/rc3/i586/Porteus-KDE-v3.2rc3-i586.iso
    
Now more in line with what brokenman has in mind. :wink:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#11 by Ed_P » 15 Jun 2016, 19:18

Will soon see. :)

Code: Select all

guest@porteus:~$ md5sum /home/guest/Downloads/*
e27023acc78169b3304d6469521dddcd  /home/guest/Downloads/initrd_rc3.xz
guest@porteus:~$ 
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#12 by Ed_P » 15 Jun 2016, 20:14

:good:

Code: Select all

guest@porteus:~$ ./touchpad.sh
guest@porteus:~$ cat /var/log/porteus-livedbg | grep ISO=
ISO=/mnt/sda5//ISOs/Porteus-CINNAMON-v3.2rc3x-x86_64.iso
guest@porteus:~$ 


BTW Lately loosing the desktop background image. Happens both with your initrd and the regular one. I can reset it but can loose it again also. Strange.

I've got to address the logging on problem when using a changes save.dat file. :(
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Porteus 3.2rc3 bug - sidebar

Post#13 by Bogomips » 16 Jun 2016, 00:35

That's great. The scripts will need very little adjustment when 3.2 comes out then. As for saving changes, gave that up in Mint, where had been using persistence. By the time had it all nicely ticking over, next version came out, and had to start all over. Keeping changes for me just not worth the hassle, for the extra ease in usage.

Now just use /home/guest like a /tmp. Browser profile on hdd, big caches redirected to hdd, /tmp redirected to hdd. Most of initial settings taken care of in guiexec script, so probably will not be of advantage to have a changes=EXIT:/folder.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 5436
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus 3.2rc3 bug - sidebar

Post#14 by brokenman » 16 Jun 2016, 01:56

I've got to address the logging on problem when using a changes save.dat file.
Probably permissions on /home/guest
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus 3.2rc3 bug - sidebar

Post#15 by Ed_P » 16 Jun 2016, 04:22

brokenman wrote:I've got to address the logging on problem when using a changes save.dat file.
Probably permissions on /home/guest
See bug report here: viewtopic.php?f=117&t=5928&p=46362#p46362
Bogomips wrote:That's great. The scripts will need very little adjustment when 3.2 comes out then.
Yes, thank you very much. :friends:
As for saving changes, gave that up in Mint, where had been using persistence. By the time had it all nicely ticking over, next version came out, and had to start all over. Keeping changes for me just not worth the hassle, for the extra ease in usage.

Now just use /home/guest like a /tmp. Browser profile on hdd, big caches redirected to hdd, /tmp redirected to hdd. Most of initial settings taken care of in guiexec script, so probably will not be of advantage to have a changes=EXIT:/folder.
Interesting. I do backup most of my settings to a folder outside of Porteus with a script and have a restore script for when the save.dat file gets corrupted and needs to be rebuilt or to move to a new release. But new releases don't always have the same apps and settings so the backup and restore scripts need to be rebuilt themselves.

For example in 3.0.1 LXQT I have spaceFM bookmarks. In 3.2 Cinnamon I have nemo bookmarks. spaceFM bookmarks file is most likely not compatible with nemo's bookmarks file. In fact I don't even know where nemo's bookmarks file is. I thought /home/guest/.config/nemo/bookmark-metadata file might be them but it doesn't look like it. So....
Ed

Post Reply