From 78067dd62a285731305b7a890da333d265ce6cad Mon Sep 17 00:00:00 2001
From: Francis Rowe
The "Parse" options read ./isolinux/isolinux.cfg on a CD or USB,
and automatically converts it to a grub config and switches to the boot menu of that distro.
- This makes booting ISO's *much* easier than before.
+ This makes booting ISOs *much* easier than before.
- TODO: T60: find (for rare buggy CPU's that are unstable without microcode updates) if there is a workaround (patched kernel, special parameter, etc) So far, only 1 processor has been found to have issues. See microcode errata sheets http://download.intel.com/design/mobile/SPECUPDT/31407918.pdf and http://download.intel.com/design/mobile/SPECUPDT/30922214.pdf and then look at the debugging results collected in t7200q directory (q means quirk).
+ TODO: T60: find (for rare buggy CPUs that are unstable without microcode updates) if there is a workaround (patched kernel, special parameter, etc) So far, only 1 processor has been found to have issues. See microcode errata sheets http://download.intel.com/design/mobile/SPECUPDT/31407918.pdf and http://download.intel.com/design/mobile/SPECUPDT/30922214.pdf and then look at the debugging results collected in t7200q directory (q means quirk).
@@ -93,8 +93,8 @@
- Apparently, only 8MB VRAM is available on i945 GPU's (though it could do 64MB):
The VBIOS on i945 (intel gpu) platforms is self-modifying; that is,
- it's contents change when you run it. intelvbttool takes a dump of
+ its contents change when you run it. intelvbttool takes a dump of
the currently running vbios, and parses it.
@@ -349,11 +349,11 @@
-
@@ -924,7 +924,7 @@
T60 cpu microcode
i945 VRAM size
- phcoder: No. Hardware default is 8 MiB. When I wanted to make it configurable, I saw that docs mention only one other alternative: 1MiB. Later isn't event enough for 1024x768 at 24bpp without any acceleration or double buffering. It's possible there are undocumented values. Which options do you have in vendor BIOS?
+ Apparently, only 8MB VRAM is available on i945 GPUs (though it could do 64MB):
+ phcoder: No. Hardware default is 8 MiB. When I wanted to make it configurable, I saw that docs mention only one other alternative: 1MiB. Later isn't event enough for 1024x768 at 24bpp without any acceleration or double buffering. It's possible that there are undocumented values. Which options do you have in vendor BIOS?
How to find out how much vram you have:
phcoder: TOM - BSM
phcoder: check what vendor BIOS offers as options
@@ -286,10 +286,10 @@
- intelvbttool test results (VGA ROM's)
+ intelvbttool test results (VGA ROM dumps)
- T60 has DVI on it's dock, make sure that the dock is attached when getting this output. + T60 has DVI on its dock, make sure that the dock is attached when getting this output.
diff --git a/docs/git/index.html b/docs/git/index.html index 7aa2c6a..8164503 100644 --- a/docs/git/index.html +++ b/docs/git/index.html @@ -37,8 +37,8 @@
- To build the ROM's, see #build. + To build the ROM images, see #build.
@@ -148,7 +148,7 @@- Flashrom is the utility for flashing/dumping ROM's. This is what you will use to install libreboot. + Flashrom is the utility for flashing/dumping ROM images. This is what you will use to install libreboot.
@@ -358,8 +358,8 @@ scripts for this machine.
- It is believed that the motherboards on 14.1" and 15.1" T60's are the same, so the same configuration is used - on both the 14.1" and 15.1" T60's. + It is believed that the motherboards on 14.1" and 15.1" T60s are the same, so the same configuration is used + on both the 14.1" and 15.1" T60s.
- Go back and disable option ROM's: + Go back and disable option ROMs:
- Go back and disable option ROM's: + Go back and disable option ROMs:
You don't need to do much, as there are scripts already written for you that can build everything automatically.
@@ -474,7 +474,7 @@ $ ./builddepsIf you've already run ./builddeps and/or ./buildall before, you don't need to run them again.
- Just run that from now on to build your ROM's:
+ Just run that from now on to build the ROM images:
$ ./build
To un-build (clean) the build dependencies that you built before, do the following:
@@ -540,7 +540,7 @@
SeaBIOS isn't really needed since libreboot uses the GRUB payload which diff --git a/docs/gnulinux/configuring_parabola.html b/docs/gnulinux/configuring_parabola.html index 270d2bb..e3c9239 100644 --- a/docs/gnulinux/configuring_parabola.html +++ b/docs/gnulinux/configuring_parabola.html @@ -176,7 +176,7 @@ and more maintenance work.
- The Arch forum can also be useful, if others have the same issue as you (if you encounter issues, that is). Parabola's + The Arch forum can also be useful, if others have the same issue as you (if you encounter issues, that is). The Parabola IRC channel (#parabola on freenode) can also help you.
@@ -400,7 +400,7 @@
- You'll note that I set both lines; the 2nd line is for IPv6. More and more ISP's are providing this now (mine does) + You'll note that I set both lines; the 2nd line is for IPv6. More and more ISPs are providing this now (mine does) so it's good to be forward-thinking here.
@@ -475,7 +475,7 @@ This is important, so make sure to read them!
- Install smartmontools (can be used to check smart data - note: HDD's use non-free firmware inside, it's transparent to you
+ Install smartmontools (it can be used to check smart data. HDDs use non-free firmware inside, but it's transparent to you
but the smart data comes from it. Therefore, don't rely on it too much):
# pacman -S smartmontools
Read https://wiki.archlinux.org/index.php/S.M.A.R.T. to learn how to use it.
diff --git a/docs/gnulinux/encrypted_trisquel.html b/docs/gnulinux/encrypted_trisquel.html
index 1cca4f0..7f80272 100644
--- a/docs/gnulinux/encrypted_trisquel.html
+++ b/docs/gnulinux/encrypted_trisquel.html
@@ -21,7 +21,7 @@
Libreboot uses the GRUB payload
by default, which means that the GRUB configuration file
(where your GRUB menu comes from) is stored directly alongside libreboot
- and it's GRUB payload executable, inside
+ and its GRUB payload executable, inside
the flash chip. In context, this means that installing distributions and managing them
is handled slightly differently compared to traditional BIOS systems.
@@ -102,7 +102,7 @@
- You can work directly with one of the ROM's already included in the libreboot ROM archives. For the purpose of + You can work directly with one of the ROM images already included in the libreboot ROM archives. For the purpose of this tutorial it is assumed that your ROM is named libreboot.rom so please make sure to adapt.
@@ -120,7 +120,7 @@If you currently have flashed a ROM image from an older version, it is recommended to update first: - basically, modify one of the latest ROM's and then flash it. + basically, modify one of the latest ROM images and then flash it.
@@ -191,8 +191,8 @@ Yours might be different. In GRUB terms, sda means ahci0. 1 means msdos1, or gpt1, depending on whether I am using MBR or GPT partitioning. Thus, /dev/sda1 is GRUB is (ahci0,msdos1) or (ahci0,gpt1). In my case, I use MBR partitioning so it's (ahci0,msdos1). - 'msdos' is GRUB's name simply because this partitioning type is traditionally used by MS-DOS. - It doesn't mean you have a proprietary OS. + 'msdos' is a GRUB name simply because this partitioning type is traditionally used by MS-DOS. + It doesn't mean that you have a proprietary OS.
@@ -209,14 +209,14 @@
- For the GRUB payload's grubtest.cfg (in the 'Load Operating System' menu entry), we therefore have (in this example):
+ For the GRUB payload grubtest.cfg (in the 'Load Operating System' menu entry), we therefore have (in this example):
set root='ahci0,msdos1'
linux /vmlinuz root=UUID=3a008e14-4871-497b-95e5-fb180f277951
initrd /initrd.img
- Optionally, you can convert the UUID to it's real device name, for example /dev/sda1 in this case. + Optionally, you can convert the UUID to its real device name, for example /dev/sda1 in this case. sdX naming isn't very reliable, though, which is why UUID is used for most distributions.
diff --git a/docs/grub/index.html b/docs/grub/index.html index f2d554a..e4dd8dc 100644 --- a/docs/grub/index.html +++ b/docs/grub/index.html @@ -55,7 +55,7 @@I took Dejavu Sans Mono from dejavu (included in this version of libreboot) and did:
$ ../../../grub/grub-mkfont -o dejavusansmono.pf2 ../../../dejavu-fonts-ttf-2.34/ttf/DejaVuSansMono.ttf
I then added the instructions to 'build' script to include resources/grub/dejavusansmono.pf2 in all of the ROM's in root of cbfs.
+
I then added the instructions to 'build' script to include resources/grub/dejavusansmono.pf2 in all of the ROM images in root of cbfs.
I then added that instructions to the grub.cfg files (to load the font):
loadfont (cbfsdisk)/dejavusansmono.pf2
The scripts build and buildrom-withgrub will automatically see this, and automatically build - ROM's with your custom layout (given the name) and include them under bin. Example: libreboot_frazerty.rom. + ROM images with your custom layout (given the name) and include them under bin. Example: libreboot_frazerty.rom.
diff --git a/docs/hcl/index.html b/docs/hcl/index.html index 30f9564..f8c7c50 100644 --- a/docs/hcl/index.html +++ b/docs/hcl/index.html @@ -25,8 +25,8 @@- 'Supported' means that the build scripts know how to build ROM's for these machines, + 'Supported' means that the build scripts know how to build ROM images for these machines, and that the machines have been tested (confirmed working). There may be exceptions; in other words, this is a list of 'officially' supported machines.
@@ -78,7 +78,7 @@Native gpu initialization ('native graphics') which replaces the proprietary VGA Option ROM @@ -145,11 +145,11 @@
- Most X60T's only have digitizer (pen), but some have finger (touch) aswell as pen; finger/multitouch doesn't work, only digitizer (pen) does. + Most X60Ts only have digitizer (pen), but some have finger (touch) aswell as pen; finger/multitouch doesn't work, only digitizer (pen) does.
- You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in it's place (for flashing libreboot). The chassis is mostly identical + You can remove an X61/X61s motherboard from the chassis and install an X60/X60s motherboard in its place (for flashing libreboot). The chassis is mostly identical and the motherboards are the same shape/size. It is unknown if the same applies between the X60 Tablet and the X61 Tablet.
@@ -227,7 +227,7 @@ EndSection- Some T60's have ATI GPU's, and all T60p's have ATI GPU's These are incompatible! See #t60_ati_intel for how to remedy this. + Some T60s have ATI GPUs, and all T60P laptops have ATI GPUs These are incompatible! See #t60_ati_intel for how to remedy this.
@@ -341,7 +341,7 @@ EndSection- Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and have ROM's compiled for it, however + Theoretically, the ThinkPad T60 with ATI GPU can work with libreboot and have ROM images compiled for it, however in practise it would not be usable as a laptop because there would be no visual display at all. That being said, such a configuration is acceptable for use in a 'headless' server setup (with serial and/or ssh console as the display).
@@ -420,7 +420,7 @@ EndSectionLinks to wget backups (and the backups themselves) of Mono's pages (see above) removed temporarily. Mono has given me permission to distribute them, but I need to ask - him to tell me what license these works fall under first. Otherwise, the above URL's should be fine. NOTE TO SELF: REMOVE THIS WHEN DONE + him to tell me what license these works fall under first. Otherwise, the above URLs should be fine. NOTE TO SELF: REMOVE THIS WHEN DONE
- Some X200's have a CCFL backlight and some have an LED backlight, in their LCD panel. This + Some X200s have a CCFL backlight and some have an LED backlight, in their LCD panel. This also means that the inverters will vary, so you must be careful if ever replacing either the panel and/or inverter. (a CCFL inverter is high-voltage and will destroy an LED backlit panel).
- CCFL's contain mercury. An X200 with a CCFL backlight will (unless it has been changed to an LED, + CCFLs contain mercury. An X200 with a CCFL backlight will (unless it has been changed to an LED, with the correct inverter. Check with your supplier!) the following: "This product contains Lithium Ion Battery, Lithium Battery and a lamp which contains mercury; dispose according to local, state or federal laws" (one with an LED backlit panel will say something different). diff --git a/docs/hcl/x200_remove_me.html b/docs/hcl/x200_remove_me.html index e306433..48468c6 100644 --- a/docs/hcl/x200_remove_me.html +++ b/docs/hcl/x200_remove_me.html @@ -233,7 +233,7 @@
List of directories corresponding to each board: @@ -53,7 +53,7 @@
These images use coreboot text-mode graphics:
@@ -100,7 +100,7 @@
diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html
index 8d7ab9d..ba010d3 100644
--- a/docs/install/t60_unbrick.html
+++ b/docs/install/t60_unbrick.html
@@ -39,7 +39,7 @@
In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:
- *Those dd commands should be applied to all newly compiled T60 ROM's (the ROM's in libreboot binary archives already have this applied!):
+ *Those dd commands should be applied to all newly compiled T60 ROM images (the ROM images in libreboot binary archives already have this applied!):
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k
dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump
dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
diff --git a/docs/install/x60_unbrick.html b/docs/install/x60_unbrick.html
index 3b3d6be..89edfb4 100644
--- a/docs/install/x60_unbrick.html
+++ b/docs/install/x60_unbrick.html
@@ -39,7 +39,7 @@
In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:
- *Those dd commands should be applied to all newly compiled X60 ROM's (the ROM's in libreboot binary archives already have this applied!):
+ *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k
dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump
dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
@@ -246,7 +246,7 @@ POMONA 5250:
- Trisquel live USB menu (using GRUB's ISOLINUX parser):
+ Trisquel live USB menu (using the GRUB ISOLINUX parser):
diff --git a/docs/install/x60tablet_unbrick.html b/docs/install/x60tablet_unbrick.html
index cd2878c..0510867 100644
--- a/docs/install/x60tablet_unbrick.html
+++ b/docs/install/x60tablet_unbrick.html
@@ -39,7 +39,7 @@
In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:
- *Those dd commands should be applied to all newly compiled X60 ROM's (the ROM's in libreboot binary archives already have this applied!):
+ *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):
dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k
dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump
dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
@@ -96,7 +96,7 @@
- Some X60T's you have to unroute those too:
+ For some X60T laptops, you have to unroute those too:
- If you are using one of the ROM's with 'serial' in the name, then you have serial port enabled in libreboot + If you are using one of the ROM images with 'serial' in the name, then you have serial port enabled in libreboot and you have memtest86+ included inside the ROM. Connect your null modem cable to the serial port on the dock and connect the other end to a 2nd machine using your USB Serial adapter.
diff --git a/docs/release.html b/docs/release.html index 6659faa..18e2ea3 100644 --- a/docs/release.html +++ b/docs/release.html @@ -91,7 +91,7 @@
diff --git a/docs/security/x60_security.html b/docs/security/x60_security.html
index 69a8e4e..c87c581 100644
--- a/docs/security/x60_security.html
+++ b/docs/security/x60_security.html
@@ -138,9 +138,9 @@
Reason: has direct (and very fast) memory access, and could (theoretically) leak data over a side-channel.
Wifi: The ath5k/ath9k cards might not have firmware at all. They might safe but could have
access to the computer's RAM trough DMA. If people have an intel
- card(most X60's come with Intel wifi by default, until you change it),then that card runs
+ card(most X60s come with Intel wifi by default, until you change it),then that card runs
a non-free firwamre and has access to the computer's RAM trough DMA! So
- it's risk-level is very high.
+ the risk-level is very high.
Wwan (3d modem): They run proprietary software and have access to the
computer's RAM! So it's like AMT but over the GSM network which is
probably even worse.
--
cgit v0.9.1