13.0-ALPHA2 is a Winner!

The bufdaemon has been tamed! 13.0 really is impressive, no joke. Thanks to all the developers and such. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Weekly 13.0 snapshot works Great!

Weekly snapshot works Great! clay@fbsd:~ $ uname -a FreeBSD fbsd 13.0-CURRENT FreeBSD 13.0-CURRENT #0 7578a4862f0-c255032(main): Thu Dec 10 11:40:27 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 Dmesg attached Dmesg Description: Binary data

Re: New FreeBSD snapshots available: main

clay@bsd13:~ $ uname -a FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 1544934ffb2-c253004(main): Thu Sep 10 06:18:34 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 Works great, no problems with snapshot, thanks much Glen & everybody.

Re: Weekly Current 13.0 Snapshot?

> > On Thu, Aug 20, 2020 at 3:47 PM Glen Barber wrote: > >> On Thu, Aug 20, 2020 at 04:41:59PM -0500, Clay Daniels wrote: >> > I hope nobody is ill & just busy filling the weekly snapshot of 13.0 >> > Current with new goodies. I don't see it at it's usual loca

Weekly Current 13.0 Snapshot?

I hope nobody is ill & just busy filling the weekly snapshot of 13.0 Current with new goodies. I don't see it at it's usual location: https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/ Clay ___ freebsd-current@freebsd.org mailing

Re: nightly snapshot for CURRENT ?

On Tue, Jun 9, 2020 at 2:48 PM Emmanuel Vadot wrote: > > Hello all, > > I've just hit again something that I've hit (and probably others too) > often. > If a change in base break some ports and it's snapshoted in the txz > available at download.freebsd.org, you need to wait a week for the

Re: ZFS BE not booting

> > [... snip ...] > > > Is there something I'm perhaps missing regarding loader.conf and/or > rc.conf ? > I may be wrong, but it looks like a "framebuffer problem" that is most often associated with amdgpu, but may help your i915 intel graphics too. Just try adding this to /boot/loader.conf :

Re: Working on Zoom port

On Tue, Apr 14, 2020 at 3:31 AM Jan Beich wrote:> According to [1] latest firefox nightly builds now support audio in> zoom. This nightly builds are not available for FreeBSD but you can try to build it from sources. > > [1] > > >

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

On Sat, Apr 11, 2020 at 2:06 AM Niclas Zeising wrote: > > How did you install the driver? > When using the drm drivers on current, you usually have to build them > from ports rather than use the packages, this way the driver matches the > kernel you are using. > Regards > -- > Niclas > Thanks,

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

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 show as normal, but stalled out there.

Re: When will the FreeBSD (u)EFI work?

"*Stop* blockquoting massive amounts of reply text, it is not necessary, trim it out leaving only the few lines of what you are replying to directly above your reply." What good advice. I finally figured out how to do this in gmail:

r358133 snapshot works fine

clay@fbsd:~ % uname -a FreeBSD fbsd 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r358133: Thu Feb 20 04:41:10 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 The reason I bother the list is that I had trouble getting drm-kmod loaded right for the last two weeks of

Re: OFWBUS: How does autoconfiguration work?

Take a look at the Porter's Handbook: https://docs.freebsd.org/doc/7.4-RELEASE/usr/share/doc/en/books/porters-handbook/using-autotools.html On Sat, Feb 1, 2020 at 8:56 AM Niteesh wrote: > I am interested in adding autoconfiguration to one of my projects. > The current drivers use lazy

kyua test

I've started running kyua test when I load the weekly current snapshot, and I'm a little confused about if I should run kyua test as user or root. In order to make the /usr/ports/devel/kyua port you need to be root and I have just been doing the test as root, but I notice in the instructions I'm

Re: 13.0-CURRENT r356767 wanted ZFS

, 2020 at 12:18:41AM +0000, Clay Daniels wrote: >> >>> >> 13.0-CURRENT r356767 would not take NO for an answer, and kept up a >>> loop >>> >> until I gave up trying to use UFS. No big deal, seems to work fine... >>> >> >>&g

Re: 13.0-CURRENT r356767 wanted ZFS

.20200117-002752-646645.db 7652/7761 passed (109 failed) clay@bsd13:~ % kyua test -k /usr/tests/Kyuafile On Fri, Jan 17, 2020 at 12:29 AM Yuri Pankov wrote: > David Wolfskill wrote: > > On Fri, Jan 17, 2020 at 12:18:41AM +0000, Clay Daniels wrote: > >> 13.0-CURRENT r356

13.0-CURRENT r356767 wanted ZFS

13.0-CURRENT r356767 would not take NO for an answer, and kept up a loop until I gave up trying to use UFS. No big deal, seems to work fine... Clay ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current

r355889 snapshot works fine

