Discussion:
radeon driver bug?
(too old to reply)
岡本健二
2018-12-04 07:19:38 UTC
Permalink
I'm using AMD HD6450 graphic card which I reported before, and faced a
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.

After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.

Thanks in advance

Kenji
岡本健二
2018-12-05 09:41:44 UTC
Permalink
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.

So, it may be the mesa problem...

Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced a
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
t***@fastmail.com
2018-12-05 14:58:48 UTC
Permalink
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
There's a known bug where the shader on r600 uses too many registers:

https://bugs.freedesktop.org/show_bug.cgi?id=99349

I encountered this bug with godot on a Radeon HD 7570, too, and it went away with the updated mesa that's in -current.
岡本健二
2018-12-06 04:26:12 UTC
Permalink
in-current means stable 6.4?

Kenji
Post by t***@fastmail.com
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
https://bugs.freedesktop.org/show_bug.cgi?id=99349
I encountered this bug with godot on a Radeon HD 7570, too, and it went
away with the updated mesa that's in -current.
岡本健二
2018-12-06 06:14:03 UTC
Permalink
also, it stull has some bugs, because the colors of some
parts are different from those of original ones.

Kenji
Sorry, I'm a novice to OpenBSD.
Yes, it's current branch of xenocara.
I updated my xenocara (stable) to that current, and build new xenocara
here.
Wow, it makes the Jahshaka works!
However, it still has some bugs, because it moves and stop suddenly and
then
move again. Whine the animation stops, the system seems to halting...
Anyway it makes much advance, I included the screenshot of it.
Kenji
PS: sorry tfrohwein, this is doubled to you
Post by 岡本健二
in-current means stable 6.4?
Kenji
Post by t***@fastmail.com
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
https://bugs.freedesktop.org/show_bug.cgi?id=99349
I encountered this bug with godot on a Radeon HD 7570, too, and it went
away with the updated mesa that's in -current.
岡本健二
2018-12-07 02:09:13 UTC
Permalink
I checked mesa-18.3.0 sources under src/gallium/drivers/r600 and compared
with those
of xenocara. File names are all same, however, individual sizes are very
different for
most of those, which would not permit me to copy those to xenocara...

Kenji
Post by 岡本健二
also, it stull has some bugs, because the colors of some
parts are different from those of original ones.
Kenji
Sorry, I'm a novice to OpenBSD.
Yes, it's current branch of xenocara.
I updated my xenocara (stable) to that current, and build new xenocara
here.
Wow, it makes the Jahshaka works!
However, it still has some bugs, because it moves and stop suddenly and
then
move again. Whine the animation stops, the system seems to halting...
Anyway it makes much advance, I included the screenshot of it.
Kenji
PS: sorry tfrohwein, this is doubled to you
Post by 岡本健二
in-current means stable 6.4?
Kenji
Post by t***@fastmail.com
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation sample
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
https://bugs.freedesktop.org/show_bug.cgi?id=99349
I encountered this bug with godot on a Radeon HD 7570, too, and it went
away with the updated mesa that's in -current.
岡本健二
2018-12-08 05:48:35 UTC
Permalink
I installed Ubuntu 18.04 to a AMD 6450 graphic card, and played
Jahshaka. It has mesa version 18.2, and runs Jahshaka very
smoothly.

The colors I reported before are same in this machine, so that
report was not correct.

