@Bob Two coworkers ordered Firefox OS "geeksphones" and they're getting it delivered here, apparently today. It costed EU 180. The taxes were more than that.
Apparently there is a table at customs with the "market prices", and if you order something at a price they don't expect, they charge taxes based on "market prices"
Imagine they seeing a Raspberry Pi!
"RaspWhat? Oh! A computer! NO WAY you paid U$35 for a computer! Computers are at least U$750, let's charge taxes on THAT"
@JourneymanGeek which also means that even with half the number of cores, if each core can process >2x faster (ignoring context switching), then it still wins
more RAM cache is good, but you're probably going to be CPU-bound before the difference between 32GB and 64GB is really significant with an Atom, even an 8-core one
it is ECC RAM, so there's that
I can't find any benchmark results, but it's only 2W TDP, which isn't all that much power (course, you have 17W TDP i7s, but they're considerably less powerful than their desktop counterparts)
sure, you get more perf/Watt with Atoms, but at some point the difference in power (consumption) will make a difference, assuming similar architectures
@Bob I can't find any benchmark results, but it's only 20W TDP, which isn't all that much power (course, you have 17W TDP i7s, but they're considerably less powerful than their desktop counterparts) (source)
On Super User, ui is a synonym for user-interface.
On Meta Super User, they are two
separate tags.
That doesn’t make any sense.
I recommend making [ui] a synonym
for [user-interface]
on Meta Super User.
What is the proper way to cite an answer from another StackExchange site? It is not uncommon to find an answer to a question for SuperUser on ServerFault or StackOverflow. But there doesnt seem to be an easy way, other than to quote the answer and make a link.
One would think there would be a ...
OK, I received and installed the Intel 530 SSD and it's being detected by the BIOS. I added a GPT partition table and set one of the partitions to bootable. The BIOS refuses to let me select the SSD as a boot device; it only offers the spinning-rust drive I'm trying to replace and the DVD drive. SATA is set to AHCI. Any good suggestions as to why, anyone?
@MichaelKjörling the very concept of a "bootable" flag is alien to GPT, since UEFI operates completely differently by having an EFI System Partition that provides the boot loaders... are you sure you set it correctly? in GPT it would be done by setting the legacy_boot flag in the protective MBR
also, are you sure your "BIOS" isn't actually a UEFI, and if so, is compatibility mode enabled?
and does your UEFI firmware have compatibility mode enabled?
trying to configure a GPT disk for being booted in legacy BIOS mode by setting the legacy boot flag and then trying to boot it in UEFI mode won't be fruitful
really you should just decide right now whether you want to go all-out BIOS mode or all-out UEFI mode, and decide to cater your entire stack appropriately
all-out BIOS mode: partition the drive as MBR (not GPT), turn on compatibility support module in UEFI configuration screen, and install OS booting in CSM mode
I honestly don't know how well GRUB 2 handles pure-UEFI. Are you thinking it might be that the BIOS doesn't want to see the GPT and wants a MBR in its place?
It's worth nothing that the 4 TB spinning-rust drive doesn't show up either, and I know that one is partitioned GPT because MBR doesn't do that much. The SSD is 180 GB so no capacity problems there.
Should I try scrapping the GPT and just try with MBR instead, and see what happens?
a good Linux distro will do all of this for you automatically
basically you pop in the Linux CD/DVD, boot to it in UEFI mode (disable CSM), and it should automatically partition your disk appropriately and put GRUB2 in the system partition and make it bootable
well if you're copying things at the file layer, there's really nothing stopping you from doing a fresh install of the OS and then copying over programs/data
But let's say I wipe the GPT off the SSD and put a MBR in its place. Then set one partition as bootable. Should that make the SSD show up as a boot-possible device in the motherboard firmware setup?
so wait, you haven't wiped your old disk, and it's still connected, but the BIOS can't boot to it? and the only thing you've changed is installing a new SSD?
sounds like you don't have the hardware plugged in properly or something
there's no reason I can think of that installing a new disk would cause an old disk to be unbootable, unless you did something wrong at the hardware level
I added a new SSD and want to migrate the data from the old spinning-rust drive to the SSD. BIOS detects both fine, I'm running off spinning rust now, but BIOS won't let me select the SSD as a boot device. It just isn't listed as an option, only the HDD and DVD drive are.
It's worth nothing that the 4 TB spinning-rust drive doesn't show up either, and I know that one is partitioned GPT because MBR doesn't do that much. The SSD is 180 GB so no capacity problems there.
now I have been able to boot from GPT on a non-UEFI system before; in theory it should work, provided there's bootloader support; and that can be useful for booting from very large (like 4 TB) disks that MBR can't support; but it's somewhat of an odd case
the happiest paths are UEFI + GPT and (BIOS or CSM) + MBR
GPT doesn't provide any performance or safety benefits during runtime, anyway -- really the only potential performance win you can see is native UEFI booting + GPT + something like hybrid sleep (Windows 8...) or Intel Rapid Boot Technology
you also get UEFI GOP if CSM is disabled; the Graphics Output Protocol combined with a supporting graphics card (it's firmware-dependent) can initialize the display device directly to the native resolution without ever using text mode or VESA compatibility modes, reducing mode switching and loading time
unsure of the state of UEFI GOP support with the open source graphics stack; I presume it's supported by now at least on Intel iGPUs; but it's definitely not supported by the proprietary graphics drivers
OK, now I'm not quite sure if I should be happy that it seems to have worked out, or angry at the idiosynchronicies of the ASUS firmware setup UI.
The UI only displays the primary boot device of each class (HDD, CD/DVD), but when I went into HDD boot priorities I could choose between all three drives, including the SSD. Tried setting the SSD primary and at least it didn't break completely; it continued with the HDD though, likely because it didn't find a valid boot sector signature.
"/dev/sdb contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?"
@MichaelKjörling don't expect fdisk (or anything in software, really) to have a good understanding of what constitutes an efficient use of the underlying storage device... block sizes, boundaries, etc. are all pretty hard to understand from a software perspective due to the tons of abstraction between the physical NAND and the block layer