Re: HEADS UP: Enabling vt(4) by default

2014-12-30 Thread Hans Petter Selasky

Hi,

I just had a quick look at "vt_core.c" with regard to callouts. And have 
the following comments:


1) Make sure callout_reset(), callout_schedule() and callout_stop() is 
always called locked. When no lock is specified, that means Giant!


2) callout_drain() must have an unlocked sleeping context, else use 
callout_stop() with the mutex specified in callout_init_mtx() to get 
atomicity.


For now adding MTX_RECURSE to "mtx_init(&main_vd->vd_lock, "vtdev", 
NULL, MTX_DEF | MTX_RECURSE)" solved my problem temporarily, because 
callout_drain() tried to get the vd_lock, which was already taken.


--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-12-29 Thread Hans Petter Selasky

Hi,

FreeBSD 11-current:

I had a panic, that VT tries to drain a callout while a mutex is locked 
rooting down from somewhere:


vt_late_window_switch()

When starting X11. Try to apply my kernel timeout work in progress patch 
in the new "[RFC] kern/kern_timeout.c rewrite in progress" thread and 
you will see right away.


I can get full backtrace if you can't figure this out. Just out of time 
right now.


Thank you!

--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Chris H
On Wed, 05 Nov 2014 22:29:53 +0100 Hans Petter Selasky  wrote

> On 11/05/14 22:27, Chris H wrote:
> > On Wed, 5 Nov 2014 12:55:51 -0700 (MST) Warren Block 
> > wrote >
> >> On Wed, 5 Nov 2014, Chris H wrote:
> >>
> >>> On Wed, 5 Nov 2014 08:15:04 -0700 (MST) Warren Block 
> >>> wrote >
>  On Wed, 5 Nov 2014, Chris H wrote:
> > On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
> > wrote >>
> >> No, video mode won't work with the nVidia blob.  That requires
> >> a KMS (in-kernel) driver.
> >
> > Thank you for the reply, Gary.
> >
> > Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?
> 
>  Or Intel, or anything with KMS drivers.
> >>>
> >>> Thanks. Everything I manage, is using nVidia. Looks like
> >>> the kms VESA might work. But I'm not sure if there would
> >>> be any appreciable gain going that route (assuming it's even
> >>> possible).
> >>
> >> It's worth asking Nvidia directly.  I would not be optimistic about
> >> that, but it's easy to try, and they might surprise everyone.
> >>
> >> Another option might be nouveau.  Don't know the current status of
> >> whether that works on FreeBSD, though.
> > LOL funny you should bring that up, just now.
> > Prior to a fresh install on bare metal. I always boot to a gpartd
> > CD. I use it to easily see, and quickly blank the disk(s). I only
> > choose it, because it's quick-n-easy. It is also the perfect tool
> > to wipe that evil grub[2] off the MBR. Which has given me no end
> > of grief after evaluating some Linux distro. Anyhow, point being;
> > the desktop is powered by nouveau. I've never had an issue with it,
> > and it always seems to pick the "right" resolution/frequency. So,
> > because of that. I was already thinking of investigating that route.
> > As to talking to nVidia. My past experiences in that regard were,
> > shall I say; less than ideal. They're always friendly. But getting
> > anything that might "uncover" any coveted driver info, always fell
> > short of helpful. :)
> >
> > Thanks for the reply, and helpful information, Warren.
> >
> > --Chris
> 
> Hi,
> 
> FYI:
> 
> The KMS stuff seems to work on my intel HD graphics based MAC. Finally I 
> can switch back to the console!
Thanks for sharing that, Hans. I'm looking to pick up some Mac hardware
to put FreeBSD on. Now, I'm even more anxious to get it. :)

--Chris

> 
> --HPS
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Hans Petter Selasky

On 11/05/14 22:27, Chris H wrote:

On Wed, 5 Nov 2014 12:55:51 -0700 (MST) Warren Block  wrote


On Wed, 5 Nov 2014, Chris H wrote:


On Wed, 5 Nov 2014 08:15:04 -0700 (MST) Warren Block 
wrote >

On Wed, 5 Nov 2014, Chris H wrote:

On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
wrote >>

No, video mode won't work with the nVidia blob.  That requires
a KMS (in-kernel) driver.


Thank you for the reply, Gary.

Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?


Or Intel, or anything with KMS drivers.


Thanks. Everything I manage, is using nVidia. Looks like
the kms VESA might work. But I'm not sure if there would
be any appreciable gain going that route (assuming it's even
possible).


It's worth asking Nvidia directly.  I would not be optimistic about
that, but it's easy to try, and they might surprise everyone.

Another option might be nouveau.  Don't know the current status of
whether that works on FreeBSD, though.

