*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Registry Administrators (registry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
I have been having this problem with a fresh install of both Ubuntu
8.04, 7.10, and Xubuntu 8.04 on a Dell Inspiron 700m. Currently, I'm
using Xubuntu 8.04 exclusively. There appears to be multiple triggers
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
Unfortunately, Gerry's workaround didn't work for me either, nor any of
the other fixes that have been posted. I find it bizarre that the
problem is being blamed on our hardware and/or BIOS. Even a casual
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
I'm not questioning why this hasn't been fixed, I'm questioning why this has
been marked a duplicate. In my experience marking something as a duplicate
means that you have a duplicate bug report in the same st
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
This won't shut down bug cropped up on Feisty in the middle of February
on the early builds just after a whole load of stuff from Debian got
dumped on Ubuntu, as far as I can see replacing good code with defec
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
Do I not understand the "duplicate" status. When I work on bugs a
duplicate is only applicable to the same stream. If you mark this as a
duplicate to a bug found in Hardy, will it still be fixed in Gutsy? If
s
*** This bug is a duplicate of bug 181892 ***
https://bugs.launchpad.net/bugs/181892
** This bug has been marked a duplicate of bug 181892
Hardy Alpha Shutdown Doesn't
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a mem
I now use Vista on my main machine pretty much soley because of the
wasted time this bug was causing me.
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
Leann, I just entered bug #181892 from Hardy Alpha daily build 20080109,
the latest Hardy I could find. Yes it hangs on shutdown.
By the way, CD Live, this version is a little jerky on youtube my
impression better than the original Alpha.
Jerry
--
Gutsy shutdown doesn't
https://bugs.launchpad.
Hi All,
The symptom of this particular bug, failure to power off when shutting
down, is specific to the hardware and BIOS used. So while many of you
may have the same symptom they really should be different bugs. It would
be helpful if everyone were to test with a Hardy Alpha build,
http://www.ubu
Unfortunately, none of the above fixes work on my machine (Asus A7N8X
motherboard with Nvidia chipset)). Sometimes a change to the
/boot/grub/menu.lst file will result in a proper shutdown but only once.
After the next boot shutdown results in a reboot. The same thing
happens if I use the termina
Jerry's first mod works for me so far:
Do sudo gedit /etc/modules. Add the following line, then save:
apm power_off=1
But the second mod causes a bios error after grub on loading (not the
end of the world) but then I cannot see my laptop battery charging.
do sudo gedit /boot/grub/menu.lst (where
+1 to this causing/fixing the issue
Shutdown problem occurred when I disabled Power Management in
System--->Preferences--->Sessions
Linux xxx 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
GNU/Linux
Running an old Dell Dimension 3000
--
Gutsy shutdown doesn't
https://bugs.launchpad
I've had this issue before with the 2.4 kernel. I fixed it on my 2.6
kernel by adding the following to the end of the to the grub menu.lst
kernel line:
acpi=force apm=off
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member
uname -a Linux cheeseburger 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12
GMT 2007 i686 GNU/Linux
Shutdown problem occurred when I disabled Power Management in
System--->Preferences--->Sessions
Screen froze, no mouse/menus unresponsive
keyboard shortcut: Ctrl+Alt+Backspace used to shutdown from lo
last file attached
** Attachment added: "dmidecode.log"
http://launchpadlibrarian.net/10569817/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
next file attached
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10569813/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I've solved the problem as jerrylamos suggests, but only modifying the file
/etc/modules.
I've no touched the menu.lst and the laptop shuts down properly.
these are my files:
a name:
Linux alberto-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
dmesg attached
** Att
I faced the same problem with my old IBM Thinkpad 380Z after installing
Ubuntu 7.10 onto it -- the laptop did not shutdown. However, with Ubuntu
6.06.10 it used to. I added acpi=off and apm=on to the kernel booting
line in /boot/grub/menu.lst, and also apm power_off=1 to /etc/modules.
And I confirm
After some tests with a machine that wouldn't shut down since upgraded
to Gutsy and was shutting down perfectly in Feisty, I could trace the
problem down to the "Network Manager".
This machine uses a Wi-Fi network connection using ndiswrapper + Network
Manager, and hangs shutting down in Gutsy.
I
I switched to the i810 driver and loaded the 915resolution package to
display resolution too 1280x800. Now shutdown/restart/hibernate issue is
completely got resolved for my laptop 700m.
Below are step to switch back to i810 drivers.
Issue following command either from the command line or by botti
Linux does a scheduled fsck (file system check) after a certain number
of boots. It takes a while and there should be a progress bar. I've
seen 27, 37, you name it. Any time it finds what it thinks is an error
it will give directions and ask permission to fix something. Any time
I've had an fsc
Applied changes as per instruction.
Now system sometime shutdowns without issue. sometime not.
Unpredictiable.
Issue is not completly resolved.
After every 37 times boot.
System gives error /dev/sda3 is mounted 37 times.
I got this error message 3 times in week.
It seems to be during shutdown di
This works for me as on my post dated 2007-08-23. Take caution on changing
system files:
Do sudo gedit /etc/modules. Add the following line, then save:
apm power_off=1
do sudo gedit /boot/grub/menu.lst (where the l is a lower case L). Find the
line that start with "kernel" and add this onto the
I am also experiencing same issue on my Dell Inspiron 700m laptop.
I have installed fresh ubuntu 7.10.
I have tried all below specified options :
1) adding "acpi=force"
2) removing "splash"
3) removing "ro quiet splash"
Nothing worked for me.
Only shutdown works from command prompt with follo
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10277363/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
I too have this bug. It is really quite irritating!
Uname -a: Linux steve-desktop 2.6.22-14-generic #1 SMP Sun Oct 14
23:05:12 GMT 2007 i686 GNU/Linux
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/10277361/dmesg.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bu
** Attachment added: "dmidecode output"
http://launchpadlibrarian.net/10277362/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
Ok - this bug is clearly conscious, intelligent and mischievous. It
waited until I had made that last post, then came back. acpi=force did
not work for me, unfortunately.
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member o
Ok, I tried the acpi=force workaround and it's worked for 3 shutdowns.
Unfortunately, since my problem only happened about 50% of the time, I
can't say for certain if it's fixed the problem, but it looks good so
far.
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received th
Well, i think i've fixed it :)
ThomThom, me too, my bios doesn't identify itself as a 2004 bios and the
kernel avoids loading acpi.
I added this option to force it:
acpi=force
at the end of the kernel booting line at /boot/grub/menu.lst:
kernel/boot/vmlinuz-2.6.22-14-generic root=... ro quiet
lscpi-vvnn attached.
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10230512/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Same here. Didn't shutdown on Feisty or Gutsy.
When booting i get the message:
DMI not present or invalid
ACPI: No DMI bios year, acpi=force is required to enable ACPI
My bios is from 2004.
uname -a
Linux dunduntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
sudo dmide
Not sure this is the same bug but :
Recent desktop system (AMD Sempron, NVidia chipset) which was shutting
down perfectly with Feisty now sporadically hangs on shutdown after
upgrade to Gutsy (kernel 2.6.22-14-generic).
Not easy for me to be very specific, the machine is 400 miles away, it's
a f
Only needed to add apm power_off=1 to /etc/modules after installing
ubuntu/xubuntu gutsy on a couple of old Win98 desktops.
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
Turns out that ACPI was my problem. I force enabled it and it now shuts
down correctly. I suppose it's the BIOSs fault for not identifying it's
year? It's from 2005.
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubu
I'm having this issue on my VIA EPIA SP 13000.
When I disable the boot splash screen I'm faced with this:
---
System is shutting down, please wait...
---
NetworkManager: mn_signal_handler(): caught signal 15,
shutting down normally.
NetworkManager: Caught termination signal
NetworkManager:
** Attachment added: "lspci-vvnn"
http://launchpadlibrarian.net/10194296/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Thanks Jerry, worked like a charm :)
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
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
https://lists.ubuntu.co
** Attachment added: "dmidecode.log"
http://launchpadlibrarian.net/10171451/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10171449/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
Same problem here on a Compaq Presario 6000.
uname -a:
Linux marpau-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10171448/dmesg.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/11930
I am experiencing this issue on an Inspiron 700m laptop. It happens
about 50% of the time. I installed Gutsy fresh, not an upgrade.
[EMAIL PROTECTED]:~$ uname -a
Linux Argon 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
dmesg.log is attached.
** Attachment added: "dmesg.
Here is the next attachment
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10170309/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
And the last attachment
** Attachment added: "dmidecode.log"
http://launchpadlibrarian.net/10170312/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Sorry the command at the top of the halt script is rmmod snd-hda-intel
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
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.
I don't know if this is related but I had a shutdown issue with feisty
and gutsy, it was module snd-hda-intel that would hang. (black screen no
info) So what I did was went to the script for the actual halt command
in /etc/init.d opend the halt script and at the top of it added rmmod
snd-hda-int s
Released Gutsy Ubuntu 7.10 still hangs on shutdown on this computer. Here's
the old workaround from Feisty from 6 months ago:
Do sudo gedit /etc/modules. Add the following line, then save:
apm power_off=1
do sudo gedit /boot/grub/menu.lst (where the l is a lower case L). Find the
line that start
Linux megatron 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
i686 GNU/Linux
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10051530/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are
** Attachment added: "dmidecode.log"
http://launchpadlibrarian.net/10051528/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Same problem here. Here's the requested attachments.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10051522/dmesg.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Same problem here. Beta Xubuntu Alternate and Desktop CD Hang on
shutdown. Never had this problem before. Feisty runs fine.
AMD 4200 X2
nforce4 A8N SLI Premium.
2 GB ram.
ASUS ATI X1600Pro
WD 74 GB raptor + WD 250 GB caviar.
XP + Ubuntu Gutsy
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/
I can confirm a similar scenario with Gutsy. Clicking the shutdown just
hangs the system with the desktop image. Virtual consoles cannot be
opened and a hard reset is required.
AMD 2400
nForce motherboard
1GB Ram
nVidia FX5500
IDE Main drive (XP,Ubuntu)
SATA Raid1 storage
--
Gutsy shutdown does
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Medium
Assignee: Brian Murray => Ubuntu Kernel ACPI Team
Status: Invalid => Triaged
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of U
The following patch worked for Tribe 5. Strange how Edgy and Dapper and
Puppy ... shutdown O.K. but Feisty and Gutsy Tribe 5 don't. Maybe
there's a clue for you in what the fix may do.
Cheers, Jerry
"Shutdown" doesn't
This system powers off with Edgy, Dapper, Knoppix, ... but not Feisty. If I
Here's output from sudo dmidecode > dmidecode.log
** Attachment added: "Attached is dmidecode > dmidecode.log"
http://launchpadlibrarian.net/8957476/dmidecode.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ub
Attached is lspci-vvnn.log
** Attachment added: "Here's sudo lspci -vvnn > lspci-vvnn.log"
http://launchpadlibrarian.net/8957472/lspci-vvnn.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here's uname -a:
Linux linuxGutsy 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007
i686 GNU/Linux
Attached is dmesg.log
** Attachment added: "dmesg.log as requested"
http://launchpadlibrarian.net/8957461/dmesg.log
--
Gutsy shutdown doesn't
https://bugs.launchpad.net/bugs/119308
You rec
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
feel free to submit bug reports in the future.
** Changed in: linux-source-2.6.22 (Ub
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 as attachments the following additional information, if you have
not already done so (please pay attention
60 matches
Mail list logo
