-
It can be the cause?
pci0: <network> at device 11.0 (no driver attached)
-
There is no driver that recognises it, that;s the device shown as none0 in the pciconf output.
Ok I typo'd the baud rate! Try:
cu -l /dev/cuau1 -s 19200
If there's still nothing look in /dev to see if there are other serial ports.
Steve
-
@stephenw10 said in Install on NETASQ U30 S ?:
cu -l /dev/cuau1 -s 19200
same issue.
I tried cuau0 too# ls /dev acpi ctty hpet0 pass0 ttyu0.lock ttyva ada0 cuau0 io pci ttyu1 ttyvb ada0s1 cuau0.init kbd0 pf ttyu1.init ufs ada0s1a cuau0.lock kbd1 pts ttyu1.lock ufssuspend ada0s1b cuau1 kbdmux0 random ttyv0 ugen0.1 apm cuau1.init klog reroot ttyv1 ugen1.1 apmctl cuau1.lock kmem sndstat ttyv2 ugen2.1 atkbd0 devctl led speaker ttyv3 ugen3.1 audit devctl2 mdctl stderr ttyv4 ugen4.1 auditpipe devstat mem stdin ttyv5 urandom bpf fd midistat stdout ttyv6 usb bpf0 fido netmap sysmouse ttyv7 usbctl console full nfslock ttyu0 ttyv8 xpt0 consolectl geom.ctl null ttyu0.init ttyv9 zero
-
Hmm, it's at 9600 on the U70: https://forum.netgate.com/post/882959
Try:
cu -l /dev/cuau1 -s 9600
-
@stephenw10 it's always the same issue..
-
Hmm, you might try some other common board rates. I expect cuaU0 to be the front panel com port, but they might be swapped for some reason.
It could be that the switch in the smallest unit doesn't have a console to access. Can you see what the switch chip is on the board?
Steve
-
On the board I see near the RJ45 connectors a chip named "LB G4P109 LF"
My friend google said that it's a "quad port network transformer"
-
Hmm probably under that small heatsink unfortunately.
What baud rates did you try?
Any BIOS options that might suggest something?
Can you boot the original OS and check the boot messages?
Steve
-
I tried 4800 -> 115200 baudrate.
I will look in the bios tomorow.
OUPS ! Unfortunately I have written pfsense over the old OS
-
I don't see any option in bios thas suggest something. :(
-
[2.4.4-RELEASE][admin@pfSense.local]/dev: stty -a -f /dev/cuau0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab0 -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>; eol2 = <undef>; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;
-
@stephenw10 said in Install on NETASQ U30 S ?:
Hmm probably under that small heatsink unfortunately
I took the heatsink off ( I already tear up the warranty label :D)
It's an Atheros AR8328
--> it's not like in the command result where it is written intel --> I need to install a new driver ?
-
Hmm, OK.
It looks like the Atheros AR8328 does not have a serial interface that could be used to configure it unlike the other Netasq devices. That makes things immediately 100x more difficult as you need to configure it via MDC/MDIO or
via the config eprom directly.
Netasq/Stormshield OS is built on FreeBSD though I believe, they have contributed stuff back into the base. Unfortunately though I don't see the 8328 as supported:
https://github.com/freebsd/freebsd/tree/master/sys/dev/etherswitch/arswitch
Unless it's so similar to the 8327 it might be able to use that. We are still talking about significant work to get it running.One thing you might try here is Installing OpenWRT which does have support AR8328 switch. Even if just as a test.
Kind of curious what those jumpers might do but it's hard to recommend you change them without knowing. Are they labelled?
Steve
-
@stephenw10 said in Install on NETASQ U30 S ?:
Netasq/Stormshield OS is built on FreeBSD though I believe, they have contributed stuff back into the base. Unfortunately though I don't see the 8328 as supported:
https://github.com/freebsd/freebsd/tree/master/sys/dev/etherswitch/arswitch
Unless it's so similar to the 8327 it might be able to use that. We are still talking about significant work to get it running.How can I try that ?
@stephenw10 said in Install on NETASQ U30 S ?:
One thing you might try here is Installing OpenWRT which does have support AR8328 switch. Even if just as a test.
I did it PM.
eth1 is a Broadcomm, but down. nothing appends when i plug a cable in one of 4 ports.
I don't know what test I have to do.@stephenw10 said in Install on NETASQ U30 S ?:
Kind of curious what those jumpers might do but it's hard to recommend you change them without knowing. Are they labelled?
Yes they are : JP3 et JP4
-
So you did install OpenWRT already?
I'm not sure exactly what you were seeing as Broadcom. The two NIC would still be Intel. It may have created a bridge as OpenWRT usually does.
You probably have to install the correct switch control modules for it to see and recognise the switch. Not entirely sire what those might be though... -
I will search on this way
-
Nothing better...
I don't understand why cu command freez on "connected" -
The 'connected' output is generated by cu, it implies that cu is connected to the port. After that there is nothing there because there is nothing connected to the second com port. It's listening but nothing ever arrives.
You can only configure that switch chip via the MDC/MDIO bus.
Steve
-
@stephenw10 said in Install on NETASQ U30 S ?:
The 'connected' output is generated by cu, it implies that cu is connected to the port. After that there is nothing there because there is nothing connected to the second com port. It's listening but nothing ever arrives.
In bios COM1 and COM2 are mapped with physical interface. is there a relation to ?
@stephenw10 said in Install on NETASQ U30 S ?:
You can only configure that switch chip via the MDC/MDIO bus.
it's doable for me ?
-
I mean anything is possible; it's a simple matter of coding.
But if I were doing this I would start by trying to get OpenWRT to work with it as that's much closer to what you need to talk to the switch. Once that is working you will know exactly how it's connected and what it can do so it would make any work in pfSense much easier.
Steve
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.