Re: Updating motherboard BIOS without MS Windows

From: Nuno Teixeira Subject: Updating motherboard BIOS without MS Windows Date: Sat, 11 Nov 2023 10:56:58 + > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy

Re: Updating motherboard BIOS without MS Windows

On Sat, 11 Nov 2023 10:56:58 + Nuno Teixeira wrote: > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for > brand

Re: Updating motherboard BIOS without MS Windows

Hi! > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for > brands that have bios-cli that work in FreeBSD. There's sysutils/flashrom which allows to flash some BIOS systems. Th

Re: Updating motherboard BIOS without MS Windows

Hi, > On 11 Nov 2023, at 10:56, Nuno Teixeira wrote: > > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for bra

Re: Updating motherboard BIOS without MS Windows

On Saturday, November 11th, 2023 at 11:56, Nuno Teixeira wrote: > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking

Re: Updating motherboard BIOS without MS Windows

On 11/11/23 11:56, Nuno Teixeira wrote: Hello all, Maybe not the best mailing to ask it but... How do you update BIOS without Windows since most brands only have bios software to windows? I'm about to buy a new pc without windows license and I'm looking for brands that have bios-cli that wo

Re: Updating EFI boot loader results in boot hangup

On 8/nn/22, yet top-posted: > [snip] https://www.idallen.com/topposting.html

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Re: Updating EFI boot loader results in boot hangup Date: Tue, 16 Aug 2022 12:01:42 +0900 (JST) >>> I made regular update of my 14-CURRENT amd64 system from >>> main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated >>> EFI

Re: Updating EFI boot loader results in boot hangup

On Wed, 17 Aug 2022 07:55:32 +0900 Tomoaki AOKI wrote: > On Mon, 15 Aug 2022 21:35:52 -0600 > Warner Losh wrote: > > > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader res

Re: Updating EFI boot loader results in boot hangup

On Thu, Aug 18, 2022, 12:19 AM Simon J. Gerraty wrote: > Warner Losh wrote: > > I think I broke it with my latest updates. I don't have a good ZFS > testing setup > > so I'm spending a little time enhancing the bootable image generator to > have > > one that I can easily test boot with qemu. > >

Re: Updating EFI boot loader results in boot hangup

Warner Losh wrote: > I think I broke it with my latest updates. I don't have a good ZFS testing > setup > so I'm spending a little time enhancing the bootable image generator to have > one that I can easily test boot with qemu. FWIW bhyve is *excellent* for mucking about with EFI and loader in g

Re: Updating EFI boot loader results in boot hangup

Hi all, > Am 17.08.2022 um 13:48 schrieb Idwer Vollering : > > $ sudo camcontrol devlist > at scbus0 target 0 lun 0 (pass0,ada0) > at scbus1 target 0 lun 0 (pass1,ada1) > > $ gpart show ada0 ada1 > =>40 1953525088 ada0 GPT (932G) > 401024 1 f

Re: Updating EFI boot loader results in boot hangup

n, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader results in boot hangup > > > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > > > > > > > From: Yasuhiro Kimura > > &g

Re: Updating EFI boot loader results in boot hangup

On Wed, 17 Aug 2022 07:55:32 +0900, Tomoaki AOKI wrote: > On Mon, 15 Aug 2022 21:35:52 -0600 > Warner Losh wrote: > > > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > > > From: Yasuhiro Kimura > > > Subject: Re: Updating EFI boot loader

Re: Updating EFI boot loader results in boot hangup

On Mon, 15 Aug 2022 21:35:52 -0600 Warner Losh wrote: > On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > > > From: Yasuhiro Kimura > > Subject: Re: Updating EFI boot loader results in boot hangup > > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > &g

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Mon, 15 Aug 2022 21:35:52 -0600 > Would you be able to share camcontrol devlist output? Privately if > need be. root@rolling-vm-freebsd1[1001]# camcontrol devlist at scbus0 target 0 lun 0

Re: Updating EFI boot loader results in boot hangup

On Mon, Aug 15, 2022, 9:04 PM Yasuhiro Kimura wrote: > From: Yasuhiro Kimura > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > > > From: Yasuhiro Kimura > > Subject: Updating EFI boot loader results in boot

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Re: Updating EFI boot loader results in boot hangup Date: Sun, 14 Aug 2022 06:34:40 +0900 (JST) > From: Yasuhiro Kimura > Subject: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > >> I made regul

