Created attachment 560825 [details] anaconda log Description of problem: install system with basic video driver, after reboot, get the text "hda_intel:azx_get_response timeout, switching to simgle_cmd mode" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install system with basic video driver mode 2. reboot after installation 3. Actual results: Expected results: Additional info:
Created attachment 560826 [details] anaconda xlog
Created attachment 560827 [details] program log
Created attachment 560828 [details] storage log
Created attachment 560829 [details] syslog
Created attachment 560830 [details] install log
Created attachment 560831 [details] install log syslog
file this as F17Alpha Block according F17 Alpha release criteria article "14.In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account "
There is no firstboot-text in rawhide. I believe this has nothing to do with the firstboot application.
Yeah, there's no firstboot-text app or service in F17 so far as I can tell, so I don't think this is a firstboot issue. Hongqing, can you check if the problem here is some service hanging, or if it's simply X failing to start up? (Check /var/log/Xorg.0.log). Was this a DVD or network install? What version of libpciaccess is installed? Thanks! Discussed at 2012-02-10 blocker review meeting. Agreed we need more information (see above) to make a blocker determination for this bug. Will revisit next week. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
OK, I think I know why this was filed against firstboot-text. A similar issue was brought up in the firstboot-text bug that we hit in F16 (bz#737118) but as stated in bug 737118 comment 32, it is not an issue with firstboot and a different bug needs to be filed against alsa or pulseaudio. Hongqing, can you give more details on the affects of this bug? Is it preventing you from logging into the installed system? What else is going on besides the log messages on the console @ login time?
With F17 Alpha TC2 Before reboot, I got the error on terminal window 2 "Oh no. Something has gone wrong." and the message at terminal window 1 ""hda_intel:azx_get_response timeout, switching to simgle_cmd mode". After reboot, I still hit the information at terminal window 1, but I could login now. There is VESA error in the Xlog.0.log.
Created attachment 561346 [details] X log
I don't see any errors in that X log? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #13) > I don't see any errors in that X log? > > > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers sorry. I think I have mixed it with other guest. I have installed several guests, there is no ERR in X log.
This is fixed with F17 Alpha RC2
Discussed at 2012-02-17 blocker review meeting. As it's reported to be fixed in RC2, we will just close this instead. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers