Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

Running these commands makes the boot menu show up, and then takes me to the BSD installer! Med vänlig hälsning/Best Regards Linus Sundqvist System Engineer, Loopia AB On 04/07/18 16:50, Toomas Soome wrote: > set currdev=cd1: > include /boot/loader.rc > > This should give menu/boot. > > Rgds,

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

Could you check, show currdev from OK prompt before setting it. Somehow the boot device path is shown but we fail to recognize it (as seen by error message). However, the lsdev -v does show the path, so the efipart.c seems to do its work correctly. I feel, there should be some corner case in

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

Here's the output, variable 'currdev' not found: https://imgur.com/LlBygfr And to answer Rodneys question from before, this is the emulated CD drive from a Dell iDRAC (remote console thingy). Med vänlig hälsning/Best Regards Linus Sundqvist System Engineer, Loopia AB On 05/07/18 09:17, Toomas

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

> On 5 Jul 2018, at 10:28, Linus Sundqvist wrote: > > Here's the output, variable 'currdev' not found: > https://imgur.com/LlBygfr Yes indeed, as you got the error, so the variable was not set at all. My suggestion would be to walk over the code in main.c, and to

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

I have no idea how to do that or where to begin, but if anyone would like to assist with those steps I'll gladly run commands or a test ISO on one of our Dell servers. Med vänlig hälsning/Best Regards Linus Sundqvist System Engineer, Loopia AB On 05/07/18 10:23, Toomas Soome wrote: > > >> On

EFI booting from external USB pen drive

