Hi Toby, On 30/12/14 16:25, Toby Schneider wrote: > All - > > I cannot get Linux to recognize the second serial port on the net6501. > I'm running a Debian Wheezy root filesystem, and tried several kernels > (including one I built). None of them will register a second serial port > (presumably would be /dev/ttyS1):
I simply do the following on Debian Wheezy amd64: echo "pch_uart" >>/etc/modules After that I can simply use the second serial port as /dev/ttyPCH0. I have the console on ttyS0 and control the second net6501 on ttyPCH0. For reference, I use the following kernel options: console=ttyS0,19200 elevator=noop intel_idle.max_cstate=1 pcie_aspm=off 8250.nr_uarts=2 i8042.noaux i8042.nokbd Best regards, Martin > > == Linux 3.2.0 (debian wheezy stock) == > > mituser@polpo-2014-11-12:~$ uname -a > Linux polpo-2014-11-12 3.2.0-4-686-pae #1 SMP Debian 3.2.63-2 i686 > GNU/Linux > mituser@polpo-2014-11-12:~$ dmesg | grep tty > [ 0.000000] Kernel command line: > BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae > root=UUID=bda2c665-6b64-4815-8dde-ca9c6915be54 ro console=tty1 > console=ttyS0,57600n8 acpi=off > [ 0.000000] console [tty1] enabled > [ 0.000000] console [ttyS0] enabled > [ 2.796353] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a TI16750 > [ 12.462436] ttyS1: LSR safety check engaged! > [ 12.465707] ttyS1: LSR safety check engaged! > [ 12.485800] ttyS2: LSR safety check engaged! > [ 12.501702] ttyS2: LSR safety check engaged! > > == Linux 3.16.0 (debian wheezy backports) == > mituser@polpo-2014-11-12:~$ uname -a > Linux polpo-2014-11-12 3.16.0-0.bpo.4-686-pae #1 SMP Debian > 3.16.7-ckt2-1~bpo70+1 (2014-12-08) i686 GNU/Linux > mituser@polpo-2014-11-12:~$ dmesg | grep tty > [ 0.000000] Kernel command line: > BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-686-pae > root=UUID=bda2c665-6b64-4815-8dde-ca9c6915be54 ro console=tty1 > console=ttyS0,57600n8 acpi=off > [ 0.000000] console [tty1] enabled > [ 0.000000] console [ttyS0] enabled > [ 2.972377] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = > 115200) is a TI16750 > [ 8.442372] 0000:02:0a.1: ttyPCH0 at I/O 0x1040 (irq = 65, base_baud > = 0) is a pch_uart > [ 8.669015] 0000:02:0a.2: ttyPCH1 at I/O 0x1048 (irq = 67, base_baud > = 0) is a pch_uart > [ 8.680706] 0000:02:0a.3: ttyPCH2 at I/O 0x1050 (irq = 68, base_baud > = 0) is a pch_uart > [ 8.692644] 0000:02:0a.4: ttyPCH3 at I/O 0x1058 (irq = 69, base_baud > = 0) is a pch_uart > > > There seems to be some history, but it seems that no resolution was found: > > http://lists.soekris.com/pipermail/soekris-tech/2013-August/019044.html > > Any help is greatly appreciated. I assume this second uart would be > handled by the linux serial8250 driver. > > Thanks- > -Toby > -- Martin Sofaru (Head of Consulting and Services), http://www.lsexperts.de LSE Leading Security Experts GmbH, Postfach 100121, 64201 Darmstadt Tel: +49 6151 86086-253, Fax: -299, Mobil: +49 170 7833883 Unternehmenssitz: Weiterstadt, Amtsgericht Darmstadt: HRB8649 Geschaeftsfuehrer: Oliver Michel, Sven Walther
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
