Typical - been looking at this off and on for a week or so, but posting
here got me looking again. Searched for "linux 90 second boot delay" and
found a few people who'd found that the swap partition was incorrectly
configured, causing a 90 second delay.
I'd also changed my SSD for a bigger one
I've got a similar issue in that there's a pause of around 90 seconds
during boot, though the messages either side of the pause are different.
Thing is, there's no way of knowing whether the messages either side are
even relevant - I can't believe that an almost identical length pause is
not
I have the same problem ( on a VPC Z12 ) but unlike others I can find no
way to get the Intel card working - though this may be because I have
kept the fake raid 0 set up and am dual booting with Windows 7, and so
booting without using grub 2 seems impossible. However, I have tried
booting the
Yep, works here ( tried the amd64 generic kernel. )
Thanks Tim.
--
URGENT for upcoming release: Resolutions requiring dual link DVI on radeon
result in no display
https://bugs.launchpad.net/bugs/564559
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Tim. Sorry, not that it should make a difference but your
Impact/Description in #5 is slightly wrong. The impact is that dual-link
( not dual ) DVI fails to work, and the patch checks for a pixel clock
above that of single-link and initialises dual-link accordingly.
Thought that I'd better
Public bug reported:
Please see https://bugs.freedesktop.org/show_bug.cgi?id=27001
I assume that this is now ( as of yesterday ) in the upstream kernel.
However, all kernels so far shipped with lucid have the issue and it
would be good if it could be patched in the Ubuntu Lucid kernel before
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/44409866/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/44409867/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/44409868/ArecordDevices.txt
I've just come across this one myself... again an NEC CDROM though this
time in a Laptop ( a Philips Freevents model. ) Since changing the CDROM
is not an option for me, and I don't have a USB CDROM drive handy, I
came up with this workaround:
When the message appears the first time:
Ctrl-Alt-F2
