On 2024-07-14 09:54, Ivan Quitschal wrote:
> One idea
> Cant say it that would help , but ive checked here and 2 things are working
>
> mount command
> usb is all good
>
> and the filesystem is fine too.
> So does anybody knows where I could literally get the entire 15-CURRENT
> containing the
On 2024-03-19 16:02, Emmanuel Vadot wrote:
> On Tue, 19 Mar 2024 07:55:15 +
> Alastair Hogge wrote:
>
>> On 2024-03-19 15:23, Emmanuel Vadot wrote:
>> > Hi,
>>
>> Hey Emmanuel,
>>
>> > On Tue, 19 Mar 2024 06:54:27 +
>> > Ala
On 2024-03-19 15:23, Emmanuel Vadot wrote:
> Hi,
Hey Emmanuel,
> On Tue, 19 Mar 2024 06:54:27 +0000
> Alastair Hogge wrote:
>
>> Hello,
>>
>> Recently a similar module (PAM) mentioned in the subject was committed
>> to base[1]. The module in base masks the
Hello,
Recently a similar module (PAM) mentioned in the subject was committed
to base[1]. The module in base masks the currently installed Port, the
man page can be accessed with man -M /usr/local/share/man 8 pam_xdg,
however, I can now no longer build the Port. I noticed that the base
module has
On 2023-10-25 10:50, Rick Macklem wrote:
> Garrett Wollman asked me via email how a server
> admin could tell what usage NFS over TLS was
> happening.
>
> I admitted that there was nothing. I have come up
> with a patch that generates the following:
> kern.rpctls.snd_tls_msgbytes: 21508
>
On 2023-08-13 23:22, Matthias Apitz wrote:
> fwd to freebsd-current@ because I don't know if kde@ is read by someone;
>
> matthias
>
> - Forwarded message from bugzilla-nore...@freebsd.org -
>
> Date: Sun, 13 Aug 2023 15:08:04 +
> From: bugzilla-nore...@freebsd.org
> To:
On 2023-08-10 17:38, Matthias Apitz wrote:
> El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman
> escribió:
>
>> This perfectly builds on the latest HEAD without any problem as shared in my
>> build log. I am not sure what is wrong at your end. Neither can I see any
>>
Recreating the glabel manually easily sorted that unnecessary panic out.
Sorry for the noise, tho another GEOM gem for the records.
Hello,
I have a NFS host that exports one GELI UFS from a stripe of some number
of mirrored disks, all GEOM.
While replacing a disk in this RAID—far too tired and late one night—I
was
playing with gcache, adding/removing one gcache device starting at a
time to the
gmirrors, and then the gstripe.
On 2023-05-29 03:24, Pete Wright wrote:
> i've had this pinephone pro for a few months now and finally got
> around to attempting to boot FreeBSD on it. Here's the phone:
> https://wiki.pine64.org/wiki/PinePhone_Pro
>
> I needed to get this serial console adapter which works flawlessly
> with
Hello Guido,
On 2023-05-28 12:44, Guido Falsi wrote:
> On 28/05/23 00:42, Alastair Hogge wrote:
>> Hello,
>>
>> Is there some way to test your X session with minimum components, and slowly
>> adding whatever XFCE does?
>
> Maybe I was not perfectly clear.
Hello,
Is there some way to test your X session with minimum components, and slowly
adding whatever XFCE does?
I would switch from using a X Display Manager, and launch X from the login vty
using startx (if not already ), with a minimum .xinitrc. I would find out what
is needed to get a
On 2023-05-19 12:51, Ivan Quitschal wrote:
> hi Alastair
Hey Ivan,
> could you please tell us how did you do to make mpv working ?
>
> when i try to run it, i get something like this:
>
> $ mpv --vo=drm video.mp4
> (+) Video --vid=1 (*) (h264 424x240 30.000fps)
> (+) Audio --aid=1 (*) (aac
On 2023-05-19 11:30, Tomek CEDRO wrote:
> On Fri, May 19, 2023 at 1:28 PM Alastair Hogge wrote:
>> As long as those packages support DRMKMS and does your GPU, you can to a
>> degree. I noticed video works for mpv and games/sdl, tho, I cannot get
>> input working. I
On 2023-05-19 11:04, Ivan Quitschal wrote:
> Hi all
>
> i have a question. searched everywhere and found nothing about.
>
> Is it possible to visualize photos on tty console like we used to on old
> SYSCONS by using zgv or something?
>
> Or watching videos with mpv/mplayer + sdl 2.0/openGL or
On 2022-10-27 20:57, Matteo Riondato wrote:
> On 2022-10-26 at 17:15 EDT, Colin Percival wrote:
>
>>On 10/26/22 13:48, Ed Maste wrote:
>>>On Mon, 24 Oct 2022 at 22:11, void wrote:
this started appearing in dmesg
ns8250: UART FCR is broken
ns8250: UART FCR is broken
>>>
>>>This
On Sun, 28 Aug 2022 11:37:16 +0200
Michael Gmelin wrote:
> > On 28. Aug 2022, at 10:42, free...@oldach.net wrote:
> >
> > Cy Schubert wrote on Sat, 27 Aug 2022 17:26:38 +0200 (CEST):
> >> As stated before in this thread, replacing /var/run with tmpfs is
> >> not a supported configuration.
On 30 May 2022 8:38:27 pm AWST, David Wolfskill wrote:
>On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote:
>> ...
>> I have not been able to use a new /boot/loader.efi (following -CURRENT)
>> since
>> mid to late 2021, and your symptoms look the same;
On 2022-05-30 07:10, David Wolfskill wrote:
> -- but only on one machine (of the 3 that I use for daily tracking head
> (and stable/12 & stable/13) -- the build machine ("freebeast").
>
> Each is amd64, using ... venerable ... BIOS/MBR & UFS -- stuff that has
> generally been functionally stable
On Sunday, 19 December 2021 6:47:23 PM AWST Gary Jennejohn wrote:
> Some recent change, probably in a .mk file, breaks builworld on HEAD
> when WITHOUT_PF is enabled in src.conf.
I have had to disable WITHOUT_PF since 2020-07-27, but probably earlier.
> Disabling WITHOUT_PF results in a
On 2021-03-28 16:09, Hans Petter Selasky wrote:
> On 3/27/21 11:54 AM, Santiago Martinez wrote:
>> Hi, i have the same output as @Nils B. If i run with steal =2 and dtrace the
>> micro stutter doesn't happen but as soon as i stop the dtrace script it the
>> stutters come back again.
>>
>
> Here
On 2021-03-23 17:34, myfreeweb wrote:
> On March 23, 2021 9:11:46 AM UTC, Michael Gmelin wrote:
>>
>>
>>On Mon, 22 Mar 2021 23:50:52 -0400
>>monochrome wrote:
>>
>>> After about 8 months of struggling to narrow this down I did another
>>> search and saw this:
>>>
>>>
On 2021-03-18 18:07, Jamie Landeg-Jones wrote:
> "Hartmann, O." wrote:
>
>> On Sat, 13 Mar 2021 15:13:15 -0500
>> Michael Butler via freebsd-current wrote:
>>
>> > On 3/13/21 3:00 PM, Hartmann, O. wrote:
>> > > On Sat, 13 Mar 2021 19:52:47 + (UTC)
>> > > Filippo Moretti via freebsd-current
Tested on main-n245400-e75eac2cb81
___
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 2021-03-12 12:04, David Wolfskill wrote:
> On Thu, Mar 11, 2021 at 07:57:36PM -0800, Alastair Hogge wrote:
>> Turns out, EFI boot stopped working. The following boots but fails with
>> ...
>> umass0: SCSI over Bulk-Only; quirks = 0x4001
>> umass0:6:0: Attached to s
On 2021-03-12 12:04, David Wolfskill wrote:
> On Thu, Mar 11, 2021 at 07:57:36PM -0800, Alastair Hogge wrote:
>> Turns out, EFI boot stopped working. The following boots but fails with
>> ...
>> umass0: SCSI over Bulk-Only; quirks = 0x4001
>> umass0:6:0: Attached to s
Turns out, EFI boot stopped working. The following boots but fails with
umass0:6:0: Attached to scbus6
Root mount waiting for: usbus5 CAM
panic: malloc(M_WAITOK) with sleeping prohibited
Tested with
FreeBSD-14.0-CURRENT-amd64-20210311-15565e0a217-257277-mini-memstick.img
OK boot
On 2021-02-09 02:20, Emmanuel Vadot wrote:
> Alastair: Can you report a bug there :
> https://github.com/freebsd/drm-kmod/issues
https://github.com/freebsd/drm-kmod/issues/64
___
freebsd-current@freebsd.org mailing list
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
>
Hello,
Recently I wanted to resurrect and old AMD Bobcat (14h) for use with
kgdb over dconschat. The system booted a
FreeBSD-13.0-ALPHA2-amd64-20210122 without a problem. I noticed the BIOS
was ~9 years old, so I updated the to most recent version, which is ~5
years old. After the BIOS update,
Sorry, please ignore previous reply, the modified sysctl is still
running,
the output earlier, was from the stock binary.
On 2021-02-09 14:25, Alastair Hogge wrote:
> On 2021-02-08 21:01, Hans Petter Selasky wrote:
>> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>>> Boot to multi-
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
>
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
> Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
___
On Monday, 16 September 2019 7:55:32 PM AWST Masachika ISHIZUKA wrote:
> Hi.
>
> This panic happens on 1300047 (both r352239 and r352386) with core
> i5-7500 as follows. This panic dose not happen on r351728 (1300044).
> (The following lines were typed by hand so they might have some miss
>
On Friday, 21 September 2018 11:36:27 PM AWST Matthias Apitz wrote:
> El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz
escribió:
> > ===
> > ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg
> > - not
On Mon, 30 Oct 2017-10-30 15:38:02 Alastair Hogge wrote:
> On Fri, 27 Oct 2017-10-27 12:59:30 Alastair Hogge wrote:
> > Hi,
> >
> > I am attempting to build a release ${SRC}/release/release.sh -c
>
> > ${custom_release.conf}, however, the build fails with:
>
On Fri, 27 Oct 2017-10-27 12:59:30 Alastair Hogge wrote:
> Hi,
>
> I am attempting to build a release ${SRC}/release/release.sh -c
> ${custom_release.conf}, however, the build fails with:
Updated log from a host r325110:
[...]
--- installconfig_subdir_usr.b
Source tree is at r325004
On Fri, 27 Oct 2017-10-27 12:59:30 Alastair Hogge wrote:
> Hi,
>
> I am attempting to build a release ${SRC}/release/release.sh -c
> ${custom_release.conf}, however, the build fails with:
>
> make[1]: "/scratch/fafnir/usr/src/Makefile.inc1&quo
Hi,
I am attempting to build a release ${SRC}/release/release.sh -c
${custom_release.conf}, however, the build fails with:
make[1]: "/scratch/fafnir/usr/src/Makefile.inc1" line 162: SYSTEM_COMPILER:
Determined that CC=cc matches the source tree. Not bootstrapping a cross-
compiler.
On Fri, Jun 23, 2017, at 21:00, Guy Yur wrote:
> On 23 June 2017 at 15:36, Alastair Hogge <a...@fastmail.fm> wrote:
> > Hi,
> >
> > My 12.0-CURRENT r320259 host is unable to complete a release.sh build of
> > a generic world:
> >
> > [...]
Hi,
My 12.0-CURRENT r320259 host is unable to complete a release.sh build of
a generic world:
[...]
./usr.sbin/fstyp missing (created)
./usr.sbin/makefs missing (created)
./usr.sbin/newsyslog missing (created)
On Mon, 8 May 2017 11:47:23 AM Ngie Cooper wrote:
[...]
> Hi Alastair,
> r317967 should allow you to build release images again.
Thank you very muchly,
Alastair
___
freebsd-current@freebsd.org mailing list
On Fri, 5 May 2017 11:26:44 PM Ngie Cooper wrote:
> (CCing emaste)
>
> > On May 5, 2017, at 21:55, Alastair Hogge <a...@fastmail.fm> wrote:
> …
>
> > Calculated size of `memstick.img.part': 485474304 bytes, 9435 inodes
> > Extent size set to 8192
> >
Hi,
On a r317857 amd64 host, the release.sh build fails:
# cd /usr/src/release && ./release.sh
[...]
===> usr.sbin/yp_mkdb (installconfig)
On Fri, 5 May 2017 12:41:27 PM Kyle Evans wrote:
[...]
> FYI- This has now been committed as r317842. Apologies for the breakage,
> and thanks for the reports!
Thanks :-)
___
freebsd-current@freebsd.org mailing list
On Fri, 5 May 2017 12:31:41 PM Vladimir Zakharov wrote:
> Hello!
>
> Cannot build world due to error in compiling lib/libsysdecode. Cleaning
> (make clean, make cleandepend and wiping out ccache data) does not help.
>
> $ make -j 4 buildworld && make -j 4 buildkernel && make installkernel
> ...
On Sun, 5 Mar 2017 09:50:49 AM Andriy Gapon wrote:
> On 05/03/2017 08:08, Chris H wrote:
> > Thanks for the reply.
> > I rebooted to kernel.old, so I could get the exact
> > src revision I built this on. It's r314640
> >
> > Any news as to whether it's safe to update src, and
> > build a usable
On Sat, 4 Mar 2017 10:34:39 PM Chris H wrote:
> On Sun, 05 Mar 2017 14:26:31 +0800 Alastair Hogge <a...@fastmail.fm> wrote
>
> > On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote:
> > > Thanks for the reply.
> > > I rebooted to kernel.old, so I could get
On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote:
> Thanks for the reply.
> I rebooted to kernel.old, so I could get the exact
> src revision I built this on. It's r314640
>
> Any news as to whether it's safe to update src, and
> build a usable kernel?
I am not able to boot a kernel > r314627. I
Hi *,
On Sat, 4 Mar 2017 07:38:55 PM Chris H wrote:
[remove 12-CURRENT history & hardware summary]
> I finished the
> buildworld, and finished the build/install kernel, and
> (attempted) to boot to single user. But got a trap
> shortly into booting the new kernel;
>
> kernel trap 12 with
Dear FreeBSD community,
Thanks so much for this awesome effort.
Will /usr/src/release/release.sh eventually support building base packages
as an option? If possible, is it something that we could see soon?
Ta,
Alastair
--
Why isn't there a special name for the tops of your feet?
On 2013-10-10 Thu 21:51:48 +0200, Marc UBM wrote:
Hiho! :-)
Hi
Trying to compile several ports in the wake of the recent iconv change
yields the following error that I could not get rid of yet:
libtool: link: cc -O2 -pipe -fno-strict-aliasing -Wall
-I/usr/local/include
On 2013-09-26 Thu 11:26:48 +0200, O. Hartmann wrote:
Hi,
I try my first steps with unbound on most recent current and snealing
through the web I find interesting things and howto's. But I realise if
I'd like to replace my office's DNS server (based on BIND as it was
part of the FreeBSD
On 2013-09-21 Sat 12:46:56 +0100, RW wrote:
On Sat, 21 Sep 2013 11:14:29 +0800
Alastair Hogge wrote:
On 2013-09-16 Mon 19:21:39 +0200, Joel Dahl wrote:
Hi,
Hi,
I noticed the following during boot on a machine running HEAD from
today:
I have noticed this since the recent
On 2013-09-16 Mon 19:21:39 +0200, Joel Dahl wrote:
Hi,
Hi,
I noticed the following during boot on a machine running HEAD from today:
I have noticed this since the recent work to /sys/dev/random
Entropy harvesting:sysctl: unknown oid 'kern.random.sys.harvest.interrupt':
No such file or
On Tue, May 03, 2011 at 11:50:53PM +0200, Michael Schmiedgen wrote:
On 03.05.2011 23:24, Jack Vogel wrote:
If you get the setup receive structures fail, then increase the nmbclusters.
If you use standard MTU then what you need are mbufs, and standard size
clusters (2K).
Only when you
56 matches
Mail list logo
