PC Engines apu2 experiences
-
@sikita I am on pfSense 2.5.0 and here it says:
Do you have AES-NI enabled?
-
Can anyone share there System / Advanced / Networking on a APU2
Mine are
as these are the defaults, grabbed them from a VM installation, which is not quit the same setup.
The old and not anymore recommend settings from https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/ are quit different!
...and there is a new settings present in 2.5.0. " hn ALTQ support"
Could anyone elaborate on all these or there settings?
-
There are no hn NICs on any APU so it makes no difference. You can disable it.
Steve
-
I performed all the bootloader and other tweaks mentioned in various threads throughout the years on my <= 2.45-p1 installation and now I don't remember what they all are. It would be great if somebody could post what things to look for (to remove?) when you update your apu2 from 2.4.5 --> 2.5.0.
At the moment because of the performance issues, I'm not upgrading.
-
@valnar said in PC Engines apu2 experiences:
when you update your apu2 from 2.4.5 --> 2.5.0.
Hi,
With that, I would wait a little longer
here,....you will find a lot of useful info if you even decide to upgrade...
https://teklager.se/en/knowledge-base/
https://teklager.se/en/knowledge-base/apu2-1-gigabit-throughput-pfsense/+++edit:
and of course
https://pcengines.github.io/ -
Smooth update to pfSense 2.5.1 CE
-
Updated to bios coreboot v4.13.05.
-
@qinn Fine !
I am still on 2.4.5_1.
Did you notice any performance degradation ? -
@flok No, so far not.
-
I received an email notification about v4.14.0.2 and this IMPORTANT message was included:
To update the firmware and keep the runtime configuration unchanged please use the following command:
flashrom -p internal -w apuX_v4.14.0.2.rom --fmap -i COREBOOT
The persistent runtime configuration works only when migrating from versions v4.14.0.1 and later. The feature is not yet supported on apu1. Flashrom version needs to be v1.1 or newer.I did the upgrade from v4.14.0.1 with that new command without any issues. However, for the longest time this is what I've been using:
flashrom -p internal -w apuX_v4.14.0.2.rom
What is the difference?
-
@kevindd992002
I'm not by any means an expert on coreboot, butflashrom -p internal -w apuX_v4.14.0.2.rom
will overwrite the entire flash chip with the new rom file.
flashrom -p internal -w apuX_v4.14.0.2.rom --fmap -i COREBOOT
The flash chip has various partitions defined in a 'flashmap' format and this command specifies which area to overwrite. This probably allows for user altered settings such as seabios boot order changes to persist and not get overwritten during the coreboot update, but I haven't tried it out.
-
@bigsy said in PC Engines apu2 experiences:
@kevindd992002
I'm not by any means an expert on coreboot, butflashrom -p internal -w apuX_v4.14.0.2.rom
will overwrite the entire flash chip with the new rom file.
flashrom -p internal -w apuX_v4.14.0.2.rom --fmap -i COREBOOT
The flash chip has various partitions defined in a 'flashmap' format and this command specifies which area to overwrite. This probably allows for user altered settings such as seabios boot order changes to persist and not get overwritten during the coreboot update, but I haven't tried it out.
That's what I thought. However, with the 1st command I have never seen any seabios setting get changed when I use it to update my APU2. I'm wondering if it's really better to use the 2nd command from this point moving forward.
-
@kevindd992002 If you look at the changes to the pcEngines fork of SeaBIOS, the addition of 'support for persistent bootorder in FMAP region' has only been in the most recent release of SeaBIOS v1.14.0.1 and similarly for sortbootorder v4.6.21.
-
@bigsy I see. So we're just preserving boot order here? Since I just have one boot device in my APU2, then it wouldn't matter to me.
-
For the APU2C4, why is it that when I have a serial cable connected between its serial port and a computer, its USB ports don't work? I have a UPS plugged in to one of its USB ports and I use the NUT package in pfsense. As soon as I connect to the hardware through the serial port (using putty), the USB port does not work. Unplugging the serial cable fixes the issue and that's why I know it's the one causing it. This is happening for both of my APU2C4 boxes.
-
@kevindd992002 said in PC Engines apu2 experiences:
connected between its serial port and a computer, its USB ports don't work?
Hmmmm, I haven't seen it yet, it is true we don't even connect to MOBO in this multiple way...
Have you tried to remove NUT? (of course temporarily)
-
@daddygo said in PC Engines apu2 experiences:
@kevindd992002 said in PC Engines apu2 experiences:
connected between its serial port and a computer, its USB ports don't work?
Hmmmm, I haven't seen it yet, it is true we don't even connect to MOBO in this multiple way...
Have you tried to remove NUT? (of course temporarily)
I haven't yet but I see the usb disconnect message in the terminal itself so I figured it's a board issue. I also use the USB port only for NUT so removing it will be a moot point but I can still try for the sake of troubleshooting.
-
@kevindd992002 said in PC Engines apu2 experiences:
but I can still try for the sake of troubleshooting.
Sure
Would it be worth doing to rule out the SW/Code issue (on NUT) in the background...
The NUT is a strange animal anyway and sometimes difficult to get to work..
It also handles USB and RS232 stuff, so I guess that's where the rub is
-
@daddygo said in PC Engines apu2 experiences:
@kevindd992002 said in PC Engines apu2 experiences:
but I can still try for the sake of troubleshooting.
Sure
Would it be worth doing to rule out the SW/Code issue (on NUT) in the background...
The NUT is a strange animal anyway and sometimes difficult to get to work..
It also handles USB and RS232 stuff, so I guess that's where the rub is
I already uninstalled NUT and I soon as I connected to the serial port, I still see the issue:
ugen0.2: <Unknown > at usbus0 (disconnected)
So this is definitely an APU2C4 issue. Can anyone try this?
-
@kevindd992002 said in PC Engines apu2 experiences:
So this is definitely an APU2C4 issue. Can anyone try this?
I dont have a APU2C4 (Only APU2C0) but I would suggest to try an older BIOS version.
-
@fireodo said in PC Engines apu2 experiences:
@kevindd992002 said in PC Engines apu2 experiences:
So this is definitely an APU2C4 issue. Can anyone try this?
I dont have a APU2C4 (Only APU2C0) but I would suggest to try an older BIOS version.
I'm at v4.14.0.2 but this is not the first time I've tried this. I've tried this a year ago when it was still using an older BIOS version and it's the same issue.
-
@kevindd992002 said in PC Engines apu2 experiences:
4.14.0.2 but this is not the first time I've tried this
You say, this is the case on several boxes (MOBO)
(so no HW issue I think, some PCB schematics or BIOS)Worth a question for him:
https://github.com/miczyg1BTW:
I can't check it either, because we only use apu24d4 -
@daddygo said in PC Engines apu2 experiences:
@kevindd992002 said in PC Engines apu2 experiences:
4.14.0.2 but this is not the first time I've tried this
You say, this is the case on several boxes (MOBO)
(so no HW issue I think, some PCB schematics or BIOS)Worth a question for him:
https://github.com/miczyg1BTW:
I can't check it either, because we only use apu24d4Just created an issue:
https://github.com/pcengines/pcengines.github.io/issues/107
-
@kevindd992002 using the serial port is pretty normal, and what you're describing is not at all common. I'd probably first make sure of the power supply (marginal power supplies cause all sorts of issues), then look at whether the serial cable is dodgy/shorted/etc.
-
@vamike said in PC Engines apu2 experiences:
what you're describing is not at all common
Hi,
we are not talking about just one unit, so this is not relevant advice now...
(marginal power supplies cause all sorts of issues), then look at whether the serial cable is dodgy/shorted/etc.)by the way he is quite an experienced pcEngines user @kevindd992002
-
@vamike said in PC Engines apu2 experiences:
@kevindd992002 using the serial port is pretty normal, and what you're describing is not at all common. I'd probably first make sure of the power supply (marginal power supplies cause all sorts of issues), then look at whether the serial cable is dodgy/shorted/etc.
I know it's happening for two units and I'm using a power supply that I sourced from pcengines themselves. The only variable that I haven't eliminated is the serial cable that I'm using. I guess I can buy one of the good ones and try.
-
@daddygo really? so you think "apu2 hardware generally doesn't work with serial and usb at the same time and up until now nobody ever noticed" is a likely thing?
-
Mmm, I would at least try a different cable.
Does it disconnect all usb devices when you connect the serial cable?
You may be creating a ground loop there since it's the UPS that is connected. Is the terminal device you're using also running from the UPS?
Steve
-
@stephenw10 said in PC Engines apu2 experiences:
Mmm, I would at least try a different cable.
Does it disconnect all usb devices when you connect the serial cable?
You may be creating a ground loop there since it's the UPS that is connected. Is the terminal device you're using also running from the UPS?
Steve
I only have one usb device plugged in, the UPS. I'm trying now to see if using the other USB port will fix the issue because I only ever see the ugen0.2 disconnect message in the terminal. If ugen0.1 is the other port, then I don't see it getting affected.
Is there a command that I can invoke in the pfsense shell to see which usb port is a device connected to?
Yes, the terminal I'm using is connected to the same UPS.
-
@vamike said in PC Engines apu2 experiences:
so you think "apu2 hardware generally doesn't work with serial and usb
hmmmm, ... no one assumed such a thing
just trying to figure out what is happening
while also having to "fumble" with ironic remarks -
You can run
usbconfig list
to see info about the USB devices attached but it won't show the specific port only the bus.But try just connecting anything, mouse, keyboard, data drive etc. Anything just to see if it also gets disconnected then the serial is attached.
Does it happen when you connect the serial cable if it isn't connected to the terminal client? That would almost certainly be the cable if so.
Steve
-
@daddygo if you're trying to figure out what is happening the best thing to do is refrain from distracting commentary about what you think is "irrelevant"
@kevindd992002 if you got the two units at the same time I still wouldn't rule out wonky power supply as an issue. wall warts are notoriously unreliable, and I've seen >60% failure rates in the field (not DOA) from some batches in the past. those issues are complete PITA to debug because everything will work fine until the load reaches a certain point, then the PS can't keep up and weird things happen. much easier when they fail to the point that they melt, so the problem is obvious. trying different combinations of usb & serial is probably an easier place to start--throwing a thumb drive on with a serial console should work fine and is extremely well tested as a way to perform installs. if that doesn't work, definitely try a different serial cable and even a completely different serial source on the other end (e.g., try a different usb2serial converter on the machine you're using as a terminal). if it does work then you've narrowed down the source of the problem and it's neither serial nor usb generally, but that one specific usb device.
-
@vamike said in PC Engines apu2 experiences:
the best thing to do is refrain from distracting commentary about what you think is "irrelevant"
hey buddy, leave it to those who know what they're doing, for example @stephenw10
-
Ok calm down! We are all trying to solve this problem.
Do not dismiss @VAMike. Review his old posts. You will see he knows what's what.
Steve
-
@stephenw10 said in PC Engines apu2 experiences:
Ok calm down!
Okay, I understand, but I don't like it when someone arrives and immediately attacks...
@VAMike sorry bro, let's respect each other
+++edit: @stephenw10 by the way the best idea was the UPS ground loop
-
@stephenw10 said in PC Engines apu2 experiences:
You can run
usbconfig list
to see info about the USB devices attached but it won't show the specific port only the bus.But try just connecting anything, mouse, keyboard, data drive etc. Anything just to see if it also gets disconnected then the serial is attached.
Does it happen when you connect the serial cable if it isn't connected to the terminal client? That would almost certainly be the cable if so.
Steve
Ok, I did more tests and the results are more conclusive.
- Both ports are labelled ugen0.2 when invoking
usbconfig list
which proves the point that that command lists only the bus. - Both ports are affected by the issue.
- The issue only happens with the UPS USB device. I tried plugging in different devices (flash drives, keyboard, mouse, etc.) and all of them did not disconnect while the serial connection is opened.
- When I connect the terminal, it disconnects the APC UPS and running the same command gives me this:
[2.5.2-RELEASE][root@pfSense.condo.arpa]/root: ugen0.2: <Unknown > at usbus0 (disconnected) usbconfig list ugen0.2: <Unknown > at usbus0 (disconnected) ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen1.1: <AMD EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: <vendor 0x0438 product 0x7900> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
Look how it says "unknown" in ugen0.2. When this happens, unplugging and replugging the APC USB cable doesn't do anything.
It only happens when I connect the serial cable to the terminal client. If one end of the cable is connected to the APU2C4 but disconnected from the terminal client, no issue.
At this point, I would think the ground loop theory is making more sense to be the cause of the issue. What do you think? Can it still be the cable?
- Both ports are labelled ugen0.2 when invoking
-
@kevindd992002 said in PC Engines apu2 experiences:
What do you think? Can it still be the cable?
do you have a multimeter at your hand, with a diode tester (discontinuity measurement)?
+++edit:
the metal enclosures of UPS and APU stuff,- bringing them up to equipotential is not a bad idea -
@daddygo said in PC Engines apu2 experiences:
@kevindd992002 said in PC Engines apu2 experiences:
What do you think? Can it still be the cable?
do you have a multimeter at your hand, with a diode tester (discontinuity measurement)?
+++edit:
the metal enclosures of UPS and APU stuff,- bringing them up to equipotential is not a bad ideaI do. So you want me to see if there's low resistance between the APU's metal enclosure and UPS' ground point, correct? The UPS doesn't have a metal case because it's all plastic. It's an APC BR1500GI. So the ground points would be the screws and the third prong in the outlets themselves.
Do I test before and after the serial cable connection?
-
@kevindd992002 said in PC Engines apu2 experiences:
The UPS doesn't have a metal case because it's all plastic.
I can already see the type (double insulated), the earthing is on the IEC13 connector(s) - the secondary circuit (after the inverter) is completely internally disconnected from primer
the middle leg of IEC13 is the ground, measure a resistance between this point and the APU metal housing
but you can also "ringing" the cable in question to see if there is a break somewhere
+++edit:
that reminds me, you say you have two of these boxes, how about testing the second one completely independently of the UPS on, say, on the kitchen table?this would bring us closer to a solution
-
@daddygo said in PC Engines apu2 experiences:
Okay, I understand, but I don't like it when someone arrives and immediately attacks...
you'll note that my first interaction with kevindd992002 in this thread dates from before you joined the forum...