16
Operating Systems and Porting / Re: Slackware64-Current
« on: July 12, 2020, 02:36:05 pm »
He marked one of my posts in the thread on Linux Questions helpful, so I assume that means he's aware.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
Operating Systems and Porting / Re: Slackware64-Current
« on: July 12, 2020, 11:38:05 am »
I updated a lot of packages to bring it closer to sync with Slackware64-current.
But of course Mr. Volkerding released new updates well I was doing that.
So its closer, but a moving target.
I managed to get Krita working with the new version of QT5.
Also, managed to figure out enough patches to get QT4 to build, so that exists now.
Its more usable, yay!
But of course Mr. Volkerding released new updates well I was doing that.
So its closer, but a moving target.
I managed to get Krita working with the new version of QT5.
Also, managed to figure out enough patches to get QT4 to build, so that exists now.
Its more usable, yay!
18
Operating Systems and Porting / Re: Slackware64-Current
« on: July 02, 2020, 12:01:04 pm »
Oh yeah, Slackpkg is patched to support ppc64le for my mirror.
19
Operating Systems and Porting / Re: Slackware64-Current
« on: July 02, 2020, 09:16:35 am »
Playing with it this morning I found that the Konqueror browser works with QTWebEngine, but crashes when set to use QTWebKit or KHTML.
Looks like a QT4 DBus lib is missing.
Working on rebuilding to see if I can get it working.
Krita still just hangs on loading :/
Looks like a QT4 DBus lib is missing.
Working on rebuilding to see if I can get it working.
Krita still just hangs on loading :/
20
Operating Systems and Porting / Re: Slackware64-Current
« on: July 01, 2020, 11:22:22 pm »
I've updated the mirror a bit with new packages and fixes, and almost always remembered to put something in the Changelog.txt, almost.
There is now an .iso file on the mirror.
https://mirror.riscyslack.org/RiscySlack/current-iso/
I tested it by mounting it as a virtual drive in the OpenBMC console.
Petitboot detected it and allows it to boot.
After that you can fdisk or cfdisk your drives and run Setup like a normal Slackware setup.
You'll have to ignore the MBR error and tell it not to install Lilo.
I haven't modified the Setup script to remove that yet.
After installing you'll need to exit back to bash and chroot /mnt
then run grub-mkconfig -o /boot/grub/grub.cfg
After rebooting Petitboot should detect the install and automatically load it.
If you use the NIC that's shared with the BMC you'll want to edit /etc/rc.d/rc.inet1.conf to set eth2 USE_DHCP[2]="yes"
I've also noticed the gpu doesn't always reinitialize on my Radeon RX580 after reboot.
When that happens I end up having to shutdown, then boot back up.
There is now an .iso file on the mirror.
https://mirror.riscyslack.org/RiscySlack/current-iso/
I tested it by mounting it as a virtual drive in the OpenBMC console.
Petitboot detected it and allows it to boot.
After that you can fdisk or cfdisk your drives and run Setup like a normal Slackware setup.
You'll have to ignore the MBR error and tell it not to install Lilo.
I haven't modified the Setup script to remove that yet.
After installing you'll need to exit back to bash and chroot /mnt
then run grub-mkconfig -o /boot/grub/grub.cfg
After rebooting Petitboot should detect the install and automatically load it.
If you use the NIC that's shared with the BMC you'll want to edit /etc/rc.d/rc.inet1.conf to set eth2 USE_DHCP[2]="yes"
I've also noticed the gpu doesn't always reinitialize on my Radeon RX580 after reboot.
When that happens I end up having to shutdown, then boot back up.
21
Operating Systems and Porting / Re: Any Linux Desktop for X86 run on Talos/Raptor?
« on: June 30, 2020, 10:57:42 am »
If its 32-bit I would think you would use the qemu-i386 command.
You can specify which 32-bit x86 cpu to emulate by using the -cpu flag.
Running qemu-i386 -cpu help will show you all the cpu options.
You can specify which 32-bit x86 cpu to emulate by using the -cpu flag.
Running qemu-i386 -cpu help will show you all the cpu options.
22
Operating Systems and Porting / Re: Slackware64-Current
« on: June 29, 2020, 08:22:53 pm »
I managed to get an initrd containing the Slackware Setup scripts to boot!
A big step closer to having a proper installable version.
A big step closer to having a proper installable version.
23
Operating Systems and Porting / Re: Any Linux Desktop for X86 run on Talos/Raptor?
« on: June 29, 2020, 02:38:44 pm »
The -smp flag is usually how its done.
-smp 4
Like that would tell it to use 4 vCPU.
-smp 4
Like that would tell it to use 4 vCPU.
24
Operating Systems and Porting / Re: Any Linux Desktop for X86 run on Talos/Raptor?
« on: June 28, 2020, 10:30:23 pm »
I don't think you'd have to install it each time.
Qemu would just translate from x86 to power. So you should be able to install the software and then use Qemu to run it when you need it.
Qemu would just translate from x86 to power. So you should be able to install the software and then use Qemu to run it when you need it.
25
Operating Systems and Porting / Re: Any Linux Desktop for X86 run on Talos/Raptor?
« on: June 27, 2020, 08:29:07 pm »
Outside of running a full VM you could try Qemu user mode emulation.
Here's a couple links that discuss how it works.
It'd allow x86 code to run on power without full VM emulation.
https://www.qemu.org/docs/master/user/main.html
https://ownyourbits.com/2018/06/13/transparently-running-binaries-from-any-architecture-in-linux-with-qemu-and-binfmt_misc/
Here's a couple links that discuss how it works.
It'd allow x86 code to run on power without full VM emulation.
https://www.qemu.org/docs/master/user/main.html
https://ownyourbits.com/2018/06/13/transparently-running-binaries-from-any-architecture-in-linux-with-qemu-and-binfmt_misc/
26
Operating Systems and Porting / Re: Any Linux Desktop for X86 run on Talos/Raptor?
« on: June 26, 2020, 02:54:01 pm »
What kind of application are you trying to run?
What settings are you using when running it?
I usually use Qemu for my VMs.
I setup a Qemu VM that I'm installing Slackware64 in right now.
Its running, though a little slower than it would with KVM acceleration.
What settings are you using when running it?
I usually use Qemu for my VMs.
I setup a Qemu VM that I'm installing Slackware64 in right now.
Its running, though a little slower than it would with KVM acceleration.
27
Operating Systems and Porting / Re: Slackware64-Current
« on: June 26, 2020, 09:49:23 am »
The initial packages and source files have been uploaded to https://mirror.riscyslack.org
I started this from a snapshot of Slackware64-current, its been a little over a month, so its probably a little out of sync with the official version.
I also got tired of fighting with KDE 4 and just dumped it for Alien Bob's KTown 5.19, so a lot of out of sync.
There isn't an installer at the moment, but the packages can be extracted to a folder or drive, and with a couple tweaks, be made into a mostly functional Slackware install.
I put the tarballs with the files from Debian's grub powerpc packages under Other for now.
I just extracted them to root with tar xvf *.txz -C /
They also need libdevmapper.so linked to libdevmapper.so.1.02.1 for the Debian grub-mkconfig to work.
I had to create an /etc/fstab with the mount entries and then run grub-mkconfig -o /boot/grub/grub.cfg to be able to boot directly into.
In case anyone hasn't noticed, I call it Riscy Slack. One because its for PowerPC64LE which is a RISC architecture, and two because its an unofficial build, so use at your own risk.
I'm still working on reverse engineering the process Patrick uses to do all the package signing and stuff for making it look like a proper mirror usable with Slackpkg.
I started this from a snapshot of Slackware64-current, its been a little over a month, so its probably a little out of sync with the official version.
I also got tired of fighting with KDE 4 and just dumped it for Alien Bob's KTown 5.19, so a lot of out of sync.
There isn't an installer at the moment, but the packages can be extracted to a folder or drive, and with a couple tweaks, be made into a mostly functional Slackware install.
I put the tarballs with the files from Debian's grub powerpc packages under Other for now.
I just extracted them to root with tar xvf *.txz -C /
They also need libdevmapper.so linked to libdevmapper.so.1.02.1 for the Debian grub-mkconfig to work.
I had to create an /etc/fstab with the mount entries and then run grub-mkconfig -o /boot/grub/grub.cfg to be able to boot directly into.
In case anyone hasn't noticed, I call it Riscy Slack. One because its for PowerPC64LE which is a RISC architecture, and two because its an unofficial build, so use at your own risk.
I'm still working on reverse engineering the process Patrick uses to do all the package signing and stuff for making it look like a proper mirror usable with Slackpkg.
28
Operating Systems and Porting / Re: Slackware64-Current
« on: June 25, 2020, 03:25:16 pm »
Guess that means I should start using normal titles instead of random jokes about Star Trek and such.
29
Applications and Porting / Re: Red Dead Redemption 2 For Linux
« on: June 25, 2020, 02:09:48 pm »
If it runs on Linux natively on x86 someone could try running it on Power using something like Qemu to translate from x86 to Power.
Not sure if that'd work, but would be interesting to try.
Not sure if that'd work, but would be interesting to try.
30
Operating Systems and Porting / Re: Slackware64-Current
« on: June 25, 2020, 01:55:45 pm »
There isn't much useful information on my blog site at the moment, but I added an RSS feed.
https://www.riscyslack.org/?feed
It's mostly my ramblings of constantly almost having a useful build.
https://www.riscyslack.org/?feed
It's mostly my ramblings of constantly almost having a useful build.
