Actions
Forum Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 353 subscribers
  • Views 764 views
  • Users 0 members are here
Related

How do I login to Pulsar Linux on Microzed?

shanedora

I just booted the pulsar linux image that came with my microzed board. I went ahead and setup minicom so I could see the boot process. My host computer is a laptop running CentOS 7 (NOT WINDOWS). It's giving me a login prompt as such...

cube-10-12-15-cube-server login:

On the pulsar linux getting started guide it says to use the credials at the login prompt

root:incendia

Minicom doesn't let me type in anything. So how am I suppose to log in to it? Where are these instructions at? Can I setup a ssh session and if so where are the instructions for this? Direct links much appreciated in setting up a ssh session.

A few restrictions are...

I cannot plug this board into a modem. I need to plug the zed into my laptop which is connected to wifi.

~S

Parents
  • 0

    I'm going to add something to this post real quick as part of the solution I found. Zedhead provided me with a great post on configuring minicom and udev rules on a linux box. However, in that post you'll need to change a few things based on your enviornment.

    First, verify the product and vendor id of your device. The id that is listed in the post is specific to their board. You can accomplish this as...
    lsusb
    The first 4 hex characters are the vendor id and the last are the product id. Therefore, the vendor id in "10c4:ea60" would be "10c4" and the product ID would be "ea60".

    Second, I have no idea who this AES_CM user is that is being referenced in the following command from that post...
    sudo usermod -a -G dialout AES_CM
    This username I'm assuming is that person's personal username???? I've always added myself to the dialout group so if your username is billyBobBlue then issue...
    sudo usermod -a -G dialout billyBobBlue

     

Reply
  • 0

    I'm going to add something to this post real quick as part of the solution I found. Zedhead provided me with a great post on configuring minicom and udev rules on a linux box. However, in that post you'll need to change a few things based on your enviornment.

    First, verify the product and vendor id of your device. The id that is listed in the post is specific to their board. You can accomplish this as...
    lsusb
    The first 4 hex characters are the vendor id and the last are the product id. Therefore, the vendor id in "10c4:ea60" would be "10c4" and the product ID would be "ea60".

    Second, I have no idea who this AES_CM user is that is being referenced in the following command from that post...
    sudo usermod -a -G dialout AES_CM
    This username I'm assuming is that person's personal username???? I've always added myself to the dialout group so if your username is billyBobBlue then issue...
    sudo usermod -a -G dialout billyBobBlue

     

Children
No Data