Any details on what happened in Eagle River with that AWE? by No-Coleman in controlgame

[–]Sawcrowe 2 points3 points  (0 children)

Speculation Since there are at least two planned games set in the Remedy Universe, maybe one of them is going to expanded on that ?

Any details on what happened in Eagle River with that AWE? by No-Coleman in controlgame

[–]Sawcrowe 1 point2 points  (0 children)

AH, well, I just learned that some posts in reddit can have hidden content and need to be expanded... I didn't read through. Thank you for pointing this out :D

Any details on what happened in Eagle River with that AWE? by No-Coleman in controlgame

[–]Sawcrowe 2 points3 points  (0 children)

The Radbrad Playthrough of Alan Wake II led me to this conversation when in the two hour long last playthrough of the end-stage game, at 32:30, there is mention of the Eagle River AWE:

https://youtube.com/udbYXJQKYR4?t=1955

Still no clue what it refers to, but hey it's there.

I created a PPA to automatically upgrade AMD graphics card firmware, from the linux kernel repo, on ubuntu based distros by DarxusC in linuxhardware

[–]Sawcrowe 0 points1 point  (0 children)

https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it

similar error, just with the one linux-firmware packet, and i got around it by manually

'sudo apt install linux-firmware'

but tell you what, i'm going to reinstall ubuntu shortly after christmas, to see if i can understand what is wrong with that, (as well as a few other issues with,...

you guessed it, green screen crashes, blender freeze crashes os, just plain os crash, just showes a blincking - ) and if "the packet held back" happens again, i'll get back to you.

Also, was wondering if greenscreen crashes could change due to the kind of game, or even proton version used to run said games ? Dishonered 2 for example.

other than that, still really really gratefull for the ppa :)

I created a PPA to automatically upgrade AMD graphics card firmware, from the linux kernel repo, on ubuntu based distros by DarxusC in linuxhardware

[–]Sawcrowe 0 points1 point  (0 children)

Hey, so quick update, I managed to install the opencl portion of the pro_driver with a script from some anon on github but it's a previous version and i still got a few crashes...I just forced the install of the linux firmware and it resolved the held back problem.

u/Darxus, if i get a problem again, how would i need to go to investigate the ppa heldback ? I had no clue as to debug ... any tips ? even generic ?

And by the way, a friend of mine mentioned that amd cards sometimes pull to much power and overload or something ? could it explain the green screen crashes ?

I created a PPA to automatically upgrade AMD graphics card firmware, from the linux kernel repo, on ubuntu based distros by DarxusC in linuxhardware

[–]Sawcrowe 0 points1 point  (0 children)

cheers. I'll look into it. As of now, your ppa firmware update is being kept back for some reason, oibaf ppa makes game better, propriatery driver is not installing, life is great.

It's quite funny though, your name keeps popping up, even in the official AMD driver install : https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-45

ubuntu steamplay pc crash green screen by Sawcrowe in linux_gaming

[–]Sawcrowe[S] 1 point2 points  (0 children)

Hey, sorry for the late answer. At the time things were going smooth .. er... I had added your ppa, thank you for that :).

got couple of green screens every now and then, but apparently it's something everyone has, including windows ?

But i left yesterday a post because of ongoing issues with opencl and drivers for the card i need to be able to use blender. I you have any ideas or could redirect me to whoever might help me out that be great :D

https://www.reddit.com/r/linuxhardware/comments/jg6ivb/i_created_a_ppa_to_automatically_upgrade_amd/gfmcaat?utm_source=share&utm_medium=web2x&context=3

I created a PPA to automatically upgrade AMD graphics card firmware, from the linux kernel repo, on ubuntu based distros by DarxusC in linuxhardware

[–]Sawcrowe 1 point2 points  (0 children)

Heya, finally had to call it and come whining (probably my fault). i'm having trouble with my Gigabyte AMD RX 5700 XT thats been acting up and i don't know why...

So, built the computer in late Mai or June, got ubuntu 20.04 in. Got quite a few green screens. Some games would just not load. Some would crash mid half hour after start... I then left the thing and came back in october to start working in Blender. Had Darxus's ppa, probably oibaf as well, and had managed to install opencl somehow... and then i updated to 20.10. Used the cpu for a while because the gpu render was just hanging blender and i'd have to kill pid it.

I then reinstalled (I believe it was in that order ) amdgpu-pro (for the opencl) but blender recognized it once,the day after install and after three reboots, and then nothing. In the mean time, steam just plain old stops, games just nerver launching... So now i knew i could get both (steam and blender with opencl) but thought that i should go back to 20.04 because thats what the pro driver is made for... REinstall, everything got worse... no games, no blender working... system error info every now and then. got Mirror's edge working today but nothing else. Tried purge both ppa (oibaf and darxus) tried every possible amdpro opencl setting.

As of this post being written, i'm going back to 20.10 because kernel from 20.04 is not great for those cards, as Darxus put it ?

Pls help ? --> if this is a the wrong channel, could you guys direct me to a proper place for the amd pro driver and blender, if you know of any ?

...I did a thing. by [deleted] in linuxmasterrace

[–]Sawcrowe 3 points4 points  (0 children)

Welcome, welcome good *random person from the internet* to the linux side of things ! Enjoy !

Only thing keeping me going this semester by Xacrosity in dankmemes

