I'm still getting this error with the lastest Dapper ISO (downloaded the
ia64 CD on 18 Aug 2006).
* My BIOS doesn't have any options whatsoever for my harddrive, so I
can't switch to LBA mode
* Booting the Windows recovery console and running FIXMBR, just got rid
of grub but didn't not bring back
Public bug reported:
At about 9:00 PM EST on Oct 17 I upgraded from Dapper to Edgy using "sudo
update-manager -c -d" and when I rebooted the next morning it got hung during
the boot process. When I tried the failsafe kernel it last displayed "Begin:
Running /scripts/local-top", then listed my
Hmmm...
In GRUB, if I replace "root=UUID..." with "root=/dev/sda3" for the
2.6.15-27-amd64-generic kernel it last prints "Begin: Waiting for root
filesystem..." and hangs there.
If I make the same change to the 2.6.15.26-amd64-generic kernel I get to
the log in prompt. I can't start X since all
Is there any useful information I can give to help anybody debug this?
Here's part of dmesg from the 2.6.15-26 kernel which boots:
[ 30.228987] libata version 1.20 loaded.
[ 30.229872] sata_nv :00:0e.0: version 0.8
[ 30.230415] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 23
[ 30.230
Hi Michael. Thanks for your attention to my problem! I have been able
to get the edgy kernel to boot by passing "acpi=off" in grub. Would the
apt logs still help?
--
Can't boot after upgrading to Edgy (AMD64)
https://launchpad.net/bugs/66837
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
No, I'm using the linux2go.dk repos for nm now.
On 10/3/06, Riccardo Setti <[EMAIL PROTECTED]> wrote:
> hello,
>
> do you still have this bug?
>
> --
> nm-vpn-properties crashes on startup
> https://launchpad.net/bugs/37224
>
--
nm-vpn-properties crashes on startup
https://launchpad.net/bugs/372
TestDisk[1] fixed it for me. When I reinstalled with Feisty (i386), I
didn't have this problem.
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Public bug reported:
Binary package hint: network-manager-gnome
My university does not broadcast its wireless ESSID, so I have to use the
"Connect to Other Wireless Network..." option to manually provide the network
name and enter the WEP key. That's expected the first time, but on subsequent
After an update to gnome-keyring, I am now asked to unlock the keyring
after entering the network information. But it's still not saving that
information.
--
[Gusty] nm-applet wireless network amnesia
https://bugs.launchpad.net/bugs/128511
You received this bug notification because you are a mem
Public bug reported:
Binary package hint: compiz
The crash happens whenever I click "Enable Desktop Effects" in the
Desktop Effects app. All the window borders disappear, then crash
report, and metacity comes back.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Mar 2 07:50:30
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6598669/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6598670/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6598671/Disassembly.txt
** Attachm
11 matches
Mail list logo