I was a bit worried with all the talk in drm changes, but just fine here. AMD Ryzen 7 3700x/MSI 570 chipset Motherboard & Video card I did notice the drm-current-kmod had a date of 12/17/2019: Works fine. dmesg: nvd0: 976762MB (2000409264 512 byte sectors) hdacc0: at cad 0 on hdac0 hdaa0: at

FreeBSD 13.0-CURRENT r355634 weekly snapshot works Great!

clay@bsd13:~ $ uname -a FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355634: Thu Dec 12 04:17:50 UTC 2019 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 clay@bsd13:~ $ kldstat Id Refs AddressSize Name 1 77 0x8020 1f073a0 kernel

13.0-CURRENT r355121 snapshot .img Works Great!

drmn0: successfully loaded firmware image with name: amdgpu/polaris~ AMD Ryzen 7 3700x cpu with MSI 570 series Motherboard & Video Card [Home built machine] Able to make drm-kmod from ports Third week in a row with no problems! Clay ___

Re: FreeBSD Friday

itten a utility, snapaid, that makes is much easier > to fetch the latest snapshot: > https://github.com/jmgurney/snapaid > > Hope people find it useful. > > > On Fri, 22 Nov 2019 at 22:21, Clay Daniels > > wrote: > > > > > Just my two cents worth, but I

Re: FreeBSD Friday

Just my two cents worth, but I think you would have more fun and learn new stuff if you followed weekly the 13.0 Current snapshots all shown at the same place, most every Thursday: https://www.freebsd.org/where.html Pick the i386 for your intel laptop. You will get the most up to date install

FreeBSD 13.0-CURRENT r354423: Nice!

ugen1.2: at usbus1 drmn0: successfully loaded firmware image with name: amdgpu/polaris10_mc.bin Real Nice! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: GhostBSD and FreeBSD-sources

GhostBSD is downstream to FreeBSD. Take a look at DistroWatch: https://distrowatch.com/search.php?ostype=BSD=All=All=FreeBSD=None=All=All=All=All=All=All=All=All=Active#simple On Fri, Nov 1, 2019 at 3:28 PM Miranda van den Breukelingen < mms.vanbreukelin...@gmail.com> wrote: > Dear specialists,

Re: r354057 Weekly Snapshot Works - my report

What I intended to say is that "make install clean" returned error 1 and failed, But "pkg install drm-kmod" worked On Fri, Oct 25, 2019 at 3:56 PM Clay Daniels Jr. wrote: > clay@bsd13:~ $ uname -a > FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r354057: Fri

r354057 Weekly Snapshot Works - my report

aded the basic r354057 install, did a Pkg install drm-kmod, and it worked with no problems. (With the new drm-current-kmod dated 10-23-19) This is my first good install since r353072 of Oct 4th. Thanks to all the developers who work on this, and for answering all my ignorant questions. Clay Dan

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

9 at 4:33 PM Niclas Zeising wrote: > 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) &g

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

sorry, should be all 3 installed (drm-kmod, drm-current-kmod, & gpu-firmware-kmod) On Wed, Oct 23, 2019 at 2:50 PM Clay Daniels Jr. wrote: > r353709 > Looked promising, but failed: > > Loaded r353709 > make install drm-kmod, all 3 installed > (drm-devel-kmod, drm-curren

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

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 install xorg rebooted and ran startx panic:

Re: r353072 > r353427 > r353709

On 10/20/19 3:42 AM, Gary Jennejohn wrote: This is a patch to a file used in the port itself, not to the kernel sources under /usr/src/sys. This should be pretty clear from this line in the referenced link to the posting in freebsd-current: # cat files/patch-linuxkpi_gplv2_src_linux__page.c

Re: r353072 > r353427 > r353709

On 10/19/19 4:54 AM, Evilham wrote: Have you seen the recent threads about this? Particularly this with some steps that worked-for-me (tm):  https://lists.freebsd.org/pipermail/freebsd-current/2019-October/074660.html -- Evilham i looked at the patch  & made a file which says: diff --git

Re: r353072 > r353427 > r353709

t 19, 2019 at 4:54 AM Evilham wrote: > > On ds., oct. 19 2019, Clay Daniels, Jr. wrote: > > > r353709 of today 18 Oct has only gone down hill. I tried to load > > it a half > > dozen times, gave up and then tried re-installing r353072 which > > was working > >

r353072 > r353427 > r353709

r353072 from 4 Oct worked great! r353427 from 11 Oct last week did not. It had some drm-kmod problems and I quickly dumped it and reloaded r353072 as I was hot to work on a project of my own. That only bought me a week, did not solve the problem. r353709 of today 18 Oct has only gone down hill.

Re: AMD Secure Encrypted Virtualization - FreeBSD Status?

Simon, please do elaborate more on your implementation. I suspect you are talking about libsecureboot? I have played with the generation of certs with OpenSSL & LibreSSL, but libsecureboot seems to take a different approach. Please tell us more. Clay On Mon, Oct 14, 2019 at 1:52 PM Simon J.

Re: AMD Secure Encrypted Virtualization - FreeBSD Status?

Grarpamp,Tomasz, and all: Thanks for all the reference documents. I looked through them, and did some more research myself: Creating Secure Boot Keys --- 0. https://wiki.freebsd.org/SecureBoot A work in progress. --- 1. http://www.rodsbooks.com/efi-bootloaders/controlling-sb.html Need: openssl -

Re: AMD Secure Encrypted Virtualization - FreeBSD Status?

Just whose secure keys do you suggest? I go to a lot of trouble to disable secure boot so I can load any operating system I want. On Thu, Oct 3, 2019 at 11:10 AM Tomasz CEDRO wrote: > would be really nice also to get UEFI BOOT compatible with SECURE BOOT :-) > > > -- > CeDeROM, SQ7MHZ,

