Test the upcomming siduction release

[towo]

Hello,

for all who wants to help us, bringing our next siduction release to the daylight, you find the lastest testbuilds on
https://testbuilds.siduction.site. Test thos builds if you want and give us feadback.

[vilde]

tried to install xfce version on an old T420, failed installation

edited: I tried one more time but let the installer be in English, the same thing happen, the same message at fail.

System:
  Host: siduction Kernel: 5.12.12-1-siduction-amd64 x86_64 bits: 64
  compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
  Distro: siduction 21.1.99 Farewell - xfce - (202106191433)
  base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: LENOVO product: 4180G73 v: ThinkPad T420
  serial: <superuser required>
  Mobo: LENOVO model: 4180G73 serial: <superuser required> UEFI: LENOVO
  v: 83ET82WW (1.52 ) date: 06/04/2018
Battery:
  ID-1: BAT0 charge: 0 Wh condition: N/A model: N/A status: Unknown
CPU:
  Info: Dual Core model: Intel Core i5-2540M bits: 64 type: MT MCP
  arch: Sandy Bridge rev: 7 L2 cache: 3 MiB
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20731
  Speed: 931 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 931 2: 1130
  3: 2251 4: 886
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
  vendor: Lenovo ThinkPad T420 driver: i915 v: kernel bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting
  unloaded: fbdev,vesa resolution: 1600x900~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2)
  v: 3.3 Mesa 21.1.3 direct render: Yes
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Lenovo ThinkPad T520
  driver: e1000e v: kernel port: 5080 bus ID: 00:19.0
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: 00:21:cc:ba:0c:ec
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
  v: kernel port: efa0 bus ID: 03:00.0
  IF: wlan0 state: down mac: 10:0b:a9:97:57:10
  IF-ID-1: wwx028037ec0200 state: down mac: 02:80:37:ec:02:00
Drives:
  Local Storage: total: 96.9 GiB used: 6.35 GiB (6.6%)
Info:
  Processes: 200 Uptime: 19m Memory: 3.72 GiB used: 1.03 GiB (27.6%)
  Init: systemd runlevel: 5 Compilers: gcc: 10.2.1 Packages: 2091
  Shell: Bash v: 5.1.8 inxi: 3.3.01

[towo]

For now you can fix that yourself, delete line 49 in /etc/apt/sources.list.d/fixes.list which contains

Code: [Select]

" echo ".
That is wrong i fix that at the moment, i write that post.

[Mister00X]

I installed in qemu in uefi mode as I'm currently lacking bare metal to test on.

Everything seems to work fine when using the standard mode (delete hard drive and install). I will try a more sophisticated setup with logical volumes tomorrow.

Mister00X

[vilde]

Just for testing/helping I installed the builds listed here under, both with Swedish keyboard and language during installation. Did the wipe-and-use-whole-hd version and this time all went very well. Test machine was the same old T420 as in my post from yesterday.

[img alt=[DIR]]https://testbuilds.siduction.site/icons/folder.gifxfce/

2021-06-19 23:00 

and

[img alt=[DIR]]https://testbuilds.siduction.site/icons/folder.gifkde/

2021-06-19 21:50

[sunrat]

I haven't tried it yet but the md5 file for the KDE version is wrong. It lists siduction-21.1.99-farewell-kde-amd64-202106191935.iso whereas the downloaded file name is siduction-farewell-kde-amd64-latest.iso
Once corrected the md5sum checks out OK.

Edit, next day: Booted the iso in KVM/QEMU and opened a few programs. All good!

[toga]

siduction-farewell-kde-amd64-latest.iso

After installation, the keyboard language is set to "us", although "de" was previously selected before booting

Otherwise everything went fine! :-)

[Mister00X]

I have installed the KDE iso again in qemu again in uefi mode. This time I tried to install on logical volumes using the calamares installer.

Out of 7 tries it succeeded once. The workaround of tricking calamares into installing on logical volumes by having KDE's partitionmanager open worked once but the fstab was not set up correctly and something with the efi partition seemed to be borked too because the system would not boot.
I have tried installing the same setup using a manjaro iso (which also uses calamares) and after some excessive googling I found that a bug in calamares itself is the cause of this issue.

Therefore I tried classical manual partitioning too. Using this disk layout

Code: [Select]

$ lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0     11:0    1 1024M  0 rom
vda    252:0    0   30G  0 disk
├─vda1 252:1    0  500M  0 part /boot/efi
├─vda2 252:2    0   25G  0 part /
└─vda3 252:3    0  4,5G  0 part /disks/data

It worked like a charm   

[DeepDayze]

@Mister00X I usually do my own partitioning (or formatting) prior to installing any distro as can't always trust the builtin partitioners within the installer to actually work. In addition you can have fuller control over how your partitions are set up if you set them up first before installing. You can also set the EFI partition's desired size as well (if using UEFI), but I find that even with Windows' default EFI size of 100MB usually works well if you plan to have just 2 OS's installed in dual boot (Windows and Linux).

