OPNsense Forum
Archive => 16.1 Legacy Series => Topic started by: Clown on March 03, 2016, 04:46:56 pm
-
Is not booting on APU2 board, I'll get this in the console.
The "OPNsense-15.7.18-OpenSSL-serial-amd64.img" is working. What's the difference between this two installers?
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC" frequency 998149002 Hz quality 1000
Root mount waiting for: usbus1 usbus0
uhub0: 4 ports with 4 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen1.2: <vendor 0x0438> at usbus1
uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
uhub2: 4 ports with 4 removable, self powered
ugen0.2: <vendor 0x0457> at usbus0
umass0: <vendor 0x0457 product 0x0151, class 0/0, rev 2.00/1.00, addr 1> on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x8100
umass0:2:0:-1: Attached to scbus2
Trying to mount root from ufs:/dev/ufs/OPNsense_Install [ro,noatime]...
mountroot: waiting for device /dev/ufs/OPNsense_Install ...
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense_Install
vfs.root.mountfrom.options=ro,noatime
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/acd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
-
There's just the difference of FreeBSD 10.1 (15.7) and 10.2 (16.1).
FreeBSD 10.2 has been quite the surprise in terms of quality. We're expecting 10.3 to be better...
Does installing 15.7 and upgrading to 16.1 keep the APU2 happy?
-
Yes, upgrading from 15.7 to 16.1 works and the APU2 keeps to be happy ;-)
But as I'm switching between different Firewall distributions (testing) it's quit a bit painful.
-
This is the 15.7 installer Output:
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 10.1-RELEASE-p23 #0 a743323(stable/15.7): Sun Nov 1 01:40:07 CET 2015
root@sensey64:/usr/obj/usr/src/sys/SMP amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: AMD GX-412TC SOC (998.15-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x730f01 Family = 0x16 Model = 0x30 Stepping = 1
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x3ed8220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C>
AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
AMD Features2=0x1d4037ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,Topology,PNXC,DBE,PTSC,PL2I>
Structured Extended Features=0x8<BMI1>
TSC: P-state invariant, performance statistics
real memory = 4815060992 (4592 MB)
avail memory = 4090728448 (3901 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <CORE COREBOOT>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
random device not loaded; using insecure entropy
ioapic1: Changing APIC ID to 5
ioapic0 <Version 2.1> irqs 0-23 on motherboard
ioapic1 <Version 2.1> irqs 24-55 on motherboard
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff805f84a0, 0) error 1
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff805f8550, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff805f8600, 0) error 1
wlan: mac acl policy registered
random: <Software, Yarrow> initialized
kbd0 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xffffffff80f6e160, 0) error 19
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <CORE COREBOOT> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.2 on pci0
pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff
pci1: <ACPI PCI bus> on pcib1
igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> mem 0xfe600000-0xfe61ffff,0xfe620000-0xfe623fff at device 0.0 on pci1
igb0: Using MSIX interrupts with 5 vectors
igb0: Ethernet address: 00:0d:b9:41:08:24
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: Bound queue 2 to cpu 2
igb0: Bound queue 3 to cpu 3
pcib2: <ACPI PCI-PCI bridge> at device 2.3 on pci0
pci2: <ACPI PCI bus> on pcib2
igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x2000-0x201f mem 0xfe700000-0xfe71ffff,0xfe720000-0xfe723fff at device 0.0 on pci2
igb1: Using MSIX interrupts with 5 vectors
igb1: Ethernet address: 00:0d:b9:41:08:25
igb1: Bound queue 0 to cpu 0
igb1: Bound queue 1 to cpu 1
igb1: Bound queue 2 to cpu 2
igb1: Bound queue 3 to cpu 3
pcib3: <ACPI PCI-PCI bridge> at device 2.4 on pci0
pci3: <ACPI PCI bus> on pcib3
igb2: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x3000-0x301f mem 0xfe800000-0xfe81ffff,0xfe820000-0xfe823fff at device 0.0 on pci3
igb2: Using MSIX interrupts with 5 vectors
igb2: Ethernet address: 00:0d:b9:41:08:26
igb2: Bound queue 0 to cpu 0
igb2: Bound queue 1 to cpu 1
igb2: Bound queue 2 to cpu 2
igb2: Bound queue 3 to cpu 3
pci0: <encrypt/decrypt> at device 8.0 (no driver attached)
xhci0: <XHCI (generic) USB 3.0 controller> mem 0xfeb22000-0xfeb23fff at device 16.0 on pci0
xhci0: 32 byte context size.
usbus0 on xhci0
ahci0: <AMD Hudson-2 AHCI SATA controller> port 0x4010-0x4017,0x4020-0x4023,0x4018-0x401f,0x4024-0x4027,0x4000-0x400f mem 0xfeb25000-0xfeb253ff at device 17.0 on pci0
ahci0: AHCI v1.30 with 2 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfeb25400-0xfeb254ff at device 19.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
sdhci_pci0: <Generic SD HCI> mem 0xfeb25500-0xfeb255ff at device 20.7 on pci0
sdhci_pci0: 1 slot(s) allocated
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (115200,n,8,1)
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc0fff,0xef000-0xeffff on isa0
ppc0: cannot reserve I/O port range
uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
acpi_throttle2: <ACPI CPU Throttling> on cpu2
acpi_throttle2: failed to attach P_CNT
device_attach: acpi_throttle2 attach returned 6
acpi_throttle3: <ACPI CPU Throttling> on cpu3
acpi_throttle3: failed to attach P_CNT
device_attach: acpi_throttle3 attach returned 6
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
random: unblocking device.
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <0x1022> at usbus0
uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1: <AMD> at usbus1
uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <SATA SSD S9FM02.3> ATA-10 SATA 3.x device
ada0: Serial Number A1D407570FF100008020
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 15272MB (31277232 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC" frequency 998151347 Hz quality 1000
Root mount waiting for: usbus1 usbus0
uhub0: 4 ports with 4 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen1.2: <vendor 0x0438> at usbus1
uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
ugen0.2: <vendor 0x0457> at usbus0
umass0: <vendor 0x0457 USB Mass Storage Device, class 0/0, rev 2.00/1.00, addr 1> on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:2:0:-1: Attached to scbus2
da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
da0: <OCZ ET1208AD 1.0> Removable Direct Access SCSI-2 device
da0: Serial Number 64a7dd469a3668
da0: 40.000MB/s transfers
da0: 980MB (2007040 512 byte sectors: 64H 32S/T 980C)
da0: quirks=0x2<NO_6_BYTE>
uhub2: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/OPNsense_Install [ro,noatime]...
Mounting filesystems...
tunefs: soft updates set
tunefs: file system reloaded
camcontrol: subcommand "identify" requires a valid device identifier
-
I realise this is suboptimal, but I'm not sure what to do without a hands on session with the APU2 platform. It may as well be fixed in FreeBSD 10.3, but that is still a few months ahead, so even if fixed there we'd have to look and see what caused this and provide a backport of the fix in our 16.1 series.
Both dmesg dumps look ok, except for the former refusing to boot using the same layout. It may also be related to the good old cam boot delay setting...
https://github.com/rharmonson/richtech/wiki/Alix-APU1C4,-pfSense-2,-&-sdcard-boot-delay
-
Hello,
I had the same problem "...failed with error 19".
I think it's a problem with USB 3 and FreeBSD.
I've get arround by using the USB 2 internal connector to install opnsense. I guess it should work also with the card reader.
-
Another user also noted that APU2 requires a BIOS update to make it boot reliably with 16.1.
-
This is definitely not fixed. Why were the old images pulled when they're the only apparently bootable ones on this platform?
-
Hi there,
You'll have to be more specific.
Older images (16.1) are available from all mirrors, e.g.: http://mirror.wjcomms.co.uk/opnsense/releases/
15.x was outpaced too fast to keep the images around and since we're going to discontinue upgrade support next year for those who haven't upgraded for 2 years there isn't much reason to bring them back.
Images in general work well. Things to go over:
o Don't panic.
o Upgrade your BIOS.
o Name your hardware. Match it against bugs from FreeBSD over here: http://bugs.freebsd.org/bugzilla/
o Describe your problem in detail. Match it against bugs from FreeBSD over here: http://bugs.freebsd.org/bugzilla/
o We cannot possibly fix boot problems inside our GUI package.
o We provide gradual FreeBSD upgrades in the hopes that such issues will be overcome, but there's no guarantee.
o If there are issues with our build tools please review them and send us actionable intel on how to make them better *for everyone*: https://github.com/opnsense/tools
Cheers,
Franco
-
A workaround for USB-related issues exist, please test if it works for you:
https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USB
This workaround is not included in OPNsense by default. It will not work for all users, but would abuse all users with a boot delay.
Anyway if it works for you, you could persist this workaround in System->Settings->Tunables.
Regards
- Frank
-
Sorry I misread this. Thanks to fraenki for clearing this up. OPNsense should have a 17.1 has a fix for this already:
https://pkg.opnsense.org/snapshots/OPNsense-17.1.a-OpenSSL-serial-amd64.img.bz2
Relevant issue here:
https://github.com/opnsense/tools/issues/28
Cheers,
Franco
-
Yeah sorry we were on IRC in a different TZ. 17.1 installer works. How do I downgrade back to stable? Does stable have PIE (AQM)?
-
Thanks for confirming.
Stable has PIE for dummynet, but I think it's not hooked up to the traffic shaper GUI as of now (only CoDel because that came first).
Downgrade is discouraged, but as long as you don't manually compile third party software on the box this should work...
# opnsense-update -ur 16.7
# /usr/local/etc/rc.reboot
(reboots happening, back to stock 16.7)
(another upgrade to 16.7.7)
# opnsense-update -t opnsense
(switches back to stable from devel)
(reboot just to be safe)
-
# opnsense-update -ur 16.7
# /usr/local/etc/rc.reboot
Instantly destroyed my install, isn't even booting into the opnsense shell... While I get this seems humourous, can a 16.1 or 16.7 please be re-released with the backported patch so OPNsense is usable on any platform supporting USB3?
-
Hi guys!
Same issue here, I'm trying to install this baby on a brand-new APU2 board ;D but I'm using 16.7...
Edit: Ok, now I was able to boot by pressing ESC to get into the Boot prompt and there I typed:
set kern.cam.boot_delay="10000"
boot
But now it seems my 16 GB mSATA which is plugged in the first port is not recognized as install-destination? Only the USB Stick I am booting from....
BIOS is up to date (2016/03/07) The newer BIOS only adds PXEi funktionality (http://pcengines.ch/howto.htm#bios)
Any ideas?;D
Cheers
-
See Screenshot in attachment.
EDIT: Solved. Unbelievable what it was. I knew that mSATA and mPCIE are the same form factor but not compatible. But who would have guessed that on the APU2, those exactly IDENTICAL LOOKING ports are built next to each other >.<