Upon further review of my notes: the stalling is not actually occurring while
loading the pata_sis driver, it appears to be happening immediately after this,
while displaying that it is "Loading usb-storage driver...".

This is still an issue with the final release version of the fedora 7
installation dvd. I have, however, successfully installed fedora 7 from the live
cd on the same test machine as mentioned above.

Please let me know if anyone wants the lspci output of machine that doesn't have
the stalling problem when booting the installation dvd.

I will try to update this bug report with this new version and summary information.

Hello Gabriel,

I'm reviewing this bug as part of the kernel bug triage project.

http://fedoraproject.org/wiki/KernelBugTriage

As this is possibly an issue with the usb subsystem I have added a blocker bug
in an attempt to get more interest in resolving your issue. Please could you
confirm this is still an issue for you with the latest kernel. 

As there has been no activity for a while it is possible things are resolved so
I will close in a week or so if no additional information is forthcoming.

Cheers
Chris

Hi Chris,

Thanks for looking into this. The short answer to your comment is that, yes this
is still an issue, due to the fact that, as mentioned in comment #1, i have the
same problem with the fedora 7 final release installation dvd. This installation
dvd iso image, to my knowledge, has not changed since release, and therefore the
problem still stands that when i try to boot off of the installation dvd, it
still hangs as described above. Ideally, one would hope that this "stalling"
problem, which may or may not be unique to the sis chipset in my test box, would
be addressed, and an updated installation dvd iso respin would be published so
that others using similar hardware would not encounter the same problem. Also,
as mentioned above, the live cd does not exhibit this defect, and i was able to
install fedora 7 onto my test box from that disc.

As for this being an issue with the _current_ kernel, that is somewhat
irrelevant, because this is an issue with the kernel / configuration / subsystem
that is present on the installation dvd iso. That is actually what made it so
difficult for me to categorize this bug report from the beginning. Please add a
comment to contact me via CC List ASAP if you require additional info or assistance.

Hello Gabriel,

Ugh, sorry for the horrendous delay. So I wonder if you've been able to test
this with either the F8 installation DVD or one of the Fedora Unity spins:

http://spins.fedoraunity.org/spins

which might help. My hope is that highlighting this issue as a blocker bug
caused it to be addressed for F8 but if you could update the bug with the latest
that would be greatly appreciated. I'll also try not to take 3 months to respond.

Cheers
Chris

Hi Chris,

Glad to hear this hasn't been forgotten about; thanks for working on it.

I still experience the same problem with the F8 installation DVD. Haven't tried
any re-spins. If i do manage to find some time to do that, i'll be sure to let
you know the results. Any word on what might be causing this annoying behavior
when trying to install? Like i said, this isn't a problem when booting and
installing via the live cd. What's going on during the driver loading / startup
routine of the installation DVD that could be causing this on this particular
machine?

Difficult to say without more information. If you can switch tty's when running
the install (Ctrl+Alt+FunctionKey 1 -6) and post back what each gives you that
might be helpful.

Have you discounted bad media and tested with another DVD?

Check here:

http://fedoraproject.org/wiki/KernelCommonProblems

for additional information on hanging installs. Thanks for the feedback - keep
it coming!

Updating bug title to reflect issue

The media was fine, and i did burn at least two copies. All copies had the same
result where the installer would hang during startup on my test box, but were
able to continue past that point on my primary workstation and even pass the
built-in media check there.

I'll keep you posted with further information and test results, as time permits.

This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.