"Perhaps the suspend script can check for the presence of the fglrx
module and refuse to suspend in that case... (with a comment documenting
this)"
That's a pretty drastic solution to the problem, considering that it's
caused by premature commitment to a brand new kernel feature (the SLUB
allocato
"The kernel freeze is approaching. The only suggestion from the devs is
to blacklist the fglrx module. I.e. add a `/etc/modprobe.d/blacklist-
fglrx' with the content `blacklist fglrx' and reboot. This will
deactivate 3D acceleration" ...
Not an optimal solution if a) you need 3D acceleration (game
Philipp Kern wrote:
> The response would indeed be different if the source code had been
> available.
*snip* [it's hard debugging a binary blob]
Agreed. No argument there. The situation totally sucks.
> Complain to ATI please. It seems that they did not even respond to the
> Ubuntu Kernel devs,
Nice writeup - thanks.
Yes, path a) seems to be the current stance. I'll be more cynical than
Charl and assert that this is probably deliberate, in part to punish
ATI, in part to make a statement about closed source drivers in general
and in part to punish users that didn't choose 100% FLOSS comp
It's not just z61m - I think this bug report just self-selected for z61m
users. Other systems seem to be experiencing the same problem, so I
think this is a more general problem. See:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/126214
ATI + fglrx + SLAB + x.org seems to
This definitely seems to be related to/a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/121653
I'm experiencing the same problem on a z61m with an ATI x1400 (kernel
2.6.22, fglrx 8.37.6, amd64), and custom compiling a SLAB kernel
restores suspend/resume. A workar
At the risk of being redundant, I'll confirm that installing a custom
compiled SLAB-enabled kernel and restricted modules restores
suspend/resume on my machine.
(Hmm. Seem to have gotten SLAB/SLUB confused in my last post. Sorry -
distracted by other stuff going on around me).
--
[gutsy] Suspe
Superficially, this smells like a duplicate of the following:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126214
The symptoms described are similar to what I and other have experienced,
anyhow.
If th
Ditto for z61m.
--
hdaps do not support Z60t
https://bugs.launchpad.net/bugs/45014
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
I can confirm the same behavior on my z61m (Intel Core 2 Duo/ATI
X1400/latest Gutsy fglrx driver/2.6.22-12 kernel/fresh install of tribe
5 + updates, otherwise stock): initiating suspend results in a black
screen, a blinking cursor in the corner and a blinking half moon LED.
This happens during en
I just ran into this on my KDE Neon system when I noticed this morning
that a full upgrade of the neon packages was running that I hadn't
triggered myself.
>From what I can tell, adding "${distro_id}:${distro_codename}" to
/etc/apt/apt.conf.d/50unattended-upgrades has the effect of enabling
unatte
Zygmunt, that's unfortunate to hear if what you are describing is a
fundamental design principle of the snap ecosystem.
While I wouldn't advocate that a user customize their home environment
in a way that arbitrarily goes against convention and standards,
locations should at least be configurable
I encountered this bug after installing linux-generic-hwe-16.04-edge on
Ubuntu 16.04 LTS.
Installing the deb suggested by vgerris in comment #14 fixed the
problem. The bcmwl kernel module built successfully for both the
16.04.1 kernel (kernel-4.4.0-53-generic-x86_64) and the HWE kernel
(linux-gen
13 matches
Mail list logo
