Re: buildkernel: don't know how to make cleandir in drm-current-kmod

On 2021-02-18 09:41, Ruslan Makhmatkhanov wrote: Niclas Zeising wrote on 2/18/21 9:55 AM: On 2021-02-18 06:32, Ruslan Makhmatkhanov wrote: Hello, trying to build kernel from commit f61e92ca5a23450bc28169bbdd71d7674df98c19 (HEAD -> main, origin/main, origin/HEAD) Author: Glen Barber D

Re: buildkernel: don't know how to make cleandir in drm-current-kmod

On 2021-02-18 06:32, Ruslan Makhmatkhanov wrote: Hello, trying to build kernel from commit f61e92ca5a23450bc28169bbdd71d7674df98c19 (HEAD -> main, origin/main, origin/HEAD) Author: Glen Barber Date:   Wed Feb 17 23:00:03 2021 -0500 world built ok, but then I have this on make kernel: ===> z

Re: Problem with X Server when updating to 38bfc6dee33

On 2021-02-03 16:46, Thomas Laus wrote: On 2/3/21 8:07 AM, Michael Gmelin wrote: There was a problem with xorg-server which made it build without udev on 14. Try reinstalling xorg-server from ports (something like: portsnap fetch extract; cd /usr/ports/x11-servers/xorg-server && make clean re

Re: loading drm crashes system

On 2021-01-25 00:19, Robert Huff wrote: Hello: On a system now running: 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: Sun Jan 24 14:16:54 EST 2021 amd64 (src+ports updated at midnight US EST) with PORTS_MODULES="drm-current-kmod gpu-firmware-kmod", starting the

Re: geeqie, and neverball build problem on 13-current

On 2020-09-24 11:52, Stefan Esser wrote: Am 24.09.20 um 11:24 schrieb Niclas Zeising: On 2020-09-24 11:17, monochrome wrote: Not sure how long this has been a problem, I noticed with the new version of geeqie (geeqie-devel builds fine) and found the neverball problem when rebuilding all

Re: geeqie, and neverball build problem on 13-current

On 2020-09-24 11:17, monochrome wrote: Not sure how long this has been a problem, I noticed with the new version of geeqie (geeqie-devel builds fine) and found the neverball problem when rebuilding all packages to investigate. neverball output changes with consecutive build attempts, geeqie doe

Re: vfs.zfs.min_auto_ashift and OpenZFS

On 2020-09-09 17:55, Ryan Moeller wrote: On 9/8/20 4:31 PM, Niclas Zeising wrote: On 2020-05-02 02:20, Matthew Macy wrote: OpenZFS doesn't have the same ashift optimization logic that FreeBSD has. It's something that needs to be resolved before the code can be integrated downst

Re: vfs.zfs.min_auto_ashift and OpenZFS

On 2020-05-02 02:20, Matthew Macy wrote: OpenZFS doesn't have the same ashift optimization logic that FreeBSD has. It's something that needs to be resolved before the code can be integrated downstream. So currently all pools created with OpenZFS will use 512 bit alignment, at least if the unde

Re: Is pkg site forbidden by brower?

On 2020-09-06 09:00, grarpamp wrote: On 9/6/20, Kevin Oberman wrote: On Sat, Sep 5, 2020 at 8:04 PM Yoshihiro Ota wrote: Is "403 Forbidden" an intended response for a brower access to http://pkg.freebsd.org/FreeBSD:12:i386/ nowdays? I used to see available packages with a brower and decided

deprecation of drm-legacy-kmod

ease in transition. On FreeBSD 12, there is also the option of using the graphics drivers in base, although those are supported on a best-effort basis only. Regards -- Niclas Zeising FreeBSD Graphics Team ___ freebsd-current@freebsd.org mailing list

Re: KiCad is horrible on CURRENT

On 2020-07-29 21:18, Poul-Henning Kamp wrote: Michael Gmelin writes: Which driver are you using? drm-devel-kmod-5.3.g20200724 Can you try with drm-current-kmod? Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://list

Re: FYI: forum web site is .. unreadable

On 2020-06-23 08:48, Gary Jennejohn wrote: On Tue, 23 Jun 2020 01:14:52 +0200 Steffen Nurpmeso wrote: Hello. Normally i do not do forums (web interface etc etc), but i was interested in ZFS encryption support and so i searched, and found a page[1]. Now when i open that on a glibc Linux box w

Re: lock order reversal and poudriere

On 2020-05-02 20:36, Kurt Jaeger wrote: Hi! I am compiling some packages with poudriere on 13-current kernel. I noticed some strange messages printed into the terminal and dmesg: lock order reversal: [...] Are those the debug messages that aren't visible on non-current kernel and should they

Re: Weird mouse behaviour

On 2020-04-27 17:06, Malcolm Matalka wrote: Michael Gmelin writes: Could you share your setup by running pkg install ca_root_nss fetch \ https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xorg-udev-setup-check.sh ./xorg-udev-setup-check.sh -desk and mailing

Re: Weird mouse behaviour

On 2020-04-27 11:29, Michael Gmelin wrote: On Mon, 27 Apr 2020 08:28:50 + "Poul-Henning Kamp" wrote: In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas Zeising writes: With my touchpad, ctrl left click and ctrl right click opens two differen

Re: Weird mouse behaviour

On 2020-04-27 10:28, Poul-Henning Kamp wrote: In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas Zeising writes: With my touchpad, ctrl left click and ctrl right click opens two different menus in xterm, main menu and vt font menu, respectively. ctrl-

Re: Weird mouse behaviour

On 2020-04-27 10:14, Malcolm Matalka wrote: Niclas Zeising writes: On 2020-04-27 08:03, Malcolm Matalka wrote: I saw that there was another thread on this and I wanted to throw my experience in: my mouse was sluggish and tap-to-click did not work. I set the evdev mask back to 3 and it

Re: Weird mouse behaviour

On 2020-04-27 09:26, Poul-Henning Kamp wrote: In message <7549a5dd-3edc-4efd-bc0b-4d67232b4...@grem.de>, Michael Gmelin writes: In my case, with the default sysctl kern.evdev.rcpt_mask=12 CTRL + middle button would not activate the menu in xterm. Are you using the trackpoint?

Re: Weird mouse behaviour

On 2020-04-27 08:03, Malcolm Matalka wrote: I saw that there was another thread on this and I wanted to throw my experience in: my mouse was sluggish and tap-to-click did not work. I set the evdev mask back to 3 and it worked. I am on a Dell XPS 13. Hi! Is this on CURRENT? When using X? Can

Re: FreeBSD-13.0-CURRENT-amd64-20200409-r359731: drm-kmod failure?

On 2020-04-11 08:09, Clay Daniels wrote: I removed what I thought was FreeBSD-13.0-CURRENT-amd64-20200402-r359556 snapshot yesterday. It was working fine. I loaded the 20200409-r359731 snapshot, rebooted, installed drm-kmod, and it booted into the first "flash" screen where there is a great light

Re: Undefined symbol "xf86DisableRandR"

rsion of the nVidia driver does not support xorg-server 1.20, and since it's a binary driver there is not much we can do about it. I suggest you talk to nVidia about getting the driver to support xserver 1.20. Regards -- Niclas Zeising ___ fr

Re: users of xorg, in particular on FreeBSD 11.3

On 2020-03-23 22:00, Niclas Zeising wrote: In ports r528813 I switched FreeBSD 11 (including FreeBSD 11.3 and the This should be r529003, sorry about that. upcoming 11.4) back to use the legacy rule set.  This means that once you have installed libxkbcommon 0.10.0_2 on

Re: users of xorg, in particular on FreeBSD 11.3

changed. If you are on FreeBSD 12 or later, and are using xf96-input-keyboard, you might still need to set this env variable. Please see the instructions below. Regards On 2020-03-21 00:41, Niclas Zeising wrote: [ This is cross-posted across several mailing lists for maximum visibility

users of xorg, in particular on FreeBSD 11.3

The easiest way to accomplish this is by adding it to your shell startup file. As an example, for users of [t]csh, put setenv XKB_DEFAULT_RULES xorg in ~/.login For users of bourne type shells (sh, bash, ksh, zsh, ...) instead put export XKB_DEFAULT_RULES=xorg in ~/.profile Regards -- Niclas Zeis

Re: New Xorg - different key-codes

On 2020-03-11 10:29, Niclas Zeising wrote: On 2020-03-11 01:46, Greg 'groggy' Lehey wrote: Sorry.  I should have thought of reporting it.  For me, with a number of other issues, it was a frustrating week,some of which are still not resolved. As a side note, if it's not repo

Re: New Xorg - different key-codes

now opens and closes a KDE "Application Launcher", alternatively with its original function (which makes editing a frustration).   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 And that PR has a suggested solution for at least KDE us

Re: New Xorg - different key-codes

devices, as does the x11@ mailing list archives. Regards -- Niclas Zeising FreeBSD Graphics Team ___ 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"

users of drm-legacy-kmod or drm drivers from base

drivers, I'm also very interested in hearing what issues you are facing that prevents you from using the new lkpi based drivers. Regards -- Niclas Zeising FreeBSD Graphics Team ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/ma

Re: DRM-current-kmod is still a problem at r353339

Hi! On 2019-10-24 01:32, Clay Daniels Jr. wrote: Niclas, my last working install of 13.0 Current was r353072 of Oct 4th. The next week's r353427 of Oct 11th did not work and I reverted to r353072 for a week. Then r353709 of Oct 18th did not work, and when I tried to revert back to r353072 it do

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-23 21:50, Clay Daniels Jr. wrote: r353709 Looked promising, but failed: Loaded r353709 make install drm-kmod, all 3 installed (drm-devel-kmod, drm-current-kmod, & gpu-firmware-kmod) set /etc/rc.conf & /boot/loader.conf configs as usual rebooted and looked good, video tingling pkg inst

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 10:13, Niclas Zeising wrote: On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 11:08, Yuri Pankov wrote: Niclas Zeising wrote: On 2019-10-20 08:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-21 09:01, Thomas Mueller wrote: from Neel Chauhan: For me, the following code is still necessary for me (HP Spectre x360 2018), which is the remaining parts of the patches not committed if you are using a recent kernel. I don't know about you all ThinkPad users, it should still apply

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-20 08:45, Yuri Pankov wrote: On 10/18/2019 8:01 AM, Xin Li wrote: Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi"))   -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and mjg@'s earlier patch at https://people.freebsd

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a little while, it broke with r353645. https://i.imgur.com/Q5nYZf2.jpg I'm using the same HP Spectre t

Re: DRM-current-kmod is still a problem at r353339

On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a little while, it broke with r353645. https://i.imgur.com/Q5nYZf2.jpg I'm using the same HP Spectre that I used earlier (where it worked and where it panicked). That commit looks unrelated, it touches the wbwd and

Re: hang up with r352239 and r352386 with i5-7500

t will take some time before it shows up as packages, but there is no problems building drm-current-kmod from ports even if packages are used for the rest of the system. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://li

Re: hang up with r352239 and r352386 with i5-7500

On 2019-09-16 16:06, Masachika ISHIZUKA wrote: Can you please use absolute paths to i915kms.ko anyway, just to test? The same hang up occure with kld_list="/boot/modules/i915kms.ko" in /etc/rc.conf. Even after applying the patch I suggested? Regards -- Nicl

Re: hang up with r352239 and r352386 with i5-7500

1000 acf mac_ntpd.ko Hi! Can you please use absolute paths to i915kms.ko anyway, just to test? Thanks! Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsu

Re: hang up with r352239 and r352386 with i5-7500

top/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d that might solve the issue, can you apply that and recompile drm-current-kmod and see if it works? Thanks! Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https

Re: ses no longer attaches

On 2019-08-29 00:07, Alexander Motin wrote: On 27.08.2019 19:15, Niclas Zeising wrote: I did some more digging. r351355 is ok, while r351356 is bad.  This is Warner's (CC:d) commit to add RST support to nvme, however, I'm using a ssd drive connected to ahci. What happens is that the

Re: ses no longer attaches

On 2019-08-28 01:45, Michael Butler wrote: On 2019-08-27 19:41, Michael Butler wrote: On 2019-08-27 19:15, Niclas Zeising wrote: On 2019-08-28 00:38, Alexander Motin wrote: Hi. On 27.08.2019 18:03, Niclas Zeising wrote: I have an issue where the ses driver no longer attaches.  Last known

Re: ses no longer attaches

On 2019-08-28 00:38, Alexander Motin wrote: Hi. On 27.08.2019 18:03, Niclas Zeising wrote: I have an issue where the ses driver no longer attaches.  Last known good version was r351188, r351544 is broken.  In that interval, something happened.  I haven't had time to bisect yet. I

ses no longer attaches

Hi! I have an issue where the ses driver no longer attaches. Last known good version was r351188, r351544 is broken. In that interval, something happened. I haven't had time to bisect yet. Thanks! Regards -- Niclas Zeising ___ freebsd-cu

Re: Installing drm-current-kmod from ports

On 2019-08-18 04:08, Clay Daniels Jr. wrote: I've been reading the HEADSUP: drm-current-kmod thread, actually several times, and since my pkg install of plain vanilla drm-kmod was a dud after working for several weekly installs of 13.0-Current, it's clear I probably need to make install from the

Re: HEADSUP: drm-current-kmod now installs sources

built for those arches where there is support, and only the modules needed, as an example, i915kms.ko will only be built on amd64 and i386, if that's what you're worried about. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mail

Re: HEADSUP: drm-current-kmod now installs sources

work like this for a while, to shake out any bugs or other unexpected issues, and then look into converting more kmod ports. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd

Re: drm-legacy is broken, again

ual names escaped me. I reproduced the issue and submitted a PR: https://github.com/FreeBSDDesktop/drm-legacy/pull/13 Thanks for that, too. I'm not in a position to submit a PR as my mouse has gone missing under Xorg. Port has been updated: https://svnweb.freebsd.org/changeset/ports

Re: Can't buildworld at r350321

On 2019-07-25 12:33, Masachika ISHIZUKA wrote: Hi. I want to update 13-current from r349989 to r350321 as follows. % cd /usr/src % pwd /usr/altlocal/freebsd-current/src % df -h . Filesystem SizeUsed Avail Capacity Mounted on 192.168.1.2:/usr/altlocal2.5T

Re: Someone broke USB

ortunately, things have gone left. To update /usr/src to get your change, I pulled in some vm changes, which break the graphics/drm-legacy-kmod port. Can you report this, including the failure you're seeing, to x...@freebsd.org or as an issue on the FreeBSDDesktop github? Thanks! Regards --

Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to?

On 2019-06-23 04:56, Karl Denninger wrote: On 6/22/2019 20:16, Thomas Mueller wrote: I am trying to set up UEFI to boot my FreeBSD and NetBSD installations, and later, Linux. Easy.  Refind should do that and allow selection from a menu. I wrote this as an instruction on how to get FreeBSD

Re: signal 11 for 'conftest' && poudriere jails

On 2019-06-17 07:32, Matthias Apitz wrote: While running poudriere jails on a very recent CURRENT: FreeBSD jet 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r349041: Sat Jun 15 07:45:13 CEST 2019 guru@jet:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I see messages about signal 11 for 'conftest'

Enabling synaptics and elantech touchpads by default

rk in X by default, meaning we get a more user friendly appearance. Is there any reason not to do this? Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, sen

Re: Heads up for breaking drm update.

ions. It should also be noted that drm-current now has a new dependency on lindebugfs. It won't load without it :-( Previously, lindebugfs was part of the port, and loaded from the port. With this update, we simply switched to using the debugfs version that was imported into base. Re

Re: Inability to build FreeBSD-current amd64

On 2019-05-16 09:36, Thomas Mueller wrote: from Niclas Zeising: I run a build WITH_CLANG_EXTRAS, and that worked, on current, last weekend, if that's what you're asking about. This won't take away the need for llvm ports in certain ports builds, however, such as firefox and

Re: Inability to build FreeBSD-current amd64

On 2019-05-16 03:46, Thomas Mueller wrote: In general, WITH_CLANG_EXTRAS controls the building of extra tools such as a disassembler, and tools for working on clang itself such as bug reporting tools. I don't have a really detailed answer because I've never enabled the option. I've always perce

Re: SVN r345102 breaks drm-current-kmod

(((x) & ((__typeof(x))(a) - 1)) == 0) >> ^ >> --- drm_atomic_helper.o --- >> 1 error generated. >> *** [drm_atomic_helper.o] Error code 1 >> >> make[3]: stopped in >> /usr/ports/graphics/drm-current-kmod/work/kms-drm-78e51d0/drm >> >_

Re: What is evdev and autoloading?

ork much worse. We in the FreeBSD Graphics Team are working very hard to improve the FreeBSD Desktop experience, since it is an avenue to recruit new users, and make current users use FreeBSD more. Evdev and libinput is used by both Wayland and xorg. You are free to use either one. Regar

Re: "Oddness" in head since around r343678 or so

On 2/12/19 1:38 PM, David Wolfskill wrote: On Thu, Feb 07, 2019 at 05:09:40AM -0800, David Wolfskill wrote: ... The laptop is configured to run xdm; while running stable/11 or stable/12, there's a period of about 5 seconds after xdm's login banner shows up before either the mouse or keyboard res

Re: drm2 removed?

On 2/11/19 6:36 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote: On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I

Re: drm2 removed?

On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? It was r343567. The merg

Re: drm2 removed?

On 2/11/19 5:20 PM, Steve Kargl wrote: On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? It was r343567. The merg

Re: "Oddness" in head since around r343678 or so

On 2019-02-10 16:35, Niclas Zeising wrote: On 2019-02-08 10:27, Alexander Leidinger wrote: Hi, I recently noticed some generic slowness myself. I experienced this during replacing disks in a raidz by bigger ones. Long story short, check top -s if you have vnlru running for a long period at

Re: "Oddness" in head since around r343678 or so

On 2019-02-08 10:27, Alexander Leidinger wrote: Hi, I recently noticed some generic slowness myself. I experienced this during replacing disks in a raidz by bigger ones. Long story short, check top -s if you have vnlru running for a long period at high CPU... If yes increase kern.maxvnodes (I

Re: drm changes and updating to 12.0

-video-ati-legacy rather than xf86-video-ati. Regards -- Niclas Zeising ___ 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 x11-servers/xorg-server and CVE-2018-14665

x27;t hesitate to contact me or to send a message to the x...@freebsd.org mailing list. Regards Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnica.com/inform

Re: FreeBSD x11-servers/xorg-server and CVE-2018-14665

On 10/27/18 11:00 PM, Niclas Zeising wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [ cross posted to several FreeBSD lists. Please keep replies to x...@freebsd.org ] Yes, I know the signature is BAD. GPG is as user friendly as always. I'm about to re-send this with a (hope

FreeBSD x11-servers/xorg-server and CVE-2018-14665

x27;t hesitate to contact me or to send a message to the x...@freebsd.org mailing list. Regards - -- Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnic

Re: Dependencies – drm-kmod, drm-stable-kmod and drm-next-kmod

on FreshPorts is probably based on the version of FreeBSD FreshPorts is using to parse the ports tree. gpu-firmware-kmod is a dependency of all drm-*-kmod ports, but it's not a direct dependency of drm-kmod. Regards -- Niclas Zeising ___ freebsd-curren

Re: Problem starting Xorg

On 10/2/18 7:02 PM, Filippo Moretti wrote: I get the following error while attemptong to start xorg,that did work until today,amd64 alpha3drmn0:error:no GEM object associated to handle 0x0400 can't  create framebufferany help appreciatedFilippo Hi! Can you provde your Xorg log, as well as

Re: priority of paths to kernel modules?

ne of the reasons we wanted to get rid of the base drivers, as I've stated before). X can't always know which driver to load (when using modesetting for instance), and in my opinion, it should be the kernel/loader that decides which drivers to loa

Re: ntpd as ntpd user question

On 07/21/18 19:56, RW wrote: On Sat, 21 Jul 2018 11:14:45 -0600 Ian Lepore wrote: There's a "pre-world" stage of mergemaster (-Fp option I think) which isn't needed often, but one of the times it is needed is apparently when new user ids are added. I wish mergemaster had an option to just ad

Re: atomic changes break drm-next-kmod?

On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > wrote: On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky wr

Re: atomic changes break drm-next-kmod?

On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Michael Butler schrieb: It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. --- i915_drv.o --- In file included from i915_drv.c:30: In file included fro

Re: How to run drm-next-kmod on r334511

On 06/02/18 09:56, Masachika ISHIZUKA wrote: When I updated to r334511, drm-next-kmod is not working with the message '[drm:fw_domain_wait_ack] render: timed out waiting for forcewake ack request.'. drm-next-kmod was working fine on r333704. My CPU is pentium G4560(kaby lake). We are w

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/31/18 16:21, Rodney W. Grimes wrote: I do remeber for a long time this was a -current only modules, is that still true, or can I load it on 11.0, 11.1 and 11.2Beta3 now? drm-stable-kmod works on 11.2 (including the betas) and later. We can't backport the needed changes to the lkpi to t

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/18/18 19:58, Niclas Zeising wrote: [ Cross posted to freebsd-current@ and freebsd-x11@.  Please respect reply-to and send all replies to freebsd-x11@.  Thanks! ] Hi! I propose that we remove the old drm2 driver (sys/dev/drm2) from FreeBSD.  I suggest the driver is marked as deprecated

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/22/18 13:47, dpolyg wrote: I have one comment regarding usage of the drm2 on a "legacy" hardware. Excuse me in advance if I misunderstand something. For the last 2-3 years I'm playing with devices such as small form factor PCs from Shuttle: http://global.shuttle.com/products/productsList?

Re: [RFC] Deprecation and removal of the drm2 driver

On 05/20/18 18:40, Steve Kargl wrote: On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < s...@troutmask.apl.washington.edu> wrote: On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: On Fri, May 18, 2018, 20:00

[RFC] Deprecation and removal of the drm2 driver

Thank you Regards -- Niclas Zeising FreeBSD x11/graphics team ___ 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: suspend/resume regression

On 05/15/18 16:48, Pete Wright wrote: On 05/14/2018 20:35, Theron wrote: On 05/13/18 15:44, Pete Wright wrote: so i've done a bit more debugging on my end.  i've even installed the 11.2-BETA branch last night since 11-STABLE worked without issues about a month or so ago. i've set "debug.ac

Re: suspend/resume regression

On 05/14/18 10:06, Edward Tomasz Napierała wrote: On 0513T1244, Pete Wright wrote: On 05/13/2018 10:27, Pete Wright wrote: On 05/13/2018 08:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system beco

Re: suspend/resume regression

On 05/13/18 17:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operati

Re: suspend/resume regression

On 05/13/18 18:16, Michael Gmelin wrote: On 13. May 2018, at 11:54, Niclas Zeising wrote: On 05/13/18 09:48, Andriy Gapon wrote: On 13/05/2018 05:25, Pete Wright wrote: hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stabl

Re: suspend/resume regression

On 05/13/18 21:44, Pete Wright wrote: On 05/13/2018 10:27, Pete Wright wrote: On 05/13/2018 08:58, Theron wrote: Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish.  It feels like I/O takes more

Re: suspend/resume regression

On 05/13/18 09:48, Andriy Gapon wrote: On 13/05/2018 05:25, Pete Wright wrote: hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stable for graphics. during the past week or so i've run into issues with suspend resume...well technically resume

Re: Regression Resume Lenovo T450

On 05/08/18 22:09, Manuel Stühn wrote: P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. What issues are you seeing with drm-next-kmod? Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailm

Re: Call for Testing: UEFI Changes

On 2018-03-25 14:52, Sheda wrote: >> >> I've tested on two different computers, my ThinkPad x230 and my desktop >> with a Intel DQ77MK motherboard. I've only done light testing such as >> loading efirt.ko and running efibootmgr to check the boot settings, but it >> has worked fine. >> I also haven

Re: Call for Testing: UEFI Changes

On 03/22/18 01:45, Kyle Evans wrote: Hello! A number of changes have gone in recently pertaining to UEFI booting and UEFI runtime services. The changes with the most damaging potential are: We now put UEFI runtime services into virtual address mode, fixing runtime services with U-Boot/UEFI as w

Re: Bad GPTZFSBOOT?

On 2016-01-27 04:07, Larry Rosenman wrote: > Can someone(tm) look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206659 for me? Just to get the same information here as in the PR. This seems to have broken between r294750 and r294770. There were a series of commits to the boot loaders in

Panic using QLogic NetXtreme II BCM57810 with latest CURRENT snapshot

Hi! I got the following panic with a QLogic NetXtreme II BCM57810 when trying to assign an IP address using dhclient. The network card uses the bxe driver. The machine in question is a HP DL380 Gen9. Kernel page fault with the following non-sleepable locks held: shared rw if_addr_lock (if_addr_l

[HEADS UP] xorg version switch in CURRENT

xorg. Please send reports of successes, failures and/or comments to x...@freebsd.org. Remember to include any relevant information, such as xorg logs (Xorg.log.0), dmesg, graphics card model and ports versions with your report. Please test this as much as possible! Regards! -- Niclas Zeising

Re: error: unknown warning group '-Wcpp', ignored (#pragma GCC)

On 05/25/13 12:09, O. Hartmann wrote: > With CLANG on FreeBSD 10.0-CURRENT r250968, I get this error message in > a source I try to port. > > I did not find any suitable "official" workaround and I'd like to avoid > patching all files containing those #pragma statements. Is there a > geenral solut

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

On 03/11/13 14:13, Steve Kargl wrote: > On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

On 2013-03-11 11:58, Hartmann, O. wrote: > Am 03/11/13 11:17, schrieb Dimitry Andric: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.8.0. AFAICT, the

Re: Response of *.freebsd.org websites are very slow

On 2013-02-27 20:25, Mehmet Erol Sanliturk wrote: > I have installed snapshot > > FreeBSD-9.1-STABLE-amd64-20130223-r247167-release.iso > > # traceroute ftp.freebsd.org > > 3 failures : traceroute : unknown host ftp.freebsd.org > 2 successes : > > Route is Izmir ( Turkey ) -> Frankfurt -> New Y

Re: 7+ days of dogfood

On 02/13/13 00:23, Jakub Lach wrote: > This is good moment to bring that around, > > https://wiki.freebsd.org/PortsAndClang > > "Help we don't want: > Submitting ports PR without fixes. We're not yet at the point > where it can help." That should probably be removed... Regards! -- Niclas

Re: 7+ days of dogfood

On 02/10/13 07:33, Ian FREISLICH wrote: > 1. WITHOUT_CLANG_IS_CC=yes >I don't think clang is ready for prime time in FreeBSD, or FreeBSD >isn't ready to use clang in prime time. I got a new laptop (ASUS >UX31A) and found that a lot of the ports I needed to install >didn't compile o

Re: 7+ days of dogfood

On 02/10/13 01:07, Steve Kargl wrote: > In a long thread started by Peter Wemm on developers@, he described > the move/upgrade of the FreeBSD.org cluster to using FreeBSD-10. A > part of his description included the need to test top-of-tree under > actual real-world conditions. In his words, Free

  1   2   >