Language Selection

English French German Italian Portuguese Spanish

China Doll: Dell + Ubuntu, Again

Filed under
Ubuntu

It took me a few days to get it right. Didn’t have any problem installing Ubuntu5.10 on my old DIY desktop pc. But the same couldn’t be said about installing the newer release on my brand new Dell. There were unpleasant surprises and frustrating moments:

Getting the Ubuntu6.06 LiveCD to run was easy – it probably didn’t load any exotic video driver even when it was not actually running in Safe Graphic mode. Installing it on my harddisk was entirely a different matter.

As mentioned in my last post, the first surprise was that the Ubuntu6.06 LiveCD just installed its Grub bootloader on the MBR – no warning and no option to choose from. Grub is a fine bootloader but there are two major problems: first, if the computer is a Dell with a special MBR to cater for its two hidden partitions, Grub will simply mess up your specially partitioned harddisk. Second, Grub will invariably see your harddisk arrangement differently than your OS does (whether it’s Ubuntu or Suse) if you are using SATA or USB external harddrive. For my Dell, my internal SATA drive was sde during installation but becomes sda once Ubuntu was booted up (unless you are aware of this, you won’t be able to boot up Ubuntu using the Grub menu. One simple but sure-work way is to press ‘e’ and manually changes the root. In my Dell, I have a card reader which alone takes up sdb, sdc, sdd and sde. So my external drive can be anything from sda to sdg depending on (1) which harddisk I boot up from and (2) whether the OS will first see my card reader or the USB harddisk). One thing for certain is that whichever partition Grub thinks your root actually resides on will be wrong. It is necessary to manually edit the grub menu before Ubuntu will boot up.

Full Post.

More in Tux Machines

Octa-core Cortex-A53 hacker SBC sells for $60

FriendlyARM’s $60, open spec “NanoPC-T3” SBC runs Android or Linux on an octa-core Cortex-A53 SoC packed with wireless and media interfaces, plus 8GB eMMC. The over-caffeinated board builders at Guangzhou, China-based FriendlyARM have shipped their highest-end hacker board yet. The NanoPC-T3 is almost identical to the NanoPC-T2 board, but swaps out the quad-core, Cortex-A9 Samsung S5P4418 SoC for a layout-compatible S5P6818 with eight Cortex-A53 cores that can be clocked dynamically from 400MHz to 1.4GHz. Last month, FriendlyARM’ unveiled an $11, quad-core NanoPi M1 single board computer with similarly open source hardware and Android and Linux software. Read more

today's leftovers

Linux and Graphics

Security Leftovers

  • Cockpit 0.104
    Cockpit is the modern Linux admin interface. There’s a new release every week. Here are the highlights from this weeks 0.104 release.
  • FFmpeg 3.0.2 "Einstein" Multimedia Framework Released with Updated Components
    Today, April 28, 2016, the development team behind the popular FFmpeg open-source and cross-platform multimedia framework has released the second maintenance release in the stable FFmpeg 3.0 "Einstein" series. FFmpeg 3.0 was a massive release announced in mid-February, which brought in numerous existing changes, including support for decoding and encoding Common Encryption (CENC) MP4 files, support for decoding DXV streams, as well as support for decoding Screenpresso SPV1 streams.
  • Using bubblewrap in xdg-app
    At the core of xdg-app is a small helper binary that uses Linux features like namespaces to set up sandbox for the application. The main difference between this helper and a full-blown container system is that it runs entirely as the user. It does not require root privileges, and can never allow you to get access to things you would not otherwise have.
  • Build System Fallbacks
    If you are using Builder from git (such as via jhbuild) or from the gnome-builder-3-20 branch (what will become 3.20.4) you can use Builder with the fallback build system. This is essentially our “NULL” build system and has been around forever. But today, these branches learned something so stupidly obvious I’m ashamed I didn’t do it 6 months ago when implementing Build Configurations.
  • Node.js version 6 is now available