Re: UEFI ISO boot not working in 12.1 ?
Oh, I didn't realize I updated a PXE boot PR. I am not PXE: I tested with real media in a Dell, and with Dell iDRAC virtualized media, and with USB. I absolutely represent a user who has h/w which I can reproducably show cannot load UEFI from true and virtualized local media, not PXE. And, this state has existed for some time. On Thu, Nov 7, 2019 at 10:21 AM Julian Elischer wrote: > > On 11/6/19 4:04 PM, George Michaelson wrote: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239876 is relevant maybe? > > I suspect a separate bug because the OP specified that it worked in > 12.0 where those bugs go back to 9.x > > Julian. > > > > > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote: > >> On 11/6/19 2:53 PM, Warner Losh wrote: > >>> On Wed, Nov 6, 2019 at 2:03 PM Chris Ross > >>> wrote: > >>> > On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: > > Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a > [...] > > I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? > More information. A stable/12 ISO that I built fails in the same way the > 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a > release > ISO, and it boots. So, something seems definately to have changed in the > way > the UEFI bits are on the boot ISOs? Or maybe a change in the loader? > Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. > > Let me know what to try next. > > >> You could try some bisection back along the 12 branch.. > >> > >> > >> ___ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
On 11/6/19 4:04 PM, George Michaelson wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239876 is relevant maybe? I suspect a separate bug because the OP specified that it worked in 12.0 where those bugs go back to 9.x Julian. On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote: On 11/6/19 2:53 PM, Warner Losh wrote: On Wed, Nov 6, 2019 at 2:03 PM Chris Ross wrote: On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a [...] I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? More information. A stable/12 ISO that I built fails in the same way the 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a release ISO, and it boots. So, something seems definately to have changed in the way the UEFI bits are on the boot ISOs? Or maybe a change in the loader? Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. Let me know what to try next. You could try some bisection back along the 12 branch.. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
No. That's netboot which is a different path in the loader. Warner On Wed, Nov 6, 2019, 5:04 PM George Michaelson wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239876 is relevant > maybe? > > On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote: > > > > On 11/6/19 2:53 PM, Warner Losh wrote: > > > On Wed, Nov 6, 2019 at 2:03 PM Chris Ross > wrote: > > > > > >> On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: > > >>> Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a > > >> [...] > > >>> I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? > > >> More information. A stable/12 ISO that I built fails in the same way > the > > >> 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a > release > > >> ISO, and it boots. So, something seems definately to have changed in > the > > >> way > > >> the UEFI bits are on the boot ISOs? Or maybe a change in the loader? > > >> Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. > > >> > > >> Let me know what to try next. > > >> > > You could try some bisection back along the 12 branch.. > > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239876 is relevant maybe? On Thu, Nov 7, 2019 at 9:46 AM Julian Elischer wrote: > > On 11/6/19 2:53 PM, Warner Losh wrote: > > On Wed, Nov 6, 2019 at 2:03 PM Chris Ross wrote: > > > >> On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: > >>> Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a > >> [...] > >>> I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? > >> More information. A stable/12 ISO that I built fails in the same way the > >> 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a release > >> ISO, and it boots. So, something seems definately to have changed in the > >> way > >> the UEFI bits are on the boot ISOs? Or maybe a change in the loader? > >> Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. > >> > >> Let me know what to try next. > >> > You could try some bisection back along the 12 branch.. > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
On 11/6/19 2:53 PM, Warner Losh wrote: On Wed, Nov 6, 2019 at 2:03 PM Chris Ross wrote: On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a [...] I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? More information. A stable/12 ISO that I built fails in the same way the 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a release ISO, and it boots. So, something seems definately to have changed in the way the UEFI bits are on the boot ISOs? Or maybe a change in the loader? Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. Let me know what to try next. You could try some bisection back along the 12 branch.. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Random system lockups with 12.1-STABLE r354241 amd64
On 11/6/19 2:58 PM, James Wright wrote: Hi, [...] Can anyone offer some advice as to how I can track down this issue? The first question which I couldn't see from your dmesg is "do you have ht krnel debugger configured into your kernel?" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Random system lockups with 12.1-STABLE r354241 amd64
Hi, Since upating to r354241 a few days ago I've been experiencing more frequent complete system lockups, with around 4 happening over the last couple of days. Prior to this I would get the occasional lockup, perhaps once a month on my laptop which is used daily. I'm finding it hard to determine the issue as it seems completely random, and the only course of action left open once it occurs is to hard power down the machine, which *always* seems to lead to filesystem inconsistencies upon restarting, (the file system is UFS with SU+J). Can anyone offer some advice as to how I can track down this issue? # uname -a FreeBSD macbook 12.1-STABLE FreeBSD 12.1-STABLE r354241 GENERIC amd64 # dmesg ---<>--- Copyright (c) 1992-2019 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.1-STABLE r354241 GENERIC amd64 FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1) VT(efifb): resolution 1440x900 CPU: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz (2200.05-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306d4 Family=0x6 Model=0x3d Stepping=4 Features=0xbfebfbff Features2=0x7ffafbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21c2fbb Structured Extended Features3=0x9c000400 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8154464256 (7776 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads random: unblocking device. ioapic0 irqs 0-39 on motherboard Launching APs: 1 2 3 Timecounter "TSC-low" frequency 1100025386 Hz quality 1000 random: entropy device external interface kbd0 at kbdmux0 000.23 [4336] netmap_init netmap: loaded module [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0x81131fa0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 efirtc0: on motherboard efirtc0: registered as a time-of-day clock, resolution 1.00s cryptosoft0: on motherboard acpi0: on motherboard acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) hpet0: iomem 0xfed0-0xfed03fff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 cpu0: on acpi0 atrtc0: port 0x70-0x77 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.00s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x3000-0x303f mem 0xc000-0xc0ff,0xb000-0xbfff at device 2.0 on pci0 vgapci0: Boot video device hdac0: mem 0xc161-0xc1613fff at device 3.0 on pci0 xhci0: mem 0xc160-0xc160 at device 20.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA xhci0: Port routing mask set to 0x usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 pci0: at device 22.0 (no driver attached) hdac1: mem 0xc1614000-0xc1617fff at device 27.0 on pci0 pcib1: at device 28.0 on pci0 pci1: on pcib1 pcib2: at device 28.1 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) pcib3: at device 28.2 on pci0 pci3: on pcib3 pci3: at device 0.0 (no driver attached) pcib4: at device 28.4 on pci0 pci4: on pcib4 pcib5: at device 28.5 on pci0 pci5: on pcib5 ahci0: mem 0xc130-0xc1301fff at device 0.0 on pci5 ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 isab0: at device 31.0 on pci0 isa0: on isab0 battery0: on acpi0 acpi_acad0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 asmc0: port 0x300-0x31f iomem 0xfef0-0xfef0 irq 6 on acpi0 uart0: <8250 or 16450 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0 uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. coretemp0: on cpu0 est0: on cpu0 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 3 on hdaa0 hdacc1: at cad 0 on hdac1 hdaa1: at nid 1 on hdacc1 pcm1: at nid 18,16 and 24 on hdaa1 ugen0.1: <0x8086 XHCI root HUB> at usbus0 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr
Re: UEFI ISO boot not working in 12.1 ?
On Wed, Nov 6, 2019 at 2:03 PM Chris Ross wrote: > On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: > > > > Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a > system > > here, which didn't work, and I found that > FreeBSD-12.0-RELEASE-amd64-disc1.iso > > did work on that same system. [Systems were configured to boot in UEFI > mode] > > > > And continues on from there. However, the attempt to boot 12.1-RELEASE > > never loads the loader and allows it to boot. The console output > > for 12.1-RELEASE is below. Can anyone help me figure out if it's > something > > I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? > > More information. A stable/12 ISO that I built fails in the same way the > 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a release > ISO, and it boots. So, something seems definately to have changed in the > way > the UEFI bits are on the boot ISOs? Or maybe a change in the loader? > Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. > > Let me know what to try next. > 99% sure it's a change in the loader. Do you have an easy way to put loader.efi into a 12.0 ISO? Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cisco 12G SAS RAID support ?
On Tue, Nov 05, 2019 at 05:04:41PM -0500, Chris Ross wrote: > > However, if you've already placed > > mpr_load="YES" in your /etc/loader.conf and rebooted your device, then you > > probably need to move into a diagnostic phase. > > Yeah. I think I see what PCI id is missing in the driver, after digging > around in the sources. I was just hoping it was a process/human error. > I'll get another machine running a build, and see if I can stub it in. Okay. Well, the simple try didn't magically work. I added a few lines in dev/mpr/mpr_pci.c in releng/12.0, built a new ISO, and booted. Now it recognizes the part, but says the following: pcib7: [...] pci7: numa-domain 0 on pcib7 mpr0: port 0x7000-0x70ff mem 0xb800-0xb80f,0xb7f0-0xb7ff,0xb7e0-0xb7ef at device 0.0 numa-domain 0 on pci7 mpr0: IOC in fault state 0x0, resetting mpr0: IOC in fault state 0x0, resetting mpr0: IOC in fault state 0x0, resetting mpr0: IOC in fault state 0x0, resetting mpr0: IOC in fault state 0x0, resetting mpr0: IOC in fault state 0x0, resetting There is about a 4 second pause between each of the "in fault state, resetting" lines. This may not be a freebsd-stable converstion any longer. I'm going to switch over to freebsd-drivers, unless someone has a suggestion of a better list for trying to figure out if small adjustments can be made to the mpr driver to accept this device. Thanks all. - Chris ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
On Wed, Nov 06, 2019 at 02:17:11PM -0500, Chris Ross wrote: > > Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system > here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso > did work on that same system. [Systems were configured to boot in UEFI mode] > > And continues on from there. However, the attempt to boot 12.1-RELEASE > never loads the loader and allows it to boot. The console output > for 12.1-RELEASE is below. Can anyone help me figure out if it's something > I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? More information. A stable/12 ISO that I built fails in the same way the 12.1-RELEASE ISO did. But, I just grabbed releng/12.0, and built a release ISO, and it boots. So, something seems definately to have changed in the way the UEFI bits are on the boot ISOs? Or maybe a change in the loader? Is okay in releng/12.0, but broken in 12.1-RELEASE and stable/12. Let me know what to try next. - Chris ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: UEFI ISO boot not working in 12.1 ?
On Wed, 6 Nov 2019 14:17:11 -0500 Chris Ross cross+free...@distal.com said Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso did work on that same system. Another [older] system I had was working with FreeBSD-12.1-RELEASE-amd64-disc1.iso, but after I had reason to change that older system to UEFI boot mode, I found it also would not boot the 12.1 ISO any longer A successul UEFI boot of 12.0-RELEASE-amd64-disc1 shows many lines of EFI information to the console, and nearing the bottom: BootOrder: 0001 0002 0003 0004[*] BootInfo Path: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) BootInfo Path: VenHw(,) Ignoring Boot0004: No Media Path Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3) Setting currdev to cd3: - And, that last line is a spinning cursor, after which becomes: Loading /boot/defaults/loader.conf And continues on from there. However, the attempt to boot 12.1-RELEASE never loads the loader and allows it to boot. The console output for 12.1-RELEASE is below. Can anyone help me figure out if it's something I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? The 12.1-RELEASE shows the same as above until starting with "Trying ESP": Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) Setting currdev to cd4: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x1) Setting currdev to cd0: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x2) Setting currdev to cd1: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3) Setting currdev to cd2: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x0) Setting currdev to cd3: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x4) Setting currdev to cd5: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x5) Setting currdev to cd6: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x6) Setting currdev to cd7: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x7) Setting currdev to cd8: Failed to bind bootable partition press any key to interrupt reboot in 5 seconds Let me know why 12.1-RELEASE is not behaving the same way on my systems... Thank you. - Chris Not trying to hijack this thread, But on a similar note; Wile I'm able to boot/install from them. None of the October (12.1) install images will produce a bootable install. So I'm stuck on RELENG-12. This is on a Core 13 second gen. IOW my problem is the inverse of yours. --Chris ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
UEFI ISO boot not working in 12.1 ?
Hi there. I tried booting FreeBSD-12.1-RELEASE-amd64-disc1.iso on a system here, which didn't work, and I found that FreeBSD-12.0-RELEASE-amd64-disc1.iso did work on that same system. Another [older] system I had was working with FreeBSD-12.1-RELEASE-amd64-disc1.iso, but after I had reason to change that older system to UEFI boot mode, I found it also would not boot the 12.1 ISO any longer A successul UEFI boot of 12.0-RELEASE-amd64-disc1 shows many lines of EFI information to the console, and nearing the bottom: BootOrder: 0001 0002 0003 0004[*] BootInfo Path: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) BootInfo Path: VenHw(,) Ignoring Boot0004: No Media Path Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3) Setting currdev to cd3: - And, that last line is a spinning cursor, after which becomes: Loading /boot/defaults/loader.conf And continues on from there. However, the attempt to boot 12.1-RELEASE never loads the loader and allows it to boot. The console output for 12.1-RELEASE is below. Can anyone help me figure out if it's something I need to do? How has 12.1 changed w.r.t. 12.0 for UEFI? The 12.1-RELEASE shows the same as above until starting with "Trying ESP": Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) Setting currdev to cd4: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x1) Setting currdev to cd0: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x2) Setting currdev to cd1: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3) Setting currdev to cd2: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x0) Setting currdev to cd3: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x4) Setting currdev to cd5: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x5) Setting currdev to cd6: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x6) Setting currdev to cd7: Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x7) Setting currdev to cd8: Failed to bind bootable partition press any key to interrupt reboot in 5 seconds Let me know why 12.1-RELEASE is not behaving the same way on my systems... Thank you. - Chris ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.1-RELEASE schedule update
On 2019-11-02 19:31, Glen Barber wrote:
On Sat, Nov 02, 2019 at 12:14:05PM -0600, Warner Losh wrote:
On Sat, Nov 2, 2019 at 10:20 AM Glen Barber wrote:
On Sat, Nov 02, 2019 at 02:12:50PM +, Sergey A. Osokin wrote:
On Fri, Nov 01, 2019 at 02:52:50PM +, Glen Barber wrote:
On Fri, Nov 01, 2019 at 01:44:18PM +, Sergey A. Osokin wrote:
At the moment we have graphics/drm-fbsd12.0-kmod port for 12.0.
I hope in most cases it's enough for RELENG_12 branch, however
just to avoid a potential confusion I see the following options
we can do:
- create a new port for 12.1 only
- rename the existing port to drm-fbsd12-kmod
- rename the existing port to drm-fbsd12.1-kmod (in case of 12.0 EoL)
What about using the meta-port and keying off of OSVERSION?
(Personally
I have no real preference either way, nor with any of the solutions you
propose above.)
Actually we have one, graphics/drm-kmod, and it depends on the following
one:
.elif ${OSVERSION} >= 1200058 && ${OSVERSION} < 130
RUN_DEPENDS=${KMODDIR}/drm.ko:graphics/drm-fbsd12.0-kmod
...
So, in case we don't expect an API/ABI changes in 12.x branch we can
just rename it to drm-fbsd12-kmod, or create a specific version of
the port for 12.1 - drm-fbsd12.1-kmod and update the meta-port as well.
We should never expect this type of ABI/KBI breakage along a stable
branch. (That is our definition of "stable", technically, but sometimes
there are unexpected breakages that occasionally go undetected.)
The KPIs that drm depends on are quite specific and weird and aren't part
of the set we guarantee (and we can't do what drm needs to do with only the
'safe' ones). It's not much different than virtual box which also has this
issue frequently because it too falls into that category.
Agreed. (FWIW, I specifically made sure the virtualbox-ose-additions
did not cause system crashes for 12.1.)
Also, since this is repeatable thing for every upcoming release
we can add this point to the check list and release scheduling.
Yes, good idea. Just let us know how you want to proceed, and we can
add a note to the documentation.
I mean I believe we should that (create a new port, update the meta-port,
etc.) in advance, in the beginning of the first phase of release cycle.
This seems like a reasonable approach.
How do we get packages from the new port into the release so that users
don't install the 12.0 port by mistake?
It just needs to be merged to the 2019Q4 ports branch. For the package
available on the dvd, it is unfortunately too late, but only the
graphics/drm-legacy-kmod and graphics/drm-stable-kmod packages are on
the dvd by default anyway. In other words, the meta-port is not
included, but once a commit is merged to the 2019Q4 branch and the
upstream binary packages are rebuilt, they will be available by default.
Please note that just creating a separate package for FreeBSD 12.1 (in
this case) does not solve the issue. drm-fbsd12.0-kmod builds and works
fine on FreeBSD 12.1, the issue is that the version built on 12.0 does
not work on 12.1.
Since packages for 12.1 are built on 12.0, just having a separate
package would not work in any case.
Regards
--
Niclas Zeising
FreeBSD Graphics Team
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
