Dapper F5 Hibernate slows GRUB to crawl

Bug #34744 reported by Dan MacDonald
6
Affects Status Importance Assigned to Milestone
hibernate (Ubuntu)
Invalid
Medium
MOTU

Bug Description

I just did a fresh install of Dapper Drake Flight 5 on my ASUS A7N8X Deluxe w/ Athlon XP 2000, 512MB RAM, 80GB ATA-133 Maxtor drive, NEC 16x DVD-RW and a Lite-On 52x CDRW. I'm using the stock i386 kernel and I'm dual-booting with Breezy. If I just do a normal reset, Dapper boots OK (GNOME does take longer to boot than under Breezy tho) but using hibernate causes GRUB to act strangely- slowing right down and defeating the whole point of hibernate.

After doing choosing hibernate, the computer shuts down OK. Turning it back on, it says

GRUB loading, please wait

And that stays on for about a minute before the GRUB menu comes up. I then select Dapper and then it takes about another minute or so for GRUB to get up to saying

Uncompressing Linux, OK booting kernel

When it gets to that point it resume normal speed and boots OK. This didn't happen under Breezy, but under Breezy my sound wouldn't work without messing with ALSA mixer after hibernating so I didn't bother. The hibernate sound problem with my Audigy ZS2 seems to be fixed in Dapper.

Revision history for this message
Dan MacDonald (danboid) wrote :

I just installed the Dapper k7 kernel, rebooted then tried hibernating again and the same problem occured but this time X didn't come up, just a blank (black) screen.

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

Thanks for the report Dan.
Could you try again with the recent beta2 dapper?

Changed in hibernate:
assignee: nobody → motu
status: Unconfirmed → Needs Info
Revision history for this message
Dan MacDonald (danboid) wrote :

I've just installed Ubuntu 6.06 on the same machine. The same hibernate problem was still present on a fresh and remains after I updated the system

Revision history for this message
William Grant (wgrant) wrote :

Is it still present in Edgy, Feisty or Gutsy?

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hibernate:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.