Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Pocock here is the output you asked me, I hope it is well readable ...
22
Operating Systems and Porting / Re: Slackware64-Current
« Last post by bw42 on January 05, 2021, 08:48:16 am »
Running a slackpkg install-new should also list things that aren't installed.


As a heads up if you use sbopkg or download slackbuilds, you might want to add a ppc64le section to the $ARCH portion of the .SlackBuild file.
Without adding it the scripts tend to try installing libraries in the /usr/lib and /lib folders instead of /lib64 and /usr/lib64

Usually just adding something like the below right before the else section works to make it work like Slackware64.

elif [ "$ARCH" = "ppc64le" ]; then
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX="64"
23
Operating Systems and Porting / Re: Slackware64-Current
« Last post by Logout on January 05, 2021, 08:32:32 am »
Wonderful! So the fastest and most convenient way to check for missing libraries will for me be downloading new ISO and reinstalling, since I didn't do much in the fresh install yesterday. Again, thanks for all the slacks!
24
Operating Systems and Porting / Re: Slackware64-Current
« Last post by bw42 on January 05, 2021, 08:13:13 am »
It looks like when I updated the mirror structure a couple months ago to add the extras mirror I forgot to update my makeiso script for the new folder name.
So it was building the .iso file off an old copy of the current folder that was missing the libXaw and libXmu packages.
Its been corrected and should properly match the riscyslack64-current folder.

Thank you again for letting me know.
25
Operating Systems and Porting / Re: Slackware64-Current
« Last post by Logout on January 05, 2021, 08:00:06 am »
The iso was from January 4th, I still have it somewhere on my drive if needed for examination.
26
Operating Systems and Porting / Re: Slackware64-Current
« Last post by bw42 on January 05, 2021, 07:55:41 am »
I'm not sure why they are missing, the .iso is generated each morning automatically form the contents of the mirror.

I'll see if I can find out why they weren't there.
Thanks for letting me know.
27

For the firmware, can you please show me the output confirming which firmware you already have?

For using the kernel on Fedora: this is not what I would regard as a supported installation, it is a hack.  What you can try to do:

a) unpack the 5.9 Debian kernel package in a temporary location (use dpkg -X)

b) repack it into a tar file

c) copy the tar file into a Fedora system

d) untar the file in Fedora

e) manually copy the files into the correct places on Fedora, for example, copy the vmlinux and initrd file to /boot and copy the modules to /lib/modules, be careful not to overwrite any other files in those places or Fedora may not boot again

f) on the next boot, in petitboot, manually edit the petitboot settings to use the vmlinux and initrd file

This is unsupported from either Debian or Fedora but it may let you test.  In the Fedora environment, everything else will be much newer than in Debian, you will already have newer mesa, newer Xorg, newer firmware, maybe the RX 5700 will work.

Fedora's wiki provides instructions for building the kernel as an RPM, this might be a better way to proceed.  It is not very difficult.  The only thing you need to change in the official package is this one line:

Code: [Select]
CONFIG_PPC_64K_PAGES=n

According to search results people did get the RX 5700 working on Debian buster on x86 / 4k.  One of them mentions firmware.  You can try to download and install the firmware update like this:

Code: [Select]
sudo apt update
sudo apt install -t buster-backports firmware-linux-nonfree
28
Pocock, while verifying the firmware installed on Debian, I wanted to understand if to try the Kernel 5.9 4K that you compiled on Fedora, you can perform the exact same procedure that is used for Debian ... What can you tell me about it?
29
Operating Systems and Porting / Re: Slackware64-Current
« Last post by Logout on January 05, 2021, 03:08:24 am »
Finally managed to get decent 1TB NVMe instead of my ancient 64 GB SATA SSD and therefor I tried my favorite distro, which in fact I use on all my other (x86, x64 and ARM) computers. Everything was smooth, no surprise during the install, Riscy Slackware boots on my 8C Blackbird like a marvel ...

... but then one surprise emerged: It seems that the content of http://mirror.riscyslack.org/RiscySlack/riscyslack64-current/slackware64/ is not the same what is on the current install ISO. To be precise some quite important libraries are missing on the ISO, like libXaw or libXMu, so I couldn't even start xterm. No big deal - downloading txz packages from mirror and installing them manually fixed this. But now I have to find out what else didn't install.

Is there any reason for this?

(Anyway: thanks for bringing my native distro to my native platform!)
30

Wayland: yes, Debian enables it by default.  If you remove the '#' in the config, that disables it

For the firmware, for an RX 5700, I think that you want to make sure it is a 2020 firmware package.  If you have the 2019 firmware package that may not be OK.

For Big Navi, RX 6800 / RX 6900, the 2020 firmware package may not be sufficient, it may require the next firmware package or a manual installation of the firmware from Git.
Pages: 1 2 [3] 4 5 ... 10