• 0

Serial port (COM1) - stages of operation.


Question

Please explain to knowledgeable people at what stage data output to the serial port begins.

 

When loading the 1.03b loader (for DS3617xs or for DS3615xs), it comes to the standard screen about successful loading. The flash drive flashes a little more and everything stops there. No data is output to the serial port. Not a single letter. I'm wondering if the bootloader doesn't find the network card, should it output to the serial port? Or, if there are problems with the network, no data will be output? I tried different options, including different boot loaders and BIOS settings - I couldn't see anything on the serial port. 

 

You may think that it doesn't work for me, but it doesn't, because on the 1.04b bootloader for DS918+, all data is output correctly to the serial port. I see all the messages when loading.

I'm not asking about my specific problem right now, I'm asking you to explain under what conditions output to the serial port is not possible.

 

Does the serial port settings in grub.cfg affect this? I noticed that the serial port parameters for 1.04b and 1.03b are different. Could this be a problem?

 

Why do I need this? I want to see the reason why I can't run DS3617xs or for DS3615xs.

 

There is one point: my motherboard does not have a built-in serial port, so I use an external PCI-E serial port controller, however, I am not sure that this could be a problem.

 

Edited by allex
Link to post
Share on other sites

16 answers to this question

Recommended Posts

  • 0

Using additional com hardware can be the problem of no output. If the card isn’t recognized by DSM it can’t give any output to it. Usually onboard com ports are no problem but some exotic devices will not work for console output/debugging.

  • Like 1
Link to post
Share on other sites
  • 0
On 10/30/2020 at 12:26 PM, jensmander said:

but some exotic devices will not work for console output/debugging.

 i have tested usb2serial and two different pcie cards, no luck

the only exceptions beside a real onboard com port (often now just a header on the board you need to use with a adapter) are virtual com ports of integrated remote managment chips like HPE's iLO

 

On 10/30/2020 at 9:20 AM, allex said:

There is one point: my motherboard does not have a built-in serial port, so I use an external PCI-E serial port controller, however, I am not sure that this could be a problem.

 

i'd say thats the problem but

 

On 10/30/2020 at 9:20 AM, allex said:

You may think that it doesn't work for me, but it doesn't, because on the 1.04b bootloader for DS918+, all data is output correctly to the serial port. I see all the messages when loading.

 

if that worked then what exact pcie card is this, whats the chip on that card, whats its vendor and device id (lspci) - i want one of these cards ;-)

 

On 10/30/2020 at 9:20 AM, allex said:

I'm not asking about my specific problem right now, I'm asking you to explain under what conditions output to the serial port is not possible.

 

synology has the documentation, we're just messing around

 

On 10/30/2020 at 9:20 AM, allex said:

When loading the 1.03b loader (for DS3617xs or for DS3615xs), it comes to the standard screen about successful loading. The flash drive flashes a little more and everything stops there. No data is output to the serial port.

IF it would be working you would see a mirror of the video screen with the grub selection including jun's message and after that the output to the serial console would be unique, in case of loader 1.03b 3615/17 and uefi (not working, it needs csm) you would just see a special ascii character and then it would stop - kind of worst case but you see something an can make assumptions like oh, usually there is a second ascii character of the same type and then it starts to output text about system and drivers - but you would need to have seen it working to know that

as long as you don't see the grub message mirrored on the serial console assume the serial console is not working at all

 

On 10/30/2020 at 9:20 AM, allex said:

Does the serial port settings in grub.cfg affect this?

 

it should but i'm not sure i ever switched to com 2 or changed the speed

 

 

On 10/30/2020 at 9:20 AM, allex said:

I noticed that the serial port parameters for 1.04b and 1.03b are different. Could this be a problem?

 

i use all three loaders with the same setting in putty

 

 in my loaders its all the same

 

918+
console=ttyS0,115200n8

3615
console=ttyS0,115200n8

3617
console=ttyS0,115200n8

 

whats the reference for that claim, mine it the line

set common_args_XXXX=

 

 

Link to post
Share on other sites
  • 0
Цитата

if that worked then what exact pcie card is this, whats the chip on that card, whats its vendor and device id (lspci) - i want one of these cards ;-)

