The partition ID problem might be one reason for the problems reported, but not the only one:
I'm running FreeBSD on a A20p for about 2 mths now. My system is running, using the following partition layout:
[...]
The data for partition 3 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 4626720, size 7106400 (3469 Meg), flag 0
beg: cyl 306/ sector 1/ head 0;
end: cyl 775/ sector 63/ head 239
[...]
As you can see, my FreeBSD slice is type 0xa5, but the BIOS does in fact boot the machine.
I've contacted some people at ibm, expressing my displeasure concerning the above mentioned "support" notice. It seems as they will be discussing this problem again.
It could be helpful, to have more customers complaining at ibm's support lines...
regards,
cpunkt
Slashdot Mirror
The partition ID problem might be one reason for the problems reported, but not the only one: I'm running FreeBSD on a A20p for about 2 mths now. My system is running, using the following partition layout: [...] The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4626720, size 7106400 (3469 Meg), flag 0 beg: cyl 306/ sector 1/ head 0; end: cyl 775/ sector 63/ head 239 [...] As you can see, my FreeBSD slice is type 0xa5, but the BIOS does in fact boot the machine. I've contacted some people at ibm, expressing my displeasure concerning the above mentioned "support" notice. It seems as they will be discussing this problem again. It could be helpful, to have more customers complaining at ibm's support lines... regards, cpunkt