To be clear, I have since successfully upgraded but done so by:
0. (running apt-get update, dist-upgrade, etc to prepare)
1. deinstalling (via apt-get) gdm3
2. booting into recovery mode & initiating networking
3. running do-release-upgrade
4. restarting the system.
I don't think I can exactly 'r
Hi Christopher:
I won't be able to do this for another week. I hope that that timing
works for you.
Henry Baker
At 12:53 PM 2/27/2016, Christopher M. Penalver wrote:
>foobar, in order to allow additional upstream developers to examine the issue,
>at your earliest convenience, could
*** This bug is a duplicate of bug 1548903 ***
https://bugs.launchpad.net/bugs/1548903
Hi Christopher:
I submitted this bug yesterday, in case there was a race condition
between fixes to 4.2.0-30 and my previous bug report.
BTW, since multiple versions of 4.2.0-30 have gone out, what is
the
Henry Baker
At 11:54 AM 2/27/2016, Christopher M. Penalver wrote:
>foobar, thank you for reporting this and helping make Ubuntu better.
>
>Could you please provide the full computer model as noted on the sticker
>of the computer itself (not from the Bug Description)?
>
>** Changed
Public bug reported:
X11 crashes during booting on kernel 4.2.0-30 (the version dated Feb 26,
2016 -- version 36 ???)
This bug report is being submitted on 4.2.0-27 since I can't get
4.2.0-30 to run.
This is the *second* version of 4.2.0-30 that doesn't boot; the first
version was earlier in the
Public bug reported:
4.2.0-25 (this linux) works.
I upgraded to 4.2.0-30 today, and X11 won't start; get simple login:
prompt, but no X11.
I have to downgrade to 4.2.0-25 to get any work done.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu
Wooppeee!
At 11:40 AM 1/18/2016, Christopher M. Penalver wrote:
>foobar, to clarify, does the display glitches persist after the change
>of the display, or only as it is changing?
>
>** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>
>--
>You received th
se, tell me how to disable the GPU completely!
Thanks.
At 11:40 AM 1/18/2016, Christopher M. Penalver wrote:
>foobar, to clarify, does the display glitches persist after the change
>of the display, or only as it is changing?
>
>** Changed in: xorg (Ubuntu)
> Status: Ne
"HP Pavilion dv7-4272us entertainment PC" I think this gets printed out
somewhere -- perhaps in the BIOS of this laptop.
At 05:27 PM 10/27/2015, Christopher M. Penalver wrote:
>foobar, could you please provide the full computer model as noted on the
>sticker of the computer itse
rbara, CA
At 03:14 PM 10/25/2015, Christopher M. Penalver wrote:
>foobar, also, could you please run the following command from a terminal as it
>will automatically gather and attach updated debug information to this report:
>apport-collect -p xorg 1509135
>
>Please ensure y
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506869/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https:
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506860/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506862/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506876/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506855/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506857/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs
apport information
** Attachment added: "xserver.errors.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506875/+files/xserver.errors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506868/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506865/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506854/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506859/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506866/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506861/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506864/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506867/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506871/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506858/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506874/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506872/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506870/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506856/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Tags added: apport-collected compiz-0.9 ubuntu
** Description changed:
After upgrading from Ubuntu 15.04 to 15.10, the AMD discrete card keeps
coming on.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubuntu-release-upgrader-core 1:15.10.14
ProcVersion
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506863/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1509135/+attachment/4506873/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
After turning off radeon.dpm=1, the temperature at idle goes up about 2
degrees C.
However, if I then do
echo low > /sys/class/drm/card0/device/power_profile
echo low > /sys/class/drm/card1/device/power_profile
The temperature at idle goes down about 4 degrees C -- i.e., less than
when dpm=1.
T
GA-switcheroo
Jul 4 09:14:54 HP-ubuntu kernel: [ 392.808780] snd_hda_intel :02:00.1:
Cannot lock devices!
At 07:28 AM 7/4/2015, Christopher M. Penalver wrote:
>foobar, just to confirm, if you remove kernel parameters radeon.dpm=1
>radeon.audio=0 are there any visual glitches?
>
>**
mand" v
"low"), but this raises the operating temperature by only a
handful of degrees C.
At 07:28 AM 7/4/2015, Christopher M. Penalver wrote:
>foobar, just to confirm, if you remove kernel parameters radeon.dpm=1
>radeon.audio=0 are there any visual glitches?
>
>** Tag
7/3/2015, Christopher M. Penalver wrote:
>foobar, thank you for reporting this and helping make Ubuntu better.
>Could you please provide the full computer model as noted on the sticker
>of the computer itself (not from the Bug Description)?
>
>** Tags added: needs-full-computer
Public bug reported:
Setting radeon.dpm=1 keeps causing glitches every time the display
changes from the IGD to DIS and vice versa.
It may be related to the HDMI audio, which I tried to turn off using
radeon.audio=0.
Below are the lines from the kernel log having to do with snd_hda_intel
(which
Public bug reported:
I'm using radeon.dpm=0 and radeon.runpm=0 for reasons explained in a
previous bug report.
I'm able to turn the radeon discrete graphics off using
echo IGD > /sys/kernel/debug/vgaswitcheroo/switch
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
and my power consumption dro
Public bug reported:
This AMD 3-core + Radeon runs really hot, and I'm trying to maximize
battery life.
When I try radeon.dpm=1, I get display glitching every few seconds when
the dpm switches displays. I haven't found any way to force dpm to keep
the discrete display completely turned off, both
41 matches
Mail list logo
