On Mon, May 06, 2013 at 06:16:34PM +0400, Stas Timokhin wrote:
S> > S> > Can you please try the attached patch to kernel?
S> > S> Test of patch with nvidia-driver-310.44_1 (builded by clang from
S> > S> -CURRENT) passed successfully - booting module from /boot/loader.conf
S> > S> is OK.
S> > Sorry
Hello !
S> > Can you please try the attached patch to kernel?
S> Test of patch with nvidia-driver-310.44_1 (builded by clang from
S> -CURRENT) passed successfully - booting module from /boot/loader.conf
S> is OK.
Sorry if I wasn't clear before.
Can you please test nvidia-driver-310.44_1 with
On Mon, May 06, 2013 at 04:16:28PM +0400, Stas Timokhin wrote:
S> > d>This problems appears about 4-6 months ago after updating of
S> > -CURRENT host.
S> > d> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
S> > d> But when nvidia driver loads manually via kldload, ev
Hello !
d>This problems appears about 4-6 months ago after updating of
-CURRENT host.
d> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
d> But when nvidia driver loads manually via kldload, everything OK.
d> Nvidia driver version is 310.44 at this moment, but
On Mon, May 06, 2013 at 11:27:33AM +0400, Gleb Smirnoff wrote:
T> On Sun, May 05, 2013 at 10:01:00AM +0400, de...@stasyan.com wrote:
T> d>Hello !
T> d>
T> d>This problems appears about 4-6 months ago after updating of -CURRENT
host.
T> d> Unable to boot host with nvidia_load="YES" in
On Sun, May 05, 2013 at 10:01:00AM +0400, de...@stasyan.com wrote:
d>Hello !
d>
d>This problems appears about 4-6 months ago after updating of -CURRENT
host.
d> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
d> But when nvidia driver loads manually via kldloa
On Sun, 2013-05-05 at 10:01 +0400, de...@stasyan.com wrote:
> Hello !
>
>This problems appears about 4-6 months ago after updating of -CURRENT host.
> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
> But when nvidia driver loads manually via kldload, everything OK.
>
Hello !
This problems appears about 4-6 months ago after updating of -CURRENT
host.
Unable to boot host with nvidia_load="YES" in loader.conf because panic.
But when nvidia driver loads manually via kldload, everything OK.
Nvidia driver version is 310.44 at this moment, but problem was and
On 05.05.2013 09:24 (UTC+2), de...@stasyan.com wrote:
> Hello !
>>> This problems appears about 4-6 months ago after updating of -CURRENT
>>> host.
>>> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
>>> But when nvidia driver loads manually via kldload, everything OK
Hello !
This problems appears about 4-6 months ago after updating of -CURRENT
host.
Unable to boot host with nvidia_load="YES" in loader.conf because panic.
But when nvidia driver loads manually via kldload, everything OK.
Nvidia driver version is 310.44 at this moment, but problem was and
On 05.05.2013 08:01 (UTC+2), de...@stasyan.com wrote:
> Hello !
>
> This problems appears about 4-6 months ago after updating of -CURRENT
> host.
> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
> But when nvidia driver loads manually via kldload, everything OK.
>
Hello !
This problems appears about 4-6 months ago after updating of -CURRENT host.
Unable to boot host with nvidia_load="YES" in loader.conf because panic.
But when nvidia driver loads manually via kldload, everything OK.
Nvidia driver version is 310.44 at this moment, but problem was an
12 matches
Mail list logo
