Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[OPi One] 5.10 image (4.6.0-rc1) doesn't boot

Featured Replies

Hi,

 

I've tried to finally move on from 5.04, but the new image doesn't boot. At least, HDMI doesn't show anything and my router doesn't see the board when connected via ethernet.

On the first power-on the green led glows a few minutes, then red one blinks a  few times alone, then both leds blink and then only green one glows. On successive boots only green led glows uninterruptedly.

 

Do you need any information to make it work?

 

BTW, legacy kernel worked fine for me, except my HDD connected with hdd-usb adapter (Agestar 3FBCP1) spits errors every few seconds and performance is unbearable.  Connected to my router with TomatoUSB the same hdd works fine. I hoped new kernel would solve the problem. Here's the error:

 usb 1-1: reset high-speed USB device number 2 using sunxi-ehci

Changing /sys/block/sda/device/max_sectors didn't help.

 

Thanks for all the hard work!

BTW, legacy kernel worked fine for me, except my HDD connected with hdd-usb adapter (Agestar 3FBCP1) spits errors every few seconds and performance is unbearable.  Connected to my router with TomatoUSB the same hdd works fine. I hoped new kernel would solve the problem. Here's the error:

 usb 1-1: reset high-speed USB device number 2 using sunxi-ehci

What does "lsusb" report for this adapter?

I removed Vanilla images since they are not ready for end users. They are for server usage - no HDMI output, serial console only.

OPI 2 does not boot also with Jessie Server 5.10 Vanilla. My primary usage is headless server, so I'd like to test vanilla builds :)

  • Author

Those errors can be related to not sufficient power supply. Do you power your HDD via USB? Than this is normal.

 

I removed Vanilla images since they are not ready for end users. They are for server usage - no HDMI output, serial console only.

 

Oh, I wasn't aware of it. I've used HDMI on 5.04 Debian server image to set everything up, so I supposed the new images weren't serial-only. Shouldn't DHCP at least work?

 

On the HDD issue: it's externally powered, I've checked it with 2 different power supplies with no change. Here's lsusb, connected to my laptop:

Bus 008 Device 003: ID 1f75:0611 Innostor Technology Corporation 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1f75 Innostor Technology Corporation
  idProduct          0x0611 
  bcdDevice            0.06
  iManufacturer           4 
  iProduct                5 
  iSerial                 6 20150317
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength           22
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000002
      HIRD Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
Device Status:     0x0000
  (Bus Powered)
Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.