2016 at 9:15 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Aaron Sosnick, in order to eliminate confusion, it will help immensely if
> you filed a new report (not reopen this one) with Ubuntu (not Mint) via a
> terminal:
> ubuntu-bug linux
>
> Please feel free to
This problem happens with or without Mint packages.
It is an Ubuntu problem and you are not nice for suggesting otherwise.
Please mark "won't fix" not invalid if that's your attitude.
I'll give some more recent Ubuntu versions a chance when I can and reopen
if it hasn't been fixed.
--
You rece
Umm.. I did as you asked. Is there anything else I should try or any
additional information I can provide? Do we have any idea why the newer
kernels don't work at all with the graphics card? Should I assume from
silence that this isn't going to be a priority for anyone to work on?
--
You received
Since virtualbox seemed to the source of at least some of the errors
coming from installing the 3.16rc2 kernel I uninstalled virtualbox and
reinstalled the 3.16rc2 kernel. Output from sudo dpkg -i is attached.
The install error messages are gone, but the behavior is is the same,
graphics card and w
Oh. Am I not supposed to mark as confirmed since I first reported?
Apologies if I should not have marked. At any rate, unless I am making a
mistake in installing, newer kernels make things worse not better. I'm
happy to provide additional diagnostics or information if someone can be
so kind as to l
Attached is the output from
$ sudo dpkg -i linux-
headers-3.16.0-031600rc2_3.16.0-031600rc2.201406220135_all.deb linux-
headers-3.16.0-031600rc2-generic_3.16.0-031600rc2.201406220135_amd64.deb
linux-
image-3.16.0-031600rc2-generic_3.16.0-031600rc2.201406220135_amd64.deb
The output contains errors
Note that this bug was reported back in 2011
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894308 so it is not new.
The graphics card is not recognized at all and the system boots in an
innapropriate, unchangeable resolution if
nomodeset is added to the boot options
** Tags added: 5100 ace
Public bug reported:
On this old laptop, Ubunutu 14.04 works fine on boot (after making sure
fgrlx drivers are removed).
However after a Suspend/Resume the screen flickers/tears so badly as to make
the system unusable.
Note that the problem does not occur with Hibernate/Resume. In fact if I can
The screen is fine after hibernate. In fact if I leave a window open
with $ sudo pm_hibernate ready to go, I can bring the screen back by
hitting enter to hibernate after a suspend/resume. However the wifi
disconnects after after hibernate/suspend. Will file/revive a second bug
report for that.
--
Also I have tried booting with nomodeset, but then the proper driver
isn't run at all, the screen resolution is wrong, and there's no way to
change it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I also have an Acer Aspire 5100. I just installed Ubuntu 14.04 and I
have this exact problem. The machine boots fine, but after a suspend the
screen tears/flickers so badly that the machine is unusable. Note that
the problem does not occur with hibernate.
** Changed in: linux (Ubuntu)
Statu
11 matches
Mail list logo