LOL funny you should bring that up, just now.
Prior to a fresh install on bare metal. I always boot to a gpartd
CD. I use it to easily see, and quickly blank the disk(s). I only
choose it, because it's quick-n-easy. It is also the perfect tool
to wipe that evil grub[2] off the MBR. Which has given me no end
of grief after evaluating some Linux distro. Anyhow, point being;
the desktop is powered by nouveau. I've never had an issue with it,
and it always seems to pick the "right" resolution/frequency. So,
because of that. I was already thinking of investigating that route.
As to talking to nVidia. My past experiences in that regard were,
shall I say; less than ideal. They're always friendly. But getting
anything that might "uncover" any coveted driver info, always fell
short of helpful. :)

Thanks for the reply, and helpful information, Warren.

--Chris


Hi,

FYI:

The KMS stuff seems to work on my intel HD graphics based MAC. Finally I 
can switch back to the console!


--HPS


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Chris H
On Wed, 5 Nov 2014 12:55:51 -0700 (MST) Warren Block  wrote

> On Wed, 5 Nov 2014, Chris H wrote:
> 
> > On Wed, 5 Nov 2014 08:15:04 -0700 (MST) Warren Block 
> > wrote >
> >> On Wed, 5 Nov 2014, Chris H wrote:
> >>> On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
> >>> wrote >>
>  No, video mode won't work with the nVidia blob.  That requires
>  a KMS (in-kernel) driver.
> >>>
> >>> Thank you for the reply, Gary.
> >>>
> >>> Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?
> >>
> >> Or Intel, or anything with KMS drivers.
> >
> > Thanks. Everything I manage, is using nVidia. Looks like
> > the kms VESA might work. But I'm not sure if there would
> > be any appreciable gain going that route (assuming it's even
> > possible).
> 
> It's worth asking Nvidia directly.  I would not be optimistic about 
> that, but it's easy to try, and they might surprise everyone.
> 
> Another option might be nouveau.  Don't know the current status of 
> whether that works on FreeBSD, though.
LOL funny you should bring that up, just now.
Prior to a fresh install on bare metal. I always boot to a gpartd
CD. I use it to easily see, and quickly blank the disk(s). I only
choose it, because it's quick-n-easy. It is also the perfect tool
to wipe that evil grub[2] off the MBR. Which has given me no end
of grief after evaluating some Linux distro. Anyhow, point being;
the desktop is powered by nouveau. I've never had an issue with it,
and it always seems to pick the "right" resolution/frequency. So,
because of that. I was already thinking of investigating that route.
As to talking to nVidia. My past experiences in that regard were,
shall I say; less than ideal. They're always friendly. But getting
anything that might "uncover" any coveted driver info, always fell
short of helpful. :)

Thanks for the reply, and helpful information, Warren.

--Chris


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Warren Block

On Wed, 5 Nov 2014, Chris H wrote:


On Wed, 5 Nov 2014 08:15:04 -0700 (MST) Warren Block  wrote


On Wed, 5 Nov 2014, Chris H wrote:

On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
wrote >>

No, video mode won't work with the nVidia blob.  That requires
a KMS (in-kernel) driver.


Thank you for the reply, Gary.

Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?


Or Intel, or anything with KMS drivers.


Thanks. Everything I manage, is using nVidia. Looks like
the kms VESA might work. But I'm not sure if there would
be any appreciable gain going that route (assuming it's even
possible).


It's worth asking Nvidia directly.  I would not be optimistic about 
that, but it's easy to try, and they might surprise everyone.


Another option might be nouveau.  Don't know the current status of 
whether that works on FreeBSD, though.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Chris H
On Wed, 5 Nov 2014 08:15:04 -0700 (MST) Warren Block  wrote

> On Wed, 5 Nov 2014, Chris H wrote:
> > On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
> > wrote >>
> >> No, video mode won't work with the nVidia blob.  That requires
> >> a KMS (in-kernel) driver.
> >
> > Thank you for the reply, Gary.
> >
> > Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?
> 
> Or Intel, or anything with KMS drivers.

Thanks. Everything I manage, is using nVidia. Looks like
the kms VESA might work. But I'm not sure if there would
be any appreciable gain going that route (assuming it's even
possible).

Thanks again, for the reply, Warren.

--Chris


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Warren Block

On Wed, 5 Nov 2014, Chris H wrote:

On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn  wrote


No, video mode won't work with the nVidia blob.  That requires
a KMS (in-kernel) driver.


Thank you for the reply, Gary.

Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?


Or Intel, or anything with KMS drivers.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Andreas Nilsson
On Wed, Nov 5, 2014 at 3:36 PM, Chris H  wrote:

