ventoy has only been working with freebsd since 12 or so, it was not
working before since I started using ventoy. Also ventoy won't boot the
new devuan release, for example. ventoy has to jump through hoops to get
some things to boot, so give it some time I guess.
On 10/23/23 11:06, Rodney W.
OP here, I've been running with kern.sched.steal_thresh=1 with no
stutter since it was originally suggested. I tried these instead and I
get stutter, maybe a little less but its definitely back.
On 4/3/21 1:23 AM, Rozhuk Ivan wrote:
I have no micro stutter with default kern.sched.steal_thresh
After about 8 months of struggling to narrow this down I did another
search and saw this:
https://www.reddit.com/r/freebsd/comments/lc8fwo/freebsd_13_vega_64_micro_stutter_in_x/
I haven't seen this come up here so I thought I would bring it up.
My story started sometime before around August la
heh I got worried because my ryzen vega needs 4.17 and up
On 1/29/21 5:05 AM, Emmanuel Vadot wrote:
On Fri, 29 Jan 2021 04:59:27 -0500
monochrome wrote:
correct me if I'm wrong, but shouldn't it say:
Currently corresponding to Linux 5.4.62 DRM.
instead of:
Currently correspondin
correct me if I'm wrong, but shouldn't it say:
Currently corresponding to Linux 5.4.62 DRM.
instead of:
Currently corresponding to Linux 4.16 DRM.
got caught by this while trying to update drm-devel-kmod from ports on
stable/13, and took a chance that it was just an oversight :)
having this issue building virtualbox-ose-kmod, its been like this for a
while but I deinstalled and forgot, for quite a while now, maybe over a
month. now that I've moved from 13-current to stable/13 I thought I
would try to put it back, but it still wont build. I haven't seen anyone
else with
after looking in the git log for the hash I use:
git -C /usr/src reset --hard
you will lose any local changes
On 1/24/21 5:40 PM, Steve Kargl wrote:
On Sun, Jan 24, 2021 at 03:22:18PM -0700, Warner Losh wrote:
On Sun, Jan 24, 2021, 12:14 PM Steve Kargl
wrote:
Any advice on how to jump,
I should add my experience to this since its different and haven't seen
anyone else mention it.
I see the new boot loader, it's not blank, but its large text, and it's
very SLOW.
I can see each char drawn, and then when it gets to the bottom and has
to redraw all the lines to scroll up for new l
local changes. Though it does blow away changes to the conf
file, that's a lesser issue to deal with.
thanks!
On 12/29/20 9:37 AM, Andriy Gapon wrote:
On 2020-12-29 02:56, Pete Wright wrote:
On 12/28/20 4:38 PM, monochrome wrote:
what would be the git command for reverting source to a pre
On 12/29/20 7:15 AM, Kristof Provost wrote:
On 29 Dec 2020, at 4:33, monochrome wrote:
sry forgot details:
source tree @ ead01bfe8
git -C /usr/src checkout gf20c0e331
error: pathspec 'gf20c0e331' did not match any file(s) known to git
what is the 'g' for?
That would
On 12/28/20 7:56 PM, Pete Wright wrote:
On 12/28/20 4:38 PM, monochrome wrote:
what would be the git command for reverting source to a previous
version using these numbers? for example, with svn and old numbers:
svnlite update -r367627 /usr/src
I will generally just checkout the short git
ne mention that a 12 digit shortened hash is the
standard to use, yet uname only spits out 9?
thanks
On 12/28/20 7:56 PM, Pete Wright wrote:
On 12/28/20 4:38 PM, monochrome wrote:
what would be the git command for reverting source to a previous
version using these numbers? for example, with s
what would be the git command for reverting source to a previous version
using these numbers? for example, with svn and old numbers:
svnlite update -r367627 /usr/src
this is needed often when it blows up for someone tracking current
On 12/28/20 11:27 AM, Ed Maste wrote:
On Mon, 28 Dec 2020 at
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 does not.
--
Rainer, I'm all up and running and clean with the latest again, if it
still doesn't work after your next try, send me your step-by-step to
patch and i'll try it here. I'm using ryzen video so I have to disable
stuff to even see the fault messages.
On 9/22/20 1:06 AM, Rainer Hurling wrote:
Am
Sunday, so can't investigate ATM.
And no, I haven't solved it until now. Thanks for your report.
Rainer
Am 18. September 2020 00:38:31 MESZ schrieb monochrome
:
forgot you
Forwarded Message
Subject: Re: r365488 page faults on AMD Ryzen 9 3950X
Date: Thu, 17 Sep 202
I am also having this problem. Have you resolved it? Mine is a Ryzen 5 2400G
On 9/12/20 5:22 AM, Rainer Hurling wrote:
Since r365488 (and above until recent) my box breaks with the following
error when starting:
Fatal trap 12: page fault while in kernel mode
cpuid = 31; apic id = 1f
fault virtu
17 matches
Mail list logo
