Since Ubuntu 19.04, I can not use Ubuntu on my VMware virtual machines on my
MacBook Pro Retina (200% scaling). The desktop is white. This still occurs
under Ubuntu 19.10 (even with a clean install).
I hope this problem will be resolved quickly. I want to migrate to a newer
version than my curre
I've found what causes this, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089/comments/43...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776803
Title:
Natty does not shut down clean
Glad to hear this is working for everyone else! Personally I can't
think of a time that my system has locked hard and this watchdog would
have actually come in handy, most times I'd have hit the reset button
myself before waiting one minute for it to kick in. I guess it would be
useful for a prod
@Alex
Okay, yes I agree that the watchdog/timer should be reset on reboot;
it seems silly that it would remain enabled after the BIOS initializes.
A config option would be fine for clean reboots, but it persists even
after a hardware reset once it's been set up, so I think the best option
would
Oh, is there a BIOS setting for the watchdog? I don't remember seeing
one.
In my case (Archlinux) this module comes with the kernel:
---
pacman -Qo ./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz
./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz is owned by linux
3.0.1-1
---
I j
I've found the cause of this.
I looked at my loaded modules for anything nvidia-specific and the first
hit was nv_tco.
Looked at the source for this module (http://lxr.free-
electrons.com/source/drivers/watchdog/nv_tco.c) and it seems to handle
some hardware watchdog timer for Nvidia chipsets (as
PS, my kernel is 2.6.39-ARCH and it's 64 bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791089
Title:
crash after rebooting or shutting down from Ubuntu 11.04
To manage notifications about this
I have the same problem with the same board, but I run ArchLinux. Since
it seems to also affect Ubuntu and Fedora
(http://forums.fedoraforum.org/showthread.php?p=1502068#post1502068), I
suspect a kernel or module issue.
I've thought I've had a funny hardware issue for months and tried
different C