> On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn 
> wrote
>
> > On Tue, 04 Nov 2014 18:01:41 -0800
> > "Chris H"  wrote:
> >
> > > On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sebastien Pedron
> > >  wrote
> > >
> > > > Hello!
> > > >
> > > > As announced a week ago, vt(4) is now the default console driver in
> > > > 11-CURRENT as of r274085.
> > > >
> > > > You may have to update your console settings in /etc/rc.conf. During
> > > > boot, /etc/rc.d/syscons will indicate what you need to do.
> > > >
> > > > The original HEADS UP mentioned several known issues. Among them, the
> > > > following were fixed:
> > > >
> > > > o  A video mode can be selected using the following tunable in
> > > >/boot/loader.conf:
> > > >kern.vt.fb.default_mode="1024x768"
> > > >
> > > >This only works when using a KMS video driver. It's not
> > > >supported by the VGA backend. See vt(4) man page for further
> > > >documentation.
> > > >
> > > > o  The keyboard was not working when kbdmux(4) was disabled. This
> > > >is fixed.
> > > >
> > > > o  After loading a KMS driver, the text cursor was in the middle
> of
> > > >the kernel messages. The problem was that the cursor position
> was
> > > >not updated after the change in window size. This is fixed.
> > > >
> > > > Up-to-date information can be found on the wiki page:
> > > > https://wiki.freebsd.org/Newcons
> > > >
> > > > If you want to keep using syscons(4), you can add the following line
> to
> > > > /boot/loader.conf:
> > > > kern.vty=sc
> > > >
> > > > Thank you to everyone who tested and reported problems! Please
> continue
> > > > to do so, especially if you find the need to go back to syscons.
> > >
> > > No. Thank _you_! :)
> > >
> > > I was unable to determine from the wiki. But do all these wonderful
> > > new features also work with the nVidia blob, under vt(4)?
> > > I'm currently building a new 11-CURRENT from the 10-26 iso, as I write
> > > this, and was wondering if the graphics mode at higher resolutions was
> > > now possible using the nVidia blob.
> > >
> >
> > No, video mode won't work with the nVidia blob.  That requires
> > a KMS (in-kernel) driver.
>
> Thank you for the reply, Gary.
>
> Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?
>
> Thanks again.
>
> --Chris
>
> >
> > --
> > Gary Jennejohn
>
> Well,

ATI or Intel chip.

Best regards
Andreas
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Chris H
On Wed, 5 Nov 2014 10:19:51 +0100 Gary Jennejohn  wrote

> On Tue, 04 Nov 2014 18:01:41 -0800
> "Chris H"  wrote:
> 
> > On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sebastien Pedron
> >  wrote
> > 
> > > Hello!
> > > 
> > > As announced a week ago, vt(4) is now the default console driver in
> > > 11-CURRENT as of r274085.
> > > 
> > > You may have to update your console settings in /etc/rc.conf. During
> > > boot, /etc/rc.d/syscons will indicate what you need to do.
> > > 
> > > The original HEADS UP mentioned several known issues. Among them, the
> > > following were fixed:
> > > 
> > > o  A video mode can be selected using the following tunable in
> > >/boot/loader.conf:
> > >kern.vt.fb.default_mode="1024x768"
> > > 
> > >This only works when using a KMS video driver. It's not
> > >supported by the VGA backend. See vt(4) man page for further
> > >documentation.
> > > 
> > > o  The keyboard was not working when kbdmux(4) was disabled. This
> > >is fixed.
> > > 
> > > o  After loading a KMS driver, the text cursor was in the middle of
> > >the kernel messages. The problem was that the cursor position was
> > >not updated after the change in window size. This is fixed.
> > > 
> > > Up-to-date information can be found on the wiki page:
> > > https://wiki.freebsd.org/Newcons
> > > 
> > > If you want to keep using syscons(4), you can add the following line to
> > > /boot/loader.conf:
> > > kern.vty=sc
> > > 
> > > Thank you to everyone who tested and reported problems! Please continue
> > > to do so, especially if you find the need to go back to syscons.
> > 
> > No. Thank _you_! :)
> > 
> > I was unable to determine from the wiki. But do all these wonderful
> > new features also work with the nVidia blob, under vt(4)?
> > I'm currently building a new 11-CURRENT from the 10-26 iso, as I write
> > this, and was wondering if the graphics mode at higher resolutions was
> > now possible using the nVidia blob.
> > 
> 
> No, video mode won't work with the nVidia blob.  That requires
> a KMS (in-kernel) driver.

Thank you for the reply, Gary.

Ahh. I see. So unless I have ATI hardware, I'm pretty much out of luck?

Thanks again.

--Chris

> 
> -- 
> Gary Jennejohn


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-05 Thread Gary Jennejohn
On Tue, 04 Nov 2014 18:01:41 -0800
"Chris H"  wrote:

