2.4.4 memstick serial usb wont boot on a c3558

ozlecz

this is whats on the bios for the console redirection menu

A2

Version 2.19.1266. Copyright (C) 2018 American Megatrends, Inc.
BIOS Date: 07/02/2018 17:40:40 Ver: 10404T10
Press <DEL> or <ESC> to enter setup.
Entering Setup...

                                                                         A9
   Aptio Setup Utility - Copyright (C) 2018 American Megatrends, Inc.
      Advanced

/----------------------------------------------------+-------------------------
| |Legacy Console |
| COM1 |Redirection Settings |
| Console Redirection [Enabled] | |
|> Console Redirection Settings | |
| | |
| Legacy Console Redirection | |
|> Legacy Console Redirection Settings | |
| | |
| | |
| |-------------------------|
| |><: Select Screen |
| |^v: Select Item |
| |Enter: Select |
| |+/-: Change Opt. |
| |F1: General Help |
| |F2: Previous Values |
| |F3: Optimized Defaults |
| |F4: Save & Exit |
| |ESC: Exit |
----------------------------------------------------+-------------------------/
Version 2.19.1266. Copyright (C) 2018 American Megatrends, Inc.

ozlecz

and this are the settings on the legacy redirection

A2

Version 2.19.1266. Copyright (C) 2018 American Megatrends, Inc.
BIOS Date: 07/02/2018 17:40:40 Ver: 10404T10
Press <DEL> or <ESC> to enter setup.
Entering Setup...

                                                                         A9
   Aptio Setup Utility - Copyright (C) 2018 American Megatrends, Inc.
      Advanced

/----------------------------------------------------+-------------------------
|
|
|
|
|
|
|
|
|
/> |
|
|
|
|
|
|
|
|
/>

ozlecz

BTW I just got a reply from the supplier

"our console port is initialled to com2 (ttyu1), do you think it maight cause problem during installation?"

So this explains why the ADI image goes thru all the way until it reached the mounting prob. (which i guess is due to the image is not right)

Does it mean also that the serial image is using com1? If so then how to configure that?

Thanks again

stephenw10

Ah interesting. What mount problem do you see exactly using the ADI image?

Is that whilst booting the installer or the resulting install?

Com1 is probably on some internal header you could use just to get past the install.

You could also try installing on something else and moving the drive but it would need to have ix NICs to boot fully in the C3K.

Steve

ozlecz

this is the full txt of the ADI image booting