[vinzv]

I have tried installing the same setup using a manjaro iso (which also uses calamares) and after some excessive googling I found that a bug in calamares itself is the cause of this issue.

Do you still have the bug report at hands? Maybe it can be solved somehow.

[Mister00X]

@vinzv

I believe it to be this bug https://github.com/calamares/calamares/issues/1564 as calamares mounts its install target to /tmp/calamares and I observed running out of RAM when trying to install on LV's and I belive it's because /tmp/calamares was no longer a mounted file system but a ordinary directory at that point.

EDIT: I want to add when I talk about running out of memory, I am also talking about konsole (where the output of calamares -d was displayed) and other parts of plasma getting OOM-killed on a VM with 7.8 GiB RAM, which I believe should not happen.

[Mister00X]

So I installed again in qemu in uefi mode this time using the KDE image, the cli-installer and (again) logical volumes.

Here are some remarks:

• The cli-installer seems to be unable to install in uefi mode. Which means one has to chroot into the installed system and make changes to the fstab, (re)install grub and update the initramfs. Btw what does a default entry for the efi partiton look like? I found multiple different entries for it online.
• The installer has no options for mounting file systems at custom mount points. (This is not a huge problem because one has to make changes to /etc/fstab anyway. See above.)
• The cli-installer does not remove the calamares installer.

Apart from this the install was way less painfull than trying to trick calamares into installing on logical volumes and I imagine everyone wanting to install on LVs be proficient enough with linux to be able to chroot and fix those minor issues.

[yunanideniz]

Hello,

for all who wants to help us, bringing our next siduction release to the daylight, you find the lastest testbuilds on
https://testbuilds.siduction.site. Test thos builds if you want and give us feadback.


I have installed  Mate Farewell on old Hp... run and  work..fine...   now i will test.. and give reports.

[yunanideniz]

Hello,

for all who wants to help us, bringing our next siduction release to the daylight, you find the lastest testbuilds on
https://testbuilds.siduction.site. Test thos builds if you want and give us feadback.

Siduction Farewell Mate ... Work fine in these Computer HP Pavilion

CPU Intel Core (TM) 2 DUO - T7300  2.00Ghz
Ram  2029688 Kib
Nvidia G86MGeForce 8400 Gs    1280x800

I will give reports in next times

[unklarer]

Mein Bericht.

Nach sonnigen Urlaub    bin ich heute dazu gekommen diese ISO zu installieren:

Code: [Select]

inxi -SMa
System:    Host: T500 Kernel: 5.12.17-1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.12.17-1-siduction-amd64
root=UUID=801f4917-5f88-4f5e-9399-785cb8384e2c ro quiet systemd.show_status=1
Desktop: LXDE 0.10.1 info: lxpanel, plank wm: Openbox 3.6.1 dm: SDDM
Distro: siduction 21.1.99 Farewell - lxde - (202106192004) base: Debian GNU/Linux 11 (bullseye)
Machine:   Type: Laptop System: LENOVO product: 20564QG v: ThinkPad T500 serial: <superuser required> Chassis:type: 10 serial: <superuser required>
Mobo: LENOVO model: 20564QG serial: <superuser required> BIOS: LENOVO v: 6FET83WW (3.13 )
date: 03/15/2010 dieser Code wird pro Zeile formatiert/ausgegeben. Handarbeit war angesagt, was läuft da im neuen Forum falsch?


Die Installation dauerte 15 Minuten.
Calamares arbeitete einwandfrei.
Installiert wurde "über" eine MX19-FVWM-DesktopInstallation, ohne extra /home, in ein Multibootsystem mit bunsenlabs-openbox, antiX19-fluxbox und archlinux-fluxbox. Der Bootloader Grub wurde in / installiert.
Entsprechende Änderungen an den Dateien default-grub, 30_os-prober und 40_custom - ohne Probleme.

Bereits in der live-ISO als auch jetzt in der Installation kam/kommt das gesamte Netzwerk mit LAN; Wlan und Bluetooth zum Einsatz. Entsprechende Umschaltungen oder Aufwachen, funktionieren einwandfrei.

Überptüft hatte ich
-die fstab
-die sources.list (extra und fixes)
eingestellt war der italienische Mirror garr.it, was ich auf die in Germany geändert habe.

Erstes dist-upgrade spielte 96 Pakete ein, darunter der 5.12.17'er Kernel. Autoremove arbeitete korrekt, indem der "ausgelieferte" Kernel 5.12.12 an Bord blieb.

Teilweise eingerichtet ist das System bereits mit Anwendungen, die mir wichtig sind (geany; keepassxc)
Die Leiste wurde von unten waagerecht nach links senkrecht geändert...