Hello? Any corrections for that revisions range you wanted me to
bisect?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
Status in
This last weird effect was transient; it went away after a reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no longer works
Status in linux
It just got a bit weirder.
I've got my custom xrandr-defined 2560×1440 resolution going. But for
purposes like window placement, resizing windows, and maximising
windows, the UI seems to think it's 1920×1080 or thereabouts.
So if I open a whole bunch of editor windows from the shell, they all
This is getting awkward. The upper-bound version you wanted me to
bisect is also missing from the Ubuntu/upstream version mapping. So
even if I want to bisect upstream versions I still have the same
problem. Are you sure you gave me the correct versions for bisection?
Maybe you meant
Thanks. Could you also update that section? It says that it applies in
two situations, but it never actually lists those two situations. I
*think* (but without already knowing of course I can't be sure) that
it's meant to refer to a list of three headings, “BISECTING: A MERGE
BASE MUST BE
Thanks for following up. I read most of that document, but it's
difficult in places. My understanding is that what you're asking me to
do is what's described under “Commit bisecting Ubuntu kernel versions,”
correct? That's the only part of the main page (excluding the FAQ
below) that seems to
If you don't have time to read what I wrote, or if something I wrote is
not clear, just say so and I will understand. Let's not get caught in
the endless Confirmed/Incomplete circle.
I'll summarise what I said before, to make it easier to digest:
You asked me to bisect between 3.13.0.18.38 and
Read back and it will become clear.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution
Once again: with the given instructions I can't bisect kernel commits
any further. Is there another way to obtain the kernel source versions
we need?
Marking as Confirmed again until then, to avoid this bug timing out.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You
3.13.0-19.40 also works OK! So it broke sometime after that.
I'm now trying to find 3.13.0-20.24 in one of the kernel branches from
before Vivid. It's not in the Trusty branch. I can't get the Quantal,
Raring, or Saucy ones, presumably because those releases are no longer
supported.
Using the ubuntu-vivid kernel branch, 3.13.0-18.38 works OK.
That branch has no tag Ubuntu-3.13.0.20.24 or Ubuntu-3.13.0-20.24. The
closest tags I see are Ubuntu-3.13.0-19.40 and Ubuntu-3.13.0-20.41.
I'll try 3.13.0-19.40 next.
--
You received this bug notification because you are a member of
The Precise kernel repository finished downloading, but it doesn't have
3.13.0-20.24. It has 3.13.0-19.39 and 3.13.0-20.41, nothing inbetween.
Pinning my hopes on the Utopic branch...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Nope, the Utopic kernel branch only has 3.13.0-19.40 and 3.13.0-20.41,
nothing inbetween.
So, all I know is up to and including 3.13.0-19.40 it still works OK.
The problem must have been introduced later than that.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You
Oh, one other thing: with the older kernels I can play AssaultCube
again! I couldn't really do that with the current Vivid kernels because
the frame rate was too low. Reported frame rate would be around 60 fps,
but it looks more like 10 fps. With these old kernels it plays
smoothly.
--
You
No Tried 4.1-rc7. No change.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest
resolution offered in the System Settings is 1920×1200.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
After another reboot this effect seems to have gone away. So I still
don't have my native resolution available by default, but at least I can
get it back by defining it with xrandr.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hurray, the problem just got a little worse!
After the upgrade to kernel 3.19.0-14.14, when I define my monitor's
native resolution using xrandr, I get the right *resolution* but still
not the right number of *pixels*. So I'm getting (as far as I can see)
one logical pixel per physical pixel on
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It
was the upgrade to 3.19.0-15.15.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution
Well, I did some bisecting but the results are disappointing. Actually
I ended up trisecting. On Saucy, kernel...
3.11.0-12 was OK. Recognised my full native resolution and enabled it
by default. Wonderful.
3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted
in some
Okay, I got a seemingly successful install of the last Saucy kernel.
But it's not working very well: I get a super-low-res login screen, and
the system doesn't respond to keyboard or mouse. (It does notice the
power button, so it's not frozen). This happens both with the default
boot on that
Trying 13.11.0-17. There was a problem while installing linux-headers
though... fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime-
dkms kernel module failed to build. Somewhere along the way it said:
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic
I could temporarily swap out the hard drive and install Saucy on the
spare. More after the weekend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1300557
Title:
Screen resolution no
The latest upstream version I found there was v4.0-rc4-vivid. It boots,
but it doesn't fix the problem.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
24 matches
Mail list logo