Description of problem: Installation of Fedora 10 Beta isn't working. First problem found on the first graphicahl screen with button 'Next', notebook rebooted wen I plugged out AC/DC adaper(battery was 100% charged). I've tried installation one more times, got through all steps, unchecked all of 3 installation package variants. Installation finished sucessfully, but after reboot fedora starts loading, with kernel message: "pci 000:01:00.0: BAR 6: can't allocate mem resource [0xe0000000-0xdfffffff]", after that progress bar appears, and computer reboots when progress bar reaches 1/5~1/4 all progress. Tried both boot choices available - neither helps. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
You need to report bugs for the installer in the "component", I just changed this for this bug report. Otherwise the people who can fix your issues, will not find your bug report. :-)
The main problem is that I can't use just installed Fedora. Installation finishes normally. But it is impossible to start just installed system. Btw. I tried installing Fedora 9 x86_64 - somewhat similar results: installer finished successfully but system just restarts after booting. Last few text lines seen: ----------------------- Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: -------------------------- Tried single mode - result is the same. So i don't know if it is installer problem. But also I don't know which component is responsive for this restart...
Tried with acpi=off option, F9 will boot then OK. Will try acpi=off on F10 tomorrow. BTW. AFAIK acpi=off parameter forces kernel to work only with one core, so I don't think it is acceptable solution.
Confirmed F10, also works with acpi=off. Now trying to update to newest rawhide kernel.
If you need to pass acpi=off to the kernel, the bug is in the kernel, not the acpi helper programm, therefore I reassign this bug.
updated kernel 2.6.27.3-27.rc1.fc10.x86_64 - the same results, isn't booting without acpi=off
If you remove "rhgb" and "quiet" from the kernel boot options, can you see any messages just before it reboots? (Press up-arrow on the first boot screen and edit the options for the kernel.)
Already did this: see comment #2. Btw. actually I don't know how to activate this interactive mode. By pressing 'i' or 'I', trying to press it once or keep pressed - nothing happens. This is the problem as I remember - it seems that I never succeeded activating interactive mode, last time I saw it working was on some last RedHat before FC1. P.S. If you need more details - just ask, and you can ask using low level language - behind me almost 10 years of Linux developer experience. :)
Ok - it was F9, on F10 beta not a big difference: Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: don't know how to make device "loop1" don't know how to make device "loop2" don't know how to make device "loop3" don't know how to make device "loop4" don't know how to make device "loop5" don't know how to make device "loop6" don't know how to make device "loop7" don't know how to make device "lp1" don't know how to make device "lp2" don't know how to make device "lp3"
If you add udevdebug to the kernel boot options you should get a lot of diagnostic info from udev as it loads drivers.
Trying with today's latest kernel(2.6.27.3-34.rc1.fc10.x86_64) and other updates. Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: Messages "don't know how to make device..." disappeared. If I try to use 'udevdebug' - lots of text scrolls, and then immediately reboots - no way to notice text. Looking for way to stop this auotoreboot or to put all output to some log file...
No idea, how to get these last messages - messages can be found on the log file but only if there was successful boot, without acpi=off system restarts immediately and no log files are updated :( tried netconsole, but also unsucessfuly - either netconsole doesn't work from kernel boot, or ethernet device is initialized somewhere later or something wrong with netconsole params...
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I just wonder is there any progress on this bug? Just tell me how can I help debugging this issue? I've already updated latest BIOS, it had no effect on this issue. I'm also once a week updating to the newest kernel and still the problem persist. Even with acpi=off it is hard to work with OS, because plugging in/out power or just closing lid makes instant reboot.
I've also found on inet, that 32bit version is working ok, so it seems that this problem is 64bit problem...
Hey, some breakthrough at least! Using kernel boot parameter mem=4096M is working ok, tried with latest kernel: 2.6.27.7-134.fc10.x86_64. Only notice, it seems that system is using only 3GB of memory: $ free total used free shared buffers cached Mem: 3089588 638584 2451004 0 3892 97668 -/+ buffers/cache: 537024 2552564 Swap: 4200988 217732 3983256 It can be related with shared graphics memory? The mem=4096M idea I found on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272530 - you can look here to find some adittional details about this issue.
Exactly the same problem on my Samsung R510 notebook. And kernel boot parameter mem=4096M is working as temporary solution with only 3GB memory accessible.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.