> On 18 Nov 2014, at 9:00 am, slug-requ...@slug.org.au wrote:
>
The install wasn't really the problem (once I got a version of Linux
and the BIOS updated) - just cloning it.
I think it came down to the UEFI stuff not liking being cloned.
>>>
>>> I have dd’d A disk in and out
On 17/11/14 12:40, DaZZa wrote:
On 17 November 2014 12:22, James Linder wrote:
The install wasn't really the problem (once I got a version of Linux
and the BIOS updated) - just cloning it.
I think it came down to the UEFI stuff not liking being cloned.
I have dd’d A disk in and out succesful
On 17 November 2014 12:22, James Linder wrote:
>> The install wasn't really the problem (once I got a version of Linux
>> and the BIOS updated) - just cloning it.
>>
>> I think it came down to the UEFI stuff not liking being cloned.
>
>
> I have dd’d A disk in and out succesfully but even 2 samsun
> On 17 Nov 2014, at 9:00 am, slug-requ...@slug.org.au wrote:
>
>> I’ve booted ubuntu, suse and arch on the atom, i3 and i5 versions. It’s easy
>> but fiddly …
>>
>> First start with a blank disk. I dd if=/dev/zero because the efi partition
>> is a
>> bitch. I *have* dualbooted Win7 and linux
On 13 November 2014 12:25, James Linder wrote:
> I’ve booted ubuntu, suse and arch on the atom, i3 and i5 versions. It’s easy
> but fiddly …
>
> First start with a blank disk. I dd if=/dev/zero because the efi partition is
> a
> bitch. I *have* dualbooted Win7 and linux but it is really not easy
On 12 November 2014 15:54, Patrick Shirkey wrote:
> Did you enable the M$ UEFI rootkit or are you using the normal/traditional
> BIOS?
Couldn't get them to boot in legacy mode (they didn't see the storage
as a disk), so I had to use UEFI mode.
> BTW, I installed Debian 7.0 on a NUC. It worked fi
Hi Dazza,
I've had some weird problems with rolling out many boxes in the past.
I would have first set all the bios to factory default so that they are
all the same.
(After checking firmware versions are the same etc...)
I've had in the past two really weird things happen.
First was a keyboa
> On 13 Nov 2014, at 9:00 am, slug-requ...@slug.org.au wrote:
>
>
> So I got my hands on two Intel Nuc's for work (nice toys - small and
> quiet), and that other OS everyone seems to love didn't want to
> install on the USB "disk" which was stuck in them, the decision was
> made to go to Linux.
On Wed, November 12, 2014 3:29 pm, DaZZa wrote:
> On 12 November 2014 15:25, Michael Chesterton
> wrote:
>> On 12/11/14 15:13, DaZZa wrote:
>>> Has anyone come across this before? Is it something specific to
>>> Ubuntu, or is it the stupid "SecureBoot" crap (which was turned off,
>>> by the way)
On 12 November 2014 15:25, Michael Chesterton wrote:
> On 12/11/14 15:13, DaZZa wrote:
>> Has anyone come across this before? Is it something specific to
>> Ubuntu, or is it the stupid "SecureBoot" crap (which was turned off,
>> by the way) they put into the BIOS for these things doing *something*
On 12/11/14 15:13, DaZZa wrote:
> And it flat out refused to boot. Nada. Get nicked.
>
> I thought I must have stuffed up the image - but both disks booted the
> first device fine.
>
> After scratching my head for a few hours and trying every BIOS option
> I could find, I decided to try a fresh ins
Long time no post.
So I got my hands on two Intel Nuc's for work (nice toys - small and
quiet), and that other OS everyone seems to love didn't want to
install on the USB "disk" which was stuck in them, the decision was
made to go to Linux.
A bit of research showed me that Ubuntu was about the on
12 matches
Mail list logo
