Re: Is sc(4) no longer supported in GENERIC?

[Chris]

On Thu, 2 Apr 2020 19:31:53 -0400 Ed Maste ema...@freebsd.org said


On Thu, 2 Apr 2020 at 17:13, Chris  wrote:
>
> Ahem... I used the wrong syntax.
> changing the entry to
>
> kern.vty=sc
>
> solved it! :)

I'm glad it's working for you, but note that sc(4) is deprecated and
has no ongoing effort behind it, so it would be best if we can
identify and resolve the issue you encountered.

The first thing you can try is vt(4) in text mode, by setting
hw.vga.textmode=1

Thanks for the thoughtful reply, Ed!

The box in question is in the middle of a big build session ATM.
But when it's finished, I'll happily try your suggestion. I'll
report back with my findings.

Thanks again!

--Chris


___
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"

Re: Is sc(4) no longer supported in GENERIC?

[Ed Maste]

On Thu, 2 Apr 2020 at 17:13, Chris  wrote:
>
> Ahem... I used the wrong syntax.
> changing the entry to
>
> kern.vty=sc
>
> solved it! :)

I'm glad it's working for you, but note that sc(4) is deprecated and
has no ongoing effort behind it, so it would be best if we can
identify and resolve the issue you encountered.

The first thing you can try is vt(4) in text mode, by setting
hw.vga.textmode=1
___
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"

Re: FreeBSD Office Hours: April 1, 2020 18:00 UTC

[Jan Bramkamp]

On 02.04.20 09:56, Ihor Antonov wrote:

On 2020-04-01 16:01, Allan Jude wrote:

On 2020-03-29 20:25, Allan Jude wrote:

Our first FreeBSD Office Hours event was a success with over 60 people
in attendance.

I've not had time to edit and post the video yet, but it is available in
the DVR buffer on the streaming page:

https://live.freebsd.org/FreeBSD/officehours/

Hi Allan,

Is there a recording available? I missed the event :(


The recording is at:https://live.freebsd.org/FreeBSD/officehours/ .

___
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"

Re: How does everyone get a synced console after a fresh install?

[Chris]

On Wed, 01 Apr 2020 21:30:38 -0700 bsd-li...@bsdforge.com said


OK I just installed a fresh copy of 13 from an official
memstick image. All went as expected. But upon reboot,
I'm missing about 4 to 5 characters on the left hand
side of the screen. I know vesa is built into GENERIC.
But vidcontrol(1) won't help. I've tried both sc(4), and
vt(4). Is textmode no longer supported?

Thanks for any, and all insight into solving this.


OK I was able to solve this.
I used the wrong syntax in loader.conf(5)
changing
kern_vty=sc
to
kern.vty=sc
fixed it. I now have a fully working console! :)

Thanks for your time, and sorry for the noise!

--Chris

--Chris


___
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"

Re: Is sc(4) no longer supported in GENERIC?

[Chris]

On Thu, 02 Apr 2020 14:01:02 -0700 bsd-li...@bsdforge.com said


I just performed a fresh install from an official install image.
But am unable to see the entire console (missing ~5 characters
on the left hand side of (LCD) monitor. GENERIC uses vt(4). So
I decided to see if sc(4) would help, and added kern_vty=sc
to loader.conf(5). However. That seems to have been ignored.

How to get it on a fresh install?

Ahem... I used the wrong syntax.
changing the entry to

kern.vty=sc

solved it! :)