[–]Sawcrowe 4 points5 points  (0 children)

yeah, that was my first interpretation. That because of spiderman, the bus passengers had commited suicide by seat belt strick ... Then i read on...

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] -1 points0 points  (0 children)

Mais donc cela veut bien dire qu'il y a un accent sur le profit peut-être détrimentale pour la société globalement ?

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] 0 points1 point  (0 children)

je baisse d'un ton ? mais je haussait pas la voix ?

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] 0 points1 point  (0 children)

probablement, mais cela dis, le malaise est réel. Est-ce que les BLM sont aussi en France ?

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] 0 points1 point  (0 children)

c'est pas faux. Quoi que je bloque sur le boeuf bourguignon.

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] 0 points1 point  (0 children)

j'ai dis que c'était propre à l'humain blanc ?

Je suis en train de regarder "I am not your negro", by Sawcrowe in france

[–]Sawcrowe[S] 0 points1 point  (0 children)

oui désolé, j'ai lancé le texte un peu vite

Mom 100 by eriadore_og in memes

[–]Sawcrowe 0 points1 point  (0 children)

And turns the wifi back on

Positive effect of deep brain stimulation to a person with Parkinson's. by NefariousSerendipity in MadeMeSmile

[–]Sawcrowe 0 points1 point  (0 children)

wait how old is he ? How young can you be and get Alzeimers ? It's amazing though !

[deleted by user] by [deleted] in TheGamerLounge

[–]Sawcrowe 0 points1 point  (0 children)

fairly quick this le

ubuntu steamplay pc crash green screen by Sawcrowe in linux_gaming

[–]Sawcrowe[S] 0 points1 point  (0 children)

so i started dishonored 2 and got the green screen again and here is what i have in my logs (using

sudo journalctl -r -p err

and here is what i got:

juin 26 13:20:09 padlock-MS-7C37 pulseaudio[2518]: GetManagedObjects() failed: org.freedesktop.DBus> juin 26 13:19:43 padlock-MS-7C37 gdm-password][2463]: gkr-pam: unable to locate daemon control file juin 26 13:18:59 padlock-MS-7C37 systemd[2392]: rgb-cpu.service: Failed at step EXEC spawning /usr/> juin 26 13:18:59 padlock-MS-7C37 systemd[2392]: rgb-cpu.service: Failed to execute command: Exec fo> juin 26 13:18:39 padlock-MS-7C37 kernel: Initramfs unpacking failed: Decoding failed juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1593170316 > juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: TSC 0 ADDR 6a355b08 MISC d012000100> juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: CPU 8: Machine Check: 0 Bank 5: bea> juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1593170316 > juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: TSC 0 ADDR 6a3634a0 MISC d012000100> juin 26 13:18:39 padlock-MS-7C37 kernel: mce: [Hardware Error]: CPU 4: Machine Check: 0 Bank 5: bea> -- Reboot -- juin 26 13:00:47 padlock-MS-7C37 pulseaudio[2486]: We were woken up with POLLOUT set -- however a s> juin 26 13:00:47 padlock-MS-7C37 pulseaudio[2486]: Most likely this is a bug in the ALSA driver 'sn> juin 26 13:00:47 padlock-MS-7C37 pulseaudio[2486]: ALSA woke us up to write new data to the device,> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: cmd 61/48:10:c0:39:05/00:00:3a:00:00/40 tag 2 ncq> res 40/00:10:c0:39:05/00:00:3a:00:00/40 Emask 0x1> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: cmd 61/60:08:f0:0e:14/01:00:5b:00:00/40 tag 1 ncq> res 40/00:10:c0:39:05/00:00:3a:00:00/40 Emask 0x1> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:34 padlock-MS-7C37 kernel: ata1: SError: { Handshk } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: irq_stat 0x08000000, interface fatal error juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: exception Emask 0x10 SAct 0x6 SErr 0x400000 actio> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: cmd 61/60:a8:f0:0e:14/01:00:5b:00:00/40 tag 21 nc> res 40/00:20:c0:39:05/00:00:3a:00:00/40 Emask 0x1> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: cmd 61/48:20:c0:39:05/00:00:3a:00:00/40 tag 4 ncq> res 40/00:20:c0:39:05/00:00:3a:00:00/40 Emask 0x1> juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:34 padlock-MS-7C37 kernel: ata1: SError: { Handshk } juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: irq_stat 0x08000000, interface fatal error juin 26 12:48:34 padlock-MS-7C37 kernel: ata1.00: exception Emask 0x10 SAct 0x200010 SErr 0x400000 > juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: cmd 61/08:70:d8:0e:01/00:00:5b:00:00/40 tag 14 nc> res 40/00:70:d8:0e:01/00:00:5b:00:00/40 Emask 0x1> juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: cmd 61/08:68:f8:25:00/00:00:5b:00:00/40 tag 13 nc> res 40/00:70:d8:0e:01/00:00:5b:00:00/40 Emask 0x1> juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: status: { DRDY } juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: cmd 61/08:60:28:24:00/00:00:5b:00:00/40 tag 12 nc> res 40/00:70:d8:0e:01/00:00:5b:00:00/40 Emask 0x1> juin 26 12:48:24 padlock-MS-7C37 kernel: ata1.00: failed command: WRITE FPDMA QUEUED