I've updated the title and description based on recent findings.
Hybrid graphics switching support is still fairly embryonic upstream and
I don't feel it is yet stable or reliable enough yet for us to support
in Ubuntu, so I am setting the importance of the X task here to
Wishlist.
However, even
marking the bug as confirmed
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and
If I add
radeon.modeset=0
in the boot line when starting, the crash does not happen and the system
continues with is using integrated Intel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Sorry, I got sidetracked while getting a set of logs. However, some (yet
slightly vague) findings may be useful - even if debugging gets maybe
even harder:
Firstly: the computer (BIOS or whatever) behaves differently when
external power is connected or only battery used, and secondly: it
behaves
@Bryce: Yes, booting with only discrete or integrated enabled does solve
the problem for me as well.
@Dweia: I patched the CMOS for my 3820TG and unlocked the Intel menu.
Now I can choose to only have the IGD activated and PEG (radeon)
completely shut off drawing zero power. Same thing as going
Btw, should we work on the bug on here on launchpad or keep the
discussion on freedesktop working directly with the AMD devs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD
I have taken logs from a set of ubuntu kernels starting up using the
requested kernel boot argument drm.debug=0x0e:
2.6.38-7 --- fb0: radeondrmfb frame buffer device
2.6.38-8 --- fb0: inteldrmfb frame buffer device
2.6.39-rc1-- kernel oops (pointing to evergreen something), not caught in the
afoglia - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=36003 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
Johan, I attached your logs to the upstream bug report. Generally
Upstream would like to see if setting the video to the radeon/descrete
setting in the BIOS configuration makes it function properly.
If so, this may be a known issue in the new vga_switcheroo
functionality, ala bug https://bugzilla.kernel.org/show_bug.cgi?id=30052
** Bug watch added: Linux
Chris Halse Rogers wrote in #22: This does look a lot like some bad
interaction between i915/radeon
I agree - I did some more testing and placed an entry for the radeon-
module into /etc/initramfs-tools/modules, and voilá - no crash! (after
booting into X I can't get back to the text-console, but
Bryce Harrington wrote in #25 Upstream would like to see if setting the
video to the radeon/descrete setting in the BIOS configuration makes it
function properly.
Answer: Yes it does. I tried that a while ago already, but can't (don't
want to) use that for regular running, because the radeon-card
** Changed in: xserver-xorg-driver-ati
Status: Unknown = Confirmed
** Changed in: xserver-xorg-driver-ati
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
This does look a lot like some bad interaction between
i915/radeon(/vesafb?). Although we don't seem to have a full dmesg of a
-7 kernel it seems like it's not vesafb-based.
It would be useful to have logs - both of good and bad boots - with the
“drm.debug=0x0e” kernel argument added to the boot
Unfortunately I discovered yesterday, that I lied. Wehn used without
battery (this is a Aspire 3820TG laptop) and connected power-cord, the
crash occurs also with kernel 2.6.36-1. Probably the BIOS does something
to/with the graphics-cards, when external power is connected. All the
previous tests
It's starting to sound like this is due to confusion (maybe a
regression) in the plumbing layer between X and the kernel, such as
module-init-tools or one of the related packages.
I think either apw or cjwatson need to look into this issue. apw's on
vacation though.
--
You received this bug
Bryce Harrington wrote on 2011-03-04:[...] That suggests a regression in
the kernel between 2.6.38-3 and -4
The error must have occured a lot earlier. I tried a bunch of different
kernels, each with the (at the moment) most recent version (highest
number after the dash):
2.6.35-25 - works
Does anybody works on this bug ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Driver crash during recovery boot and in
normal boot (Regression from
I have a theory... Maybe there is a race condition between the intel and
ati driver involved here? My notebook starts up in two seemingly random
configurations, or three including the radeon crash:
1. X server is on VT8 - unable to unload radeon module because it is in
use (by some framebuffer I
When I have booted into an evironment where both X server and
framebuffer uses intel, sometimes when I try to unload the radeon module
it crashes like this:
[ 346.860598] radeon :02:00.0: 88014b362000 unpin not necessary
[ 346.860619] BUG: unable to handle kernel paging request at
I confirm that the bug is still there. I install last update this
morning (I saw xserver-xorg-video-ati, -radeon... update so I was
expecting the bug to be solved).
When I restart, I need to reboot more than 5 time before I get a
desktop. And now, when the boot crash, I don't get any shell,
Note : Here is the result of
lspci -v | grep -A 12 VGA :
guillaume@guillaume-HP-Notebook:~$ lspci -v | grep -A 12 VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard
kolio, not sure what you're talking about. The Radeon HD 5650 came on
the market on Jan 7, 2010, so it did not exist 2 or 3 years ago.
Whatever posts you're looking at are unrelated to this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
afoglia, just to confirm - you still seeing this crash with the current
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Driver crash during recovery
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Driver crash during recovery
Yes and no. I did six normal boots with 2.6.38-7.35, then realized
there was an update, and booted that both normally and in recovery and
here's what I saw
2.6.38-7.36 normal, 6 boots, 5 reached gdm login screen, 1 gdm started but hung
before login window appeared (only one of the 5 successful
** Tags added: crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Driver crash during recovery boot and in
normal boot (Regression from 2.6.38-3 to -4)
Hi guys,
i have the same problem.I like very much this OS-Ubuntu, but why such a good
system do not resolve this problem such a long time?I see a posts from the last
2 or 3 yaers.It's strange for me.I don't want to experiment with my PC.I tried
but it's always a crash,black screen,red
Even though this seems to be pinpointed to the kernel, I'll leave the X
task open for now so we can keep track of the bug's progress from the X
end.
** Summary changed:
- [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot
+ [Radeon HD 5650 and 5470] Driver crash
28 matches
Mail list logo