Re: Updating EFI boot loader results in boot hangup

Isn't better just to mount -t msdos /dev/xxxpn /mnt and cp /boot/loader.efi /mnt/efi/boot/bootx64.efi? Pete Wright escreveu no dia domingo, 14/08/2022 à(s) 22:58: > > > On 8/14/22 13:26, Graham Perrin wrote: > > On 14/08/2022 20:26, Pete Wright wrote: > > … has anyone else who has been impacted

Re: Updating EFI boot loader results in boot hangup

On 8/14/22 13:26, Graham Perrin wrote: On 14/08/2022 20:26, Pete Wright wrote: … has anyone else who has been impacted by this been able to recover? … If you have multiple boot environments: do you have a non-affected BE (prior to c32dde3166922f55927764464d13f1bc9640f5f6)? So unfortunately

Re: Updating EFI boot loader results in boot hangup

On 14/08/2022 20:26, Pete Wright wrote: … has anyone else who has been impacted by this been able to recover? … If you have multiple boot environments: do you have a non-affected BE (prior to c32dde3166922f55927764464d13f1bc9640f5f6)?

Re: Updating EFI boot loader results in boot hangup

On Sun, Aug 14, 2022 at 1:26 PM Pete Wright wrote: > On Sun, Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote: > > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: > > > Yes, Yasuhiro and I have the same error. > > > > Just a "me too", also on ZFS, on a Ryzen 3 based system. > > > > Booting the lat

Re: Updating EFI boot loader results in boot hangup

On Sun, Aug 14, 2022 at 10:26:32AM +0200, Stefan Esser wrote: > Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: > > Yes, Yasuhiro and I have the same error. > > Just a "me too", also on ZFS, on a Ryzen 3 based system. > > Booting the latest USB snapshot image worked, but not when I copy > the whole of

Re: Updating EFI boot loader results in boot hangup

ok, yes, there is something bad happening: https://paste.ec/paste/4p6Tf7Bl#yD6QIahJs1U1SRryaKUCqOHDdf5YDUfvB-wBvwAmhV4 second pointer is supposed to be pointer to device specific format function and on last visible li

Re: Updating EFI boot loader results in boot hangup

Am 14.08.22 um 04:20 schrieb Oleg Lelchuk: Yes, Yasuhiro and I have the same error. Just a "me too", also on ZFS, on a Ryzen 3 based system. Booting the latest USB snapshot image worked, but not when I copy the whole of /boot from that USB stick to my ZFS boot partition. The system is usable

Re: Updating EFI boot loader results in boot hangup

Yes, Yasuhiro and I have the same error. On Sat, Aug 13, 2022, 10:09 PM Yasuhiro Kimura wrote: > From: Warner Losh > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 20:01:03 -0600 > > > UFS or ZFS? > > > > Warner > >

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 20:01:03 -0600 > UFS or ZFS? > > Warner ZFS in my case. --- Yasuhiro Kimura

Re: Updating EFI boot loader results in boot hangup

at precedes it > https://cgit.freebsd.org/src/commit/?id=ad759c73522efb606135e2891ac03864926b80a3 > causes a different kind of error. > > On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura wrote: > >> From: Oleg Lelchuk >> Subject: Re: Updating EFI boot loader results in bo

Re: Updating EFI boot loader results in boot hangup

b80a3 causes a different kind of error. On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura wrote: > From: Oleg Lelchuk > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 20:28:09 -0400 > > > I can

Re: Updating EFI boot loader results in boot hangup

From: Oleg Lelchuk Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 20:28:09 -0400 > I can already see that commit > > c32dde3166922f55927764464d13f1bc9640f5f6 causes breakage, but the commit that > precedes it > > f197c0bf3e075286ccea32

Re: Updating EFI boot loader results in boot hangup

et another commit caused a different kind of breakage again. On Sat, Aug 13, 2022 at 7:41 PM Yasuhiro Kimura wrote: > From: Oleg Lelchuk > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 19:32:16 -0400 > > > You can do make and make insta

Re: Updating EFI boot loader results in boot hangup

From: Oleg Lelchuk Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 19:32:16 -0400 > You can do make and make install in /usr/src/stand Thanks for letting me know. I'll try it. --- Yasuhiro Kimura

Re: Updating EFI boot loader results in boot hangup

