Re: serial driver issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Dec 04, 2022 at 08:11:11PM +0200, Oleksii Hryhorovych wrote:
> вс, 4 дек. 2022 г. в 18:53, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>:
> >
> > On Sun, Dec 04, 2022 at 06:42:19PM +0200, Oleksii Hryhorovych wrote:
> > > Hi. I have a problem with linux "serial" driver. I`m using a MosChip
> > > 9901 based ExpressCard 34 dual rs-232 controller. When I plugged this
> > > card into my PC, the system detected it, but when I tried to send or
> > > read something from one of the ports, there was silence. Loopback test
> > > also fails. On windows this card works perfectly, so this is not a
> > > hardware issue. My kernel version is "5.15.78-1-MANJARO".
> >
> > How exactly are you trying to send data through the port?  What command
> > did you use and what was the result?
> >
> I tried(each test 4 times, trying each device node for each port):
> 1) Execute "cat /dev/ttyS6"(or ttyS7), connect rs-232 cable to port on
> the card and to another PC, then send from another PC something to
> port.
> Result: nothing new appeared in console

"cat" isn't the best test, minicom is good, as you tried:

> 2) Connect rs232 cable to port on card and to another PC. Run terminal
> on another PC, run minicom on this PC. Disable flow control. Send
> something to terminal on both PCs.
> Result: nothing appeared in terminals on both PCs.
> 3) Connect pins number 2 and 3 on rs232 port (loopback test). Open
> minicom, disable flow control and send something to the terminal.
> Result: nothing new appeared in the terminal
> 4) Connect pins number 2 and 3 on rs232 port (loopback test). Open
> first console window, run "cat /dev/ttyS6"(or ttyS7). Open second
> window, run "echo "test" > /dev/ttyS6"(or ttyS7).
> Result: nothing new appeared in the first console

I think the problem is that you do not have a driver attached to your
serial ports, because:

> > > "dmesg" output about this card:
> > >
> > > [64329.311478] pcieport 0000:00:1c.1: pciehp: Slot(1): Card present
> > > [64329.311485] pcieport 0000:00:1c.1: pciehp: Slot(1): Link Up
> > > [64329.442833] pci 0000:02:00.0: [9710:9901] type 00 class 0x070002
> > > [64329.442867] pci 0000:02:00.0: reg 0x10: [io  0x0000-0x0007]
> > > [64329.442883] pci 0000:02:00.0: reg 0x14: [mem 0x00000000-0x00000fff]
> > > [64329.442922] pci 0000:02:00.0: reg 0x20: [mem 0x00000000-0x00000fff]
> > > [64329.443096] pci 0000:02:00.0: supports D1 D2
> > > [64329.443099] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> > > [64329.443402] pci 0000:02:00.1: [9710:9901] type 00 class 0x070002
> > > [64329.443434] pci 0000:02:00.1: reg 0x10: [io  0x0000-0x0007]
> > > [64329.443451] pci 0000:02:00.1: reg 0x14: [mem 0x00000000-0x00000fff]
> > > [64329.443495] pci 0000:02:00.1: reg 0x20: [mem 0x00000000-0x00000fff]
> > > [64329.443679] pci 0000:02:00.1: supports D1 D2
> > > [64329.443683] pci 0000:02:00.1: PME# supported from D0 D1 D2 D3hot D3cold
> > > [64329.443948] pci 0000:02:00.0: BAR 1: assigned [mem 0xd0000000-0xd0000fff]
> > > [64329.443960] pci 0000:02:00.0: BAR 4: assigned [mem 0xd0001000-0xd0001fff]
> > > [64329.443969] pci 0000:02:00.1: BAR 1: assigned [mem 0xd0002000-0xd0002fff]
> > > [64329.443979] pci 0000:02:00.1: BAR 4: assigned [mem 0xd0003000-0xd0003fff]
> > > [64329.443987] pci 0000:02:00.0: BAR 0: assigned [io  0x2000-0x2007]
> > > [64329.443995] pci 0000:02:00.1: BAR 0: assigned [io  0x2008-0x200f]
> > > [64329.444006] pcieport 0000:00:1c.1: PCI bridge to [bus 02-22]
> > > [64329.444012] pcieport 0000:00:1c.1:   bridge window [io  0x2000-0x3fff]
> > > [64329.444017] pcieport 0000:00:1c.1:   bridge window [mem
> > > 0xd0000000-0xd3ffffff]
> > > [64329.444023] pcieport 0000:00:1c.1:   bridge window [mem
> > > 0xbfb00000-0xbfcfffff 64bit pref]
> > > [64329.444110] serial 0000:02:00.0: enabling device (0000 -> 0003)
> > > [64329.444690] 0000:02:00.0: ttyS6 at I/O 0x2000 (irq = 17, base_baud
> > > = 115200) is a 16550A
> > > [64329.448040] serial 0000:02:00.1: enabling device (0000 -> 0003)
> > > [64329.452843] 0000:02:00.1: ttyS7 at I/O 0x2008 (irq = 18, base_baud
> > > = 115200) is a 16550A

ttyS6 and ttyS7 seem to be the correct devices, but:

> > Which tty device node are you using here?
> >
> I tried using both nodes, /dev/ttyS6 and /dev/ttyS7, and the result
> was the same.
> > What does the output of `find /dev/serial/` show?
> >
> /dev/serial/
> /dev/serial/by-id
> /dev/serial/by-id/usb-HP_HP_hs2340_HSPA+_MobileBroadband_C69366190FA2EB60-if01
> /dev/serial/by-id/usb-HP_HP_hs2340_HSPA+_MobileBroadband_C69366190FA2EB60-if03
> /dev/serial/by-id/usb-HP_HP_hs2340_HSPA+_MobileBroadband_C69366190FA2EB60-if09
> /dev/serial/by-path
> /dev/serial/by-path/pci-0000:00:1a.0-usb-0:1.2:1.9
> /dev/serial/by-path/pci-0000:00:1a.0-usb-0:1.2:1.1
> /dev/serial/by-path/pci-0000:00:1a.0-usb-0:1.2:1.3

You only have usb-serial devices seen in the system.

Are you sure the PCI card is being controlled properly?  No other kernel
log messages?

Is /dev/ttyS6 and ttyS7 present in /dev?

What does 'ls -l /sys/class/tty/' show?

thanks,

greg k-h



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux