Date:Sun, 8 Jan 2023 02:46:48 + (UTC)
From:NetBSD Test Fixture
Message-ID: <167314600759.7791.10321313004943192...@babylon5.netbsd.org>
| The NetBSD-current/i386 build is working again.
Note that this does not relate to the current build failure, this message
Updating src tree:
P src/doc/CHANGES
P src/sbin/fsck_ffs/main.c
P src/sbin/fsck_ffs/pass1.c
P src/sbin/fsck_ffs/pass1b.c
P src/sbin/fsck_ffs/pass4.c
P src/sbin/fsck_ffs/pass5.c
P src/sbin/fsck_ffs/setup.c
P src/sbin/fsdb/fsdb.c
P src/sbin/newfs/mkfs.c
P src/sbin/resize_ffs/resize_ffs.c
P
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2023.01.06.17.06.33 christos
src/external/gpl3/binutils/usr.bin/ld/Makefile,v 1.37
Logs can be found at:
On Sat, Jan 07, 2023 at 03:42:00PM -, Christos Zoulas wrote:
> In article ,
> Thomas Klausner wrote:
> >Hi!
> >
> >I've just replaced my 10.99.2/20221231 userland (kernel slightly
> >older, but also 10.99.2) with a 10.99.2/20230107 kernel+userland.
> >
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2023.01.07.19.41.30.
An extract from the build.sh output follows:
--- dependall-fsck_ffs ---
matthew green wrote:
> the old drm code for i915 is probably extremely obsolete at this
> point. i don't think it works on anything that current does
> (or least, before the latest refresh -- i think there are still
> a couple of blank screens, but i think newer than this code would
> support
Side note: we are collecting all bug reports for the new DRM/KMS that
should be fixed before the 10.0 release here:
https://wiki.netbsd.org/releng/netbsd-10/
If you know of any other PRs that should be listed there, please let me know.
Martin
the old drm code for i915 is probably extremely obsolete at this
point. i don't think it works on anything that current does
(or least, before the latest refresh -- i think there are still
a couple of blank screens, but i think newer than this code would
support anyway.)
the only reason i
Am Sat, Jan 07, 2023 at 10:00:39AM +0100 schrieb Thomas Klausner:
> #9 0x7f59b6644282 in scm_error (key=0x7f59a6a41560,
> subr=subr@entry=0x7f59b670f487 "scm_hash_fn_get_handle",
> message=message@entry=0x7f59b670c9e0 "Wrong type argument in position ~A
> (expecting ~A): ~S",
>
Just reviving this thread in the new year.
Story so far for my laptop is:
- On Linux both eDP and HDMI work fine, even with rotation. Linux uses
intel driver with SNA acceleration.
- On NetBSD 10.0 BETA, only intel driver works, only with UXA
acceleration. No other driver or no other
On Sat, Jan 07, 2023 at 03:58:21PM +0700, Robert Elz wrote:
> I doubt it is possible to make i915drm work on -10 or HEAD
Ok. I get several linker errors if I enable i915drm, showing a few of
them.
ld: i915_dma.o:(.data+0x88): undefined reference to `i915_irq_emit'
ld:
In article ,
Thomas Klausner wrote:
>Hi!
>
>I've just replaced my 10.99.2/20221231 userland (kernel slightly
>older, but also 10.99.2) with a 10.99.2/20230107 kernel+userland.
>
>Now gnucash dumps core on startup:
Could be rtld related. Can you try with the older ld_elf.so?
christos
Hi!
I've just replaced my 10.99.2/20221231 userland (kernel slightly
older, but also 10.99.2) with a 10.99.2/20230107 kernel+userland.
Now gnucash dumps core on startup:
(gdb) bt
#0 0x in ?? ()
#1 0x7f59b66414b1 in scm_c_hook_run (hook=0x7f59b695d140
, data=0x0
Date:Sat, 7 Jan 2023 13:41:13 +0530
From:Mayuresh
Message-ID: <20230107081113.bdzqjxuihxxszvmr@localhost>
| Now stripping off all the context and just seeking to know the difference
| between these two drivers:
|
| $ config -x | grep i915
|
Have requested more information about these on multiple threads.
Now stripping off all the context and just seeking to know the difference
between these two drivers:
$ config -x | grep i915
#i915drm* at drm? # Intel i915, i945 DRM driver
i915drmkms* at pci? dev ?
15 matches
Mail list logo
