On Sun, 22 Oct 2000, David O'Brien wrote:
> On Sat, Oct 21, 2000 at 11:05:37AM -0700, Jordan Hubbard wrote:
> > > I wish to update rc.network6 and introduce rc.firewall6.
> >
> > H. I must confess that I see /etc as getting rather cluttered
> > these days. Is there no way to perhaps collap
On Mon, 23 Oct 2000, Garrett Rooney wrote:
> On Tue, Oct 24, 2000 at 04:49:40AM +0700, Alexey Dokuchaev wrote:
> > Well, would not be this stepping aside from BSD startup sequence, which we
> > all know and love? Having dozens of small files instead of pair of
> > big ones
On Mon, 23 Oct 2000, Brandon D. Valentine wrote:
> On Tue, 24 Oct 2000, Alexey Dokuchaev wrote:
>
> >Still, it would be better if I could choose between "classical" and "new"
> >startup layout, say, somewhere at the installation stage.
>
> Well if
On Tue, 24 Oct 2000, Terry Lambert wrote:
> > Well, would not be this stepping aside from BSD startup sequence, which we
> > all know and love? Having dozens of small files instead of pair of
> > big ones always frustrates me when I have to work with linux.
>
> Install a binary package that nee
> Well, we *already* have over a dozen /etc/rc.* files on -current. And
> we *don't* have the advantage of a consistent interface to control all
> the functions in /etc/rc. If you break things up, then if you need to
> restart the mail server, just go "/etc/rc.d/sendmail restart". dhcpd?
> "/etc/
On Tue, 24 Oct 2000, David O'Brien wrote:
> On Tue, Oct 24, 2000 at 04:23:40PM +0700, Alexey Dokuchaev wrote:
> > Why can't I simply write kill -1 `cat /var/run/sendmail.pid`?
>
> What about deamons that don't understand `kill -HUP'? Sendmail didn't
&
Hello!
On Sat, 28 Oct 2000, David O'Brien wrote:
> I am switching us from using or native crt{begin,end}.c to GCC's
> crtstuff.c in the building of /usr/lib/crt{begin,end}.o.
>
> Testing a new world with this change not show any problems.
> HOWEVER, I have only done cursory testing with already
On Sun, Oct 17, 2010 at 11:32:00PM +, Alexander Best wrote:
> i'm running 256.52 on HEAD (amd64) without any issues. the 260.X drivers all
> freze my computer when i exit X.
>
> it's quite easy to work around the isse that the nvidia drivers fail to
> compile
> on HEAD. simply change the line
On Wed, Sep 03, 2003 at 03:08:30PM +0400, Sergey A. Osokin wrote:
> On Wed, Sep 03, 2003 at 01:01:55PM +0200, Harald Schmalzbauer wrote:
> >
> > with today's -current the nvidia port failed to compile.
> > With a bit luck I found that there seems to be a misstype in the
> > src/nvidia_sysctl.c. I
On Wed, Sep 03, 2003 at 12:14:52PM +0100, Matt wrote:
> Sergey A. Osokin wrote:
>
> >On Wed, Sep 03, 2003 at 01:01:55PM +0200, Harald Schmalzbauer wrote:
> >
> >>with today's -current the nvidia port failed to compile.
> >>With a bit luck I found that there seems to be a misstype in the
> >>src/n
On Thu, Dec 20, 2018 at 03:49:38PM +0500, Eugene M. Zheganin wrote:
> On 19.12.2018 23:32, Allan Jude wrote:
> > The biggest thing to remember is that this is still OpenZFS, and still
> > run by the same developers as it has been. We are just commonizing on
> > the repo that has the most features i
Hi there,
For many years, OpenSSL was quite vocal about which hw-accelerated algos
it can use:
$ uname -UK
1200058 1200058
$ openssl version
OpenSSL 1.0.2n-freebsd 7 Dec 2017
$ openssl engine -c -t
(cryptodev) BSD cryptodev engine
[RSA, DSA, DH] <<< word
On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote:
> On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote:
> > Had something got broken here, or I'm misunderstanding how this machinery
> > now works?
>
> Start reading here:
>
> https://lists.free
On Fri, Dec 21, 2018 at 01:10:07AM +0700, Alexey Dokuchaev wrote:
> On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote:
> > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote:
> > > Had something got broken here, or I'm misunderstanding how this ma
hi there,
i've made my -CURRENT world and installed, but "make delete-old" tells
me it cannot remove some directories:
>>> Removing old directories
rmdir: /usr/share/dtrace: Directory not empty
rmdir: /usr/lib/dtrace: Directory not empty
rmdir: /usr/lib/debug/usr/tests/libexec/rtld-elf: Directory
On Tue, Oct 22, 2019 at 04:34:53PM -0700, John Baldwin wrote:
> On 10/18/19 10:05 AM, Alexey Dokuchaev wrote:
> > hi there,
> >
> > i've made my -CURRENT world and installed, but "make delete-old" tells
> > me it cannot remove some directories:
> >
On Thu, Oct 24, 2019 at 11:07:16AM -0700, John Baldwin wrote:
> On 10/22/19 8:42 PM, Alexey Dokuchaev wrote:
> > On Tue, Oct 22, 2019 at 04:34:53PM -0700, John Baldwin wrote:
> >> ...
> >> These are from the OpenSSL 1.1.1 commit. However, they are tagged as
> >
On Sun, Oct 27, 2019 at 07:40:36PM +0700, Alexey Dokuchaev wrote:
> On Thu, Oct 24, 2019 at 11:07:16AM -0700, John Baldwin wrote:
> > On 10/22/19 8:42 PM, Alexey Dokuchaev wrote:
> > > On Tue, Oct 22, 2019 at 04:34:53PM -0700, John Baldwin wrote:
> > >> ...
> >
Hi there,
I've decided to give -CURRENT a try on my i386 laptop with a 915GM video
(supported by i915kms.ko) @ r295286; minimal kernel with most of the stuff
loaded from /boot/loader.conf.
While debugging suspend/resume issues, I've found out that loading vesa.ko
now apparently only works from /b
On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote:
> On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote:
> > Looking through dmesg, it seems that other USB devices (build-in) are
> > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after
> > resume, just not the
On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote:
> > > VESA needs to be removed for i915kms, but I've no idea if it needs
On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote:
> > I've started to observe similar lines in the logs after updating to
> > fresh -CURRENT, upon resume (on a different laptop though, not T41
On Thu, Feb 18, 2016 at 09:48:40AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote:
> > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote:
> > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> >
On Thu, Feb 18, 2016 at 10:02:17AM -0800, Adrian Chadd wrote:
> [snip]
>
> Someone should sit me down with pizza and "help" me just modularise
> the vesa/fb code so we can use it in vt.
>
> It isn't /that/ hard, I've just been preoccupied.
And before it happens, someone(tm) could write a few par
On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> > # pciconf -lc pci0:0:0
> > hostb0@pci0:0:0:0: class=0x06 card=0x83191033 chip=0x25908086
> > rev=0x04 hdr=0x00
> > ca
On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote:
> On 26 Mar 2017, at 23:36, Mark Millard wrote:
> > ...
> > Also interesting was:
> >
> > Installed packages to be REMOVED:
> > llvm40-4.0.0.r4
> >
> > Number of packages to be removed: 1
> >
> > The operation will free 49 GiB.
On Thu, Mar 30, 2017 at 07:26:43PM +0200, Matthew Rezny wrote:
> LLVM 3.8 introduced the option to build a shared LLVM library, which is
> what Mesa needs for use at runtime (for e.g. compiling shaders), separate
> from linking to it. Previous versions only had one option, if the library
> was buil
On Wed, Apr 05, 2017 at 07:12:06PM +0200, Mathieu Arnold wrote:
> Le 05/04/2017 ?? 18:15, Alexey Dokuchaev a ??crit :
> > ...
> > That 1G looks like a big jump from 259M of llvm39-3.9.1_1.txz to me.
>
> So, you are comparing the size of the llvm39 package with the size
On Wed, Apr 05, 2017 at 08:46:22PM +0200, Mathieu Arnold wrote:
> Le 05/04/2017 ?? 19:20, Alexey Dokuchaev a ??crit :
> > On Wed, Apr 05, 2017 at 07:12:06PM +0200, Mathieu Arnold wrote:
> >> Le 05/04/2017 ?? 18:15, Alexey Dokuchaev a ??crit :
> >>> ...
> >>&g
Sorry Matthew, forgot to reply to this one.
On Wed, Apr 05, 2017 at 07:01:35PM +0200, Matthew Rezny wrote:
> On Wednesday 05 April 2017 16:15:41 Alexey Dokuchaev wrote:
> > ...
> > Hmm, I don't quite get it: shouldn't static linking actually increase
> > the binar
On Thu, Oct 06, 2011 at 01:35:14AM +, Nali Toja wrote:
> Ali Mashtizadeh writes:
> > 2011/8/31 Alexey Dokuchaev :
> >> On Mon, Aug 29, 2011 at 02:59:48PM +0200, Olivier Smedts wrote:
> >>> 2011/8/29 ken :
> >>> > Could I test your patch for nvidia-
Hi there,
I've recently put back online one of my home servers, updated to the latest
-CURRENT code. All went fine, but one thing bothers me. This box bears
Asus P5Q Pro mobo, with the following onboard NIC:
ale0@pci0:2:0:0:class=0x02 card=0x82261043 chip=0x10261969
rev=0xb0 hdr=0x0
On Wed, Feb 20, 2013 at 01:37:39PM +0900, YongHyeon PYUN wrote:
> On Tue, Feb 19, 2013 at 08:23:02AM +0000, Alexey Dokuchaev wrote:
> > ale0@pci0:2:0:0:class=0x02 card=0x82261043 chip=0x10261969
> > rev=0xb0 hdr=0x00
> > vendor = 'Atheros Communica
On Thu, Feb 21, 2013 at 05:33:35PM +0900, YongHyeon PYUN wrote:
> On Wed, Feb 20, 2013 at 06:08:53AM +0000, Alexey Dokuchaev wrote:
> > $ dmesg | egrep ale\|atphy
> > ale0: port 0xcc00-0xcc7f mem
> > 0xfe9c-0xfe9f irq 17 at device 0.0 on pci2
> > ale0: 960 Tx
On Fri, Feb 22, 2013 at 10:13:08AM +0900, YongHyeon PYUN wrote:
> On Thu, Feb 21, 2013 at 12:43:44PM +0000, Alexey Dokuchaev wrote:
> > ale_flags = 0x0040
>
> Thanks for the info. Indeed, your controller is AR8121 Gigabit
> etherent(L1E). I guess the PHY initializati
On Wed, Jan 19, 2011 at 08:14:19AM -0500, John Baldwin wrote:
> On Wednesday, January 19, 2011 5:08:10 am Bruce Cran wrote:
> > On Tue, 18 Jan 2011 11:25:38 -0500
> > John Baldwin wrote:
> >
> > > Oh, the uart[01] devices already exist. I suspect if you removed the
> > > hints from /boot/device.
On Thu, Feb 23, 2012 at 08:28:47AM -0500, John Baldwin wrote:
> Hmm, can you see what 'dev->nameunit' is? Maybe just do 'p *dev' actually
> and reply with that.
(kgdb) p *dev
$1 = {ops = 0xc50de000, link = {tqe_next = 0xc5271380, tqe_prev =
0xc5271184},
devlink = {tqe_next = 0xc5271380, tqe_pre
On Fri, Feb 24, 2012 at 12:22:36PM -0500, John Baldwin wrote:
> Try this for fixing the panic. New-bus was not clearing the description
> if a device's attach routine failed.
Thanks, this patch indeed fixes the panic.
./danfe
___
freebsd-current@freebs
On Fri, Sep 06, 2013 at 10:46:49AM -0700, John-Mark Gurney wrote:
> Alexey Dokuchaev wrote this message on Sat, Sep 07, 2013 at 00:29 +0700:
> > On Fri, Sep 06, 2013 at 10:08:20AM -0700, hiren panchasara wrote:
> > > On Fri, Sep 6, 2013 at 8:12 AM, Alexey Dokuchaev wrote
Hi there,
Just now my pretty fresh 11-CURRENT rebooted unexpectedly in the middle of
'svn up'. Some information from core.txt.0 (full version available upon
request) given in the end of this email. (Machine: 11.0-CURRENT/i386 built
on Oct 18, GENERIC kernel, default install, single / partition w
Hi again,
I was running out of space on my UFS partition and decided to use big NTFS
one I also have on the drive. I've mounted it with ntfs-3g and our native
fuse.ko. I needed the scratch space to built Open/LibreOffice on it *LOL*.
Well, it failed with a panic (see the excerpt from text core a
Hi,
Judging from /usr/share/mk/bsd.cpu.mk, it knows about both "core" and
"core2" and should be able to give me the list of features these CPUs
support. However, I'm puzzled:
$ make -V MACHINE_CPU CPUTYPE=core2
ssse3 sse3 sse2 sse i686 mmx i586 i486
$ fmake -V MACHINE_CPU CPUTYPE=cor
On Thu, Oct 31, 2013 at 11:35:34AM +0100, Tijl Coosemans wrote:
> bsd.cpu.mk redefines CPUTYPE sometimes and that doesn't work if you
> pass it as a command line argument. You can only set this variable
> in make.conf.
Indeed, thanks; setting in make.conf works, however the fact that redefined
va
On Thu, Oct 31, 2013 at 09:59:42AM -0700, Kevin Oberman wrote:
> On Tue, Oct 29, 2013 at 3:24 AM, Alexey Dokuchaev wrote:
> > I was running out of space on my UFS partition and decided to use big NTFS
> > one I also have on the drive. I've mounted it with ntfs-3g and our na
On Sun, Oct 06, 2013 at 10:24:09AM -0700, Alfred Perlstein wrote:
> I got one of these (if_urtwn) and it works enough to download about a meg
> or so before the watchdog kicks in and I have to ifconfig down/up it to
> get it to respond again.
>
> I even have a patch pending to add the usb identifi
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
> Your usb wlan dongles use RTL8188EU chip which is currently not
> supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is id-patch urtwn(4). ;-)
Does anyone know if sup
On Fri, Dec 20, 2013 at 01:35:37PM +0800, Kevin Lo wrote:
> I'd like to port it after finishing RT5373 driver support. :-)
Nice, looking forward to it. :)
> Here's a site you could use for info about your wireless device:
> http://wikidevi.com/wiki/TP-LINK_TL-WN723N_v3
Thank you Kevin.
./danfe
On Tue, Oct 15, 2013 at 11:13:56PM -0700, Rui Paulo wrote:
> On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
> > I too am seeing
> > urtwn0: timeout waiting for checksum report
>
> Sorry, this is a know problem that I haven't been able to figure out...
> It probably exists in the OpenBSD dri
On Mon, Feb 10, 2014 at 01:25:06PM +0100, Hans Petter Selasky wrote:
> On 02/10/14 13:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report&
On Sun, Nov 03, 2013 at 11:16:53PM -0800, Kevin Oberman wrote:
> Are you booting directly to X or using startx from the console? In either
> case, I think that i915kms should auto-load at the start of X, so you
> should not need to pre-load it.
Just switched to newcons on fresh -CURRENT, seem to w
resolutions). Is there way
to select particular one (other than patching source code)?
> On 10 February 2014 16:07, Alexey Dokuchaev wrote:
> > Also, even at native resolution, switching consoles takes LCD considerable
> > time to redraw screen contents. Looks like it's not acc
Hi there,
Following my previous more of less successful experience with newcons on
-CURRENT/amd64 and some ATI/AMD card, I've decided to give it a try here
on i386 with somewhat older HD 4350, also from ATI. Unfortunately, this
time newcons'ified GENERIC kernel + startx => reboot (core.txt attach
On Mon, Mar 10, 2014 at 03:41:16PM +0800, Kevin Lo wrote:
> On 2014/02/10 20:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report"
On Fri, Mar 14, 2014 at 02:54:43PM +0100, Jilles Tjoelker wrote:
> On Thu, Mar 13, 2014 at 05:14:56AM -0700, Anton Shterenlikht wrote:
> > Mar 13 12:08:48 casperd[1313]: [ERROR] (casperd) Unable to receive message
> > from client: Cannot allocate memory.
> > Mar 13 12:08:50 last message repeated 2
On Tue, Apr 01, 2014 at 06:40:18PM -0400, Garrett Wollman wrote:
> Hmmm. I'm a bit biased here, but I've been using FreeBSD on the
> desktop since, well, before it was called FreeBSD. It's still my
> primary platform for nearly everything (except photo management, which
> drove me to a Mac laptop
On Tue, Apr 01, 2014 at 03:10:22PM -0700, Kevin Oberman wrote:
> FreeBSD desktop since 3.3 (makes me a newbie!) I really dislike pulseaudio
> and have managed to live without it. Firefox works fine without it.
> Unfortunately they dropped OSS support a while go, so I now must use alsa,
> but it wor
On Thu, Apr 03, 2014 at 11:21:34AM +0200, Matthias Gamsjager wrote:
> > Since when is GIMP an alternative to Lightroom? I was talking about
> > raw processors, not raster image manipulators.
>
> The opensource alternatives to Lightroom come not close to the original.
They maybe not yet a drop-in
On Thu, Apr 03, 2014 at 09:49:31AM +0200, Matthias Gamsjager wrote:
> > There are a few alternatives to Lightroom available in Ports Collection,
> > you might want to give them a try one day.
> >
> offtopic:
> But it does not even come close to Lightroom. Gimp is also not even
> close to Photoshop.
On Tue, Apr 01, 2014 at 08:38:28AM +0100, David Chisnall wrote:
> On 1 Apr 2014, at 08:11, Jordan Hubbard wrote:
> > 1. Power. As you point out, being truly power efficient is a complete
> > top-to-bottom engineering effort and it takes a lot more than just trying
> > to idle the processor whenev
On Tue, Mar 05, 2013 at 09:14:11AM +, Alexey Dokuchaev wrote:
> On Tue, Mar 05, 2013 at 05:57:03PM +0900, YongHyeon PYUN wrote:
> > Hmm, Does the switch support EEE feature? If yes, would you try
> > disabling it?
>
> I do not think it [1] does; plus I cannot do much abou
On Fri, May 09, 2014 at 02:38:16PM +0900, Yonghyeon PYUN wrote:
> On Thu, May 08, 2014 at 05:23:32PM +0000, Alexey Dokuchaev wrote:
> > I just had a chance to plug the Ethernet cable directly into my laptop's
> > bge(4) port, and it immediately negotiated at 1000baseT; but
On Sat, Jun 14, 2014 at 09:39:18PM +0200, Kurt Jaeger wrote:
> http://en.wikipedia.org/wiki/System_Management_Bus
>
> You can read some system status values (CPU temp etc).
>
> In the ports, check sysutils/xmbmon or sysutils/healthd
> whether it detects anything.
It can also be used to talk to o
On Mon, Feb 25, 2013 at 05:23:44PM +0900, YongHyeon PYUN wrote:
> Then have no idea at this moment. Can you try other OS and check
> whether it can establish a gigabit link?
I did not have a chance to try other OS, because machine paniced during
tinderbuilding of a large port. Unfortunately I don
On Sun, Mar 03, 2013 at 09:53:30AM +, Alexey Dokuchaev wrote:
> However, after reboot ale0 come up at 1000baseT , with patched
> driver (longer delays in ale_phy_reset()). I've reverted this change and
> rebooted again, but it again come up as GigE.
Alas, after "make kerne
On Mon, Mar 04, 2013 at 09:50:44AM +0900, YongHyeon PYUN wrote:
> On Sun, Mar 03, 2013 at 12:00:10PM +0000, Alexey Dokuchaev wrote:
> > Alas, after "make kernel", link come up as 100mbps again, playing with
> > delays and rebooting (several times) did not make it GigE.
On Mon, Mar 04, 2013 at 11:10:59AM +0900, YongHyeon PYUN wrote:
> On Mon, Mar 04, 2013 at 01:53:44AM +0000, Alexey Dokuchaev wrote:
> > Yes, it did help. With 2000us delays (I didn't revert them [...]
>
> Great! But it seems 2ms delays is too much. Could you revert the cha
On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
> Ok, here is final diff which combines two things you've tested.
> So revert any changes before applying it.
> Let me know how it goes on your box.
Hmm, apparently something went wrong, as I'm back to 100baseTX after make
kernel and
On Mon, Mar 04, 2013 at 03:29:44PM +0900, YongHyeon PYUN wrote:
> On Mon, Mar 04, 2013 at 05:59:48AM +0000, Alexey Dokuchaev wrote:
> > On Mon, Mar 04, 2013 at 02:23:28PM +0900, YongHyeon PYUN wrote:
> > > Ok, here is final diff which combines two things you've tested.
>
On Mon, Mar 04, 2013 at 04:06:32PM +0900, YongHyeon PYUN wrote:
> On Mon, Mar 04, 2013 at 06:59:40AM +0000, Alexey Dokuchaev wrote:
> > Better this time, I'm having 1000baseT again! :-)
>
> Thanks a lot for testing and patience!
> Could you reboot multiple times and check w
On Tue, Mar 05, 2013 at 02:49:20PM +0900, YongHyeon PYUN wrote:
> On Mon, Mar 04, 2013 at 08:18:58AM +0000, Alexey Dokuchaev wrote:
> > Yes, multiple reboots was a good idea, it's not very stable: [...]
> >
> > I've tried various combinations of just reboot, shutd
On Tue, Mar 05, 2013 at 04:43:15PM +0900, YongHyeon PYUN wrote:
> > > Could you disable WOL before rebooting your box?
> >
> > # ifconfig ale0 -wol
> > # reboot
> >
> > It came up as 100baseTX. :(
>
> You don't use any manual link configuration, right?
Right, everything is auto (that is, the de
On Tue, Mar 05, 2013 at 05:57:03PM +0900, YongHyeon PYUN wrote:
> Hmm, Does the switch support EEE feature? If yes, would you try
> disabling it?
I do not think it [1] does; plus I cannot do much about this switch, as I'm
pretty far away from it right now.
./danfe
[1]
http://netgear.com/home/pr
Hi there,
I've been trying to install fresh -CURRENT (in VirtualBox/i386), and since
recent snapshots did not work for me, had to do this by first installing
from 9.1-release .iso. After "svn co .../head /usr/src" and standard make
world/kernel/mergemaster procedure (w/out any custom settings in
On Tue, Jun 18, 2013 at 10:21:33PM +0700, Alexey Dokuchaev wrote:
> I've been trying to install fresh -CURRENT (in VirtualBox/i386), and since
> recent snapshots did not work for me, had to do this by first installing
> from 9.1-release .iso. After "svn co .../head /usr/src
On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote:
> I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
>
> https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1
> https://github.com/lichray/nvi2
>
> The goal was to update the multibyte handling
On Sun, Aug 11, 2013 at 02:15:15AM -0700, Peter Wemm wrote:
> On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev wrote:
> > Yes, please do something about our base(1) being unable to talk in anything
> > non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, a
On Fri, Sep 06, 2013 at 10:08:20AM -0700, hiren panchasara wrote:
> On Fri, Sep 6, 2013 at 8:12 AM, Alexey Dokuchaev wrote:
> > Hi there,
> >
> > I've been trying to cross-build an amd64 kernel on i386 host on recent
> > -CURRENT for a while, and it fails like this
Hi there,
I've been trying to cross-build an amd64 kernel on i386 host on recent
-CURRENT for a while, and it fails like this:
$ cd /usr/src && make buildkernel TARGET=amd64 TARGET_ARCH=amd64
[...]
In file included from /usr/src/sys/amd64/amd64/genassym.c:46:
In file included from /usr/sr
On Mon, Aug 29, 2011 at 02:59:48PM +0200, Olivier Smedts wrote:
> 2011/8/29 ken :
> > Could I test your patch for nvidia-driver, too?
> > I cannot find your patch in this mail.
>
> I took the patch in :
> http://lists.freebsd.org/pipermail/freebsd-current/2011-August/026515.html
>
> And it work
Hi there,
I'm in the process of moving my data from a dying HDD, and just noticed
something weird. It's an MBR partitioned drive, and there is a FreeBSD
slice and Fedora LVM in EBR, accessible as
/dev/linux_lvm/fedora-{swap,home,root}.
The problem is that once I mount my old FreeBSD partition,
On Sun, Dec 25, 2022 at 09:32:55AM -0700, Warner Losh wrote:
> On Sun, Dec 25, 2022, 1:02 AM Alexey Dokuchaev wrote:
> > ...
> > The problem is that once I mount my old FreeBSD partition, e.g.
> > /dev/ada0s2a, those LVM nodes are gone, logging this:
> >
> >
On Mon, May 01, 2023 at 06:14:49PM +, Glen Barber wrote:
> ...
> There is no feasible way we are going to make the branch point of
> stable/14 in time, with that scheduled for May 12, 2023 with the above
> points. That said, this is not an all-inclusive list, but the more
> major items on our
On Thu, Dec 07, 2017 at 11:33:51AM +0200, Andriy Gapon wrote:
> ...
>
> I've done some work with a debugger and it seems that there is code that does
> something like this:
>
> char *last = NULL;
>
> while (1) {
> ...
>
> The binary patch is here: https://people.freebsd.org/~avg/nvidia-sm
On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote:
> This is caused by r334533 and/or r334534 (memset-related changes).
> sysutils/lsof is also affected.
>
> You should revert r334533 and r334534 temporarily until nvidia-driver
> support this change.
nVidia driver port was fixed as of
On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote:
> ...
> The change was committed as r334752. Are you seeing unexpected OOM
> kills on or after that revision?
I've just discovered this thread. I've updated my -CURRENT desktop ca.
June 4th and my X.org session crashes within several
On Wed, Jun 27, 2018 at 07:55:26AM -0400, Mark Johnston wrote:
> On Wed, Jun 27, 2018 at 10:46:38AM +0000, Alexey Dokuchaev wrote:
> > On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote:
> > > ...
> > > The change was committed as r334752. Are you seeing un
On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
>
> Перенаправленное сообщение
> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
> Дата: Tue, 21 Aug 2018 16:41:42 +0700
> От: Alex V. Petrov
> Кому: FreeBSD Ports
Should be fixed as of r477761.
./danf
On Sun, Apr 05, 2020 at 07:41:38PM -0400, Ed Maste wrote:
> On Sun, 5 Apr 2020 at 08:32, Jeffrey Bouquet wrote:
> >
> > A recent build[k,w] [ ** stable 12.1] and many .debug files I'd
> > like to skip if poss. A knob?
>
> Yes, from src.conf(5):
> WITHOUT_DEBUG_FILES
> Set to avo
On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote:
> Niclas Zeising asks:
> > When did it stop working?
>
> September ... I _think_.
Yeah, that sounds about right.
There are known issues with Radeon cards, they were quite well supported
a year ago, then something got broken. I've prom
On Mon, Dec 13, 2021 at 07:45:07AM -0800, John Baldwin wrote:
> ...
> However, it was a bit harder to see this originally as the 915kms driver
> tries to do a malloc(M_WAITOK) from cn_grab() when entering DDB which
> recursively panics (even a malloc(M_NOWAIT) from cn_grab() is probably a
> bad ide
On Mon, Dec 13, 2021 at 06:32:22PM +0100, Emmanuel Vadot wrote:
> On Mon, 13 Dec 2021 17:01:43 +0000 Alexey Dokuchaev wrote:
> > On Mon, Dec 13, 2021 at 07:45:07AM -0800, John Baldwin wrote:
> > > ...
> > > However, it was a bit harder to see this originally as the 915k
On Tue, Dec 14, 2021 at 09:14:27AM +0100, Emmanuel Vadot wrote:
> On Tue, 14 Dec 2021 07:11:28 +0000 Alexey Dokuchaev wrote:
> > ...
> > Oh, you know, it's about steadily deteriorating quality of our gfx
> > stack once we had started pulling things from Linux.
>
>
On Tue, Dec 14, 2021 at 11:27:07AM +0100, Emmanuel Vadot wrote:
> On Tue, 14 Dec 2021 10:14:24 +0000 Alexey Dokuchaev wrote:
> > ...
> > I know that I had problemless desktop some 10-5 years ago, okayish
> > desktop ~three years ago, tolerable experience with 4.16.x DRM bi
On Tue, Dec 14, 2021 at 09:27:01AM -0800, John Baldwin wrote:
> On 12/14/21 2:14 AM, Alexey Dokuchaev wrote:
> > How do you mean? Most FreeBSD people, not some random Twitter crowd,
> > want the bell to be on by default, but it's still off.
>
> I don't know that t
On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote:
> Hi Glen,
>
> From: Glen Barber
> Subject: Considering stepping down from all of my FreeBSD responsibilities
> Date: Fri, 1 Apr 2022 00:15:02 +
>
> > Dear community,
> >
> > Given the mental toll the past two years or so have
On Tue, Jan 28, 2025 at 08:46:04AM -0800, Gleb Smirnoff wrote:
> On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
> A> something has changed in the output of "netstat -rn" between
> A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as
> A> "default" any
96 matches
Mail list logo