> On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sebastien Pedron
>  wrote
> 
> > Hello!
> > 
> > As announced a week ago, vt(4) is now the default console driver in
> > 11-CURRENT as of r274085.
> > 
> > You may have to update your console settings in /etc/rc.conf. During
> > boot, /etc/rc.d/syscons will indicate what you need to do.
> > 
> > The original HEADS UP mentioned several known issues. Among them, the
> > following were fixed:
> > 
> > o  A video mode can be selected using the following tunable in
> >/boot/loader.conf:
> >kern.vt.fb.default_mode="1024x768"
> > 
> >This only works when using a KMS video driver. It's not
> >supported by the VGA backend. See vt(4) man page for further
> >documentation.
> > 
> > o  The keyboard was not working when kbdmux(4) was disabled. This
> >is fixed.
> > 
> > o  After loading a KMS driver, the text cursor was in the middle of
> >the kernel messages. The problem was that the cursor position was
> >not updated after the change in window size. This is fixed.
> > 
> > Up-to-date information can be found on the wiki page:
> > https://wiki.freebsd.org/Newcons
> > 
> > If you want to keep using syscons(4), you can add the following line to
> > /boot/loader.conf:
> > kern.vty=sc
> > 
> > Thank you to everyone who tested and reported problems! Please continue
> > to do so, especially if you find the need to go back to syscons.
> 
> No. Thank _you_! :)
> 
> I was unable to determine from the wiki. But do all these wonderful
> new features also work with the nVidia blob, under vt(4)?
> I'm currently building a new 11-CURRENT from the 10-26 iso, as I write
> this, and was wondering if the graphics mode at higher resolutions was
> now possible using the nVidia blob.
> 

No, video mode won't work with the nVidia blob.  That requires
a KMS (in-kernel) driver.

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: HEADS UP: Enabling vt(4) by default

2014-11-04 Thread Chris H
On Tue, 04 Nov 2014 18:22:06 +0100 Jean-Sébastien Pédron
 wrote

> Hello!
> 
> As announced a week ago, vt(4) is now the default console driver in
> 11-CURRENT as of r274085.
> 
> You may have to update your console settings in /etc/rc.conf. During
> boot, /etc/rc.d/syscons will indicate what you need to do.
> 
> The original HEADS UP mentioned several known issues. Among them, the
> following were fixed:
> 
> o  A video mode can be selected using the following tunable in
>/boot/loader.conf:
>kern.vt.fb.default_mode="1024x768"
> 
>This only works when using a KMS video driver. It's not
>supported by the VGA backend. See vt(4) man page for further
>documentation.
> 
> o  The keyboard was not working when kbdmux(4) was disabled. This
>is fixed.
> 
> o  After loading a KMS driver, the text cursor was in the middle of
>the kernel messages. The problem was that the cursor position was
>not updated after the change in window size. This is fixed.
> 
> Up-to-date information can be found on the wiki page:
> https://wiki.freebsd.org/Newcons
> 
> If you want to keep using syscons(4), you can add the following line to
> /boot/loader.conf:
> kern.vty=sc
> 
> Thank you to everyone who tested and reported problems! Please continue
> to do so, especially if you find the need to go back to syscons.

No. Thank _you_! :)

I was unable to determine from the wiki. But do all these wonderful
new features also work with the nVidia blob, under vt(4)?
I'm currently building a new 11-CURRENT from the 10-26 iso, as I write
this, and was wondering if the graphics mode at higher resolutions was
now possible using the nVidia blob.

Thank you again, for all your work on this!

--Chris

> 
> -- 
> Jean-Sébastien Pédron


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: Enabling vt(4) by default

2014-11-04 Thread Jean-Sébastien Pédron
Hello!

As announced a week ago, vt(4) is now the default console driver in
11-CURRENT as of r274085.

You may have to update your console settings in /etc/rc.conf. During
boot, /etc/rc.d/syscons will indicate what you need to do.

The original HEADS UP mentioned several known issues. Among them, the
following were fixed:

o  A video mode can be selected using the following tunable in
   /boot/loader.conf:
   kern.vt.fb.default_mode="1024x768"

   This only works when using a KMS video driver. It's not
   supported by the VGA backend. See vt(4) man page for further
   documentation.

o  The keyboard was not working when kbdmux(4) was disabled. This
   is fixed.

o  After loading a KMS driver, the text cursor was in the middle of
   the kernel messages. The problem was that the cursor position was
   not updated after the change in window size. This is fixed.

Up-to-date information can be found on the wiki page:
https://wiki.freebsd.org/Newcons

If you want to keep using syscons(4), you can add the following line to
/boot/loader.conf:
kern.vty=sc

Thank you to everyone who tested and reported problems! Please continue
to do so, especially if you find the need to go back to syscons.

-- 
Jean-Sébastien Pédron



signature.asc
Description: OpenPGP digital signature