r354057 Weekly Snapshot Works - my report

clay@bsd13:~ $ uname -a FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r354057: Fri Oct 25 05:24:01 UTC 2019 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I will note that when I tried to do pkg install drm-kmod, it returned error code 1 & failed. I reloaded the

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

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-*

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 fusefs-libs-2.9.9: fusefs-ntfs-2017.3.23 fusefs-ext2-0.0.10_2 fusefs-ext4fuse-0.1.3_1,1 clay@bsd13:~ $ pkg

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)

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. "kld_list=i915kms" just as you would for other modules. This will prefer the module built with your kernel if one exists and fall back to the

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

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 everything was going great. So last night, a little late I guess, I wiped the older install and loaded r250702. Then I loaded Xorg, all 172

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

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 and Forum, and try to learn all I can. So do you have any specific suggestions for programs

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