|
|
| (19 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| − | ==Use the HPA for GNU/Linux?==
| |
| − | More interesting than removing the HPA (which includes a.o. Acces IBM Predesktop Area, some other tools and a backup of the pre-installed OS) would be to use this area for GNU/Linux too. At least, removing the HPA only saves 3,5 GB on my 60 GB hard disk. It would be worth a try to see whether the backup of the pre-installed OS on the largest PSA could be replaced by a backup of your favourite GNU/Linux distribution.
| |
| | | | |
| − | Elaborating on my ideas a few days later, I'd guess the following could be tried:
| |
| − | * see whether GRUB can be made to boot the Access IBM Predekstop Area (I guess by "chainloading" the bootsector of its PSA). Right now GRUB refuses to load sectors outside the partioned area. I've got absolutely no idea if it's possible to write a hack to overcome that restriction. Need to contact the GRUB people about that ...
| |
| − | * write a HPA or SPA driver. That driver should provide something like "/dev/hpa", "/dev/hpa0", etc or "/dev/spa", "/dev/spa0", whatever. The idea here is that it allows you to simply mount (ro!) the Hidden Protected Area (given the correct BIOS settings). Probably just an addaption of the current drivers for (IDE?) harddisks. (This might mean "/dev/hda" and "/dev/hpa" overlap: dangerous?) That would probably need - way - more coding skills than I have ...
| |
| − | * write some userspace tools for the HPA/the SPAs (things like: dumpbeer, printDoS).
| |
| − |
| |
| − | It should be clear these are basically random ideas. Still feedback would be appreciated ...
| |
| − | ----
| |
| − | Hei,
| |
| − |
| |
| − | interesting ideas, but i'd only see a point in it if one could keep Win and Linux rescue stuff in the HPA. That means it would need to be expandable or fit the stuff for both systems.
| |
| − | [[User:Wyrfel|Wyrfel]] 20:03, 15 Mar 2005 (CET)
| |
| − | ----
| |
| − | Thanks.
| |
| − |
| |
| − | Short answer: that should be possible.
| |
| − |
| |
| − | Long answer: I see little in the specs (as I understand them now) to stop one from adding (say) an extra 3 GB GNU/Linux-rescue PSA or something like that. We might try to do that first by changing the BEER and DoS manually. (Not sure whether Phoenix added some proprietary stuff to keep you from booting it. The PSA should always be accesable with the proper BIOS setting.) It might be mandatory to put it on a FAT filesystem. The hard part probably is to have it show up in the Access IBM Predesktop Area. (My guess is you need to regenerate the FirstSight "graphical shell". If that's correct we probably only can use the FirstWare tools "hidden" on their little PSA. That's no fun. Well it might a little fun if we try FreeDOS).
| |
| − |
| |
| − | [[User:Pebolle|Paul Bolle (not logged in)]]
| |
| − | ----
| |
| − | Update: a trivial patch to grub allows it to also work outside the partioned area:
| |
| − |
| |
| − | --- /var/tmp/rpm/BUILD/grub-0.95/stage2/disk_io.c.oud 2004-05-23 18:35:24.000000000 +0200
| |
| − | +++ /var/tmp/rpm/BUILD/grub-0.95/stage2/disk_io.c 2005-03-18 22:38:30.050907408 +0100
| |
| − | @@ -297,8 +297,8 @@
| |
| − | * Check partition boundaries
| |
| − | */
| |
| − | if (sector < 0
| |
| − | - || ((sector + ((byte_offset + byte_len - 1) >> SECTOR_BITS))
| |
| − | - >= part_length))
| |
| − | + /*|| ((sector + ((byte_offset + byte_len - 1) >> SECTOR_BITS))
| |
| − | + >= part_length)*/)
| |
| − | {
| |
| − | errnum = ERR_OUTSIDE_PART;
| |
| − | return 0;
| |
| − |
| |
| − | I made a grub CD with a grub patched with the above. Now I can "cat" the bootsector of the Predesktop Area from the grub shell (when booting of that grub CD). But I haven't yet managed to boot the Predesktop Area (dangerous stuff!) To be continued ...
| |
| − |
| |
| − | [[User:Pebolle|Paul Bolle]] Fri Mar 18 22:42:43 CET 2005
| |
| − |
| |
| − | ----
| |
| − |
| |
| − |
| |
| − | I've been playing around with the predesktop area tonight. I was simply trying to just leave the diagnostics stuff and remove the windows part. I wrote some programs to read/write the BEER data and stuff, but I wasn't able to get the system to boot it, it kept erroring "Authentication of System Services failed" (or something along those lines). I will play around with this some more later
| |
| − |
| |
| − |
| |
| − | [[User:Invisi|Tim Nordell]]
| |
| − | ----
| |
| − |
| |
| − |
| |
| − | A quick look with a hexeditor gave me two instances of "Application authentication has failed!" in the FirstSight application. Does that sound familair?
| |
| − |
| |
| − | [[User:Pebolle|Paul Bolle]] Fri Apr 1 19:35:30 CEST 2005
| |
| − |
| |
| − | ----
| |
| − |
| |
| − |
| |
| − | Actually it wasn't that. I did a search of that too, the message itself was not in the predesktop area at all. What also is interesting is the fw*.exe utilities for manipulating the predesktop area, contains the string "MD5" which makes me wonder if there is an md5 hash of each "predesktop" partition. I know on the IBM whitepaper it states there being a signature so that non-signed applications can not be run. Could a simple "md5" be the signature?
| |
| − |
| |
| − | [[User:Invisi|Tim Nordell]] 12:01, 3 Apr 2005 (CEST)
| |
| − |
| |
| − | ----
| |
| − |
| |
| − |
| |
| − | *What is it that you were trying to do (what did trigger the error you saw)?
| |
| − |
| |
| − | *About ten of the fw*.exe utilities contain the phrase "MD5 Checksums do not match". So they could very well be using MD5 sums for some sort of validation. But they could use the MD5 sums in a lot of ways actually, so I won't yet speculate ...
| |
| − |
| |
| − | [[User:Pebolle|Paul Bolle]] Sun Apr 3 15:11:10 CEST 2005
| |
| − |
| |
| − | == Predesktop Area ==
| |
| − |
| |
| − | I made a program that takes the BEER record at the end, parses it out to a ".cfg" file, lets you modify it, recalibrate the start spots for the records, and write it out to disk again. It doesn't directly access hda, 'cept for reading the original beer record. It makes a script file to go with the files you have, to read in the HPA data, and to write it out again with the new record.
| |
| − |
| |
| − | Anyways, I tried simply removing the last record from the BEER, which is the windows recovery partition. It didn't like that.
| |
| − |
| |
| − | ----
| |
| − |
| |
| − |
| |
| − | Did you update the two's complement checksum at the end of the BEER?
| |
| − |
| |
| − | [[user:Pebolle|Paul Bolle]]
| |
| − |
| |
| − | == TODO ==
| |
| − |
| |
| − | * Ad a section on dmesg and hdparm -I output:
| |
| − | (...)
| |
| − | Commands/features:
| |
| − | Enabled Supported:
| |
| − | (...)
| |
| − | * Host Protected Area feature set
| |
| − | (...)
| |
| − | SET MAX security extension
| |
| − | Address Offset Reserved Area Boot
| |
| − | (...)
| |
| − |
| |
| − | * Check boot parameters: is hda=stroke still valid?
| |
| − | Kernel command line: ro root=LABEL=/ acpi=off hda=stroke
| |
| − | ide_setup: hda=stroke -- BAD OPTION
| |
| − |
| |
| − | [[User:Pebolle|Paul Bolle]]
| |
| − |
| |
| − | == Two's Complement ==
| |
| − |
| |
| − | Yep, I updated that. If I don't update that, it doesn't even say that failed message. I also made a seperate program to update the checksum so you can also modify the beer record by hand with a hex editor and have valid checksums.
| |
| − |
| |
| − | == RE: How to remove it / ATTENTION! ==
| |
| − |
| |
| − | Please tell us how you are trying to access the BIOS. Via "Access IBM" or F12 (or something similar)? "Access IBM" at start up shouldn't work when you remove the HPA (that's my guess at least) but F12 at start up should work (I would be very surprised if it didn't ....).
| |
| − |
| |
| − | [[user:Pebolle|Paul Bolle]] Fri Jul 15 01:11:33 CEST 2005
| |
| − | ==What about that IBM link???==
| |
| − | Hei Paul, why did you remove that IBM link? I think it's nice to know what IBM has to say about this, even if it doesn't help much. At least i find it interesting that they have something to say about it.
| |
| − |
| |
| − | Wyrfel.
| |
| − | ----
| |
| − | Ok, I'm getting it, roughly. Now what's the "Recovering Partition" as opposed to the HPA??? Wyrfel.
| |
| − |
| |
| − | ----
| |
| − | Wyrfel,
| |
| − |
| |
| − | Let met _try_ to explain. (Please google on "Andries Brouwer" and partitions for more correct info on partitions.)
| |
| − |
| |
| − | Recovery partitions are ordinary partitions, accessible through the (let say) partition tree (the chain of the MBR [in /dev/hd''x''] and boot records [in /dev/hd''xn'', /dev/hd''xm'', etc]). As they are ordinary partitions they are (easily) accessible by ordinary (partitioning) tools (read: easily messed up). One of the things you can do with ordinary partitions is (sort of) "hide" some types of those. Anyway, this is what the IBM link was about.
| |
| − |
| |
| − | Protected Service Areas on the other hand are (lets say) images of partitions written to the end of a harddisk. They are only accessible through their BEER. The general idea here is that with the correct settings in BIOS (and I guess some cooperation of the OS) the PSAs are totally hidden from all (ordinary) tools. Under certain conditions they still could be accessible through special PSA tools and under GNU/Linux they are only accessible with low level tools like dd (either always or if certain kernel parameters are set?) .
| |
| − |
| |
| − | [[user:Pebolle|Paul Bolle]] Fri Jul 15 12:09:34 CEST 2005
| |
| − |
| |
| − | == Newer thinkpads don't use Phoenix Firstware? ==
| |
| − |
| |
| − | On my T42 that arrived yesterday, the predesktop area looks a lot like MS Windows. The widget set, the fonts, even the boot sequence looks exactly like Windows 2000. Debian-installer indentified it as "Microsoft Windows NT/2000/XP", while it identified my XP partition as "Microsoft Windows XP Professional"
| |
| − |
| |
| − | Has Lenovo/IBM changed their system, or is this Phoenix stuff really just Windows?
| |
| − |
| |
| − | -- EvanHeidtmann
| |
