Re: Installing on old systems with only PATA/IDE hard drives
On Sun, 2013-05-12 at 21:27 -0400, Basil Mohamed Gohar wrote: I thought that this might be an issue with incompatible hardware, as I was trying to install Fedora 18 on an old Dell (Celeron D processor) I'd bought for my mother that she was no longer using. However, I got an error when attempting to install when the process was probing the drives. I thought maybe it was something wonky with the Dell hardware, so I ignored it for the time being, as the only results when searching online were apparently older, seemingly unrelated bugs fixed in previous kernel commits. However, I ran into the same problem when attempting to install to a more recent AMD 64-bit system that I'd put together (and which has had older versions of Fedora installed on, but I cannot remember which at this time), but which still stalled at the same point during the install. In both cases, the install process dropped to the dracut emergency prompt, and in both cases, I was attempting to install from a USB stick. The USB stick image was verified in both cases, as well. The same issue happened with both DVD images as well as netinst images. I tried with both F18 and F19 Alpha. Both systems were installing to an 80GB EIDE/PATA hard drive. I encountered the same problem attempting to install to a 20GB drive as well. It's a little challenging because the disk is inaccessible, and I could not figure-out how to save the install log up to that point. Any tips on what I can do to make a proper report out of this would be most appreciated, or just let me know if installs to PATA/EIDE systems are just no longer supported. I could not find any language addressing this issue online, but that could be just insufficient Google-Fu. We do have an install-to-IDE device test in the validation matrix: https://fedoraproject.org/wiki/QA:Testcase_install_to_PATA_device but for the last few releases it's mostly been marked as pass by me on the basis of virtual machine testing, so it's just barely possible it's somehow broken on real hardware. I'd be surprised, though. The way I test this is just to remove the virtio 'disk' from my test VM and re-add the same disk image as a PATA 'disk' instead. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Installing on old systems with only PATA/IDE hard drives
Any tips on what I can do to make a proper report out of this would be most appreciated, or just let me know if installs to PATA/EIDE systems are just no longer supported. I've got a i686 box with only PATA, and two root partitions of F19-Alpha-i386; one via netinst+network, one via netinst+USB. (The box cannot boot via USB.) Both roots have been yum update daily with updates-testing. The anaconda installer keeps its log files in /tmp, and you should attach those files to a bug report. 'scp' them to another system (the network will be up if the installer gets that far). Or, copy to a USB stick then move that USB stick to another system. Then file the bug report. Change to console VT2 by typing CtrlAltF2 where F2 is Function key F2. dmesg (or tail /tmp/syslog) to determine which /dev/sdX is the USB stick mkdir /stick mount /dev/sdX1 /stick cd /stick mkdir MMDDa # such as '0513a'; probably you're going to be doing this more than once cd 0513a cp /tmp/* . # ignore the directories; you want the top-level files sync cd /tmp umount /stick Change back to installer graphics with CtrlAltF7. -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Installing on old systems with only PATA/IDE hard drives
On 05/13/2013 12:50 AM, John Reiser wrote: Any tips on what I can do to make a proper report out of this would be most appreciated, or just let me know if installs to PATA/EIDE systems are just no longer supported. I've got a i686 box with only PATA, and two root partitions of F19-Alpha-i386; one via netinst+network, one via netinst+USB. (The box cannot boot via USB.) Both roots have been yum update daily with updates-testing. The anaconda installer keeps its log files in /tmp, and you should attach those files to a bug report. 'scp' them to another system (the network will be up if the installer gets that far). Or, copy to a USB stick then move that USB stick to another system. Then file the bug report. Change to console VT2 by typing CtrlAltF2 where F2 is Function key F2. dmesg (or tail /tmp/syslog) to determine which /dev/sdX is the USB stick mkdir /stick mount /dev/sdX1 /stick cd /stick mkdir MMDDa # such as '0513a'; probably you're going to be doing this more than once cd 0513a cp /tmp/* . # ignore the directories; you want the top-level files sync cd /tmp umount /stick Change back to installer graphics with CtrlAltF7. Thanks, John. I'll try my best to follow these steps the next time I go through the install, and see what I can get. I'll put it all in a bug report, most likely. -- Libre Video http://librevideo.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Installing on old systems with only PATA/IDE hard drives
I have multiple PATA-only systems running F18 and/or F19, but all are pre-newUI HTTP installations that have been Yum upgraded. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
