Raptor Computing Systems Community Forums (BETA)
Software => Operating Systems and Porting => Topic started by: tle on August 14, 2021, 07:31:36 pm
-
For more details, check release notes:https://www.debian.org/releases/bullseye/ppc64el/release-notes/
-
I did a fresh install of Bullseye instead of updating my current 10.9.
As with other Debian flavors it is not really ready for prime time, but yes, it does install and run at least in the AST chip.
Some of the missing software that I use regularly has not reached the distro yet and will no doubt be along soon (ish).
For example, Midnight Commander and XFE. No hurry...10.9 is working fine.
-
When I bought my Talos II, I did a fresh install of buster
As mentioned elsewhere, I rebuilt my kernel for a 4k page size and created Btrfs filesystems with 4k
I recently made a dist-upgrade to bullseye, Debian 11. As part of the upgrade, I rebooted into the 4k kernel from buster so I could continue accessing my Btrfs filesystem
Then I built a 4k version of the 5.10 kernel package from bullseye. Rebooting into that and the system runs fine. I pushed my kernel here:
https://gitlab.com/dpocock/linux-kernel-debian/-/tree/pocock/bullseye-ppc64el-4k
After a week or so I had a crash, I'm not sure if that is the bullseye kernel or if it is just what I was doing at that moment in time. I've been doing some development with GStreamer and VAAPI for the AMD Radeon cards and that has also produced some crashes so I'm not sure if this is because of bullseye or the testing that I'm doing with the GPU.
GNOME appears to be slightly faster when switching workspaces compared to buster.
-
When I bought my Talos II, I did a fresh install of buster
As mentioned elsewhere, I rebuilt my kernel for a 4k page size and created Btrfs filesystems with 4k
I recently made a dist-upgrade to bullseye, Debian 11. As part of the upgrade, I rebooted into the 4k kernel from buster so I could continue accessing my Btrfs filesystem
Then I built a 4k version of the 5.10 kernel package from bullseye. Rebooting into that and the system runs fine. I pushed my kernel here:
https://gitlab.com/dpocock/linux-kernel-debian/-/tree/pocock/bullseye-ppc64el-4k
After a week or so I had a crash, I'm not sure if that is the bullseye kernel or if it is just what I was doing at that moment in time. I've been doing some development with GStreamer and VAAPI for the AMD Radeon cards and that has also produced some crashes so I'm not sure if this is because of bullseye or the testing that I'm doing with the GPU.
GNOME appears to be slightly faster when switching workspaces compared to buster.
Any kernel log when it crashes?
-
Hi everyone, I need to understand how to install firmware for AMD GPUs on Debian 11. I have done some tests by downloading and installing what should be the latest firmware but I have not solved the same. Can you give me the procedure to download and install the firmware you need in bullseye for the AMD gpu? Thanks
-
Eventually I managed to sort it out on my own. I saw a site where it reported to add for Bullseye, a repository line that is not there. After I put it on it allowed me to download the slightly newer firmware and that point the graphics card started. Instead I tested the new Kernel 5.15 but the problem of not starting with the GPU unfortunately remains a curse ...
-
I'm also experiencing boot issues with Bullsye that didn't previously occur with Buster. The problem apparently always goes back to starting with AMD GPUs. At the time of loading the Kernel, I am currently using version 5.12.8 compiled by myself, during startup at some point, usually the screen goes black, you see the cursor that stops at the top right and then AST shuts down and the external GPU starts up. It has happened to me more than once that after the screen is cleaned, the Kernel loaded, the cursor at the top left remains there and does not switch with the external GPU and everything freezes and I must necessarily turn off everything and restart as it was totally blocked ... Which Buster did not do, so I suppose it is a problem related to Bullsye it seems ... For the rest I also noticed a general performance improvement compared to Buster and it took because it was a bit slow and jerky indeed!
-
It looks like you figured some of it out but firmware files basically just need to be in /lib/firmware/amdgpu/ for whichever GPU you have.
-
Hi Borley, the main problem was that I couldn't figure out how to get the updated firmware installed, then I figured it out and I succeeded and at that point the GPU started normal. I was missing some repositories that once entered, they updated and automatically made me update the firmware.
-
I feel ya. I am on the fence about whether or not I even want to use a dedicated GPU anymore, since I don't really play games much at all. And configuring a Raptor system with just the Aspeed graphics is so much less headache. What we really need is a good fully open top-to-bottom graphics add in card. Even if it's just mediocre performance.
-
friend Borley, unfortunately now Aspeed is no longer suitable with the passage of time and as the Linux distros advance, so you need a good GPU. I took the 5700 to have a long-lasting GPU over the years, I don't have to play but in any case I want a performing GPU that allows me to do everything and so when I created my buld Power system, I immediately got this GPU. Unfortunately, however, on Debian 11 there are boot problems often I'm noticing, I have the impression that the fault is with this current firmware because the previous one from Buster did not and neither does the Ubuntu one.
-
I received quite a few messages about Debian recently.
I won't go into the details. As a professional, I simply want to focus on what this means for people who invested in the OpenPOWER platform.
There are not so many people doing OpenPOWER development for Debian. The current politics will prevent important technical work and patches.
For example, my patch for the 4k page size can very easily be integrated into the official Debian releases. I designed the patch to follow Debian's kernel packaging structure. Unfortunately, in a period when I lost two family members, I experienced some extraordinary rudeness from the more difficult people in the Debian ecosystem. I feel that they put politics ahead of the users, people like you.
From my perspective, if anybody wants to discuss the technical merits of the work I do as a Debian Developer, I remain happy to have those discussions and simply publish my packages using more reliable repositories and Gitlab.
After all, the Debian Social Contract, point 4 asserts "Our priorities are our users and free software". Anybody who comes here to help users and provide them with solutions, such as the 4k patch for the Debian kernel packages and the installer ISO based on that patch, is free to call themselves a Debian Developer.
-
Hi Daniel, I don't understand your message to be honest, I personally have described my current experience with Debian, it being understood that I mainly use Fedora and Ubuntu and lately, given the unresolved Fedora issues, I have focused on Ubuntu which I see going better than the others and also having more software available and more repositories also available than Debian itself. As for the 4k pages, I now compile kernels only with 4k pages, but I don't know what these patches you have developed about them are. Having said that I have seen that unfortunately Bullsye has problems with starting on the GPU and in fact it often freezes at startup, turns off the GPU and does not complete the loading of the Kernel, so it is clear that there is some problem, perhaps in the latest firmware I don't know, the fact is that there is unfortunately ...
-
His statement is related to this, I guess
https://www.debian.org/News/2021/20211117
-
I'm not afraid to share those links but I prefer not to because if we look at that then we also need to look at the links about Debian Developers, Ubuntu employees, GSoC mentors and a Debian Project Leader having inappropriate interactions with the young female interns from developing countries. I chose not to post any of that here.
The link about me does not contain any links to evidence. It is pure defamation.
The real question is this: why would Donald Norwood write such a post about a volunteer? Or to put that question in other words: if the attack on me is nonsense (a smokescreen), what are the real flaws in the Debian structure that they are trying to avoid discussion about?
-
Oops I didn't know anything about this friend Daniel, I'm sorry about this thing, I didn't know anything about this story ... I hope you can fix it as soon as possible given the work you do for Debian, especially for our Power!
-
The person who wrote the character assassination claims that I am "purporting to be a Debian Developer"
If you look at his own Debian Developer profile, it says he is a non-uploading developer and he never created one package:
https://qa.debian.org/developer.php?login=donald@debian.org
https://nm.debian.org/person/donald/
I started programming microprocessors when I was about 10 years old and before Debian existed. They can not prevent me from creating and publishing Debian packages. All they are doing is stopping other people like you from using them in the most convenient manner. In other words, they are not hurting me, they are simply sabotaging Debian.
This rogue behavior deters other people from creating packages too. If somebody spends a weekend creating a package, nobody is going to pay them for it but if they are unlucky they will be subject to defamation. So there is no upside but there is a very big downside. These vendettas stop people, especially women, from doing voluntary work in any free software project. Everybody loses in situations like this.
-
Yes, I understand everything, do not worry, in the meantime from the whole Power community you enjoy the fullest support and respect and I believe that nobody here denies it, so do what you feel like doing and don't give a damn about these useless people! As for Debian 11 instead, I noticed that since I boot it with Kernel 5.15.2, it is no longer crashing on boot, maybe it's a 5.12.8 problem that has something that doesn't work well with Debian 11. With Ubuntu on the other hand when I used it didn't give me any problems. In any case, I continue to monitor it to see if it continues to start without problems, if it does then I can say that the problem lies precisely in that version of Kernel.
-
I did a fresh install of Bullseye instead of updating my current 10.9.
As with other Debian flavors it is not really ready for prime time, but yes, it does install and run at least in the AST chip.
Some of the missing software that I use regularly has not reached the distro yet and will no doubt be along soon (ish).
For example, Midnight Commander and XFE. No hurry...10.9 is working fine.
How did you install 11? Did you need to switch over to serial console to interact with the whiptail installer?
-
Today I will attempt to do a new install with the latest Debian 11 net install iso.
I use the onboard VGA for the install as not all the AMD firmware is on the install iso.
I'll be back later to report.
-
I have a hardisk with Debian 11 installed and I use it with my AMD Radeon 5700 XT Navi 10. Obviously I had to use a more recent Kernel than the 5.10 which is by default and I also had to update the firmware to be able to use the Navi 10 but once all this is done, it works quite well under the graphics card. As a Kernel I have compiled a 5.15.2 with 4K pages.
-
@MauryG5
Borley made his post sometime ago and have already worked out his install problem with Debian 11.
Since his list of hardware is not listed it is difficult to offer help.
I hope he is using the AST VGA for the install, and then go from there to tune system for his hardware.
I hope he replies.
And YES, the Deb 11.2 netinstall.iso works fine.
-
I will try tomorrow myself.
-
Xlinder yes I know that it refers to an old post of yours but since he wrote on December 29th or 2 days ago, then I thought that his post was worth now since he wrote now and that's why I wrote my personal experience. .. If it solved perfect fine!
-
Unfortunately, my install still isn't working even when manually setting output for tty0. I don't want to clog up this thread so here is the link to the issue (https://forums.raptorcs.com/index.php/topic,329.0.html) for those who care to take a look.
-
Guys I suddenly got a pretty serious problem on Debian 11. I lost the audio, classic speaker icon at the top right and consequently no audio. I try to load volume control, it tries to open the preferences but it remains constantly loading. I tried uninstalling and reinstalling Pulse audio but got nothing. I tried to force alsa to start but it doesn't recognize alsa, I don't understand what happened ... If I turn up the volume in the settings I get nothing, it doesn't recognize anything anymore, what the hell is going on?
-
In the various tests I have done, I have realized that the problem is not in some Kernel driver or even in pulse audio, apparently it depends on gnome. In fact, as soon as I arrive at the login screen, the loudspeaker with the volume is regularly present and then disappears when you log in. Trying to tap it on the login screen, it started working smoothly again even after. There must be some small bug on gnome 3.38 regarding this thing ... See over time if the same thing happens to you too ...
-
Hi guys, I wanted to ask you something that I have never been able to understand well. For some time now, I have been compiling the kernels myself to make sure that I use options that are more congenial to me and be able to use the infamous 4K page format as my friend Daniel Pocock taught me. To compile the Kernel, both on Debian and on Ubuntu which is a derivative, I use the universal procedure and then I do: make menuconfig and I configure the kernel, make -jx, obviously I put the number of treed in place of x, make modules, make modules install and finally make install. At that point after make install the grub updates and gives me the new kernel and actually at the new start, I find it in the list of usable kernels. The only thing I can't understand though is, why when I give the grep command to see the installed kernels, I never get my compiled files? Consequently if I have to remove one of mine, I can't because giving the classic remove command, it tells me that that kernel obviously doesn't exist. I would like to understand what is missing in my procedure, which allows the system to recognize 100 by 100 the kernel compiled and installed by me ... Thanks to all of you always
1
-
make install places everything in the filepaths directly, so dpkg never sees it. You probably want to build into .deb packages instead, starting from apt source linux-image-X.XX.X-XX-powerpc64le. But don't ask me details, I'm really new to the procedure myself.
-
Hi Borley, yes you are right, the installation part with the dpkg -i command is missing but the universal procedure does not bring you anything on how to do after the make install that's why I have never deepened further. Now I have found a procedure that reports the command: sudo make -j 32 KDEB_PKGVERSION = 1.-maury.ppc64le deb-pkg
I call my custom kernel as you understand of course, if I do this then he creates the .deb packages which can then be installed with the dpkg command, only I noticed that if I do this command, I try to compile the 5.15 kernel. X, it gives me an error towards the end of the compilation while if I try to compile a more recent version like 5.17, then the compilation procedure is successful and I honestly don't understand why. If I use the procedure that I have always done, that is the universal one I mentioned above, then the compilation takes place without problems even on version 5.15.X but as usual I have the problem that I do not have the .deb files to perform the actual installation. If I understood how to get the .deb files from the universal procedure, I would continue to use that without any problems ... I would like to understand well how to do after the make install, how to get the .deb files, I need the advice of a Debian expert like Daniel Pocock or Xlinder or Linux experts that there are many in here :-)
-
I do not make .deb packages. I also do not use make -jx, or make modules.
Pretty much I do make menuconfig, make, make modules_install, make install.
In menuconfig I change things to what I want, like 4k PAGESIZE, and for my system with 2x8 cores, I use 64 processors.
If I want I use mc (midnight commander) as root or sudo to look at /boot and perhaps remove,move, or add kernels and
other stuff and then use update-grub as necessary.
Using the update-grub command may require you to login as su - (the - is important) and then do /usr/sbin/update-grub.
-
Hi Xlinder, I also do like you and I use that procedure that they say is the universal one, only that way the system does not recognize you the fully installed kernel and when you have to remove it to put a new one, you have to remove file by file in the boot folder and when you run the grep command to find out how many kernels you have installed, the one you made is not there since you have not installed .deb packages. and you can't even do the classic purge command to remove that kernel because it tells you that kernel isn't installed on your system. So the system eventually does not recognize as installed, a kernel with that procedure even if it regularly makes you use it obvious. I would like to understand if it is possible to make the system recognize a kernel installed with this universal procedure as you do ...
-
I have been burned by running make as root user in the past, so I always avoid running make with sudo when possible. My understanding of the process so far:
- apt install dpkg-dev flex bison rsync libssl-dev (if not already installed)
- mkdir build-directory && cd build-directory
- apt source linux-image-X.XX.X-XX-powerpc64le
- make oldconfig (to copy kernel config from existing entries)
- Edit .config and:
CONFIG_LOCALVERSION="" (<-- append custom kernel name in "")
- Make whichever changes you need to the kernel/modules
- make bindeb-pkg
Then finally:
- sudo dpkg -i linux-image-X.XX.X_X.XX.X-1_ppc64el.deb
-
I have been using Midnight Commander for so long, not only on Linux, that it has become my goto default tool for kernel building, system snooping, etc.. I build my kernels as user, and install as root as necessary.
Many times I will remove them from /boot by moving to a folder in /home along with the modules....just in case.
Different strokes for different folks.
Now that my Radeon 7750 is working with 64k pagesize there is less urgency.
-
Borley, I tried your procedure, practically the same as the one done with the command: make -j 32 KDEB_PKGVERSION = 1.-maury.ppc64le deb-pkg and the error that gives me at the end is always the same on the Kernels with long support of the 5.15.X series If I try to compile the recent ones then it works but unfortunately the recent kernels as we know do not work on Power, like 5.17.X and therefore I cannot use this procedure yet. The error here is this too: make [2]: *** [debian / rules: 7: build-arch] Error 2
dpkg-buildpackage: Error: debian / rules binary subprocess returned exit status 2
make [1]: *** [scripts / Makefile.package: 83: bindeb-pkg] Error 2
make: *** [Makefile: 1576: bindeb-pkg] Error 2
I don't understand why these 5.15 Kernels make this error, 5.15.2 does it, 5.15.30 does it and also the current 5.15.33. Only if you use the universal procedure like the one I've always used and which uses Xlinder, then it doesn't give you compiler errors but I don't know how to make the system recognize it in that case. I'm waiting for them to fix the new Kernel bug so I can use that ...
-
Finally, I got my Talos 2 (second hand machine) recently so I am not just a dreaming follower anymore ;D
I successfully installed Debian 11.4 (kernel 5.10.0-17). Hopefully I am quite familiar with Debian installer because its display was partially corrupted with truncated text and unexpected characters (I started installation with a 17" screen, not large enough?).
I tried KDE Plasma and Mate, installed tools, started to compile few programs, used Firefox a bit ... and also got display from a Radeon HD6570 (and I have received a RX550) but details about that will take place in another section of the forum.
I am not able to test audio, I will do that later. And today, I upgraded to Debian 11.5 (available for 2 days).
Everything works well so far. Ready to enjoy my machine. I just would like it to be less noisy (CPU fans).
-
Great job, you can also try Gnome, since Debian has been updated to version 11, Gnome has improved a lot as a graphical environment and has gone from the old 3.30 to my second best version which is 3.38. I don't know how you manage to make the graphics card work with the default kernel or 5.10.x. To run Radeons correctly on that version of Kernel, you need the page size in 4k and by default the Kernels on Power all have 64K. They fixed this bug only later in the Kernel even though I don't remember exactly from that version right now ...
-
Finally, I got my Talos 2 (second hand machine) recently so I am not just a dreaming follower anymore ;D
Everything works well so far. Ready to enjoy my machine. I just would like it to be less noisy (CPU fans).
Congrats. To get the fan noise down with the default SC747 chassis, make sure your firmware is fully up to date first. My system also has the superquiet power supplies (bought from a third-party) and I disconnected and removed the two rear fans since the HSFs and other case fans are more than sufficient. With these changes, my dual-8 T2 is very quiet most of the time, even under load -- certainly much quieter than the Quad G5 next to it.
-
@ClassicHasClass Thanks! The chassis is a CSE-732 from MicroSemi (https://www.senetic.fr/product/CSE-732I-500B) and I have no fans except HSFs ones (https://store.vikings.net/en/3u-heatsinkfan-assembly) and the power supply. I will have to check the firmware version ... I am not yet familiar with all components.
I don't remember who much noise produces my Dual G5 that is side by side with the Talos 2 :P I will reboot it to install Debian 11 too (don't know when).
@MauryG5 It was reported that the problem was fixed in kernel 5.10.101 and kernel 5.11.12. And this bug was only concerning amdgpu. At the moment, I tried HD6570 that uses radeon driver. Sorry if mentionning RX550 was confusing, let's consider I have not started to test it.
-
The SC732 is very similar, though I don't know if it takes the same power supplies. I'd say the power supply replacement was the biggest reduction, but even just getting rid of the rear fan and relying on the front fans helped.
-
Sorry guys, if I want to update mesa drivers and firmware on Debian 11, which procedure should I use? Thanks always!
-
Sorry guys, if I want to update mesa drivers and firmware on Debian 11, which procedure should I use? Thanks always!
One solution might be to dist-upgrade to testing (currently Bookworm) where things are more up to date. On my test system it's stable (though the number of updates you get each day feels a bit like a rolling-release distro).
Testing doesn't usually get security fixes as quick (or at all), though, unless you get those from unstable. So that's something to keep in mind. Then again it's more difficult to keep the system up to date with an increasing number of packages installed from source. With just the graphics stack built from source that's probably not going to be a problem, so that would be another option I guess.
-
so you advise against doing these updates at the moment I understand... Better wait for the next distro 12 maybe...