> Extents (2 meg blocks) are used for synchronization after the
> secondary is reconnected. Normally (the secondary is connected) writes
> to the primary and the secondary are the same.
Ah, Ok, that was not clear to me from the documentation. That would
also expain what I was seeing when I did a r
I have a number of machines in Azure, all booting from ZFS and, until
the weekend, running 10.3 perfectly happily.
I started upgrading these to 11. The first went fine, the second would
not boot. Looking at the boot diagnistics it is having problems finding the
root pool to mount. I see this is th
One extra datapoint - the machines which do not fail are the small DS1_v2
instances. These seem to boot fine, but if I move to the DS2 size then the
problem shows up.
-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
> The variable still exists but is ignored when using ZFS.
>
> It's a known issue. You could try this patch:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882#c3
Ah, OK, thanks...
> Manually specifying the root pool should workaround the issue.
Interesting, I didnt think of trying tha
> Are you sure the above transcript is right? There are three reasons
> I'm asking. First, you'll see the "Root mount waiting" message,
> which means the root mount code is, well, waiting for storvsc, exactly
> as expected. Second - there is no "Trying to mount root". But most
> of all - for so
/usr/src/sys/modules/mlx4ib/../../ofed/drivers/infiniband/hw/mlx4/sysfs.c:90:22:
error:
format specifies type 'unsigned long long *' but the argument has type
'u64 *' (aka 'unsigned long *') [-Werror,-Wformat]
sscanf(buf, "%llx", &sysadmin_ag_val);
Thanks - that is a better fix than my hack ;-)
On 03/15/17 20:12, Dimitry Andric wrote:
On 15 Mar 2017, at 13:42, Pete French wrote:
/usr/src/sys/modules/mlx4ib/../../ofed/drivers/infiniband/hw/mlx4/sysfs.c:90:22:
error:
format specifies type 'unsigned long long *' but th
So, the kernel attempted to mount the root even before vmbus was attached and,
thus, before storvsc appeared and informed the kernel that it might be holding
the root.
How ZFS was supposed to know that vmbus is ever going to appear?
To me this sounds more like a problem with the Hyper-V drivers.
> I don't like the delay and retry approach at all.
Its not ideal, but it is what we do for UFS after all...
> Imagine that you told the kernel that you want to mount your root from a ZFS
> pool which is on a USB driver which you have already thrown out. Should the
> kernel just keep waiting for
Using the lldb installed with 11-STABLE from an hour or so ago. Thoigh
I dont know when this started, as I have been using db until now.
First command I type is fine, subsequent commands, every keypress I
type looks like this:
(lldb) \U+7F68\U+7F65\U+7F08
That's an attempted 'bt' so something is
On 03/27/17 11:09, Andrea Venturoli wrote:
On 03/25/17 19:02, Andriy Gapon wrote:
Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors
with FreeBSD?
Will an equivalent Athlon do or is this Opteron specific?
What would that Athlon be?
Opteron 6100 was a K10 core, like t
Am running into a problem trying to compile a piece of code staticly
which ultimately uses opie. I get the following:
/usr/local/lib/libsasl2.a(otp.o): In function `opie_server_mech_step':
otp.c:(.text+0x345): undefined reference to `opiechallenge'
otp.c:(.text+0x414): undefined reference to `opie
Ignore me. I just found libopie. Duh. Sorry!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
now find the below backtrace from waagent when it tries to attach
the resource disc. It looks as if it is finding 'pass1' as the device,
when it should be finding 'da1'. As the waagents hasnt changed I am
wondering what might h
ime I tried it
clashed and didnt work at all actually). )
-pete.
On 05/26/17 13:30, Baptiste Daroussin wrote:
On Fri, May 26, 2017 at 01:26:46PM +0100, Pete French wrote:
Have upgraded one of my Azure boxes to 11.1-PRERELEASE yesterday, and I
now find the below backtrace from waagent when it
> The agent has just been updated in the ports tree a few days ago, can you
> try the new version?
Just checked and the version in ports is 2.2.8, and I am running 2.2.11
-pete.
..
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/m
A bit more investigation on this and I think I found what the differece is
at least. waagent is using camcontrol periphlist 3:1:0 to find devices,
and this has chnaged from placing the discs before the pass
devices to afterwards. So on an earlier version I get this:
root@joanna-may:/home/w
Just been through the azure python code - my intiial impressin was wrong, its
not the chnage to the periphlist output which is the issue. Instead
its the fact that a simple 'devlist' now puts the pass devices first in
the list, and the azure waagent uses the first listed device when it initially
lo
I am trying to attach a brand new disk to an azure VM, and
what I see is the disk attachng and detaching immediately like this:
da2 at storvsc3 bus 0 scbus5 target 0 lun 0
da2: Fixed Direct Access SPC-2 SCSI device
da2: 300.000MB/s transfers
da2: Command Queueing e
The HP micro servers work very well, and you can pick them up remakably
cheaply if you look. I have six of these in various laces, all running
ZFS and FreeBSD to perform various funcytions. Not sure about ECC memory
support there though. Also theres only one expansion slot, which we ut
10 gig c
> Maybe the folk that made hardware suggestions can post which net
> interface(s) they are using and whether they are seeing driver issues?
The HP boxes have Broadcom ethernet controllers driven with the 'bge'
driver, and thatw orks fine. I stick to Intel or Broadcom controllers for
gigabit ether
> temperature sensor is somehow controlled by the raid controller. So enabling
> JBOD technically works, but the machine is a lot louder than with enabled
> raid. As a workaround I've built 4 raid arrays with one disk each.
Upgrade the firmware. That fixed it for me - I run JBOD and the fanes are
I have an iSCSI production system that exports a large number of zvols
as the iSCSI targets. System is running FreeBSD 11.0-RELEASE-p7 and
initially all of the zvols were confugured with default volmode. I've
read that it's recommended to use them in dev mode, so the system isn't
bothered with
We recently moved our software from 11.0-p9 to 11.1-p1, but looks like there
is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) where
the virtual hn0 interface hangs with the following kernel messages:
hn0: on vmbus0
hn0: Ethernet address: 00:15:5d:31:21:0f
hn0: link sta
> Hmm, by ntpd I think you mean ntp client? You will have to disable
> timesync if you run ntp client:
> sysctl hw.hvtimesync.sample_thresh=-1
> sysctl hw.hvtimesync.ignore_sync=1
>
> They interfere w/ each other.
Oh! Does this apply to machines in Azure Hyper-V as well as on standalone
installat
Just off the phone with the lovely people at Exonetric (my hosting
provider - if you need FreeBSD in the UK then definitely go talk to them)
about a hardware refresh, and we are looking at the Epyc chips
from AMD. I have seen comments about people runnng on Zen, but nothing
from people on Epy yet.
I am in much the same situation as you (want to deploy Epyc, waiting for
SM stuff to become available). I currently have here a set of parts to
make a test Ryzen box, so you are ahead of me on that though. Should
have that gong this week I hope.
Are you running the latest STABLE ? There were s
Out of interest, is there anyone out there running Ryzen who *hasnt*
seen lockups ? I'd be curious if there a lot of lurkers thinking "mine
works fine"
To be honest this thread has put me off building my machine, the pile of
boxes with motherboard, case, cpu and ram is still sitting next to me
On 21/01/2018 19:05, Peter Moody wrote:
hm, so i've got nearly 3 days of uptime with smt disabled.
unfortunately this means that my otherwise '12' cores is actually only
'6'. I'm also getting occasional segfaults compiling go programs.
Isn't go known to have issues on BSD anyway though ? I ha
On 22/01/2018 18:25, Don Lewis wrote:
On 22 Jan, Pete French wrote:
On 21/01/2018 19:05, Peter Moody wrote:
hm, so i've got nearly 3 days of uptime with smt disabled.
unfortunately this means that my otherwise '12' cores is actually only
'6'. I'm also getting
On 23/01/2018 19:08, Mike Tancsa wrote:
It looks like this thread got mention on phorix :) In the comments
section (comment #9) a post makes reference to
http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen
I guess Linux is still working through similar lockups too :(
Int
>> I'm about ready to have a party. My Ryzen 5 1600 has been up for over 8
>> days so far after changing the memory to a slower speed. System load
>> hovers around .3
>
> I couldn't find an easy way to down-speed my memory in the bios :(
Out of interest, what motherboards are people using ? I st
On 28/01/2018 20:28, Don Lewis wrote:
I'd be wary of the B350 boards with the higher TDP eight core Ryzen CPUs
since the VRMs on the cheaper boards tend to have less robust VRM
designs.
Gah! Yes, I forgot that.originally sec'd the board for a smaller Ryzen,
then though "what the hell" and go
On 17/02/2018 20:19, Matt Smith wrote:
And thank you for pointing this out. I can now just wait a while to see
what comes along rather than accidentally upgrading it and killing the
already really slow performance.
I was just looking at this too, and wondering what (if any) the
performance
That won't work for the boot drive.
When no boot drive is detected early enough, the kernel goes to the
mountroot prompt. That seems to hold a Giant lock which inhibits
further progress being made. Sometimes progress can be made by trying
to mount unmountable partitions on other drives, but
Just perusing the commits on a sunday evenong and I happened across
this one: https://freshbsd.org/commit/freebsd/r313276
"Use kldload -n when loading if_deqna
This fixes if_deqna from being loaded by accident twice if it's already
loaded in the kernel."
Unless my memory fails m
Ah, thankyou! I haven;t run current before, but as this is such an issue
for us I;ll setup an Azure machine running it and have it reboot every
five minutes or so to check it works OK. Unfortunately the error doesnt
show up consisntently, as its a race condition. Will let you know if it
fails f
It looks like r330745 applies fine to stable-11 without any changes,
and there's plenty of value in testing that as well, if you're already
set up for that world.
Ive been running the patch from the PR in production since the original
bug report and it works fine. I havent looked at r330745
On 10/03/2018 23:48, Ian Lepore wrote:
I based my fix heavily on that patch from the PR, but I rewrote it
enough that I might've made any number of mistakes, so it needs fresh
testing. The main change I made was to make it a lot less noisy while
waiting (it only mentions the wait once, unless
I based my fix heavily on that patch from the PR, but I rewrote it
enough that I might've made any number of mistakes, so it needs fresh
testing.
Ok, have been rebooting with the patch eery ten minutes for 24 hours
now, and it comes back up perfectly every time, so as far as I am
concerned
I aalways found hast very easy to configure - I stopped using it a
couple of weeks ago, but up until then we had used it heavily in
production. Have found some old config files, which do work, as examples:
two machines - catbert-active, catbert-passive. catbert-active is
192.168.10.3, passive
On 20/03/2018 01:05, Dewayne Geraghty wrote:
We rebuild 11.1-Stable at least every two weeks. Our build on the 7th
Feb is in use on our development boxes, however the rebuild on 22nd
resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE
r329008. Is anyone actually running a St
So, resurrecting the thread from a few weeks ago, as I finally found
time yesterday to out together the Ryzen machine I bought the parts for in
Jaunary (busy year at work). All went smoothl;y, checked it
booted up, used it for 15 minutes, was impressed by the speed and went home.
...and by the
On 20/04/2018 12:48, Nimrod Levy wrote:
I'm really glad to see that I'm not the only one still interested in
this thread. I don't really have anything new to contribute. I've been
getting about a week or so uptime out of my box. My habit has been to
see if it hangs, then reboot and rebuild l
This amsued me. If I run 'sysctl -a' on a box with a ConnectX-2 card in
it then I get this message on console:
"mlx4_core0: port level mtu is only used for IB ports"
Quite surprised that listing sysctls results in messages to console!
-pete.
___
freebs
> Its not just the Ryzen, I can lock up Epyc CPUs as well. They take a bit
> longer, but its not that hard to repeat. Unfortunately, I had to
> allocate this hardware over the Linux where it works reliably under all
> workloads without any such lock ups with all the default BIOS settings :(
AH, th
> And of course now that we say something about it, I get a lockup
> overnight...
Sods law I guess. Mine survived the weekend quite happily though, so am
fairly pleased with that. Am going to try the test case that Mike Tancsa
posted to see if I can get it to lockup today though,. now that I am in
> I have a Ryzen system
> parts: https://pcpartpicker.com/list/HhycYT
> dmesg: http://dmesgd.nycbug.org/index.cgi?do=view&id=3516
>
> which I have been using for months without issue and on completely
> default settings.
Thats encouranging -= and I think you are the first person to report
that wit
> fairly pleased with that. Am going to try the test case that Mike Tancsa
> posted to see if I can get it to lockup today though,. now that I am in
> front of it to reset of required. Will report results either way...
So, I have been ran the iperf scripts all day (about 4 hours now) with
the Ryze
On 24/04/2018 14:56, Mike Tancsa wrote:
I was doing the tests with bhyve, and the iperf tests were between VMs
on the same box. That seems to trigger it fairly quickly. The Epyc took
a bit more work, but I could reliable do it there too.
Well, I ranh the iperf tests between real machine for
processor clocks and thus dont surprise me
too much as a soource of instabuloty, but I am surprised that SMT causes
issues, as that should (I belive) simply present as two cores.
On 24/04/2018 15:22, Mike Tancsa wrote:
On 4/24/2018 10:01 AM, Pete French wrote:
Well, I ranh the iperf tests
It would be interesting to test other AMD CPUs. I think AMD and Intel
have some differences in the virtualization implementations.
I've been using AMD CPU's pretty extensively since the early 90's - back
then I was running NeXTStep and out of the three Intel alternatives it
was the only one
So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was
closes as fixed. I cant remember if there was another bug report for ongoing
Ryzen issues at all - I have been experimenting and have re-enabled most of
the BIOS setting and tweaks fne, but I still need SMP disbled or it
The compile bug has been fixed for me. However, last I checked I can
still freeze a system by generating a lot of network traffic between VMs
in either bhyve or virtbox. Its been a while since I tested (couple of
months) but I dont recall anything obviously committed that highlighted
that iss
On 03/06/2018 18:49, Mike Tancsa wrote:
I have c-states disabled on the ryzen both for FreeBSD and Linux. To
disable SMP on the Epyc doesnt seem to be possible. But then again kill
off 31 cores is a heavy cost to pay for stability :( When I am back at
the office, I will see if a recent chec
> Check out this thread on current. I re-ran the tests I did in Feb to
> lockup the Ryzen box, and they are ok now with the latest micro code
> updates from AMD. I will let the tests run a good 48hrs, but in the
> past it would only take 5-10 min to cause a hard lockup
>
> https://lists.freebsd.or
On 18/06/2018 14:59, Mike Tancsa wrote:
FYI, both my Epyc and Ryzen system have been running 2+ days with the
tests that would normally hard lock the system in 5-60 min. The combo of
Microcode updates and system settings
Thats for the update - I turned all the default motherboard settings
b
I use VirtualBox all the time on 11-STABLE. I do make sure I recompile
the ernel module every time I rebuild the OS, but its pretty solid for
me. You need the AIO tunings though.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
-pete.
___
fre
> On 06/18/2018 09:34, Pete French wrote:
> > Preseumably in the slightly longer term these workarounds go into the
> > actual kernel if it detects Ryzen ?
>
> Yes, Kostik said he would code this into the kernel after he gets enough
> feedback.
So, I've been runn
> If you run without the script, with the same settings, do you experience
> problems ?
I have not tried this since the last BIOPS update which brought with it
the latest AEGSA version. Previously the machine would lock uop
if I enabled SMT though which is why looking at those settings
and cross r
Gah! I my memory said it was /var/boot - so close :-) Thanks!
On 26/06/2018 15:22, Freddie Cash wrote:
On Tue, Jun 26, 2018, 5:33 AM Pete French, <mailto:petefre...@ingresso.co.uk>> wrote:
> Also, please show the 100 first lines of the verbose boot dmesg
on this
> % sudo x86info -a | grep Microcode
> Microcode patch level: 0x8001136
>
> Without that script, the system would lockup up to 5-6 times a day.
> Now running without any lockup at all for 3 days, with all kinds
> of workload from idle to torture tests. Too early to tell, but it
> looks good for now
> This should be the kernel patch equivalent to the script.
Ah, thankyou. I shall give this a try on tuesday when I am
physically back in front of the machine. I have been trying without
the oath as you asked by the way, and with the latest microcode
update (0x8001137) it also seems stable, withou
It is very likely that the latest microcode sets the chicken bits for the
known erratas already. AFAIK, this is the best that a ucode update
can typically do anyway.
I just did some testing - it does do these bits:
cpucontrol -m '0xc0011029|=0x2000' $x
cpucontrol -m '0xc00
On 03/07/2018 11:09, Konstantin Belousov wrote:
On Tue, Jul 03, 2018 at 10:27:06AM +0100, Pete French wrote:
It is very likely that the latest microcode sets the chicken bits for the
known erratas already. AFAIK, this is the best that a ucode update
can typically do anyway.
I just did
So, I got my first lockup in weeks, testing with the latest stable
and the patch which sets the kernel bits. But I cant say it its
Ryzen related or not.
Meanwhile I also got access to an Epyc server in Azure. Am also
runing the latest STABLE on that tp see how it goes. Interesting
thing there is t
> It does not make any sense to even try to access the chicken bits
> MSRs when running under virtualization. It is the duty of the
> hypervisor to configure hardware.
I would tend to agree with you :-) I was kind of surprised to read that they
are actually saved and restored as part of a VM con
On 05/07/2018 11:47, Konstantin Belousov wrote:
Why do you state that they are saved/restored ? What is the evidence ?
https://software.intel.com/en-us/blogs/2009/06/25/virtualization-and-performance-understanding-vm-exits
specificly...
3) "Save MSRs in the VM-exit MSR-store area."
and
> This is true, but absolutely irrelevant.
>
> Modern CPUs have hundreds, if not thousands, MSR registers. Only some of
> them define architectural state, and saved/restored on the context switches.
> Chicken bits are global knobs not relevant to the vmm entry.
That actually makes far more sense.
/usr/bin.mail (still my preferred mail reader) has just started
coredumping on me when I delete seom messages. A trace is below,
and I notice http://www.freshbsd.org/commit/freebsd/r335693
is applying some fixes in the area I am seeing coredumps
-pete.
#0 sigchild (signo=) at /usr/src/usr.bin/ma
:56, Eitan Adler wrote:
On Fri, 6 Jul 2018 at 05:52, Pete French wrote:
/usr/bin.mail (still my preferred mail reader) has just started
coredumping on me when I delete seom messages. A trace is below,
and I notice http://www.freshbsd.org/commit/freebsd/r335693
is applying some fixes in the area I
> Am going to try that. I should have added that the cordeump happens when
> I am viewing an email inside 'more' and I quit out of it, not when I try
> and delete it, I was wrong about that.
>
> Will give it a go with that chnage revertsed and let you know
Reverting the chnage makes the core
> Understood. Like I said, my development box is dead, so expect nothing
> for the next couple of weeks [0] unless someone gets to it first.
Ok, no worries. Will you revert the chnage in STABLE until then, or
should I continue running with it reverted locally ? I will try and
look at it myself if
Yesterday I inreased my memory speed on my Ryzen box from 2133 to 2400
as I had previously been underclocking it. Ryzens are sensetive to
memory clock speed as it affects the speed of the underlying fabric
between the cores as well as I understand it, so worth running it at
its rated speed.
I meau
On 22/07/2018 02:48, George Mitchell wrote:
Based on people's recent Ryzen experiences, is it fair to say that
FreeBSD 11.2 is now believed to work on Ryzens, if you have a recent
enough Ryzen and your motherboard has been updated to the latest BIOS?
I would still use the patches provided in
Hmm, I gte a core dump trying to run any Linux binary at the moment (stable
from Tuesday - r336665). I have remoed all packages and re-installed
and running /compat/linux/bin/bash coredumps. Running ldd on it coredumps
too, and gdb gets e nowhre.
Unfortunately I have no idea when it last worked, a
> Hmm, I gte a core dump trying to run any Linux binary at the moment (stable
> from Tuesday - r336665). I have remoed all packages and re-installed
> and running /compat/linux/bin/bash coredumps. Running ldd on it coredumps
> too, and gdb gets e nowhre.
I did a bit more testing on this. It only a
So, I have been running the patched kernel for quiet a while now, and it
works fine for me, but last night I did hit a surprising issue - the
Linux emulator does not work on Ryzen / Epyc. I tried this on two
machines (both with the patches) and it coredumps when simply running
bash on both of t
I highly doubt that this can be related.
Well, yes, it suroprised me too :-) Admittedly I dont have a very big
samle set - I nly have one Ryzen box and a pair of Epyc boxes in Azure.
but I cant make it run on any of them. I take the same OS and run it on
Intel and its fine (literally I am
On 27/07/2018 14:10, Mike Tancsa wrote:
I havent used the linux emulator in ages. What is the easiest way to try
this out ?
in rc.conf have
linux_enable="YES"
when you boot. then
pkg install linux_base-c7
/compat/linux/bin/bash
and you should see a bash pprompt f
I just brought everything upto date and re-tested and same issue.
FreeBSD 11.2-STABLE #1 r336761
# mount | grep -v zfs
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
linsysfs on /compat/linux/sys (linsysfs, local)
tmpfs on /compat/linux/dev/shm (tmp
> Mark Johnston fixed this. See
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230196
Thanks - I saw the commit go in earlier, but I hadnt checked my email
until now. Sorry I didnt investigate this myself, as I am perfectly capable
of doing so, to be honest, just very short of time :-(
cheer
having enabled local_unbound in /etc/rc.d how do I remove that
and go back to using just DHCP delivered nameservers ? I
set it to 'NO' but yet the machine still seems to have traces of
the config in other places and keeps trying to use them, for reasons I
dont understand.
Is there a quyick guide t
Hmm. First, make sure that it isn't running (service local_unbound
stop, etc).
Then look at your /etc/resolv.conf -- unbound tends to rewrite that
on initial
startup, taking some of it's settings and inserting itself into the
middle as a
caching DNS server. At the v
So, having been stable for quite sme time, I have had three lockups on
my Ryzen in the last week. two were whilst I was in X11, but one
happened over the weekend whilst I was looged out, and thus I could get
a screenshot of what was on the console when I got in this morning:
https://www.twi
So, I was trying to switch to using this, as I realise its where things
are heading, and I rather like the look of it. But I cant get it to see my
multiple monitors. I install the port, set 'kld_list="amdgpu"' and it boots
up with the new modules, and appears to find all my displays in dmesg. But
w
I think you have to use kld_list="/boot/modules/amdgpu.ko" to get the
new one.
Will give it a try - I think its unnecessary as the name doesnt clash,
but worth a go...
-pete. [quick reboot comming up]
___
freebsd-stable@freebsd.org mailing list
On 11/09/2018 14:42, Pete French wrote:
I think you have to use kld_list="/boot/modules/amdgpu.ko" to get the
new one.
Will give it a try - I think its unnecessary as the name doesnt clash,
but worth a go...
-pete. [quick reboot comming up]
I tired this, it doesnt help -
I'd try a make deinstall inside drm-stable-kmod and drm-legacy-kmod
directories and see if that fixes anything.
On Tue, 11 Sep 2018 13:50:24 +0100
Pete French wrote:
So, I was trying to switch to using this, as I realise its where
things are heading, and I rather like the look of it. But I
can you post your dmesg output from when you've set
kld_list="/boot/modules/amdgpu.ko"? also, please verify that your user
is in the "video" group. but from what you've described it sounds like
a conflict is popping up between the base amdgpu.ko and the one
available in the ports tree.
also
Starting from the beginning:
how the "drm.ko" is loaded ?
Thats a very good question! I am not loading it myself
explicitly anyhere, so my guess is that xorg is loading it.
On the machine right now (which I was using with X11 yesterday)
it only has drm2 loaded - again, I assume from starting
I believe your best bet is to let Xorg probe your devices automatically
- i.e. don't have an xorg.conf in place when starting X.
Yes, I dont have an xorg to conf - I was a bit unclear, I meant which
drivers should I instal from the xorg-drivers package as I dont
generally install all of the
it's from the xorg-server port/pkg:
$ pkg list xorg-server|grep modes
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
/usr/local/man/man4/modesetting.4.gz
Ah, OK, in that case I would have had it when I did my experiment with
remiving all the existing xf86-* drivers. I wont be able to
> I would like to build a Ryzen desktop.? Can anyone recommend a good
> motherboard?
I have oe of these:
https://www.msi.com/Motherboard/X370-XPOWER-GAMING-TITANIUM
but I just saw how much they are charging for it these days! I got one
at about half that. I did originally get a B370 based board
I just upgraded to STABLE, having been running r338093 since the end of August,
and was su[psised when it locked up on boot for me. By which I mean the keyboard
is unresponsible and the SATA drive access LED is on permamently.
I have a small encryopted partition, and the boot gets as far as asking
On 03/10/2018 15:16, Pete French wrote:
The machine is booting ZFS (unencrypted) and is a Ryzen CPU. I will
start trying to work out where the offending commit is, but if anyone
has an insight which might help shortcut the process then please let me know.
Been testing various kernels since
On 04/10/2018 20:54, Doug Hardie wrote:
I have a number of production servers that only have bge and I don't see that
listed in either category. None of them are running FreeBSD 12 yet as it has
not been released. Also there are some with rl. Those are add-on boards so
they could be chan
> Been testing various kernels since I posted this, currently at r338931
> which runs fine. Will continue on Friday as am not inf ront of the
> machine tomorrow.
Just to uodate this, I have tried the update from this morning, r339193, and
tthat works fine. I noticed some more ZFS stuff went in,
So this is kind of interesting - I posted here last month about trying to
use drm-next and it not finding my 2nd monitor properly. I did try and
subscribe to x11@ but for some reaosn that didnt work, and I didnt worry
abotu it too much so didnt investigate further as I wont be running 12.0
for a wh
, xrandr only showed one outout on
the card, which puzzled me (there are 4 outputs).
-pete. [copying to -stable so others know the outcome]
On 16/10/2018 12:39, Niclas Zeising wrote:
On 10/9/18 12:32 PM, Pete French wrote:
So this is kind of interesting - I posted here last month about trying to
501 - 600 of 789 matches
Mail list logo