I'll write the model tonight. If it is suitable for you and you can not find it on sale, I am ready to send it to you as a thank you for the development. Free of charge, of course.

Edited by allex
Link to post
Share on other sites
  • 0

This is my pci-e serial adapter (01:00.0 Serial controller: Device 1c00:3253 (rev 10)).

 

I used a bundle:

SERIAL PCI-E --> Null modem cable --> COM2USB --> terminal (Windows 7)

 

In the photos, I took a picture of the pci-e board itself and the chip, as well as a photo of the COM2USB adapter and its ID (Windows 7).

I added another photo of the data output to the terminal so that you don't think I'm deceiving you. This is the data output when loading DS 918+.

 

https://nextcloud.data-netsoft.ru/index.php/s/RyQQNg9CNFcdCXg

 

There is a similar adapter on the same chip.

 

Write me a message before Saturday if you need any more information about the configuration of the computer I'm setting up (running 918+). On Saturday, I put it into operation in the company and then it will be difficult to read information about its hardware from it.

 

Скрытый текст

00:00.0 Host bridge: Intel Corporation Device 3e0f (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e90
00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #11 (rev f0)
00:1d.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #12 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2ca
00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC
00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller
01:00.0 Serial controller: Device 1c00:3253 (rev 10)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

 

Edited by allex
Link to post
Share on other sites
  • 0

I tried running 3615 again. I tried the bootloader 1.03b and 1.02b. I also copied the extra (and rd.gz+zimage from pat file). But I always get a picture on the monitor as in the photo and not a single character on the serial port. I changed the BIOS settings, but it didn't lead to anything. I think the kernel in these loaders doesn't support (?) my PCI-e serial card.

 

I don't know what else I can do.

 

 

IMG_20201103_213210.jpg

IMG_20201103_213153.jpg

Edited by allex
Link to post
Share on other sites
  • 0

Ahaha)))

I decided to scan the network and I found my xpenology!!! 

I used:

DS3615xs 6.1 Jun's Mod V1.02b + extra3615_v4.9_test + rd.gz+zimage from pat file 6.1.7

 

I put DSM6. 1. 7 on a test hard drive and it all works. But I will use DS918+ in my work.

 

But I still haven't received a single character on the serial port.

Nowadays, the serial port is less and less common. Can't I add drivers to the bootloader for serial ports on PCI-e? It's very hard to work blindly I don't know what errors the kernel displays...

 

PS Bootloader 1.04 for DS 918+ correctly outputs all data to the serial port so far (last photo)!

 

IMG_20201103_214719.jpg

IMG_20201103_220817.jpg

IMG_20201103_223458.jpg

Edited by allex
  • Like 1
Link to post
Share on other sites
  • 0
4 hours ago, allex said:

This is my pci-e serial adapter (01:00.0 Serial controller: Device 1c00:3253 (rev 10)).

thanks that gives pretty much most or all it needs because if anything then its about the chip used on that card (but you even ha a good photo with the chip)

 

giving it a thought, you 918+ show a serial console with it and 3615/17 does not then it might be the age of the kernel, 4.4.59 is of 918+ is newer then 3.10.105

the driver in question might have in been introduced into the kernel later

maybe i did use 3615/17 and had negative results

i will check the other card i can borrow and the one i ordered now (its cheap enough) with 918+ first and then with 3615/17

even if its only going to work with kernel 4.4.x, with 7.0 the 3617 will get 4.4.x too - but we dont know who will hack what system so we might end up with a total different one with 7.0 (there might be better choices now)

might be pretty useful to have the option to add a serial port for a low price, lots of system start to come without legacy i/o

Link to post
Share on other sites
  • 0
On 11/3/2020 at 5:22 PM, allex said:

This is my pci-e serial adapter (01:00.0 Serial controller: Device 1c00:3253 (rev 10)).

chip is WCH CH382L

http://www.wch-ic.com/products/CH382.html

 

just got a cheaper card (random vendor, with a CH382L ) from amazon and i can confirm you findings

the chip is working with synology's 4.4.59+ kernel on 918+

not in grub pre-boot and not with 3.10.105 synology kernel from 3615/17

