xeno74 wrote: ↑Fri Jun 28, 2019 7:55 am
Hi All,
I released a
new image of
openSUSE Tumbleweed 20190521 for the X5000 and X1000 today.
New:
- Renamed the libglamoregl.so to libglamoregl.so.bak for using openSUSE Tumbleweed 20190521-2 PPC64 with Radeon SI graphics cards
- The issue with "reboot" and "poweroff" has been fixed through configuring /etc/polkit-1/rules.d/90-default-privs.rules
- MATE desktop added (version 1.22.1)
- Mesa updated to version 19.0.5
- Samba AD-DC 4.10.2 added
Download:
openSUSE_Tumbleweed_20190521-2_ppc64.img.tar.gz (3.5GB)
md5sum for the tar.gz:
a81b03ef98f5e4bc11ffaa864b630028
md5sum for the uncompressed img:
9bf6cc871f6e7f793d06572c642fbf63
Users:
root (password "amigaone")
amigaone (password "amigaone")
I copied this img to a partition today.
Code: Select all
# dd if=openSUSE_Tumbleweed_20190521-2_ppc64.img of=/dev/sdb4
Output:
Code: Select all
32323584+0 records in
32323584+0 records out
16549675008 bytes (17 GB, 15 GiB) copied, 668.356 s, 24.8 MB/s
Then I checked the file system.
Output:
Code: Select all
e2fsck 1.46.4 (18-Aug-2021)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb4: 387640/1011840 files (0.5% non-contiguous), 2527259/4040448 blocks
After that I resized the file system to the whole partition size.
Output:
Code: Select all
resize2fs 1.46.4 (18-Aug-2021)
Resizing the filesystem on /dev/sdb4 to 10179328 (4k) blocks.
The filesystem on /dev/sdb4 is now 10179328 (4k) blocks long.
Afterwards I created a label for this partition.
Output:
Then I copied the kernel modules to this partition:
Code: Select all
# cp -R 6.6.0-rc1_A-EON_X1000_Nemo /lib/modules
After that I got a new package signing key and updated the package database.
The repo debug isn't available anymore. Please remove it with
zypper rr repo-debug.
After that execute
zypper refresh again.
Dist-upgrade:
It is not possible to dist-upgrade or install new packages because rpm is too old and cannot install new packages. Furthermore, it is not possible to upgrade rpm because it requires a new version of libc and this cannot be installed because rpm is too old.