Setting an alternate com port for serial output
-
Hi, I currently have a device that only outputs to com2 (com1 is internal) and was wondering if there is a way to make it work without recompiling the kernel (as there are no tools or kernel configs available anymore)
is there a way to do this or do I now have a $700 paperweight? :(
-
If you're using Nano then there isn't an easy way to do this AFAIK. Please let me know if you find one.
For a full install you just choose a different com port. What hardware are you using? What install type?Steve
-
Lanner 7573. has a comA port in front, then COMB1 and COMB2 pinouts on the board.
uses the newest intel chipset that is in 2.1.3 (2.1.1 actually)
-
So you're running Nano from a CF card then?
Hmm, so three serial ports then? And ComA is not the default console? Can you change the arrangement in the bios?
Other similar Lanner hardware works fine with the front console port.
Steve
-
pfsense sees it as com2 for some reason.
interesting enough, older netgate hakamua images display just fine and dandy.
-
I'm running a Lanner 7535 and new installs with 2.x did run fine with the default front console port. Did you check your BIOS if you can change a console setting or disable the other serial pin outs? Would seem strange, that 753x and 754x series run fine?
Greets
-
Yep, check for bios options.
I have to say though we failed misarably to do exactly this with the XTM8 (a customised Lanner box). We did eventually get it going by just using the Nano+VGA image and temporarily hooking up a monitor.Steve
-
A couple things you'll need to do:
1. To get a login prompt/menu without boot message/log entries, you can edit the entry for the second COM port in /etc/ttys (copy ttyv0 line for ttyv1)
2: To get boot messages, you can change /boot/device.hints to set the flags to 0x30 for hint.uart.1.flags and set port 0 to 0x00.I haven't tried that, but at least in theory it should work…
Used to be you had to recompile the kernel to set the serial port flags but that shouldn't be necessary these days.
-
Ah, that's interesting Jim.
That's true for Nano? And for 2.1.3?Steve
-
Should be true for either one, but there is code that alters the ttys file that may overwrite changes if you're not careful, and on nano I don't think /boot/device.hints is copied from slice to slice.
