y: 22BE39E2FA68D8BA8DC4B43A55A16D8CE2B036DE
>
> Messages from this account are considered the best-secured and most reliable.
> Send information regarding health, wealth, or requiring higher standards of
> security to this address.
>
> Sent with [Proton Mail](https://proton.me/mail/home) secure email.
Cheers,
--
Emmanuel Vadot
.
The second is people loading from loader who updates their box from
13/14 to current, as make installkernel doesn't install the firmware
anymore it will fail, removing iwm_load from loader.conf for the
upgrade phase is the way to go I think as I don't see any other way.
> commi
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> p...@freebsd.org | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
--
Emmanuel Vadot
On Thu, 16 May 2024 22:10:16 -0700
Ryan Libby wrote:
> On Thu, May 16, 2024 at 9:56?PM Emmanuel Vadot wrote:
> >
> > On Thu, 16 May 2024 10:27:40 -0700
> > Ryan Libby wrote:
> >
> > > On Thu, May 16, 2024 at 6:00?AM David Wolfskill
> > > wrote:
cannot reproduce this here (either with i915kms or amdgpu)
but I guess that depending on the hardware version or number of screens
etc ... code path is different and might trigger this.
David can you test with
https://people.freebsd.org/~manu/0001-linuxkpi-Fix-spin_lock_init.patch
just to be sure that it fixes this issue ?
Cheers,
--
Emmanuel Vadot
On Tue, 19 Mar 2024 07:55:15 +
Alastair Hogge wrote:
> On 2024-03-19 15:23, Emmanuel Vadot wrote:
> > Hi,
>
> Hey Emmanuel,
>
> > On Tue, 19 Mar 2024 06:54:27 +
> > Alastair Hogge wrote:
> >
> >> Hello,
> >>
> >> Recentl
4d9a170c030b292
>
> Thanks.
>
I don't see why you can't build the ports.
Using would be a problem but why do you want to use it now that we
have one in base ?
Do you have any problems with the one in base ?
Cheers,
--
Emmanuel Vadot
porting, it's fixed now in
https://cgit.freebsd.org/src/commit/?id=c81495a621c461b3d3395a7c5b0e73458201c443
Note that -vn will not work but -v -n will, switching to getopt(1)
should fix that but I don't plan to work on that right now.
Cheers,
--
Emmanuel Vadot
gt; rgds,
> toomas
There is a third reason : you have multiple screens and EFI firmware
output on all of them. Never took the time to dig into this one.
--
Emmanuel Vadot
On Thu, 11 May 2023 12:03:51 +0300
Oleksandr Kryvulia wrote:
> 11.05.23 10:59, Emmanuel Vadot :
> > Hello,
> >
> > Recently I've adde the fwget(8) utility, see
> > https://cgit.freebsd.org/src/commit/?id=d198b8774d2cfb6f140893e1c6236af9e97d1497
> >
>
t so you will need to ssh into
the machine to check for similar lines like i915kms.
Thanks,
--
Emmanuel Vadot
On Fri, 27 Jan 2023 11:34:10 +0100
Emmanuel Vadot wrote:
>
> Hello,
>
> It's 2023 and I don't think that ATM have any users (but could be
> wrong hence the mail).
> Is everyone ok with switching MK_ATF to no by default ?
> This will stop installed sscop(1)
nnected, which is a
> bit annoying...
So if you have, let's say brightness at 50%, and you plug an external
monitor, brightness goes up to 100% ?
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> p...@freebsd.org | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
--
Emmanuel Vadot
On Tue, 31 Jan 2023 13:09:39 +
"Poul-Henning Kamp" wrote:
> ----
> Emmanuel Vadot writes:
>
> > > > Does backlight(8) works for you?
> > >
> > > Speaking of backlight(8): On my T14s, I see the following:
> > >
> > > I
t/backlight.c?id=e26ef41f79902991c772b59927c721aa7fa5fc64
It's not in 13.1 but will be in 13.2
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> p...@freebsd.org | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
--
Emmanuel Vadot
ruary.
Cheers,
--
Emmanuel Vadot
path
> (as per /boot/defaults/loader.conf) ? Or is it that /boot/kernel does not get
> added to the *effective* module path?
>
> Thanks!
> --
> Andriy Gapon
>
if you escape to prompt directly loader didn't loaded all it's config
so there is no modulepath defined, you need to 'boot-conf' to load the
configuration files.
Cheers,
--
Emmanuel Vadot
le = NULL;
> #endif
Hello Filipe,
Sorry for the breakage, should be fixed in 10c6af344108.
--
Emmanuel Vadot
use I see that you have
gpu-firmware-kmod so it should have installed all of them.
Anyway, pkg install gpu-firmware-radeon-kmod-redwood should solve your
problems.
> FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-85d7875d42: Mon Jun
> 6 13:40:11 CEST 2022 filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/STING
> amd64
--
Emmanuel Vadot
rm.
But you shouldn't need this, backlight(8) should work everywhere once
drm is loaded.
Cheers,
--
Emmanuel Vadot
buggy firmwares?), but you can try loader_lua.efi. The other
> cause could be grown kernel modules - we try to allocate 64MB staging area
> first, if it is not enough, then we try to get larger chunk?.
>
> Of course, screen spamming is bug, that should not happen.
>
> rgds,
> toomas
See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264021
It was bisected to the latest llvm update, I haven't digged yet.
--
Emmanuel Vadot
On Thu, 21 Apr 2022 08:51:26 -0400
Michael Butler wrote:
> On 4/21/22 03:42, Emmanuel Vadot wrote:
> >
> > Hello Michael,
> >
> > On Wed, 20 Apr 2022 23:39:12 -0400
> > Michael Butler wrote:
> >
> >> Seems this new requirement breaks kmod
t; panic: _sleep: curthread not running
> cpuid = 4
> time = 1650389478
> KDB: stack backtrace:
>
> One common trigger appears to be the use of firefox-99.0,2 from
> the ports collection.
>
> --
> Steve
>
What version of drm are you using ?
Since when do you experience this ?
drm as not changed much for a long time now except adapting a few
files for new linuxkpi addition.
Cheers,
--
Emmanuel Vadot
> *** [amdgpu_cs.o] Error code 1
>
How are you building the port, directly or with PORTS_MODULES ?
I do make passes on the warning for drm and I did for set-but-not-used
case but unfortunately this option doesn't exists in 13.0 so I couldn't
apply those in every branch.
Cheers,
--
Emmanuel Vadot
or whatever, use the graphics in it and
after shutting down the VM one could use again the GPU on FreeBSD.
It's a bit low on my todo list though.
> Also, I know the older hardware thing is hard to swallow. I get that people
> want
> that stuff to work forever because it performs adequately. However, we are
> heavily
> dependent on leveraging the work of others to support what we can, so when
> the
> work we depend on starts to bitrot, our support for that hardware suffers
> as well...
>
> Warner
>
>
> > -pete
> >
> > --
> > Pete Wright
> > p...@nomadlogic.org
> > @nomadlogicLA
> >
> >
> >
--
Emmanuel Vadot
213 lkpi_iicbb/iicbb
> > 212 lkpi_iic/lkpi_iicbb
> > 211 lkpi_iic/iicbus
> > 210 drmn/lkpi_iic
> > 56 iichid/hidbus
> >
> > Can I help debug this issue?
> >
> > I could re-install the latest version and boot with hw.dri.drm_debug or
> > dev.drm.drm_debug set?
> >
> > Or are there other settings to get a debug log from the i2c side?
> >
> > Regards, STefan
> >
> > PS: I'm keeping the CC to current@, since this might be an issue in the i2c
> > kernel code ...
>
> There are no successful lkpi_iic attachments in your output. They look like:
>
> lkpi_iic0: on drmn0
>
> Please share your `devinfo -v` output.
> Kldload output with verbose boot enabled can be helpful too.
That's because this card is probably using the bitbang part.
As stated in the commit this wasn't tested as I don't have compatible
hardware.
It's likely a timing issue in the bitbang part.
That's the main reason it's only in master and 5.7 branch of drm-kmod,
so people can debug/fix.
--
Emmanuel Vadot
On Thu, 16 Dec 2021 07:01:30 -0800
Gleb Smirnoff wrote:
> Emmanuel,
>
> On Thu, Dec 16, 2021 at 10:17:33AM +0100, Emmanuel Vadot wrote:
> E> > E> I'm not sure I understand the logic here.
> E> > E> We're keeping drivers for museum grade hardware th
On Wed, 15 Dec 2021 10:11:16 -0800
Gleb Smirnoff wrote:
> On Wed, Dec 15, 2021 at 05:52:02PM +0100, Emmanuel Vadot wrote:
> E> > > I've noticed this /sbin/sconfig binary and after looking it's for
> E> > > configuring Cronyx E1 PCI (PCI as in PCI, not PC
/reviews.freebsd.org/D30683
I'll commit this in two weeks unless there is some valid argument to
keep this.
Cheers,
--
Emmanuel Vadot
On Wed, 15 Dec 2021 10:42:36 -0500
Ed Maste wrote:
> On Wed, 15 Dec 2021 at 10:27, Emmanuel Vadot wrote:
> >
> >
> > Hello all,
> >
> > I've noticed this /sbin/sconfig binary and after looking it's for
> > configuring Cronyx E1 PCI (PCI as in
iews.freebsd.org/D33467
https://reviews.freebsd.org/D33468
https://reviews.freebsd.org/D33469
Cheers,
[1]: http://www.cronyx.ru/hardware/tau32.html
[2]: http://www.cronyx.ru/hardware/taupci.html
--
Emmanuel Vadot
On Tue, 14 Dec 2021 11:05:19 +
Alexey Dokuchaev wrote:
> On Tue, Dec 14, 2021 at 11:27:07AM +0100, Emmanuel Vadot wrote:
> > On Tue, 14 Dec 2021 10:14:24 + Alexey Dokuchaev wrote:
> > > ...
> > > I know that I had problemless desktop some 10-5 years ago, o
On Tue, 14 Dec 2021 10:14:24 +
Alexey Dokuchaev wrote:
> On Tue, Dec 14, 2021 at 09:14:27AM +0100, Emmanuel Vadot wrote:
> > On Tue, 14 Dec 2021 07:11:28 + Alexey Dokuchaev wrote:
> > > ...
> > > Oh, you know, it's about steadily deteriorating quality of
On Tue, 14 Dec 2021 07:11:28 +
Alexey Dokuchaev wrote:
> On Mon, Dec 13, 2021 at 06:32:22PM +0100, Emmanuel Vadot wrote:
> > On Mon, 13 Dec 2021 17:01:43 + Alexey Dokuchaev wrote:
> > > On Mon, Dec 13, 2021 at 07:45:07AM -0800, John Baldwin wrote:
> > > >
d fixed the beeper frequency, why we still didn't enable
> it back on by default?
>
> ./danfe
>
Because all people who wanted it off wasn't because it wasn't the
right vt100 frequency, they just wanted it off.
--
Emmanuel Vadot
has only:
>
> # ls -FTld *
> -r--r--r-- 1 root wheel 6170 Feb 1 04:48:34 2020 COPYRIGHT
> drwxr-xr-x 23 root wheel 1536 Dec 8 20:18:34 2021 boot/
> drwxr-xr-x 2 root wheel512 Apr 26 14:39:22 2020 etc/
> drwx-- 2 root wheel 33280 Nov 27 09:46:08 2019 lost+fou
epository, there is often a gap between the revision of
> > the
> > kernel and the port containing kernel modules.
> >
> > So, the question is: how can I add ports to the building process of the
> > FreeBSD
> > sources tree in the way they get build every time I build the FreeBSD-base
> > packages alongside the OS?
> >
> > Thanks in advance,
> >
> > oh
> >
>
--
Emmanuel Vadot
ed it will not be
upgraded, so I just pkg install -f drm-devel-kmod from time to time.
Cheers,
--
Emmanuel Vadot
> > installkernel" only installs the first kernel listed in KERNCONF.
>
> Good find. I honestly thought this worked as expected versus as
> written. In fact, I *thought* secondary, tertiary, etc. kernels were
> installed as /boot/kernel.KERN2, /boot/kernel.KERN3 (using the example
> above).
You need to set NO_INSTALLEXTRAKERNELS=no for that to happens (yes the
variable name and double no sucks if anyone have a patch for that that
would be awesome).
> Although, I may be misremembering, and 'kernel.KERN2.txz' may be created
> instead, although not installed/extracted. Though, we are going back at
> least seven years, and I do not even remember what I had eaten for
> dinner last night, so there's that...
>
> Glen
>
--
Emmanuel Vadot
CAM by default so if you have any spare time don't hesitate to
contact me.
Cheers,
--
Emmanuel Vadot
^
> 1 error generated.
> --- fts.o ---
> *** [fts.o] Error code 1
>
> make[4]: stopped in /usr/src/lib/libc
> ...
>
Sorry, forgot to mfc the fix for this.
Should be fixed now.
--
Emmanuel Vadot
_
> 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"
Try with
https://cgit.freeb
On Mon, 08 Feb 2021 21:05:24 +0300
Greg V wrote:
>
>
> On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
> > On 2021-02-04 17:50, Emmanuel Vadot wrote:
> >
> > [...]
> >
> >> Only happens with drm when you do what ?
> >
> > Boot
130d1c,...) at syscall+0x17d/frame 0x4074ecdc
> > > Xint0x80_syscall() at 0xffc033f9/frame 0x4074ecdc
> > > --- syscall (881410048), eip = 0x2d086faf, esp = 0xfa1e339c, ebp =
> > > 0xfa1e33c8 ---
> > > KDB: enter: panic
> >
> > This is the crash.
>
o update drm-devel-kmod from ports on
> stable/13, and took a chance that it was just an oversight :)
Indeed, just fixed this.
Thanks,
--
Emmanuel Vadot
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
On Thu, 28 Jan 2021 12:02:55 -0800
Steve Kargl wrote:
> On Thu, Jan 28, 2021 at 08:48:06PM +0100, Emmanuel Vadot wrote:
> > On Thu, 28 Jan 2021 11:15:10 -0800
> > Steve Kargl wrote:
> >
> > > All,
> > >
> > > I have finally gotten my old lap
wait on fence i915:Xorg[100156]:4 timed out (hint:0x24ad37f0S)
> drmn0: Resetting chip for hang on rcs0
> Asynchronous wait on fence i915:Xorg[100156]:4 timed out (hint:0x24ad37f0S)
> drmn0: GPU recovery timed out, cancelling all in-flight rendering.
> drmn0: Resetting chip for hang on
ijl since you also reported a build failure a few days/weeks ago for
radeon can you report if your radeon card works ? (And which one it is).
Cheers,
--
Emmanuel Vadot
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
of problems on migrating more stuff into base so that
one day we will finally have drm in base again. But I'm a bit
tired of dealing with all those problems and I've wondered a lot of
times about removing installing sources for drm-current-
On Wed, 20 Jan 2021 09:47:28 -0800
Pete Wright wrote:
>
>
> On 1/19/21 11:55 PM, Emmanuel Vadot wrote:
> >
> >> i'm happy now running the current-kmod but let me know if it'd be
> >> helpful to do any more tests or provide additional info.
> >
On Tue, 19 Jan 2021 13:29:12 -0800
Pete Wright wrote:
>
>
> On 1/19/21 1:18 PM, Emmanuel Vadot wrote:
> >
> >> interesting - so it seems like if i have drm-devel-kmod installed this
> >> will fail (missing or wrong linuxkpi_gplv2.ko). this happens both if i
On Tue, 19 Jan 2021 13:06:37 -0800
Pete Wright wrote:
>
>
> On 1/19/21 12:18 PM, Pete Wright wrote:
> >
> >
> > On 1/19/21 12:11 PM, Emmanuel Vadot wrote:
> >> On Tue, 19 Jan 2021 11:40:04 -0800
> >> Pete Wright wrote:
> >>
> >>&
o include dmesg error:
> KLD drm.ko: depends on linuxkpi_gplv2 - not available or version mismatch
> linker_load_file: /boot/modules/drm.ko - unsupported file type
> KLD amdgpu.ko: depends on drmn - not available or version mismatch
> linker_
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
t
I did, we introduce changes that breaks external kmods, you first need
to upgrade your ports/package (not your ports tree) so the new sources
are updated too and then do a make buildkernel.
That really sucks but still helps a bit when there isn't conflicted
changes in the s
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-C
rg/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Sorry that's my fault.
https://github.com/freebsd/drm-kmod/blob/master/linuxkpi/gplv2/include/linux/pci.h#L121
This if 0 should have been #if __FreeBSD_
be
rebuilt when you build a kernel.
This works as long as no changes in base need changes in those sources
too. If there is needed changes in drm-kmod sources this unfortunatelly
fails to compile, not much we can do here.
Cheers,
--
Emmanuel Vadot
On Thu, 10 Sep 2020 16:36:44 +
Glen Barber wrote:
> On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote:
> > On Thu, 3 Sep 2020 16:00:51 +
> > Glen Barber wrote:
> >
> > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot
On Thu, 3 Sep 2020 16:00:51 +
Glen Barber wrote:
> On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote:
> >
> > Hello,
> >
> > On Thu, 3 Sep 2020 15:02:45 +
> > Glen Barber wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
12).
In that case a issue at https://github.com/freebsd/drm-kmod/ would be
the best thing to do.
I'm also interested in AMD users telling me if they use the
mesa-dri option VDPAU, I can't make it work with my system (but mpv
-vo=gpu works perfectly).
--
Emmanuel Vadot
=
> 7ac321d23dd3280b7ea5c72730b6f5586027bb709365663258e7154e47071e50
> SHA256 (FreeBSD-13.0-CURRENT-arm64-aarch64-20200903-c122cf32f2a.vhd.xz) =
> cb9849e4c832d04cc6235cb42619a30ad0705aa012949e3658a5ae3d97a05ece
> SHA256 (FreeBSD-13.0-CURRENT-arm64-aarch64-20200903-c122cf32f2a.vmdk.xz) =
> 198cbd12b5
; problems due to duplicated symbols. And ideally, those duplicated
> symbols should be patched out of the ports.
>
> For example, ports-mgmt/pkg already has such a patch:
> https://github.com/freebsd/pkg/commit/7fbde60c4af4a1a07db7c5c36efbb2a495f7b1a4
> but I have no idea why it is not
On Tue, 18 Aug 2020 10:25:10 +0200
Emmanuel Vadot wrote:
> On Mon, 17 Aug 2020 20:44:38 +0200
> Jan Beich wrote:
>
> > Emmanuel Vadot writes:
> >
> > > Hello,
> > >
> > > 5.4 was finilly reached !
> > > For AMD users it means th
On Mon, 17 Aug 2020 20:44:38 +0200
Jan Beich wrote:
> Emmanuel Vadot writes:
>
> > Hello,
> >
> > 5.4 was finilly reached !
> > For AMD users it means that Navi12/14, Arctarus and Renoir should work.
> > For Intel users it means that TigerLake should wo
On Mon, 17 Aug 2020 10:56:08 -0400
Ed Maste wrote:
> On Mon, 17 Aug 2020 at 04:46, Emmanuel Vadot wrote:
> >
> > - Remove the remaining GPLv2 code to start thinking of import into
> > base.
>
> How much GPLv2 code do we have left now?
~50% of what's in
htt
is needed for making 5.4 default on 13-CURRENT and later 12.2).
All this work is under sponsorship from the FreeBSD Foundation.
--
Emmanuel Vadot
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
T
On Mon, 27 Jul 2020 14:14:13 +
Glen Barber wrote:
> On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> > On Fri, 24 Jul 2020 22:28:39 +
> > Glen Barber wrote:
> >
> > > On Sat, Jul 25, 2020 at 12:14:52AM +0200, Emmanuel Vadot wrote:
> &
On Fri, 24 Jul 2020 22:28:39 +
Glen Barber wrote:
> On Sat, Jul 25, 2020 at 12:14:52AM +0200, Emmanuel Vadot wrote:
> > On Fri, 24 Jul 2020 22:06:07 +
> > Glen Barber wrote:
> >
> > > On Fri, Jul 24, 2020 at 10:31:35PM +0200, Emmanuel Vadot wrote:
>
On Fri, 24 Jul 2020 22:06:07 +
Glen Barber wrote:
> On Fri, Jul 24, 2020 at 10:31:35PM +0200, Emmanuel Vadot wrote:
> > On Tue, 9 Jun 2020 22:04:07 +0200
> > Emmanuel Vadot wrote:
> >
> > > On Tue, 9 Jun 2020 19:56:30 +
> > > Glen Barber wrote:
On Tue, 9 Jun 2020 22:04:07 +0200
Emmanuel Vadot wrote:
> On Tue, 9 Jun 2020 19:56:30 +
> Glen Barber wrote:
>
> > On Tue, Jun 09, 2020 at 09:47:56PM +0200, Emmanuel Vadot wrote:
> > >
> > > Hello all,
> > >
> > > I've just hi
___
> 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"
--
Emmanuel Vadot
___
freebsd-current@fr
On Sat, 11 Jul 2020 00:41:53 +0300
Yuri Pankov wrote:
> Emmanuel Vadot wrote:
> [...]
>
> Hi Emmanuel,
>
> Sorry for somewhat hijacking the thread, but as you mentioned (IIRC)
> testing the vmwgfx in one of the previous mails, I'd like to ask if any
> work/fixes
it's ~20% done and I
expect the sync to be finish at the end of July.
https://github.com/freebsd/drm-kmod/tree/5.4
I don't think that I've forgotten something, if I did it will be
included in next week reports :)
All this work is under spo
On Tue, 9 Jun 2020 19:56:27 -0500
Kyle Evans wrote:
> On Tue, Jun 9, 2020 at 7:17 PM Clay Daniels wrote:
> >
> > On Tue, Jun 9, 2020 at 2:48 PM Emmanuel Vadot wrote:
> >
> > >
> > > Hello all,
> > >
> > > I've just hit again
On Tue, 9 Jun 2020 19:16:47 -0500
Clay Daniels wrote:
> On Tue, Jun 9, 2020 at 2:48 PM Emmanuel Vadot wrote:
>
> >
> > Hello all,
> >
> > I've just hit again something that I've hit (and probably others too)
> > often.
> > If a change in
On Tue, 9 Jun 2020 19:56:30 +
Glen Barber wrote:
> On Tue, Jun 09, 2020 at 09:47:56PM +0200, Emmanuel Vadot wrote:
> >
> > Hello all,
> >
> > I've just hit again something that I've hit (and probably others too)
> > often.
> > If a chang
rches.
Cheers,
--
Emmanuel Vadot
___
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 Fri, 05 Jun 2020 14:58:37 +0200
Malcolm Matalka wrote:
>
> Emmanuel Vadot writes:
>
> > On Fri, 05 Jun 2020 10:41:48 +0200
> > Malcolm Matalka wrote:
> >
> >>
> >> Emmanuel Vadot writes:
> >>
> >> >
On Fri, 05 Jun 2020 10:41:48 +0200
Malcolm Matalka wrote:
>
> Emmanuel Vadot writes:
>
> > On Fri, 05 Jun 2020 10:25:59 +0200
> > Malcolm Matalka wrote:
> >
> >>
> >> Hans Petter Selasky writes:
> >>
> >> > On 2020-06-05 06:5
hich version of kernel and kms driver are you using?
>
> I am on 361660 and drm-current-kmod-4.16.g20200320.
>
> This is not a new problem, by the way, I finally just rebooted again
> today and decided to ask.
Resume could be due to TPM being active, try to disable it in the b
//svnweb.freebsd.org/changeset/base/361138
https://svnweb.freebsd.org/changeset/base/361139
https://svnweb.freebsd.org/changeset/base/361140
https://svnweb.freebsd.org/changeset/base/361418
https://svnweb.freebsd.org/changeset/base/361419
I hope to finish 5.3 this week.
Cheers,
--
Emmanuel Vado
- i7-8665U (Whiskeylake) (Thanks to db@)
The goal for next week is obviously to continue the update for 5.2 and
updating to 5.3. The goal is to go as quickly as possible to 5.4 and
stabilise there in a branch while going further on the master branch as
5.4 is a LTS branch in
ned a bugreport: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240582
>
> --
> Martin
Hi,
thanks for the report, it's now fixed in r352389.
--
Emmanuel Vadot
___
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 Wed, 14 Aug 2019 11:04:03 -0700
John Baldwin wrote:
> On 8/14/19 10:23 AM, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> >> On 8/14/19 9:22 AM, Ian Lepore wrote:
> >>> This all sounds vaguely wr
On Wed, 14 Aug 2019 19:55:02 +0200
Niclas Zeising wrote:
> On 2019-08-14 19:23, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> >> On 8/14/19 9:22 AM, Ian Lepore wrote:
> >>> This all sounds vaguely wr
king on arm64.
Shouldn't LOCAL_MODULE have ${TARGET}.${TARGET_ARCH} as a
subdirectory ? So when you install drm-kmod-* it will only install the
source in /usr/local/modules/${TARGET}.${TARGET_ARCH}/ ? (or whatever
the correct dir is).
--
Emmanuel Vadot
_
On Mon, 29 Apr 2019 10:05:59 -0400
Kris Moore wrote:
> On Mon, Apr 29, 2019 at 9:55 AM Emmanuel Vadot
> wrote:
>
> > On Mon, 29 Apr 2019 09:25:05 -0400
> > Kris Moore wrote:
> >
> > > On Mon, Apr 29, 2019 at 8:12 AM Emmanuel Vadot
> &g
On Mon, 29 Apr 2019 09:25:05 -0400
Kris Moore wrote:
> On Mon, Apr 29, 2019 at 8:12 AM Emmanuel Vadot
> wrote:
>
> >
> > Hi Kris,
> >
> > On Sun, 28 Apr 2019 15:52:21 -0400
> > wrote:
> >
> > > FreeBSD Community,
> > >
> >
DevSummit/201905/PackageBase
>
I will be present and looking forward to work with you on this.
Cheers,
P.S. : FYI I'm working on pkgbase currently and I will have some
patches to commit soon (bsdinstall support, memstick creation that
install a pkgbase aware ins
esting (and finding leaks).
>
> ___
> 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"
--
Emmanuel Vadot
___
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"
have something commitable soon, we need the same thing for
i386 (and probably other arches).
> This is not some leap forward for anyone, and defanitly a slight
> step backwards for some, many, who knows, I put it in the 1000's,
> of users.
Again wrong, this is a big leap forward for 99% of the users.
akov
>
With UEFI Boot* variable you could do :
- Update previous partition and set BootNext to it
- If it fail next boot will be on current partition due to BootOrder
- If it succeed, change the BootOrder to have the new partition first.
--
Emmanuel Vadot
___
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"
h to a different mode)
gop set 0 (switch to the correct mode)
You can gop list (iirc) to checks the available mode.
The problem is that we are mixing serial and gop in loader.efi and
when you set one mode in serial (or for SIMPLE_TEXT_PROTOCOL) is can
mess the graphical mode.
--
Emmanuel Vadot
___
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"
ework yes.
>
> Datasheet for the pmic can be found here
> http://download.bbs.ickey.cn/201707/cfe88ee7ef01eed7a4586ce340165da0.pdf
>
> Cheers
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/li
plain :)
>
> Eric
> ___
> 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"
--
Emmanuel Vadot
___
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"
v.hdaa.0.reconfig=1
>
> Works, thank you!
Dude that's some serious shit !
Jacob, is this documented somewhere ?
I haven't read the driver code but what does as/seq etc represent
there ?
What could we do to make this
easier for users ?
> > That should make pcm0 and pcm1 "merge" i
man/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
--
Emmanuel Vadot
___
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"
__
> 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"
--
Emmanuel Vadot
ic location of the KVA.
>
> I didn't realize the kernel implementation was arch-specific. So I
> guess this comes under the category of "we'll solve that problem when
> something comes along that provides efi rt for arm32."
U-Boot doesn't provide a runtime service, I never tested the available
port of EDK2 for BBB or RPI, I guess they boot the kernel in
HYP/non-secure mode and install an runtime in secure world along with
some psci firmware.
--
Emmanuel Vadot
___
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"
1 - 100 of 117 matches
Mail list logo
