Messages

46

Development and Scripting / Re: From ova to image

« on: July 22, 2014, 09:08:03 AM »

You'll need to use gparted to make the partition bigger on the key. The default key partition is only 2.3 Gb. See http://ubermix.org/customization.html for details.

47

Development and Scripting / Re: From ova to image

« on: July 18, 2014, 12:27:17 PM »

Could be that vbox didn't finish writing to the key. Definitely watch the usb indicator at the bottom of the vbox window to make sure that it is done before rebooting. Usually takes an extra 30 seconds or so.

48

Development and Scripting / Re: Ubermix 2.031 Lite Deployment Script Issue

« on: July 18, 2014, 10:55:24 AM »

Awesome, thanks for the tip! Will update the Lite version asap.

49

Hardware Specific / Re: Fail to install fresh Ubermix 2.0 on Asus X201E

« on: July 18, 2014, 10:54:08 AM »

You can either use a 2.03 key to take the image off of your 2.02 build device, or copy the boot folder off of the 2.03 key to the 2.02 key.

50

Development and Scripting / Re: From ova to image

« on: July 11, 2014, 09:51:03 AM »

Sounds like your disk is too small in your virtual machine. Default install wants 8Gb for the base, 4Gb for the user changes, and at least 2Gb for home folders. You could squeeze that down to about 10Gb when installing by choosing 2. Advanced Install and entering the minimum sizes for the partitions.

51

Hardware Specific / Re: Fail to install Ubermix 2.02L on Intel N2600

« on: July 11, 2014, 09:47:52 AM »

That's the issue. A default 2.0L install won't squeeze down to 8Gb of primary storage out of the box - it really wants about 10Gb minimum. You could get it to fit by:

1. Install on a bigger system and boot in generic mode.
2. Remove a bunch of apps that the older devices would not be able to run well - like Blender, etc. You'll want to purge about 2 Gb worth.
3. Update your install key from that bigger system
4. Boot the little ones from the updated key, choose 2. Advanced Install, and then enter the suggested minimum sizes for the partitions.

52

Hardware Specific / Re: Fail to install Ubermix 2.02L on Intel N2600

« on: July 04, 2014, 03:37:36 PM »

Sounds like an incomplete image. Are you sure you have the entire image? Make sure the file is 2.3Gb.

53

Hardware Specific / Re: Fail to install fresh Ubermix 2.0 on Asus X201E

« on: July 04, 2014, 07:02:24 AM »

I just added a "create legacy partition map" option to 2.03 (just posted) under Expert Options. Give that a try and let me know if it helps.

54

Hardware Specific / Re: Fail to install Ubermix 2.02L on Intel N2600

« on: July 04, 2014, 07:00:44 AM »

I just added a "create legacy partition map" option to 2.03 (just posted) under Expert Options that might solve the problem. Am finding that some older system BIOS can't handle newer GPT partition tables. Give that a try and let me know if it helps.

55

Hardware Specific / Re: Fail to install fresh Ubermix 2.0 on Asus X201E

« on: July 03, 2014, 10:05:26 AM »

I'm going to build in an option to force an old school partition map on these troublesome models, since they can't seem to handle GPT partition tables. Will let you know when it is up.

56

Hardware Specific / Re: Fail to install Ubermix 2.02L on Intel N2600

« on: July 03, 2014, 10:04:06 AM »

Did you try resetting the partition map under Expert Options? It looks like an EFI install, however I'd be surprised if a system with an N2600 supports EFI.

57

General Discussion / Re: Ubermix 2.0 on 32-bit

« on: June 21, 2014, 03:42:00 PM »

2.0L(ite) is now available for download at http://ubermix.org/files.html

58

General Discussion / Re: Ubermix 2.0 on 32-bit

« on: June 19, 2014, 12:53:47 PM »

It's being tested by several key peeps now. Send me your email and I'll send you a link.

59

Q&A / Re: SBAC on Unbermix 2.0

« on: June 17, 2014, 02:15:04 PM »

Yes - see http://forums.ubermix.org//index.php/topic,193.msg688.html#msg688

60

Hardware Specific / Re: Fail to install fresh Ubermix 2.0 on Asus X201E

« on: June 06, 2014, 06:26:56 AM »

The X201 had a really early EFI BIOS as I recall, so it may be a bit out of spec. Try putting it in EFI mode with secure boot disabled, and it will probably work fine.