/boot/kernel/kernel text=0x17bf9f0 data=0xb93c38+0x517b18 syms=[0x8+0x197280+0x8+0x197de9]
Booting...
Start @ 0xffffffff8031a000 ...
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2018 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 11.2-RELEASE-p3 #17 e6b497fa0a3(RELENG_2_4_4): Thu Sep 20 09:04:45 EDT 2018
    root@buildbot3:/crossbuild/ce-244/obj/amd64/WvDslnYb/crossbuild/ce-244/pfSense/tmp/FreeBSD-src/sys/pfSense amd64
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz (2200.07-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x506f1  Family=0x6  Model=0x5f  Stepping=1
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x101<LAHF,Prefetch>
  Structured Extended Features=0x2294e283<FSGSBASE,TSCADJ,SMEP,ERMS,NFPUSG,MPX,PQE,RDSEED,SMAP,CLFLUSHOPT,PROCTRACE,SHA>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8187498496 (7808 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <INTEL  TIANO   >
WARNING: L1 data cache covers less APIC IDs than a core
0 < 1
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
ioapic0 <Version 2.0> irqs 0-23 on motherboard
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC-low" frequency 1100035819 Hz quality 1000
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
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, 0xffffffff80680430, 0) error 1
random: entropy device external interface
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
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, 0xffffffff806804e0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
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, 0xffffffff80680590, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a7460, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a7510, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a75c0, 0) error 1
wlan: mac acl policy registered
hn: tranparent VF mode, if_transmit will be used, instead of if_start
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff81209800, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I > 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
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 24000000 Hz quality 950
Event timer "HPET" frequency 24000000 Hz quality 550
Event timer "HPET1" frequency 24000000 Hz quality 440
Event timer "HPET2" frequency 24000000 Hz quality 440
Event timer "HPET3" frequency 24000000 Hz quality 440
Event timer "HPET4" frequency 24000000 Hz quality 440
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 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: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <processor> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> mem 0xdff20000-0xdff3ffff irq 16 at device 9.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> mem 0xdff00000-0xdff1ffff irq 21 at device 15.0 on pci0
pci3: <ACPI PCI bus> on pcib3
ahci0: <Intel Denverton AHCI SATA controller> port 0xf090-0xf097,0xf080-0xf083,0xf040-0xf05f mem 0xdff56000-0xdff57fff,0xdff5f000-0xdff5f0ff,0xdff5e000-0xdff5e7ff irq 20 at device 19.0 on pci0
ahci0: AHCI v1.31 with 1 6Gbps ports, Port Multiplier supported
ahcich7: <AHCI channel> at channel 7 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
ahci1: <Intel Denverton AHCI SATA controller> port 0xf070-0xf077,0xf060-0xf063,0xf020-0xf03f mem 0xdff54000-0xdff55fff,0xdff5d000-0xdff5d0ff,0xdff5c000-0xdff5c7ff irq 21 at device 20.0 on pci0
ahci1: AHCI v1.31 with 2 6Gbps ports, Port Multiplier supported
ahcich9: <AHCI channel> at channel 1 on ahci1
ahcich13: <AHCI channel> at channel 5 on ahci1
ahciem1: <AHCI enclosure management bridge> on ahci1
xhci0: <Intel Denverton USB 3.0 controller> mem 0xdff40000-0xdff4ffff irq 19 at device 21.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 22.0 on pci0
pci4: <ACPI PCI bus> on pcib4
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdf800000-0xdf9fffff,0xdfa04000-0xdfa07fff irq 16 at device 0.0 on pci4
ix0: Using MSI-X interrupts with 5 vectors
ix0: Ethernet address: 20:18:10:40:07:00
ix0: netmap queues/slots: TX 4/2048, RX 4/2048
ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdf600000-0xdf7fffff,0xdfa00000-0xdfa03fff irq 17 at device 0.1 on pci4
ix1: Using MSI-X interrupts with 5 vectors
ix1: Ethernet address: 20:18:10:40:07:01
ix1: netmap queues/slots: TX 4/2048, RX 4/2048
pcib5: <ACPI PCI-PCI bridge> at device 23.0 on pci0
pci5: <ACPI PCI bus> on pcib5
ix2: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdf200000-0xdf3fffff,0xdf404000-0xdf407fff at device 0.0 on pci5
ix2: Using MSI-X interrupts with 5 vectors
ix2: Ethernet address: 20:18:10:40:07:02
ix2: netmap queues/slots: TX 4/2048, RX 4/2048
ix3: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xdf000000-0xdf1fffff,0xdf400000-0xdf403fff at device 0.1 on pci5
ix3: Using MSI-X interrupts with 5 vectors
ix3: Ethernet address: 20:18:10:40:07:03
ix3: netmap queues/slots: TX 4/2048, RX 4/2048
pci0: <simple comms> at device 24.0 (no driver attached)
sdhci_pci0: <Intel Denverton eMMC 5.0 Controller> mem 0xdff5a000-0xdff5afff,0xdff59000-0xdff59fff irq 16 at device 28.0 on pci0
sdhci_pci0: 1 slot(s) allocated
mmc0: <MMC/SD bus> on sdhci_pci0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
pci0: <memory> at device 31.2 (no driver attached)
pci0: <serial bus> at device 31.5 (no driver attached)
acpi_tz0: <Thermal Zone> on acpi0
uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 11 on acpi0
uart1: <Non-standard ns8250 class UART with FIFOs> port 0x2f8-0x2ff irq 10 flags 0x10 on acpi0
uart1: console (115200,n,8,1)
uart2: <Non-standard ns8250 class UART with FIFOs> port 0x3e8-0x3ef irq 6 on acpi0
ppc0: cannot reserve I/O port range
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 221400001600
device_attach: est0 attach returned 6
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 221400001600
device_attach: est1 attach returned 6
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 221400001600
device_attach: est2 attach returned 6
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 221400001600
device_attach: est3 attach returned 6
Timecounters tick every 1.000 msec
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
mmc0: No compatible cards found on bus
uhub0: 8 ports with 8 removable, self powered
ugen0.2: <Generic Mass Storage> at usbus0
umass0 on uhub0
umass0: <Generic Mass Storage, class 0/0, rev 2.00/1.00, addr 1> on usbus0
ses0 at ahciem0 bus 0 scbus1 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
ses1 at ahciem1 bus 0 scbus4 target 0 lun 0
ses1: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses1: SEMB SES Device
ada0 at ahcich7 bus 0 scbus0 target 0 lun 0
ada0: <WDC WDS120G2G0A-00JH30 UE450000> ACS-2 ATA SATA 3.x device
ada0: Serial Number 182363802294
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 114480MB (234455040 512 byte sectors)
da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
da0: <Generic Flash Disk 8.07> Removable Direct Access SPC-2 SCSI device
da0: Serial Number E929819D
da0: 40.000MB/s transfers
da0: 7680MB (15728640 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
/etc/rc: WARNINGrandom: unblocking device.

stephenw10

Ok, that still looks like bad console setup.
That's the point at which the output switches from all consoles to only the primary console. It will be waiting for you agree to the install at the primary console which is clearly slightly different to the ADI boxes. It does also switch to an ASCII menu at that point. It may be possible your terminal setup cannot display it...

It looks like you have a 120GB SSD you're installing to. Probably the easiest thing here is going to be installing to it on something else and moving the drive across. You would just need to edit the config to use ix0 and ix1 as WAN and LAN and it will boot fully with web access to the GUI.

Steve

ozlecz

What will be the command to swirch console so i could just try to interupt the booting and invoke.

stephenw10

There is no command as such. As I understand it output from the kernel is sent to all configured consoles user space stuff is sent only to primary console. Or something along those lines.
That is the last output you see on all consoles until the console menu is drawn. But that doesn't happen in the installer.

Find and connect to com1 on an internal header or install on something else and move the drive is what I would try in that situation.

Steve

ozlecz

Ive tried plugging in a vga image preinstalled drive but without editing the nics...its the same result...stops at the start of booting only

ozlecz

been struggling where to find/edit the NIC from diagnostics/edit file

ozlecz

wewwww....found it and it works...many many thanks
=only problem now is how to really display on the console.

ozlecz

another thing is its very slow internet
=without this box, DL=25mbps
=with this box, DL=5mbps

stephenw10

If you installed a VGA image then first enable the serial console in System > Advanced > Admin Access.

That will give you a serial console but on com1. Try adding

comconsole_port="0x2F8"

To the file /boot/loader.conf.local , create that file if required.

com2 is usually at that hardware address but it may not be on your board which seems to be non-standard. There are probably some clues to where it is in the BIOS if that doesn't work.

With a throughput that low I would check for a speed duplex mismatch on one of the interfaces in Status > Interfaces. If your upstream device is set to 100MB-FD rather than auto for example it will probably default to 10MB-HD. Youe WAN would need to be set to match.

Steve

ozlecz

i dont have config.local

i have only /boot/loader.conf
is this file okay or i still have to create one

stephenw10

You should create the loader.conf.local file.

loader.conf is overwritten by system changes, firmware upgrades etc.

Steve

ozlecz

sorry but still i dont know how to create it....pls

stephenw10

From the command line or Diag > Command prompt run:
touch /boot/loader.conf.local

Steve

ozlecz

the same result sir

stephenw10

You mean setting that still gives no serial console?
And serial console is enabled in System > Advanced > Admin Access?

That is the standard location for com2 but it might not be there on that hardware since they decided to use com2 as the console. Check the BIOS for any reference to the I/O location.

Other than that I'm not sure what more we can do. You could try some other OS to see if that is able to use the console.

Steve