Re: athn in 6.5: no link. Works in 6.4

On Wed, Sep 04, 2019 at 04:55:02AM +, Pedro Fortuny Ayuso wrote: > How can I do that? I mean, commit of what files, etc? If all you need is a list of files in the source tree, the list is: sys/dev/ic/athn.c sys/dev/ic/athnvar.h sys/dev/ic/ar5008.c sys/dev/ic/ar5416.c sys/dev/ic/ar5416reg.h sy

Re: What is you motivational to use OpenBSD

User since ~2001 here, albeit intermittently. My first encounter with it was where it was used — mostly to run Postfix, Squid and BIND, if my hazy memory is trustworthy — by a private company who was effectively an ISP for many Australian Federal Government departments. I think the aspect I like m

support new

0 C Turkey P Ankara T Cankaya Z 06510 O Rakort Information Technologies I Ebubekir Okur A 2139. Street 2/11 M open...@rakort.com U http://www.rakort.com B +90-850-460-10-58 X N More than 5 years, OpenBSD setup/installation/remote administration. Network engineering, software development. Also exp

Re: AMDGPU in current issue

Hey, I’ve been trying to write a patch to get vega 20 working, but due to a screw up on my end I lost the progress I’d made. Before I start over again, I was wondering if you had any advice on how to do it? Before, I was trying to more or less just port the vega 20 hwmgr files in from FreeBSD drm n

Re: AMDGPU in current issue

Look for individual post 4.19 linux commits that are relevant. We have in the past taken small patches to enable more generations of hardware. On Wed, Sep 04, 2019 at 08:11:24AM -0500, Charlie Burnett wrote: > Hey, > I???ve been trying to write a patch to get vega 20 working, but due to a > screw

wskbd without wsdisplay

I want to use an USB-keyboard/barcode-reader on a pc-engines apu. Since the apu has no graphics card, there is no wsdisplay and the keyboard stays unconnected. # wsconscfg -k wsconscfg: /dev/ttyCcfg: Device not configured How can I read that keyboard input? Do I even have to write some

Re: AMDGPU in current issue

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 hardware. > > O

OpenBSD on AWS - pciide/wd issue

Dear all, Today I've got some headache after upgrading OpenBSD-current running on AWS. Usually I upgrade twice a month using ansible. Last time I upgraded it on Aug 13. Today I started upgrade to the snapshot built on Sep 2, the instance didn't boot. The logs showed where it stuck: pciide0:0:0:

Re: What is you motivational to use OpenBSD

On 2019-08-28 07:47, Raul Miller wrote: I would fix the issue, or use something else to get that done or abandon that project. (I am not sure why you would imagine that using OpenBSD implies not using other operating systems. It's *because* I use other operating systems that I like using OpenBSD

Re: AMDGPU in current issue

My apologies for bothering the mailing list once more- I found the relevant commit for this in the linux git history, and found the relevant changes. I added those changes locally on my machine, however when I compile I get the following: ld -T ld.script -X --warn-common -nopie -o bsd ${SYSTEM_HEAD

Re: AMDGPU in current issue

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 Jonathan Gray wr

Re: OpenBSD on AWS - pciide/wd issue

On Wed, Sep 4, 2019 at 12:56 PM Pavel Korovin wrote: > The logs showed where it stuck: > > pciide0:0:0: not ready, st=0x0, err=0x00 > wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying > pciide0:0:0: not ready, st=0x0, err=0x00 > wd0c: device timeout reading fsbn 0 (wd0 bn 0;