Jump to content

Jens Bauer

Members
  • Posts

    208
  • Joined

  • Last visited

Everything posted by Jens Bauer

  1. Hi miguipda. Now we're talking! This is normal. PXE is network boot, so this is expected, as I'm pretty sure you didn't set up a netboot server. I think you can know that the Lamobo R1 got an IP address if you type some simple command on the command-line. Try for instance ping 192.168.1.1 (from the Lamobo R1, so the Lamobo R1 will ping your router). If it succeeds and sees your router, the Lamobo R1 *will* have an IP address. To find your IP address, there are several options. The most universal one is probably to use "ip addr show". You could simply enter ... ip addr show ... or if you know your subnet always starts with 192, you could filter it through grep: ip addr show "192\." ... or slightly better (for all private subnets): ip addr show | grep -e "192\.168\." -e "10\.0\." -e "172\.16\." ... if the reply of the above command is one line, which looks like this one ... inet 10.0.1.3/8 brd 10.255.255.255 scope global eth0 ... then you've found your Lamobo R1's IP address. If you've successfully found your IP address, then it's time to see if your SSH server is up and running. Try this command: top -b -n 1 | grep ssh Note: 'top' is a good utility, which you need to be familiar with; you can use it to see what processes (programs) are currently running and you can monitor how much CPU time (and other resources) they are using. Likewise, 'grep' will save you hours, days, weeks or years of time (depending on when you start using it). One could wish for a 3D version of grep. Now, if the SSH server is not running, you will not be able to SSH into your Lamobo R1. If it is running, however, then you should be able to SSH into your Lamobo using the following command: ssh 192.168.1.2 -l root -Of course, you'll need to supply the IP address you found earlier. It is highly recommendable that you use static IP addresses for your computers on your LAN; especially for those that are not laptops or portable devices. Eg. boxes that run any kind of server should really have a static IP address, otherwise you'd have to figure out the IP address every time your would need to copy a file to / from for instance your file-server. Using DHCP for a server would be worse than having nternet without domain names.
  2. Try having a look at the top of /boot/boot.cmd -This is a file, which needs to be compiled (but you have the compiler) Now, if you make a mistake, you might have to re-write your sd-card, so I will suggest you do the following: 1: Take out the SD-card you usually boot from and put it somewhere safe. 2: Get an empty card (a different card). 3: Write Armbian to this card, then boot from it. 4: When you've done the basic setup, CD into /boot. 5: copy boot.cmd to boot.cmd.old and boot.scr to boot.scr.old 6: Edit boot.cmd using your favorite editor. (I like nano myself, as it's very simple and easy to learn) 7: Look in /usr/sbin/nand-sata-install, you'll find a few places where 'boot.scr' is re-built from 'boot.cmd'. 8: Pick the one, which generates the SD-card booter and copy that: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr After running the above command, your boot.scr is updated. Try booting from the card and see if it works as expected. My boot.cmd for CubieBoard2 looks like this (note: you can most likely not use mine; use the one that is already written to your SD-card)... setenv bootargs "console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup-enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" -As you see, there are several interesting things to mess with. What exactly to do to disable things, I do not know, but I'd start by reducing the screen resolution to something small like 640x480@60. I think that other users of this forum will be able to provide a much better answer than mine, but this should give you a place to start.
  3. See page 37 in the BBox2 Manual for information on how to set up the DHCP pool - it appears that it's set up to the range 192.168.1.2 ... 192.168.1.254 by default. You're quite lucky. The manual for the BBox2 is pretty well written. Maybe the following static IP setup on your Lamobo R1 would be better: # Wired adapter #1 auto eth0 # iface eth0 inet dhcp iface eth0 inet static address 192.168.2.1 netmask 255.255.252.0 gateway 192.168.1.1 # Local loopback auto lo iface lo inet loopback I've changed the subnet mask, because then the IP 192.168.2.x would be on the same subnet as your DHCP pool (192.168.1.x). I think that 192.168.0.x, 192.168.2.x and 192.168.3.x could be used for static IP addresses if the above works.
  4. If you can find the "DHCP Statistics page" on your router, it might be able to show you what IP addresses are connected to it. This might be a baudrate mismatch (it sounds very much like it) - make sure your terminal (on the PC) is set up to 115200 baud, 8, N, 1. Here's a shortened version of mine on the CubieBoard2 (I haven't set up my Lamobo R1 yet): # Wired adapter #1 auto eth0 # iface eth0 inet dhcp iface eth0 inet static address 10.0.1.3 netmask 255.0.0.0 gateway 10.0.0.1 # Local loopback auto lo iface lo inet loopback -Your configuration file would probably need to be something like ... # Wired adapter #1 auto eth0 # iface eth0 inet dhcp iface eth0 inet static address 192.168.1.250 netmask 255.255.255.0 gateway 192.168.1.1 # Local loopback auto lo iface lo inet loopback -Eg. netmask differs and your DHCP range would probably conflict with the static IP range if the IP is too close to the beginning. Often home-routers are set up to reserve the first 40 or 64 IP-addresses for DHCP (sometimes more; it depends on the router's firmware and the vendor's behaviour). If you succeed in using a static IP, you might be able to configure your router to your own preference, but the important thing right now is to get it up and running.
  5. I definitely second that. I've bought plenty of the CP2102 USB-to-UART adapters (more than 10); all of them works well. Just one thing: I change the resistors connected to the LEDs with 2K7 resistors, so that they don't blind me. Bonus advantage of the CP2102 module: SiLabs actually made a driver for PowerPC based Macintosh (which is my primary computer) - many of the others don't want to support anything but Windows. In addition, Prolific requires you to pay a mountain of money, if you want to change the VID/PID of PL2303, which was why I moved to CP2102.
  6. Some of the explanation might be found here ... "NAND is not supported yet." ... however, shouldn't /dev/nand be at least visible as a device ? I tried installing jessie/legacy on a microSD card, but when I boot from it, I can only log in as root, and all I can do is change the password from 1234 to whatever I desire, then I'm logged out. This repeats as often as I log in. -So I've decided to go for jessie/vanilla and hope for nand support. -This is the only real problem I've had. I've had great success with moving Armbian to the SATA harddisk using the nand-sata-install script (note: if you have more than 4 devices, they *are* listed in the box; just scroll using the down-arrow key). I've also moved /var and /home to their own partitions (along with a few others). I'm also using UUID= in fstab instead of /dev/sd??*
  7. Please correct me where I am wrong. I'm putting up a lot of guesses, because it might save us some time in finding out what's going on and why. A lot of these guesses might be wrong - this is intended. I assume that by "modem" you mean "router". Can you provide some details on your hardware connections ? Eg. I would expect that you have your internet connection from a box that is connected directly to your ISP; let's call that the 'modem'. If this box has more than 1 RJ45 connector, then it might be a combined modem+router. If it has only a single RJ45 connector (and perhaps TV connector and RJ11 connectors too), then it's probably just a single 'modem'. If you have your computer connected directly to this box, and you have another device (the Lamobo R1) connected to it too via a separate RJ45 socket, then try swapping the two connectors. If your computer still connects to the internet, then we're sure it's a router. If your Lamobo R1 is connected to the 'modem' and your computer is connected to the Lamobo R1 and not the 'modem', then I am absolutely confused, because as I understand it, Armbian wouldn't default into being a router as far as I understand. ... I assume you wrote an unmodified image to an SD-card and booted your Lamobo R1 from that card. After starting your Lamobo R1, did you do any setup/configuration ? -If not, your Lamobo R1 is expecting you to log in as root and register a user-account. -If you did set it up, how did you log in - via serial interface ? I think you have approximately 3 or 4 fairly easy options: 1: Log in via SSH (go to your router's web-page and find the IP address of your Lamobo R1, then use this IP-address for the SSH session) example: ssh 192.168.1.2 -l root password is 1234 the first time you log in; you will be asked to change it before you continue. 2: Log in via the serial console. If you have a PC and you have a USB-to-UART (eg. CP2102 module from eBay), then you can connect the module to the UART0-RX, UART0-TX and GND pins on your board and you should be able to communicate with the board if you have a console-version of Armbian [i have not tested this]. DO NOT TRY TO CONNECT YOUR PC'S SERIAL CABLE TO THE BOARD, YOU WILL FRY (DAMAGE) THE BOARD! 3: You can connect a USB-keyboard to the Lamobo R1 and HDMI-cable from the R1 to a monitor of your choice. The monitor needs to have either a HDMI connector or DVI connector. You can use a DVI-to-HDMI adapter if the monitor has a DVI connector. 4: If you have Linux on a PC, then you can take out your SD-card and insert it in a USB-to-SD/MMC adapter (eg one of these from eBay) and you can mount the file system, make a backup-copy of /etc/network/interfaces on your PC, then set up your /etc/network/interfaces to use a static IP address, save the file and put the card back into the Lamobo R1 and boot it. Note: The eBay links I've added are to some items that I have tried a bunch of and they're working well. Furthermore they're dirt-cheap. It takes a long time for them to arrive, but I have the impression that time is not the issue for you, so I recommend that you just order a couple of each now (it's quite useful to have some in the drawer, so they're ready for when they're needed). I use a microSD-to-SD card adapter with the microSD cards, otherwise you can't use the mentioned USB-to-SD/MMC adapter; you'd have to find an alternative, but do not buy any of the "tiny" or "slim" ones; they are no good or they disconnect/unmount when they get hot (this one or this one might be good alternatives, but I have not tested them).
  8. Image: Armbian_5.04_Cubieboard2_Debian_jessie_4.4.3 Board: CubieBoard2 (SD+NAND version) Available platforms: i386 with Debian Jessie (sunxi tools) and PowerMac G5. Before Armbian, I had Cubian installed on an SD card. I saved the NAND root data and all the NAND? sub-partitions, so I have a full image of the original NAND and images of each partition. I took out the card, and inserted a fresh Armbian installation, it boots up quickly and works fine. However, as I wanted to set my CubieBoard2 up so it boots from a S-ATA disk (I bought a 1TB WDC drive), I decided to run nand-sata-install. But I got only one menu item to select, so I cancelled. I then did a cat /proc/partitions - to my big surprise, there was no 'nand' partitions. I did a ls -la /dev/ ... but no nand devices. I then decided to try booting from my Cubian SD card, but now the CubieBoard2 just blinks the LED. I can still boot from the Armbian SD card, but I'm quite puzzled what went wrong. My goal: To boot Armbian from the S-ATA disk on my CubieBoard2, so I can remove the MicroSD card from the MicroSD card slot. (I successfully partitioned the 1TB harddisk. Note: It took less than a second to partition it from the CubieBoard2).
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines