closing as fixed, thanks.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/55108
Title:
radeon driver, INVALID I
** Changed in: xserver-xorg-driver-ati
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/55108
Title:
radeon driver, INVALID IO ALLOCATION
--
ubuntu-bugs mailing list
** Changed in: xserver-xorg-driver-ati
Status: Confirmed => Fix Released
** Changed in: xserver-xorg-driver-ati
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/55
I'm a bit busy, but I'll see if I can test soon.
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I just upgraded my MacMini from jaunty to karmic and it does not show
the error anymore. No modeset change needed. Would you like me to
upgrade to lucid? I'm planning a full reinstall sometime soon, but I can
wait if further testing is needed.
** Changed in: xserver-xorg-video-ati (Ubuntu)
[This is an automatic notification.]
Hi Ryan,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal
Right, now works, i ve put on /etc/default/grub "quiet splash
nomodeset", and put modeset=0 on KMS configuration,
# ATI Radeon:
echo options radeon modeset=0 > /etc/modprobe.d/radeon-kms.conf
I think this creates conflicts on kernel loading module.
Regards.
--
radeon driver, INVALID IO ALLOCA
Bug, confirmed, trying to fix, it, Regards.
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Invalid => Confirmed
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We're closing this bug since it is has been some time with no response
from the original reporter. However, if the issue still exists please
feel free to reopen with the requested information. Also, if you could,
please test against the latest development version of Ubuntu, since this
confirms th
Just checking back to see if you had a chance to test it? Is the issue
still occurring in Jaunty?
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed => Incomplete
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notificatio
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Triaged => Confirmed
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: valid-xorg-conf
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Thanks; if/when you're able to get the system booted and can re-test,
please update the upstream bug report with your findings as well.
Setting to Triaged for the time being.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Triaged
--
radeon driver, INVALID IO ALLOCAT
Done!
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/258432
By the way, that wiki page (uneditable) neglects to mention that (at
least with intrepid 4) you must specify the filesystem of the usb drive
otherwise it will fail. I tried with both vfat and ext2 drives and it
didn't work until s
Ryan it would be great if you could submit a new bug using the
instructions at https://wiki.ubuntu.com/DebuggingCasper so we can get
that resolved for Intrepid. Please feel free to subscribe me to the bug
when you submit it. Thanks!
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad
Followup to my previous post.
Running without 'quiet splash', the live cd displays dozens of
kjournald starting. Commit interval 5 seconds.
EXT3-fs: mounted filesystem with ordered data mode.
before dropping to the prompt.
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bug
Still happening in my PowerPC MacMini running Hardy.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/15495799/Xorg.0.log
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Bryce-
I previously experienced this problem on Gutsy. I no longer see this
problem on Hardy on my Powerpc Mac Mini.
Thanks,
:-Dustin
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which
Confirmed on a PowerPC Mac Mini with up-to-date Gutsy.
Linux mini 2.6.22-14-powerpc #1 Sun Oct 14 21:42:06 GMT 2007 ppc
GNU/Linux
xserver-xorg-video-ati 1:6.7.195-1ubuntu2
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because yo
This problem was gone, and it came back approx 10 days ago.
I'm using gutsy
xserver-xorg-video-ati 1:6.7.195-1ubuntu2
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Changed in: xserver-xorg-driver-ati
Status: Incomplete => Confirmed
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
Just reported this same information upstream.
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
This log file contains another error at the end of file, but the INVALID
IO ALLOCATION is unrelated to that one.
** Attachment added: "Xorg.0.log reported after running just X"
http://launchpadlibrarian.net/9462531/Xorg.0.log
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net
Still happening with latest xserver-xorg-video-ati (6.7.193-1ubuntu1) in
Gutsy.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Invalid => Confirmed
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a m
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
I'm seeing this, but it does not crash:
(WW) INVALID IO ALLOCATION b: 0xf400 e: 0xf4ff correcting^G
(EE) end of block range 0xefff < begin 0xf000
I thought that this bug could be related to bug #29365, but it seems it
isn't since DVI-to-DVI works fine for radeon since Feis
Hi Ryan,
Have you had a chance to test this against Feisty? If it's still
occuring, could you please attach your full /var/log/Xorg.0.log.old
after rebooting from a crash?
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because yo
On Tue, Apr 17, 2007 at 02:57:59PM -, Timo Aaltonen wrote:
> Please try with Feisty.
Okay, will do.
What were your results with Feisty and the affected card?
Ryan
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you ar
Sorry, after not hearing anything for a while I gave up and got rid of
the non-functioning PCI card.
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Please try with Feisty.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Sourcepackagename: xorg => xserver-xorg-video-ati
Status: Confirmed => Needs Info
--
radeon driver, INVALID IO ALLOCATION
https://bugs.launchpad.net/bugs/55108
You received this bug notification because you are a membe
My xserver-xorg was working fine with no PCI cards, but I plugged in a
PCI SATA adapter and I now get these same errors and X fails to load.
If I unplug the PCI SATA card, X works again. I confirmed the same
problem both on my usual Dapper configuration (a dual-head setup), and
single-head setup,
** Changed in: xserver-xorg-driver-ati (upstream)
Status: Unknown => Needs Info
--
radeon driver, INVALID IO ALLOCATION
https://launchpad.net/bugs/55108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: Freedesktop Bugzilla #7760
https://bugs.freedesktop.org/show_bug.cgi?id=7760
** Also affects: xserver-xorg-driver-ati (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=7760
Importance: Unknown
Status: Unknown
** Changed in: xorg (Ubuntu)
Status
xorg.conf
--
radeon driver, INVALID IO ALLOCATION
https://launchpad.net/bugs/55108
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
35 matches
Mail list logo