You can do make and make install in /usr/src/stand On Sat, Aug 13, 2022 at 7:31 PM Yasuhiro Kimura wrote: > From: Warner Losh > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 16:59:55 -0600 > > > Any chance of a bisect of which revis

Re: Updating EFI boot loader results in boot hangup

From: Warner Losh Subject: Re: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 16:59:55 -0600 > Any chance of a bisect of which revision starts to fail? > > Warner I'll try it. Is it possbile to build only loader.efi without doing buildworld? I'd

Re: Updating EFI boot loader results in boot hangup

Any chance of a bisect of which revision starts to fail? Warner On Sat, Aug 13, 2022 at 4:49 PM Oleg Lelchuk wrote: > I experienced the same problem. I hope this bug will be fixed soon. > > On Sat, Aug 13, 2022 at 5:36 PM Yasuhiro Kimura wrote: > >> From: Yasuhiro Kimura >> Subject: Updating

Re: Updating EFI boot loader results in boot hangup

I experienced the same problem. I hope this bug will be fixed soon. On Sat, Aug 13, 2022 at 5:36 PM Yasuhiro Kimura wrote: > From: Yasuhiro Kimura > Subject: Updating EFI boot loader results in boot hangup > Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > > > I made regular update of my 14-CURREN

Re: Updating EFI boot loader results in boot hangup

From: Yasuhiro Kimura Subject: Updating EFI boot loader results in boot hangup Date: Sat, 13 Aug 2022 01:54:26 +0900 (JST) > I made regular update of my 14-CURRENT amd64 system from > main-n257134-a69c0964625 to main-n257316-9d16275c65b. I also updated > EFI boot loader (/boot/efi/efi/freebsd/loa

Re: Updating EFI boot loader results in boot hangup

On Sat, Aug 13, 2022 at 9:37 AM Nuno Teixeira wrote: > Hi Larry, > > boot off a memstick? >> > Yes, that's it. > With it we can mount efi partition and use bkp efi file by renaming it. > Yup. > I forgot that efi boot is restricted to use bootx64.efi (amd64) and my > though was looking for a co

Re: Updating EFI boot loader results in boot hangup

Hi Larry, boot off a memstick? > Yes, that's it. With it we can mount efi partition and use bkp efi file by renaming it. I forgot that efi boot is restricted to use bootx64.efi (amd64) and my though was looking for a command to load bootx64.efi.old avoiding use of a memstick (e.g.). I've tested i

Re: Updating EFI boot loader results in boot hangup

ike: > > --- > > mount -t msdosfs /dev/nvd0p1 /mnt > > cp /mnt/efi/boot/bootx64.efi /mnt/efi/boot/bootx64.old > > cp /boot/loader.efi /mnt/efi/boot/bootx64.efi > > --- > > > > I can't find the right docs to load bootx64.old. > > Could you tell me w

Re: Updating EFI boot loader results in boot hangup

From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 21:03:02 +0100 > I'm searching without success to load a bkp loader in case of boot failure. > > Upgrade process willl be like: > --- > mount -t msdosfs /dev/nvd0p1 /mn

Re: Updating EFI boot loader results in boot hangup

escreveu no dia sexta, 12/08/2022 à(s) 18:45: From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? No, you need not. The only time that I upda

Re: Updating EFI boot loader results in boot hangup

t; > Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) > 18:45: > > From: Nuno Teixeira > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Fri, 12 Aug 2022 18:26:11 +0100 > > > Hello Yasu, > > > > Does it needes to update boot loader e

Re: Updating EFI boot loader results in boot hangup

5: From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? No, you need not. The only time that I updated was a month ago because of zfs upgr

Re: Updating EFI boot loader results in boot hangup

ad bootx64.old. Could you tell me what you did to solve your boot? Thanks Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) 18:45: > From: Nuno Teixeira > Subject: Re: Updating EFI boot loader results in boot hangup > Date: Fri, 12 Aug 2022 18:26:11 +0100 > > > Hello Yas

Re: Updating EFI boot loader results in boot hangup

From: Nuno Teixeira Subject: Re: Updating EFI boot loader results in boot hangup Date: Fri, 12 Aug 2022 18:26:11 +0100 > Hello Yasu, > > Does it needes to update boot loader everytime that we upgrade current? No, you need not. > The only time that I updated was a month ago be

Re: Updating EFI boot loader results in boot hangup

