r220's with serial

[Paul Macdonald]

has anyone managed to get serial console access working under dell r220's.

-All below under bios boot, as opposed to uefi, (which i can't use
anyway as usb installer doesn't support ZFS on boot)

tried under both ZFS boot and traditional UFS setup.

I see:
- with bios redirection after boot on (which i have on all
other working non r220 prior boxes)
-broken boot menu which gets kicked out to an
usuable loader prompt, if you catch it quick it'll boot,
(i suspect there's some unwanted output from
the dell serial output)

- when bios redirection after boot is disabled box does boot ok
under serial but i can't get a vt100 terminal login with same settings
as i have workign on all other boxes.

thanks
Paul.
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------

[Paul Macdonald]

Post by Paul Macdonald
has anyone managed to get serial console access working under dell
r220's.
-All below under bios boot, as opposed to uefi, (which i can't use
anyway as usb installer doesn't support ZFS on boot)
tried under both ZFS boot and traditional UFS setup.
- with bios redirection after boot on (which i have on all
other working non r220 prior boxes)
-broken boot menu which gets kicked out to an
usuable loader prompt, if you catch it quick it'll boot,
(i suspect there's some unwanted output from
the dell serial output)
- when bios redirection after boot is disabled box does boot
ok under serial but i can't get a vt100 terminal login with same
settings as i have workign on all other boxes.
thanks
Paul.

given most of the above is fixed by turning off bios redirection after
boot, a potentially better question is why do i not get a login prompt
after boot?
neither:

ttyu0 "/usr/libexec/getty std.57600" vt100 onifconsole secure
ttyu0 "/usr/libexec/getty std.57600" vt100 on secure

give a login prompt.

getty on ttyu0 is running

root 766 0.0 0.0 14488 2120 - I 10:31PM 0:00.00
/usr/libexec/getty std.57600 ttyu0
root 758 0.0 0.0 14488 1984 v0 Is+ 10:31PM 0:00.00
/usr/libexec/getty Pc ttyv0


Paul.
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------

[Paul Macdonald]

uart0 not seen in dmesg which i think is def related:

/var/log/messages
Jun 9 22:59:31 asd getty[796]: open /dev/ttyu0: No such file or directory

(tried disabling ttyu0 and only having ttyu1 but no luck)

#ttyu0 "/usr/libexec/getty std.57600" vt100 onifconsole secure
ttyu1 "/usr/libexec/getty std.57600" vt100 onifconsole secure


*dmesg:**
*
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0

Whereas on a currently working serial system i see uart 0 and 1

///uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0//
// uart0: console (57600,n,8,1)////
// uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0//
/
is this just a serial port driver issue on com1?

(altho i see all serial stuff till login)

help!
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------

[Paul Macdonald]

Is the issue is a lack of a an appropriate serial driver in 10.1 for
dell r220's?

(serial is fine till OS boot and login should be shown)
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------

[Paul Macdonald]

Post by Paul Macdonald
Is the issue is a lack of a an appropriate serial driver in 10.1 for
dell r220's?
(serial is fine till OS boot and login should be shown)

centOS find's ttyS0 and ttyS1 fine on this box (dell r220)

Under FreeBSD 10-1 uart0 is not found (dmesg or under /dev)

uart1 is found as per:

Jun 10 12:25:14 asd kernel: uart1: <16550 or compatible> port
0x2f8-0x2ff irq 3 on acpi0

Paul.
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------

[Paul Macdonald]

Post by Paul Macdonald
has anyone managed to get serial console access working under dell
r220's.

This was due to an ACPI bug in r220's

Marcel Moolenaar provided me with a fix which is:

-BIOS-

Serial Communication <On with Console Redirection via COM2>
Serial Port Address <Serial Device1=COM2,Serial Device2=COM1>
External Serial Connector <Serial Device 1>

-FreeBSD-

adding the following line to /boot/loader.conf:
hw.uart.console="io:0x2f8,br:57600"


.....

From the looks of it, you have a BIOS bug. In particular a bug in the
ACPI AML (you can dump the ACPI AML with acpidump -d). If I understand
it correctly then the first 2 serial devices (UAR1 and UAR2) have the
same H/W registers. What this boils down to is that the kernel only
works with 1 serial port (UAR1), which ends up having the H/W
configuration of the second serial port (UAR2).

With the BIOS redirecting to COM1 (which is H/W address 0x3f8) and
serial device 1 assigned to COM1 *and* serial device assigned to the
serial port on the chassis, the kernel had no chance to present a login
prompt.

I worked around the problem by reconfiguring the BIOS so that COM2
(which is H/W address 0x2f8) is assigned to serial port 1 and the BIOS
redirecting to COM2. What this does is have COM2 connected to the serial
port on the chassis.

So, even though I suspect that the kernel thinks it’s talking to the
first serial port, it’s actually talking to the second serial port (due
to the ACPI/BIOS bus).
--
-------------------------
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-------------------------
t: 0131 5548070
m: 07970339546
e: ***@ifdnrg.com
w: http://www.ifdnrg.com
-------------------------
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
----------------------------------------------------
High Specification Dedicated Servers from £100.00pm
----------------------------------------------------