<p>AIDA was relocated, and now I want to power it on to do some tests. However, I cannot get the Rly16 service running.</p>
<p>Specifically, after powering up the entire AIDA system, on aidas1 PC, I cannot connect to the raspberry pi (nnrpi1) via a web browser<br />
<br />
http://nnrpi1:8015/AIDA/Rly16/<br />
<br />
The following elog may be relevant: https://elog.ph.ed.ac.uk/AIDA/58<br />
<br />
Now I am ssh'd to nnrpi1 via aidas1<br />
<br />
% dmesg | grep -A 3 USB0<br />
[ 8.970098] usb 1-1.3: pl2303 converter now attached to ttyUSB0<br />
[ 9.012479] usb 1-1.2.2: Detected FT232RL<br />
[ 9.178208] usb 1-1.2.2: FTDI USB Serial Device converter now attached to ttyUSB1<br />
[ 9.348288] ftdi_sio 1-1.2.3:1.0: FTDI USB Serial Device converter detected<br />
<br />
So, I will try Patrick's workaround in elog #58<br />
<br />
I tried it, though it's hard to know if it is done correctly. Which item is which? Or more importantly, which one runs Rly16?<br />
<br />
[ 8.107290] usb 1-1.2.3: USB disconnect, device number 8<br />
[ 8.261338] usbserial: USB Serial support registered for FTDI USB Serial Device<br />
[ 8.541012] ftdi_sio 1-1.2.2:1.0: FTDI USB Serial Device converter detected<br />
[ 8.712409] usb 1-1.2.2: Detected FT232RL<br />
[ 8.847955] usb 1-1.2.2: FTDI USB Serial Device converter now attached to ttyUSB0<br />
[ 12.252576] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)<br />
[ 12.728966] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)<br />
[ 23.695562] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup<br />
[ 25.212043] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1<br />
[ 32.372015] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:2134012k SSFS<br />
[ 109.219022] usb 1-1.2.3: new full-speed USB device number 9 using dwc_otg<br />
[ 109.335538] usb 1-1.2.3: New USB device found, idVendor=0403, idProduct=6001<br />
[ 109.335579] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
[ 109.335601] usb 1-1.2.3: Product: USB <-> Serial<br />
[ 109.335619] usb 1-1.2.3: Manufacturer: FTDI<br />
[ 109.354420] ftdi_sio 1-1.2.3:1.0: FTDI USB Serial Device converter detected<br />
[ 109.354761] usb 1-1.2.3: Detected FT232BM<br />
[ 109.356174] usb 1-1.2.3: FTDI USB Serial Device converter now attached to ttyUSB1<br />
[ 163.939476] usb 1-1.3: new full-speed USB device number 10 using dwc_otg<br />
[ 164.042348] usb 1-1.3: New USB device found, idVendor=067b, idProduct=2303<br />
[ 164.042424] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
[ 164.042446] usb 1-1.3: Product: USB-Serial Controller D<br />
[ 164.042468] usb 1-1.3: Manufacturer: Prolific Technology Inc. <br />
[ 164.096379] usbcore: registered new interface driver pl2303<br />
[ 164.098786] usbserial: USB Serial support registered for pl2303<br />
[ 164.099085] pl2303 1-1.3:1.0: pl2303 converter detected<br />
[ 164.106666] usb 1-1.3: pl2303 converter now attached to ttyUSB2<br />
<br />
On ttyUSB# have:<br />
FT232RL<br />
FT232BM<br />
pl2303<br />
<br />
<br />
% lsusb<br />
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. <br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. <br />
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB<br />
Bus 001 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port<br />
Bus 001 Device 005: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse<br />
Bus 001 Device 007: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard<br />
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC<br />
Bus 001 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC<br />
<br />
N.B. USB-serial link to FEE64 is not connected to anything on the serial side. What is the FEE64 Console? See Attachment 1. It goes to nothing! Should it go somewhere?</p> |