Yes! That works! Thank you!
See:
https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
On 1/13/21 10:07 AM, Hans Petter Selasky wrote:
Yes! That works! Thank you!
See:
https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f
Nice! Thanks again!
Jakob
___
freebsd-current@freebsd.org mailing list
https:/
On Wed, 13 Jan 2021 10:32:01 + (UTC)
Filippo Moretti wrote:
> Good morning, my system:[root@STING
> /usr/ports/graphics/drm-current-kmod]# uname -a
> FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #16
> main-c255860-g2903606b606: Tue Jan 12 04:59:16 CET 2021
> r
On Wed, 13 Jan 2021 11:45:31 +0100
Emmanuel Vadot wrote:
> On Wed, 13 Jan 2021 10:32:01 + (UTC)
> Filippo Moretti wrote:
>
> > Good morning, my system:[root@STING
> > /usr/ports/graphics/drm-current-kmod]# uname -a
> > FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT
On Wed, 2021-01-13 at 10:37 +0100, Jakob Alvermark wrote:
> On 1/13/21 10:07 AM, Hans Petter Selasky wrote:
> > >
> > > Yes! That works! Thank you!
> > >
> >
> > See:
> >
> >
https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f
> >
> >
>
>
> Nice! Thanks again!
On Tue, Jan 12, 2021 at 07:37:28AM -0800, David Wolfskill wrote:
> On Tue, Jan 12, 2021 at 05:31:30PM +0200, Andriy Gapon wrote:
> > On 2021-01-11 14:55, David Wolfskill wrote:
> > > pci3: unknown notify 0x2
> > > ACPI Error: AE_ERROR, Thread 12 could not acquire Mutex
> > > [ACPI_MTX_Caches]
On 2021-01-13 16:03, David Wolfskill wrote:
> On Tue, Jan 12, 2021 at 07:37:28AM -0800, David Wolfskill wrote:
>> On Tue, Jan 12, 2021 at 05:31:30PM +0200, Andriy Gapon wrote:
>>> On 2021-01-11 14:55, David Wolfskill wrote:
pci3: unknown notify 0x2
ACPI Error: AE_ERROR, Thread 12 coul
On Wed, Jan 13, 2021 at 04:07:35PM +0200, Andriy Gapon wrote:
> ...
> > I believe that this is evidence in favor of a "race condition" diagnosis.
> > (In precisely what, I don't know,)
>
> I haven't followed source changes too closely as of recent.
> It might be a good idea to check for recent imp
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Thanks
Santi
OpenPGP_signature
Description: OpenPGP d
Good morning, my system:[root@STING
/usr/ports/graphics/drm-current-kmod]# uname -a
FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #16 main-c255860-g2903606b606:
Tue Jan 12 04:59:16 CET 2021
root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64
I get the following
On 1/13/21 3:31 PM, Santiago Martinez wrote:
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Try to updat
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
Santi
On 1/13/21 2:34 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:31 PM, Santiago Martinez wrote:
>> Hi there,
>>
>> Just wondering if someb
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
Maybe?
--HPS
___
freebsd-cu
On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
You need to update that
On 2020-09-12 01:24, Kevin Oberman wrote:
I'm happy to see that I am not crazy!
This is mostly anecdotal. The freezes have occurred regularly, without
question, but the details are not statistically verified. This is based
on
my perceptions. The only things I am really sure of is that the syst
Hi there,
Any chance to see fresh openssh in upcoming 13.0 release?
Thanks.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
‐‐‐ Original Message ‐‐‐
On Monday, January 11, 2021 7:37 PM, Alexander V. Chernikov
wrote:
> 11.01.2021, 14:59, "qroxana" qrox...@protonmail.com:
>
> > On Mon, 11 Jan 2021 13:25:51 +, Alexander V. Chernikov melif...@ipfw.ru
> > wrote:
> >
> > > Could you please consider clarifying
Hello,
I'm running 13-current on my Thinkpad T495 (AMD Ryzen 7 PRO 3700U)
It has the following sound devices:
cat /dev/sndstat
Installed devices:
pcm0: (play) default
pcm1: (play)
pcm2: (play)
pcm3: (play/rec)
pcm4: (play/rec)
No devices installed from userspace.
So far so good, but random
Hi,
After updating -current on my Acer laptop the touchpad stopped working.
The device is detected fine:
iichid0: at addr 0x2c irq 67 on
iicbus0
But there are no events from it.
Might it have something to do with this:
commit b1f1b07f6d412cb3ec8588a634836e26396eec70
Author: Vladimir Kond
On 13.01.2021 18:54, Jakob Alvermark wrote:
> Hi,
>
>
> After updating -current on my Acer laptop the touchpad stopped working.
>
> The device is detected fine:
>
> iichid0: at addr 0x2c irq 67 on
> iicbus0
>
> But there are no events from it.
>
> Might it have something to do with this:
>
On 2021-01-13 16:13, David Wolfskill wrote:
> On Wed, Jan 13, 2021 at 04:07:35PM +0200, Andriy Gapon wrote:
>> ...
>>> I believe that this is evidence in favor of a "race condition" diagnosis.
>>> (In precisely what, I don't know,)
>>
>> I haven't followed source changes too closely as of recent.
>
Hello:
On a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
with sources updated to last night, "buildworld" succeeds.
"buildkernel", with the appended config file, fails with:
/usr/src/sys/sys/types.h:275:16: note: forward declarat
On Wed, Jan 13, 2021 at 1:57 PM Vladimir Kondratyev
wrote:
> On 13.01.2021 18:54, Jakob Alvermark wrote:
> > Hi,
> >
> >
> > After updating -current on my Acer laptop the touchpad stopped working.
> >
> > The device is detected fine:
> >
> > iichid0: at addr 0x2c irq 67 on
> > iicbus0
> >
> > Bu
Hi HPS! thanks, that solved the issue. sorry dint realize i had to
recompile the drm.
Cheers
Santi
On 1/13/21 2:45 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
>> On 1/13/21 3:40 PM, Santiago Martinez wrote:
>>> Thanks Peter, this is what i got
>>>
>>> root@t
Hi, +1 on this, i still have issue on a supermicro.
Santi
On 1/8/21 8:11 PM, John Kennedy wrote:
> On Wed, Jan 06, 2021 at 02:19:12PM -0800, John Kennedy wrote:
>> I saw your commit of 99870c70bac7 (loader: rewrite vidc_install_font),
>> 31c2bcad7e44 (loader: remove left over call to unsetenv()
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 12/01/2021 09:45, Johan Hendriks wrote:
> Re: zpool can not create a pool after using gdisk to prepare the device
On 12/01/2021 07:50, Graham Perrin wrote:
I used gdisk(8) with a USB flash drive to:
1. zap (destroy) GPT data structures
2. blank out the MBR
3. (below) write a new GPT with a
Hans Petter Selasky :
> You need to update that DRM port you are using before the issue
> will be fixed.
I'm confused.
I have drm-current-kmod listed in PORTS_MODULES; things on that
list get built _after_ buildkernel (installkernel??) for reasons I
thought I understood.
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote:
>
> Hans Petter Selasky :
>
> > You need to update that DRM port you are using before the issue
> > will be fixed.
>
> I'm confused.
> I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built _af
On 1/13/21 5:56 PM, Vladimir Kondratyev wrote:
On 13.01.2021 18:54, Jakob Alvermark wrote:
Hi,
After updating -current on my Acer laptop the touchpad stopped working.
The device is detected fine:
iichid0: at addr 0x2c irq 67 on
iicbus0
But there are no events from it.
Might it have someth
On 1/13/21 6:52 PM, Mario Lobo wrote:
On Wed, Jan 13, 2021 at 1:57 PM Vladimir Kondratyev
wrote:
On 13.01.2021 18:54, Jakob Alvermark wrote:
Hi,
After updating -current on my Acer laptop the touchpad stopped working.
The device is detected fine:
iichid0: at addr 0x2c irq 67 on
iicbus0
B
On Wed, 13 Jan 2021 14:52:32 -0500
Robert Huff wrote:
>
> Hans Petter Selasky :
>
> > You need to update that DRM port you are using before the issue
> > will be fixed.
>
> I'm confused.
> I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built _after_
On 13.01.2021 23:29, Jakob Alvermark wrote:
> On 1/13/21 5:56 PM, Vladimir Kondratyev wrote:
>> On 13.01.2021 18:54, Jakob Alvermark wrote:
>>> Hi,
>>>
>>>
>>> After updating -current on my Acer laptop the touchpad stopped working.
>>>
>>> The device is detected fine:
>>>
>>> iichid0: at addr 0x2c
Emmanuel Vadot writes:
> That's one of the problems of having external kmods.
> drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a make buildkernel
> those sources are getting built too.
That would be the SOURCE opt
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
>
> Emmanuel Vadot writes:
>
> > That's one of the problems of having external kmods.
> > drm-current-kmod have the option by default to install it's
> > sources in /usr/local/sys/ and when doing a make buildkernel
> > those sou
On 2021-01-13 13:28, Emmanuel Vadot wrote:
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
Emmanuel Vadot writes:
>That's one of the problems of having external kmods.
>drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a
Chris writes:
> >> Further: if I have that set ... does that mean I can
> >> remove it from PORTS_MODULES?
> >
> > I don't know what that is
> eg;
> PORTS_MODULES=x11/nvidia-driver-304
> for the nvidia driver, for example. see src.conf(5).
Actually make.conf(5).
On 10/12/20 12:13 PM, Warner Losh wrote:
> Xin Li's traceback lead to code I just rewrote in current, while this code
> leads to code that's been there for a long time and hasn't been MFC'd. This
> suggests that Xin Li's backtrace isn't to be trusted, or there's two issues
> at play. Both are plaus
Since the switch to git I've been wondering how /usr/bin/uname works.
The man page is thin on details and uname.c is far too subtle.
For example, on my test box uname -a reports
FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT #7
main-c255937-g818390ce0ca5: Wed Jan 13 16:42:12 PST 2021
I should add my experience to this since its different and haven't seen
anyone else mention it.
I see the new boot loader, it's not blank, but its large text, and it's
very SLOW.
I can see each char drawn, and then when it gets to the bottom and has
to redraw all the lines to scroll up for new l
On Wed, Jan 13, 2021, 8:22 PM bob prohaska wrote:
> Since the switch to git I've been wondering how /usr/bin/uname works.
> The man page is thin on details and uname.c is far too subtle.
>
> For example, on my test box uname -a reports
> FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT #7
On 14/01/2021 04:46, Warner Losh wrote:
On Wed, Jan 13, 2021, 8:22 PM bob prohaska wrote:
… uname -KU reports
1300135 1300134
…
__FreeBSD_version is defined in sys/param.h. For -U, uname prints that
value. For -K, it asks the kernel for this value to print.
MMmmnnn where MM is the major ver
On Wed, Jan 13, 2021, 10:13 PM Graham Perrin wrote:
> On 14/01/2021 04:46, Warner Losh wrote:
>
> > On Wed, Jan 13, 2021, 8:22 PM bob prohaska wrote:
> >
> >> … uname -KU reports
> >> 1300135 1300134
> >> …
> > __FreeBSD_version is defined in sys/param.h. For -U, uname prints that
> > value. For
On Wed, Jan 13, 2021 at 10:15:32PM -0700, Warner Losh wrote:
> > > __FreeBSD_version is defined in sys/param.h. For -U, uname prints that
> > > value. For -K, it asks the kernel for this value to print.
> > >
> > > MMmmnnn where MM is the major version, mm is minor, and nnn is
> > incremental
> > >
On 1/14/21 4:49 AM, monochrome wrote:
I should add my experience to this since its different and haven't
seen anyone else mention it.
I see the new boot loader, it's not blank, but its large text, and
it's very SLOW.
I can see each char drawn, and then when it gets to the bottom and has
to red
45 matches
Mail list logo
