Undefined symbol "xf86DisableRandR"
I'm struggling with a build of 13/current on a box. Everything went pretty much as I might expect. But I'm stuck on Xorg; big changes. I read updating, and understood that building xorg-server with default options would DTRT. I I added the sysctl(8) line for the keyboard, installed my video driver (nvidia), and also followed advise in pkg-message. Starting Xorg resulted in: ... ld-elf.so.1: /usr/local/lib/xorg/modules/drivers/nvidia_drv.so: Undefined symbol "xf86DisableRandR" So I searched the interweb for solution(s), and found a shell script in pr(1) 196678. Ran it, and was informed that the xf86-input-evdev driver was not installed. I installed it. But the results were the same. Thoughts? Solutions? Thank you for all your time, and consideration. --Chris P.S. source for ports is from head yesterday, base (install) is from 2 weeks ago. ___ 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?
On Fri, Apr 03, 2020 at 11:50:44AM -0700, Chris wrote: > > No. *I'm* sorry. You were perfectly clear. It was late for me, and I > wasn't very alert. Thank you *very* much for all your help! :) > For future reference, FreeBSD comes with some fairly decent documentation (see, e.g., vt(4)). -- Steve ___ 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?
On Fri, 3 Apr 2020 14:01:47 -0400 Ed Maste ema...@freebsd.org said On Fri, 3 Apr 2020 at 04:25, Chris wrote: > > 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 > Attempting your suggestion returned: > > sysctl: unknown oid 'hw.vga.textmode' Sorry for being unclear - it's a loader tunable, so you need to set it from the loader prompt or in /boot/loader.conf. No. *I'm* sorry. You were perfectly clear. It was late for me, and I wasn't very alert. Thank you *very* much for all your help! :) --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: HOWTO donate CPU to the fight against the Corona-virus
On Sunday, March 22, 2020 11:38:31 AM CEST Stefan Ehmann wrote: > On Saturday, March 21, 2020 12:07:55 PM CET Alexander Leidinger wrote: > > Quoting Stefan Ehmann (from Sat, 21 Mar 2020 > > > > 11:38:26 +0100): > > > On Thursday, March 19, 2020 8:57:45 AM CET Alexander Leidinger via > > > freebsd- > > > > > > stable wrote: > > >> Hi, > > >> > > >> if someone wants to donate some FreeBSD based CPU resources to the > > >> fight against the Corona-virus, here is a quick HOWTO in terms of > > >> installing the Folding@Home client on FreeBSD: > > >> > > >> https://www.leidinger.net/blog/2020/03/19/fighting-the-coronavirus-with > > >> -f > > >> ree bsd-foldinghome/ > > > > > > Unfortunately, (using a CPU slot for the same work unit) TPF is 2-3 > > > times > > > slower than on Ubuntu for me. Much of the speed difference seems to > > > be related > > > to libOpenCL. If remove libOpenCL on Ubuntu, it's still 20-30% faster > > > than > > > on FreeBSD. > > > > The pure CPU based code should be the same. Someone would have to > > trace / reverse engineer what is going on. > > I'm pretty sure now that libOpenCL is only relevant for GPU slots. > > I couldn't reproduce that the presence of libOpenCL.so has any effect on CPU > slots. Didn't make much sense anyway, something else must have been going > on. So there's probably no point in getting OpenCL to run on FreeBSD until > we have GPU rendering. > > The numbers displayed by FAHControl are rather strange: > * There is no discernible difference in speed if 1 or all CPU cores are used > (but top shows that 600% CPU cycles are burned) - happens on both Ubuntu > and Linuxolator > * According to the progress bar, Ubuntu completes 1% per minute, but > Linuxolator only 0.1% (for the same work unit) > > Don't know if the numbers displayed are bogus or there is really that much > of a difference. Maybe the issue is only related to a specific WU or to > AMD-CPUs. Just a short update: I've tested the port with a different WU and everything seems normal. Speed is comparable to Linux and multi-core also works as expected. My previous problems can probably be ignored, not sure what the problem actually was. ___ 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?
On Fri, 3 Apr 2020 at 04:25, Chris wrote: > > 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 > Attempting your suggestion returned: > > sysctl: unknown oid 'hw.vga.textmode' Sorry for being unclear - it's a loader tunable, so you need to set it from the loader prompt or in /boot/loader.conf. ___ 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?
On Fri, 3 Apr 2020 20:10:36 +0900 junch...@dec.sakura.ne.jp said
On Fri, 03 Apr 2020 01:25:18 -0700
Chris wrote:
> 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
> Attempting your suggestion returned:
>
> sysctl: unknown oid 'hw.vga.textmode'
Hi.
Have you tried via command line, /etc/sysctl.conf or /etc/rc.conf?
If so, try setting it in /boot/loader.conf and reboot.
hw.vga.textmode is tunable, so can be set only by loader.
Sigh... I'm afraid it was quite late last night when
I attempted this, and I took it out of context.
Yes. Adding the line to *loader.conf(5)* worked as intended.
Sorry for all the bother. :(
Thanks for your kind help. :)
--Chris
% grep -r -n "hw.vga" /usr/src/sys/ | fgrep textmode
/usr/src/sys/dev/vt/hw/vga/vt_vga.c:1298:* If
"hw.vga.textmode" is not set and we're running on
hypervisor,
/usr/src/sys/dev/vt/hw/vga/vt_vga.c:1304:
TUNABLE_INT_FETCH("hw.vga.textmode", &textmode);
^^^
> Thanks for trying!
>
> I guess I should look into attempting to put some effort into sc(4)
> and try to find out why it's being depreciated. If it's just lack
> of commitment to it. I'll see if I can't take it on myself. :)
>
> Thanks again! :)
>
> --Chris
>
--
Tomoaki AOKI
___
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?
On Fri, 03 Apr 2020 01:25:18 -0700
Chris wrote:
> 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
> Attempting your suggestion returned:
>
> sysctl: unknown oid 'hw.vga.textmode'
Hi.
Have you tried via command line, /etc/sysctl.conf or /etc/rc.conf?
If so, try setting it in /boot/loader.conf and reboot.
hw.vga.textmode is tunable, so can be set only by loader.
% grep -r -n "hw.vga" /usr/src/sys/ | fgrep textmode
/usr/src/sys/dev/vt/hw/vga/vt_vga.c:1298:* If
"hw.vga.textmode" is not set and we're running on
hypervisor,
/usr/src/sys/dev/vt/hw/vga/vt_vga.c:1304:
TUNABLE_INT_FETCH("hw.vga.textmode", &textmode);
^^^
> Thanks for trying!
>
> I guess I should look into attempting to put some effort into sc(4)
> and try to find out why it's being depreciated. If it's just lack
> of commitment to it. I'll see if I can't take it on myself. :)
>
> 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"
--
Tomoaki AOKI
___
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?
Den Thu, 2 Apr 2020 19:31:53 -0400 skrev 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. This is probably side-tracking a bit, but since I never figured out how to make vt handle 8859-1, it has become a habit for me to change between vt when using x11 and sc when I need console. Has anything changed for this lately? -- Eivind Nicolay Evensen ___ 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?
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 Attempting your suggestion returned: sysctl: unknown oid 'hw.vga.textmode' Thanks for trying! I guess I should look into attempting to put some effort into sc(4) and try to find out why it's being depreciated. If it's just lack of commitment to it. I'll see if I can't take it on myself. :) 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"
