> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote:
>
>> On Thu, Aug 23, 2018 at 12:10:34AM +0200, Michael Gmelin wrote:
>>
>>
>>>> On 22. Aug 2018, at 23:15, Konstantin Belousov wrote:
>>>>
>>>> On Wed, Aug 22, 2018 at 10:0
>> On 24. Aug 2018, at 22:39, Konstantin Belousov wrote:
>>
>> On Fri, Aug 24, 2018 at 10:32:06PM +0200, Michael Gmelin wrote:
>>
>>
>>> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote:
>>> Please apply the following debugging
On Sun, 26 Aug 2018 16:04:35 +0300
Konstantin Belousov wrote:
> On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote:
> > Now, with the patch applied correctly, the machine actually boots.
> >
> > Before calling init_ops.mp_bootaddress in
> > getmemsize
On Wed, 29 Aug 2018 11:21:05 +0200
Michael Gmelin wrote:
> On Sun, 26 Aug 2018 16:04:35 +0300
> Konstantin Belousov wrote:
>
> > On Sat, Aug 25, 2018 at 07:21:28PM +0200, Michael Gmelin wrote:
> > > Now, with the patch applied correctly, the machine actually bo
> On 24. Sep 2018, at 11:31, Matthias Apitz wrote:
>
>
> Hello,
>
> I've booted a fresh r338641 from an USB key on my Acer C720, and have
> the required modules loaded at boot (cyapa and ig4) and the values for cyapa
> in
> /boot/device.hints, as I do use them in r314251. The moused is runni
> On 24. Sep 2018, at 12:42, Matthias Apitz wrote:
>
>> El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz
>> escribió:
>>
>>
>> Hello,
>>
>> I've booted a fresh r338641 from an USB key on my Acer C720, and have
>> the required modules loaded at boot (cyapa and ig4) an
> On 24. Sep 2018, at 15:08, Andriy Gapon wrote:
>
>> On 24/09/2018 13:21, Matthias Apitz wrote:
>> Re/ i915kms, I have to load it with kldload by hand. If I load it via
>> loader.conf, the cyapa devices (both) say 'Unable to bring the device
>> out of bootstrap'.
>
> That's probably because
> On 18. Feb 2019, at 23:54, Mark Linimon wrote:
>
>> On Mon, Feb 18, 2019 at 08:50:27AM -0800, Rodney W. Grimes wrote:
>> I think one serious problem here is the summary dismissal of things
>> simply on the "5 year old" basis.
>
> IIUC the graphics changes are being forced upon FreeBSD by ext
> On 19. Sep 2019, at 17:57, Kurt Jaeger wrote:
>
> Hi!
>
>>> We have a system with 10 SATA disks. 2 disks are for the system,
>>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
>>>
>>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE
>
On 19. Sep 2019, at 19:15, Kurt Jaeger wrote:
>>> I've made a few more details available here:
>
>>> https://people.freebsd.org/~pi/host/gpart.txt
>
>> What about gpart output of the pool drives?
>
> No gpart on the bck pool, raw drives.
>
>> In general you would create zpools using gptids
Unless your laptop is really old, make sure to install amd64.
Best,
Michael
> On 22. Nov 2019, at 22:25, Robert wrote:
>
> Thanks all, in the process of installing 13-current snapshot.
>
>> On Fri, 22 Nov 2019 at 22:21, Clay Daniels
>> wrote:
>>
>> Just my two cents worth, but I think you w
e 1
>
> make[6]: stopped in
> <https://jenkins.freebsd.org/job/FreeBSD_HEAD/ws/sys/boot/i386/libi386>
> 1 error
>
> make[6]: stopped in
> <https://jenkins.freebsd.org/job/FreeBSD_HEAD/ws/sys/boot/i386/libi386>
t;);
+ if (b_bios_probed & B_EXTMEM_E820)
+ printf(" B_EXTMEM_E820");
+ if (b_bios_probed & B_EXTMEM_E801)
+ printf(" B_EXTMEM_E801");
+ if (b_bios_probed & B_EXTMEM_8800)
+ printf(" B_EXTMEM_8800");
+ printf("\n");
+
+ return (CMD_OK);
+}
+
+COMMAND_SET(smap, "biosmem", "show BIOS memory setup", command_biosmem);
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote:
>
> [Moving to current@]
>
>> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote:
>>
>> Surprises:
>> * nagios doesn't like w / uptime anymore. libxo perhaps?
>
> Seems most likely, although I haven’t seen any differences in output
> in my (a
> On 10 Feb 2015, at 22:17, Michael Gmelin wrote:
>
>
>
>
>> On 10 Feb 2015, at 21:13, Marcel Moolenaar wrote:
>>
>> [Moving to current@]
>>
>>> On Feb 10, 2015, at 11:52 AM, Peter Wemm wrote:
>>>
>>> Surprises:
>>
On Tue, 10 Feb 2015 22:24:59 +0100
Michael Gmelin wrote:
>
>
>
> > On 10 Feb 2015, at 22:17, Michael Gmelin wrote:
> >
> >
> >
> >
> >> On 10 Feb 2015, at 21:13, Marcel Moolenaar
> >> wrote:
> >>
> >> [Movi
ur. The real solution is to
> continue sliding i915 forward in time.
>
In the meantime this workaround might be useful (not sure if it works
while the driver is loaded):
https://github.com/grembo/intel_backlight_fbsd
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On 19 Feb 2015, at 09:16, Julian Elischer wrote:
>
>> On 2/18/15 3:41 PM, Xin Li wrote:
>>
>> The _only_ reason that I can think of is that more(1) does not clear
>> screen for certain terminals (done with 'ti' and 'te' sequences),
>> while less(1) when running as less does.
>>
>> The less
nly bugs
> I've seen with the xo-ification have been ones where the JSON output
> was not always well formed.
>
There was one where uptime(1) wouldn't emit any output when called in a
pipeline (missing call to xo_finish, that wouldn't affect the output on
a tty due to implicit flush on newline).
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On 08 Apr 2015, at 21:30, Ryan Stone wrote:
>
> No, this isn't a late April Fools joke. :(
>
> I find myself in a situation where I need to integrate my employer's
> manufacturing process with a third-party OEM's process. My employer's
> hardware tests are all FreeBSD-based while the OEM i
fork_trampoline() at fork_trampoline+0xe/frame
> > 0xfe011414aab0 --- trap 0, rip = 0, rsp = 0xfe011414ab70,
> > rbp = 0 ---
>
I've seen those as well while destroying 190.000 zfs snapshots
(caused by an lpreserver runaway). Got four panics in the process, also
running on to
> On 17 Sep 2015, at 20:23, Russell L. Carter wrote:
>
>
>
>> On 09/17/15 10:40, Matthias Apitz wrote:
>> El dÃa Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore
>> escribió:
>>
>>> On 09/17/2015 09:48, Matthias Apitz wrote:
El dÃa Thursday, September 17, 2015 a las 1
> On 18 Sep 2015, at 07:34, Matthias Apitz wrote:
>
>> El día Thursday, September 17, 2015 a las 11:42:01PM +0200, Nikola Pajkovsky
>> escribió:
>>
>> Do not run those commands in X, otherwise it hangs.
>>
>> $ vidcontrol -i mode | grep 1920
>> 383 (0x17f) 0x000f G 1920x1080x32 D 8x16
> On 18 Sep 2015, at 15:33, Stefan Wendler wrote:
>
>> On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote:
>> You must run a ver y recent -HEAD; Wifi is fine
>
> I cannot run HEAD because I need a stable system for work. Will there be a
> package for FreeBSD 10? I really want to get
On Fri, 18 Sep 2015 16:12:04 +0200
Stefan Wendler wrote:
> On Friday 18 September 2015 15:57:10 Michael Gmelin wrote:
> > > On 18 Sep 2015, at 15:33, Stefan Wendler
> > >
> wrote:
> > >> On Thursday 17 September 2015 20:57:20 Matthias Apitz wrote:
> >
ing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
--
Michael Gmelin
pgpxB3FgodfPG.pgp
Description: OpenPGP digital signature
__
> 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"
--
Michael Gmelin
___
freebsd-current@freebsd.org
On Mon, 2 Nov 2015 19:29:39 -0800
Craig Rodrigues wrote:
> On Mon, Nov 2, 2015 at 3:50 PM, Michael Gmelin
> wrote:
> >
> >
> >
> > On Mon, 2 Nov 2015 14:04:18 -0800
> >
> > ikvjwd.com once offered a service using haproxy, you can find their
> >
> On 07 Jan 2016, at 02:49, Matthias Apitz wrote:
>
>
> Hello,
>
> I have updated my Acer C720 netbook (amd64) from r285885 to r292778 and
> now I do not see any network devices; the kernel is just GENERIC;
>
> the lines in /etc/rc.conf are
>
> wlans_ath0="wlan0"
> ifconfig_wlan0="WPA DHCP"
> So I have two problems --- ports are not working and buildworld is
> failing. I have run out of ideas currently so a few advices would be
> appreciated.
>
What's the output of these commands?:
freebsd-version
uname -r
uname -a
grep "define __FreeBSD_version" /usr/inclu
; In fact cc and clang look like a hardlink to the same file. Any ideas
> why one is capable of building the world and second is not?
>
Do you still have your old make.conf for comparison? Also, what is your
PATH environment variable set to?
- Michael
--
Michael Gmelin
___
> On 19 May 2016, at 23:29, jungle Boogie wrote:
>
>> On 19 May 2016 at 13:31, Glen Barber wrote:
>> Given the state of this highly-disruptive change to the base system, we
>> need to take the best interest of the FreeBSD community into primary
>> consideration, as a whole.
>>
>> We have arri
rom ufs:/dev/ad4s1a [rw]...
> mountroot: waiting for device /dev/ad4s1a ...
> Mounting from ufs:/dev/ad4s1a failed with error 19.
>
> Than it goes into the manual dialog to specify the root device but at
> the prompt
>
> mountroot>
>
> the kernel does not echo a
On Sat, 4 Jun 2016 13:48:52 +0200
Matthias Apitz wrote:
> Hi Michael,
>
> El día Saturday, June 04, 2016 a las 01:40:46PM +0200, Michael Gmelin
> escribió:
>
> > Hi Matthias,
> >
> > Did you try to connect an external USB keyboard?
>
> no; it uses t
On Sat, 4 Jun 2016 14:01:34 +0200
Matthias Apitz wrote:
> El día Saturday, June 04, 2016 a las 01:54:30PM +0200, Michael Gmelin
> escribió:
>
> >
> > On Sat, 4 Jun 2016 13:48:52 +0200
> > Matthias Apitz wrote:
> >
> > > > Did you do a full
e file a port bug against linux_base-c6. At the very least
> the message should be more intuitive about what's trying to be
> achieved; you will need to "kldload linux", which was the status quo
> in old versions IIRC. Thanks, -Ngie
>
Requiring linux_base-c6 to insta
linker_load_file: Unsupported file type
I also noticed that isl cannot be built from the module source
directory:
# cd /usr/src/sys/modules/i2c/isl
# make
...
/usr/src/sys/sys/vnode.h:571:10: fatal error: 'vnode_if.h' file not
found
#include "vnode_if.h"
^
1 error gene
On Mon, 3 Oct 2016 19:41:17 +0300
Andriy Gapon wrote:
> On 03/10/2016 19:07, Michael Gmelin wrote:
> > I upgraded the latter the r306641, applied your patches (cleanly)
> > and ran "make kernel" (GENERIC kernel), added the entries to
> > device.hints and reboote
On Tue, 4 Oct 2016 01:04:10 +0300
Andriy Gapon wrote:
> On 03/10/2016 23:25, Michael Gmelin wrote:
> > On Mon, 3 Oct 2016 19:41:17 +0300
> > Andriy Gapon wrote:
> >
> >> On 03/10/2016 19:07, Michael Gmelin wrote:
> >>> I upgraded the latter
On Tue, 4 Oct 2016 13:07:28 +0300
Andriy Gapon wrote:
> On 04/10/2016 12:46, Michael Gmelin wrote:
> > iicbus(0|1) actually show up in devinfo -v, but nothing else works.
> >
> > You can find a log file and various outputs (dmesg, devinfo etc)
> > here:
> >
> On 05 Oct 2016, at 07:48, Andriy Gapon wrote:
>
>> On 05/10/2016 01:48, Michael Gmelin wrote:
>> Double-checked the hints, it's all ok.
>>
>> Please find a more verbose log file of loading the kernel modules here:
>>
>> https
> On 05 Oct 2016, at 13:32, Malcolm Matalka wrote:
>
> Den 5 okt. 2016 13:19 skrev "Michael Gmelin" :
> >
> >
> >
> > > On 05 Oct 2016, at 07:48, Andriy Gapon wrote:
> > >
> > >> On 05/10/2016 01:48, Michael Gmelin wrote:
>
> On 05 Oct 2016, at 15:01, Andriy Gapon wrote:
>
>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>
>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and
>> iicbus_attach are not.
>
> Thank you!
> Now I think I see where
> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
>
>> On 06/10/2016 08:37, Andriy Gapon wrote:
>> The more testing the better!
>
> Based on Michael's results I've uploaded a new version:
> https://people.freebsd.org/~avg/ig4-i2c.v4.diff
>
>
Good news. Applying the last two fixes manually, is
On Thu, 6 Oct 2016 11:12:27 +0300
Andriy Gapon wrote:
> On 06/10/2016 11:10, Michael Gmelin wrote:
> >
> >
> >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote:
> >>
> >>> On 06/10/2016 08:37, Andriy Gapon wrote:
> >>> The more testin
sl and cyapa work, and
putting things like that (and other hints, e.g. to route the Intel HDA
correctly) into a man page ("apropos c720") would be the next best
thing to having it work out of the box.
-m
--
Michael Gmelin
___
freebs
t this is a driver that listens for new iicbus-es and
> adds isl and cyapa devices to a bus if some criteria are met.
>
For the Acer c720, these criteria would be:
smbios.bios.vendor=="coreboot"
smbios.system.maker=="Acer"
smbios.system.product=="Peppy"
See also
boot/i386/libi386/biosmem.c
dev/atkbdc/atkbdc.c
- Michael
--
Michael Gmelin
___
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 10 Oct 2016, at 20:27, Matthias Apitz wrote:
>
>> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió:
>>
>> I see no reason not to start the table right away based on
>> smbios.sys.product and other criteria. I don't think we need all the
>> matches that Linux us
rg/ports/head/sysutils/xmbmon/files/patch-getMB-smb_ioctl.c?r1=385155&r2=385154&pathrev=385155
> I see that it also used the approach that you use as a workaround.
> And that port commit is by Michael Gmelin who made the change to
> smb.h in r281985
> https://svnweb.freebsd.org/
worked ok (last version I tested personally was back in
November/December though).
-m
[0]
https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170210-r313561-memstick.img
--
Michael Gmelin
___
freebsd
an error return to this routine is a
> > little much, though. I think probably the caller should perform
> > input validation between the broken device and this routine.
>
> Either of those would be a much better solution. This was just a
> quick hack to get the memstick t
>
> -adrian
>
>> On 28 February 2017 at 15:26, Michael Gmelin wrote:
>> On Tue, 28 Feb 2017 17:16:02 -0600
>> Eric van Gyzen wrote:
>>
>>>> On 02/28/2017 16:57, Conrad Meyer wrote:
>>>> On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen
&g
> On 22 Mar 2017, at 21:02, O. Hartmann wrote:
>
> CURRENT (FreeBSD 12.0-CURRENT #82 r315720: Wed Mar 22 18:49:28 CET 2017
> amd64) is
> annoyingly slow! While scrubbing is working on my 12 GB ZFS volume, updating
> /usr/ports
> takes >25 min(!). That is an absolute record now.
>
> I do an a
>> # cat /dev/random > /dev/dsp*
> >> only generate noise in the headphones..
> >>
> >>
> > MBP requires some patches for the speakers to work:
> >
> > https://svnweb.freebsd.org/base?view=revision&revision=261507
> >
> > --HPS
> >
> __
vref,vref
> dev.hdaa.0.nid3_original: 0x18560010 as=1 seq=0 device=Digital-out
> conn=Jack ctype=Digital loc=0x18 color=Unknown misc=0
> dev.hdaa.0.nid3_config: 0x18560010 as=1 seq=0 device=Digital-out conn=Jack
> ctype=Digital loc=0x18 color=Unknown misc=0
> dev.hdaa.0.nid3: pin: D
akers
> hint.hdaa.1.nid18.config="as=4 seq=0"
> hint.hdaa.1.nid19.config="as=5 seq=0"
>
> hint.hdaa.1.gpio_config="3=set"
>
>
>
>
> On Fri, Apr 28, 2017 at 3:21 PM, Michael Gmelin
> wrote:
>
> > Without looking through all
>> On Fri, Apr 28, 2017 at 5:05 PM, Michael Gmelin wrote:
>>
>> device.conf or device.hints?
>>
>> Note that you can also set these using sysctl for experimentation.
>> Which exact model number of the macbook pro are you using?
>>
>> -m
>>
&
gt;
> That would be awesome! Yes, my model is also A1398.
>
> After patching the asmc driver (has been committed) freebsd runs great on
> it.
> All that's missing is sound :)
>
>
>> On Fri, Apr 28, 2017 at 7:06 PM, Michael Gmelin wrote:
>>
>>
in that specific case
also from callbacks that were called from within db5. Overall the
code was quite convoluted, but valid C++03.
On top of that there are the usual incompatibilities between
implementations (like iostreams in gcc 4.2's libstdc++ does some things
differently then the
ave been installing packages to jails this way for a while.
>
> # pkg-static -c /mnt install xorg-7.7
>
> gives the same error messages as above.
>
Did you run "pkg repo" on your repo, e.g.
cd mypackerepodir
pkg repo .
If you don't want to use a repo you could
> On 31. Jan 2023, at 22:44, Kurt Jaeger wrote:
>
> Hi!
>
This can be as easy as moving everything into Phabricator.
>>> There's the issue that Phabricator itself is no longer supported
>>> upstream:
> [...]
>>> https://we.phorge.it/
>
>> Should be no harder than regular update. They e
On Thu, 23 Jun 2022 11:15:55 -0600
Warner Losh wrote:
> On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin
> wrote:
>
> >
> >
> > On Fri, 21 May 2021 08:36:49 -0600
> > Warner Losh wrote:
> >
> > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies
&
chael
--
Michael Gmelin
On Thu, 8 Jun 2023 16:20:12 +
Glen Barber wrote:
> On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote:
> > Hi,
> >
> > I didn't dig into this yet.
> >
> > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I
> > g
On Thu, 8 Jun 2023 19:06:23 +0200
Michael Gmelin wrote:
> On Thu, 8 Jun 2023 16:20:12 +
> Glen Barber wrote:
>
> > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote:
> > > Hi,
> > >
> > > I didn't dig into this yet.
> &
On Thu, 8 Jun 2023 11:32:19 -0600
Warner Losh wrote:
> On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin
> wrote:
>
> > >
> > > Tried today's snaphot, same problem.
> > >
> > > # reboot
> > > Waiting (max 60 seconds) for system pr
On 6. Aug 2023, at 18:12, Warner Losh wrote:On Sun, Aug 6, 2023 at 10:05 AM Matthias Apitz wrote:El día domingo, agosto 06, 2023 a las 09:58:32a. m. -0600, Warner Losh escribió:
> On Sun, Aug 6, 2023 at 7:58 AM Matthias Apitz wrote:
>
> >
> > I did, based o
d.org/ports.git` work for you?
(currently it's not working from where I am). Maybe related.
Best
Michael
--
Michael Gmelin
cause keyboard/mouse freezes on some hardware, please set
loader tunable hw.atkbd.hz=1 as workaround and report the issue.
So you could try to set hw.atkbd.hz=1 (or hw.atkbd.hz=10) in
/boot/loader.conf, then reboot and see if it helps.
Best
Michael
--
Michael Gmelin
ould you please Cc me on it?
Do you know which version of FreeBSD was the last that worked for you?
Cheers
>
>
>> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael Gmelin
>> escribió:
>>
>>
>>
>> On Mon, 4 Sep 2023 18:43:11 +020
> On 4. Sep 2023, at 19:34, Matthias Apitz wrote:
>
> El día lunes, septiembre 04, 2023 a las 07:29:41p. m. +0200, Michael Gmelin
> escribió:
>
>>
>>
>>>> On 4. Sep 2023, at 19:23, Matthias Apitz wrote:
>>>
>>>
t; the loader we're using has to understand the ZFS dataset that it's
> booting off of. FreeBSD
> 13's userboot.so doesn't support all the bells and whistles that the
> ZFS folks have added
> to 14.
>
> So, either you have to turn off those features (which I got no clue
> how to do in the
> normal installer), or you have to update userboot.so to the FreeBSD 14
> version (which
> I think had a good chance of actually running on FreeBSD 13 since it
> has no 'system'
> references, which are confined to bhyveload).
>
> Warner
>
>
> > >
> > > # find /boot/efi/EFI/ -print
> > > /boot/efi/EFI/
> > > /boot/efi/EFI/FREEBSD
> > > /boot/efi/EFI/FREEBSD/loader.efi
> > > /boot/efi/EFI/BOOT
> > > /boot/efi/EFI/BOOT/bootaa64.efi
> > >
> > > There may well be only:
> > >
> > > EFI/BOOT/bootaa64.efi
> > >
> > > for all I know.
> > >
> > > From an amd64 context:
> > >
> > > # find /boot/efi/EFI/ -print
> > > /boot/efi/EFI/
> > > /boot/efi/EFI/FREEBSD
> > > /boot/efi/EFI/FREEBSD/loader.efi
> > > /boot/efi/EFI/BOOT
> > > /boot/efi/EFI/BOOT/bootx64.efi
> > >
> > > There may well be only:
> > >
> > > EFI/BOOT/bootx64.efi
> > >
> > > for all I know.
> > >
> > > (I set things up to have the EFI capitalization
> > > so that referencing efi/ vs. EFI/ in my context
> > > is unique for the mount point. vs. the msdosfs
> > > directory.)
> > >
> > > ===
> > > Mark Millard
> > > marklmi at yahoo.com
> > >
> > >
> >
> >
> >
--
Michael Gmelin
> On 19. Sep 2023, at 12:30, Ronald Klop wrote:
>
> Hi,
>
> In current the way ps -p works has been changed [1].
> I could use "ps axd -p " to see the process tree of some ongoing task.
> In current this has changed to always need an extra option "ps axd -p
> -D down". Can this become the d
> On 3. Oct 2023, at 18:27, Matthias Apitz wrote:
>
> El día martes, octubre 03, 2023 a las 06:14:23p. m. +0200, Olivier Certner
> escribió:
>
>> Hi Matthias,
>>
>> Some ZFS dataset with zstd compression on jet, and no compression on
>> c720-1400094?
>>
>
> Yes, on jet it is ZFS:
>
> r
> On 23. Dec 2023, at 16:10, Enji Cooper wrote:
>
>
>> On Dec 22, 2023, at 23:18, Xin Li wrote:
>>
>> Hi,
>>
>> Inspired by D42961, I propose that we move forward with disabling the
>> compression by default in newsyslog, as implemented in
>> https://reviews.freebsd.org/D43169
>>
>> H
> On 30. Mar 2024, at 07:30, Chris wrote:
>
> On 2024-03-29 23:06, Michael Schuster wrote:
>> Two ideas:
>> - does CTL-ALT-Fn work?
> Thanks. But no, I tried that.
>
>> - perhaps the number of predefined ttys was overwritten/set to 0 somewhere?
> I'm only aware of /etc/ttys, and they're all
4 -interface bla0"
sysrc route_default="default 1.2.3.4"
This is actually quite useful in some setups, but in the context of
deciding on default behavior when no mask is given this is probably not
very helpful.
Cheers
--
Michael Gmelin
On Wed, 12 Jun 2024 11:28:38 +
"Poul-Henning Kamp" wrote:
> ----
> Michael Gmelin writes:
>
> > You can do an interface route hack
>
> I think you misunderstand the situation.
I completely understand the situation and I can feel your pain, I just
estingly, `ifconfig vtnet0 10.0.0.1` uses "/24" whereas
192.168.87.11 uses "/8".
This dates back to:
https://cgit.freebsd.org/src/commit/?id=4bf44dd73bc0a
-m
--
Michael Gmelin
On Wed, 12 Jun 2024 15:11:14 + (UTC)
"Bjoern A. Zeeb" wrote:
> On Wed, 12 Jun 2024, Bjoern A. Zeeb wrote:
>
> > On Wed, 12 Jun 2024, Michael Gmelin wrote:
> >
> >>
> >>
> >> On Wed, 12 Jun 2024 14:36:35 +
> >> &
On Wed, 12 Jun 2024 15:35:58 +
"Poul-Henning Kamp" wrote:
> ----
> Michael Gmelin writes:
>
> > @phk From which version did you upgrade?
>
> To be totally honest: I'm not entirely sure. Probably 13.x
>
@Bjoern I checked again, I'm pre
;known issues",
which those of us who read the release notes can stumble over and check?
This would be useful in general, as it seems like doing ENs is a lot of
overhead. Also, if that process would be fast, users would be warned
early - especially in a case like this, where the workaround/long term
fix is actually fairly trivial (add a netmask to your ifconfig_xxx
line).
Best
Michael
--
Michael Gmelin
> On 17. Jun 2024, at 20:34, Shawn Webb wrote:
>
> On Mon, Jun 17, 2024 at 10:54:29AM -0400, Ed Maste wrote:
>> It is currently possible to specify an IPv4 address without a
>> netmask/width to ifconfig or in rc.conf, e.g.:
>>
>>ifconfig_igb0="192.168.0.2"
>>
>> phk recently discovered[
> being added to the boot loader. It should almost always be empty or
w> just drm-mod these days (unless you somehow have special needs).
w>
w> By adding uhid last to this list in this way, you're guaranteeing
w> you'll hit this bug because it's not after ums, and that things
w> won't work.
w>
w> Warner
Cheers
--
Michael Gmelin
> On 20. Aug 2024, at 04:15, Larry Rosenman wrote:
>
> shows up, doesn't ping -- ifconfig up brings it back for ~4 packets
>
> ifconfig_re0="DHCP"
> ifconfig_re0_ipv6="inet6 accept_rtadv"
> ipv6_activate_all_interfaces="AUTO"
> rtsold_enable="YES"
>
> 15-CURRENT as of just now, port of net/
> On 29. Dec 2017, at 20:15, Shawn Webb wrote:
>
> Hey All,
>
> It looks like evdev support in the kernel is broken.
> sys/dev/kbdmux/kbdmux.c contains various unresolved symbols to
> different evdev-related symbols.
>
> I have the following options in my kernel config:
>
> options E
(like evdev, udev and libinput), that's why I documented my
setup here, hoping that it might help others:
https://blog.grem.de/pages/t470s.html
Best and Happy New Year,
Michael
p.s. Sorry for cross-posting.
--
Michael Gmelin
___
freebsd-current@f
> On 7. Jan 2018, at 20:43, clutton wrote:
>
>> On Sat, 2017-12-30 at 15:58 +0100, Michael Gmelin wrote:
>> Hi,
>
> Running carbon 5th gen I can't call my setup a success. Wireless iwm
> doesn't support even N and AC is not supported at all. The wifi is
On 7. Jan 2018, at 21:32, Rodney W. Grimes
wrote:
>>
>>
>>>> On 7. Jan 2018, at 20:43, clutton wrote:
>>>>
>>>> On Sat, 2017-12-30 at 15:58 +0100, Michael Gmelin wrote:
>>>> Hi,
>>>
>>> Running carbon 5th gen I
On 7. Jan 2018, at 22:40, Rodney W. Grimes
wrote:
>>
>>
>> On 7. Jan 2018, at 21:32, Rodney W. Grimes
>> wrote:
>>
>>>>
>>>>
>>>>>> On 7. Jan 2018, at 20:43, clutton wrote:
>>>>>>
>>>
t;
> For me the main concern is Thunderbolt thought, docking station is
> amazing thing. Any ideas and thought how to make it work would be
> highly appreciated.
--
Michael Gmelin
___
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"
as those really
shouldn't be touched these days):
https://reviews.freebsd.org/D14103
Direct link to the patch:
https://reviews.freebsd.org/D14103?download=true
Testers and code reviews are welcome.
Best,
Michael
p.s. Make sure to load the correct kernel module in case you rebuilt
it individually.
--
Michael Gmelin
___
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"
ble to provide a bit of debugging direction here?
> > Reviewing `dmesg -a` doesn't tell me anything specific about
> > acpi_ibm.
> >
> > Thanks in advance for your time and trouble.
> > Bridger
> > ___
> > 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"
>
>
--
Michael Gmelin
___
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 19. Feb 2018, at 20:27, Ronald Klop wrote:
>
> I just did this.
>
> root@sjakie ~]# pkg upgrade
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%944 B 0.9kB/s00:01
> Fetching packagesite.txz: 100%6 MiB 6.0MB/s00:01
> Processing entries: 0%
> pkg: Ne
Still breaks automation, doesn’t it?
> On 21. Feb 2018, at 20:49, Andreas Nilsson wrote:
>
> As of pkg-1.10.5 it will ask if you wish to proceed which makes this much
> easier to deal with.
>
> Best regards
> Andreas
>
> On Feb 21, 2018 20:45, "Trond Endrestøl" <
> trond.endres...@fagskolen.gj
> On 11. Mar 2018, at 00:47, O. Hartmann wrote:
>
> Am Wed, 7 Mar 2018 14:39:13 +0400
> Roman Bogorodskiy schrieb:
>
>> Danilo G. Baio wrote:
>>
On Tue, Mar 06, 2018 at 01:36:45PM -0600, Larry Rosenman wrote:
On Tue, Mar 06, 2018 at 10:16:36AM -0800, Rodney W. Grimes wrote:
>>
> On 13. May 2018, at 11:54, Niclas Zeising wrote:
>
>> On 05/13/18 09:48, Andriy Gapon wrote:
>>> On 13/05/2018 05: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
> On 2. Jun 2018, at 12:41, Matthias Apitz wrote:
>
>> On Saturday, 2 June 2018 12:26:03 CEST, Greg V
>> wrote:
>> ...
>> cyapa is indeed not the right driver either. The "cy" is for Cypress. That's
>> the touchpad found in e.g. the Acer C720.
>> ...
>
> Side note:
>
> I own three C720, th
= 0
current process = 0 ()
[ thread pid 0 tid 0 ]
Stopped at native_start_all_aps+0x08f: movq %rax,(%rsi)
db>
Any key press in the debugger will reboot the machine.
Booting with kern.smp.disabled=1 works.
Any ideas?
-m
--
Michael Gmelin
On Sun, 3 Jun 2018 16:21:10 +0300
Konstantin Belousov wrote:
> On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote:
> > Hi,
> >
> > After upgrading CURRENT to r333992 (from something at least a year
> > old, quite some changes in mp_machdep.c since),
1 - 100 of 223 matches
Mail list logo