Sorry for the noise! :(

--Chris


Thanks!

--Chris


___
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"

Is sc(4) no longer supported in GENERIC?

[Chris]

I just performed a fresh install from an official install image.
But am unable to see the entire console (missing ~5 characters
on the left hand side of (LCD) monitor. GENERIC uses vt(4). So
I decided to see if sc(4) would help, and added kern_vty=sc
to loader.conf(5). However. That seems to have been ignored.

How to get it on a fresh install?

Thanks!

--Chris


___
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"

pkg upgrade … solver: cannot find provide for requirement …

[Graham Perrin]

Re: VirtualBox segmentation fault, 5.2.34_1 on FreeBSD-CURRENT r359249

On 24/03/2020 11:36, Graham Perrin wrote:

> … Locally built 5.2.34_1 not working on -CURRENT. …

Now with r359249:

grahamperrin@momh167-gjp4-8570p:~ % pkg rquery '%o %v %R' virtualbox-ose
emulators/virtualbox-ose 5.2.34_1 FreeBSD
emulators/virtualbox-ose 5.2.34_2 poudriere

– 5.2.34_2 is built, but I can't upgrade from 5.2.34_1.

Partial record:



…
root@momh167-gjp4-8570p:~ # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating poudriere repository catalogue...
poudriere repository is up to date.
All repositories are up to date.
Checking for upgrades (15 candidates): 100%
Processing candidates (15 candidates): 100%
solver: cannot find provide for requirement libopenblas.so when 
processing package: py27-numpy
solver: cannot find provide for requirement libopenblas.so when 
processing package: suitesparse
solver: cannot find provide for requirement libdioritegtk-0.2.so when 
processing package: nuvolaplayer
solver: cannot find provide for requirement libdioriteglib-0.2.so when 
processing package: nuvolaplayer
solver: cannot find provide for requirement libopenblas.so when 
processing package: coin-or-CoinUtils

Checking integrity... done (0 conflicting)
Your packages are up to date.
root@momh167-gjp4-8570p:~ # pkg upgrade virtualbox-ose
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating poudriere repository catalogue...
poudriere repository is up to date.
All repositories are up to date.
solver: cannot find provide for requirement libcurl.so.4 when processing 
package: virtualbox-ose

…



Context: 
___
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"

Re: USB microphones with FreeBSD-CURRENT: bug 194727, r358629

[Graham Perrin]

On 31/03/2020 03:47, Theron wrote:



I don't know what would be attaching to mixer before login. …



www/plasma5-plasma-browser-integration interaction with x11/sddm maybe?

___
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"

mount -t zfs … and (RFC, 7452) zfs mount -o mountpoint=…

[Graham Perrin]

Re: ZFS: OpenZFS: lost the ability to boot a BE

Allan Jude wrote:


To temporarily mount a ZFS filesystem:

mount -t zfs poolname/data/set /path/here


– thanks, Allan – I have probably been given the same hint more than 
once before! (Rarely needed. I forget.)



Rodney W. Grimes wrote:


Is there anyway to get the zfs command to add mountpoint as
a temporary value like it does some of the others so that

zfs mount -o mountpoint=/mnt poolname/data/set

would just do the right thing?


RFC: Temporary property and mount handling design changes needed to 
address multiple issues. · Issue #7452 · openzfs/zfs




___
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"

Re: FreeBSD Office Hours: April 1, 2020 18:00 UTC

[Ihor Antonov]

On 2020-04-01 16:01, Allan Jude wrote:
> On 2020-03-29 20:25, Allan Jude wrote:
> 
> Our first FreeBSD Office Hours event was a success with over 60 people
> in attendance.
> 
> I've not had time to edit and post the video yet, but it is available in
> the DVR buffer on the streaming page:
> 
> https://live.freebsd.org/FreeBSD/officehours/

Hi Allan,

Is there a recording available? I missed the event :(

Thanks


Ihor
___
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"

How does everyone get a synced console after a fresh install?

[Chris]

OK I just installed a fresh copy of 13 from an official
memstick image. All went as expected. But upon reboot,
I'm missing about 4 to 5 characters on the left hand
side of the screen. I know vesa is built into GENERIC.
But vidcontrol(1) won't help. I've tried both sc(4), and
vt(4). Is textmode no longer supported?

Thanks for any, and all insight into solving this.

--Chris


___
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"

Re: FYI: artifact-based head bisect and OPi+2e (an armv7): -r359311 fails to boot but -r359309 boots (kernel substitutions)

[Mark Millard]

On 2020-Mar-29, at 10:58, Ian Lepore  wrote:

> On Sun, 2020-03-29 at 09:44 -0700, Thomas Skibo wrote:
>> On Sun, Mar 29, 2020 at 12:29:00AM -0700, Mark Millard via freebsd-
>> arm wrote:
>>> While trying to update the head version
>>> in use I ran into boot hangups on the
>>> OrangePi+ 2e and did an approximate
>>> bisect of artificact.freebsd.org kernels
>>> to find approximately which kernel
>>> version the issue started at.
>>> 
>>> I found that head -r359309 boots and
>>> -r359311 fails (shown later below).
>>> The original update attempt was from
>>> -r359966 to -r359376 and -r359376
>>> stopped there as well. (I kept world
>>> there and varied the kernel version
>>> for the approximate bisect activity.)
>>> 
>>> It seems that at least one of the
>>> "MI-namespace" atomics added do not work
>>> in all its usage-contexts on the cortexA7
>>> (armv7) involved.
>> 
>> It looks like my previous reply didn't go to the mailing lists.  I'm
>> new to
>> mutt.
>> 
>> Anyway, I looked at this problem yesterday and it seems r359311
>> enables
>> using some atomic operations that were not being used until now.  In
>> particular, atomic_fcmpset_8() seems broken and hangs up
>> in vm_page_bits_swap().  I think I have a fix but I want to run it
>> by Ian.
>> 
>> --Thomas
>> 
>> Index: sys/arm/include/atomic-v6.h
>> ===
>> --- sys/arm/include/atomic-v6.h  (revision 359412)
>> +++ sys/arm/include/atomic-v6.h  (working copy)
>> @@ -196,7 +196,7 @@
>>   \
>>  __asm __volatile( \
>>  "1: ldrex" SUF "   %[tmp], [%[ptr]]  \n"  \
>> -"   ldr%[ret], [%[oldv]] \n"  \
>> +"   ldr" SUF " %[ret], [%[oldv]] \n"  \
>>  "   teq%[tmp], %[ret]\n"  \
>>  "   ittee  ne\n"  \
>>  "   str" SUF "ne   %[tmp], [%[oldv]] \n"  \
>> 
> 
> 
> I've committed this fix as r359423, thanks!

Thanks to both of you: the OPi+2e boots just fine
now and has been operating like it used to (head
-r359427 in use).


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
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"