Comment # 60 on bug 1173733 from Matthias Bach

(In reply to Mister Pend from comment #59)
> (In reply to Matthias Bach from comment #52)
> > Based on the previous test I have been able to solve the problem for myself.
> > The solution is as obvious as hidden in plain sight. All I had to do was
> > execute the following:
> > 
> > /sbin/mkinitrd
> > 
> > Still, I don't fully understand _why_ this solves the problem. I always
> > assumed the driver installation to trigger this.
> > 
> > Maybe Mister Pend or Cor Blom can confirm this behaviour.
> 
> Sorry, I've tried on separate systems and can't confirm this. Executing
> mkinitrd doesn't error, but doesn't solve the issue. Even after a further
> reboot.

After the last driver update, and having worked around bug 1174204, I know also
have the issue again. The /sbin/mkinitrd didn't help this time, so it must have
been something else that fixed it for me back than.

Still, I have that weird effect that unloading the modules after boot will
actually make the system work as expected afterwards, until the next reboot.