CURRENT r352544 & new drm-current-kmod worked fine

I noticed a new : drm-current-kmod Version: 4.16.g20190918 Worked fine with my AMD R7 and "amdgpu" I needed the line in /boot/loader.conf hw.syscons.disable=1 Note: I tried first without adding the loader.conf line. Same story, cannot boot in framebuffer mode, but now I know the trick I

Re: Another X server start failure

Assuming you are running 13.0 Current, and already put the entry in /etc/rc.conf: kld_list="amdgpu" #Yes, no path needed, just "amdgpu" Having done that, try this in /boot/loader.conf hw.syscons.disable=1 # then reboot I'm not the expert here, but the cause is what I might call a

Re: AMD & 13.0 Current

een with 3 xterminals and a clock. On Sun, Sep 15, 2019 at 7:25 PM Clay Daniels Jr. wrote: > Mark, the line added in /boot/loader.conf was shared by others on this > list in August when I missed my usual install of the weekly 13.0 Current > snapshot. Turned out to be what could be called a &

Re: AMD & 13.0 Current

give it a try. Clay On Sun, Sep 15, 2019 at 6:20 PM wrote: > On Sun, Sep 15, 2019 at 05:29:36PM -0500, Clay Daniels Jr. wrote: > > I have built me a new computer, put it together, and being impatient did > > not even partition the 2TB WD HD, but just installed last weeks Current. &g

AMD & 13.0 Current

I have built me a new computer, put it together, and being impatient did not even partition the 2TB WD HD, but just installed last weeks Current. Worked great! Now that I have these two to compare I will share the details and results, particularly if you are using AMD CPR/Radeon Graphics. The

Re: "cpuset -n prefer:?" --what values for "?" are supposed to be allowed? (only 1 is, despite two numa domains)

Mark, this is what I get on my machine: root@new:~ # cpuset -g pid -1 mask: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 pid -1 domain policy: first-touch mask: 0 root@new:~ # cpuset -l0 -n prefer:0 COMMAND cpuset: COMMAND: No such file or directory root@new:~ # cpuset -l0 -n prefer:2

Re: fusefs & ntfs-3g

PM, Alan Somers wrote: >> > On Sun, Sep 8, 2019 at 5:00 PM Clay Daniels Jr. < >> clay.daniels...@gmail.com> >> > wrote: >> > >> >> I want to view my Windows C: drive on ata0p4. >> >> This is what I have: >> [...] >> >&g

fusefs & ntfs-3g

I want to view my Windows C: drive on ata0p4. This is what I have: FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r351901 GENERIC amd64 clay@bsd13:~ % pkg info -r fusefs-libs fusefs-libs-2.9.9: clay@bsd13:~ % pkg info -r fusefs-libs3 fusefs-libs3-3.6.2: clay@bsd13:~ % cat /boot/loader.conf

Re: FUSE & fusefs-*

i, Aug 30, 2019, 12:45 PM Clay Daniels Jr. > wrote: > >> I finally have a little time to play with the FUSE, and installed some >> fusefs utilities I might like to try, for ntfs & ext. This is what I have: >> --- >> clay@bsd13:~ $ pkg info -r fusefs-libs >> fuse

FUSE & fusefs-*

hing mission critical, but any help would be a appreciated. I think it would be handy to mount ntfs & ext partitions from my ufs FreeBSD partition. Clay Daniels ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: Adding DRM modules to /etc/rc.conf for 13.0 Current r351363 (drm-current-kmod g20190814)

Oops, should be *hw.syscons.disable=1* in /boot/loader.conf On Mon, Aug 26, 2019 at 8:56 PM Clay Daniels Jr. wrote: > RE: > "In order to use these modules, you need to update the 'kld_list' >lines in your rc.conf to just list the modules without a >path, e.g. "

Adding DRM modules to /etc/rc.conf for 13.0 Current r351363 (drm-current-kmod g20190814)

