Raptor Computing Systems Community Forums (BETA)
Software => Operating Systems and Porting => Topic started by: MPC7500 on July 19, 2020, 05:23:59 pm
-
Debian 9.13 has been released.
https://www.debian.org/News/2020/20200718
-
The final stretch :D
-
LOL
-
Debian 10.5 has been released:
https://www.debian.org/News/2020/20200801
-
The announcement page doesn't really tell us much about the impact for ppc64* users. This is where it would be really useful to have tags for ppc64* issues (https://forums.raptorcs.com/index.php/topic,141.0.html), we could then run a report in the BTS and see exactly which issues were fixed by each new release and which issues are fixed in unstable and ready for backporting.
-
Guys but do you know if this last relase of Debian supports AMD Navi 10 by any chance? Or do you have to wait for Debian 11...
-
guys good morning, sorry but why does Debian not recognize the optical disc player that the other distributions recognize automatically immediately? I am obviously talking about our Power version because in the X86 version this problem does not exist ... Even Ubuntu that derives from Debian does not have this problem ... What should be done to make it recognize it, is there any driver or is there any procedure to be performed? Thanks
-
@MauryG5
???
https://ibb.co/bv5xxHq (https://ibb.co/bv5xxHq)
Works here.
-
Hi Xlinder, yes I understand that from the operating system it works smoothly, I'm talking about when you have to install Debian from the beginning, when you copy to the optical disc the ISO image downloaded from the official Debian website and start the installation process. At a certain point, after choosing the language and the keyboard type, the installer tells me that it doesn't see the optical disc drive and I don't understand why... Everyone sees it in a direct way and I don't understand why the Debian installer is the only one who doesn't see it...
-
Don't Know. Try USB stick.
-
done well but with the key it does not start the installation from petit boot, whether I copy the iso image directly as I download it, or if I put the ISO file through a procedure with Shell. Eventually I managed to install it by putting both. With the DVD I started the installation and with the stick I did the installation once I entered ... I honestly don't understand this strange behavior of Debian. Now I am installing gnome and the optical drive works fine ... Anyway, apart from these oddities, do you or someone else know by chance where to download the 5.9.6 kernel for Debian Power? Thanks
-
The 5.9.6 kernel is in backports
You can look here to see it really built for ppc64le:
https://buildd.debian.org/status/package.php?p=linux&suite=buster-backports
To install it, after you installed Debian, you type something like this:
$ sudo apt install -t buster-backports linux-image-powerpc64le
-
Hi Pocock, thanks for reporting, I'll do as you tell me. The thing I am seeing for now is that for me Debian runs very badly at the moment, it jerks ... Obviously at the moment I have to use it with Blackbird video output but the resolution is still low so I don't know if it depends on the graphics server or other...
-
Do a lsmod in a terminal and see if there are several amdgpu modules installed.
Then Look in /lib/firmware for your GPU and make sure all the firmware for the card is in there.
-
Xlinder sorry, but I have to do the ismod command after installing the 5.9.6 kernel right? I don't think that at the moment with 4.19 there can be support for recent AMD GPUs like my Navi 10 ... The problem is that at the moment it jerks and I don't know if I can make it go well, let's see if I have to do everything as a server and so I should exit with ctrl, alt, F2 to return to server mode and from there type ismod and possibly also install the kernel or I can do it from desktop ...
-
guys then this Debian is a nightmare for me. Not only does it work terrible after installation, it jerks and is unusable but it doesn't even let me log in as root. When I try to authenticate with SU and after entering the password, it tells me that the authentication has failed and it always does even if I try to change the password. For me this Debian is totally unusable ...
-
Navi 10 is newer than the latest Debian stable, right? It is possible that the firmware is not yet present in firmware-amd-graphics.
You might need to also install the backport for it until you move to Bullseye firmware-amd-graphics/buster-backports 20200918-1~bpo10+1
-
No Borley the problem is not Navi 10 but with the Blackbird video output ... As soon as you finish installing and restart the operating system you just installed, initially you have not put anything yet and therefore it works by default with the video output of the card mother and the problem is right at the beginning then. Fedora or Ubuntu never gave me this problem as soon as they were installed, only Debian is giving all these problems and the Navi GPU I haven't even used yet. The problem is fundamental and I do not honestly understand what could be wrong, I downloaded the 10.7 version which has recently come out so the most updated ... Also another absurd thing is that I do not authenticate the root for the super user and this is incredible honestly because during the installation I have reported username and password as requested ... I don't understand honestly why this distro is so problematic, I just don't understand ... I'm very disappointed!
-
The problem affects every other distribution as well
https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#Xorg_crashes_or_is_laggy_with_the_AST_VGA_GPU & Display stuck at default low resolution with AST HDMI GPU
-
I didn't know they were doing this kind of settings for operating system 3D management now, thanks for the MPC info. In any case I managed to get it to work normally with a trick. If you quit with ctrl alt F2 and then re-enter with startx, disable 3D handling and go back to 2D and you can use it. But my problem is that the command that Pocock gave me doesn't work. When I give it it gives me an error telling me that it is not valid for APT :: Default-Release since this release is not available in the sources ... I tried to look for a site where I could directly download Kernel and Kernel modules to install it manually but I cannot find it ... How can I solve?
-
Guys then update, I was able to understand the problem of the failure to download the kernel 5.9, pocock forgot to tell me that first you had to run another command to be able to prepare the download of the package, I do not know the steps unfortunately, not being familiar with Debian. In any case I found a site that gave a mini-guide for the commands to do, including what I posted pocock, after as the last command also performs the installation of firmware for this new Kernel. At reboot I also put the file on usr/share/X11/xorg.conf.d, to enable the amd gpu but at reboot unfortunately gives me an error and tells me that it can not load the gpu... I send you the photos of both the error for the gpu and the error that has always given me at boot Debian but this time I speak of Debian itself and its Kernel. In fact I've noticed that I always get error loading Kernel modules, both with the old one that is installed by default, and with this new one. I don't know if it's related to the problem but it's a fact that it always gives it and it's very strange considering that it does it right after the installation and then without me touching or modifying anything, I've noticed since the first boot, that this error does it always. In fact I noticed that in normal operation with kernel 4.19, sometimes the video disappears and returns to server mode for example. This Debian seems to have its own underlying problems, regardless of the 5.9 kernel in my opinion ...I attach pictures of what gives me as errors both kernel and gpu...
-
If you do lsmod does it show any modules being loaded ?
If you look in /lib/modules are they in there for the kernel you are using ?
Some times all the modules are built into the kernel so there may not be any modules
-
I'm going to publish more of my own Debian packages over the next few weeks, along with documentation, that will make it a lot easier. The packages I've described this week, Domoticz (https://forums.raptorcs.com/index.php/topic,242.0.html), an optimized ffmpeg (https://forums.raptorcs.com/index.php/topic,243.0.html) and OBS Studio 26.1.0 (https://forums.raptorcs.com/index.php/topic,244.0.html) are an example of how things can be backported to get the latest fixes on POWER9.
It is really useful if people can help to test these things and provide feedback, for example, by opening Debian bug reports (https://bugs.debian.org) or trying different smart home products with Domoticz (https://forums.raptorcs.com/index.php/topic,242.0.html) and sharing feedback about which products work and which products don't work. Developers can then focus our energy on other aspects of development while the community is testing things.
Another good place to ask for help: subscribe to the debian-user mailing list (https://lists.debian.org/debian-user/).
-
Xlinder no I didn't give that command, I should try to do it and see what you say but apart from that, in my opinion the underlying problem is in the Kernel after version 5.6. I also tried to install Ubuntu, up to version 5.4 of the Kernel, with Ubuntu 20.0.4, the internal gpu mode works and with AMD Navi 10, I tried to enable the card by inserting the usual file in xorg.conf, as reported in the guide on wiki and that made me enable Navi 10 on Fedora, but the operating system at that point doesn't start anymore. In any case, before inserting this file on Xorg, I updated Ubuntu to the latest version or the 20.10 which has in Kernel 5.8 and coincidentally, even in AST mode and without enabling the Navi 10, the computer just after it loads the system, yes it crashes irreversibly and must be shut down manually, just like with kernels from 5.7 onwards on Fedora. So in my opinion there is an underlying problem of the Kernel from version 5.7 onwards on Power that goes into constant conflict with the Navi 10 and that no one has yet unearthed for our misfortune. It is not possible that all distros that exceed version 5.6 of the Kernel suddenly stop working! You have to work on this first thing, you have to eliminate this damn bug that causes conflict between the drivers of Navi 10 and the new files contained by the Kernel 5.7 onwards on Power! Now I want to try to disassemble the graphics card and start Ubuntu version 20.10, do you want to see that if I remove the graphics card it starts? We'll see...
-
I will publish a 5.9 kernel built with the 4k page size, I think it is a really good idea to try that.
It will be available as a Debian package so you can install it very easily along with any other Debian kernels and choose between them when you boot.
I'm really interested to know if this fixes the problem for you.
It may be some time next week, I'll post an update here when it is available.
-
Okay, then I'm waiting for your publication, let me know how to install it, the command you need or where to download it and tell me if I have to delete at this point, the current kernel 5.9.6 that does not work even if I think say yes at this point. I know the procedure on Fedora for deleting kernels, I always delete the kernel entry and the Kernel modules entry and he deletes the kernel in question. In case it's different let me know this too ... Thanks.
So you think it's just a page size problem, it would be amazing that a simple thing like this would affect the Kernel so badly that it crashes. This perhaps would also mean that the other distros could settle down the same way at this point ... Hopefully, I trust you Pocock, you're all of us ...
-
Guys one thing I didn't understand about the installation of this Debian Buster is that when I prepared the 4 partitions to install it, it touched the swap partitions of the other 2 hard drives where I installed Fedora and I don't understand why. I have regularly selected the empty hard disk where I had to install Debian, why I have to touch the swap partitions of both one and the other hard disk that have nothing to do with it! Now both hard disks with Fedora boot with a 2o seconds delay and this is very annoying honestly and I didn't think that doing this touch on the swap partition of those, would create this problem... I've tried reformatting the swap partitions on both and but the problem persists, they keep starting with delay...
-
A question first. Did you use the graphical installer?
When installing Debian you have to set the other disks or partitions to "Do Not Use", and Debian will ignore them. That is in the section where you format the disks.
-
yes I used the graphical installer but honestly I have not seen this option, strange ... now do you think I can do something to avoid this small inconvenience?
-
Not sure. Perhaps by adding a # in front of the lines for the disks/partitions you do not want to use in /etc/fstab (?)
-
I don't know honestly, you obviously speak from inside Debian I suppose ... In any case, let's see if Pcock tells us something for further help it would not be bad ... Meanwhile, I take this opportunity to wish all of you Open Power friends! Happy New Year, Happy New Year to the Raptor staff!
-
The file you say is this, we are talking about Fedora in this case and as you can see it has no partition other than its own and in this moment the hard drive containing Debian is completely deactivated and unmounted from the computer...
-
Yes. That is the file and the Debian file should be similar. You can see the UUID for Fedora and that device should not be in the Debian fstab. Put a # before that UUID line in Debian and also for the UUID for the Ubuntu SWAP device.
When setting up drives during Deb install select the other drives/partitions and there will be a choice "Do Not Use" and it will not appear in fstab.
-
The command to bring up these UUID files should be "blkid" from what I see on the web. In any case, it is better for me to open them from the operating system directly and then find the folder with these files and once the contents of the end have been launched through a text edit make the change you tell me, both on Fedora and on Debian, but first I have to find those righteous ... I'll try thanks
-
Your Fedora setup looks fine. Only one swap partition.
The Debian setup probably has 3 swap partitions. Find which partition is on the same disk as Debian and # out the other 2, only in Debian.
-
As promised, the kernel with 4k page size is now available for Debian (https://forums.raptorcs.com/index.php/topic,247.0.html), please try it, I'm curious to know if this fixes problems with the Radeon RX 5700
When you boot into the new kernel, you can verify the page size like this:
$ getconf PAGESIZE
4096
-
Xlinder picking up for a moment that talk about the Debian partition that put me something on Fedora and now it loads me with 1 minute and a half delay compared to before, I tried to see those files you told me about Debian as well but they are regular like that of Fedora. What you see when you load Fedora and it freezes for about 1 and a half minutes is what you see in the picture, it writes to you like this and you have to wait about 1 and a half minutes before it resumes. What can it be in your opinion?
-
My first question is....What disk partition is uuid/d6572c89 etc.. Is it a Fedora partition or is it on your Debian disk?
Next, if you look at /etc/fstab is that uuid/d657 etc. listed in that file?
You can use Gparted to find the uuid for all partitions on your system. Select the partition and then select Information in the Partition menu.
-
Meanwhile, I can tell you that Debian is currently not on my system because I physically removed its hardisk. Right now I have 2 hard drives running Fedora 33 and one hard drive running Ubuntu mounted on the computer. The problem is that something Debian did when I made that mistake of saying yes to it on installation the first time and from that moment both fedora disks stop about 1 and a half minutes before restarting ... I will check the partition and i will let you know what is that disk partition you tell me ...
-
My first question is....What disk partition is uuid/d6572c89 etc.. Is it a Fedora partition or is it on your Debian disk?
Next, if you look at /etc/fstab is that uuid/d657 etc. listed in that file?
You can use Gparted to find the uuid for all partitions on your system. Select the partition and then select Information in the Partition menu.
Hi Xlinder, I checked all the uuid partitions on both Fedora hardisks but of the one in the picture no trace, it's not there. Considering that Debian is not mounted right now, do you think it's possible that it looks for a partition it can't find and then wastes that minute and a half looking for something it can't find but that is stored somewhere and causes it to look for it at every boot? Where to look eventually for this file to delete it and not make him look for it anymore?
-
If is not in /etc/fstab I don't know how to delete it. Perhaps it was a USB disk that was not unmounted before removal(?) . I just don't know.
-
never used usb disks, so i rule it out. I'll try to see where you say, etc / fstlab, what should I look for specifically in your opinion?
-
The only disk UUID in there should be the ones for the running OS.
I wonder if you could have something active for a repository that is looking for a local disk or USB stick (?)
-
good question, I have no idea honestly ... I don't even know how to understand if I have this repository that you say ...
-
open dnfdragora, click File, then select Repositories.
As you highlight each of the active repositories, the ones that are checkmarked, then look at the bottom section in 'Meta Link'. If any of them refer to a local disk then uncheck that selection.
-
Xlinder I think I found it ... In the end it is the swap partition that Debian actually went to touch, I just don't understand why the system has to dwell on it at this point, what it finds anomalous since I had reformatted it and also disabled it is ... The offending partition is her because it corresponds exactly to the one you see in the load and where it remains for 1 minute and a half ... What can it have in your opinion since it was formatted new?
-
Free advice (for what it's worth). This could fix the problem, or screw things up really bad.
The UUID of that partition in /dev/disk/by-uuid and /etc/fstab must be the same.
Open Gparted and select the proper swap partition. Then in the Partition Menu select swap-off and Apply that. Next, select the partition again and from the menu select Format and Cleared from the secondary menu.
Apply that. Now format the partition as Linux-swap, and apply. Then set swapon.
Select Information and Highlight the new uuid, you can use Ctrl + c to copy it and paste it into a text editor.
As root open /etc/fstab with a text editor, cut the old uuid number from the file and paste the new number in it's place and save the file.
Reboot. It's okay to curse me if things went very badly.
-
Don't worry, now I have to try somehow, indeed I always thank you for the advice you give me. As soon as I can I will try to do this procedure you wrote to me, it also seems articulated so not easy, I need time to do everything calmly. Thanks so much
-
Xlinder hi, before doing any procedure, I'll show you something interesting. As you tell me in your last post, the partitions contained in etc / fstab and dev / disk / by-uuid must match and in fact I find the first 3 all in its place. Except that as you can see for yourself, the offending one is not present, so maybe that's why he freezes for 1.30 as he looks for a partition that is present in etc / fstab but not in dev / disk / by-uuid ! What do you think? At this point, can you confirm that you try to do the procedure you described?
Thanks always very kind!
-
Yes, I have done this before.
There have been many requests for someway to rebuild or refresh /etc/fstab, but no luck from the distros. So this works IF you are careful.
In gparted, just be sure to copy the new uuid number of the partition you Clear. Then paste it into /etc/fstab replacing the old one.
I have another recommendation for you after this problem solved. Let me know when you are done.
-
In practice, now that I carefully read your procedure, I have already performed the deletion of the offending swap partition when all this happened to me and I thought it was enough but it wasn't. What I did not do, however, as I did not know, is the last part of the procedure or copy the new uuid number created with the new partition and copy it instead of the old one ... I have to try and let you know ok, thank you
-
Free advice (for what it's worth). This could fix the problem, or screw things up really bad.
The UUID of that partition in /dev/disk/by-uuid and /etc/fstab must be the same.
Open Gparted and select the proper swap partition. Then in the Partition Menu select swap-off and Apply that. Next, select the partition again and from the menu select Format and Cleared from the secondary menu.
Apply that. Now format the partition as Linux-swap, and apply. Then set swapon.
Select Information and Highlight the new uuid, you can use Ctrl + c to copy it and paste it into a text editor.
As root open /etc/fstab with a text editor, cut the old uuid number from the file and paste the new number in it's place and save the file.
Hi Xlinder, you are great! I applied everything you told me and solved the problem big time. Fedora now starts up smoothly and no longer hangs there for 1.30 minutes. Since you told me that the uuid number of etc / fstab must also be on dev / disk / by-uuid you have made me understand the whole problem. In practice he crashed because he did not find the correspondence of the swap partition, the number that was there of the new partition he had created before Debian and then when I deleted and reformatted it the first time, it no longer corresponded with the one contained in by-uuid and consequently he stopped at that point and finding no response then deactivated the swap partition. Now I have to do the same procedure on the other hardisk with another Fedora installed and restore that to return to normal. Thank you so much for your advice you were great!
Reboot. It's okay to curse me if things went very badly.
-
I noticed you are using the default desktop file manager for this problem.
May I suggest to you to install and try XFE and MC (Midnight Commander). Play with them for a while, especially for system and kernel work you might find them very handy.
Sometimes all you need is a bigger hammer. :)
-
https://gitlab.com/chromium-ppc64le/chromium-ppc64le
Debian friends, the link that TLE posted brings Chromium version 84 for various distributions. Is it possible in your opinion to install it on Debian by downloading it from this link? I tried this with the dpkg command but couldn't, maybe because it has no .Deb extension ... I tried dpkg -i
-
Hi guys excuse me, I was trying to upgrade debian buster to bullseye but something went wrong. While he was doing all the upgrades he put himself in stenad by, I was out of the room and I did not notice and now he no longer takes the commands sudo apt-get upgrade or sudo apt-get dist-upgrade and tells me that the dpkg is locked and I need to make some changes. What exactly must he do that I don't understand? Thanks
-
I typically only run into dpkg locked when there is an apt installation running in another terminal or window. Do you have any others open?
-
Hi Borley, no I don't have anything else open but now it doesn't load completely anymore, unfortunately it got damaged and I guess I have to delete everything and reinstall Debian ... Damn ...
-
Good evening guys, after having irreparably damaged the Debian version 10.7 so far, I decided to delete and re-install everything. I installed version 11 and now after compiling a Kernel with 4K pages to start the Radeon 5700 XT graphics card, I realized that at startup it gives me a GPU error and does not start with that but always starts with AST. Can you tell me if it's a Mesa or Wayland problem or something else I don't know? I know that the Mesa drivers have been updated to version 20 or higher on Debian 11 so there shouldn't be this problem ... Currently it starts by default with Wayland but I don't remember how to disable it to tell the truth, always if you need to do it, maybe not need to disable Wayland now ... What do you think I'm missing? Hey Daniel Pocock, best wishes for your Talos II bought by my friend in Italy, what do you think is happening since you are Debian expert? Thanks
-
Maybe you have to blacklist the AST GPU
https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#I_want_Petitboot_via_AST_but_the_subsequent_Linux_OS_console_on_a_discrete_GPU
-
But I don't think that's the MPC problem as I've always used the GPU activation file in the xorg.conf.d folder and it always worked. It worked with Debian 10, works with all Fedora and all Ubuntu. So I really don't think that now I have to do this suddenly ...
-
I think I understand the problem anyway, I was able to read the initial error message and it tells me it can't find the GPU firmware! I wanted to see if I had the firmware updated by trying: sudo apt install -t bullseye-backport firmware-realtek firmware-iwlwifi firmware-linux-nonfree but it tells me that bullseye-backport I don't have them in release and therefore I can't install ... I have to understand so how to recover this updated firmware ...
-
I ran into something like this when I tried Debian 11 also. (https://forums.raptorcs.com/index.php/topic,292.msg2271.html) Apt gave me a message about possible missing firmware, even though I know for a fact that the bin files for polaris were present from installing firmware-amd-graphics. And Dan may not see your earlier comment addressing him so it might be worth messaging his account.
-
Guys, after some testing, I decided to promote Debian as the first distro to use on Power. I noticed the great improvements that version 11 brought and I realized therefore that Debian is now much more usable than recently at the time of version 10. I also realized that it maintains a certain lightness compared to Fedora and Ubuntu, all load much faster than the other distros mentioned. Unfortunately Ubuntu continues to suffer chronically from some critical issues that unfortunately limit its use a bit and Fedora by now, since adopting the Gnome version 3.4X, is no longer usable as before and needs changes that must be known to do. At the moment I am therefore much more satisfied with Debian and its evolutions and so now I use it on everyone, hoping that it continues to be as good as it is now.