Hi, while I can boot memstick images just fine (which are created using makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I am not able to get anything that boots. On a Thinkpad (secure boot is off) from the “boot device chooser from ‘BIOS’” I get a quick blank screen and

Re: em0 link fail

On 07/05/18 09:27, tech-lists wrote: > On 03/07/2018 19:47, Michael Butler wrote: >> That would've been .. >> >> Jun  1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: Fri Jun >> 1 08:25:58 EDT 2018 >> >> I'm going to build one with SVN r334862 reverted to see if that works, > > Hi, > >

Re: em0 link fail

On 03/07/2018 19:47, Michael Butler wrote: That would've been .. Jun 1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: Fri Jun 1 08:25:58 EDT 2018 I'm going to build one with SVN r334862 reverted to see if that works, Hi, Is it working now? Am asking because a system I'd like to

Re: EFI booting from external USB pen drive

On 2018-07-05 16:30, Bjoern A. Zeeb wrote: Hi, while I can boot memstick images just fine (which are created using makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I am not able to get anything that boots. What is the size for the fat12 partition ? Everything over ~30MB

Re: EFI booting from external USB pen drive

Bjoern, I had this problem earlier this week while using FreeBSD-12.0-CURRENT-amd64-20180628-r335760-memstick.img on my ThinkPad P50. I had used `dd` to place the img file on a partition (e.g. /dev/sdb1) of the USB pen drive and it wouldn't boot properly. After I used `dd` to place the img on

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

> Here's the output, variable 'currdev' not found: > https://imgur.com/LlBygfr Hum, currdev didnt get set, but I see the loaddevice looks to be cd1: Toomas is right, we have an edge case here that is failing to set currdev properly. > > And to answer Rodneys question from before, this is the

Re: EFI booting from external USB pen drive

FAT12 isn't good for UEFI. Use FAT16 or FAT32. Warner On Thu, Jul 5, 2018, 9:32 AM Bjoern A. Zeeb wrote: > Hi, > > while I can boot memstick images just fine (which are created using > makefs/mkimg), doing the same thing using gpart/newfs_msdos -F 12/.. I > am not able to get anything that

Re: atomic changes break drm-next-kmod?

On 7/3/18 5:10 PM, Pete Wright wrote: > > > On 07/03/2018 15:56, John Baldwin wrote: >> On 7/3/18 3:34 PM, Pete Wright wrote: >>> >>> On 07/03/2018 15:29, John Baldwin wrote: That seems like kgdb is looking at the wrong CPU. Can you use 'info threads' and look for threads not stopped

SVN r336011 breaks build

As below: Building /usr/obj/usr/src/amd64.amd64/usr.sbin/config/config.c Building /usr/obj/usr/src/amd64.amd64/usr.sbin/config/lang.c Building /usr/obj/usr/src/amd64.amd64/usr.sbin/config/kernconf.c Building /usr/obj/usr/src/amd64.amd64/usr.sbin/config/config.o Building

Re: svn commit: r336012 - in head: . usr.sbin/config [ broken for ci.freebsd.org's FreeBSD-head-{sparc64,powerpcspe,powerpc,i386,armv7}-build

Examples: https://ci.freebsd.org/job/FreeBSD-head-armv7-build/568/console shows: 18:54:11 --- _bootstrap-tools-usr.sbin/config --- 18:54:11 mkmakefile.o: In function `dump_nvlist': 18:54:11 /usr/src/usr.sbin/config/mkmakefile.c:287: undefined reference to `cnvlist_get_string' 18:54:11

Re: atomic changes break drm-next-kmod?

On 07/05/18 20:59, Hans Petter Selasky wrote: On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: On 07/03/2018 15:29, John Baldwin wrote: That

Re: atomic changes break drm-next-kmod?

On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: > On 07/05/18 20:59, Hans Petter Selasky wrote: > > On 07/05/18 19:48, Pete Wright wrote: > >> > >> > >> On 07/05/2018 10:10, John Baldwin wrote: > >>> On 7/3/18 5:10 PM, Pete Wright wrote: > > On 07/03/2018 15:56, John

Re: EFI booting from external USB pen drive

On 5 Jul 2018, at 17:19, Warner Losh wrote: FAT12 isn't good for UEFI. Use FAT16 or FAT32. We use it for the default image we built and the wiki suggests it as well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI I wonder where this “default” came from? /bz

Re: svn commit: r336002 - in head: usr.bin/netstat usr.sbin/tcpdrop [ as-of -r336013: still broken: ci.freebsd.org FreeBSD-head-{mips,powerpc,powerpcspe}-build

> Author: brooks > Date: Thu Jul 5 17:02:10 2018 > New Revision: 336002 > URL: > https://svnweb.freebsd.org/changeset/base/336002 > > > Log: > Work around lame warnings in ancient gcc on 32-bit platforms. > > Fixes r335979. [The below are the gcc 4.2.1 based 32-bit architectures.]

Re: atomic changes break drm-next-kmod?

On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: On 07/03/2018 15:29, John Baldwin wrote: That seems like kgdb is looking at the wrong CPU. Can you use 'info threads' and look for

Re: EFI booting from external USB pen drive

[ Charset UTF-8 unsupported, converting... ] > On 5 Jul 2018, at 17:19, Warner Losh wrote: > > > FAT12 isn't good for UEFI. Use FAT16 or FAT32. > > We use it for the default image we built and the wiki suggests it as > well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI IIRC FreeBSD

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

I think I know what is going on... I may have some changes that fixes this. Warner On Thu, Jul 5, 2018, 9:12 AM Linus Sundqvist wrote: > I have no idea how to do that or where to begin, but if anyone would like > to assist with those steps I'll gladly run commands or a test ISO on one of > our

Re: atomic changes break drm-next-kmod?

On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: On 07/03/2018 15:29, John Baldwin wrote: That seems like kgdb is looking at the wrong CPU. 

Re: EFI booting from external USB pen drive

On Thu, Jul 5, 2018, 12:55 PM Bjoern A. Zeeb wrote: > On 5 Jul 2018, at 17:19, Warner Losh wrote: > > > FAT12 isn't good for UEFI. Use FAT16 or FAT32. > > We use it for the default image we built and the wiki suggests it as > well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI > > I

Re: atomic changes break drm-next-kmod?

On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky wrote: >>> On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: > On 7/3/18 5:10 PM, Pete

Re: EFI booting from external USB pen drive

On Thu, Jul 5, 2018 at 3:31 PM, Bjoern A. Zeeb < bzeeb-li...@lists.zabbadoz.net> wrote: > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: > > [ Charset UTF-8 unsupported, converting... ] >> >>> On 5 Jul 2018, at 17:19, Warner Losh wrote: >>> >>> FAT12 isn't good for UEFI. Use FAT16 or FAT32.

ci.freebsd.org's FreeBSD-head-i386-testvm fails for: pkg: No packages available to install matching 'scapy' have been found in the repositories

https://ci.freebsd.org/job/FreeBSD-head-i386-testvm/6978/console shows: 22:34:39 All repositories are up to date. 22:34:39 + sudo chroot ufs pkg install -y kyua perl5 scapy ksh93 python 22:34:39 Updating FreeBSD repository catalogue... 22:34:39 FreeBSD repository is up to date. 22:34:39 All

Re: EFI booting from external USB pen drive

On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: [ Charset UTF-8 unsupported, converting... ] On 5 Jul 2018, at 17:19, Warner Losh wrote: FAT12 isn't good for UEFI. Use FAT16 or FAT32. We use it for the default image we built and the wiki suggests it as well at

Re: atomic changes break drm-next-kmod?

On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin wrote: > On 7/5/18 12:36 PM, Konstantin Belousov wrote: > > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: > >> On 07/05/18 20:59, Hans Petter Selasky wrote: > >>> On 07/05/18 19:48, Pete Wright wrote: > > > On

Re: EFI booting from external USB pen drive

> On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: > > > [ Charset UTF-8 unsupported, converting... ] > >> On 5 Jul 2018, at 17:19, Warner Losh wrote: > >> > >>> FAT12 isn't good for UEFI. Use FAT16 or FAT32. > >> > >> We use it for the default image we built and the wiki suggests it as > >> well

Re: atomic changes break drm-next-kmod?

On 07/05/2018 12:12, Hans Petter Selasky wrote: On 07/05/18 20:59, Hans Petter Selasky wrote: On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright

Re: EFI booting from external USB pen drive

On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: > > > > > [ Charset UTF-8 unsupported, converting... ] > > >> On 5 Jul 2018, at 17:19, Warner Losh wrote: > > >> > > >>> FAT12 isn't good for UEFI.