APU set up with Wi-Fi



  • Hi, I'm continuing on from this pfSense thread.

    I bought an
    APU (not an ALIX) and an
    APU cover.

    I think I need to buy a power supply with 12V and 1 or 2 Amps and 2.5mm plug.
    I would also like Wi-Fi if it can be done.

    How do I install pfSense onto the APU. I think I need to buy a mini SD or SD for 4GB or 8GB.
    How do I install the pfSense to the APU then?

    Then I can remove my old Linksys Wi-Fi router with 4 Ethernet port and my 3 port Switch.
    Does anyone know of a good 12-48 port switch for home use?

    Also, I'm thinking of upgrading to a fanless silent server with low 20-30 Watt power needs.
    Any suggestions?



  • Okay, so I bought an 8GB Transcend microSDHD with SD adapter.
    Specs are up to 20 MB/s 133X, Class 10.

    Will pfSense run on this SD card, or do I need a Compact Flash card?



  • Well, plugged APU in with SD card with img.gz, but can't plug my monitor's 15 pin male VGA cable into the APU serial port 9 pin male.

    Haven't found an adaptor yet, anyone know a solution to this?



  • Ok, ordered a bunch of cables:
    Serial port 9 pin female to female adaptor.
    Serial port 9 pin male to VGA port 15 pin male.
    VGA port 15 pin female to female adaptor.

    Once arrived, hopefully my monitor will connect to the APU and see the cli to install pfSense from the SD card.


  • Moderator

    No no no. Stop! You are doing it wrong ;)

    The serial port is NOT an VGA port. Never ever. That is a console port. And to install pfsense on an APU, just search the forums for the APU topics already out there explaining what to do. To summarize:

    • you need to write the appropriate image to the SD card. as the APU has NO video out, you need a console-only nano-BSD version. I'd recommend the 4GB nanobsd image.
    • go to https://www.pfsense.org/download/mirror.php?section=downloads
    • select: 64bit, embedded, no vga / serial console (9-port SERIAL port), card size 4GB
    • download
    • to write the image to your sd card, use something like http://m0n0.ch/wall/physdiskwrite.php (the one with gui for example), watch out that you select the right target!
    • after the image is written correctly, put it into the apu
    • boot

    Another option would be to use a simple small usb stick and the live-boot image (amd64, live-cd with installer on usb memstick, serial!) and write that image to an usb stick with sth like http://sourceforge.net/projects/win32diskimager/

    What you need to actually see the output of your APU in case sth goes wrong is a "Serial Console cable". Do NOT put a VGA port with any kinds of adapters on that port, you may or may not damage your video port or the device!
    Read about that on https://doc.pfsense.org/index.php/Console_Types
    What you can use if you don't have a serial port on your PC or notebook is a USB to serial port adapter or cable. Like http://www.amazon.com/Manhattan-Serial-Converter-Connects-205146/dp/B0007OWNYA/

    Please don't "assume" things like console/VGA as that may simply damage your device. Read the forums ahead of ordering! :)

    Greets



  • A serial to USB adapter is good, but you will also need a f2f NULL modem adapter such as this one.


  • Moderator

    @forbiddenlake: No you don't. What would you need that for? I'm using a USB/Serial Adapter for WRAP, ALIX and APUs all the time. There is no need for a gender changer whatsoever. If you need one, you have the wrong cable. All I need from time to time is a serial 9-port to RJ-45 adapter for those devices that use RJ-45 as easier (and smaller) ways to build console ports into their devices (such as cisco, lanner inc. devices, etc.).

    Greets


  • Netgate Administrator

    Yes you do.
    Or at least every serial console I've ever used required a null modem cable. A USB to serial adapter, such as the one you linked to, gives you a male 9-pin serial port such as you would have found on the back of a PC 10 years ago. The console port on most hardware, including the APU, is also male. You need a cable that both changes the gender and cross connects the Tx and Rx lines; a null-modem cable.

    Steve



  • @JeGr yes you do, as stephenw wrote.  Also because I bought a f2f straight adapter and it didn't work, then I researched further, bought a f2f null modem adapter, and it worked.


  • Moderator

    @stephen: Or at least every serial console I've ever used required a null modem cable.
    @forbiddenlage: yes you do

    Guys please. I don't want to argue, but give me the benefit of the doubt. And read what I wrote:

    What you need to actually see the output of your APU in case sth goes wrong is a "Serial Console cable".
    -> That is per se known as null modem cable.

    What you can use if you don't have a serial port on your PC or notebook is a USB to serial port adapter
    -> That is the one you are arguing over, that it needs some converter/adapter.

    Why? You take that stupid USB2Serial thing, plug it in, and take your console cable and plug it into the converter (that's what it is, a converter) and your board (WRAP, ALIX, APU, Lanner, whatever). So please give me the point that I know what I'm doing. I didn't mention any "strange" f2f or other adapters because the TS already seemed awfully confused over the nature of a console port in difference of a VGA port. And because me personally don't like any strange f2m/m2m/f2f adapters as they are - in most cases - calling for errors or strange happenings.

    That's why I was suggesting going the classic route by using a standard 9port console/nullmodem cable and a usb2serial adapter.

    Let's agree we all talk about the same and stop irritating the TS and other readers from this topic to buy any strange adapters or converters that perhaps won't function the way they want. OK? :D

    Cheers


  • Netgate Administrator

    I agree we are talking the same thing.  :) We must be since all three of us have used a console cable and are aware of what's required.

    Reading back through it I can see where the confusion started. Forbiddenlake said you need an adapter as well as a USB-Serial converter, which is true you do. You had already stated you need a console cable which is the same thing. However you then wrote 'no you don't' meaning you don't need the adapter as well as the console cable. I then misinterpreted that as you saying you don't need any sort of adapter.  ::)

    Anyway just to be clear you need a null-modem cable also known as a console cable (the null-modem adapter is the same thing but shorter) and, if you don't have a serial port, you need a USB-serial converter.

    Steve


  • Moderator

    Agreed :D



  • The Serial-USB and serial female-serial female cables arrived.
    Micro SD 4GB card with the pfSense-2.1.2-RELEASE-4g-amd64-nanobsd-20140410-0542.img downloaded onto it,
    I bought a 12V 1.5A power supply but no power to ALU?
    Specs/tutorial for building the APU say a power supply of 1 - 2 Amps should be fine.

    Plugged serial-USB cable into
    serial female-serial-female to ALU serial male port and into
    computer's USB port, but computer recognises no USB?

    Ok, tested power supply using a multimeter.
    Red cable plugged into VOhmmA
    Black cable plugged into COM.
    Yellow dial turned to 750 V AC.

    Black cable pushed into the inside of the 2.5mm power supply connector (positive).
    Red cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: HV 026.

    Red cable pushed into the inside of the 2.5mm power supply connector (positive).
    Black cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: HV 000.


  • Netgate Administrator

    Your power supply is almost certainly fine. To test the output with a multimeter you need to be on the correct range (if it's not auto-ranging). The '750V AC' setting is for measuring high voltage AC, such as the Volts at a wall socket. To measure the PSU, which is 12V DC, you need a low voltage DC setting. Typically that would be 20V DC or sometimes written 19V DC since the display can only read to 19.99V.
    The output plug of the PSU is usually 'centre positive' so the red lead should go down the center of the connector.

    Do you have links to the actual cables you bought?
    If the computer is not detecting the USB cable then it can't work. What OS is running on the terminal computer?

    Steve



  • Thanks for the help.

    Multimeter yellow dial set to 20V.

    Black cable pushed into the inside of the 2.5mm power supply connector (positive).
    Red cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: 12.1.

    Red cable pushed into the inside of the 2.5mm power supply connector (positive).
    Black cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: - 12.1.

    Serial female to female cable.

    Serial male to USB.

    So yes, it seems the power supply is working.
    No life at all on the APU?
    Maybe the APU needs a trick like connecting an Ethernet cable or powering up and then putting the microSD card in the APU?


  • Netgate Administrator

    Ok, check the leads at the multimeter end. The black lead is definitely in the COM connector and the red lead in the ' VOhmmA' connector?

    Just as an aside here, I'm not sure how familiar with meters you are, do not put the red lead in the other connector, usually marked '10A', unless you know what you're doing. It's so very easy to kill powersupplies doing that!  ;)

    If the leads are correct then it looks like your power supply is wired 'centre negative' which is incorrect:

    @http://pcengines.ch/apu1c.htm:

    12V DC, about 6 to 12W depending on CPU load. Jack = 2.5 mm, center positive

    Maybe you typo'd the results? Where did you source the PSU?

    Steve



  • So
    the power supply cable tip had the negative cable end with the 2.5mm metal positive.
    the power supply cable tip had the positive cable end with the 2.5mm metal negative.

    I changed
    the power supply cable tip with the negative end with the 2.5mm metal negative.
    The power supply cable tip with the positive end with the 2.5mm metal positive.

    Black cable pushed into the inside of the 2.5mm power supply connector (positive).
    Red cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: -12.13.

    Red cable pushed into the inside of the 2.5mm power supply connector (positive).
    Black cable touching the outside of the 2.5mm power supply connector (negative).
    Multimeter result: 12.13.

    The ALU now shows a green LED light on the MOBO D7, D10 and D11.

    The computer isn't showing any recognition of a USB connection.
    My OS is Linux Mint 16 Mate 64-bit.


  • Netgate Administrator

    You'll have to check the logs in Mint to see what it made of the cable. It could be some obscure converter chip.

    Steve



  • Ok, not sure how to find logs on Linux Mint 16.
    I went to /var/log, but nothing really re USBs?

    I'm wondering if the MicroSD card is causing the pfSense OS to somehow not load and 'awaken' the USB port?
    The MicroSD card has pfSense-2.1.2-RELEASE-4g-amd64-nanobsd-20140410-0542.img on it.
    I downloaded this file from pfSense download
      > Computer Architecture: AMD64 (64-bit) > Platform: Embedded (NanoBSD) typically with CF > Console: Serial > CF card size: 4GB.


  • Moderator

    Logs are usually in the /var/log directory


  • Moderator

    USB logs should be in /var/log/messages

    You can run a tail -f /var/log/messages which is a live display of the log. Or use a cat or vi command to see the log



  • Thanks for the suggestions.

    /var/log has no directory or file names messages?

    Just these ones:

    
    /var/log $ ls
    alternatives.log       auth.log.4.gz  dpkg.log        kern.log.2.gz          pm-powersave.log.3.gz  teamviewer
    alternatives.log.1     boot.log       dpkg.log.1      kern.log.3.gz          pm-powersave.log.4.gz  udev
    alternatives.log.2.gz  bootstrap.log  dpkg.log.2.gz   kern.log.4.gz          pycentral.log          ufw.log
    alternatives.log.3.gz  btmp           dpkg.log.3.gz   lastlog                samba                  unattended-upgrades
    alternatives.log.4.gz  btmp.1         dpkg.log.4.gz   mail.err               speech-dispatcher      upstart
    alternatives.log.5.gz  ConsoleKit     dpkg.log.5.gz   mail.log               syslog                 vbox-install.log
    apt                    cups           faillog         mdm                    syslog.1               wtmp
    aptitude               dmesg          fontconfig.log  mintsystem.log         syslog.2.gz            wtmp.1
    aptitude.1.gz          dmesg.0        fsck            mintUpdate.history     syslog.3.gz            Xorg.0.log
    auth.log               dmesg.1.gz     hp              news                   syslog.4.gz            Xorg.0.log.old
    auth.log.1             dmesg.2.gz     installer       pm-powersave.log       syslog.5.gz            Xorg.20.log
    auth.log.2.gz          dmesg.3.gz     kern.log        pm-powersave.log.1     syslog.6.gz            Xorg.20.log.old
    auth.log.3.gz          dmesg.4.gz     kern.log.1      pm-powersave.log.2.gz  syslog.7.gz
    
    

  • Moderator

    Try dmesg | grep -i usb



  • Results are:

    
    /var/log $ dmesg | grep -i usb
    [    0.116162] ACPI: bus type USB registered
    [    0.116175] usbcore: registered new interface driver usbfs
    [    0.116181] usbcore: registered new interface driver hub
    [    0.116199] usbcore: registered new device driver usb
    [    0.554559] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    0.554638] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    [    0.568048] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    [    0.568070] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.568071] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.568073] usb usb1: Product: EHCI Host Controller
    [    0.568074] usb usb1: Manufacturer: Linux 3.11.0-12-generic ehci_hcd
    [    0.568075] usb usb1: SerialNumber: 0000:00:1a.0
    [    0.568145] hub 1-0:1.0: USB hub found
    [    0.568273] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [    0.584052] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [    0.584067] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.584069] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.584070] usb usb2: Product: EHCI Host Controller
    [    0.584072] usb usb2: Manufacturer: Linux 3.11.0-12-generic ehci_hcd
    [    0.584073] usb usb2: SerialNumber: 0000:00:1d.0
    [    0.584127] hub 2-0:1.0: USB hub found
    [    0.584186] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [    0.584191] uhci_hcd: USB Universal Host Controller Interface driver
    [    0.584239] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
    [    0.584432] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
    [    0.584434] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.584435] usb usb3: Product: xHCI Host Controller
    [    0.584437] usb usb3: Manufacturer: Linux 3.11.0-12-generic xhci_hcd
    [    0.584438] usb usb3: SerialNumber: 0000:04:00.0
    [    0.584492] hub 3-0:1.0: USB hub found
    [    0.584545] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 4
    [    0.584564] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
    [    0.584566] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    0.584567] usb usb4: Product: xHCI Host Controller
    [    0.584568] usb usb4: Manufacturer: Linux 3.11.0-12-generic xhci_hcd
    [    0.584570] usb usb4: SerialNumber: 0000:04:00.0
    [    0.584618] hub 4-0:1.0: USB hub found
    [    0.882942] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [    1.024631] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
    [    1.024636] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    1.024905] hub 1-1:1.0: USB hub found
    [    1.136210] usb 2-1: new high-speed USB device number 2 using ehci-pci
    [    1.268694] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
    [    1.268699] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    1.268976] hub 2-1:1.0: USB hub found
    [    1.340309] usb 1-1.6: new low-speed USB device number 3 using ehci-pci
    [    1.436570] usb 1-1.6: New USB device found, idVendor=04f3, idProduct=0230
    [    1.436572] usb 1-1.6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    [    1.436573] usb 1-1.6: Product: USB+PS/2 Optical Mouse
    [    1.539296] usbcore: registered new interface driver usbhid
    [    1.539298] usbhid: USB HID core driver
    [    1.604101] input: USB+PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input3
    [    1.604186] hid-generic 0003:04F3:0230.0001: input,hidraw0: USB HID v1.11 Mouse [USB+PS/2 Optical Mouse] on usb-0000:00:1a.0-1.6/input0
    [ 9232.342528] usb 2-1.2: new full-speed USB device number 3 using ehci-pci
    [ 9232.436085] usb 2-1.2: New USB device found, idVendor=1a86, idProduct=7523
    [ 9232.436090] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    [ 9232.436093] usb 2-1.2: Product: USB2.0-Ser!
    [ 9232.460808] usbcore: registered new interface driver usbserial
    [ 9232.460826] usbcore: registered new interface driver usbserial_generic
    [ 9232.460839] usbserial: USB Serial support registered for generic
    [ 9232.463155] usbcore: registered new interface driver ch341
    [ 9232.463175] usbserial: USB Serial support registered for ch341-uart
    [ 9232.466347] usb 2-1.2: ch341-uart converter now attached to ttyUSB0
    [14756.388091] usb 2-1.2: USB disconnect, device number 3
    [14756.388293] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
    [14757.476486] usb 1-1.6: USB disconnect, device number 3
    [14757.716443] usb 1-1.6: new low-speed USB device number 4 using ehci-pci
    [14757.812687] usb 1-1.6: New USB device found, idVendor=04f3, idProduct=0230
    [14757.812692] usb 1-1.6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    [14757.812695] usb 1-1.6: Product: USB+PS/2 Optical Mouse
    [14757.815407] input: USB+PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input11
    [14757.815597] hid-generic 0003:04F3:0230.0002: input,hidraw0: USB HID v1.11 Mouse [USB+PS/2 Optical Mouse] on usb-0000:00:1a.0-1.6/input0
    [14757.884482] usb 2-1.4: new full-speed USB device number 4 using ehci-pci
    [14757.977730] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523
    [14757.977735] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    [14757.977739] usb 2-1.4: Product: USB2.0-Ser!
    [14757.980085] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
    
    

    Maybe the memory card doesn't work?
    I think the APU is supposed to have a Compact Flash 4GB card, but I have a MicroSD card 4GB?



  • So, just ordered a new Serial female to female adaptor, in case the current serial female to female cable is faulty.

    I also removed the APU's microSD 8GB card > placed the microSD 8GB card into the memory card reader > placed the memory card reader into the computer's USB > opened the microSD 8GB card's folder > unzipped pfSense-2.1.2-RELEASE-4g-amd64-nanobsd.img.gz > deleted pfSense-2.1.2-RELEASE-4g-amd64-nanobsd.img.gz > kept the unzipped file pfSense-2.1.2-RELEASE-4g-amd64-nanobsd-20140410-0542.img > ejected the memory card reader > removed the microSD 8GB card from the memory card reader > placed the microSD 8GB card into the APU > powered on the APU > connected the APU into my computer's USB port > the computer is still not recognising any USB from the APU (the computer recognises other USB devices ok).

    I also tried the APU USB cable in another computer which recognised no USB when plugged into the 2nd computer.


  • Netgate Administrator

    Neither that adapter or the cable you linked to earlier are null-modem cables which is what you need. Something like this:
    http://www.ebay.com.au/itm/1-5m-Serial-RS232-Null-Modem-Cable-Female-to-Female-DB9-FTA-DB9F-F-/161195465404?pt=AU_CablesConnectors&hash=item2587ff9abc

    I assume you're in Australia. :)

    Try looking at the syslog in Mint:

    cat /var/log/syslog|grep usb
    

    or tail it whilst you plug in the cable:

    tail -f /var/log/syslog
    

    Steve



  • Thank you for the reply.

    Forgive my ignorance, but what is the difference between the
    null-modem cable and the
    serial female to female cable I bought or the
    serial female to female adaptor I bought?

    Not quite sure what I'm looking for with the below commands.
    I have included the output if it helps check the USB with the APU cable plugged in.

    
    $ cat /var/log/syslog | grep usb
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.342528] usb 2-1.2: new full-speed USB device number 3 using ehci-pci
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.436085] usb 2-1.2: New USB device found, idVendor=1a86, idProduct=7523
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.436090] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.436093] usb 2-1.2: Product: USB2.0-Ser!
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.460808] usbcore: registered new interface driver usbserial
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.460826] usbcore: registered new interface driver usbserial_generic
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.460839] usbserial: USB Serial support registered for generic
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.463155] usbcore: registered new interface driver ch341
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.463175] usbserial: USB Serial support registered for ch341-uart
    May 16 11:20:26 linuxmint-Z68MA-D2H-B3 kernel: [ 9232.466347] usb 2-1.2: ch341-uart converter now attached to ttyUSB0
    May 16 12:52:29 linuxmint-Z68MA-D2H-B3 kernel: [14756.388091] usb 2-1.2: USB disconnect, device number 3
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.476486] usb 1-1.6: USB disconnect, device number 3
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.716443] usb 1-1.6: new low-speed USB device number 4 using ehci-pci
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.812687] usb 1-1.6: New USB device found, idVendor=04f3, idProduct=0230
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.812692] usb 1-1.6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.812695] usb 1-1.6: Product: USB+PS/2 Optical Mouse
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.815407] input: USB+PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input11
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.815597] hid-generic 0003:04F3:0230.0002: input,hidraw0: USB HID v1.11 Mouse [USB+PS/2 Optical Mouse] on usb-0000:00:1a.0-1.6/input0
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.884482] usb 2-1.4: new full-speed USB device number 4 using ehci-pci
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.977730] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.977735] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.977739] usb 2-1.4: Product: USB2.0-Ser!
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 kernel: [14757.980085] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
    May 16 12:52:30 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4"
    May 16 16:08:16 linuxmint-Z68MA-D2H-B3 kernel: [26507.052035] usb 2-1.4: USB disconnect, device number 4
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 kernel: [26507.350341] usb 2-1.4: new full-speed USB device number 5 using ehci-pci
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 kernel: [26507.443614] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 kernel: [26507.443620] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 kernel: [26507.443623] usb 2-1.4: Product: USB2.0-Ser!
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 kernel: [26507.445789] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
    May 16 16:08:17 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4"
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.170560] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.263211] usb 2-1.2: New USB device found, idVendor=1e3d, idProduct=4082
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.263216] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=3
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.263219] usb 2-1.2: Product: Flash Disk
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.263222] usb 2-1.2: SerialNumber: 213244704081
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.285404] usb-storage 2-1.2:1.0: USB Mass Storage device detected
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.285464] scsi4 : usb-storage 2-1.2:1.0
    May 16 16:12:47 linuxmint-Z68MA-D2H-B3 kernel: [26778.285560] usbcore: registered new interface driver usb-storage
    May 16 16:25:17 linuxmint-Z68MA-D2H-B3 kernel: [27528.501341] usb 2-1.2: USB disconnect, device number 6
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.116191] usbcore: registered new interface driver usbfs
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.116197] usbcore: registered new interface driver hub
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.116215] usbcore: registered new device driver usb
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.568106] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.568108] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.568109] usb usb1: Product: EHCI Host Controller
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.568111] usb usb1: Manufacturer: Linux 3.11.0-12-generic ehci_hcd
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.568112] usb usb1: SerialNumber: 0000:00:1a.0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584106] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584108] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584109] usb usb2: Product: EHCI Host Controller
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584111] usb usb2: Manufacturer: Linux 3.11.0-12-generic ehci_hcd
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584112] usb usb2: SerialNumber: 0000:00:1d.0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584474] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584475] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584476] usb usb3: Product: xHCI Host Controller
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584478] usb usb3: Manufacturer: Linux 3.11.0-12-generic xhci_hcd
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584479] usb usb3: SerialNumber: 0000:04:00.0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584603] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584605] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584606] usb usb4: Product: xHCI Host Controller
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584608] usb usb4: Manufacturer: Linux 3.11.0-12-generic xhci_hcd
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.584609] usb usb4: SerialNumber: 0000:04:00.0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    0.882965] usb 1-1: new high-speed USB device number 2 using ehci-pci
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.024644] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.024649] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.136244] usb 2-1: new high-speed USB device number 2 using ehci-pci
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.268708] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.268713] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.340474] usb 1-1.6: new low-speed USB device number 3 using ehci-pci
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.436502] usb 1-1.6: New USB device found, idVendor=04f3, idProduct=0230
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.436507] usb 1-1.6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.436510] usb 1-1.6: Product: USB+PS/2 Optical Mouse
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.540529] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.567410] usbcore: registered new interface driver usbhid
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.567412] usbhid: USB HID core driver
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.632907] input: USB+PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input3
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.632972] hid-generic 0003:04F3:0230.0001: input,hidraw0: USB HID v1.11 Mouse [USB+PS/2 Optical Mouse] on usb-0000:00:1a.0-1.6/input0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.649389] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.649391] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    1.649393] usb 2-1.4: Product: USB2.0-Ser!
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.553345] usbcore: registered new interface driver usbserial
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.553546] usbcore: registered new interface driver usbserial_generic
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.553715] usbserial: USB Serial support registered for generic
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.556629] usbcore: registered new interface driver ch341
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.556857] usbserial: USB Serial support registered for ch341-uart
    May 16 16:27:36 linuxmint-Z68MA-D2H-B3 kernel: [    3.558988] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
    May 16 16:45:05 linuxmint-Z68MA-D2H-B3 kernel: [ 1052.238828] usb 2-1.4: USB disconnect, device number 3
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.119770] usb 2-1.2: new full-speed USB device number 4 using ehci-pci
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213050] usb 2-1.2: New USB device found, idVendor=1a86, idProduct=7523
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213056] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213059] usb 2-1.2: Product: USB2.0-Ser!
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.215761] usb 2-1.2: ch341-uart converter now attached to ttyUSB0
    
    
    
    $ tail -f /var/log/syslog
    May 16 20:53:51 linuxmint-Z68MA-D2H-B3 mate-screensaver-dialog: pam_ecryptfs: seteuid error
    May 16 20:59:16 linuxmint-Z68MA-D2H-B3 mate-screensaver-dialog: pam_ecryptfs: seteuid error
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.119770] usb 2-1.2: new full-speed USB device number 4 using ehci-pci
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213050] usb 2-1.2: New USB device found, idVendor=1a86, idProduct=7523
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213056] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213059] usb 2-1.2: Product: USB2.0-Ser!
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.213465] ch341 2-1.2:1.0: ch341-uart converter detected
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 mtp-probe: bus: 2, device: 4 was not an MTP device
    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.215761] usb 2-1.2: ch341-uart converter now attached to ttyUSB0
    
    

  • Netgate Administrator

    A null-modem cable has the transmit and receive lines crossed such that two machines with standard serial ports can talk to one another. A standard serial cable for connecting a PC to some other serial device does not.
    See:
    http://en.wikipedia.org/wiki/Null_modem

    It looks like your USB-serial adapter was recognised just fine:

    May 16 21:04:10 linuxmint-Z68MA-D2H-B3 kernel: [16602.215761] usb 2-1.2: ch341-uart converter now attached to ttyUSB0
    

    You should be able to open ttyUSB0 in a serial terminal emulator, like putty. In Xubuntu there is an issue where the user doesn't have permissions to access the serial port and putty gives no helpful errors or log entries. Nice  ::). The workaround is to add your user to the modem group. There may be a similar issues in Mint.

    Steve



  • Oh, great to see the APU is connecting via the USB port.

    So, I've tried a few ways to connect to the serial APU.

    Terminal > $ cu -1 /dev/ttyUSB0 -s 19200
    cu: /dev/ttyUSB0: System not found

    $ screen /dev/ttysUSB0 19200
    [screen is terminating]
    $ screen /dev/ttys0 19200
    [screen is terminating]

    $ minicom
    minicom: cannot open /dev/tty8: Permission denied

    $ sudo mincom
    Welcome to minicom 2.6.2

    OPTIONS: I18n
    Compiled on Feb  8 2013, 07:03:03.
    Port /dev/tty8, 22:05:36

    Press CTRL-A Z for help on special keys

    $ putty
    Serial line: /dev/ttyUSB0 > Speed: 9600 > PuTTY Fatal Error: Unable to open connection to: Unable to open serial port.


  • Netgate Administrator

    Right so you have the permissions error.
    Looks like it's the 'dialout' group you need to be added to. Try doing

    sudo adduser your_account_name dialout
    

    Then logout and back in again. Try Putty again.

    https://bugs.launchpad.net/ubuntu/+source/gtkterm/+bug/949597

    Steve



  • Yes, I did the line $ sudo adduser user_name dialout.

    Logging gives the same results?


  • Netgate Administrator

    Hmm, well that's all that's requiered in Xubuntu but Mint may be different (different versions of Mint too) but usually isn't because they're all Debian based.
    You may need to reboot if logging out and back in didn't do it.
    You may also need to do:

    sudo chmod a+rw /dev/ttyUSB0
    

    https://fedorahosted.org/fldigi/wiki/Documentation/HOWTO/Serial_Port_Setup

    Steve



  • Thanks. Yes, I had actually tried the chmod a+rw /dev/ttyUSB0, but same errors.

    I tried:
    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 9600 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 19200 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 38400 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 115200 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.


  • Netgate Administrator

    That is the expected behaviour if you're not connected to a serial console. Since your cable is not a null-modem you aren't seeing anything. Putty has a gui you can use to set the serial speed etc.

    Steve



  • Okay, I bought a Null Modem cable.
    Plugged into APU and USB cable.

    I tried:
    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 9600 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 19200 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 38400 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 115200 > Open > Black window opens with the Title /dev/ttyUSB0 - PuTTY and green blinking cursor, but unable to type anything.


  • Netgate Administrator

    Hmm. Well you clearly have some problem there. Do you have anything else you can use to prove the serial terminal with?

    Steve



  • I'm trying to think of a way of proving the serial terminal.
    All I can think of is
    trying another Null modem cable
    trying another computer's USB port. (I tried Linux, Mac and Windows).

    I thought the MicroSD 8GB card might not have the pfSense OS file properly, but I understand this would not effect the serial connection needed to configure the MicroSD 8GB card?


  • Netgate Administrator

    One simple way to test basic connectivity is to use a paper clip or short piece of wire to connect the Tx and Rx pins at the end of the null modem cable. Take the end of the null-modem cable (where it connects to the APU) and connect pins 2 and 3. See photo. Now when you open Putty, at any speed, you should see anything you type echoed back to you.

    Steve




  • Thanks, that's a handy test to try :-)

    I disconnected the Null Modem cable from the APU.
    I stuck a paper clip into the Null Modem cable pins 2 and 3.
    On my computer > Terminal > $ putty > putty window appears >
    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 9600 > Open > Black window opens with the Title putty and another windows opens with PuTTY Fatal Error. Unable to open connection to :  Unable to open serial port.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 19200 > Open > Black window opens with the Title putty and another windows opens with PuTTY Fatal Error. Unable to open connection to :  Unable to open serial port.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 38400 > Open > Black window opens with the Title putty and another windows opens with PuTTY Fatal Error. Unable to open connection to :  Unable to open serial port.

    Terminal > $ putty > Connection type: Serial > Serial line: /dev/ttyUSB0 > Speed: 115200 > Open > Black window opens with the Title putty and another windows opens with PuTTY Fatal Error. Unable to open connection to :  Unable to open serial port.


  • Netgate Administrator

    That's back to the permissions problem. Try chmodding the port again.

    Steve