Hello Yasu, Does it needes to update boot loader everytime that we upgrade current? The only time that I updated was a month ago because of zfs upgrade and I need to practice how to boot loader bkp file :) Cheers, Yasuhiro Kimura escreveu no dia sexta, 12/08/2022 à(s) 17:56: > Hello, > > I ma

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is > missing sw > IOW the line MUST read as: > /dev/gpt/Sea1-18noneswapsw 0 0 > or > /dev/gpt/Sea1-18noneswapsw,trimonce 0 0 > as appropriate for the media referenced.

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 2021-06-06 23:49, Graham Perrin wrote: On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of t

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of the original where

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> On 7 Jun 2021, at 02:15, Thomas Mueller wrote: > > I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took > 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be > successful with "dhclient re0". > > UPDATING file says to boot single-user aft

Re: Updating to FreeBSD-current, can't mount -uw /

On Sun, Jun 6, 2021 at 5:24 AM Thomas Mueller wrote: > I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld > took 11:15 (hours:minutes), buildkernel was also successful, I even > appeared to be successful with "dhclient re0". > > UPDATING file says to boot single-user after b

Re: Updating current i386 broke wlan0...

On Fri, 11 Dec 2020 13:55:14 -0800, Chris wrote: > On 2020-12-11 13:07, Jeffrey Bouquet wrote: > > On Fri, 11 Dec 2020 10:53:55 -0800, Chris wrote: > > > >> On 2020-12-11 10:32, Chris wrote: > >> > On 2020-12-11 08:10, Steve Kargl wrote: > >> >> On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeff

Re: Updating current i386 broke wlan0...

On Dec 11, 2020, at 1:55 PM, Chris wrote: > > Well FWIW when I've been confronted with the need to perform an "unorthodox" > upgrade > path. I always perform a > cd / && cp -rp /etc /eetc > *prior* to a mergemaster(8) > because you never know. ;-) Just commit every *working* set of files in /et

Re: Updating current i386 broke wlan0...

On 2020-12-11 13:07, Jeffrey Bouquet wrote: On Fri, 11 Dec 2020 10:53:55 -0800, Chris wrote: On 2020-12-11 10:32, Chris wrote: > On 2020-12-11 08:10, Steve Kargl wrote: >> On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: >>> Longtime BSD current user, due to several constraints

Re: Updating current i386 broke wlan0...

On Fri, 11 Dec 2020 10:53:55 -0800, Chris wrote: > On 2020-12-11 10:32, Chris wrote: > > On 2020-12-11 08:10, Steve Kargl wrote: > >> On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: > >>> Longtime BSD current user, due to several constraints I had to update > >>> from > >>>

Re: Updating current i386 broke wlan0...

