I've just installed the system using the alternate-install CD as I said
before. Although this doesn't _solve_ the problem (no live CD, and no
card reader), if you want to _bypass_ it:

- Install from the alternate CD. The sdhci module will not interfere with the 
process.
- When done, boot again from the CD and use the recovery system to start up a 
terminal rooted on whichever partition holds your installation (or wherever 
you've decided to put your /etc). Type echo "blacklist sdhci" >> 
/etc/modprobe.d/blacklist , then exit and reboot into your new system.

This was a lot more complicated when the 8139 problem overlapped with
this one, since debian-installer attempts to set up the network, so one
had to prevent it from hanging by awkward means. I'm glad we got rid of
that one!

Regarding the lack of a blacklist-module-on-boot capability in Ubuntu,
I've noticed this idea on the Ubuntu brainstorm site,
http://brainstorm.ubuntu.com/item/86 , which seems not to be too popular
at present. I've made my case for it, perhaps some of the people
affected by this bug may want to add a comment as well?

-- 
sdhci module hangs Everex StepNote 2053T
https://bugs.launchpad.net/bugs/187671
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to