looks like the serial output switches to a available serial port when the kernel inits such devices that has a driver active in the kernel

 

that we don't see the grub selection does not hurt, that's visible on a monitor, but having the option on newer system without serial port (but pcie slot) to see the serial output of the synology kernel booting can be helpful

 

when looking deeper into synology's published kernel config looking for support of CH38x chips and comparing the same section with the 3615/17 config might show other pcie chips that would possibly work with 3615/17

 

edit: a chip not working at all would be Oxford OXuPCI952-LG (card was a Exsys EX-44092)

 

other chips that might be interesting to test

Sunix SUN2212

ITE IT8728F

Asix MCS9922CV-AA

Axix MCS9901CV-CC

Asix AX99100

SystemBase SB16C1052PCI

 

 

 

Edited by IG-88
Link to post
Share on other sites
  • 0
14 часа назад, IG-88 сказал:

чип WCH CH382L

http://www.wch-ic.com/products/CH382.html

 

только что получил более дешевую карту (случайный продавец, с CH382L) от Amazon, и я могу подтвердить ваши выводы

чип работает с ядром Synology 4.4.59+ на 918+

не в предварительной загрузке grub и не с ядром Synology 3.10.105 от 3615/17

похоже, что последовательный вывод переключается на доступный последовательный порт, когда ядро запускает такие устройства, у которых есть драйвер, активный в ядре

 

что мы не видим, что выбор grub не повредит, это видно на мониторе, но наличие опции в более новой системе без последовательного порта (но слот pcie) для просмотра последовательного вывода загрузки ядра Synology может быть полезным

 

при более глубоком изучении опубликованной конфигурации ядра Synology в поисках поддержки чипов CH38x и сравнении того же раздела с конфигурацией 3615/17 могут быть обнаружены другие чипы pcie, которые, возможно, будут работать с 3615/17

 

edit: чип, который вообще не работает, будет Oxford OXuPCI952-LG (карта была Exsys EX-44092)

 

другие чипы, которые может быть интересно протестировать

Sunix SUN2212

ITE IT8728F

Asix MCS9922CV-AA

Axix MCS9901CV-CC

Asix AX99100

SystemBase SB16C1052PCI

 

 

 

 

Interesting conclusion. I'll try looking for cards on these chips and buy some. This will be an interesting experiment. I'll keep you posted.

Link to post
Share on other sites
  • 0

I found the following in China:

 

Asix AX99100 (Specified chip ASIX/AX99100b)

Asix MCS9922CV-AA (Specified chip MCS9922CV. Support for the Linux kernel 2.6.11 and higher is explicitly specified here.)

 

Interestingly, the second one costs almost three times as much. I don't know why. He probably still knows how to make hot cakes in the morning. 😄

I will order the Board on the AX99100 chip for now. For the experiment. The PCI-e Board will come to me in about a month. Then I'll let you know what happened.

 

If it doesn't work out, then I will order an expensive Board on the MCS9922CV chip. But I think the community should support cheap device drivers. We're here mainly because we can't afford expensive devices.

Edited by allex
Link to post
Share on other sites
  • 0
6 hours ago, allex said:

I'll try looking for cards on these chips and buy some.

the chips are all from cards i found online, most of them www.startech.com

some  www.delock.com and amazon.com

 

maybe wait with buying a little until i had a look into the kernel config

also its not that important, only very few people use a 0-modem cable

 

5 hours ago, allex said:

But I think the community should support cheap device drivers.

 

the one we have now is really affordable

 

5 hours ago, allex said:

We're here mainly because we can't afford expensive devices.

 

when i see some of the build's here i'm not so sure about that :-)

