Bug 499064 - Fedora 11 LiveCD X fails to start
Summary: Fedora 11 LiveCD X fails to start
Keywords:
Status: CLOSED DUPLICATE of bug 498457
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drivers
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-05 03:11 UTC by Nicholas Coltharp
Modified: 2018-04-11 09:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-13 04:21:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X log (33.59 KB, text/plain)
2009-05-08 02:34 UTC, Nicholas Coltharp
no flags Details

Description Nicholas Coltharp 2009-05-05 03:11:44 UTC
Description of problem:
The Fedora 1686 LiveCD does not work on my Toshiba Satellite A135-S2386. When I start it up, at the point where X11 should start, I get stuck on a screen of black-and-white bars.

My graphics card is an ATI Radeon Xpress 200M.

I have tried this CD on other computers, and it works fine. I have also tested the media without error.

Version-Release number of selected component (if applicable):
11 (preview)

How reproducible:
Completely

Steps to Reproduce:
1. Obtain a computer with a Radeon Xpress 200M graphics card (I assume)
2. Insert the F11 i686 LiveCD
3. Boot the CD
4. Wait until X starts
  
Actual results:
A screen with nothing but black-and-white bars and a moveable cursor.

Expected results:
An actual screen.

Comment 1 Matěj Cepl 2009-05-05 21:53:19 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

When the anaconda crashes, please, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, some on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Nicholas Coltharp 2009-05-06 03:29:43 UTC
Neither of the files/folders that you told me to copy seem to exist.

Comment 3 Matěj Cepl 2009-05-06 09:00:25 UTC
(In reply to comment #2)
> Neither of the files/folders that you told me to copy seem to exist.  

/tmp just have to exist. Anyway, if you are not able to collect the required information (and it is quite hard core stuff to do it), don't worry, quite probably somebody else will file the same bug.

Setting into NEEDINFO in case you will be able to reproduce it again and collect the required information. If you won't be able to do it for thirty days (and really, don't worry if you cannot), I will close this bug as INSUFFICIENT_DATA.

Comment 4 Nicholas Coltharp 2009-05-08 02:34:24 UTC
Created attachment 342962 [details]
X log

No, I have the necessary skills. The files are simply _not_ there.

I switched to a terminal environment and logged in as root. I then mounted my home fs on /mnt/fs. After that, I ran 'cp -t /mnt/fs/home/nicholas /tmp/X* /var/anaconda.xlog' and got the result:

cp: cannot stat `/tmp/X*': No such file or directory
cp: cannot stat `/var/log/anaconda.xlog': No such file or directory

I tried to use "locate," but locate didn't seem to exist either. But I did find a file named "Xorg.0.log" in /var, and I copied that over. I attached it here.

I should say one more thing--although the integrity check says that the disk is ok, K3B told me that there was an error after it was done burning it. But after I ran the medium check, and since the disk (basically) runs, I assumed that it was inconsequential.

Comment 5 Nicholas Coltharp 2009-05-13 04:21:06 UTC
Found another report that matched my problem, so closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 498457 ***


Note You need to log in before you can comment on or make changes to this bug.