Re: radeon driver bug?
also, it stull has some bugs, because the colors of some parts are different from those of original ones. Kenji 2018年12月6日(木) 15:10 岡本健二 : > 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 > > 2018年12月6日(木) 13:26 岡本健二 : > >> in-current means stable 6.4? >> >> Kenji >> >> 2018年12月5日(水) 23:58 tfrohw...@fastmail.com : >> >>> On December 5, 2018 9:41:44 AM UTC, "岡本健二" wrote: >>> >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 >>> > >>> > >>> >2018年12月4日(火) 16:19 岡本健二 : >>> > >>> >> 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 >>> >> >>> >> >>> >>> 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. >>> >>
Re: radeon driver bug?
in-current means stable 6.4? Kenji 2018年12月5日(水) 23:58 tfrohw...@fastmail.com : > On December 5, 2018 9:41:44 AM UTC, "岡本健二" wrote: > >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 > > > > > >2018年12月4日(火) 16:19 岡本健二 : > > > >> 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 > >> > >> > > 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. >
Re: X server gbm: failed to open any driver
I started startx from local user previously... Found that from "2018/10/26 - setuid bit removed from /usr/X11R6/bin/Xorg The Xorg binary is no longer installed setuid. So startx(1) can no longer be used by non-root users. The xenodm(1) display manager has to be used." Is possible to run Xorg by startx as user since than? Why setuid has been removed from Xorg? On 12/3/2018 8:06 PM, Denis wrote: > When X server starts on OpenBSD6.4amd64 I'm getting the message below > > .. > (II) [KMS] Kernel modesetting enabled. > gbm: failed to open any driver (search paths /usr/X11R6/lib/modules/dri) > gbm: Last dlopen error: File not found > failed to load driver: redeonsi > EGL_MESA_drm_image required. > spectrwm: Welcome to spectrwm ... > > Can it be fixed? >
Re: X server gbm: failed to open any driver
I've just rebuilt Xenocara from -current with bsd-wrapper patch implemented.
Getting the error when run startx:
...
(==) Using system config derectory "/usr/X11R6/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at
"/home/deniza/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connecto to X server: Connection refused
xinit: server error
On 12/4/2018 6:08 AM, Jonathan Gray wrote:
> On Mon, Dec 03, 2018 at 08:06:18PM +0300, Denis wrote:
>> When X server starts on OpenBSD6.4amd64 I'm getting the message below
>>
>> ...
>> (II) [KMS] Kernel modesetting enabled.
>> gbm: failed to open any driver (search paths /usr/X11R6/lib/modules/dri)
>> gbm: Last dlopen error: File not found
>> failed to load driver: redeonsi
>> EGL_MESA_drm_image required.
>> spectrwm: Welcome to spectrwm ...
>>
>> Can it be fixed?
>>
>
> As the radeonsi Mesa driver depends on libLLVM and libelf it can not
> currently be included in the xenocara sets.
>
> With -current using Mesa 17.3.9 in xenocara and LLVM 6.0 from ports it
> is possible to build it yourself.
>
> Install libelf and llvm packages, apply the below patch and then build
> xenocara.
>
> Index: lib/mesa/Makefile.bsd-wrapper
> ===
> RCS file: /cvs/xenocara/lib/mesa/Makefile.bsd-wrapper,v
> retrieving revision 1.21
> diff -u -p -r1.21 Makefile.bsd-wrapper
> --- lib/mesa/Makefile.bsd-wrapper 23 Oct 2018 06:35:32 - 1.21
> +++ lib/mesa/Makefile.bsd-wrapper 4 Dec 2018 02:44:28 -
> @@ -11,7 +11,7 @@ GALLIUM_DRIVERS=swrast
>
> .if ${MACHINE} == i386 || ${MACHINE} == amd64
> DRI_DRIVERS=swrast,radeon,r200,i915,i965
> -GALLIUM_DRIVERS=swrast,r300,r600
> +GALLIUM_DRIVERS=swrast,r300,r600,radeonsi
> .endif
>
> .if ${MACHINE} == arm64 || ${MACHINE} == loongson || \
> @@ -23,7 +23,8 @@ GALLIUM_DRIVERS=swrast,r300,r600
> CONFIGURE_ARGS= --with-dri-drivers=${DRI_DRIVERS} \
> --with-gallium-drivers=${GALLIUM_DRIVERS} \
> --disable-silent-rules \
> - --disable-llvm \
> + --enable-llvm \
> + --with-llvm-prefix=/usr/local \
> --disable-glx-tls \
> --disable-regen-sources \
> --enable-gles1 --enable-gles2 \
> @@ -70,6 +71,25 @@ O2= ${O1} -fthread-jumps -fcrossjumping
>
> CONFIGURE_ARGS+= USER_CFLAGS="-O0 ${O2}"
> .endif
> +
> +PKGCONFIG_LIBDIR=
> /usr/lib/pkgconfig:${X11BASE}/lib/pkgconfig:/usr/local/lib/pkgconfig
> +
> +XENOCARA_PATH= /bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
> +
> +config.status:
> + PKG_CONFIG_LIBDIR="${PKGCONFIG_LIBDIR}" \
> + CONFIG_SITE=$(CONFIG_SITE) \
> + CC=${CC} \
> + CFLAGS="${CFLAGS}" \
> + CXX=${CXX} \
> + CXXFLAGS="${CXXFLAGS}" \
> + AR_FLAGS="cruD" \
> + MAKE="${MAKE}" \
> + PATH=$(XENOCARA_PATH) \
> + sh ${_SRCDIR}/configure --prefix=${X11BASE} \
> + --sysconfdir=/etc \
> + --mandir=${X11BASE}/man \
> + ${CONFIGURE_ARGS}
>
> ${.OBJDIR}/src/util/format_srgb.c:
> lndir -s -e obj -e obj.${MACHINE_ARCH} -e Makefile.bsd-wrapper
> ${.CURDIR}
>
Re: procmail and new grammar in smtpd.conf
On 05.12.18 13:22, Eda Sky wrote: Hi I'm preparing an update from 6.3 to 6.4 and fix the required configuration files For many years I've been using fetchmail/procmail and I do not know how to overwrite smtpd.conf to a new grammar the original rule is accept from any for domain "example.com" alias deliver to mda "/usr/local/bin/procmail -f -" \ that seems to become: action "procmail" mda "/usr/local/bin/procmail -f -" match for domain "example.com" action "procmail" I do not know how to write new rules. Everything I'm trying to do ends with syntax error. Will anyone advise me? Thank you
Re: procmail and new grammar in smtpd.conf
at 6:22 AM, Eda Sky wrote: Hi I'm preparing an update from 6.3 to 6.4 and fix the required configuration files For many years I've been using fetchmail/procmail and I do not know how to overwrite smtpd.conf to a new grammar the original rule is accept from any for domain "example.com" alias deliver to mda "/usr/local/bin/procmail -f -" I do not know how to write new rules. Everything I'm trying to do ends with syntax error. Will anyone advise me? procmail is no longer maintained. It last saw a stable release in September of 2001 In the author’s own words: https://marc.info/?l=openbsd-ports=141634350915839=2 Executive summary: delete the procmail port; the code is not safe and should not be used as a basis for any further work. -Daniel
Re: procmail and new grammar in smtpd.conf
On Wed, December 5, 2018 6:22 am, Eda Sky wrote: > > the original rule is > > accept from any for domain "example.com" alias deliver to mda > "/usr/local/bin/procmail -f -" > > I do not know how to write new rules. > Everything I'm trying to do ends with syntax error. > What have you tried?
Re: Core Dev?
On Wed, Dec 05, 2018 at 02:30:50PM +, Ahmad Bilal wrote: > - I honestly didn't intend to call him (Antoine) or anyone else for the > record, bad in anyway. I think my homework was lacking, that is the issue > here. But please don't bash me, for not knowing who Antoine is. You know I > could still be actually Antoine himself in disguise doing a public opinion > bath for himself :P (although I think, that is unbelievable at this point :D ) Even though Antoine has some past as an actor, there's no way he would write English in the same style that you do. There's something about having worked with someone for years, you can actually identify them with near certainty in their writings, and it takes a lot of skill to disguise your penmanship.
Re: radeon driver bug?
On December 5, 2018 9:41:44 AM UTC, "岡本健二" wrote: >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 > > >2018年12月4日(火) 16:19 岡本健二 : > >> 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 >> >> 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.
Re: Core Dev?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On a second thought, I will just leave this matter here, before it unnecessarily escalates into a fireball. In the end, I will just clear a few things please: - I genuinely didn't knew much about the structure of openBSD community/team or how loved Antoine is by everyone around here in general. Nice to know it now. - I honestly didn't intend to call him (Antoine) or anyone else for the record, bad in anyway. I think my homework was lacking, that is the issue here. But please don't bash me, for not knowing who Antoine is. You know I could still be actually Antoine himself in disguise doing a public opinion bath for himself :P (although I think, that is unbelievable at this point :D ) - I will read up about the AMIs and will then look at Antoine's github then (as someone suggested), thank you. I tried talking to him, and yes he seems like the nice guy everyone made him out to be. - About AWS: It was not my first choice, nor did I call it a fortress anywhere. I knew about the drawbacks of the cloud, and I did heard about past breaches at AWS. In India, due to payment-option issues, a lot of services are still not available. Even AWS was not, until sometime ago, when they set-up a dedicated subsidiary to meet the regulatory requirements here. So given that my options are limited to begin with,.. in order to scratch one more out, I have to think twice. When Nick and others pointed out that the situation is very bad (akin to using Windows Xp today), I understood that I needed to review my opinion of AWS 'properly'. But before I go on to do that, it is reasonable to ask the people who know about it that if they have some nice starting pointers. - On that account, I will still welcome any suggestions regarding where to host my first openBSD machine securely. But please email me privately. It would be very kind of you (and helpful!). - Finally, I came here (to openBSD mailing lists) with a good opinion of what you guys (and gals) have created and continue to maintain. And I still continue to think good about everyone here. Thanks for the help everyone, and my apologies, if the slight silly nature of my query was not even enough for a chuckle. Peace or Salaam to everyone. Ahmad -BEGIN PGP SIGNATURE- Version: ProtonMail Comment: https://protonmail.com wsBcBAEBCAAQBQJcB+EYCRD3irc5ItUgGgAA+v8H/08x20r6oA2NJfL3sCgt ps0oYknPsIPIXo2BI62wLYZSSHPCd/FB+eJJvl7dVlqTMws5LWNShpswJXKM kdXlU9L8XkkTRZUKOMmyh3NMdjx4O5cCG+Dkkklr9s45sOCswKMdzCQasZJH WDTD2zW/AmI54/tJmqFX9Qj/JishPGG3Gk9KMIN/q8oDICZCxzsYznbAZAaS QUY4MvHtdk0O1D2lTZ07a1iysZdPD4d/q2wKMZIXjfxEZ+orQVbDg3eQ23+s sX/yzyMqT82OQZkDRqN85OkpPYbLMR3vflLvvAma2N1hYGbbRf8jsQmQQR4c XCR9+hhNmo9+ae+G8VnlaRU= =YFxw -END PGP SIGNATURE- publickey - ssabs@protonmail.com - 0x39054E9B.asc Description: application/pgp-keys publickey - ssabs@protonmail.com - 0x39054E9B.asc.sig Description: PGP signature
procmail and new grammar in smtpd.conf
Hi I'm preparing an update from 6.3 to 6.4 and fix the required configuration files For many years I've been using fetchmail/procmail and I do not know how to overwrite smtpd.conf to a new grammar the original rule is accept from any for domain "example.com" alias deliver to mda "/usr/local/bin/procmail -f -" I do not know how to write new rules. Everything I'm trying to do ends with syntax error. Will anyone advise me? Thank you
Re: Fetching full CVS tree (-current -stable) by /usr/bin/cvs
Den ons 5 dec. 2018 kl 14:07 skrev Denis : > I'm using cvsync currently, but it is not so secure as SSH wrapped > /usr/bin/cvs fetching. > > According to OpenBSD FAQ: https://www.openbsd.org/anoncvs.html > I can follow -stable -or current by executing separate commands and it > seems I should have to separate directories for -current and -stable. cvsync gets you a clone of the repo, "cvs co" gets you a checkout, which for cvs (and svn, but not git) is not the same, which is why you would have two separate dirs, one where you checked out -current and one where you track the -stable branch. > May I fetch from public available anonymous CVS servers full cvs repo > with -current and -stable branches to have them locally by single > /usr/bin/cvs command like: cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs > checkout .. which makes this part moot, since the cvs command will not collect all branches but only the one you specify or -current if you don't. -- May the most significant bit of your life be positive.
Fetching full CVS tree (-current -stable) by /usr/bin/cvs
I'm using cvsync currently, but it is not so secure as SSH wrapped /usr/bin/cvs fetching. According to OpenBSD FAQ: https://www.openbsd.org/anoncvs.html I can follow -stable -or current by executing separate commands and it seems I should have to separate directories for -current and -stable. May I fetch from public available anonymous CVS servers full cvs repo with -current and -stable branches to have them locally by single /usr/bin/cvs command like: cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs checkout Please advice
Re: Core Dev?
On Tue, Dec 04, 2018 at 07:29:31PM -0800, Philip Guenther wrote: > On Tue, Dec 4, 2018 at 2:47 AM Marc Espie wrote: > > > (note that Antoine is the 2nd most prolific contributor to OpenBSD in terms > > of # of commits) > > > > Sure, Marc, but that's just because Antoine is such a high caliber mole > that 22 years and 22k commits in order to backdoor AWS systems that were > _clearly_ going to happen is completely believable. Hush, this is going to make the headlines on lwn or phoronix or the register. ;)
Re: use tablet interface under vm running linux
December 4, 2018 9:18 PM, "Stuart Henderson" wrote: > On 2018-12-04, rsyk...@disroot.org wrote: > >> Dear list, >> >> I am running OpenBSD desktop, but I need to use my usb-connected >> tablet wacom Intuos3, which, under OpenBSD, cannot be used together >> with pressure sensitivity. >> >> Thus, I thought I could install, say, Alpine linux under vm, and >> use the tablet via linux. I have Alpine running in vm now. But >> I don't know how to make the tablet accessible to the linux, so that >> the requested functionality would be available (i.e., probably use >> drivers from linux for the tablet). >> >> Can anybody help or make any comments? >> Thanks! >> >> Ruda > > You would need some kind of device passthrough for this approach > to work, but vmd doesn't support that, and adding that is probably > much trickier than improving usbtablet(4). Ok, thanks for the answer, though negative! I may try at one point to look at usbtablet, but at the moment it's beyond my reach. Thanks Ruda
Fw: Re: Core Dev?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Wednesday, December 5, 2018 3:40 PM, Ahmad Bilal wrote: > Woah! Where did that come from? > > Isn't this a bit too much? Perhaps you could have just ignored it Theo? > > Is it really necessary to point someone out this way? That too in a open > community? > > 'Perhaps' I'm a guy who asked a silly question in the room (who hasn't). But > that is no reason to tell everyone to stop talking to the new guy, is it? > > I think each of them is capable of thinking for themselves, and made the > choice of replying by there own will. > > And for the record, I appreciate their efforts. > > Sent from ProtonMail mobile > > Original Message > On 5 Dec 2018, 11:51, Theo de Raadt < dera...@openbsd.org> wrote: > > > Why are all of you wasting your own time chatting with Ahmad?? -BEGIN PGP SIGNATURE- Version: ProtonMail Comment: https://protonmail.com wsBcBAEBCAAQBQJcB6amCRD3irc5ItUgGgAAU0kH/jR13S7Ij5+vd9W+WGz3 WOhCyTT1ECe7aXrc51jCt8QVtapWpZ3N1k750xhNgw5u3hlZ1D2jcxaqnMiZ p32oh/ZAgltWzdC49NeLP2Zf5hZyV5GebnVfEvLhkP8uSuENQpuNGAIvT/Oe E0k1bbC/FOhXCZlCtNi1tNqkJPwkPlVUqWOAV78U5hqc4qZm1E44BZzTi38J oURojtk4alNtPWLvHBwCdhdAE/LoVa4tb2q8czj67pKQja/fnJw3oyv+Kyfn i1UL3Fso1E+0p0JarNXtH+qxK3FLXeBa5DsDUXN8YGgyqsu7cwdUHnFyymmv 40wQmJYZSrmy2Lt9hS96mrA= =a5Y5 -END PGP SIGNATURE- publickey - ssabs@protonmail.com - 0x39054E9B.asc Description: application/pgp-keys
Re: radeon driver bug?
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 2018年12月4日(火) 16:19 岡本健二 : > 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 > >
