Patch has been applied and uploaded for Oneiric as well. Marking the
actively developed linux task from Fix Committed to Fix Released.
Thanks.
ubuntu-oneiric$ git describe --contains 97ea530f6fac1f9632b0c4792a2a56411454adbe
v2.6.39-rc2~8^2~6
** Changed in: linux (Ubuntu)
Status: Fix
For Natty, this should be fixed now with 2.6.38-10.46.
Please reopen the Natty task if you still experience this issue.
** Changed in: linux (Ubuntu Natty)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Would anyone be able to verify that this fix will also work for the
issues reported at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/763909 ?
Thanks
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Changed in: xserver-xorg-driver-ati
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot
Not exactly a great surprise but I would like to note that indeed, using
that PPA fixes my problem and works fine. Thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
The patches for this bug are included in 2.6.38.3, but unfortunately
will not make it into the initial release kernel. You can load 2.6.38.3
from https://launchpad.net/~kernel-ppa/+archive/pre-proposed.
** Changed in: linux (Ubuntu Natty)
Status: Triaged = Fix Committed
** Changed in:
Closing the userspace driver task, as this needs to be fixed on the
kernel side.
Regarding the milestone, I thought the kernel was now frozen for natty?
(Not that I would object to getting this fixed prior to release, as this
will presumably also affect the live system, and thus block
And even if it does not block the installation for some reason, the
installed system would not boot because of freezing on boot with KMS
enabled. Though I only tried this with maverick-natty upgrade, but I
guess it does not count at all, if it's an upgraded system, live system,
etc, if it's kernel
Flip-flopped the milestone as it looks like this is queued to enter the
kernel prior to release, so it should remain for the natty milestone.
Apologies for any confusion.
~JFo
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** 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-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
[Original upstream bug was
https://bugs.freedesktop.org/show_bug.cgi?id=36007 and has the bisection
search information.]
** Changed in: xserver-xorg-driver-ati
Importance: High = Unknown
** Changed in: xserver-xorg-driver-ati
Status: Invalid = Unknown
** Changed in:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=97ea530f6fac1f9632b0c4792a2a56411454adbe
Upstream kernel patch to fix this issue.
JFo, please add to the kernel team's queue.
** Attachment added: git.kernel.org.txt
Looks like you did some solid work bisecting the issue down and
identifying the patch that caused the regression. Since it points to a
kernel patch, the kernel team should take it from here.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided = High
** Changed in:
** Changed in: xserver-xorg-driver-ati
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot without
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot without disabling KMS
I have this on our list now, thanks Bryce. Andy has said he will review
it tomorrow. It should make it to us through stable updates, but I have
asked for a review ahead of that to be sure it will make it in time.
~JFo
** Changed in: linux (Ubuntu)
Assignee: Jeremy Foshee (jeremyfoshee) =
** Also affects: linux (Ubuntu Natty)
Importance: High
Status: Triaged
** Also affects: xserver-xorg-video-ati (Ubuntu Natty)
Importance: High
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
It seems the bug is identified also a short patch (at fdo bugtracker)
which cures the problem. Today I will try to apply that patch to the
ubuntu's kernel source tree to see that it really fixes the freeze.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
According to my tests, the suggested commit really fixes the problem, so
I would suggest to include that patch within natty's kernel too:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=patch;h=97ea530f6fac1f9632b0c4792a2a56411454adbe
--
You received this bug notification
Bisect process is - finally - done, so I have the first bad commit from
Linus' GIT between 2.6.37 and 2.6.38 which seems to introduce the
problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
I have started to try different versions of vanilla kernels please take
a look at freedesktop.org bugtracker
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
I've tried what Alex told on freedesktop's bugtracker (please take a
look there) so it really seems it's nothing about X itself, just loading
the module without X involved the freeze happens.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
i tried too and for me it works just for 50%, i have no black screen
but no 3D ( gnome-shell start in classic mode) and still no sound
card ( i have to modprobe manually ) . System is usable but it goes
slower after some hours ...
--
You received this bug notification because you are a member
Hi, thanks for the information, I've just added myself to the cc list on
the freedesktop bug tracker. I will investigate, sorry for the delay,
just I had no access to my notebook till now. I will try some things
today.
--
You received this bug notification because you are a member of Ubuntu-X,
Maybe I've missed something: I've tried to blacklist radeon module, so
I've created /etc/modprobe.d/blacklist-radeon.conf with blacklist
radeon on it, then I did depmod -a then dpkg-reconfigure linux-
image-`uname -r` (I used the freshest natty kernel booted with
radeon.modeset=0 before to allow
MTRR settings:
reg00: base=0x0fffe ( 4095MB), size= 128KB, count=1: write-protect
reg01: base=0x0 (0MB), size= 2048MB, count=1: write-back
reg02: base=0x08000 ( 2048MB), size= 1024MB, count=1: write-back
reg03: base=0x0bff0 ( 3071MB), size=1MB, count=1: uncachable
By the way I've tried radeon.blacklist=yes kernel parameter as it was
suggested according to some google'd resources. Then radeon did not load
indeed, and system booted (checked with lsmod | grep radeon, no result).
modprobe'ing radeon did not work then (illegal parameter about that
I've forgot to mention: I've removed the remained virtualbox stuffs
totally, also dkms, etc. Still, there is no change about the issue. I've
also tried to limit the available memory for the kernel with mem=512M
kernel parameter. I've also tried nopat I've found in some forum, but
still the same
I've also tried some odd thing: using mem=512M nopat
radeon.blacklist=yes text extra kernel parameters, for sure, I got text
console well then (even without mem/nopat it works). Then I removed MTRR
entries one by one (echo disable=X | /proc/mtrr, X=0 ...). System
went slow like hell, never seen
same problem here with debian sid with some experimental ( mesa, dri, ati ), on
2.6.38.2 liquorix. If i boot normallly i have no video, no tty but i have ssh
remote login but if i try to restart gdm or manually start X it freeze all.
thanks Gàbor.
--
You received this bug notification
if i try to switch to another tty it freeze eth. i am with mesa driver
now, fglrx works too
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes
workaround: edit /etc/modprobe.d/radeon-kms.conf and setting
radeon.modeset=0 , no acceleration but it starts
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
Yes, that disables kms. I am still wondering about this kms thing: if
kernel mode setting is not in the kernel but done by the X Server or so,
what's the deal? Why make it acceleration disappear? I would be happy to
say bye-bye to KMS (and boot loge), let leave X to change video mode
(instead of
and i have no audio, no acceleration and my sound card disappeared
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot without
i added radeon in /etc/modules and now it starts with modeset=1. it
seems to have glx enabled but no 3D runing desktop. The strange thing is
that i have no sound card detected now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hi LGB, thanks for persisting with the additional testing, and figuring
out how to work around the network issue.
Looking at netconkern.log, I agree with your assessment that the failure
occurs well before X starts up. The log is a bit confusing as to what
exactly is failing, however it appears
Btw, I notice you had a virtualbox installation failure. You might want
to try removing that from your system to eliminate it as a potential
cause of this problem. (Since it carries its own X stuff, it can
sometimes cause interferences, although it's probably innocent in this
case.)
--
You
Gábor Lénárt - I've forwarded this bug upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=36007 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of time!
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status:
Please tell me, if I can do more to debug the problem, I really would
like to test natty on that notebook
LGB, upstream asks, The crash doesn't look related to radeon at all.
Can you blacklist radeon, boot to runlevel 3 and then manually load it
from the console?
Can you give that a shot?
**
** 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-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Installing fglrx allows me to use natty's own kernel, but unity is
unusable then, only black boxes can be seen instead of the panel, the
launcher etc. Classic session works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati
I've changed the status from incomplete to new, since I gave some data
which was asked.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
I've also tried the generic, non-PAE kernel, also there was some update
for natty, but the problem remains as it was.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/735126
Please tell me, if I can do more to debug the problem, I really would
like to test natty on that notebook (and at our firm we have usually
this Toshiba notebook for more people, though they are not so keen on
doing anything extra for a working system, sadly). Thanks!
--
You received this bug
I am sure I am not the right person to judge, but is it possible that
it's not even az Xorg server related bug but some kind of kernel problem
when KMS is enabled (the default)? I have no Xorg log at all, and I have
the suspect that system haven't even reached the point to start Xorg
(but I am not
** Tags added: freeze
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot without disabling KMS
No, and even no MAC address can be found in the ARP table, so I guess
networking is not on yet before the freeze, or so? Now there was an
update for kernel 2.6.38-7 (instead of -6) but the same problem. Btw,
it's nice to mention that magic sysreq keys seems to work (at least alt-
sysreq-b reboots
Ok, I've booted with the old (maverick's kernel) and I hacked a new
script as the first one in /etc/rcS.d which modprobes the network
console module and also brings up the network and setting the log level
of the console. Then I rebooted with natty's current kernel, the usual
effect: half of the
Just adding the radeon.modeset=0 to the natty's kernel's parameters
causes the system to be able to boot (into a usable state, with X etc,
of course not the same 3D performance etc), and not messages like the
previous one with KMS not disabled. So for me, it seems only using or
not using KMS cause
If you plug in an ethernet cable and then boot, are you able to ssh in?
If so, you can gather the log files that way. If not, then you may have
a deeper kernel bug at work.
Without knowing the errors being encountered it's hard to guess what
might be wrong; I have two -ati systems I regularly
I also tried the safe mode I can see the boot messages then with
natty's kernel, but there is only a black screen some seconds later
(imho at starting X itself ).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/735126
Title:
[natty] system freezes on boot without disabling KMS
___
Mailing list:
Unfortunately, I can't send bug report related to the exact environment
where bug occurs since system does not boot then at all. So this bug
report was made when radeon.modeset=0 was used. Also, I couldn't find
any usable information in kernel or Xorg log files ...
--
You received this bug
53 matches
Mail list logo