(40GBit nic's, 24 slots all flash and people asking for more slots then 24 - maybe i should compile the 100GBit intel ice E800 driver too)

 

 

 

 

  • Like 1
Link to post
Share on other sites
  • 0
On 11/6/2020 at 1:57 PM, allex said:

I found the following in China:

 

i had a look and there is only "8250/16550 PCI device Support" in the kernel

so whatever is in the kernel driver 8250 will be supported

/drivers/tty/serial/8250/8250_pci.c contains a vendor and device list

the following list contains the vendor id as text and the device id a number

(the list are actually sub device id's so its not a complete list but at least whats on the list should work)

the list for kernel 3.10.105 will be the interesting one because whats in there will also work on 4.4.59

also we are looking for a pcie card, not pci (WCH CH352/353 seems to be PCI)

 

Spoiler

#define PCI_VENDOR_ID_SBSMODULARIO    0x124B
#define PCI_SUBVENDOR_ID_SBSMODULARIO    0x124B
#define PCI_DEVICE_ID_OCTPRO        0x0001
#define PCI_SUBDEVICE_ID_OCTPRO232    0x0108
#define PCI_SUBDEVICE_ID_OCTPRO422    0x0208
#define PCI_SUBDEVICE_ID_POCTAL232    0x0308
#define PCI_SUBDEVICE_ID_POCTAL422    0x0408
#define PCI_SUBDEVICE_ID_SIIG_DUAL_00    0x2500
#define PCI_SUBDEVICE_ID_SIIG_DUAL_30    0x2530
#define PCI_VENDOR_ID_ADVANTECH        0x13fe
#define PCI_DEVICE_ID_INTEL_CE4100_UART 0x2e66
#define PCI_DEVICE_ID_ADVANTECH_PCI3620    0x3620
#define PCI_DEVICE_ID_TITAN_200I    0x8028
#define PCI_DEVICE_ID_TITAN_400I    0x8048
#define PCI_DEVICE_ID_TITAN_800I    0x8088
#define PCI_DEVICE_ID_TITAN_800EH    0xA007
#define PCI_DEVICE_ID_TITAN_800EHB    0xA008
#define PCI_DEVICE_ID_TITAN_400EH    0xA009
#define PCI_DEVICE_ID_TITAN_100E    0xA010
#define PCI_DEVICE_ID_TITAN_200E    0xA012
#define PCI_DEVICE_ID_TITAN_400E    0xA013
#define PCI_DEVICE_ID_TITAN_800E    0xA014
#define PCI_DEVICE_ID_TITAN_200EI    0xA016
#define PCI_DEVICE_ID_TITAN_200EISI    0xA017
#define PCI_DEVICE_ID_TITAN_200V3    0xA306
#define PCI_DEVICE_ID_TITAN_400V3    0xA310
#define PCI_DEVICE_ID_TITAN_410V3    0xA312
#define PCI_DEVICE_ID_TITAN_800V3    0xA314
#define PCI_DEVICE_ID_TITAN_800V3B    0xA315
#define PCI_DEVICE_ID_OXSEMI_16PCI958    0x9538
#define PCIE_DEVICE_ID_NEO_2_OX_IBM    0x00F6
#define PCI_DEVICE_ID_PLX_CRONYX_OMEGA    0xc001
#define PCI_DEVICE_ID_INTEL_PATSBURG_KT 0x1d3d
#define PCI_VENDOR_ID_WCH        0x4348
#define PCI_DEVICE_ID_WCH_CH352_2S    0x3253
#define PCI_DEVICE_ID_WCH_CH353_4S    0x3453
#define PCI_DEVICE_ID_WCH_CH353_2S1PF    0x5046
#define PCI_DEVICE_ID_WCH_CH353_2S1P    0x7053
#define PCI_VENDOR_ID_AGESTAR        0x5372
#define PCI_DEVICE_ID_AGESTAR_9375    0x6872
#define PCI_VENDOR_ID_ASIX        0x9710
#define PCI_DEVICE_ID_COMMTECH_4224PCIE    0x0020
#define PCI_DEVICE_ID_COMMTECH_4228PCIE    0x0021
#define PCI_DEVICE_ID_COMMTECH_4222PCIE    0x0022
#define PCI_DEVICE_ID_BROADCOM_TRUMANAGE 0x160a

#define PCI_VENDOR_ID_SUNIX        0x1fd4
#define PCI_DEVICE_ID_SUNIX_1999    0x1999

#define PCI_SUBDEVICE_ID_UNKNOWN_0x1584    0x1584
#define PCI_SUBDEVICE_ID_UNKNOWN_0x1588    0x1588

 

 

Spoiler

 

#define PCI_VENDOR_ID_SBSMODULARIO    0x124B
#define PCI_SUBVENDOR_ID_SBSMODULARIO    0x124B
#define PCI_DEVICE_ID_OCTPRO        0x0001
#define PCI_SUBDEVICE_ID_OCTPRO232    0x0108
#define PCI_SUBDEVICE_ID_OCTPRO422    0x0208
#define PCI_SUBDEVICE_ID_POCTAL232    0x0308
#define PCI_SUBDEVICE_ID_POCTAL422    0x0408
#define PCI_SUBDEVICE_ID_SIIG_DUAL_00    0x2500
#define PCI_SUBDEVICE_ID_SIIG_DUAL_30    0x2530
#define PCI_VENDOR_ID_ADVANTECH        0x13fe
#define PCI_DEVICE_ID_INTEL_CE4100_UART 0x2e66
#define PCI_DEVICE_ID_ADVANTECH_PCI3620    0x3620
#define PCI_DEVICE_ID_ADVANTECH_PCI3618    0x3618
#define PCI_DEVICE_ID_ADVANTECH_PCIf618    0xf618
#define PCI_DEVICE_ID_TITAN_200I    0x8028
#define PCI_DEVICE_ID_TITAN_400I    0x8048
#define PCI_DEVICE_ID_TITAN_800I    0x8088
#define PCI_DEVICE_ID_TITAN_800EH    0xA007
#define PCI_DEVICE_ID_TITAN_800EHB    0xA008
#define PCI_DEVICE_ID_TITAN_400EH    0xA009
#define PCI_DEVICE_ID_TITAN_100E    0xA010
#define PCI_DEVICE_ID_TITAN_200E    0xA012
#define PCI_DEVICE_ID_TITAN_400E    0xA013
#define PCI_DEVICE_ID_TITAN_800E    0xA014
#define PCI_DEVICE_ID_TITAN_200EI    0xA016
#define PCI_DEVICE_ID_TITAN_200EISI    0xA017
#define PCI_DEVICE_ID_TITAN_200V3    0xA306
#define PCI_DEVICE_ID_TITAN_400V3    0xA310
#define PCI_DEVICE_ID_TITAN_410V3    0xA312
#define PCI_DEVICE_ID_TITAN_800V3    0xA314
#define PCI_DEVICE_ID_TITAN_800V3B    0xA315
#define PCI_DEVICE_ID_OXSEMI_16PCI958    0x9538
#define PCIE_DEVICE_ID_NEO_2_OX_IBM    0x00F6
#define PCI_DEVICE_ID_PLX_CRONYX_OMEGA    0xc001
#define PCI_DEVICE_ID_INTEL_PATSBURG_KT 0x1d3d
#ifdef CONFIG_SYNO_PURLEY_SERIAL_OVER_LAN
#define PCI_DEVICE_ID_INTEL_LEWISBURG_KT 0xa1fb
#endif  
#define PCI_VENDOR_ID_WCH        0x4348
#define PCI_DEVICE_ID_WCH_CH352_2S    0x3253
#define PCI_DEVICE_ID_WCH_CH353_4S    0x3453
#define PCI_DEVICE_ID_WCH_CH353_2S1PF    0x5046
#define PCI_DEVICE_ID_WCH_CH353_1S1P    0x5053
#define PCI_DEVICE_ID_WCH_CH353_2S1P    0x7053
#define PCI_VENDOR_ID_AGESTAR        0x5372
#define PCI_DEVICE_ID_AGESTAR_9375    0x6872
#define PCI_VENDOR_ID_ASIX        0x9710
#define PCI_DEVICE_ID_COMMTECH_4224PCIE    0x0020
#define PCI_DEVICE_ID_COMMTECH_4228PCIE    0x0021
#define PCI_DEVICE_ID_COMMTECH_4222PCIE    0x0022
#define PCI_DEVICE_ID_BROADCOM_TRUMANAGE 0x160a
#define PCI_DEVICE_ID_AMCC_ADDIDATA_APCI7800 0x818e
#define PCI_DEVICE_ID_INTEL_QRK_UART    0x0936

#define PCI_VENDOR_ID_SUNIX        0x1fd4
#define PCI_DEVICE_ID_SUNIX_1999    0x1999

#define PCIE_VENDOR_ID_WCH        0x1c00
#define PCIE_DEVICE_ID_WCH_CH382_2S1P    0x3250
#define PCIE_DEVICE_ID_WCH_CH384_4S    0x3470
#define PCIE_DEVICE_ID_WCH_CH382_2S    0x3253

#define PCI_VENDOR_ID_PERICOM            0x12D8
#define PCI_DEVICE_ID_PERICOM_PI7C9X7951    0x7951
#define PCI_DEVICE_ID_PERICOM_PI7C9X7952    0x7952
#define PCI_DEVICE_ID_PERICOM_PI7C9X7954    0x7954
#define PCI_DEVICE_ID_PERICOM_PI7C9X7958    0x7958

#define PCI_VENDOR_ID_ACCESIO            0x494f
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_2SDB    0x1051
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM_2S    0x1053
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_4SDB    0x105C
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM_4S    0x105E
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM232_2DB    0x1091
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM232_2    0x1093
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM232_4DB    0x1099
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM232_4    0x109B
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_2SMDB    0x10D1
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM_2SM    0x10D3
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_4SMDB    0x10DA
#define PCI_DEVICE_ID_ACCESIO_MPCIE_COM_4SM    0x10DC
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM485_1    0x1108
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM422_2    0x1110
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM485_2    0x1111
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM422_4    0x1118
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM485_4    0x1119
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM_2S    0x1152
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM_4S    0x115A
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM232_2    0x1190
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM232_2    0x1191
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM232_4    0x1198
#define PCI_DEVICE_ID_ACCESIO_MPCIE_ICM232_4    0x1199
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM_2SM    0x11D0
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM422_4    0x105A
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM485_4    0x105B
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM422_8    0x106A
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM485_8    0x106B
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM232_4    0x1098
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM232_8    0x10A9
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_4SM    0x10D9
#define PCI_DEVICE_ID_ACCESIO_PCIE_COM_8SM    0x10E9
#define PCI_DEVICE_ID_ACCESIO_PCIE_ICM_4SM    0x11D8

#define PCI_SUBDEVICE_ID_UNKNOWN_0x1584    0x1584
#define PCI_SUBDEVICE_ID_UNKNOWN_0x1588    0x1588

 

Edited by IG-88
Link to post
Share on other sites
  • 0
Цитата

 

maybe wait with buying a little until i had a look into the kernel config

also its not that important, only very few people use a 0-modem cable

 

 

I already ordered. :) Let me have it. Suddenly it will work.

Link to post
Share on other sites
  • 0
On 11/6/2020 at 1:57 PM, allex said:

I will order the Board on the AX99100 chip for now. For the experiment. The PCI-e Board will come to me in about a month. Then I'll let you know what happened.

 

i stumbled across a list of DIGITUS IO controllers and had closer look about the vendor and device id

it was this two

 

ASIX AX99100 PCIe to Multi I/O Controller
125b:9100

 

MosChip MCS9901 PCIe 9901 Multi-I/O Controller
9710:9901

 

the vendor id 9710 is in the tty 8250 drivers of kernel 3.10.105 as ASIX (like in the list above) with device id "any" in the source code and as you ordered the AX99100 i did order a card with the MCS9901 (might have the higher chance of working with 3.10.105)

i will get that one in a few days so we might have results soon

Edited by IG-88
Link to post
Share on other sites
  • 0
13 часа назад, IG-88 сказал:

 

i stumbled across a list of DIGITUS IO controllers and had closer look about the vendor and device id

it was this two

 

ASIX AX99100 PCIe to Multi I/O Controller
125b:9100

 

MosChip MCS9901 PCIe 9901 Multi-I/O Controller
9710:9901

 

the vendor id 9710 is in the tty 8250 drivers of kernel 3.10.105 as ASIX (like in the list above) with device id "any" in the source code and as you ordered the AX99100 i did order a card with the MCS9901 (might have the higher chance of working with 3.10.105)

i will get that one in a few days so we might have results soon

 

I got the card I ordered yesterday. I'll try to get to my computer next week and test this card. I'll report the results and take a photo of the card.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.