Description of problem: Downloaded and attempted to install fc-development. I had previously installed both RHL9 and FC1 on these system. Both systems are dual processor. The P-II has a WDC 6.4GB drive and a WDC 18GB drive. The P-III has two Maxtor 60GB drives and a Maxtor 80GB drive. The install is an NFS install booting from cdrom created from boot.iso. I have the BIOS configured on both systems for IDE LBA. On the P-III system, I have most partitions pre-allocated. When I went to install, I got a popup for hda and hdb (two 60GB drives) saying the BIOS values were not correct and should reboot with hda=7476,255,63 For the P-II, I only have hda1 and swap defined on hda. When I went to install, I again got a popup saying that the detected values of 13328,15,63 was not correct and that I should reboot with hda=784,255,63. If I switch to VT-2 and ran fdisk, it displayed the proper (LBA) values. Version-Release number of selected component (if applicable): FC2-development as of 12/15/03 How reproducible: Every system with IDE disks
Mmmm ... parted seemed to be the same one which is in FC1 so I did not believe it was the problem. But then again, maybe it is something in the kernel which changed and parted still works the "old way" and is not responsive to the change. It appears to me that parted does not look at the partition table actually on the disk since fdisk reports the correct (LBA) values. It is interesting that when I used the hda=784,255,63 paremter at boot time and actually installed the system, when I booted the actual system, it looked OK.
The kernel used to actually do more dark voodoo determination and then export those values to userspace. Now it doesn't, instead requiring every user space program to do so instead :(
*** This bug has been marked as a duplicate of 115980 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.