Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

Oh, if you write a doc, ill be your first reader !

OK, stay tuned. Give some time...

Thank you very much, i have tried right now:
Install libdrm and meson from unstable with apt-pinning... but steam:i386 (and other packages) is linked to the default libdrm-common version and is uninstalled in the process.
I understand i have to set a prefix in meson, but i also have to update llvm.
After all that, i think i have understand that i have to use LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH to select another MESA version.
I have reinstalled default Buster libdrm(-*) and all packages removed earlier, i'm returned to square one.
All that to say i'm not asking without searching first, i think i'm on the right way, but it is definitely out of my knowledge.
Don't hesitate to PM me when you have news on the doc ! :D

Here comes the first part... compile 64bit driver. 32bit will follow.
https://www.goodbytez.de/howtos/compile-mesa-debian-bullseye [External Link]
It's a simple text file on my web server you can download or simply open in your browser.

I would not recommend mixing/pinning packages... you will run into problems one day.
Oh, you use Buster... than I have bad news for you... I've run into the same situation because of Metro Exodus.
This game is compiled against libc6 2.29 but Buster ships with 2.28. You NEED to update to Bullseye when you want to play the "native" Linux version. All programs/libs in a linux system are compiled against libc6 (GlibC) and there are no Buster backports for that.
Debian Bullseye is currently in soft-freeze and I can recommend it. It's already "rock" solid.

Wow i was not expecting the doc this soon, thank you.
Yeah i dont want a FrankenDebian too, i keep track of what i do to undo stuff if i have.
I have already tested FrankenDebian some years ago with deb-multimedia, it was working fine, but at the end it was a mess, to upgrade distro i was obliged to remove this repository, and removing it was breaking things. I finally managed to repair that without reinstalling, but it was a pain and a good lesson.
I was thinking the FrankenDebian way was the only way to have Debian with last MESA: this is why my first choice was to change my distribution.

I'm on Buster, but upgrading to Bullseye is not problematic, some games (Dying Light) have already forced me to upgrade sonner to next version (or it was AMD).
Yes i have the """best""" case possible: AMD card, and it is not the worse, it is a CGN1.0/1.1 card (i must activate experimental features in kernel command line to get my card working...)

Some info on my current system:

$ glxinfo | grep ^direct
direct rendering: Yes

$ glxinfo | grep 'renderer string'
OpenGL renderer string: AMD Radeon HD 7900 Series (TAHITI, DRM 3.27.0, 4.19.0-16-amd64, LLVM 7.0.1)

$ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.6
OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.3.6
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.6

I think i have to adapt the meson build line (i dont see radeonsi stuff) ?

Thank you again, i try this as soon as possible !

EDIT: I'm on BullsEye now :D

The docu for 32bit build is finished.
I guess you want to install "master" to test the fix. Could/can you configure the 64bit build with meson... step A)5) in my docu? I'm pretty sure that you need newer libdrm or/and LLVM, right?
Let me know and I'm glad to help if needed.

View this comment - View article - View full comments

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

Oh, if you write a doc, ill be your first reader !

OK, stay tuned. Give some time...

Thank you very much, i have tried right now:
Install libdrm and meson from unstable with apt-pinning... but steam:i386 (and other packages) is linked to the default libdrm-common version and is uninstalled in the process.
I understand i have to set a prefix in meson, but i also have to update llvm.
After all that, i think i have understand that i have to use LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH to select another MESA version.
I have reinstalled default Buster libdrm(-*) and all packages removed earlier, i'm returned to square one.
All that to say i'm not asking without searching first, i think i'm on the right way, but it is definitely out of my knowledge.
Don't hesitate to PM me when you have news on the doc ! :D

Here comes the first part... compile 64bit driver. 32bit will follow.
https://www.goodbytez.de/howtos/compile-mesa-debian-bullseye [External Link]
It's a simple text file on my web server you can download or simply open in your browser.

