Jump to content

Baos

Members
  • Posts

    23
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by Baos

  1. Thanks, I was considering that one.
  2. I would like to consolidate some of my devices into a singular device. I am having trouble coming up with a system which could work. currently my cubietruck crashes all the time, so much that it is now on a 2 hour reboot cycle and still manages to crash. I assume it's a power issue with the 3.5 harddrive. Could also be 3Terbyte drive is too much? Also 60mb/s is a bit slow. I have an asus rt-ac87u which does 802.11ac mimo wireless, but I do not like it's operating system. Also the wireless has issues. So, basically looking for something that can support 802.11ac mimo wireless(extra power?) ethernet ports 4-5 sata drive. I have been starting to look at x86 architecture for this(mini-dtx), however I would prefer low noise and low power usage unless it's actually being used.
  3. I have read it again and still do not see your link. mobile version. I posted because of the date on the article of May 11 2016. I wanted to make sure the exploit was not present in what I am using. I had a lot of issues with similar linux exploits in the 90s. For me it is the fear of worms and backdoors.
  4. http://arstechnica.com/security/2016/05/chinese-arm-vendor-left-developer-backdoor-in-kernel-for-android-pi-devices/ Troubling read.
  5. Lost the login motd following apt-get upgrade. Start-Date: 2016-05-08 10:52:11 Commandline: apt-get upgrade Upgrade: linux-image-next-sunxi:armhf (5.04, 5.10), linux-headers-next-sunxi:armhf (5.04, 5.10), linux-trusty-root-next-cubietruck:armhf (5.04, 5.10), linux-dtb-next-sunxi:armhf (5.04, 5.10), linux-firmware-image-next-sunxi:armhf (5.04, 5.10) End-Date: 2016-05-08 10:56:33 I imagine I have to reinstall a pam config file?
  6. Baos

    cubox will not boot

    For anyone who searches this thread. Here is the most up to date bootable image I could find. uname -a Linux alarm 3.5.7-14-ARCH #1 PREEMPT Mon Jun 30 13:06:45 MDT 2014 armv7l GNU/Linux https://archlinuxarm.org/about/downloads Here is the only ubuntu I could find. I would not recommend as it is no longer supported. https://www.solid-run.com/download/pub/solidrun/cubox/distros/ubuntu/cubox-ubuntu-core-12.10-core-armhf-r1.tar.xz
  7. Baos

    cubox will not boot

    Discovered it already had a serial device built-in. What a nifty device. elcome to minicom 2.7 OPTIONS: I18n Compiled on Feb 7 2016, 13:37:27. Port /dev/ttyUSB1, 21:04:50 Press CTRL-A Z for help on special keys T T CuBox ** LOADER ** U-Boot 2009.08 (Sep 20 2012 - 02:30:22) Marvell version: 5.4.4 NQ SR1 BootROM: Version on chip: 2.33 Status: OK Retries #: 0 Board: CuBox SoC: 88AP510 (A1) CPU: Marvell Sheeva (Rev 5) CPU @ 800Mhz, L2 @ 400Mhz DDR3 @ 400Mhz, TClock @ 166Mhz PEX 0: interface detected no Link. PEX 1: interface detected no Link. DRAM: 1 GB CS 0: base 0x00000000 size 512 MB CS 1: base 0x20000000 size 512 MB Addresses 60M - 0M are saved for the U-Boot usage. SF: Detected M25P32 with page size 64 kB, total 4 MB Streaming disabled L2 Cache Prefetch disabled L2 Cache ECC disabled Modifying CPU/CORE/DDR power rails to 1.0(-2.5%) / 1.0(-5%) / 1.5(-5%) USB 0: Host Mode USB 1: Host Mode Setting VPU power OFF. Setting GPU power ON. MMC: MV_SDHCI: 0, MV_SDHCI: 1 Net: egiga0 [PRIME] Hit any key to stop autoboot: 0 ===> Executing ext4load usb 0:1 0x02000000 /boot.scr (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 2 USB Device(s) found Waiting for storage device(s) to settle before scanning... scanning bus for storage devices... 0 Storage Device(s) found ** Bad partition 1 ** ===> Executing ext4load usb 1:1 0x02000000 /boot.scr ** Bad partition 1 ** ===> Executing fatload usb 0:1 0x02000000 /boot.scr ** Can't read from device 0 ** ** Unable to use usb 0:1 for fatload ** ===> Executing fatload usb 1:1 0x02000000 /boot.scr ** Can't read from device 1 ** ** Unable to use usb 1:1 for fatload ** ===> Executing ext4load usb 0:1 0x02000000 /boot/boot.scr ** Bad partition 1 ** ===> Executing ext4load usb 1:1 0x02000000 /boot/boot.scr ** Bad partition 1 ** ===> Executing fatload usb 0:1 0x02000000 /boot/boot.scr ** Can't read from device 0 ** ** Unable to use usb 0:1 for fatload ** ===> Executing fatload usb 1:1 0x02000000 /boot/boot.scr ** Can't read from device 1 ** ** Unable to use usb 1:1 for fatload ** ===> Executing ext4load usb 0:2 0x02000000 /boot.scr ** Bad partition 2 ** ===> Executing ext4load usb 1:2 0x02000000 /boot.scr ** Bad partition 2 ** ===> Executing fatload usb 0:2 0x02000000 /boot.scr ** Can't read from device 0 ** ** Unable to use usb 0:2 for fatload ** ===> Executing fatload usb 1:2 0x02000000 /boot.scr ** Can't read from device 1 ** ** Unable to use usb 1:2 for fatload ** ===> Executing ext4load usb 0:2 0x02000000 /boot/boot.scr ** Bad partition 2 ** ===> Executing ext4load usb 1:2 0x02000000 /boot/boot.scr ** Bad partition 2 ** ===> Executing fatload usb 0:2 0x02000000 /boot/boot.scr ** Can't read from device 0 ** ** Unable to use usb 0:2 for fatload ** ===> Executing fatload usb 1:2 0x02000000 /boot/boot.scr ** Can't read from device 1 ** ** Unable to use usb 1:2 for fatload ** ===> Executing ext4load mmc 0:1 0x02000000 /boot.scr Device: MV_SDHCI Manufacturer ID: 3 OEM: 5344 Name: SL32G Tran Speed: 25000000 Rd Block Len: 512 SD version 2.0 High Capacity: Yes Capacity: 31914983424 Bus Width: 4-bit Loading file "/boot.scr" from mmc device 0:1 mmcda1 ** File not found /boot.scr ===> Executing fatload mmc 0:1 0x02000000 /boot.scr reading /boot.scr ** Unable to read "/boot.scr" from mmc 0:1 ** ===> Executing ext4load mmc 0:1 0x02000000 /boot/boot.scr Loading file "/boot/boot.scr" from mmc device 0:1 mmcda1 747 bytes read ## Executing script at 02000000 ## Error: "autodetectfdt" not defined ** No boot file defined ** usage: fatload <interface> <dev[:part]> <addr> <filename> [bytes] ** No boot file defined ** Loading file "/boot/zImage" from mmc device 0:1 (mmcda1) ** File not found /boot/zImage reading zImage ** Unable to read "zImage" from mmc 0:1 ** Loading file "zImage" from mmc device 0:1 mmcda1 ** File not found zImage Unknown command 'bootz' - try 'help' ===> Executing fatload mmc 0:1 0x02000000 /boot/boot.scr reading /boot/boot.scr ** Unable to read "/boot/boot.scr" from mmc 0:1 ** ===> Executing ext4load mmc 0:2 0x02000000 /boot.scr ** Bad partition 2 ** ===> Executing fatload mmc 0:2 0x02000000 /boot.scr ** Partition 2 not valid on device 0 ** ** Unable to use mmc 0:2 for fatload ** ===> Executing ext4load mmc 0:2 0x02000000 /boot/boot.scr ** Bad partition 2 ** ===> Executing fatload mmc 0:2 0x02000000 /boot/boot.scr ** Partition 2 not valid on device 0 ** ** Unable to use mmc 0:2 for fatload ** ===> Executing ext4load ide 0:1 0x02000000 /boot.scr Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found ** Bad partition 1 ** ===> Executing fatload ide 0:1 0x02000000 /boot.scr Error No HD connection ** Can't read from device 0 ** ** Unable to use ide 0:1 for fatload ** ===> Executing ext4load ide 0:1 0x02000000 /boot/boot.scr ** Bad partition 1 ** ===> Executing fatload ide 0:1 0x02000000 /boot/boot.scr Error No HD connection ** Can't read from device 0 ** ** Unable to use ide 0:1 for fatload ** ===> Executing ext4load ide 0:2 0x02000000 /boot.scr ** Bad partition 2 ** ===> Executing fatload ide 0:2 0x02000000 /boot.scr Error No HD connection ** Can't read from device 0 ** ** Unable to use ide 0:2 for fatload ** ===> Executing ext4load ide 0:2 0x02000000 /boot/boot.scr ** Bad partition 2 ** ===> Executing fatload ide 0:2 0x02000000 /boot/boot.scr Error No HD connection ** Can't read from device 0 ** ** Unable to use ide 0:2 for fatload ** Using egiga0 device TFTP from server 192.168.15.100; our IP address is 192.168.15.223 Filename 'boot.scr'. Load address: 0x2000000 Loading: T T T T T T T T T T Retry count exceeded; starting again Using egiga0 device TFTP from server 192.168.15.100; our IP address is 192.168.15.223 Filename 'boot.scr'. Load address: 0x2000000 Loading: T T T T T
  8. Baos

    cubox will not boot

    This is a first gen cubox, half did not have a serial port. I would need a pinout to connect to what might be a serial port. I could not find an archive image from months/years ago to try. And yes, nothing at all, no hdmi signal.
  9. Maybe I missed something, it's been a few weeks since I needed to install an image. cubox with hdmi does not boot. There is no serial port, so I can not even try to figure it out. Also it never requests an ip address from the router. Tried with trusty legacy and vanilla. Used the link specifically labeled cubox-i http://www.armbian.com/cubox-i/
  10. Just threw my asus rt-ac87u in the bin because I got tired of it malfunctioning. I no longer like asus products. So, for the moment I had to turn my cable modem back into a gateway. That said, I found allwinner owns an OUI DC446D and applied it.
  11. My cubietruck mac address which I am assuming is auto generated is invalid. Though one would think it should work, other software on routers will not accept the mac as valid, and thus I can not add configurations to it. We probably need a layer somewhere to create 'valid' mac addresses. 02:C2:07:C0:B7:C7 is the generated mac that my cubietruck is currently using which software claims is invalid.
  12. I will not be running a 15 hour test. And It's now a 3tb drive. I would be willing to do .5 of a tb at most. I don't think one needs to fill the harddrive to run a decent test. Also the only stat I actually care about is how fast I can transfer files off it via an ftp client or any other, smb, nfs, etc.(75mb/s max on armbian, 20-30mb/s using netbsd) Last year I lived out in the country and my max speed most of the time was 0.3kps. I'm in the city now, when I get 10mb/s download it's great.
  13. I tried the test, 7 hours later it was still writing files. I closed the test and turned transmission back on.
  14. Will I loose any data using that?
  15. I wonder if it makes a difference that mine is formated ext4.
  16. I am getting significantly better speeds on cubietruck. using a samsung I found inside a seagate backup plus 2t drive. It's a 5400rpm laptop drive. Using vsftpd on the armbian vs nautilus ftp(no ssl) on my home computer I'm getting write 30MB/s(upload). read 70MB/s(download). Armbian out of the box without any special tweaking. I had some trouble with the 3.5 inch harddrive addon package, this is without.
  17. Someone did an amazing job implementing the cubietruck sata speed for armbian. I am curious as to what was done. The other day I pulled read 75MB/s(via nautilus ftp) to my main computer from it. Would perhaps like to apply whatever the fix was to netbsd.
  18. I noticed somebody did some work. All I did was add xenial to the compile script and it went through without any errors. Impressive. Welcome to ARMBIAN Ubuntu 16.04 4.4.5-sunxi Any reason an alpha image isn't available? Would you like the one I made?
  19. Tested with a few drives, and different operating systems. Also a couple power supplies. The harddrive runs extra hot 107F on the outside for the last one I measured myself. It dies during heavy loads. a simple fsck will kill it. But put it in my main computer and I can write /dev/zero to it all day long. My first thought is that I had a power issue with some power supplies lying about their actual amperage. So I found "FSP Net 36 Universal Netbook Power Adapter 12V 36W for ASUS Eee PC" in the discount bin and modified it to work in a 12v adapter. Still the crashing persists. However if I don't use the 3.5 addon package and I use a 2TB samsung laptop drive, no crashing.
  20. Netbsd works well with a bottleneck for sata speed. About 10% of the speed of armbian. FreeBSD will boot with the a20 kernel but lacks support for just about anything more than booting and logging in as it is intended for cubieboard2. ethernet also fails.
  21. Thanks Igor. I figured as much. I will try and work with the code, also taking into account vlad's analysis. Will post results. Oh, and fyi, my proposed solution also fell victim to the same bug today. The bug can be confirmed by having the motd output the current time.
  22. For /etc/update-motd.d/30-sysinfo I noticed it likes to say my system is up 6 seconds and then when I check with uptime I notice it's wrong and has been up for hours or over a day. Just curious if there is a reason for not doing it in a way similar to this? function displaytime { # we need dedicated function local X=$(/usr/bin/uptime -p) printf "Up time: " printf "\x1B[92m%s\x1B[0m\t\t" "$X" }
×
×
  • Create New...