** Bug watch added: Freedesktop Bugzilla #8079
https://bugs.freedesktop.org/show_bug.cgi?id=8079
** Also affects: xserver-xorg-driver-ati (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=8079
Importance: Unknown
Status: Unknown
** Summary changed:
- [edgy][regression][
Quash, would you (or someone else experiencing the same) be willing to file an
upstream bug? https://bugs.freedesktop.org/enter_bug.cgi?product=DRI
Please state all details (including that either disabling DRI or setting AGP
speed to 4x is a workaround) and attach xorg.conf and Xorg.0.log to the
Tormod: As the person who originally filed this bug, I have to report
that Ericw's suggestion to switch down to AGP x4 in bios works!
I used the default Install/Live Desktop option, not the Safe Graphics
mode. I did not make any changes to xorg.conf or anywhere else. Moving
from AGP x8 to x4 was
PCI-E cards don't have an AGP option. The AGP 2x, 4x, 8x option is for
AGP cards only.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/bugs/67487
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
I have a PCIE video card on my AMD 64 machine and after investigating
the BIOS I cannot find such AGP option !
In any case I do not like this idea as this was not an issue on Dapper
anyways.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpa
My thanks to Denes Kiss and others for the suggestions above. After many, many
failed attempts to install Ubuntu the simple act of changing the Bios AGP speed
to 4 from 8 allowed the boot to proceed beyond the black screen stage.
I am grateful and happy for the chance to see what all the fuss is
My black screen problem has been solved by changing the AGP speed in the BIOS
from 8x to 4x.
I experienced similar speed problem with my USB pen drive. The automount did
not work. But changing the full speed to only high speed, the automounting
feature returned.
--
[edgy][regression][rv280] b
I Also have this problem I have a Sempron 64 3400 running on an MSI k8T
Neo v1 with ATI Radeon 9700 pro.
I've also experinced the same thing with live CD's for both PCLinuxOS
and DreamLinux in both cases using the vesa driver overcomes the problem
and once installed to hard disk the distro seems
@ericw: I tried the two things you suggested and they both worked!
- I set the BIOS AGP speed from 8x to 4x. I can then boot the Live-CD
without any "tricks" ... I did not need safe graphics mode nor any boot
parameters, no editing of xorg.conf, either.
(For Daniel Moyne: In my BIOS it's under "A
(This is for helping Daniel Moyne, but has nothing to do with the bug
probably.)
Yes, I installed fglrx 8.31.5 manually and now I have 3D support ... or
so I was told on the forum.
Before:
$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor
Monica you mean you installed fglrx 8.31.5 manually abd it works with 3D
hardware rendering ? ; now if it is a fix why the package is not made
available to the community ?
If so can you check whether X300 Radeon is supported.
Before installing with Method 2 did you remove existing fglrx package
f
I am having a problem installing ATI driver for radeon 7000 or VE card.
The windows loads up and tells me there is no ati driver. But I have
tried to install it with the cd program and manually.
I even d/led the driver and installed but it said wrong card.
So i reinstalled the oem disk and still
I am not sure... I just know that it loads up live cd burned from iso
with my old emachines t1120 and a proview 17" monitor
it has to do with the MONITOR itself !!!
My asus will load it up but will only display through a monitor as 85hz
and I cannot change the output hz with asus intel graphics
@ericw:
As I wrote, I only disabled dri and glx in xorg.conf, didn't change the driver
to vesa. Worked.
Two more Nvidia users with the black screen problem showed up on the
ubuntuusers.de forum, for them changing the driver to vesa made booting
the Live-CD possible.
I'll have to check out the BI
The Edgy Beta works fine with my Radeon 9550, but the final release produces a
blank screen.
After upgrading to final, the blank sceen appears again.
What is the difference between the Beta and Final?
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https:
Daniel, I believe William means changing your AGP card to x4 in your
bios, instead of x8. I won't be home until tomorrow, so can't test
this yet, but I will the first chance I get.
But, I do remember that with a very early version of Fedora, the only
way I could boot in to the installed version
William,
what do you mean by I set my video card to "4x" if I want to use the same trick.
Thanks.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/bugs/67487
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Daniel,
I had the same issue as you even with google earth. I fixed my problem
with adding a video card I had on hand that was Nividia. But I was tired
of Nividia cause my ATI kicks butt in games so I reinstalled it and set
it to 4x and guess what? Both Google Earth and the new LIVE CD worked. I
d
Monika,
thanks for all this information ; in my case though I am also suffering frome
the same black screen dead end at boot time there is something completely
different :
- the black screen appears each other few boots ; for example I may have 4 to 5
sessions with normal boot session then a fai
Monika, I'm curious if you would also be able to get it working if, when
editing xorg.conf, you leave the driver set to 'ati' but just disable dri.
(well, the setting of 'glx' didn't matter for me) Or, if by chance your bios
AGP speed is forced to 8x, try setting it to auto or 4x? (- then the li
I am running a final experiment to be sure. I will switch the monitors
and see if the asus will work with the Proview if so then I am sure that
it is the monitors hz value and nothing else. Also found that on
install to HD that partitioning function is not cooperating very well.
Cannot install t
Ubuntu 6.10 Live Cd Works !!!
Problem seems to be the graphics device
It does not load properly with my ASUS with Intel Extreme Graphics
(Built On Motherboard) SVGA Output to Mitsubishi Diamond Plus 71 -
Screen goes BSOD but CTRL-ALT-F1through6 works Just F7 is BSOD
But Same Live CD-Rom D
It's odd that no fix or workaround for this bug has been released yet,
given its serious nature. I would have assumed that the Edgy DVD
Release would have, at minimum, addressed a Vesa workaround so users
could, at least, boot in to the Live Desktop under the Safe Graphics
mode. Disappointing.
-
** Attachment added: "Xorg.0.log after using break=bottom and commenting out
dri and glx in xorg.conf with initramfs"
http://librarian.launchpad.net/5217508/Xorg.0.log
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/bugs/67487
-
I forgot something:
At the (initramfs) prompt, I get the error message "/bin/sh: cannot
access tty. Turning off job control". After typing chroot /root, I get
it once more.
I'll attach the /etc/X11/xorg.conf and /var/log/Xorg.0.log I get after
using break=bottom and commenting out dri and glx.
*
I had the same problem.
My processor is AMD64 and my graphics card is "ATI Technologies Inc
RV350 AP [Radeon 9600]".
I tried the following Live-CDs and all ended with a black screen:
Kubuntu Dapper i386, Kubuntu Edgy i386, Ubuntu Edgy i386, Kubuntu Edgy
for AMD 64.
(I could install from the Alte
What is strange is that since 6.10 CD a "fglrx" update has already been
issued with no progress if I am not mistaken.
I have already put this question : how to use Dapper drivers for ATI
cards on Edgy !
William do you have also at the same time the bug on GoogleEarth that gets
stuck on splash sc
My computer was giving the very same symptoms as in the original post;
couldn't start the Live CD because it would completely freeze with a
black screen after the boot-splash part, just before starting X (it
locked up such that even pressing Caps Lock wouldn't toggle the keyboard
light!)
This is a
Also keep in mind that I have AMD with via chipset motherboard that had
the ATI 9550 Card installed AGP. So it has nothing to do with the AMD
Processor nor teh motherboard. As I mentioined it all worked great when
I place a Nividia 5700VE instead of mt ATI 9550. Both cards has teh same
memory of 25
I wonder if someone could reconpile the 6.10 with the added drivers for
the ATI cards.
Or better yet what does the version before 6.10 has that 6.10 does not?
Considering that when I had my ATI AGP CARD installed it worked well off
of that version before the 6.10 release.
--
[edgy][regression][r
So what do you suggest to do to get clean drivers ?
Regards.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/bugs/67487
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Well guys it has to be with the ATI drivers on the CD of Ubuntu. I
installed a 5700VE Nividia AGP with 256 ddr ram built on to the card. I
put in the Ubuntu Live 6.10 and it started perfect without trouble. I
had my ATI 9550 with 256 of ram built on to the video card but never was
able to boot up i
AMD Athlon 64 3500+ ATI RADEON x700
Installing Ubuntu 6.10 amd64 from cd live
Boot (all default) --> Fatal Server Error: no screens found (Enter +
Enter)
Workaurond 1: try dpkg-reconfigure xserver-xorg, and select vesa server
--> sudo killall gdm --> sudo gdm --> Black screen , music, can't ente
This is where I stand with the "black screen" (with no way to regain
control other than pushing on RESET button on computer) at boot :
(1) this is not systematic as I can for example have 5 to 6 normal boot session
until I exprerience a failure.
(2) when I have a normal session running I may hav
I experienced the same black screen problem as originally described
using the edgy 386 live cd, and like the others already mention,
ctrl+alt+F1 through F6 does NOT bring up any console.
I tried both : the default Start/Install and the safe mode. None of them
worked. I tried also at that time var
i get the blank screen with cursor blinking. (6.10)
this is after the horiztonal loading screen has been going for ~2-3
mins. cd and hdd drives stop for a bit (while the horizontal bar is
loading) for the last minute then the blank screen.
brand new Gigabyte GA-K8VM800M (rev 2)
brand new Sempron
I also have same problem.
System Spec:
ATI Radeon 9800Pro
ASUS SK8V Motherboard
Opteron-244 processor
NEC 17' LCD monitor
Tried with Edgy 386 install CD.
I have Windows-XP install in the separate partition and doing dual-boot.
Somehow, I'm getting the same problem with Dapper install CD and it
Daniel Moyne wrote:
> Basil,
> during boot procedure is this bug showing up systematically or like for me
> once in a while with the same consequences : reboot by pushing button on
> computer to regian control ?
Each and every time. No respite :-( .
Cheers.
--
If you really want to know, yo
I can say that this is not an ATI issue cause I tried to use my GEFORCE
5700 when I boot the LIVE CD it still goes black after the boot screen.
But the 6.6 LIVE CD works well.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/bugs/67487
Basil,
during boot procedure is this bug showing up systematically or like for meĀ once
in a while with the same consequences : reboot by pushing button on computer to
regian control ?
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
lockup
https://launchpad.net/
It has nothing to do with the Radeon cards because I am using a nVidia
card and get a multi-coloured, illegible, screen with 6.10 Live. The
card is a GeForce 6600 which is relevant because I don't have this
problem with the other nVidia cards I have (5200 and 5500).
Furthermore, the same problem c
I wonder is it possible to install the last "fglrx driver" package from
Dapper onto Ubuntu Edgy to check whether the black screen on boot can be
fixed this way and if yes how to proceed from command line ?
The "fglrx driver" bug may also be related to the Google Earth bug where in
this case we ge
I tried Byte's suggestion and it works great on Edgy Eft (it is not working on
Dapper Drake though-any solution yet?)
However I'm still having issues. I can't make it work in 800x600 res, the
default res is too small for my 14" monitor!
If I try changing the resolution to 800x600 it just reloads
Hi
I have similiar problems to the ones described here.Although none of the
solutions provided has solve my problem with live cd. I have managed to install
with the alternative cd but after the installation is finished and after
restart I get back to the blank screen.I can get to the command pr
> as I at least get a message telling me X did not start properly
Ray, this means you have another bug (on a different card). The
workaround here might help for you, but you should anyway file another
bug, on the appropriate intel-driver for a start.
--
[edgy][regression][rv280] black screen and
Success!!! I'm currently typing from the 6.10 Live Desktop. Yes, the
person who filed this bug report has finally had success. I tried
Bytebugger's suggestion:
1) In boot option on LiveCD boot screen (F6), add:
break=bottom
2) Boot the CD, and wait for the (initramfs) prompt. At the prompt do
All,
PLEASE NOTE - My variation is on an Intel Celeron and uses an Intel
Video Chipset -, as well as I at least get a message telling me X did
not start properly.
Using the break=bottom option & renaming the xorg.conf when at the
initramfs prompt (THANK YOU ByteJuggler & Tormod !!) I am able to b
What I do not understand is that in some cases the boot procedure
terminates correctly to the logging window and sometimes avorts for
unknown reasons ; I count now good boot runs after last failure (black
screen with no way out) ; I have now 4 good boot runs after last failure
!
--
[edgy][regress
I use Kubuntu 6.10 64-bit and I don't get this error when I booted using
Kubuntu 6.10 64-bit DVD in my AMD Athlon64 and PCI-E ATI Radeon X800.
However, after a few times booting, I got the same bug when I upgraded
from 6.06 to 6.10 (that was not a fresh install). But now I've installed
6.10 freshly
TLE and Christian, it's a known bug that ati does not load the
appropriate module on X600/X800 cards, bug #28925.
Christian, that choosing radeon helped for you, might be a side effect
(another known "feature") that when specifying radeon instead of letting
ati load it, DRI will be disabled. Check
Same problem for me with AMD 64 and ATI Radeon X300 PCIE this while booting
from HD ; 2 more comments :
(1) funny that this seems to reapear not all the time but each other few reboot
; therefore might be related to a task activated each other few runs like a
cron task !?
(2) might be related to
TLE: That is odd since the ati-driver is not a real driver, it is just a
wrapper around r128, radeon and atimisc. When it is run it probes the
hardware and then selects the appropriate driver to load.
I can reproduce your results on my system, Using "radeon" explicitly
gives me working X with dri
Christian. Actually the "ati" driver has never played nice with my x800xl card.
And they didn't this time either. This is the different combination I have
tried:
Driverdri glxcombination works
ati v v No
ati x x No
vesa x x Ye
Thanks Christian.
Yes, just commenting out the glx and dri was enough. And oh, btw. it is not
necessary to remove the splash or quite in the booting... They do not cause a
problem and with break=bottom it just stops nicely at the prompt after it is
all done.
--
[edgy][regression][rv280] black
Tormod: Disabling composite results in X hard-locking, so the only
viable option seems to be to disable dri and glx.
TLE, Troels: You should only have to disable dri and glx to get a
working Live-CD. Using the "vesa" driver results in quite a performance
hit in X rendering, so using the "ati" driv
Yeah great! Tormod you are my hero!
I am posting this with from my newly booted LIVE Ubuntu 6.10 with my ATI radeon
9600XT in :-)
Using break=bottom and changing to vesa and commenting out dri and glx did the
job.
--
[edgy][regression][rv280] black screen and console freeze when X starts - drm
Tormod: Yes I figured it out now. And disabling dri and glx and shifting
to vesa lets me boot. So thank you for the fix.
I don't know if this can be fixed in time. But it is imparative that
https://launchpad.net/distros/ubuntu/+source/xorg/+bug/59618 gets fixed
so that we can boot in safe graphics
This bug is probably a duplicate of bug #37678 or bug #26513 and
upstream https://bugs.freedesktop.org/show_bug.cgi?id=5986, all well
known for a long time. Other than the workaround I sketched above, you
can use the alternate install cd.
It should be tested if disabling Composite is another, bett
The presumed guilty drm modules are part of the linux kernel. The
workaround to disable dri for these cards should be applied to the xorg
configuration scripts.
Depending on the number of affected cards/users (of this bug and not all
the other similar things commented on here), the workaround shou
TLE, you have to do precisely what I wrote, use chroot /root. Quash and
Scott, can you also try disabling dri and glx?
About Safe Graphics Mode, I don't think it has any effect, at least on
ati cards. From looking at /var/lib/dpkg/info/xserver-xorg.config it
seems broken - the boot option xforceve
I'm not to sure if this will solve anything, but I'll give it a shot.
I have an AMD Athlon64 processor and PCI-E ATI Radeon X800. Using Kubuntu 6.06
64-bit (not 6.10) Live CD, I get a similar problem (though I tested and got the
same problem with Kubuntu 6.06 32-bit). Right before KDE should load
For what it's worth, I noticed that a number of reports, including mine,
were loading Edgy 386 CDs on AMD64 systems. So, to rule that out
configuration set out of the bug, I downloaded the AMD64 desktop iso to
see if I would experience the identical bug.
I did.
I booted in to default and Safe Gr
Tormod Volden: Disabling dri and glx results in a working system
(blacklisting the drm module gives the same result), both X and
switching to consoles work (well, no 3d acceleration of course).
--
[edgy][regression][rv280] black screen and console freeze when X starts
https://launchpad.net/bugs/6
Correction: Step 4 above (in the ati section) should read:
4.) Move the new config file to the appropriate place by executing:
mv /home/ubuntu/xorg.conf.new /etc/X11/xorg.conf
--
[edgy][regression][rv280] black screen and console freeze when X starts
https://launchpad.net/bugs/67487
--
ubuntu-
OK, also running AMD64 with ATI Radeon 9700XT and having the black
screen + lockup issue on the Edgy liveCD.
I have however found a reasonably simple set of steps that seem to get
me to a VESA desktop. They are:
1.) In boot option on LiveCD boot screen (F6), add:
break=bottom
2.) Boot the CD, a
I dont think this issue is related only to ATI driver ; many with different
drivers have posted this issue in the installation/upgrade forum.
My Dell inspiron 5160 has the XGI VOLARI XP5 driver and i was hitting the black
screen using LiveCD and after upgrading from dapper. After upgrade from dap
Hey Tormod
I just tried what you suggested, and maybe it's just me who misunderstood
something, but there doesn't seem to be an xorg.conf and the break point in the
bootprocess. So basically I get a nice terminal and it stops with the
bootprocess at some time, but there is no /etc/X11/xorg.conf
For everyone to try, if you boot with "break=bottom" (maybe remove "splash" and
"quiet" while you're at it), you get a command line shell. You can then edit
xorg.conf with: chroot /root nano /etc/X11/xorg.conf
After saving and quitting the editor, you can type "exit" (or ctrl-D) to let
the boot
68 matches
Mail list logo