I would not recommend mixing/pinning packages... you will run into problems one day.
Oh, you use Buster... than I have bad news for you... I've run into the same situation because of Metro Exodus.
This game is compiled against libc6 2.29 but Buster ships with 2.28. You NEED to update to Bullseye when you want to play the "native" Linux version. All programs/libs in a linux system are compiled against libc6 (GlibC) and there are no Buster backports for that.
Debian Bullseye is currently in soft-freeze and I can recommend it. It's already "rock" solid.

Wow i was not expecting the doc this soon, thank you.
Yeah i dont want a FrankenDebian too, i keep track of what i do to undo stuff if i have.
I have already tested FrankenDebian some years ago with deb-multimedia, it was working fine, but at the end it was a mess, to upgrade distro i was obliged to remove this repository, and removing it was breaking things. I finally managed to repair that without reinstalling, but it was a pain and a good lesson.
I was thinking the FrankenDebian way was the only way to have Debian with last MESA: this is why my first choice was to change my distribution.

I'm on Buster, but upgrading to Bullseye is not problematic, some games (Dying Light) have already forced me to upgrade sonner to next version (or it was AMD).
Yes i have the """best""" case possible: AMD card, and it is not the worse, it is a CGN1.0/1.1 card (i must activate experimental features in kernel command line to get my card working...)

Some info on my current system:

$ glxinfo | grep ^direct
direct rendering: Yes

$ glxinfo | grep 'renderer string'
OpenGL renderer string: AMD Radeon HD 7900 Series (TAHITI, DRM 3.27.0, 4.19.0-16-amd64, LLVM 7.0.1)

$ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/radeonsi_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.6
OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.3.6
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.6

I think i have to adapt the meson build line (i dont see radeonsi stuff) ?

Thank you again, i try this as soon as possible !

EDIT: I'm on BullsEye now :D

Great! I will finish the howto today evening.

View this comment - View article - View full comments

Quoting: Avehicle7887

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

Oh, if you write a doc, ill be your first reader !

OK, stay tuned. Give some time...

Thank you very much, i have tried right now:
Install libdrm and meson from unstable with apt-pinning... but steam:i386 (and other packages) is linked to the default libdrm-common version and is uninstalled in the process.
I understand i have to set a prefix in meson, but i also have to update llvm.
After all that, i think i have understand that i have to use LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH to select another MESA version.
I have reinstalled default Buster libdrm(-*) and all packages removed earlier, i'm returned to square one.
All that to say i'm not asking without searching first, i think i'm on the right way, but it is definitely out of my knowledge.
Don't hesitate to PM me when you have news on the doc ! :D

The llvm team have debian packages on their website which are easy to install. It is also possible to compile it from source but I would advise keeping that as a last resort.

Yes, this is the right way to do. Backporting LLVM on your own takes hours.
When you are an AMD user you should do that, because radv and radeonsi very often need bleeding edge LLVM.
Also newer libdrm2 is needed more or less.
These are tiny packages which I always backport myself from unstable or experimental when needed. This step is much easier than compiling Mesa but needs you to also compile the 32bit ones before you can install them.

View this comment - View article - View full comments

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

Oh, if you write a doc, ill be your first reader !

OK, stay tuned. Give some time...

Thank you very much, i have tried right now:
Install libdrm and meson from unstable with apt-pinning... but steam:i386 (and other packages) is linked to the default libdrm-common version and is uninstalled in the process.
I understand i have to set a prefix in meson, but i also have to update llvm.
After all that, i think i have understand that i have to use LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH to select another MESA version.
I have reinstalled default Buster libdrm(-*) and all packages removed earlier, i'm returned to square one.
All that to say i'm not asking without searching first, i think i'm on the right way, but it is definitely out of my knowledge.
Don't hesitate to PM me when you have news on the doc ! :D

Here comes the first part... compile 64bit driver. 32bit will follow.
https://www.goodbytez.de/howtos/compile-mesa-debian-bullseye [External Link]
It's a simple text file on my web server you can download or simply open in your browser.

