** Changed in: discover1 (Debian)
Status: Unknown = Fix Committed
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I tried http://cdimage.ubuntu.com/daily-live/20070405/feisty-desktop-i386.iso
and it uses the radeon driver.
Yoo-hoo ! ;-)
--
vesa driver used instead of radeon for R300
https://bugs.launchpad.net/bugs/90175
You received this bug notification because you are a member of Ubuntu
Bugs, which is
rumour has it that tomorrow the image should be usable :)
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Are there ISOs to try out ?
Or can I build them myself ?
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Try a current daily livecd, that should work.
http://cdimage.ubuntu.com/daily-live/
now the i386 version is oversized, so you have to wait until it is
fixed.
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
there is now a new version in Feisty.
** Changed in: discover1 (Ubuntu)
Status: In Progress = Fix Released
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
FYI: The patch did not make it into the beta.
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Freeze exception filed.
** Changed in: discover1 (Ubuntu)
Status: Confirmed = In Progress
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: discover1 (Debian)
Status: Fix Committed = Fix Released
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
actually, could you run
discover --disable=serial,parallel,usb,ide,scsi --format=%V
%M\t%S\t%D\n video 2/dev/null
I missed the '2/dev/null' -part which means that error messages are
directed to /dev/null, and they are not seen by the postinst. We should
be able to filter out the other bogus
I can handle this :)
** Changed in: xorg (Ubuntu)
Assignee: Kyle McMartin = Timo Aaltonen
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
reassigning, there is a patch to fix discover.
** Changed in: discover1 (Ubuntu)
Sourcepackagename: xorg = discover1
Status: Needs Info = Confirmed
** Bug watch added: Debian Bug tracker #415620
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415620
** Also affects: discover1
It returns :
Unknown or unsupported bus `tvcard'
Why is still discover 1.x used ? Debian uses v2 since 2005 (sarge aka
v3.1)
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I see discover2 differences between viedo outpu devices (gfx cards), that is
calls display and video in devices, called video.
discover1 mixes them all into video.
Even then, xserver-xorg.postinst.in should be fixed. Why assume the first entry
in the list is correct ? The list has no rule for
There is a bug in xserver-xorg.postinst.in, which assumes that the first
line is the actual one we should use. Unfortunately, it seems that this
cannot be fixed reliably. If discover doesn't recognize the device (=it
isn't mapped to a X driver), output is like this:
nexus6 X11 # discover
Is it that hard to tell video capture an gfx cards apart ?
Yesterday I experienced a small wonder. I booted a live Cd (not Ubuntu) on the
same PC and :
- it used the correct driver
- it didn't try to make me blind with screen flickering (it used a 70 Hz
vrefresh)
I guess Ubuntu's goals
no need to be sarcastic, I know this sucks ;)
What I don't know is why discover lists your tv-tuner as a video card.
Maybe we could just add 'tvcard' to the --disable list? Could you try
running
discover --disable=serial,parallel,usb,ide,scsi,tvcard --format=%V
%M\t%S\t%D\n video
and tell us
$ discover --disable=serial,parallel,usb,ide,scsi --format=%V %M\t%S\t%D\n
video
parse error reading X server string `snd-bt87x'
parse error reading X server string `snd-bt87x'
Brooktree Corporation Bt878 Audio Capture unknown unknown
ATI Technologies Inc R300 AD [Radeon 9500 Pro] XFree86
** Attachment added: Output of lspci -vvnn
http://librarian.launchpad.net/6736142/lspci-vvnn
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
could you run in a terminal:
discover --disable=serial,parallel,usb,ide,scsi --format=%V
%M\t%S\t%D\n video
and attach that and /var/log/casper.log so we could see why it chose
vesa.
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
That's pretty messed up, I just verified that the two ATI pci ids in
your Xorg.log are indeed properly configured in discover-data...
(II) PCI: 01:00:0: chip 1002,4144 card 1458,4016 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4164 card 1458,4017 rev 00 class 03,80,00 hdr 00
--
** Attachment added: xorg.conf as created by ubuntu
http://librarian.launchpad.net/6647079/xorg.conf
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: the log file
http://librarian.launchpad.net/6647082/Xorg.0.log
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The log file when run without a xorg.conf file :
** Attachment added: Xorg.0.log
http://librarian.launchpad.net/6647084/Xorg.0.log
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Another thing, I tried to change screen from 1280x1024 to 1024x768 (with
VESA driver) and got an X crash, see the log
And it always uses the stupid 60 Hz refresh rate !
** Attachment added: Xorg.0.log
http://librarian.launchpad.net/6647168/Xorg.0.log.old
--
vesa driver used instead of
** Changed in: Ubuntu
Sourcepackagename: None = xorg
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please include the output of lspci -vvnn in your report so we can fix
the driver detection. Additionally, it would help if you'd file another
bug for the seperate issue of the crash.
Thanks!
Kyle
--
vesa driver used instead of radeon for R300
https://launchpad.net/bugs/90175
--
ubuntu-bugs
Needs info, but I'm guessing this will end up being a bug on discover-
data.
** Changed in: xorg (Ubuntu)
Status: Unconfirmed = Needs Info
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) = Kyle McMartin
--
vesa driver used instead of radeon for R300
28 matches
Mail list logo
