GRUB/Install menu locks up (9.11)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Puredyne Live |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
NOTE: AFFECTS PUREDYNE 9.11
Puredyne never had this problem on my 6 year old HP Desktop. But on a 6 year old HP Laptop, it did.
Setup:
Old HP Laptop <-- USB --> External DVD Drive (With Puredyne disc to boot from)
(1) Live Boot menu problem: It locks up immediately after pressing any key on the Live boot screen, or 95% of the time, locks up after a few seconds even if I don't press a key. Finally after trying many times, I get past the Live boot screen and successfully boot into Puredyne. I am able to install Puredyne on a partition, but end up with problem (2) below...
(2) SIMILAR GRUB problem after installation on Hard drive partition: I can see other partitions Linux and Windows partitions, but if I try to press UP or DOWN key, GRUB freezes. However, if I press no keys after powering on, at least it boots into Puredyne 100% of the time. But I still can't access my other partitions without using Super Grub.
Work-around for (1): None? Try many times to boot off live disk and get lucky 5% of the time?
Work-around for (2) GRUB boot problem: After installing Puredyne, find a way to install a version GRUB 2.0 or later. I believe Puredyne's GRUB 1.97 is the issue. Usually, I just installed a working version of Ubuntu (yes, on ANOTHER partition XD) that had GRUB 2.0 which fixed the GRUB menu.
Question: Perhaps GRUB 1.97 caused the "PC ONLY: the current stick cannot boot on Mac (do you know why? tell us!)" from the Puredyne website?
tags: | added: 9.10 |
description: | updated |
summary: |
- GRUB/Install menu locks up + GRUB/Install menu locks up (9.10) |
summary: |
- GRUB/Install menu locks up (9.10) + GRUB/Install menu locks up (9.11) |
description: | updated |
Changed in puredyne-live: | |
status: | New → Won't Fix |
Yes it could be related...
And same question as your other bug report, 9.11 won't be updated anymore, so it would be good to know if this is a problem for the in-progress 10.10 version.