kernel.full
Building /usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel.debug
Building /usr/obj/usr/src/amd64.amd64/sys/GENERIC/kernel
--- all ---
===> Ports module x11/nvidia-driver-470 (all)
cd /usr/ports/x11/nvidia-driver-470; env -u CC -u CXX -u CPP -u
MAKESYSPATH -u MK_AUTO_OBJ -u MAKEOBJ
related to X11) was successful.
>
> The laptop is set up to rebuild x11/nvidia-driver when the kernel
> is updated.
>
> The buildkernel step on it fails with:
>
> ...
> awk -f /usr/src/sys/conf/kmod_syms.awk nvidia-modeset.ko export_syms | xargs
> -J% objcopy % nvi
is headless, and thus does
not use anything related to X11) was successful.
The laptop is set up to rebuild x11/nvidia-driver when the kernel
is updated.
The buildkernel step on it fails with:
...
awk -f /usr/src/sys/conf/kmod_syms.awk nvidia-modeset.ko export_syms |
xargs -J% objcopy % nvidia
es
> not use anything related to X11) was successful.
>
> The laptop is set up to rebuild x11/nvidia-driver when the kernel
> is updated.
>
> The buildkernel step on it fails with:
>
> ...
> awk -f /usr/src/sys/conf/kmod_syms.awk nvidia-modeset.ko export_syms | x
On Wed, Mar 17, 2021 at 02:11:48PM +0100, Gary Jennejohn wrote:
> ...
> Well, I have obj under my home directory and do all my builds as a
> normal user rather than as root. I suspect that's why it always fails
> for me. Root owns /usr/src and /usr/ports.
Hmm... I won't claim a causal
ange was intended to
> > > fix the issue that I am now just seeing.
> > > ...
> > > So... help? What do I need to do to be able to build the kernel now?
> > >
> > > (E.g., if I need to just skip building x11/nvidia-driver once, get
> > > everythi
> So... help? What do I need to do to be able to build the kernel now?
> >
> > (E.g., if I need to just skip building x11/nvidia-driver once, get
> > everything installed, then build "normally" (with x11/nvidia-driver)
> > -- that's fine; I just need a clue.)
&
es
> not use anything related to X11) was successful.
>
> The laptop is set up to rebuild x11/nvidia-driver when the kernel
> is updated.
>
> The buildkernel step on it fails with:
>
> ...
> awk -f /usr/src/sys/conf/kmod_syms.awk nvidia-modeset.ko export_syms | x
x11/nvidia-driver when the kernel
is updated.
The buildkernel step on it fails with:
...
awk -f /usr/src/sys/conf/kmod_syms.awk nvidia-modeset.ko export_syms | xargs
-J% objcopy % nvidia-modeset.ko
===> lib (all)
===> lib/libglvnd (all)
...
===> x11/driver (all)
===> x11/ex
Was there any significant change in the base code, so that Nvidia driver
suddenly can't find usable displays upon the update to r363439 ?Error message:
NVIDIA(GPU-0): Failed to select a display subsystem.
Отправлено из Yahoo Почты для Android
ude
touch opt_global.h
cc -O2 -pipe -march=native -fno-strict-aliasing -DNV_VERSION_STRING=\"440.31\"
- -DNV_SPECTRE_V2=1 -Werror=undef -march=native -Werror -D_KERNEL -DKLD_MODULE
-nostdinc
- -Imachine -I/usr/src/sys/sys -I../common/inc -include
/usr/obj/usr/src/amd64.amd64/sys/THOR/usr/port
For me it did not solve the problem.
29.08.2018 1:03, tech-lists пишет:
> On 28/08/2018 10:14, Alex V. Petrov wrote:
>> /usr/src Revision: 338342
>>
>>
>> ===> Building for nvidia-driver-390.77
>
> Hi,
>
> Have you tried applying the patch at
> http
On 28/08/2018 10:14, Alex V. Petrov wrote:
/usr/src Revision: 338342
===> Building for nvidia-driver-390.77
Hi,
Have you tried applying the patch at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230780 ? Update your
ports tree first.
Apply it in /usr/ports
It worked for
/usr/src Revision: 338342
===> Building for nvidia-driver-390.77
nvidia_subr.c:1179:65: error: too many arguments to function call,
expected 2, have 3
kmem_free(kmem_arena, at->pte_array[0].virtual_address,
at
On 26/08/2018 13:05, John wrote:
Hi,
On Sun, 26 Aug 2018, at 13:02, Tomoaki AOKI wrote:
Hi, John.
It's broken again by r338318. (Previously broken by r338107.)
If your previous src rev is older, you could be bitten by these.
If so, update ports tree at latest rev and try the latest single
Hi,
On Sun, 26 Aug 2018, at 13:02, Tomoaki AOKI wrote:
> Hi, John.
> It's broken again by r338318. (Previously broken by r338107.)
>
> If your previous src rev is older, you could be bitten by these.
> If so, update ports tree at latest rev and try the latest single patch
> below [1]. The patch
://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230780
[2] https://bz-attachments.freebsd.org/attachment.cgi?id=196559
On Sun, 26 Aug 2018 12:07:05 +0100
John wrote:
> Hello lists,
>
> x11/nvidia-driver is broken again.
>
> Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
>
Hello,
On Sun, 26 Aug 2018, at 12:12, Kubilay Kocak wrote:
> On 26/08/2018 9:07 pm, John wrote:
> > Hello lists,
> >
> > x11/nvidia-driver is broken again.
> >
> > Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
> >
> > Tried to bui
On Sun, Aug 26, 2018 at 09:12:05PM +1000, Kubilay Kocak wrote:
> ...
> > It fails here:
>
> Hi John,
>
> It fails earlier, can you find and paste the 'error: ' line(s) ?
>
I expect the observed failure is related to the message Alan Cox sent
yesterday:
| Subject:
On 26/08/2018 9:07 pm, John wrote:
Hello lists,
x11/nvidia-driver is broken again.
Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
Tried to build with make distclean clean rmconfig && make MAKE_JOBS_UNSAFE=yes
It fails here:
Hi John,
It fails earlier, can you find a
Hello lists,
x11/nvidia-driver is broken again.
Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64.
Tried to build with make distclean clean rmconfig && make MAKE_JOBS_UNSAFE=yes
It fails here:
=kernel -Wno-sign-compare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG
-Werr
00, Alex V. Petrov wrote:
>>>>> Перенаправленное сообщение
>>>>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
>>>>> Дата: Tue, 21 Aug 2018 16:41:42 +0700
>>>>> От: Alex V. Petrov
>>>>> Кому: Free
On 22/08/2018 16:29, Alan Cox wrote:
All of kmem_alloc_attr(), kmem_alloc_contig(), and kmem_malloc() should
have their first parameter, typically kernel_arena, but sometimes
kmem_arena, removed in FreeBSD 12.
There is still one more pending change to kmem_free() that has not hit
HEAD yet.
---- Перенаправленное сообщение
>>>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
>>>> Дата: Tue, 21 Aug 2018 16:41:42 +0700
>>>> От: Alex V. Petrov
>>>> Кому: FreeBSD Ports
>>> Should be fixed as of r477761.
>>
On 08/22/2018 08:48, tech-lists wrote:
> On 22/08/2018 05:29, Manfred Antar wrote:
>>
>>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev
>>> wrote:
>>>
>>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
>>>> ---- Пер
On 22/08/2018 05:29, Manfred Antar wrote:
On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote:
On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
Перенаправленное сообщение
Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
Дата: Tue, 21 Aug 2018 16:41
On 08/21/2018 23:29, Manfred Antar wrote:
>
>> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote:
>>
>> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
>>> Перенаправленное сообщение ----
>>> Тема: nvidia-driver build error (
> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote:
>
> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
>>
>> Перенаправленное сообщение ----
>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
>> Дата: Tue, 21 Aug
On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
>
> Перенаправленное сообщение
> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
> Дата: Tue, 21 Aug 2018 16:41:42 +0700
> От: Alex V. Petrov
> Кому: FreeBSD Ports
Should be f
Перенаправленное сообщение
Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
Дата: Tue, 21 Aug 2018 16:41:42 +0700
От: Alex V. Petrov
Кому: FreeBSD Ports
cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.77\"
-D__KERNEL__ -DNVRM -Wno-unuse
533 and r334534 temporarily until nvidia-driver
>> support this change.
>
> nVidia driver port was fixed as of r471574.
>
> ./danfe
>
--
-
Alex.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/l
On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote:
> This is caused by r334533 and/or r334534 (memset-related changes).
> sysutils/lsof is also affected.
>
> You should revert r334533 and r334534 temporarily until nvidia-driver
> support this change.
nVidia driver
with r334533 (and r334534),
including fix for newly-became-prominent bug(s), because both
x11/nvidia-driver and sysutils/lsof were built OK before r334533.
Now understood that 3rd param SHALL be the size of destination "value",
NOT the size of destination "pointer".
> (als
:20 AM
To:
Cc: "freebsd-current@freebsd.org" ,
, Mateusz Guzik , Alexey Dokuchaev
,
Subject: Re: Error build nvidia-driver with r334555
On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI wrote:
This is caused by r334533 and/or r334534 (memset-related changes).
sysutils/lsof is also affe
On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI
wrote:
> This is caused by r334533 and/or r334534 (memset-related changes).
> sysutils/lsof is also affected.
>
> You should revert r334533 and r334534 temporarily until nvidia-driver
> support this change.
>
> CC'in
This is caused by r334533 and/or r334534 (memset-related changes).
sysutils/lsof is also affected.
You should revert r334533 and r334534 temporarily until nvidia-driver
support this change.
CC'ing the revision author and maintainers of both ports.
On Sun, 3 Jun 2018 18:48:01 +0700
"A
t; > >
> > >
> >
> > Aye; please ref.
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228709 for
> >
> > additional details.
> >
> > The issue has been narrowed down to the range r334529 - r334535; I'm
> >
> >
t;https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228709> for
> additional details.
>
> The issue has been narrowed down to the range r334529 - r334535; I'm
> suspecting r334533 and/or r334534. (Not that the commits are in any way
> "faulty" -- merely that the nvidia-drive
nd/or r334534. (Not that the commits are in any way
"faulty" -- merely that the nvidia-driver port may need some "evasive
action" to allow for the change).
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Mr. Trump, you reap what you sow: Th
d you mean to dereference the argument to
'sizeof' (and multiply it by the number of elements)?
memset(ci, 0, sizeof(ci));
^~
1 error generated.
*** [nvidia_subr.o] Error code 1
make[4]: stopped in
/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.59/src/nvidia
1 err
M +0200, Andriy Gapon wrote:
>>
>> I have reported a couple of nvidia-driver issues in the FreeBSD
section
>> of the nVidia developer forum, but no replies so far.
>>
>> Well, the first issue is not with the driver, but with a utili
On Thu, Dec 7, 2017 at 2:33 AM, Andriy Gapon <a...@freebsd.org> wrote:
>
> [cc-ing current@ to raise more awareness]
>
> On 05/12/2017 16:03, Alexey Dokuchaev wrote:
> > On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote:
> >>
> >> I have
On Thu, Dec 07, 2017 at 11:33:51AM +0200, Andriy Gapon wrote:
> ...
>
> I've done some work with a debugger and it seems that there is code that does
> something like this:
>
> char *last = NULL;
>
> while (1) {
> ...
>
> The binary patch is here:
[cc-ing current@ to raise more awareness]
On 05/12/2017 16:03, Alexey Dokuchaev wrote:
> On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote:
>>
>> I have reported a couple of nvidia-driver issues in the FreeBSD section
>> of the nVidia developer forum, but no repli
ient loader memory, but OK after kernel is started.
> >
> > *Accidentally backed to older version that doesn't have
> > nvidia-modeset.ko and only nvidia-modeset.ko is written in
> > /boot/loader.conf.
> >
> > ## Temporary settings for nvidia-driver when fail
n
> /boot/loader.conf.
>
> ## Temporary settings for nvidia-driver when failed loading via loader.conf
> kldstat -q -n nvidia.ko
> if [ 0 -ne $? ] ; then
> echo "Loading nvidia-driver modules via rc.conf."
> # kldload nvidia
> if [ -e /boot/modules/nvidia-
after kernel is started.
*Accidentally backed to older version that doesn't have
nvidia-modeset.ko and only nvidia-modeset.ko is written in
/boot/loader.conf.
## Temporary settings for nvidia-driver when failed loading via loader.conf
kldstat -q -n nvidia.ko
if [ 0 -ne $? ] ; then
echo
Just had a unique to me, unbootable backup [beside the point,
just a sidebar comment... ] quandry dealing with the nvidia-driver update
that mesa-libs needed. [ or was appurtenant to it, unsure... ]
12.0 - CURRENT
[ my previous 'saves' -- files to consult... were in .jpg, so no avail
Hi,
On 19.03.16 21:58, Florian Limberger wrote:
I omitted the later frame adresses, I typed this off a photo, I missed
to create a crash dump, but I can provide one if it is needed:
> panic: ufs_dirbad: /usr/home: bad dir ino 6742590 at offset 512:
I resolved my issue, the fs was in an
Hi,
I updated today to:
> FreeBSD 11.0-CURRENT (GENERIC) #2 r297039+43ceb1f(master):
> Sat Mar 19 12:06:37 CET 2016
and as always I recompiled the nvidia-driver-340, which updated from
340.76 to 340.93 Now I get reliable panics when starting KDE5 (from
area51). An older version of dwm
On 02/ 4/16 08:05 PM, Mark Johnston wrote:
On Thu, Feb 04, 2016 at 05:37:24PM -0600, Eric van Gyzen wrote:
On 02/ 3/16 10:54 AM, Eric van Gyzen wrote:
I just set up a new desktop running head with x11/nvidia-driver. I've
discovered a memory leak where pages disappear from the queues, never
On Fri, Feb 05, 2016 at 09:05:00AM -0600, Eric van Gyzen wrote:
> On 02/ 4/16 08:05 PM, Mark Johnston wrote:
> > On Thu, Feb 04, 2016 at 05:37:24PM -0600, Eric van Gyzen wrote:
> >> On 02/ 3/16 10:54 AM, Eric van Gyzen wrote:
> >>> I just set up a new desktop runni
On Thu, 4 Feb 2016 18:05:43 -0800
Mark Johnston <ma...@freebsd.org> wrote:
> On Thu, Feb 04, 2016 at 05:37:24PM -0600, Eric van Gyzen wrote:
> > On 02/ 3/16 10:54 AM, Eric van Gyzen wrote:
> > > I just set up a new desktop running head with x11/nvidia-driver. I've
&
Here are the results of the test you've suggested on my system (r293722),
nvidia-driver-304-304.128 -- two runs with the break of 40 minutes:
active inactive wire cache free total
85441 282221 280649 0 100455 748766
85488 282235 280655 0 100391 748769
On 02/ 3/16 10:54 AM, Eric van Gyzen wrote:
I just set up a new desktop running head with x11/nvidia-driver. I've
discovered a memory leak where pages disappear from the queues, never to
return. Specifically, the total of
v_active_count
v_inactive_count
v_wire_count
On Thu, Feb 04, 2016 at 05:37:24PM -0600, Eric van Gyzen wrote:
> On 02/ 3/16 10:54 AM, Eric van Gyzen wrote:
> > I just set up a new desktop running head with x11/nvidia-driver. I've
> > discovered a memory leak where pages disappear from the queues, never to
> > return. Sp
AM, Eric van Gyzen wrote:
>
>> I just set up a new desktop running head with x11/nvidia-driver. I've
>> discovered a memory leak where pages disappear from the queues, never to
>> return. Specifically, the total of
>> v_active_count
>> v_inactive_count
ted console for myself.
> Lack of time =/
>
> On Wed, Feb 3, 2016 at 2:41 PM, Eric van Gyzen <vangy...@freebsd.org>
> wrote:
>
>> On 02/03/2016 10:54, Eric van Gyzen wrote:
>> > I just set up a new desktop running head with x11/nvidia-driver. I've
>>
the corrupted console for myself.
Lack of time =/
On Wed, Feb 3, 2016 at 2:41 PM, Eric van Gyzen <vangy...@freebsd.org> wrote:
> On 02/03/2016 10:54, Eric van Gyzen wrote:
> > I just set up a new desktop running head with x11/nvidia-driver. I've
> > discovered a memory leak where
I just set up a new desktop running head with x11/nvidia-driver. I've
discovered a memory leak where pages disappear from the queues, never to
return. Specifically, the total of
v_active_count
v_inactive_count
v_wire_count
v_cache_count
v_free_count
drops, eventually becoming
On 02/03/2016 10:54, Eric van Gyzen wrote:
> I just set up a new desktop running head with x11/nvidia-driver. I've
> discovered a memory leak where pages disappear from the queues, never to
> return. Specifically, the total of
> v_active_count
> v_inactive_count
>
an error while trying to build
the x11/nvidia-driver kernel module (courtesy of /etc/src.conf:
g1-254(11.0-C)[2] cat /etc/src.conf
KERNCONF=CANARY
PORTS_MODULES=x11/nvidia-driver
PORTS_MODULES+=multimedia/cuse4bsd-kmod
PORTS_MODULES+=emulators/virtualbox-ose-kmod
WITHOUT_DEBUG_FILES=1
IWN_DEBUG=1
/S3/obj/usr/src/sys/GENERIC
amd64
I find that for my laptop, I encounter an error while trying to build
the x11/nvidia-driver kernel module (courtesy of /etc/src.conf:
Please note that the (similar) refreshes for stable/10 (@r284404)
had no problems; I have typescripts of them accessible
:/common/S3/obj/usr/src/sys/GENERIC amd64
I find that for my laptop, I encounter an error while trying to build
the x11/nvidia-driver kernel module (courtesy of /etc/src.conf:
g1-254(11.0-C)[2] cat /etc/src.conf
KERNCONF=CANARY
PORTS_MODULES=x11/nvidia-driver
PORTS_MODULES+=multimedia/cuse4bsd
Garrett Cooper yaneurab...@gmail.com wrote:
Now that vanilla head @284408 builds ( boots):
I fixed this the other day - just realized I haven't committed it.
make[6]: don't know how to make
/common/S3/obj/usr/src/sys/CANARY/common/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-346.47
/sys/CANARY/common/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-346.47/src/machine.
Stop
OK; following up: I see Simon committed r284420; after hand-appling that
(1-line fix); I performed:
make -DNOCLEAN -j16 buildkernel
make installkernel
... [mergemaster c...]
make installworld
know how to make
/common/S3/obj/usr/src/sys/CANARY/common/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-346.47/src/machine.
Stop
OK; following up: I see Simon committed r284420; after hand-appling that
(1-line fix); I performed:
make -DNOCLEAN -j16 buildkernel
make installkernel
Thanks very much for the test David
David Wolfskill da...@catwhisker.org wrote:
OK; following up: I see Simon committed r284420; after hand-appling that
(1-line fix); I performed:
...
Each was successful:
___
freebsd-current@freebsd.org mailing list
Rainer Hurling rhur...@gwdg.de wrote:
I just tried r284421 and get another error. My '/etc/src.conf' includes
'WITH_LLDB=1':
A couple of folk have issue with WITH_LLDB
seeing if I can reproduce
___
freebsd-current@freebsd.org mailing list
Hey All,
More new laptop woes. The good-ish news is that the VESA driver works, but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`, it
appears that xorg switches to a new vty, but doesn't actually bring up the
UI. I see a new console (as in vty) with a cursor at the top
On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb latt...@gmail.com wrote:
Hey All,
More new laptop woes. The good-ish news is that the VESA driver works, but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`, it
appears that xorg switches to a new vty, but doesn't actually
On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu henry.hu...@gmail.com wrote:
On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb latt...@gmail.com wrote:
Hey All,
More new laptop woes. The good-ish news is that the VESA driver works, but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run
works,
but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`,
it
appears that xorg switches to a new vty, but doesn't actually bring up
the
UI. I see a new console (as in vty) with a cursor at the top left corner.
xorg.conf is pasted here: http://ix.io/1Dr
Xorg.0.log
:
Hey All,
More new laptop woes. The good-ish news is that the VESA driver works,
but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run `startx`,
it
appears that xorg switches to a new vty, but doesn't actually bring up
the
UI. I see a new console (as in vty) with a cursor at the top
:
On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb latt...@gmail.com wrote:
Hey All,
More new laptop woes. The good-ish news is that the VESA driver works,
but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run
`startx`, it
appears that xorg switches to a new vty, but doesn't actually
:
On Wed, Dec 10, 2014 at 11:14 AM, Henry Hu henry.hu...@gmail.com
wrote:
On Wed, Dec 10, 2014 at 11:02 AM, Shawn Webb latt...@gmail.com
wrote:
Hey All,
More new laptop woes. The good-ish news is that the VESA driver
works, but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run
is that the VESA driver
works, but
x11/nvidia-driver doesn't. I'm on a Lenovo Y50-70. When I run
`startx`, it
appears that xorg switches to a new vty, but doesn't actually bring
up the
UI. I see a new console (as in vty) with a cursor at the top left
corner.
xorg.conf is pasted here
2014-11-07 23:26 GMT+03:00 O. Hartmann ohart...@web.de:
Out of the blue the build of port x11/nvidia-driver fails - portmaster is
that sloppy
that it can not check BEFORE it kills the existent driver and fails to
install after the
deletion!
The src tree is at Revision: 274250
Out of the blue the build of port x11/nvidia-driver fails - portmaster is that
sloppy
that it can not check BEFORE it kills the existent driver and fails to install
after the
deletion!
The src tree is at Revision: 274250 and with Revision r274177 the build works.
The
failure
Out of the blue the build of port x11/nvidia-driver fails - portmaster is that
sloppy
that it can not check BEFORE it kills the existent driver and fails to install
after the
deletion!
The src tree is at Revision: 274250 and with Revision r274177 the build works.
The
failure
On 2014-09-28 07:00, O. Hartmann wrote:
Am Sun, 28 Sep 2014 12:05:36 +0200
Jan Kokemüller jan.kokemuel...@gmail.com schrieb:
And as far as I know: even the Linuxulator is ways behind the recent
development and
still 32Bit (ancient, so to speak). I do not want myself having lots of
...@wonkity.com schrieb:
On Sat, 20 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
On 28.09.2014 11:41, O. Hartmann wrote:
Without nouveau driver, FreeBSD people do not have the slightes chance to play
with
OpenCL/libclc on nVidia's hardware.
Some time in the past it was possible to run CUDA/OpenCL Linux binaries
with the Nvidia driver in Linux emulation mode on FreeBSD
to run CUDA/OpenCL Linux binaries
with the Nvidia driver in Linux emulation mode on FreeBSD:
https://web.archive.org/web/20121015180221/http://blogs.freebsdish.org/jhb/2010/07/20/using-cuda-with-the-native-freebsdamd64-nvidia-driver
Not sure if that still works though.
Well, I went through
Am Sat, 20 Sep 2014 09:21:34 -0500
Larry Rosenman l...@lerctr.org schrieb:
On 2014-09-20 09:10, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver
On Sat, 27 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 09:21:34 -0500
Just for the record.
Another box, running as a server with CURRENT on-top of a Intel(R) Core(TM)
i3-3220 CPU
with Ivy-Bridge HD2500 graphics, crashes/blanks screen when going into graphics
mode with
vt() (having
Am Sat, 20 Sep 2014 09:21:34 -0500
Larry Rosenman l...@lerctr.org schrieb:
On 2014-09-20 09:10, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD
11.0-CURRENT
#2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo ThinkPad Edge E540
laptop with
CPU i5-4200M (Haswell) with integrated HD4600 Intel iGPU and dedicated
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD
11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo
ThinkPad Edge
On 2014-09-20 09:10, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD
11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST
Am Sat, 20 Sep 2014 16:10:12 +0200
O. Hartmann ohart...@zedat.fu-berlin.de schrieb:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
On Sat, 20 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD
11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST
On Sat, 20 Sep 2014, O. Hartmann wrote:
The very same CURRENT (most recent as I built world on all system today) doesn't
recognize the Haswell's HD4600 iGPU (i5-4200M). So, it seems impossible to me
that
people can report having this GPU working if even the most recent FreeBSD
CURRENT
doesn't
Am Sat, 20 Sep 2014 08:27:27 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Sat, 20 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia
schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo
ThinkPad
Edge E540 laptop with CPU i5-4200M (Haswell) with integrated HD4600
2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on
Lenovo ThinkPad
On 09/20/14 07:27, Warren Block wrote:
On Sat, 20 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
11.0-CURRENT
...@wonkity.com schrieb:
On Sat, 20 Sep 2014, O. Hartmann wrote:
Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT)
Warren Block wbl...@wonkity.com schrieb:
On Fri, 19 Sep 2014, O. Hartmann wrote:
nVidia's BLOB from port x11/nvidia-driver seems to have problems in
FreeBSD
Optimus. Please
read /usr/local/share/doc/NVIDIA_GLX-1.0/README for detail.
(The location could be different if you installed nvidia driver WITHOUT
using ports nor pkg.)
At least, my ThinkPad T420 has an option to select Optimus / internal
intel GPU / nvidia discrete GPU, and I need to select nvidia
nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD
11.0-CURRENT
#2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo ThinkPad Edge E540
laptop with
CPU i5-4200M (Haswell) with integrated HD4600 Intel iGPU and dedicated nVidia
GT 740M
(Optimus) working correctly
1 - 100 of 367 matches
Mail list logo
