to this. Checking here first to make sure this isn't
already known/expected behavior.
Thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
twitter => @nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/free
On 11/12/15 09:44, Pete Wright wrote:
> Hi All,
> Just wanted a sanity check before filing a PR. I am running r290688 and
> am seeing a LOR being triggered in the mpr(4) device:
>
> $ uname -ar
> FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r290688: Wed Nov 11
&
the
latest 11-CURRENT snapshot, and I have been able to reproduce this on
several hypervisors.
Has anyone else seen this?
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
twitter => @nomadlogicLA
___
freebsd-current@freebsd.org mailing list
ht
Closing the loop on this for the archives - I am no longer seeing this
LOR as of r291998.
-pete
On 12/08/15 11:36, Pete Wright wrote:
> Hey All,
> I am seeing a repeated LOR on r291495 that is pretty reproducible. This
> happens right after the system boots:
>
> lock order r
not having to package the whole base,
and download install it on my test rig, would be a nice time saver.
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
er (see Kernel configuration)?
>
it may be helpful to investigate your system using mfiutil(8). It's
possible you have flaky hardware as I have used that card before with
out issues IIRC.
Hope this helps,
-pete
--
Pete Wright
p...@nomadlogic.org
twitter => @nomadlogicLA
On 04/30/16 19:02, Allan Jude wrote:
On 2016-04-30 19:45, Pete Wright wrote:
I recently acquired a Lenovo M900 Tiny desktop system which comes with
an intel i7-6700T Skylate CPU and Intel HD 530 graphics processor. I am
successfully running 11-CURRENT via EFI but have three devices which I
On 04/30/16 17:49, K. Macy wrote:
On Sat, Apr 30, 2016 at 4:45 PM, Pete Wright <p...@nomadlogic.org> wrote:
I recently acquired a Lenovo M900 Tiny desktop system which comes with an
intel i7-6700T Skylate CPU and Intel HD 530 graphics processor. I am
successfully running 11-CURRENT v
= 'Wireless 8260'
class = network
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
d?
Yea I can second this - IIRC it looks like around Sept or Oct vim now
defaults to enabling Visual Mode. I've been setting this in my ~/.vimrc
to disable it - but not enabling Visual Mode by default would awesome
for me:
set mouse-=a
-pete
--
Pete Wright
p...@nomadlogic.
perhaps we should preserve the expected behaviour by updating
/usr/local/etc/vim/vimrc?
-p
--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
On 1/18/17 10:24 AM, Alexander Kabaev wrote:
On Wed, 18 Jan 2017 10:06:55 -0800
Pete Wright <p...@nomadlogic.org> wrote:
On 1/18/17 10:01 AM, Julian Elischer wrote:
On 18/01/2017 5:03 PM, Raimund Sacherer wrote:
I have to put mouse=v to get the behavior I am used to.
Best
doesn't
g? I've never tried
building the drm-next branch inside a jail, but maybe your trace will
help debug it.
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
/etc/rc.d/routing restart
Perhaps we could introduce a wrapper to be used with:
# service network restart
I think this is a great idea - especially as it would make it easier for
dev's and other novice admin's to use freebsd as a development platform.
cheers,
-pete
--
Pete W
any issues on my Skylake system).
There is also a section on installing a new pkg repository that has
updated Xorg and other binaries that are required for this new code to work.
Hope this helps!
-pete
--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
_
On 10/19/16 8:10 AM, geoffroy desvernay wrote:
On 11/17/2015 21:43, Pete Wright wrote:
On 11/12/15 09:44, Pete Wright wrote:
Hi All,
Just wanted a sanity check before filing a PR. I am running r290688 and
am seeing a LOR being triggered in the mpr(4) device:
$ uname -ar
FreeBSD srd0013
On 11/03/2016 01:42, Julian Elischer wrote:
On 3/11/2016 10:45 AM, Pete Wright wrote:
On 11/02/2016 19:17, Julian Elischer wrote:
On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote:
On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote:
hi,
For long we are planning
On 11/02/2016 19:17, Julian Elischer wrote:
On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote:
On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote:
hi,
For long we are planning to remove GNU rcs from base, after a failed
attempt
before FreeBSD 10.0. Let see where we are to
getting a core.
I have found the following has enabled me to catch kernel panic's pretty
reliably on the drm-next branch when i have the i915kms module loaded:
dev.drm.skip_ddb=1
-pete
--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebs
On 1/6/17 10:44 AM, Jonathan Anderson wrote:
On 6 Jan 2017, at 12:48, Pete Wright wrote:
On 1/6/17 9:14 AM, Matthew Macy wrote:
I just did the merge and it's using a relatively untested new KPI so
regressions aren't too surprising I'm afraid. #96 is more or less
content free in terms
ss = serial bus
subclass = SMBus
iwm0@pci0:1:0:0:class=0x028000 card=0x44108086 chip=0x31658086
rev=0x79 hdr=0x00
vendor = 'Intel Corporation'
device = 'Wireless 3165'
class = network
Any pointers would be really helpful.
Thanks!
-pete
--
Pete Wright
On 03/30/2017 14:26, Dimitry Andric wrote:
On 30 Mar 2017, at 20:18, Pete Wright <p...@nomadlogic.org> wrote:
Hello,
I have a new Kabylake based Intel laptop running CURRENT (well
drm-next). Everything has "just worked" so far except audio. Here is
the output of /dev/snds
On 3/9/17 4:42 AM, Dexuan Cui wrote:
From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
curr...@freebsd.org] On Behalf Of Pete Wright
Sent: Thursday, March 9, 2017 14:04
To: freebsd-current@freebsd.org
Subject: Re: input/output error @boot
On 3/8/17 10:00 PM, Dexuan Cui wrote
On 3/9/17 8:10 AM, Pete Wright wrote:
On 3/9/17 4:42 AM, Dexuan Cui wrote:
From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
curr...@freebsd.org] On Behalf Of Pete Wright
Sent: Thursday, March 9, 2017 14:04
To: freebsd-current@freebsd.org
Subject: Re: input/output error @boot
me, though it's potentially unsafe.
+1
i'd like to see the old behaviour for physical machines to be restored
as well since this has rendered my drm-next test rig broken :(
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freeb
On 03/30/2017 14:30, Pete Wright wrote:
On 03/30/2017 14:26, Dimitry Andric wrote:
On 30 Mar 2017, at 20:18, Pete Wright <p...@nomadlogic.org> wrote:
Hello,
I have a new Kabylake based Intel laptop running CURRENT (well
drm-next). Everything has "just worked" so far ex
this on the drm-next repository after the latest merge
from upstream which happened on April 30th. I'll try to put some cycles
into trying to find a range of potential commits that is causing this.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
through the drm-next commit logs and was
wondering if this commit could be the root cause of the issues i'm seeing?
https://github.com/FreeBSDDesktop/freebsd-base-graphics/commit/2750ce9b17ee373b6d46e6d15d21d2e6c63f6d4d
my hardware is a Kabylake Dell Inspiron 2in1.
-pete
--
Pete Wright
p
updates
which broke suspend/resume - so i believe this patch works from a
functional POV.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
by this bug. Anywho - was wondering
if any devs here had more info on this issue and could provide better
context?
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
On 06/25/2017 14:53, A. Wilcox wrote:
On 25/06/17 12:56, Pete Wright wrote:
Came across this post today via HN regarding a issue with Hyperthreading
causing unpredictable behavior on these CPU's
https://lists.debian.org/debian-devel/2017/06/msg00308.html
I really wish there was more info
in the off chance that it's either related to ino64,
or some other recent change has caused this problem.
Cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
On 05/28/2017 08:54, Pete Wright wrote:
Hi all,
I can't imagine that this is related to INO64, but since upgrading my
world and kernel on drm-next (which merged upstream CURRENT as of May
27 which should include the ino64 work) I am having segfaults running
firefox. Previous
m going to re-run this w/o ccache - to verify that this is a ccache
related issue. I guess my first question - is anyone else using ccache
successfully?
thanks in advance!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@fr
On 10/02/2017 13:07, Pete Wright wrote:
hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running, but i've since cut over to CURRENT and am still
having issues. running "
On 10/02/2017 16:33, Matt Joras wrote:
On 10/02/2017 15:23, Pete Wright wrote:
On 10/02/2017 13:07, Pete Wright wrote:
hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running
On 10/02/2017 16:35, Pete Wright wrote:
On 10/02/2017 16:33, Matt Joras wrote:
On 10/02/2017 15:23, Pete Wright wrote:
On 10/02/2017 13:07, Pete Wright wrote:
hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities
gzilla/show_bug.cgi?id=220229
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre
On 10/09/2017 16:02, Pete Wright wrote:
hey there - i was really excited to see GNN's recent commits to add
support to the 8265 Intel WiFi devices:
https://svnweb.freebsd.org/base?view=revision=324434
unfortunately this does not seem to work on my system. after building
and rebooting
some cycles
rebuilding LLVM :)
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-cu
reference to see where i may be
able to chip in)?
cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail t
On 12/01/2017 11:43, Pete Wright wrote:
Hi All,
I am running into this error when attempting to buildworld from a
checkout I made recently (git hash
76ca06b62f3bfb21f1f2e1295eb89e3c235bdda7)
--- all_subdir_stand ---
/usr/home/pete/git/freebsd/stand/i386/libi386/libi386.a(bootinfo64.o
On 12/03/2017 00:27, Eitan Adler wrote:
On 2 December 2017 at 17:45, Pete Wright <p...@nomadlogic.org> wrote:
i also am not seeing any reports of functions not being declared, although
i'm currently re-testing the build now with a single worker passed to make
so that i can get clearer
sctl knob i've set in the past to help in this area,
i'll dig through my notes and see if i can find it...
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listin
On 05/14/2018 01:18, Niclas Zeising wrote:
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
buffer
either.
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
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 time, and graphics are
sluggish (very
is broken as well then i guess this could be a hardware issue.
the good news is that 11.2-BETA and drm-next works great (aside from
suspend/resume) :)
-p
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing
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.acpi.resume_beep=1" and whe
On 05/12/2018 19: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 has stopped working. i've tested
state of the art in terms of hardware support.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fre
On 05/24/2018 05:55, Mateusz Piotrowski wrote:
On Wed, 23 May 2018 09:46:13 -0700
Pete Wright <p...@nomadlogic.org> wrote:
On 05/23/2018 00:41, David Pan wrote:
how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on
FreeBSD 12?I installed FreeBSD 12 on my thinkpad t470p ,a
this entry to /etc/rc.conf:
kld_list="if_iwm"
then configuring the interface is the same as any other wifi as per the
handbook, the device will be available as "iwm0".
hope this helps,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
_
synaptics device, have you set the following in
/boot/loader.conf?
hw.psm.synaptics_support="1"
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
ter reboot by running "kldstat".
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "
On 06/07/2018 14:01, Anton Shterenlikht wrote:
On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote:
On 06/07/2018 13:21, Anton Shterenlikht wrote:
Please help get touchpad mouse on
Dell Precision 3520.
The usb mouse works fine.
pciconf isn't really applicable here i think. does
ess people dedicating their spare time to
help create useful things for others shouldn't go unpunished.
well i guess i broke my promise to ignore this bikeshed :(
-p
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org ma
On 06/22/2018 10:38, Navdeep Parhar wrote:
On 06/22/18 10:25, Pete Wright wrote:
On 06/21/2018 20:47, Danilo Egêa Gondolfo wrote:
Hi,
check if you have 'options IXL_IW' in your kernel conf. It's removed
from GENERIC. I had the same problem here with my customized conf.
ah
of sync. i've now re-created my EVDEV config to
just include GENERIC.
thanks for the heads up!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
On 07/03/2018 15:12, Pete Wright wrote:
On 07/03/2018 14:17, Pete Wright wrote:
On 07/03/2018 12:02, John Baldwin wrote:
On 7/3/18 11:28 AM, Niclas Zeising wrote:
On 07/03/18 17:02, O. Hartmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Tue, 3 Jul 2018 10:19:57 -0400
.
sure thing John - here's a gist of "thread apply all bt"
https://gist.github.com/gem-pete/d8d7ab220dc8781f0827f965f09d43ed
cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing
YPE) \
ATOMIC_LOAD(TYPE); \
i've just built a kernel with this patch applied, rebooted into it and
was able to build the drm-next-kmod port. i am also running X without
issues so far with this configuration.
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
On 07/03/2018 14:17, Pete Wright wrote:
On 07/03/2018 12:02, John Baldwin wrote:
On 7/3/18 11:28 AM, Niclas Zeising wrote:
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
On 07/03/2018 15:56, John Baldwin wrote:
On 7/3/18 3:34 PM, Pete Wright wrote:
On 07/03/2018 15:29, John Baldwin wrote:
That seems like kgdb is looking at the wrong CPU. Can you use
'info threads' and look for threads not stopped in 'sched_switch'
and get their backtraces? You could also
Is this a known issue? This is my primary workstation - so I'm going to
revert back to an older kernel, but if more info is needed I can put
some cycles into debugging today.
Cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current
On 01/15/2018 09:26, Pete Wright wrote:
Hello,
I updated an amd64 system last night to r327979 and it panics into gdb
after rc attempts to mount local filesystems.
The panic line is:
Fatal trap 12: page fault while in kernel mode
gdb states that it stopped at:
Stopped at prison_allow
help debug the issue but am not sure where to start poking.
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
On 02/15/2018 13:37, Jung-uk Kim wrote:
On 02/13/2018 17:34, Claude Buisson wrote:
On 02/13/2018 22:49, Pete Wright wrote:
Hello,
I have started seeing a lot of these messages spam my system log:
ACPI Error: No pointer back to namespace node in package
0xf8000f79a080 (20180209/dsargs
l.o:(ixl_if_detach)
*** [kernel.full] Error code 1
building a standard GENERIC kernel works without issue. my "EVDEV" kern
conf has the following two lines added:
options EVDEV_SUPPORT # D10265 from phabricator
device evdev
Not sure if a
requently when updates of software required updates to configs, being a
junior admin at the time and having a decent gui to manage diffs
certainly made me feel more confident about the changes i was making.
but honestly this is such an edge case i haven't put any effort into
hacking
this would worth my
time testing out. thanks for the links for reference!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
. here's my iovct.conf:
PF {
num_vfs: 1;
device : "ix0";
}
DEFAULT {
passthrough : true;
}
my goal is to setup several bhyve instances on this server, and allocate
one VF per instance. for now i'm attempting to create a single VF for
testing purposes.
Cheers!
-pete
--
Pet
that i can
work, but am keen to test out any patches or do any other debugging that
is needed.
thx!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
On 8/14/18 6:13 PM, Kyle Evans wrote:
On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote:
i also attempted to boot using UEFI but the system hangs very early in the
boot process. i have reverted to legacy mode for now so that i can work,
but am keen to test out any patches or do any other
ves my immediate problem!
:) interestingly enough i still see the ACPI errors I reported earlier,
but perhaps that is a red herring.
i'll go back to the tip of master and apply kib's patch and see how it goes.
-p
--
Pete Wright
p...@nomadlogic.org
@nomadlogi
On 8/14/18 9:06 PM, Pete Wright wrote:
On 8/14/18 9:01 PM, Kyle Evans wrote:
I'm curious if you've been bitten somehow by recently enabling EFIRT
in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and
see where that gets you?
i did attempt to set that in loader.conf
On 8/14/18 8:45 PM, Kyle Evans wrote:
On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote:
On 8/14/18 6:13 PM, Kyle Evans wrote:
On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote:
i also attempted to boot using UEFI but the system hangs very early in
the
boot process. i have reverted
hanging - for
example like so:
$ sudo iovctl -C -f /etc/iovctl.conf
iovctl: Failed to configure SR-IOV: No space left on device
so if its working on CURRENT i'll go through the upgrade process, but if
no one is testing this I'll forgo SR-IOV for now.
thanks!
-pete
--
Pete Wright
p
CFT (maybe before?) - i don't know anyone who's getting
paid for this specific work. at least when it comes to GPU support.
but, if you have the means, I'd love to work on this full time and am
open to any serious offers :)
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
On 8/25/18 11:51 AM, Warner Losh wrote:
On Sat, Aug 25, 2018, 12:17 PM Pete Wright wrote:
On 8/25/18 11:10 AM, Yuri Pankov wrote:
Pete Wright wrote:
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
that my usb mouse is not being detected. i made sure to do a proper
On 8/25/18 11:10 AM, Yuri Pankov wrote:
Pete Wright wrote:
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
that my usb mouse is not being detected. i made sure to do a proper
mergemaster after building my kernel and world, and verified that
updates to devd configs were
the best way to debug this is as i'm a bit
uncertain about devd and devmatch's recent changes, so let me know if
more info is needed or if i'm just missing something obvious.
thx!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current
for bectl it doesn't mention this being an issue.
so i guess i have two questions:
1) is it a bad thing(tm) to have /boot on its own pool?
2) assuming that having /boot on its own pool, why does bectl not work
with this configuration?
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
et_video=1
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
On 07/21/2018 09:47, Ian Lepore wrote:
On Sat, 2018-07-21 at 09:41 -0700, Pete Wright wrote:
hello - i am testing out the new ntpd that was committed yesterday and
am attempting to run as non-root. i've created a ntpd user/group, and
verified permissions look good on pertinent directories
t;YES"
thanks!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
On 07/21/2018 10:14, Ian Lepore wrote:
On Sat, 2018-07-21 at 10:11 -0700, Pete Wright wrote:
On 07/21/2018 09:47, Ian Lepore wrote:
On Sat, 2018-07-21 at 09:41 -0700, Pete Wright wrote:
hello - i am testing out the new ntpd that was committed
yesterday and
am attempting to run as non-root
ning
the rc script by hand. i didn't think to compare the output of x86info
before running the rc script, i can do that later today.
for reference here is my dmesg:
https://gist.github.com/nomadlogic/bfc54315b97d374a7818d29bfc93223e
Cheers,
-pete
--
P
On 9/10/18 5:41 PM, Mark Johnston wrote:
> On Mon, Sep 10, 2018 at 12:48:56PM -0700, Pete Wright wrote:
>>
>> On 9/10/18 11:26 AM, Mark Johnston wrote:
>>> Hi,
>>>
>>> Support for boot-time loading of Intel microcode updates has landed in
>>> the
On 8/27/18 3:22 PM, Allan Jude wrote:
On 2018-08-27 14:50, Pete Wright wrote:
hi there - i have a zfs based system where /boot is on its own pool.
beadm seems happy enough with this setup but bectl errors out like so:
$ sudo bectl list
/ and /boot not on same device, quitting
$
$ beadm list
On 07/05/2018 10:10, John Baldwin wrote:
On 7/3/18 5:10 PM, Pete Wright wrote:
On 07/03/2018 15:56, John Baldwin wrote:
On 7/3/18 3:34 PM, Pete Wright wrote:
On 07/03/2018 15:29, John Baldwin wrote:
That seems like kgdb is looking at the wrong CPU. Can you use
'info threads' and look
On 07/05/2018 12:12, Hans Petter Selasky wrote:
On 07/05/18 20:59, Hans Petter Selasky wrote:
On 07/05/18 19:48, Pete Wright wrote:
On 07/05/2018 10:10, John Baldwin wrote:
On 7/3/18 5:10 PM, Pete Wright wrote:
On 07/03/2018 15:56, John Baldwin wrote:
On 7/3/18 3:34 PM, Pete Wright
sorry - this was sent to incorrect list - please ignore. sorry for the
noise!
-pete
On 07/06/2018 16:22, Pete Wright wrote:
hi there - this is in relation to this ticket:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
"ena driver causing kernel panics on AWS EC2"
readi
rt above though it's not clear as to the state
of the ena drivers themselves. Are they considered unstable on
11.2-RELEASE?
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists
, John Baldwin mailto:j...@freebsd.org>> 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 wrote:
>>> On 07/05/18
automagically what happens when you
manually load the module via "kldload" or by updating rc.conf?
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
On 07/12/2018 21:15, Yuri wrote:
On 07/12/18 13:38, Pete Wright wrote:
sorry if i missed something (don't see details in the bug report) -
is the issue that the run(4) kernel module is not being loaded? is
there an error when the system attempts to load the kernel module in
the dmesg
s:
$ kldstat |grep i915
7 1 0x82f38000 11f615 i915kms.ko
If it is present, can you also verify that you are a member of the
"video" group? And failing that it will be helpful to post your dmesg
and Xorg.log.0 to help triage this.
Cheers,
-pete
--
Pete Wright
p..
ptop model: Lenovo E470
>
(removing stable since this is a potential issue on CURRENT)
we'll need more details to help triage and hopefully fix this issue.
what errors are you seeing? are you having problems loading the driver,
or is Xorg having issues?
-pete
--
Pete Wright
p...@nomadl
1 - 100 of 222 matches
Mail list logo