On 2020-12-11 10:32, Chris wrote: On 2020-12-11 08:10, Steve Kargl wrote: On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: Longtime BSD current user, due to several constraints I had to update from a recent dec 10 image in a quasi-piecemeal fashion. Fixed all issues [ I think

Re: Updating current i386 broke wlan0...

On 2020-12-11 08:10, Steve Kargl wrote: On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: Longtime BSD current user, due to several constraints I had to update from a recent dec 10 image in a quasi-piecemeal fashion. Fixed all issues [ I think ] From 11-Current to 13-Current ex

Re: Updating current i386 broke rc* [not wlan0]...

On Fri, Dec 11, 2020 at 9:46 AM Bjoern A. Zeeb < bzeeb-li...@lists.zabbadoz.net> wrote: > On 11 Dec 2020, at 14:12, Jeffrey Bouquet wrote: > > > Longtime BSD current user, due to several constraints I had to update > > from a recent dec 10 image in > > a quasi-piecemeal fashion. Fixed all issues

Re: Updating current i386 broke rc* [not wlan0]...

On 11 Dec 2020, at 14:12, Jeffrey Bouquet wrote: Longtime BSD current user, due to several constraints I had to update from a recent dec 10 image in a quasi-piecemeal fashion. Fixed all issues [ I think ] From 11-Current to 13-Current except It seems you didn’t prorperly merge /etc; are yo

Re: Updating current i386 broke wlan0...

On Fri, 11 Dec 2020 08:10:37 -0800, Steve Kargl wrote: > On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: > > Longtime BSD current user, due to several constraints I had to update from > > a recent dec 10 image in > > a quasi-piecemeal fashion. Fixed all issues [ I think ]

Re: Updating current i386 broke wlan0...

On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: > Longtime BSD current user, due to several constraints I had to update from a > recent dec 10 image in > a quasi-piecemeal fashion. Fixed all issues [ I think ] From 11-Current to > 13-Current except > service netif onestart w

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 10:13:40AM -0800, Enji Cooper wrote: > > > PS: if anyone cares there are 3 patches sitting in freebsd-numerics@. > > Steve, > As some others noted in the private channel, you’ll need > to reset your Kerberos password via these instructions in the > committer’s guide:

Re: Updating bugzilla password?

> On Feb 4, 2019, at 10:07 AM, Steve Kargl > wrote: > > On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: >> >> >> Let me loop in some other folks. Something might be up with mail forwarding >> for your account. >> > > Just sent an email to ka...@freebsd.org. It was forwarded

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: > > > Let me loop in some other folks. Something might be up with mail forwarding > for your account. > Just sent an email to ka...@freebsd.org. It was forwarded to my local account as expected. Checking /var/log/maillog, I see no

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:35:45AM -0800, Enji Cooper wrote: > > > Was this for your old FreeBSD.org address, by chance? > Yes. ka...@freebsd.org .forward is set up to send the email on to my local hacking account. -- Steve _

Re: Updating bugzilla password?

> On Feb 4, 2019, at 9:35 AM, Enji Cooper wrote: > > > >> On Feb 4, 2019, at 9:24 AM, Steve Kargl > > wrote: >> >> On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: >>> On Feb 4, 2019, at 08:34, Steve Kargl >>>

Re: Updating bugzilla password?

> On Feb 4, 2019, at 9:24 AM, Steve Kargl > wrote: > > On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: >> >>> On Feb 4, 2019, at 08:34, Steve Kargl >>> wrote: >>> >>> I have forgotten my bugzilla account password. I've >>> entered the Login: account name, and clicked the >>>

Re: Updating bugzilla password?

On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: > > > On Feb 4, 2019, at 08:34, Steve Kargl > > wrote: > > > > I have forgotten my bugzilla account password. I've > > entered the Login: account name, and clicked the > > "Forgot Password" button. Expecting to receiving an > > ema

Re: Updating bugzilla password?

Hi! > > I have forgotten my bugzilla account password. I've > > entered the Login: account name, and clicked the > > "Forgot Password" button. > I'll file a bugzilla bug on your behalf in 10-20 mins. There's > a better mailing list for this kind of query.. it's just evading my mind. bugmei

Re: Updating bugzilla password?

> On Feb 4, 2019, at 08:34, Steve Kargl > wrote: > > I have forgotten my bugzilla account password. I've > entered the Login: account name, and clicked the > "Forgot Password" button. Expecting to receiving an > email that would provide instructions for updating > the password. That email n

Re: questions re updating to -CURRENT

> Maybe ... but this is one of those things that (in my > experience) either Just Work or Go Horribly Wrong. That's why I would go at least (latest) -RELEASE to -STABLE before going -STABLE to -CURRENT, if you must. Why trying your luck with big jumps? -- Sent from: http://freebsd.1045724.x6

Re: questions re updating to -CURRENT

Jakub Lach writes: > Are you sure you are not using drm2 already? I would check > with kldstat. Ckecked; it's there. > The message in UPDATING is about removing > old code from the tree. Maybe ... but this is one of those things that (in my experience) either Just Work or

Re: questions re updating to -CURRENT

I use 11-STABLE with Intel. Some time ago, there was a switch to drm2 here. Iirc I had to add kld_list="i915kms.ko to rc.conf and ensure that drm2/drm2 and drm2/i915kms are built (which should be default). Are you sure you are not using drm2 already? I would check with kldstat. The message in

questions re updating to -CURRENT

Hello: I finally get to update a system from: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 to -CURRENT. After reading src/UPDATING, I understand everything (I think) _except_: 20170311: The old drm (sys/dev/drm/) drivers for i915 and radeon hav

Fwd: Re: UPDATING revision and seperate edge-case question(s)

Sorry, sent it to this same email originally, on to the list... - Start Forwarded Message - Sent: Sat, 12 Mar 2016 17:33:31 -0800 (PST) From: "Jeffrey Bouquet" To: "jbtakk" Subject: Re: UPDATING revision and seperate edge-case question(s) Just for completeness,

Re: updating standard headers to meet c++11 standard

On 20/05/2014 21:26, David Chisnall wrote: > Hi, > > I thought I'd already fixed this a year or so ago. Looking at my system, I > see this in cdefs.h: > > /* C++11 exposes a load of C99 stuff */ > #if defined(__cplusplus) && __cplusplus >= 201103L > #define __LONG_LONG_SUPPORTED > #ifndef __STD

Re: updating standard headers to meet c++11 standard

Hi, I thought I'd already fixed this a year or so ago. Looking at my system, I see this in cdefs.h: /* C++11 exposes a load of C99 stuff */ #if defined(__cplusplus) && __cplusplus >= 201103L #define __LONG_LONG_SUPPORTED #ifndef __STDC_LIMIT_MACROS #define __STDC_LIMIT_MACROS #endif #ifndef __S

Re: Updating from 9.1-release to svn head: what might be the problem?

I've been using 10.0 current for a few months now with no problem. What I do know about virtual machines is that they don't share kernel resources too well. If both virtual machines are trying to access the kernel, there will be a problem. On Wed, Jun 19, 2013 at 10:51 PM, Alexey Dokuchaev wro

Re: Updating from 9.1-release to svn head: what might be the problem?

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" and standard make > wo

Re: updating ports to HEAD

El día Monday, April 01, 2013 a las 10:25:46PM -0700, Kevin Oberman escribió: > Good luck. I suspect a successful update of ptlib will be the real tricky > part. At least it gave me headaches back when I was using Ekiga. PTlib and opal are compiling fine directly from their SVN repositories; > A

Re: updating ports to HEAD

On Tue, Apr 2, 2013 at 8:03 AM, Matthias Apitz wrote: > El día Monday, April 01, 2013 a las 08:54:59PM -0700, Kevin Oberman escribió: > >> > Is there something in the base system of r235646 which would not allow >> > to do so, i.e. which is to old for HEAD of ports? >> > >> >> I'm not quite sure w

Re: updating ports to HEAD

On Mon, Apr 1, 2013 at 10:03 PM, Matthias Apitz wrote: > El día Monday, April 01, 2013 a las 08:54:59PM -0700, Kevin Oberman > escribió: > > > > Is there something in the base system of r235646 which would not allow > > > to do so, i.e. which is to old for HEAD of ports? > > > > > > > I'm not qui

Re: updating ports to HEAD

El día Monday, April 01, 2013 a las 08:54:59PM -0700, Kevin Oberman escribió: > > Is there something in the base system of r235646 which would not allow > > to do so, i.e. which is to old for HEAD of ports? > > > > I'm not quite sure what you mean by "update /usr/ports with SVN to HEAD", > since

Re: updating ports to HEAD

On Mon, Apr 1, 2013 at 7:46 AM, Matthias Apitz wrote: > > Hello, > > I have a FreeBSD 10-CURRENT as of: > > $ uname -a > FreeBSD aurora.Sisis.de 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r235646: Sat > May 19 15:52:36 CEST 2012 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC > i386 > > and I want t

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Wed, May 30, 2012 at 12:00:08PM -0400, John Baldwin wrote: > On Tuesday, May 29, 2012 7:17:01 pm Anton Shterenlikht wrote: > > On Mon, May 21, 2012 at 01:08:24PM -0400, John Baldwin wrote: > > > On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote: > > > > On Mon, May 21, 2012 at 09:42:17

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Tuesday, May 29, 2012 7:17:01 pm Anton Shterenlikht wrote: > On Mon, May 21, 2012 at 01:08:24PM -0400, John Baldwin wrote: > > On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote: > > > On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote: > > > > On Sun, May 20, 2012 at 09

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Wed, May 30, 2012 at 12:17:01AM +0100, Anton Shterenlikht wrote: > > > > I might have misled you on this, > > > > > > Yes, sorry, looking at the dmesg I sent you, > > > I obviously booted the patched kernel. > > > > > > So, no, 'hw.pci.enable_io_modes=0' in /boot/loader.conf > > > doesn't help

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Mon, May 21, 2012 at 01:08:24PM -0400, John Baldwin wrote: > On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote: > > On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote: > > > On Sun, May 20, 2012 at 09:54:51AM +0100, Anton Shterenlikht wrote: > > > > On Fri, May 18, 2012

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote: > On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote: > > On Sun, May 20, 2012 at 09:54:51AM +0100, Anton Shterenlikht wrote: > > > On Fri, May 18, 2012 at 10:48:52AM -0400, John Baldwin wrote: > > > > On Wednesday, May 16

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote: > On Sun, May 20, 2012 at 09:54:51AM +0100, Anton Shterenlikht wrote: > > On Fri, May 18, 2012 at 10:48:52AM -0400, John Baldwin wrote: > > > On Wednesday, May 16, 2012 11:30:19 am Anton Shterenlikht wrote: > > > > er.. yes, of cou

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Sun, May 20, 2012 at 09:54:51AM +0100, Anton Shterenlikht wrote: > On Fri, May 18, 2012 at 10:48:52AM -0400, John Baldwin wrote: > > On Wednesday, May 16, 2012 11:30:19 am Anton Shterenlikht wrote: > > > er.. yes, of course it helped. > > > > > > My problem was that I couldn't boot. > > > So, I

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Wednesday, May 16, 2012 11:30:19 am Anton Shterenlikht wrote: > er.. yes, of course it helped. > > My problem was that I couldn't boot. > So, I presumed the very existence of dmesg.boot > showed that your patches (both of them) work fine. > But, sorry, I could've been more explicit. > All seems

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Wed, May 16, 2012 at 11:08:05AM -0400, John Baldwin wrote: > On Wednesday, May 16, 2012 4:45:51 am Anton Shterenlikht wrote: > > On Tue, May 15, 2012 at 12:11:09PM -0400, John Baldwin wrote: > > > On Monday, May 07, 2012 5:25:02 pm Anton Shterenlikht wrote: > > > > On Mon, May 07, 2012 at 10:39:

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Wednesday, May 16, 2012 4:45:51 am Anton Shterenlikht wrote: > On Tue, May 15, 2012 at 12:11:09PM -0400, John Baldwin wrote: > > On Monday, May 07, 2012 5:25:02 pm Anton Shterenlikht wrote: > > > On Mon, May 07, 2012 at 10:39:51AM -0400, John Baldwin wrote: > > > > On Friday, May 04, 2012 4:07:2

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Monday, May 07, 2012 5:25:02 pm Anton Shterenlikht wrote: > On Mon, May 07, 2012 at 10:39:51AM -0400, John Baldwin wrote: > > On Friday, May 04, 2012 4:07:24 pm Anton Shterenlikht wrote: > > > On Fri, May 04, 2012 at 11:07:59AM -0400, John Baldwin wrote: > > > > On Friday, May 04, 2012 7:51:33 a

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Mon, May 07, 2012 at 10:39:51AM -0400, John Baldwin wrote: > On Friday, May 04, 2012 4:07:24 pm Anton Shterenlikht wrote: > > On Fri, May 04, 2012 at 11:07:59AM -0400, John Baldwin wrote: > > > On Friday, May 04, 2012 7:51:33 am Anton Shterenlikht wrote: > > > > On Thu, May 03, 2012 at 02:46:18P

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Friday, May 04, 2012 4:07:24 pm Anton Shterenlikht wrote: > On Fri, May 04, 2012 at 11:07:59AM -0400, John Baldwin wrote: > > On Friday, May 04, 2012 7:51:33 am Anton Shterenlikht wrote: > > > On Thu, May 03, 2012 at 02:46:18PM -0400, John Baldwin wrote: > > > > On Thursday, May 03, 2012 11:35:1

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Fri, May 04, 2012 at 11:07:59AM -0400, John Baldwin wrote: > On Friday, May 04, 2012 7:51:33 am Anton Shterenlikht wrote: > > On Thu, May 03, 2012 at 02:46:18PM -0400, John Baldwin wrote: > > > On Thursday, May 03, 2012 11:35:19 am Anton Shterenlikht wrote: > > > > On Tue, May 01, 2012 at 12:35:

Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

On Friday, May 04, 2012 7:51:33 am Anton Shterenlikht wrote: > On Thu, May 03, 2012 at 02:46:18PM -0400, John Baldwin wrote: > > On Thursday, May 03, 2012 11:35:19 am Anton Shterenlikht wrote: > > > On Tue, May 01, 2012 at 12:35:26PM +0100, Anton Shterenlikht wrote: > > > > On Mon, Apr 30, 2012 at

  1   2   >