On 2016-12-13, peter green wrote:
> On 13/12/16 21:42, peter green wrote:
>> I would guess at this point either a race condition or a power glitch
>> (maybe powering the HDD off one of the USB ports wasn't such a good
>> idea).
>>
> OK, I found that adding ahci-imx.hotplug=1 to the kernel comman
On 20/12/16 12:50, Gunnar Wolf wrote:
I have a CuBox-i 4 (not 4x4). It's currently in stable use, and have
not fiddled with it for long (and right now, it sits 7000Km away from
me), but if I recall correctly, any USB media needed for the boot
process (i.e. a keyboard) has to be inserted in the l
peter green dijo [Tue, Dec 13, 2016 at 10:05:12PM +]:
> On 13/12/16 21:42, peter green wrote:
> >
> >I would guess at this point either a race condition or a power glitch
> >(maybe powering the HDD off one of the USB ports wasn't such a good idea).
> >
> OK, I found that adding ahci-imx.hotplu
On 13/12/16 21:42, peter green wrote:
I would guess at this point either a race condition or a power glitch
(maybe powering the HDD off one of the USB ports wasn't such a good
idea).
OK, I found that adding ahci-imx.hotplug=1 to the kernel command line
made it work.
Checking the schemati
On 13/12/16 19:59, peter green wrote:
I have just bought a cubox i4x4 and installed Debian Jessie on it
using D-I (concatenatable netboot). I am using a SD card for the
rootfs and plan to use a hard drive to store chroots.
Unfortunately while I can see the hard drive in D-I I can't see it
aft
I have just bought a cubox i4x4 and installed Debian Jessie on it using
D-I (concatenatable netboot). I am using a SD card for the rootfs and
plan to use a hard drive to store chroots.
Unfortunately while I can see the hard drive in D-I I can't see it after
installing. The ahci_imx module seem
6 matches
Mail list logo