x 0
uhid0 at uhidev0 reportid 5: input=5, output=6, feature=0
uhub2 at uhub1 port 1 configuration 1 interface 0 "Advanced Micro Devices Hub"
rev 2.00/0.18 addr 2
ugen0 at uhub2 port 2 "Intel Bluetooth" rev 2.00/0.10 addr 3
uvideo0 at uhub2 port 3 configuration 1 interface 0 &
-chromium or even badwolf), and the thing crashes...I believe the
> culprit to be the amdgpu driver but I'm not sure. Has anyone had this
> problem? It's a known one? Can anyone point me in the right direction?
>
> PS. I usually don't touch sysctl nor login.conf...Just onc
27;t happen when no browser is
working...It would be no problem since I usually use terminal apps and no mouse
at all, but still sometimes I need to open firefox (or ungoggled-chromium or
even badwolf), and the thing crashes...I believe the culprit to be the amdgpu
driver but I'm not sure.
I've been running snapshots on my Ryzen ThinkPad T14 for about 1.5 years
and everything has been working great except for some occasional hangs
which seem to be getting more frequent. I've heard about some amdgpu
issues upstream and am not sure if this is related to that or something
%
||
2117 00:00
2117 bytes received in 0.00 seconds (3.12 MB/s)
Trying 145.238.169.11...
Requesting http://firmware.openbsd.org/firmware/7.2/amdgpu-firmware-20220913.tgz
100
On a newly installed Mini PC (NiPoGi AM02) I noticed the following messages in
dmesg:
iwm0: could not read firmware iwm-7265-17 (error 2)
iwm0: failed to load init firmware
and:
drm:pid0:amdgpu_device_parse_gpu_info_fw *ERROR* Failed to load gpu_info
firmware "amdgpu/raven2_gpu_inf
into a
shell, mount the SSD, then write "disable amdgpu" into
/etc/bsd.re-config, but unfortunately it's still happening so it might
be a different issue.
Thank you for the help anyway!
Hello,
I wanted to try that out by running the same `disable amdgpu` command in
UKC, but neither the built-in keyboard nor my external keyboard work in
UKC mode.
Is there an alternative way of disabling amdgpu when my keyboards don't
work? Perhaps I can echo to some config file durin
Hello,
I recently installed OpenBSD on a MacBook Pro 15 (2017), but I'm having
trouble getting to the actual login screen because the screen turns
blank and turns off before Xenodm even starts.
After searching around the web for a bit, I found this thread about a
problematic amdgpu fir
I would great to have hardware acceleration for Raspberry Pi. But Pi's
video hardware drivers are not open source. They are some propriety
binary bits. Even theoretically, I don't see if those binary bits can be
used within
OpenBSD system.
On Thu, Jul 21, 2022 at 2:20 AM Mihai Popescu wrote:
>
> With your email now however the original question remains: Does OpenBSD
> actually support hardware accelerated video decoding today?
General answer: NO.
A more detailed answer is like this: there is a talk on the list about
libvaapi (if i recall correctly) implementation for intel only. It wa
On 7/20/22 10:24 AM, Joseph wrote:
Hi,
Is there any hardware accelerated video decoding in OpenBSD today?
E.g. in X on AMDGPU and Intel & ARM64 built-in graphics.
My best understanding is that the X graphics rendering is indeed
accelerated on those, but video decoding is not.
HW acceler
Hi,
Thanks for new release. I have this issue for few years in my system
(maybe since OpenBSD 6.6). Whenever I suspend my system using zzz
command, It suspends well, however after I press power button I see no
video and my monitor remain in sleep mode.
I've replaced my old Radeon RX 550 video c
Hey, Im having a bit problem with my Ryzen 9 4900H. When I install the
amdgpu firmware, I only get a black screen after it loads the
firmware. Im running -current. Im wondering if anyone else has this
problem. This is the error I get. I will attach my dmesg also.
drm:pid0:psp_get_runtime_db_entry
RIC.MP
>
> kern.version=OpenBSD 6.9-beta (GENERIC.MP) #350: Sun Feb 21 11:04:59 MST 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
just sharing some information for those tracking down amdgpu issues
no issues until today
machine has been suspened several tim
On Fri, Feb 19, 2021 at 06:26:40AM +0900, rgc wrote:
> On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote:
> > kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST
> > 2021
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > kern.version=OpenB
On Fri, Feb 12, 2021 at 07:02:41PM +0900, rgc wrote:
> kern.version=OpenBSD 6.9-beta (GENERIC.MP) #323: Tue Feb 9 10:19:03 MST 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> kern.version=OpenBSD 6.9-beta (GENERIC.MP) #328: Wed Feb 10 18:08:26 MST 2021
> de
On Wed, Feb 10, 2021 at 06:46:55PM +0900, rgc wrote:
>
> sysupgraded this morning
> logged in xenodm, running stterm, tmux, spyder3, firefox-esr
> left it as-is ... went to work.
> checked it later in the day, saw the console login prompt, pressing a key
> shutdown the system. hmmn.
this is proba
On Mon, Feb 01, 2021 at 08:05:45PM +0900, rgc wrote:
> misc@
>
> it's been a few days
> some crashes still occured ..
> one time i've already killed firefox-esr and was just using stterm when X
> crashed.
>
> in the meantime, i've done a BIOS update.
> i have SVM (AMDs vmm support) enabled whic
On Mon, Jan 25, 2021 at 05:33:22PM +0900, rgc wrote:
> misc@
>
> pkg_add -u; sysupgrade -ks this morning
> i see firefox-esr pull a new gtk (iirc) build ... quirks-3.517
> on firefox is visualsource.net playing commit videos
> seems to be working good now ... and it seems firefox is more snappier
d 0 thread Xorg pid 50457
> > > [drm] *ERROR* ring gfx timeout, but soft recovered
> > > [drm] *ERROR* Error in DP aux read transaction, not writing source
> > > specific data
> > > [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197
> >
riting source specific
> > data
> > [drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197
> > [drm] *ERROR* Process information: process pid 0 thread pid 0
> > [drm] *ERROR* Error in DP aux read transaction, not writing source specific
> > data
> >
0 thread pid 0
> [drm] *ERROR* Error in DP aux read transaction, not writing source specific
> data
>
> others:
> amdgpu-firmware-20201218 firmware binary images for amdgpu(4) driver
>
> kern.version=OpenBSD 6.8-current (GENERIC.MP) #286: Thu Jan 21 09:31:59 MST
> 2021
specific data
[drm] *ERROR* ring sdma0 timeout, signaled seq=1197, emitted seq=1197
[drm] *ERROR* Process information: process pid 0 thread pid 0
[drm] *ERROR* Error in DP aux read transaction, not writing source specific data
others:
amdgpu-firmware-20201218 firmware binary images for amdgpu(4
.
(Onboard graphics works but no dedicated graphic card. Probably
neither the AMD graphics card nor the amdgpu driver caused the problem.)
For the sake of completeness, I will append the dmesg for the new setup.
Thank you and with best regards,
Jens
OpenBSD 6.8 (GENERIC.MP) #2: Sat Dec 5 07:17:48 MST
Below are various xorg.conf configurations. The only configuration
that errors is when using section "Device." If I do not have an
xorg.conf file or use section "OutputClass" X works fine. I hope this
clarifies my initial question?
xorg.conf:
Section "Device&q
On Wed, Oct 21, 2020 at 11:13:59AM -0500, flint pyrite wrote:
> Question: is the amdgpu(4) manual page up to correct and up to date?
>
> https://man.openbsd.org/amdgpu
The man page is for the xorg driver.
>
> I set up an xorg.conf file in /etc/X11/xorg.conf and was trying
Question: is the amdgpu(4) manual page up to correct and up to date?
https://man.openbsd.org/amdgpu
I set up an xorg.conf file in /etc/X11/xorg.conf and was trying to get
AMDgpu working.
The man page uses "Device" as the section. This worked as root but not
a normal user. When I chang
Hi,
I'd like to report a problem with resuming from hibernation on Thinkpad X13 AMD.
BTW, everything else seems to work just fine :)
System version: OpenBSD 6.8 GENERIC.MP#115 amd64
Relevant logs from /var/log/messages:
Oct 16 08:57:29 orion /bsd: drm0 at amdgpu0
Oct 16 08:57:29 orion /bsd: am
On Sun, Jul 19, 2020 at 04:36:37PM +1000, Jonathan Gray wrote:
> On Sun, Jul 19, 2020 at 01:13:51AM -0400, jcm...@gmail.com wrote:
> > I saw that much of the amdgpu related drm code had been updated against
> > linux 5.7 and decided to try it out using a recent snapshot. While
On Sun, Jul 19, 2020 at 01:13:51AM -0400, jcm...@gmail.com wrote:
> I saw that much of the amdgpu related drm code had been updated against
> linux 5.7 and decided to try it out using a recent snapshot. While the
> amdgpu module loads and is able to mirror to both of my displays when i
I saw that much of the amdgpu related drm code had been updated against
linux 5.7 and decided to try it out using a recent snapshot. While the
amdgpu module loads and is able to mirror to both of my displays when in
a tty, attempting to use startx or starting xenodm results in both
displays
Hi,
I'm still getting the issue from earlier where X freezes entirely and I
can't get it to work, though I've got no clue what's triggering it now,
there seem to be no *regular* outputs to /var/log/messages with the crash.
However, I was trying to trigger the bug earlier so I could hopefully
provid
On Mon, Jun 29, 2020 at 11:59:28PM -0500, Charlie Burnett wrote:
> For sure, whatever helps!
> Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sdma_v4_0: Failed to load firmware
> "amdgpu/vega20_sdma.bin"
> Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load sdma firmware!
>
For sure, whatever helps!
Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sdma_v4_0: Failed to load firmware
"amdgpu/vega20_sdma.bin"
Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load sdma firmware!
Jun 27 18:58:21 tabr /bsd: drm:pid0:psp_v11_0_init_microcode *ERROR* psp
v11.0: Fail
On Mon, Jun 29, 2020 at 11:13:49PM -0500, Charlie Burnett wrote:
> Hi,
>
> Wasn’t sure who to tell this to, but with Vega 20 hardware under -current,
> there is an issue with the firmware, where it cannot load. Manually
> installing the latest amdgpu firmware from kernel.org fixes
Hi,
Wasn’t sure who to tell this to, but with Vega 20 hardware under -current,
there is an issue with the firmware, where it cannot load. Manually
installing the latest amdgpu firmware from kernel.org fixes this seemingly.
There's also an issue that I've been unable to figure out for a
I'm running the latest amd64 snapshot (kernel #619) on a system with a
Radeon RX 550 (Polaris) GPU. glxgears and glxinfo show that OpenGL is
working and Xorg.0.log shows no errors.
When I try to enable OpenGL in Firefox by setting
layers.acceleration.force-enable to true, I see the following error
).
amdgpu_irq_add_domain: stub
amdgpu_device_resize_fb_bar: stub
amdgpu: [powerplay] Failed to retrieve minimum clocks.
amdgpu0: 1600x1200, 32bpp
wsdisplay1 at amdgpu0
wsdisplay1: screen 0-5 added (std, vt100 emulation)
... machine still responsive over network ... clean shutdown
... graphics card
On all my machines utilizing AMDGPU, I've had issues with stability, lots of
hang ups and freezes, correlating to video memory in some way (my low memory
vega iGPU hangs far quicker and in many more scenarios than my dGPU in my
desktop). After my inexperienced (but extensive) testing,
Hi,
the laptop screen goes black when amdgpu driver is loaded but the laptop is
still reponsible (i can log into it and to write commands as shutdown -r now).
Here is the dmesg with amdgpu enabled and disabled
OpenBSD 6.6-beta (GENERIC.MP) #313: Tue Sep 10 23:30:52 MDT 2019
dera...@amd64
powerplay untouched and only altering the amdgpu subdirectory
results in this error in the following error in dmesg:
initializing kernel modesetting (VEGA20 0x1002:0x66AF 0x1002:0x081E 0xC1).
amdgpu_device_resize_fb_bar: stub
amdgpu: [powerplay] smc start failed
amdgpu: [powerplay] powerplay hw i
amdgpu tracks the linux-4.19.y (lts) branch of linux-stable
currently this is 4.19.69
On Wed, Sep 04, 2019 at 10:28:51AM -0500, Charlie Burnett wrote:
> Thanks for the advice!
> Do you happen to have a link to the commit amdgpu is at currently?
>
> On Wed, Sep 4, 2019 at 9:44 AM J
${SYSTEM_HEAD} vers.o ${OBJS}
ld: error: undefined symbol: psp_v11_0_set_psp_funcs
>>> referenced by amdgpu_psp.c:62
(/usr/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_psp.c:62)
>>> amdgpu_psp.o:(psp_sw_init)
ld: error: undefined symbol: vega20_smu_funcs
>>> referenced by hw
Thanks for the advice!
Do you happen to have a link to the commit amdgpu is at currently?
On Wed, Sep 4, 2019 at 9:44 AM Jonathan Gray wrote:
> Look for individual post 4.19 linux commits that are relevant.
> We have in the past taken small patches to enable more
> generations of
m having to start from scratch?
> Best regards,
> Charlie Burnett
>
> On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote:
>
> > On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> > > Hey-
> > > I'd been messing around with the AMDGPU on
any advice where to begin if I’m having to start from scratch?
Best regards,
Charlie Burnett
On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote:
> On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> > Hey-
> > I'd been messing around with the AMDGPU on current
Been using since yesterday a custom kernel with amdgpu, on a Ryzen 5 PRO
2500U, as I saw many commits. For me now the display is now usable and
stable, still minor issues, so I can use the laptop with external
monitor.
In exchange I tried to hibernate, which was working with the UEFI vesa
Dear Listeners,
Three weeks ago I compiled a current kernel on top of
OpenBSD 6.5-current (GENERIC.MP) #128: Fri Jul 12 09:59:59 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
using the kernel configuration file
$ more AMDGPU
# $OpenBSD: GENERIC.MP,v 1.14
On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> Hey-
> I'd been messing around with the AMDGPU on current (which I'm aware is very
> experimental) and had very few issues with it using a Vega 56 GPU. I
> recently swapped to another Vega GPU (Radeon VII) an
Hey-
I'd been messing around with the AMDGPU on current (which I'm aware is very
experimental) and had very few issues with it using a Vega 56 GPU. I
recently swapped to another Vega GPU (Radeon VII) and have issues with the
display not showing anything. Still boots fine, in that I can s
xKart graphical artifacts made the game unplayable. outside
of SuperTuxKart, the cursor, and the freezes, nothing out of the ordinary was
notable in Minetest, Terraria, OpenMW, mpv, ffmpeg/ffplay, Firefox, Chromium,
xterm, and cwm. This was tested on amdgpu-firmware-20190312.
OpenBSD 6.5-current (GENER
Hello,
I noticed that amdgpu is being ported over to OpenBSD, and I was curious
if Freesync will be supported by the newly ported code? Any info/insight
folks could provide would be much appreciated.
Cheers,
Jordan
enabled the driver in kernel
configuration?
It's not switched on in GENERIC yet.
Not silly question, it wasn't enabled. I compiled a kernel from today
source with it and tested.
Suspend/resume works with qualifications here. Without amdgpu (i.e. on
GENERIC.MP, displaying with efifb) it ne
iguration?
It's not switched on in GENERIC yet.
Suspend/resume works with qualifications here. Without amdgpu (i.e. on
GENERIC.MP, displaying with efifb) it never brings any displays up on resume
(but otherwise seems to resume correctly). With amdgpu, two of the three
display
outputs are b
I saw the commit yesterday, tried recompiling the kernel but the Vega 8
seems that was not detected. I have a question, does suspend work for
you?
---
Oriol Demaria
2FFED630C16E4FF8
On 23/05/2019 03:56, Peter Piwowarski wrote:
I've tried the new amdgpu driver on my RX460 (4G VRAM), a
I've tried the new amdgpu driver on my RX460 (4G VRAM), and it seems to work
reasonably. KMS picks up the appropriate console resolution, and X appears to
work. There is some strange behavior with xrandr when setting rotation on one
of
my displays (1920x1200->1200x1920) that I don
hardware without the huge import.
Realistically, neither porting amdgpu nor extending the existing code are going
to happen any time soon. There's no straightforward path to solve this problem.
er hardware.
> > Do you have plans to port amdgpu?
> > Would particular hardware donations or other donations be of help?
>
> I have no plans regarding amdgpu.
>
> Most people seem to be interested from the point of view of polaris/vega
> which are not supported in linux 4.
I have a FirePro V5900 (Cayman part from the Northern Islands family) which I
run with EXA acceleration on 6.2. H264 video with a resolution of 3840x2160 and
25fps play flawlessly with the OpenGL acceleration in mpv (on a WSXGA+
display). Ostensibly this card can drive UHD monitors at their nati
> On Wed, Apr 25, 2018 at 10:49:53AM -0400, Joe Gidi wrote:
>>
>> > On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
>> >> drivers/gpu/drm/amd in linux has over 1.5 million lines of code.
>> Which
>> >> is multiple times larger than the complete OpenBSD kernel source...
>>
>> Thanks f
On 04/25/18 17:34, mazocomp wrote:
On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
drivers/gpu/drm/amd in linux has over 1.5 million lines of code. Which
is multiple times larger than the complete OpenBSD kernel source...
Wow, this driver is fatter than elephant.
Anyway, thank
On Wed, Apr 25, 2018 at 10:49:53AM -0400, Joe Gidi wrote:
>
> > On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
> >> drivers/gpu/drm/amd in linux has over 1.5 million lines of code. Which
> >> is multiple times larger than the complete OpenBSD kernel source...
>
> Thanks for this
deon driver per se, specs are > completely open,
>nothing prevents you from coming up with your own 'slim' driver. It's just
>that it has been decided that, > moving on, new hardware support will be
>added to amdgpu only. The size of amdgpu r
On Wed, Apr 25 2018, Jonathan Gray wrote:
[...]
> Most people seem to be interested from the point of view of polaris/vega
> which are not supported in linux 4.4. Ignoring the parts of the shared
> drm/ttm code that would have to be updated the latest
> drivers/gpu/drm/amd in linux has over 1.5
On Wed, Apr 25, 2018 at 09:08:12PM +1000, Jonathan Gray wrote:
> drivers/gpu/drm/amd in linux has over 1.5 million lines of code. Which
> is multiple times larger than the complete OpenBSD kernel source...
>
Wow, this driver is fatter than elephant.
Anyway, thank you for updating radeondrm(4),
d of
graphical corruption on Intel hardware for reasons still unclear so
xenocara remains on Mesa 13.0.6.
>
>
> The major move with Radeon graphics cards today, is their move from the
> radeondrm(4) driver (called "xf86-video-ati" by Xorg and "radeon" on
> Linux) [3
quot;radeon" on
Linux) [3], to the "amdgpu" driver (called "xf86-video-amdgpu" by Xorg)
[4].
All new Radeon are driven by the amdgpu driver:
The radeondrm driver supports all Radeon cards up to and including GCN
2. GCN 2 was released 2013 and the last GCN 2 card was release
68 matches
Mail list logo