I would not recommend mixing/pinning packages... you will run into problems one day.
Oh, you use Buster... than I have bad news for you... I've run into the same situation because of Metro Exodus.
This game is compiled against libc6 2.29 but Buster ships with 2.28. You NEED to update to Bullseye when you want to play the "native" Linux version. All programs/libs in a linux system are compiled against libc6 (GlibC) and there are no Buster backports for that.
Debian Bullseye is currently in soft-freeze and I can recommend it. It's already "rock" solid.

View this comment - View article - View full comments

Quoting: DebianUser

Quoting: johndoe

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

Oh, if you write a doc, ill be your first reader !

OK, stay tuned. Give some time...

View this comment - View article - View full comments

Quoting: DebianUserHmmm, i think i have to drop Debian... MESA is the only thing problematic (i can have recent packets via flathub integrated to gnome-software, but MESA is another story).
Maybe Ubuntu... any advice on a good Debian-based distribution, maybe rolling release ?
I can debootsrap on my old Windows partition (not booted from 2017). :grin:

I use Debian for decades and its simply the best for me.
You have to compile Mesa... its easy and you can switch to any driver version you want by environment settings, symbolic links, ldconfig, etc... so flexible.
This way you can have many drivers installed... like 20.3.1, 20.3.2, 20.3.4... 21.0.1, 21.0.2... you get it.

Maybe I should write a little docu.

View this comment - View article - View full comments

Quoting: slaapliedje

Quoting: RafiLinuxThis is interesting. If I can see it in action, I may replace my HTPCs with it.

Anything in particular you'd like to see?

I'm interested, too.

1. Price is not that bad...
a) Free Access to 100 games.
b) Two controllers instead of the "usual" one.

2. How many bluetooth devices can be connected... 4?

3. Did you test Rise... and Shadow of the Tomb Raider? Can you get stable 30-60 FPS @720 or even @1080 with low, mid, high settings? I think these are the most demanding games in my lib.

4. Is the 32GB eMMC fixed internal storage fast? How long does it need to boot into Atari OS (Debian 10)?

5. Are there 2 RAM slots or only one?

6. Can you access BIOS and enable PXE?

View this comment - View article - View full comments

Quoting: Phlebiac

Quoting: johndoeCurrently I don't see anything, that MS or Apple did to enrich the FOSS ecosystem

I'm no big fan of either, but: Apple funds development of projects like CUPS, LLVM, and Webkit (not that Webkit is terribly relevant any more). Microsoft has become a big contributor to Git, and funds the guys who made Mono.

These contributions/funds are a drop in the ocean. None of them are in-house developments.

View this comment - View article - View full comments

Quoting: Liam DaweFrankly, I think that's tin-foil hat level stuff there.

MS is using and selling FOSS everywhere... especially with Azure and now Windows (SSH+WSL).
Yes they gave us SQL 2007, .Net Core, WSL, etc. These are all things to prevent people to move away from MS+Windows.
Where is Office for Linux? And much more important where can I download all source code from them?
Aren't they "loving Linux"?
Isn't InXile and Double Fine beeing aquired by MS?

Sure, I see some things different than others, but cannot ignore facts.

Edit:
Currently I don't see anything, that MS or Apple did to enrich the FOSS ecosystem, however Stallmann.

View this comment - View article - View full comments

Quoting: GustyGhostDon't be surprised if in the next few days, articles are published detailing: John Smith, CEO/PR Rep/Analyst/whatever of Microsoft has graciously assumed the role of president of the FSF.

This is exactly what I think, too.
There is a lot more going on behind the scenes.

I also read every day linux news form "lxer.com". There you can read some more "facts" what is going on at FSF - I really don't like it.
I simply can't understand how it is possible that such companies like MS or Apple can even get a seat at FSF?! Something bad is going on IMHO.

View this comment - View article - View full comments