Remastering SolydXK [adapted: 26 July 2019]

Post your tutorials and howtos here.
User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Snap » 01 Dec 2014 17:23

I'll go over it too. Thanks!
This likely means that your installation is broken. -Mr Pixbuf.

Image

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 01 Dec 2014 18:11

Gave it a try in the SolydK VM. Are you sure you wanted us to grab everything from Debian and do a dist-upgrade? I got this and the process (after an 800+MB download of packages) failed. Couldn't continue.

Code: Select all

Preparing to unpack .../libpam-systemd_215-6_amd64.deb ...
Unpacking libpam-systemd:amd64 (215-6) over (208-8) ...
Preparing to unpack .../systemd_215-6_amd64.deb ...
Unpacking systemd (215-6) over (208-8) ...
dpkg: warning: unable to delete old directory '/etc/systemd/system/multi-user.target.wants': Directory not empty
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for dbus (1.8.6-2) ...
Setting up systemd (215-6) ...
Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ...
Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.machine1.conf ...
Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.systemd1.conf ...
Installing new version of config file /etc/systemd/bootchart.conf ...
Installing new version of config file /etc/systemd/journald.conf ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version of config file /etc/systemd/user.conf ...
Created symlink from /etc/systemd/system/getty.target.wants/getty@tty1.service to /lib/systemd/system/getty@.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/remote-fs.target to /lib/systemd/system/remote-fs.target.
Processing triggers for dbus (1.8.6-2) ...
(Reading database ... 164486 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_215-6_amd64.deb ...
Unpacking systemd-sysv (215-6) over (208-8) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up systemd-sysv (215-6) ...
(Reading database ... 164486 files and directories currently installed.)
Preparing to unpack .../printer-driver-foo2zjs-common_20140925dfsg0-3_all.deb ...
Unpacking printer-driver-foo2zjs-common (20140925dfsg0-3) over (20140519dfsg0-2) ...
Preparing to unpack .../libnetpbm10_2%3a10.0-15.2_amd64.deb ...
Unpacking libnetpbm10 (2:10.0-15.2) over (2:10.0-15+b3) ...
Preparing to unpack .../netpbm_2%3a10.0-15.2_amd64.deb ...
Unpacking netpbm (2:10.0-15.2) over (2:10.0-15+b3) ...
Preparing to unpack .../dcraw_9.21-0.2+b2_amd64.deb ...
Unpacking dcraw (9.21-0.2+b2) over (9.21-0.2+b1) ...
Processing triggers for cups (1.7.5-1) ...
Updating PPD files for foo2zjs-common ...
Updating PPD files for gutenprint ...
Processing triggers for mime-support (3.56) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
dpkg: libjpeg62:i386: dependency problems, but removing anyway as you requested:
 libgphoto2-6:i386 depends on libjpeg62 (>= 1:1.3.1).

(Reading database ... 164484 files and directories currently installed.)
Removing libjpeg62:i386 (1:1.3.1-3) ...
dpkg: libjpeg62:amd64: dependency problems, but removing anyway as you requested:
 libgphoto2-6:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libvncclient0:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libopenraw1:amd64 depends on libjpeg62 (>= 1:1.3.1); however:
  Package libjpeg62:amd64 is to be removed.
 libmng1:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libjpeg-turbo-progs depends on libjpeg62 (>= 1:1.3.1).
 libsdl-image1.2:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libpano13-3:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libgdk-pixbuf2.0-0:amd64 depends on libjpeg62 (>= 1:1.3.1).
 libffmpegthumbnailer4 depends on libjpeg62 (>= 1:1.3.1); however:
  Package libjpeg62:amd64 is to be removed.
 libspandsp2:amd64 depends on libjpeg62 (>= 1:1.3.1).

Removing libjpeg62:amd64 (1:1.3.1-3) ...
Processing triggers for libc-bin (2.19-13) ...
Selecting previously unselected package libjpeg62-turbo:i386.
(Reading database ... 164476 files and directories currently installed.)
Preparing to unpack .../libjpeg62-turbo_1%3a1.3.1-10_i386.deb ...
Unpacking libjpeg62-turbo:i386 (1:1.3.1-10) ...
Preparing to unpack .../libgphoto2-6_2.5.4-1.1+b2_i386.deb ...
De-configuring libgphoto2-6:amd64 (2.5.4-1.1+b1) ...
Unpacking libgphoto2-6:i386 (2.5.4-1.1+b2) over (2.5.4-1.1+b1) ...
Preparing to unpack .../libgphoto2-6_2.5.4-1.1+b2_amd64.deb ...
Unpacking libgphoto2-6:amd64 (2.5.4-1.1+b2) over (2.5.4-1.1+b1) ...
Preparing to unpack .../libvncclient0_0.9.9+dfsg-6+b2_amd64.deb ...
Unpacking libvncclient0:amd64 (0.9.9+dfsg-6+b2) over (0.9.9+dfsg-6+b1) ...
Preparing to unpack .../libopenraw1_0.0.9-3.5+b2_amd64.deb ...
Unpacking libopenraw1:amd64 (0.0.9-3.5+b2) over (0.0.9-3.5+b1) ...
Preparing to unpack .../libmng1_1.0.10+dfsg-3.1+b2_amd64.deb ...
Unpacking libmng1:amd64 (1.0.10+dfsg-3.1+b2) over (1.0.10+dfsg-3.1+b1) ...
Selecting previously unselected package libjpeg9:amd64.
Preparing to unpack .../libjpeg9_1%3a9a-2_amd64.deb ...
Unpacking libjpeg9:amd64 (1:9a-2) ...
Preparing to unpack .../libjpeg-progs_1%3a9a-2_amd64.deb ...
Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ...
dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3
Processing triggers for udev (208-8) ...
Processing triggers for libc-bin (2.19-13) ...
Processing triggers for man-db (2.6.7.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ravenlx@solydk-test ~ $ sudo apt-get dist-upgrade
[sudo] password for ravenlx: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 dcraw : Depends: libjpeg62-turbo (>= 1:1.3.1) but it is not installed
 libffmpegthumbnailer4 : Depends: libjpeg62 (>= 1:1.3.1)
 libgdk-pixbuf2.0-0 : Depends: libjpeg62 (>= 1:1.3.1)
 libgphoto2-6 : Depends: libjpeg62-turbo (>= 1:1.3.1) but it is not installed
 libjpeg-turbo-progs : Depends: libjpeg62 (>= 1:1.3.1)
 libmng1 : Depends: libjpeg62-turbo (>= 1:1.3.1) but it is not installed
 libopenraw1 : Depends: libjpeg62-turbo (>= 1:1.3.1) but it is not installed
 libpano13-3 : Depends: libjpeg62 (>= 1:1.3.1)
 libsdl-image1.2 : Depends: libjpeg62 (>= 1:1.3.1)
 libspandsp2 : Depends: libjpeg62 (>= 1:1.3.1)
 libvncclient0 : Depends: libjpeg62-turbo (>= 1:1.3.1) but it is not installed
 netpbm : Depends: libjpeg62-turbo (>= 1.3.1) but it is not installed
E: Unmet dependencies. Try using -f.
ravenlx@solydk-test ~ $ 

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Arjen Balfoort » 01 Dec 2014 18:19

Yes, you will get in trouble if you try to create an ISO with the new sources.list while the host isn't updated.

Follow this to upgrade the VM: http://forums.solydxk.nl/viewtopic.php?f=33&t=5095
The OP of this topic describes the same steps but less detailed.

When you're done, backup the .vdi file just to be sure.


SolydXK needs you!
Development | Testing | Translations

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 01 Dec 2014 18:23

Thanks, Schoelje. I will do that. I always work with a clone anyway. So I'll create this as an "updated SolydK" VM and back this one up then clone it to make an ISO creating VM.

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 01 Dec 2014 21:25

Couldn't do the upgrade. Same problem. I posted my results in the HE to Jessie upgrade thread (I was upgrading SolydK64 in a VM).

User avatar
patzy
Posts: 408
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby patzy » 02 Dec 2014 04:19

Schoelje wrote:I have re-written the OP: http://forums.solydxk.nl/viewtopic.php?f=9&t=774
and replaced the solydxk-constructor help (which can be read from the solydxk-constructor window) with a build example of SolydK32......

I've uploaded the resulting ISO here: http://downloads.solydxk.nl/dev
I downloaded the ISO and burned it to DVD. It boots!!! :ugeek:

Problems: First boot got crazy graphics.
Second boot with no Plymouth got completely black screen
Third boot with "nomodeset" was successful. - I guess if I install I shall have to use the DDM.
Schoelje wrote:Who can make the SolydX32 ISO? ;)
Hmmmmm

Thank you for a bootable 32bit K ISO :D

User avatar
patzy
Posts: 408
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby patzy » 02 Dec 2014 06:57

So I had a go with the Nov SolydX 32bit ISO. I followed Raven's guide. Updated everything before constructing the ISO.
Burned it to disk and got the same result as my last effort to boot SolydX. It looked at the DVD and decided to boot from the HD! :(
I also tried just taking the ISO apart and remaking it with the updated constructor without upgrading and had the same result. It will only boot from the HD. :cry:

Still, I do now have a bootable SolydK 32, even though I have do do it with nomodeset.

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 02 Dec 2014 13:06

I think Schoelje's tutorial in the OP is the one to use. I'm going to give it a try today after I can successfully upgrade a SolydK64 Virtual Machine to Jessie.

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 03 Dec 2014 04:42

This is in reference to SolydK32 bit ISO made from 2014-11 SolydK32-bit ISO. This was all done in a dedicated VirtualBox virtual machine.

Success! But not without a couple bumps in the road.

Preinstallation of packages:

Code: Select all

E: Unable to locate package libjpeg62-turbo
E: Unable to locate package solydxk-mozilla-evolvere-icon-theme
I just ignored them and continued on.

font.pf2 is not in /boot/grub (which is actually /boot/boot/grub)

/boot/offline contained these which is different from the OP (when I read the OP - it may be updated by the time someone else reads this) :

Code: Select all

efibootmgr_0.7.0-2_i386.deb
grub-efi-ia32-bin_2.00-22_i386.deb
grub-efi-ia32_2.00-22_i386.deb
grub-efi_2.00-22_i386.deb
libefivar0_0.10-5_i386.deb
Overall, it took approximately 50 minutes from starting of mksquashfs to completion of the entire process.

nonEFI Test: All OK (live boot, installation and boot of OS without Live CD).

EFI Test:

To set up VirtualBox to work like an EFI-enabled boot, Right click on the new machine after you have created it but before you actually boot it the very first time (before booting the live CD that is). Select Settings (or select the machine and click the Settings icon at the top).

Click on System on the left, then Motherboard tab on the right. Click in the checkbox to enable EFI (special OSes only).

NOTE: While booting the live CD, some error with "FWS" or something like that briefly flashed on the screen but it did boot ok.

Install SolydK and then shut down the virtual machine. Go into Settings / Storage and remove the LiveCD device. Restart the machine.

This is what you'll see:
EFIBootVB_ravenlx.png
EFIBootVB_ravenlx.png (4.18 KiB) Viewed 8070 times
This is what you'll find if you restart the machine after shutting it down. At the bottom I have steps for setting it up to boot every time into SolydK but it only works if you're restarting. For some reason the changes don't stick between machine shutdowns so you have to do the following each time to boot it. (PITA!)

Type exit and press Enter.

1. Select Boot Maintenance Manager and press Enter.
2. Boot From File
3. Press Enter on large bit of text that is already selected.
4. Press Enter on <EFI>.
5. Select <solydk> and press Enter.
6. select boot.efi and press Enter.

Here's what I think you normally would do to make it permanent but like I said, no matter what I do, the settings do not stick between machine shutdowns (ie. poweroff/shutdown the virtual machine, restart it and you get that shell above again).

Boot Maintenance Manager
Boot Options
Add Boot Option
Press Enter on already selected item (large bit of text)
Press Enter on already selected <EFI>
Select <solydk> and press Enter
Select boot.efi and press Enter
Input Description: Press Enter and type: SolydK
Commit Changes and Exit
Boot Options
Set Boot Next Value
Click selected item to right of Boot Next Value
Select SolydK and press Enter
Commit Changes and Exit
Boot Options
Change Boot Order
Press Enter on already selected list.
Select SolydK and press + until it's under EFI DVD/CDROM and above EFI Hard Drive.
Press Enter
Commit Changes and Exit
Go Back To Main Page
Press ESC
Boot Manager
Select SolydK and press Enter

Hope this helps! But I am able to make both a plain and EFI SolydK ISO.

Another thing to note is that while I did do a dist-upgrade in the chrooted terminal before building the ISOs, when I install the OS from the LiveCD and then remove the LiveCD and boot the freshly installed OS, Update manager updates the system and there are packages that need updating (which I assumed shouldn't be the case since I just dist-updated the system prior to making the ISO).

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 03 Dec 2014 04:45

@patzy: Would you be willing to give this a try? If so, let me know and I will somehow try to get my ISO to you to try and make a DVD from and try to boot it and maybe even try to install it on a test (not virtual) machine (if you have one)?

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Arjen Balfoort » 03 Dec 2014 06:37

Did you check the sources.list in both the host as the guest and did you run "apt update" afterwards?
solydxk-mozilla-evolvere-icon-theme is part of the repository.solydxk.nl repository and libjpeg62-turbo is in Debian testing.

You can find all needed boot files, including font.pf2, in the OP's attachment.

The offline packages list seems the same as mentioned in the OP. Only the order is different.

I too was never able to boot EFI in VB, but never had a problem when installed on metal.

I guess that the upgrade after install was caused by an incomplete upgrade prior to building the ISO.
Before building I always check in a chrooted terminal with:

Code: Select all

apt-get -f install


SolydXK needs you!
Development | Testing | Translations

User avatar
grizzler
Posts: 2170
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby grizzler » 03 Dec 2014 07:06

Getting updates after building the ISO could also be coincidental. Debian Testing is still a moving target. At least once a day (could be around 00:00 UTC - I don't know) packages are migrating from Unstable. If your dist-upgrade was just before that...
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
patzy
Posts: 408
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby patzy » 03 Dec 2014 08:51

RavenLX wrote:@patzy: Would you be willing to give this a try? If so, let me know and I will somehow try to get my ISO to you to try and make a DVD from and try to boot it and maybe even try to install it on a test (not virtual) machine (if you have one)?
Sure I'll give it a roll. If it boots I'll install it on my test machine and see how it goes. How about using Dropbox?

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 03 Dec 2014 14:00

I've just been given access to a spot on solydxk to upload. Please watch this link:

http://downloads.solydxk.nl/ce/testing/

for:

solydk32_20141202.iso

It will take a long time to upload though (several hours) for such a large file and then it will be picked up on an hourly scan to go live. So please check back later today for the file. I'm uploading it right now.

Update: I've edited the filename so that it doesn't conflict with the one Schoelje has already up there. Note the '02' at the end of the iso name. Due to having a very slow (all I can afford to have) internet connection, my uploads take 4 hours. :(

Deleted User 2764

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Deleted User 2764 » 03 Dec 2014 21:21

File is now online and ready for testing!

User avatar
grizzler
Posts: 2170
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby grizzler » 22 Dec 2014 13:59

RavenLX wrote:Here's what I think you normally would do to make it permanent but like I said, no matter what I do, the settings do not stick between machine shutdowns (ie. poweroff/shutdown the virtual machine, restart it and you get that shell above again).
That appears to be a known issue: https://forums.virtualbox.org/viewtopic ... 70#p289297

I created my startup.nsh following that 'instruction' and it works. You still go through the UEFI shell screen, but after 5 seconds (or immediately if you press any key - other than Escape, that is...) the GRUB menu comes up.

Oh, and if you think of creating that startup.nsh file using a simple text editor inside the running SolydXK install (it shows up in /boot/efi) think again. It seems to be an UTF-16 textfile, i.e. every character is 16 bits wide and it has a BOM.

Edit
Actually, forget about that last bit. A plain textfile works just as well... :roll:

I've noticed a lot of grub weirdness after installing SolydX64_201412 in an efi VM, but I intend to create a separate thread about that.
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
escolar
Posts: 133
Joined: 23 Aug 2013 08:14
Location: Spain

Solydxk-constructor removes my debs

Postby escolar » 08 Jan 2015 18:00

I have not used Solydxk contructor since May, and now I have to build a customized iso and it doesn't work as it did.

I install two debs since the constructor terminal (two gambas applicatios I have done) without problem, but when I go to build the iso it opens a new terminal and remove my two installed apps. So I have not my apps when I run the iso.

Thanks

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Arjen Balfoort » 08 Jan 2015 18:05

That is far too little information to say something useful.
What ISO version, did you dist-upgrade first, what packages did you install, what was the terminal output?


SolydXK needs you!
Development | Testing | Translations

User avatar
escolar
Posts: 133
Joined: 23 Aug 2013 08:14
Location: Spain

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby escolar » 08 Jan 2015 19:32

Schoelje wrote:That is far too little information to say something useful.
What ISO version, did you dist-upgrade first, what packages did you install, what was the terminal output?
I use the Solydx32-201411 iso as basis.

From the Constructor terminal I do a apt-get update and remove some apps I don't need. Then I install two debs packages which I have made with Gambas, so they aren't downloaded from any repository. I Install them with dpkg -i and the process finishes ok. But then, when I go to build the Iso a new terminal windows is openned automatically, and it seems to do some update or upgrade, and in some kind of apt-get process say that my two installed applications will be removed, and it do it.

I don't know how to capture the log of this building terminal.

I hope you undertand my explanation.

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Remastering SolydXK [rewritten: 01 Dec 2014]

Postby Arjen Balfoort » 09 Jan 2015 08:40

First I recommend to use the testing ISOs that were built by the community.
These are fairly recent and are already pointing to Debian Jessie: http://downloads.solydxk.nl/ce/testing/
Do a full dist-upgrade before you change or install anything.

I can't say much about those custom packages, or if they were built according to Debian specs.
Before you build an ISO, a cleanup script is executed: /usr/lib/solydxk/constructor/cleanup.sh
This script probably recognizes those scripts as unneeded/unreferenced.

You can hack the cleanup script (even empty it, but it must stay there or else the constructor won't be happy) if you want a quick fix.


SolydXK needs you!
Development | Testing | Translations


Return to “Tutorials”

Who is online

Users browsing this forum: No registered users and 1 guest