El jue, 03-06-2004 a las 19:42, Alexander Dalloz escribió: > Am Do, den 03.06.2004 schrieb M Daniel R M um 18:05: > > > Please, I would like to hear any suggestions. > > I couldn't install Fedora 2 yet! I haven't been able to install it > > successfully. I've tried it on many ways, and nothing... > > Maybe, It would be better if I forget it? > > > Daniel R M > > Actually I do not find my crystal ball, so I can't suggest you anything > specific. Maybe until I find it you can help us with giving some > hardware data of the machine where the install fails? > > Alexander > Previously: The RedHat9 was running at this box during 12 months, and never problems. The Fedora 1 is currently running at the same box and greatly ... loving... That's my real, preferred home workstation. And also a SuSE 9.0 Pro that I also use frecuently , and a w2k that I hardly ever use (from term to term). I have the grub of SuSe managing the boot up (added manually a new entry for FC1 after installing it -about 1 month ago). All right. I would just like to try FC2 BEFORE and to decide later if it worth to switch to FC2 abandoning the FC1. I didn't want risks. So, I made appropiate partitions on the hard disk TWO. I am only a limited newbie user, It's obvious. I've tried things that previously I've found searching via google, no more. Sorry for my English. Hardware: Motherboard Gigabyte GA-8INXP, Serial ATA controller Silicon Image Si3112 on board 2 hd SATA connected, no RAID. processor Intel P4 2.8 GHz 533 2 Dual DDR RAM 512 MB each one ATI Radeon 9600 Pro Graphics Card ............................... The system is very stable (14 month running) Failed attempts: 1) Booting up with the CD1 (FC2) >Anaconda installer > nothing automated, absolutely "personalized" install process > Disk Druid for checking on hd2 /boot, /, swap, and /home partitions. Grub not in MBR, but on its /boot; WARNING: the most heavy warning I've ever read: something like that the partitions table on hd1 was wrong, and I have to accept to "correct" it LOOSING all data and partitions on that disk. Of course, I didn't want to accept similar suggestion. > Next step and screen: it seemed the hd1 didn't exist, no graphical draw of it, only the hd2. >>The installation process ended up "successfully", but after rebooting it didn't work. At this point some painful things happened that are a bit large to tell here, but summarizing... I expected a) Rebooting and (if FC2 installer trully didn't touch the MBR) seeing my old original grub options, get into SuSe and simply add a new entry for FC2 in its grub. b) Rebooting and (if FC2 installer did touch the MBR -bad boy...) get into FC2 directly (As how the events were happening, sincerely I didn't expect that FC2's grub were able to find and add the existing entries...). It happened no a) nor b)... I had to managed to revert the situation (with the rescue mode of Suse media); of course, I've never been able to load FC2 system properly. >>Many attemps, many fails; trying to place the /boot (FC2) at the fist top of the hd2 as primary partition, etc, etc. Without results. A great waste of time.I don't want to bore you in this way... 2) Then I read some troubles related with the FC2 installation that I found at: http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html http://www.ces.clemson.edu/linux/fc2.html http://www.redhat.com/archives/fedora-test-list/2004-May/msg02114.html http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115980 As you can see, almost all them were wrote recently. But the main bug date from January (or so) !!?? I can't understand how it is possible... The bugs tell about an issue with the dual boot WinXP and FC2. But the important for me is that it looks probed that the Anaconda installer from FC2 (due to its new kernel 2.6.x ???) will touch (without advising -like it did upon my hd1) and will change the geometry of the disks; it looks like that (for my case) it's enough with running the parted of Disk Druid. That explains many things about what I had to suffer... So, it is supposed that if you do an clean installation, automated, without considering any other O.S., things go right, but if not...problems probably become (It reminds me the most famous O.S. in the world...). I didn't want that the FC2 change my hd1 geometry at all. I've checked that geometry several times in different ways; I knew the "fdisk -l", at the top throws it before listing the /dev/ tree. Then I did the same with sfdisk -V And... cat /proc/ide/hd[x]/geometry and... grub > geometry (hd0) / and (hd1) Finally, I rechecked it with the FC2 Disk 1 in booting in rescue mode (fdisk -l) Although I don't understand the difference between fdisk and sfdisk, and why the meaning of co-existing both, etc. it looks like that the geometry is (C,H,S) = (14593,255,63) at both disks. 3) Last, I tried to install it like that: a) boot: linux hde=14593,255,63 hdg=14593,255,63 Fails: "kernel panic..." b) boot: linux acpi=off hde=14593,255,63 hdg=14593,255,63 Fails: "kernel panic..." c) boot: linux acpi=off selinux=permissive hde=14593,255,63 hdg=14593,255,63 Fails: the same... d) I've also heard about enforcing=0 , but even don't know what really means. And the "noapic" option, but neither tried yet. e) The BIOS settings of my mb don't have any "acpi" option, or at least I couldn't find or recognize it. Same thing about LBA mode that the above mentioned links said (I suppose that it is because the disks of mine are S-ATA). Alexander, any idea is welcome. It isn't urgent, because, as I said at the first top, I am very pleased with Fedora Core 1 (including better than with RedHat9), and in my opinion, I suspect that FC2 is like an "hidden" new test version. Regards Daniel Rodríguez Magarzo
