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
If anyone is still wishing to progress this bug report they need to take note
of Brian Murray's instructions above.
Only two people have responded to Brian's instructions and it seems that they
had different issues to that originally reported in this commentary.
** Changed in:
noktan: i did your 5 steps on a gutsy machine (Fujitsu Siemens Amilo Pi
1536 with ati x1400 mobility) and i have still these no resume
image errors when i typ ctrl+alt+f1
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of
I found this solution on this page as Bug #66637 in util-linux (Ubuntu):
1, determine your swap with 'fdisk -l'
2, do mkswap on your swap partition - RECORD THE UUID WHICH THIS COMMAND
OUTPUTS
3, now use this UUID to put into fstab and resume
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Brian Murray = (unassigned)
Status: Incomplete = New
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I cant solve this problem yet..
I haven't found any .new_pkg files in /etc/event.d
what can i do?
:(
thanks
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
sorry !!
all corrupts files are in /etc/event.d
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Actually I think I was hit by another bug.
I found https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853, followed the instructions and now the machine boots
ok.
Thanks for all assistance!
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification
I do not have any files in /etc/init.d with extension .new_pkg
I have dual boot on this machine (XP) - so I am still able to use it.
But if I do not get this solved soon I will have to reinstall...
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification
i have solve my problem : the error come after the message Kinit
it's due to udev script : all script in /etc/init.d with extension .new_pkg
must be renamed without .new_pkg
and the filesystem / is mount with readonly right
so i issue the command : mount -o remount,rw /
and now gnome starts ...
Hi
I have the same problem . I give you the output of the dmesg command
have you an idea ?
thanks
** Attachment added: dmesg.log
http://librarian.launchpad.net/7379794/dmesg.log
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a
boot file
** Attachment added: boot
http://librarian.launchpad.net/7379952/boot
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
please forgot th first sent because i boot the computer with livecd and dmesg
command give a output for the livecd distribution .
i make a mount of the hard drive in order to retrieve dmesg log
thanks for help
** Attachment added: dmesg
http://librarian.launchpad.net/7379971/dmesg
--
Please find attached dmesg,txt, lsci-vnn.txt uname.txt
** Attachment added: logs.zip
http://librarian.launchpad.net/7380556/logs.zip
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
be of more help.
Keep up the great work.
Darren
- Original Message -
From: Brian Murray [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 5:07 PM
Subject: [Bug 105316] Re: Failure to boot
Thanks for taking the time to report this bug and helping to make Ubuntu
better
'dmesg dmesg.log' puts the output of the dmesg command into a file
called dmesg.log. That should be added to you bug report as an
attachment. The correct command for the second thing we need is 'sudo
lspci -vvnn' where it is a lower case 'L' not a '1'. Thanks.
--
Failure to boot
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately we can't fix it, because your description doesn't yet
have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's
Same problem aswell with feisty beta although the last part i haven't
got (about the cpu)
i'm not sure what logs you'd need but heres 2 that may help
** Attachment added: xorg log
http://librarian.launchpad.net/7336826/Xorg.0.log
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You
** Attachment added: bootstrap log
http://librarian.launchpad.net/7336828/bootstrap.log
--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I have similar experience. Installed Feisty beta. Upgraded. After that I
get the same messages as Darren. Except for the last bit. I do not get
Bug: Soft lockup detected on CPU#0. I get a login prompt an can log
onto the console. I think I might be able to provide you with logs. (I
will probably
20 matches
Mail list logo
