Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042
FYI the above workaround does not work for machines with SATA drives. I couldn't
find a combination of modules that would get it to boot.
Switching back to previous yaird (0.0.11-12) fixes the problem on both PATA
SATA systems.
On Wed, Dec 14, 2005 at 10:42:58AM +, Richard Antony Burton wrote:
Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042
FYI the above workaround does not work for machines with SATA drives. I
couldn't
find a combination of modules that would get it to boot.
Switching back to
Package: yaird
Version: 0.0.12-1
Followup-For: Bug #343042
Confirmed Paulo's suggestion above to be working.
This problem is hitting everyone I know who has updated today. The fact that the
broken yaird was released on the same day as a new kernel means that a lot of
people are going to hit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 12 Dec 2005 16:24:26 +
Richard Antony Burton [EMAIL PROTECTED] wrote:
Considering the potential for harm I wonder if there could be
something done to mitigate this happening again in future. Avoiding
releasing yaird at the same time as
4 matches
Mail list logo
