If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
After a fresh install of Fiesty, when logging out the X-server hangs and no further logins are possible. <Ctrl><Alt><Backspace> can not kill X, so I must reboot by using the "elephant" sequence.
Solutions ? - Bug ?
Edit your /boot/grub/menu.lst as sudo (alt+F2-> kdesu kate) and add this at the end of your kernal line:
acpi=force so it looks something like this:
kernel /boot/vmlinuz-2.6.20-15-generic root=/dev/sda11 ro splash acpi=force
that worked for me.
Thanks for all the help, folks ! - After editing menu.lst , removing the quiet and splash and setting vga=791 the problem went away. Can't say why, though....
When I select "log out" from the kmenu inside Kubuntu 7.04, It starts logging out and the screen goes black.. and then a cursor appears in the top left corner of the black screen and then nothing else happens. I have to hit control / alt / del to get the system to restart and bring me back to the log in screen, which is where I wanted it to take me to start with.
I had the same problem -- This may or may not be the fix for you but here is what worked for me.
after looking at my logs i noticed a bug in ndiswrapper. It reloads itself. Thus an infinite loop occurs. Looking like it is stalled.
solution
in your favorite editor - mine is mcedit
sudo mcedit /etc/init.d/halt
at the top add
rmmod ndiswrapper
that's it. Might I add this wouldn't be needed for ME if Atheros worked in the new kubuntu. But that's another issue, yours is ndiswrapper.
Hi, I also have the same problem...when I want to reboot or shutdown, the screen turns off but pc remains on, like freezed. I tried acpi=force but it's worse...on boot appears black screen with cursor.
I tried the ndiswrapper trick but nothing changes
At this point I think it's a kernel bug...I also had a problem on boot till yesterday , and it was solved by the recent kernel update.
What do you think?
ACPI is a new version of APM (Advanced Power Management). It takes care of your power management, batterystatus, and controles your system.
More and more motherbords are using ACPI. If you have a motherboard that supports only APM, you could encounter a few problem such as:
* A PC that won't shut down (power off)
* A PC that can't leave a certain powersave mode (suspend, sleep, ....)
First check the kernel:
Check if these things are present:
# ACPI Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_HT_ONLY is not set
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_TOSHIBA=m
This can be found in the file: /usr/src/linux/.config, or you can find it through the KDE-control system.
Through the KDE-control system, you can view the Linux kernel, adapt the configuration and save it.
Anyway, booting with the new (kernel) version, you should be able to see the section /proc/sys/acpi.
Next you'll need a good ACPI deamon. Download and install acpid-xxxxxx.tar.gz
APM and ACPI can't stand eachother. So you'll have to make a choice. If APM is loaded at first, ACPI can't be activated.
You'll have to let the bootloader (LILO, GRUB) know you don't want APM, but ACPI (Append: apm=off acpi=on)
If you see this message:
*ACPI: Vendor "VIA694" System "AWRDACPI" Revision 0x0 has a known ACPI BIOS problem.
*ACPI: Reason: Bogus table. This is a non-recoverable error
in the file (/var/log/dmesg), then you have a bad BIOS. The only solution is upgrading (flashing) your BIOS. Check the website of the BIOS supplier.
Hi, thanks for answering. I specify that I never had this problem, anything was fine on hoary, dapper etc. This happens only in feisty.
Originally posted by v_override
First check the kernel:
Check if these things are present:
# ACPI Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_HT_ONLY is not set
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_TOSHIBA=m
This is my acpi support section:
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_CUSTOM_DSDT_INITRD=y
CONFIG_ACPI_BLACKLIST_YEAR=2001
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
So I think I don't have to install anything, right?
To tell you the truth, I'm still new on the Kubuntu thing.
I've only been using Feisty for a couple of weeks and prior to that, Dapper for a couple of days. So I'm still checking things out in Linux.
Now that I'm running Feista, I have the shutdown problem as well.
(My PC just says: "System Halted" in the end, I have to shut it down manually.)
I didn't have that problem on Dapper though. My PC was shutting down nicely.
So, in short, to be honest, I don't know if you have to install something else or not.
I can only tell you this.
In Dapper the boot process went smoothly.
Now, whenever I start up Feista, I get this message on my screen:
[0.000000] ACPI: BIOS age (1997) fails cutoff (2000), acpi=force is required to enable ACPI.
I checked the System Log and it continues like this.....
Really? That's the first person that's got that to solve their problem (that I know of)...
The rest of us have more obscure problems, I guess.
Sometimes, I wish they wouldn't fix the known problems. If they do, it means the harder (or more obscure) ones are left to us.
Just installed Kubuntu today, having this logout problem too. Actually had a handful of logout issues, but the black-screen-blinking-cursor one takes the cake.
Searching this forum, it looks like a lot of folks are having logout-related issues. What is is the definitive solution for this?
Comment