Difference between pages "Microcode" and "User:Abillygoatknows"

(Difference between pages)
(fixing kernelop template)
 
(Installation of Funtoo onto Toshiba NB505 netbook (1.6 Ghz AtomN455 2GB ram 60GB 2.5" sandisk extreme SsD))
 
Line 1: Line 1:
== What is this "microcode?" ==
+
Toshiba NB505 installation.
''Wikipedia defines microcode as:'' "a layer of hardware-level instructions or data structures involved in the implementation of higher level machine code instructions in central processing units, and in the implementation of the internal logic of manychannel controllers, disk controllers, network interface controllers, network processors, graphics processing units, and other hardware. It resides in special high-speed memory and translates machine instructions into sequences of detailed circuit-level operations. It helps separate the machine instructions from the underlying electronics so that instructions can be designed and altered more freely. It also makes it feasible to build complex multi-step instructions while still reducing the complexity of the electronic circuitry compared to other methods. " [http://en.wikipedia.org/wiki/Microcode]
+
  
== AMD microcode support ==
 
{{fancynote| Supported CPU families: 10h (Barcelona), 11h (Turion x2 Ultra), 12h (Llano), 14h (Bobcat), 15h (Bulldozer)}}
 
  
=== Emerging the required package ===
+
I am installing from Crunchbang waldorf (based on Debian Wheezy).
For microcode to work with AMD, first emerge {{Package|sys-kernel/linux-firmware}}:
+
  
<console>
+
First, I create a logical volume called "funtoo" that is 10 Gigabytes large in the volume group "toshiba".
###i## emerge linux-firmware
+
</console>
+
  
=== Kernel configuration ===
+
"sudo lvcreate -nfuntoo -L10G toshiba"
  
{{kernelop|desc=
+
Now, this logical volume can be access via its handle "/dev/mapper/toshiba-funtoo".
Processor type and features --->
+
  <*> CPU microcode loading support
+
  [ ] Intel microcode loading support
+
  [*] AMD microcode loading support
+
Device Drivers --->
+
  Generic Driver Options --->
+
      (amd-ucode/microcode_amd.bin amd-ucode/microcode_amd_fam15h.bin) External firmware blobs to build into the kernel binary
+
}}
+
  
Now, run:
+
So what's next... I format it with the ext4 file-system.
  
<console>###i## reboot
+
"sudo mkfs.ext4 /dev/mapper/toshiba-funtoo"
</console>
+
  
The new microcode will be loaded after the next reboot.
+
Then I create a mount-point.  In this case, I will mount my funtoo logical volume on /mnt/funtoo.
  
[[Category:Hardware]]
+
"sudo mkdir /mnt/funtoo"
[[Category:Hardware_Compatibility]]
+
 
 +
Next, I will set permissions on this logical volume (so that my $username can read/write to the volume).
 +
 
 +
In my case, let $myusername be 'daisuke'.
 +
"sudo chown daisuke:daisuke /mnt/funtoo"
 +
 
 +
Then, i download a stage 3 tarball of funtoo from one of their mirrors to a folder called "backup" in my crunchang installation's home directory "~/".
 +
"wget $urltostage3tarball ~/backup"
 +
In my case, $urltostage3tarball is "http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/atom_64/stage3-latest.tar.xz"
 +
 
 +
Then, I untar this file into /mnt/funtoo.  First I put myself into the target directory (/mnt/funtoo), then I untar the stage3 file.
 +
"cd /mnt/funtoo && sudo tar xvJpf ~/backup/$stage3tarballfilename"
 +
In my case, $stage3tarballfilename = "stage3-latest.tar.xz"
 +
 
 +
After that... Uhh.. we gotta chroot into this new installation..first, I gotta mount some stuff.
 +
"sudo mount -l proc /proc /mnt/funtoo/proc && sudo mount --rbind /dev /mnt/funtoo/dev && sudo mount --rbind /sys /mnt/funtoo/sys"
 +
Then.. copy my wifi dns-resolve info
 +
"sudo cp -L /etc/resolv.conf /mnt/funtoo/etc/resolv.conf"
 +
Then..chroot
 +
"sudo chroot /mnt/funtoo /bin/bash"
 +
BAM!
 +
 
 +
And, until next time.. I'm done.  Gotta get out of this cafe.

Latest revision as of 16:35, February 1, 2014

Toshiba NB505 installation.


I am installing from Crunchbang waldorf (based on Debian Wheezy).

First, I create a logical volume called "funtoo" that is 10 Gigabytes large in the volume group "toshiba".

"sudo lvcreate -nfuntoo -L10G toshiba"

Now, this logical volume can be access via its handle "/dev/mapper/toshiba-funtoo".

So what's next... I format it with the ext4 file-system.

"sudo mkfs.ext4 /dev/mapper/toshiba-funtoo"

Then I create a mount-point. In this case, I will mount my funtoo logical volume on /mnt/funtoo.

"sudo mkdir /mnt/funtoo"

Next, I will set permissions on this logical volume (so that my $username can read/write to the volume).

In my case, let $myusername be 'daisuke'. "sudo chown daisuke:daisuke /mnt/funtoo"

Then, i download a stage 3 tarball of funtoo from one of their mirrors to a folder called "backup" in my crunchang installation's home directory "~/". "wget $urltostage3tarball ~/backup" In my case, $urltostage3tarball is "http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/atom_64/stage3-latest.tar.xz"

Then, I untar this file into /mnt/funtoo. First I put myself into the target directory (/mnt/funtoo), then I untar the stage3 file. "cd /mnt/funtoo && sudo tar xvJpf ~/backup/$stage3tarballfilename" In my case, $stage3tarballfilename = "stage3-latest.tar.xz"

After that... Uhh.. we gotta chroot into this new installation..first, I gotta mount some stuff. "sudo mount -l proc /proc /mnt/funtoo/proc && sudo mount --rbind /dev /mnt/funtoo/dev && sudo mount --rbind /sys /mnt/funtoo/sys" Then.. copy my wifi dns-resolve info "sudo cp -L /etc/resolv.conf /mnt/funtoo/etc/resolv.conf" Then..chroot "sudo chroot /mnt/funtoo /bin/bash" BAM!

And, until next time.. I'm done. Gotta get out of this cafe.