Kenji
Post by 岡本健二
I checked mesa-18.3.0 sources under src/gallium/drivers/r600 and compared
with those
of xenocara. File names are all same, however, individual sizes are very
different for
most of those, which would not permit me to copy those to xenocara...
Kenji
Post by 岡本健二
also, it stull has some bugs, because the colors of some
parts are different from those of original ones.
Kenji
Sorry, I'm a novice to OpenBSD.
Yes, it's current branch of xenocara.
I updated my xenocara (stable) to that current, and build new xenocara
here.
Wow, it makes the Jahshaka works!
However, it still has some bugs, because it moves and stop suddenly and
then
move again. Whine the animation stops, the system seems to halting...
Anyway it makes much advance, I included the screenshot of it.
Kenji
PS: sorry tfrohwein, this is doubled to you
Post by 岡本健二
in-current means stable 6.4?
Kenji
Post by 岡本健二
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa version is 18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before, and faced
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google breakpad
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D animation
sample
Post by 岡本健二
Post by 岡本健二
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from radeon drm
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
https://bugs.freedesktop.org/show_bug.cgi?id=99349
I encountered this bug with godot on a Radeon HD 7570, too, and it
went away with the updated mesa that's in -current.
t***@fastmail.com
2018-12-09 16:23:31 UTC
Permalink
I found mesa-libs-18.1.9 for FreeBSD ports.
How can I get it without FreeBSD system?
Kenji
Post by 岡本健二
I installed Ubuntu 18.04 to a AMD 6450 graphic card, and played
Jahshaka. It has mesa version 18.2, and runs Jahshaka very
smoothly.
The colors I reported before are same in this machine, so that
report was not correct.
Kenji
Post by 岡本健二
I checked mesa-18.3.0 sources under src/gallium/drivers/r600 and
compared
Post by 岡本健二
Post by 岡本健二
with those
of xenocara. File names are all same, however, individual sizes are
very
Post by 岡本健二
Post by 岡本健二
different for
most of those, which would not permit me to copy those to
xenocara...
Post by 岡本健二
Post by 岡本健二
Kenji
Post by 岡本健二
also, it stull has some bugs, because the colors of some
parts are different from those of original ones.
Kenji
Sorry, I'm a novice to OpenBSD.
Yes, it's current branch of xenocara.
I updated my xenocara (stable) to that current, and build new
xenocara
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
here.
Wow, it makes the Jahshaka works!
However, it still has some bugs, because it moves and stop
suddenly and
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
then
move again. Whine the animation stops, the system seems to
halting...
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Anyway it makes much advance, I included the screenshot of it.
Kenji
PS: sorry tfrohwein, this is doubled to you
Post by 岡本健二
in-current means stable 6.4?
Kenji
Post by 岡本健二
Post by 岡本健二
This errors come from
/usr/xenocara/lib/mesa/src/gallium/drivers/r600/r600_state_common.c.
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
The mesa version of OpenBSD6.4 is 13.0.6.
I'm running this Jahshaka on Ubutu 18.04, where the mesa
version is
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
18.x.
So, it may be the mesa problem...
Kenji
Post by 岡本健二
I'm using AMD HD6450 graphic card which I reported before,
and
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
faced
Post by 岡本健二
a
Post by 岡本健二
curious thing
during running Jahshaka Studio (dev version 7.03a).
To run Jahshaka on OpenBSD 6.4 I needed to delete google
breakpad
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
temporally, which
is not the problem now.
After start to run 'Jahshaka Studio', I got start 3D
animation
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
sample
Post by 岡本健二
Post by 岡本健二
'Skeletal Animation' data to load, then
I got many errors included below which seems to come from
radeon
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
drm
Post by 岡本健二
Post by 岡本健二
driver's bug to me.
If you interested please check it.
Thanks in advance
Kenji
There's a known bug where the shader on r600 uses too many
https://bugs.freedesktop.org/show_bug.cgi?id=99349
I encountered this bug with godot on a Radeon HD 7570, too, and
it
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
Post by 岡本健二
went away with the updated mesa that's in -current.
I think you are asking for way more than you (or most misc@ readers) can handle. Porting low-level libraries from FreeBSD is far from trivial.

My advice remains: if you want working graphics, you should run OpenBSD-current, not 6.4-release. What you did is try to plug in stuff from -current into 6.4 which is huge gamble and I'm not surprised if the result is weird.

Just read the OpenBSD FAQ again for how to install -current. I would stop experimenting like you've one until you understand the system much better than now.
岡本健二
2018-12-06 22:39:45 UTC
Permalink
I'm using acme also on OpenBSD.
I don't know any better editor than that.
Of course, where acme cannot use, such as cui only, I use ed.

Kenji
Post by 岡本健二
in-current means stable 6.4?
No. Look in the FAQ. Look at the running -current page
Look at what release -> stable is.
Run -current only if you need something new, are developing base/ports
or wish to help test the software/hardware being developed.
It is not always stable. It could have new security problems temporarily
before those changes are fixed or pulled out.
However, OpenBSD runs ports and base code as a unit. You cannot run
current without making your current up to date and using the latest
version of ports/packages. Unless you find a nice spot and just stay
there.
OpenBSD is not a jumbled mess of code all over the place. It's one of
many reasons that it has fewer bugs -> better security. Also, security
specific methods are always under active development.
Please read the entire FAQ and PF Guide. Please read all of the man
pages for any commands you need to use or are interested in.
Please learn what you can do with boot -s or boot -c. You will at some
point need to use them. Search the mailing list archives for interesting
topics. Figure out how to handle the filesystem when it gets hosed
during a power failure. Figure out how to arrange your disklabel at
install to let you use growfs.
I also suggest that you learn to use ed. It's not hard to use, but it's
really, really old. It's still actively maintained because it's 100%
worth having.
The command line is so powerful once you learn to use it. We don't want
GUI interfaces for this stuff because we expect you to truly learn what
to do and why.
Have a good day,
Chris Bennett
Loading...