Just want to report in that thanks to Roger, I am running smoothly with
the amdgpu driver and no lockups for over a week and 1 kernel update.
I closed the bug I had filed and closing this thread.
Take care all, and thanks!
On 7/4/22 19:51, Roger Heflin wrote:
Once the conf file is in place
On 7/4/22 19:51, Roger Heflin wrote:
Once the conf file is in place any upgrades will keep this so long as
you don't do a clean instat..
-f and --force are the same, so I would suspect you were booted into
an older/different kernel and it rebuilt the initramfs for that older
kernel but this ke
Once the conf file is in place any upgrades will keep this so long as
you don't do a clean instat..
-f and --force are the same, so I would suspect you were booted into
an older/different kernel and it rebuilt the initramfs for that older
kernel but this kernel had been installed earlier and dracu
Looks like it took this time:
# grep -v adfasd /sys/module/*/parameters/si_support
/sys/module/*/parameters/cik_support
/sys/module/amdgpu/parameters/si_support:1
/sys/module/radeon/parameters/si_support:0
/sys/module/amdgpu/parameters/cik_support:1
/sys/module/radeon/parameters/cik_support:0
On 7/4/22 16:24, Roger Heflin wrote:
the 2nd entry needs to be on the same grep line.
But based on the output the options in that file aren't being used.
On mine both of the options are set to one on amdgpu, and 0 on radeon.
do
lsinitrd | grep enable_amdgpu_disable_radeon
you should see th
the 2nd entry needs to be on the same grep line.
But based on the output the options in that file aren't being used.
On mine both of the options are set to one on amdgpu, and 0 on radeon.
do
lsinitrd | grep enable_amdgpu_disable_radeon
you should see the file being included in the output.
If
On 7/4/22 15:19, Roger Heflin wrote:
try this and see what it shows:
grep -v adfasd /sys/module/*/parameters/si_support
/sys/module/amdgpu/parameters/si_support:0
/sys/module/radeon/parameters/si_support:1
/sys/module/*/parameters/cik_support
As root:
-bash: /sys/module/amdgpu/parameters
try this and see what it shows:
grep -v adfasd /sys/module/*/parameters/si_support
/sys/module/*/parameters/cik_support
to verify that radeon is disabled and amdgpu is enabled.
I tried on mine, an my amd gpu is a really old one while claiming to
be supported by amdgpu, acts like it is not.
On M
Finally did this:
I did not make the change when I got back to my office/home, and things
worked fine into mid-sunday when it locked again. Did a dnf update from
a character session after power cycle and new kernel, firefox, and
linuxfirmware. So decided to see how it would go.
And I could
I do not believe anything else is needed.Where dmesg said
"radeon:", it should now say "amdgpu:". amdgpu seems to be the
replacement and/or currently developed driver. And the recent
non-ryzen AMD laptops are using an older AMD cpu + ATI/AMD build-in
video, that originally were blocked from
Is it correct to assume that I don't have to install anything more to
get the amdgpu driver?
On 6/30/22 06:22, Roger Heflin wrote:
That will not work.
If I am reading the module options right (and other peoples comments),
amdgpu will not manage a si/cik chipset unless the correct _support is
s
That will not work.
If I am reading the module options right (and other peoples comments),
amdgpu will not manage a si/cik chipset unless the correct _support is
set to 1.
On Thu, Jun 30, 2022 at 12:16 AM Samuel Sieb wrote:
>
> On 6/29/22 18:25, Roger Heflin wrote:
> > The notes I found say to c
On 6/29/22 18:25, Roger Heflin wrote:
The notes I found say to create a file in /etc/modprobe.d
And say call it anything but something like
enable_amdgpu_disable_radeon.conf and put this in it:
options amdgpu si_support=1
options amdgpu cik_support=1
options radeon si_support=0
options radeon ci
On Wed, 2022-06-29 at 19:04 -0400, Robert Moskowitz wrote:
> Restarted. Had nothing running but Firefox. No problem.
>
> Went to cnn.com and waited maybe 1min and the things were locked.
>
> Whatever cnn is doing running things triggers the lockup. No
> Thunderbirds running around. QEMU is u
What version of Firefox are you using? There was a version a couple
weeks ago that snuck passed updates-testing into stable that has a
nasty memory leak. I ran into it with oomd killing it off, so I masked
oomd. Haha, bad idea, the memory leak locked the whole setup, had to
force power off (I gave
The notes I found say to create a file in /etc/modprobe.d
And say call it anything but something like
enable_amdgpu_disable_radeon.conf and put this in it:
options amdgpu si_support=1
options amdgpu cik_support=1
options radeon si_support=0
options radeon cik_support=0
and then do a "dracut --for
On 6/29/22 20:13, Roger Heflin wrote:
lspci -nnk | egrep -i "VGA|DISPLAY" -A3
lspci -nnk | egrep -i "VGA|DISPLAY" -A3
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
Subsystem: Lenovo Device [17aa:2219]
Kernel dr
On 6/29/22 19:49, Roger Heflin wrote:
What kind of video card/builtin do you have? (lspci | grep -i vga)
lspci | grep -i vga
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8330]
Only really old amd/ati cards use the radeon driver. The newer
lspci -nnk | egrep -i "VGA|DISPLAY" -A3
and see if the card reports amdgpu could also work for the card.I
am going to guess amdgpu can be used, my 2010 vintage FM2 amd can
apparently use either driver also.
On Wed, Jun 29, 2022 at 6:49 PM Roger Heflin wrote:
>
> What kind of video card/buil
What kind of video card/builtin do you have? (lspci | grep -i vga)
Only really old amd/ati cards use the radeon driver. The newer cards
use amdgpu. And your dmesg lists your bios as being a 2020 bios
release and that would indicate the hardware you are using is new so
makes me wonder why you
On 6/28/22 20:52, George N. White III wrote:
On Tue, Jun 28, 2022 at 8:40 PM Robert Moskowitz
wrote:
Samuel,
Well thanks. It is NOT the kernel as I am still locking up. But
it is
something else related to that update, as I did not get these lockups
before. I have upda
Just crashed again.
Restarted. Had nothing running but Firefox. No problem.
Went to cnn.com and waited maybe 1min and the things were locked.
Whatever cnn is doing running things triggers the lockup. No
Thunderbirds running around. QEMU is up, but image is not running.
OpenOffice is sitt
I am not entirely sure that Thuderbird is my problem.
I just had to get on $M Meetings and when the app came up, the app
window was white. Nothing. I am going to try and figure this out
later, but Meetings is not not working, when it did last week, then
something really changed.
On 6/29/22
There are lots of this error going around, going back >10 years.
Thunderbird is what is crashing, see if reverting thunderbird to the
prior version makes the crash go away.
In libraries and/or system calls there are often bugs that fail to
block bad/invalid call parameters provided by an applicat
On 6/28/22 21:06, Samuel Sieb wrote:
On 6/28/22 16:38, Robert Moskowitz wrote:
Well thanks. It is NOT the kernel as I am still locking up. But it
is something else related to that update, as I did not get these
lockups before. I have updated the bug report and sent a number of
related sel
On 6/28/22 20:52, George N. White III wrote:
On Tue, Jun 28, 2022 at 8:40 PM Robert Moskowitz
wrote:
Samuel,
Well thanks. It is NOT the kernel as I am still locking up. But
it is
something else related to that update, as I did not get these lockups
before. I have upda
On 6/28/22 16:38, Robert Moskowitz wrote:
Well thanks. It is NOT the kernel as I am still locking up. But it is
something else related to that update, as I did not get these lockups
before. I have updated the bug report and sent a number of related
selinux error details and messages
The se
On Tue, Jun 28, 2022 at 8:40 PM Robert Moskowitz
wrote:
> Samuel,
>
> Well thanks. It is NOT the kernel as I am still locking up. But it is
> something else related to that update, as I did not get these lockups
> before. I have updated the bug report and sent a number of related
> selinux err
Samuel,
Well thanks. It is NOT the kernel as I am still locking up. But it is
something else related to that update, as I did not get these lockups
before. I have updated the bug report and sent a number of related
selinux error details and messages
My video is radeon. That is showing in
Just locked again.
Now running with kernel: 15.17.12.200
On 6/28/22 06:18, Robert Moskowitz wrote:
On 6/28/22 02:27, Samuel Sieb wrote:
On 6/27/22 19:20, Robert Moskowitz wrote:
Happened again. I submitted a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2101629
If you think it's the
On 6/28/22 02:27, Samuel Sieb wrote:
On 6/27/22 19:20, Robert Moskowitz wrote:
Happened again. I submitted a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2101629
If you think it's the kernel, did you try booting the previous kernel
to see if it still happens?
Dah.
Next time!
On 6/27/22 19:20, Robert Moskowitz wrote:
Happened again. I submitted a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2101629
If you think it's the kernel, did you try booting the previous kernel to
see if it still happens?
___
users mailing li
Happened again. I submitted a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2101629
On 6/27/22 11:35, Robert Moskowitz wrote:
Sounds interesting. Will try this if nothing else gets fixed when I
get home Friday.
On 6/27/22 10:44, Roger Heflin wrote:
How did you reboot the machine?
Cur
On Mon, 2022-06-27 at 00:47 -0400, Robert Moskowitz wrote:
> Since updates Saturday night I have been having hard lock ups. It
> looks like Firefox is the trigger.
Do you have lots of tabs open? Any add-ons/extensions? Do you go
through its settings and check what all the preferences are?
I go
Sounds interesting. Will try this if nothing else gets fixed when I get
home Friday.
On 6/27/22 10:44, Roger Heflin wrote:
How did you reboot the machine?
Cursor still moving would seem to indicate paging possibly, or simply
userspace stopping.
If you have another machine ssh into it and r
On 6/27/22 10:17, stan via users wrote:
On Mon, 27 Jun 2022 08:53:48 -0400
Robert Moskowitz wrote:
And I should add that the cursor still moves around but no response
to mouse clicks or keystrokes. And video is frozen.
On 6/27/22 00:47, Robert Moskowitz wrote:
Since updates Saturday night
I forgot the command to see what my video driver is, but I recall it is
not nvidia.
On 6/27/22 09:40, Tom Horsley wrote:
On Mon, 27 Jun 2022 08:53:48 -0400
Robert Moskowitz wrote:
And I should add that the cursor still moves around but no response to
mouse clicks or keystrokes. And video is
How did you reboot the machine?
Cursor still moving would seem to indicate paging possibly, or simply
userspace stopping.
If you have another machine ssh into it and run "top" before trying what
crashes and see if top stops or keeps responding. if it keeps responding,
then what it says should be
On Mon, 27 Jun 2022 08:53:48 -0400
Robert Moskowitz wrote:
> And I should add that the cursor still moves around but no response
> to mouse clicks or keystrokes. And video is frozen.
>
> On 6/27/22 00:47, Robert Moskowitz wrote:
> > Since updates Saturday night I have been having hard lock ups.
On Mon, 27 Jun 2022 08:53:48 -0400
Robert Moskowitz wrote:
> And I should add that the cursor still moves around but no response to
> mouse clicks or keystrokes. And video is frozen.
Every time I install a new version of fedora, I give the nouveau drivers
a chance to see if they have improved,
And I should add that the cursor still moves around but no response to
mouse clicks or keystrokes. And video is frozen.
On 6/27/22 00:47, Robert Moskowitz wrote:
Since updates Saturday night I have been having hard lock ups. It
looks like Firefox is the trigger.
Lenovo X140e notebook
F35 c
41 matches
Mail list logo
