| 1 |
On 03/24 06:35, Nuno Silva wrote: |
| 2 |
> On 2019-03-24, tuxic@××××××.de wrote: |
| 3 |
> |
| 4 |
> > Hi, |
| 5 |
> > |
| 6 |
> > In my PC there is a quad uart PCIe-adapter with Oxford Chipset. |
| 7 |
> > With lspci it is listed as: |
| 8 |
> > 04:00.0 Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 0 (Uart) |
| 9 |
> > and |
| 10 |
> > 04:00.1 Bridge: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 1 (8bit bus) |
| 11 |
> > |
| 12 |
> > I have a DAUP9-cable, which connects the serial port to the FBUS/MBUS |
| 13 |
> > of my NOKIA 3310 (2001). |
| 14 |
> > |
| 15 |
> > I cannot speak to my NOKI handy via gammu/gnokii: Timeout |
| 16 |
> > |
| 17 |
> > To minimize the number of variables in this equitation I would like to |
| 18 |
> > ensure, that at least the UART adapter is working. |
| 19 |
> > |
| 20 |
> > The modules loaded by now are: |
| 21 |
> [...] |
| 22 |
> > Do I miss a driver? |
| 23 |
> > Is there any kind of check or test (without using another serial |
| 24 |
> > thingy, which I do not have), to test the UART adapter is working as |
| 25 |
> > expected? |
| 26 |
> |
| 27 |
> The output of "lspci -k" is probably useful to check whether the device |
| 28 |
> was picked up by some driver. It will also show drivers which are not |
| 29 |
> modules. |
| 30 |
> |
| 31 |
> Does it show any driver name for that UART controller? |
| 32 |
> |
| 33 |
> -- |
| 34 |
> Nuno Silva |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
Hi All, |
| 39 |
|
| 40 |
thanks you all for the helpful informations. |
| 41 |
As it turns out....the adapter cable was wrongly |
| 42 |
soldered by the company...it could not work. |
| 43 |
|
| 44 |
The infos will help me, when the new cable will arrive I am sure. |
| 45 |
|
| 46 |
Cheers! |
| 47 |
Meino |
Archives