s and fall back to the module in /boot/modules otherwise." WORKED GREAT, even with my kld_list="amdgpu" without the path, but I must add that I needed to add a line in /boot/loader.conf to work around the known AMD problem: hw.syscons/disable=1 Clay Daniels _

Re: "amdgpu and radeonkms are known to fail with EFI Boot"

of cake. Thanks so much, Clay Daniels On Sat, Aug 24, 2019 at 3:14 PM Evilham wrote: > > On ds., ag. 24 2019, Clay Daniels, Jr. wrote: > > > Greg, thanks for the wonderful suggestion. Where should I put > > this line: " > > hw.syscons.disable=1 "

Re: "amdgpu and radeonkms are known to fail with EFI Boot"

run startx (as user) still fails. Maybe there is some boot config file this goes in? Thanks Clay On Sat, Aug 24, 2019 at 3:29 AM Greg V wrote: > On August 24, 2019 10:15:22 AM GMT+03:00, "Clay Daniels Jr." < > clay.daniels...@gmail.com> wrote: > >From the kmod ports

"amdgpu and radeonkms are known to fail with EFI Boot"

>From the kmod ports, dated 20190814 /usr/ports/graphics/drm-current-kmod/pkg-descr "amdgpu and radeonkms are known to fail with EFI Boot" /usr/ports/graphics/drm-current-kmod/pkg-message "some positive reports if EFI is not enabled" Any practical suggestions on getting drm-current-kmod to

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

I would agree with Karl & Steffen about using rEFInd. It really gives you a lot more control of your computers boot. Take a look at Rod Smith's pages: http://www.rodsbooks.com/refind/ I use it to triple boot Windows 10, MX Linux, and FreeBSD. Clay On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger

Re: Installing drm-current-kmod from ports

e basic Xorg page with the three Xterms & a clock, it will not load a fancy desktop. Thanks so much for your help, Graham Clay On Sun, Aug 18, 2019 at 3:59 PM Clay Daniels Jr. wrote: > Graham, thanks for the reply. Since my original post on this thread last > night, I went through the ma

Re: Installing drm-current-kmod from ports

o log off, re-boot into my FreeBSD partition, and try to install xf86-video-ati, probably from the ports, under graphics I guess. Thanks a lot, Clay On Sun, Aug 18, 2019 at 3:16 PM Graham Perrin wrote: > On 18/08/2019 03:08, Clay Daniels Jr. wrote: > > … am I missing something else? … >

Installing drm-current-kmod from ports

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 ports, which I have installed, as well as the

Re: 13.0 Current - r350702 exposed a Xorg failure

lay On Wed, Aug 14, 2019 at 3:09 AM Graham Perrin wrote: > On 10/08/2019 04:56, Clay Daniels Jr. wrote: > > drm-kmod was the same (g20190710) > > It's equally (if not more) important to consider what's installed by > drm-kmod. > > Can you share output from these thre

FreeBSD-13.0-CURRENT 20190815-r351067 is online

FreeBSD-13.0-CURRENT-amd64-20190815-r351067-disc1.iso.xz ___ freebsd-current@freebsd.org mailing list

Re: 13.0 Current - r350702 exposed a Xorg failure

, 2019 at 9:49 PM Pete Wright wrote: > > > On 8/9/19 8:56 PM, Clay Daniels Jr. wrote: > > I was eager to load the new 13.0 Current snapshot yesterday as I wanted > to > > play with the new FUSE tools. I was running 13.0 Current r350491 from > last > > week and ev

13.0 Current - r350702 exposed a Xorg failure

d was the same (g20190710) that had worked for me at least two times already. I do not know if the Xorg pkg is the same. I couldn't find a date other than "latest". I'm writing this email from my Linux partition. Any ideas would be appreciated, Clay Daniels ___

Re: FUSE Call for Testing

n Fri, Aug 9, 2019 at 4:21 AM Clay Daniels Jr. > wrote: > >> Alan, I'm pretty much into 13.0 Current and most weeks install the newest >> snapshot build. I don't know if I use FUSE or not, if you must know the >> truth. I do some hobby coding, lurk here on the email lists

Re: FUSE Call for Testing

to install and test FUSE? I kind of like the no-x console & the Xterminal window too, and dabble with clang cc (strictly C, no C++) and Python too. Let me know. Clay Daniels On Thu, Aug 8, 2019 at 1:36 PM Alan Somers wrote: > The new FUSE driver has just landed in current. It raises the p

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

Rodney, you are right that the .iso "should work", and a lot of other projects, from Microsoft Windows 10 to Trident BSD only a furnish an iso, and no img file. FreeBSD is one of the few that give you both choices. The problem goes deeper than any one operating system. If you've ever used the

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

The .iso files are for a dvd install. If you want to use a usb, download the .img files. FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img ( or get the .xz