LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-02-2008, 06:28 PM   #1
lhswanson
LQ Newbie
 
Registered: Jan 2008
Location: Marysville, WA
Distribution: Ubuntu (so far)
Posts: 29

Rep: Reputation: 15
Angry Greetings from fedora 8... NOT...


Things I learned today (after spending yet another full day trying)

...As a windows user,(when I read the install instructions during my attempt at installing fedora) I assumed that when the partitioning instructions offered to "use free space on selected drive and create default layout" as an option it meant free space on the drive..."wrong" after multiple failures, I figured out that by free space, it meant "non-allocated" space. I finally resized the single partition on the drive and installed fedora (more or less) successfully in the unallocated space.

...installing and configuring the grub loader is a lot more complicated that it seems (or should be). Multiple more installs later, I finally got the grub loader (which gave me a whopping 1.5 - 2 seconds to hit any key to access the menu. Multiple re-boots later, I finally timed it so that I could actually boot to fedora.

...Just because you can actually boot to fedora, doesn't mean that it will work. After watching the progress bar move at a snail's pace (actually taking longer to boot than XP Pro, which I didn't think was physically possible!) I saw screen after screen of text commands go by, all followed by a green [OK]. Then, just when I got my hopes up that I'd finally made it, the monitor went blank, showing a "No Signal" message. The tower sat there and did nothing and I sat looking at a blank monitor for enough time to come to the conclusion that there was not going to be anything else.

...So here I am, not knowing what went wrong, with no error messages to google, and no clue what to do next.

Any and all help will be greatly appreciated!
Larry
 
Old 01-02-2008, 07:29 PM   #2
Acron_0248
Member
 
Registered: Feb 2006
Location: Venezuela
Distribution: Gentoo
Posts: 453

Rep: Reputation: 33
Hi,


From what I know, when you get a 'No Signal' error is because the utility used by the user or the system to define the range of the monitor have failed detecting the proper range.

In Fedora, you can use the following to detect the range:

(As root excecute):
Code:
ddcprobe | grep monitorrange
Then you should get something like:

monitorrange: 30-54, 50-120

Where 30-54 is the HorizSync and 50-120 is the VertRefresh (the numbers I showed are from my monitor used as examples). After you get the No Signal error, press Ctrl + Alt + F1 so you can loggin at the console and use ddcprobe.

Then, you can add those values in the /etc/X11/xorg.conf under Section "Monitor" like this:
Code:
Section "Monitor"
# Stuff configurated by the system"
HorizSync  30-54
VertRefresh 50-120
EndSection
However, I don't really remember if ddcprobe comes installed by default, if not, you could use yum to install it.

If you think that this is too much, you can go to the console (Ctrl + Alt + F1), loggin as root and try with:
Code:
X -configure
Which will make a xorg.conf.new file that you can use to test the configuration using this command:
Code:
X -config /root/xorg.conf.new
If you don't see the No Signal error, then go back to the console and, as root, do the following:
Code:
mv /etc/X11/xorg.conf{,.bak} && mv /root/xorg.conf.new /etc/X11/xorg.conf

If that doesn't work either, and you know the hardware of your PC, then you can use xorgconfig at the command line to generate a new xorg.conf





Regards
 
Old 01-02-2008, 08:43 PM   #3
Monsuco
LQ Newbie
 
Registered: Dec 2007
Location: Longmont, Colorado, USA.
Distribution: Debian Squeeze and Lubuntu
Posts: 14

Rep: Reputation: 0
Quote:
Originally Posted by lhswanson View Post

...installing and configuring the grub loader is a lot more complicated that it seems (or should be). Multiple more installs later, I finally got the grub loader (which gave me a whopping 1.5 - 2 seconds to hit any key to access the menu. Multiple re-boots later, I finally timed it so that I could actually boot to fedora.
Most of the time the defaults are pretty good, but modifying /boot/grub/menu.lst could help if you want to change the timeout or boot order. There are also other bootloaders out there such as GAG.
Quote:
...Just because you can actually boot to fedora, doesn't mean that it will work. After watching the progress bar move at a snail's pace (actually taking longer to boot than XP Pro, which I didn't think was physically possible!) I saw screen after screen of text commands go by, all followed by a green [OK].
The first time Fedora (or pretty much any distro it seems) boots, it usually takes forever. It has to create a lot of files and set stuff up. It gets quicker the next time around. Also windows has the habit of loading the desktop rather quickly but then taking an eternity to actually let you do anything (you have to wait for antivirus, and usually a bunch of other start up crap to start running before you get to do much of anything, though if your like me, you have used MSCONFIG on your windows partition to clean out the start up crap.)

As for your monitor, go with the above advice. It might be a good idea to test your hardware with Fedora's Live CD before installing it on something in the future.
 
Old 01-03-2008, 09:09 PM   #4
lhswanson
LQ Newbie
 
Registered: Jan 2008
Location: Marysville, WA
Distribution: Ubuntu (so far)
Posts: 29

Original Poster
Rep: Reputation: 15
Still no luck....

I tried to get into a console by Ctl+Alt+F1 after the screen went blank, no such luck.

...Tried waiting it out, but after 5 min. of a blank screen, gave up.

...Watched the details screen as closely as I could (goes by pretty fast) and noted that one of the longest pauses in the process occurs when fedora is looking for IP info for usb0. It fails. The only usb port I'm using is connected to an HP printer. Any way, the process moves on until it issues the command "starting anacron". Then the screen just goes blank and the monitor shows it's "no signal, check cables" message, and there I sit, no further along than I was before. Anyone know what anacron is or why it would be causing the boot to stop?

As far as the HSync and VRefresh rates, I assumed that since the install worked and I saw the x-server start, and interacted with the install at 1024x768 (which is the resolution I always use), fedora had properly identified and installed my monitor and video card. Didn't it?

Thanks again for all the help,
Larry
 
Old 01-03-2008, 09:58 PM   #5
DragonSlayer48DX
Registered User
 
Registered: Dec 2006
Posts: 1,454
Blog Entries: 1

Rep: Reputation: 74
Here's the definition of anacron.

Quirky as it may seem, try unplugging the USB printer. If your monitor still loses signal during startup, try turning off the power to the monitor, wait 5 seconds, then turn it back on.

A friend of mine had a problem booting Windows ME on his new Compaq with the printer connected- it stopped booting, and the monitor lost signal. He had to disconnect the printer to get booted up. Once ME was finished, he could reconnect the printer and use it with no problem. I, on the other hand, had a slightly different problem booting XP on my new Dell until I learned how to time the monitor warm-up before starting the tower- I'd get the XP splash screen with the blue progress bar, then the monitor lost signal. By turning off the monitor, waiting 5 seconds then turning it back on, I found XP still booting normally.

Some devices are just too smart to be truly useful.

EDIT: BTW, if this doesn't help, give us a complete list of your hardware. It might help to know what you're running. Thanks.

Cheers

Last edited by DragonSlayer48DX; 01-03-2008 at 10:17 PM.
 
Old 01-03-2008, 10:05 PM   #6
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529
Quote:
Originally Posted by lhswanson View Post
I tried to get into a console by Ctl+Alt+F1 after the screen went blank, no such luck.
Best bet would be to make GRUB boot into runlevel 1 which means single user, no network, no graphical environment. Perfect for mucking around with config tools.


Quote:
Originally Posted by lhswanson View Post
...Watched the details screen as closely as I could (goes by pretty fast)
Runlevel 1 to 3 also give you the opportunity to persue 'dmesg|less' and system logs ('less /var/log/messages') and Xorg logs ('egrep "(WW|EE)" /var/log/Xorg.0.log|less' at ease for clues. Posting any errors (preferably in BB code tags) can help your fellow LQ members help you better.


Quote:
Originally Posted by lhswanson View Post
Anyone know what anacron is or why it would be causing the boot to stop?
Definately is not gonna be the showstopper.


Quote:
Originally Posted by lhswanson View Post
As far as the HSync and VRefresh rates, I assumed that since the install worked and I saw the x-server start, and interacted with the install at 1024x768 (which is the resolution I always use), fedora had properly identified and installed my monitor and video card. Didn't it?
Making sure (by reading the logs and reconfiguring) instead of assuming would be the best approach. If all fails start by detaching all peripherals and gizmoidal contraptions that aren't crucial for getting a successful boot.
 
Old 01-04-2008, 03:44 AM   #7
lhswanson
LQ Newbie
 
Registered: Jan 2008
Location: Marysville, WA
Distribution: Ubuntu (so far)
Posts: 29

Original Poster
Rep: Reputation: 15
proving absolute linux "newbieness"

Thanks Bill, I will try your suggestion. BTW....Don't know your age, but have the same history right up to linux, then I fall way behind!

unSpawn....Thanks for the reply! Here's where the "newbie" raises it's ugly head!

I saw it boot at run level 5, but I have no idea how to use run level 1-3. Since I can't get fedora to boot (or even a command line console), and I've read (I think) that windows can't read ext3 formatted partitions, how do I read the logs?

Also...The usb printer is the only gizmo attached, except the eth0 to the cable modem. Everything else is keyboard, mouse, and monitor.

I will try removing the non-essentials. If that doesn't help, I'll send my complete hardware configuration.

Don't give up on me yet, I'm still trying!
Thanks for all the help,
Larry
 
Old 01-04-2008, 04:58 AM   #8
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
If you want to boot in single user mode (i.e. runlevel 1), then at the GRUB menu screen, select your installation, press 'e', add a '1' (no quotes) to the end of the line that starts with the word 'kernel' and then press 'b' to boot. You can read ext3 partitions under Windows with Explore2fs.
 
Old 01-04-2008, 08:47 AM   #9
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529
FWIW I prefer Ext2 IFS. Contrary to its name it handles Ext3 as well.
 
Old 01-04-2008, 11:41 AM   #10
lhswanson
LQ Newbie
 
Registered: Jan 2008
Location: Marysville, WA
Distribution: Ubuntu (so far)
Posts: 29

Original Poster
Rep: Reputation: 15
Still no complete boot, so here's some more info

I tried everything I could, and still get to the command that starts "anacron" until the monitor goes blank. I grabbed explore2fs and was able to look at the message.log and have posted parts further down. But first, here's my pc hardware etc...

Generic pc (not a brand name)
(2) PIII 1G CPU's (bought it used, came that way)
1G RAM
(2) 80G hd's
#1 formatted into 2 40G partitions
1- win xp pro (ntfs)
2- storage and apps (ntfs)
#2 2 partitions
1- storage (fat32) 55G
2- Linux (ext3) 25G
1 generic (pioneer) DVD-ROM
1 generic (NEC) DVD-RW
1 legacy floppy drive
ms keyboard and mouse (tried both wireless and wired)
Hanns-G 19" LCD widescreen

In the message log, it always ends at the same place. I've also included any warnings or problems I was able to pick out, so here goes...


I assume that this is where it pauses for a very long time for usb0. (I have no idea where the smilies came from, sorry)

Quote:
kernel: EXT3 FS on sdb2, internal journal
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k
kernel: IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
kernel: Netfilter messages via NETLINK v0.30.
kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
kernel: audit(1199315709.135:4): avc: denied { read write } for pid=1889 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: audit(1199315709.135:5): avc: denied { read write } for pid=1889 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: audit(1199315709.147:6): avc: denied { read write } for pid=1891 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: audit(1199315709.147:7): avc: denied { read write } for pid=1891 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: audit(1199315709.183:8): avc: denied { read write } for pid=1893 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: audit(1199315709.183:9): avc: denied { read write } for pid=1893 comm="consoletype" path="/dev/pts/0" dev=devpts ino=2 scontext=system_u:system_r:consoletype_t:s0 tcontext=system_ubject_r:rhgb_devpts_t:s0 tclass=chr_file
kernel: NETDEV WATCHDOG: usb0: transmit timed out
kernel: NETDEV WATCHDOG: usb0: transmit timed out
kernel: audit(1199315770.368:10): audit_pid=1945 old=0 by auid=4294967295 subj=system_u:system_r:auditd_t:s0
automount[2135]: lookup_read_master: lookup(nisplus): couldn't locat nis+ table auto.master
acpid: starting up
acpid: 1 rule loaded

Here's the next warning...

Quote:
avahi-daemon[2340]: Found user 'avahi' (UID 498) and group 'avahi' (GID 495).
avahi-daemon[2340]: Successfully dropped root privileges.
avahi-daemon[2340]: avahi-daemon 0.6.21 starting up.
avahi-daemon[2340]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
avahi-daemon[2340]: Successfully called chroot().
avahi-daemon[2340]: Successfully dropped remaining capabilities.
avahi-daemon[2340]: Loading service file /services/ssh.service.
avahi-daemon[2340]: System host name is set to 'localhost'. This is not a suitable mDNS host name, looking for alternatives.
avahi-daemon[2340]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.10.
avahi-daemon[2340]: New relevant interface eth0.IPv4 for mDNS.
avahi-daemon[2340]: Network interface enumeration completed.
avahi-daemon[2340]: Registering new address record for fe80::7cc5:27ff:fe63:8b68 on usb0.*.
avahi-daemon[2340]: Registering new address record for fe80::202:b3ff:fe41:7f28 on eth0.*.
avahi-daemon[2340]: Registering new address record for 192.168.0.10 on eth0.IPv4.
avahi-daemon[2340]: Server startup complete. Host name is linux.local. Local service cookie is 3507518044.
avahi-daemon[2340]: Registering HINFO record with values 'I686'/'LINUX'.

And here's where it stops every time...

Quote:
acpid: client connected from 2989[0:0]
acpid: 1 client rule loaded
kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
kernel: [drm] Setting GART location based on new memory map
kernel: [drm] Loading R200 Microcode
kernel: [drm] writeback test failed
Could putting an AGP v2 into 4x mode be what's causing the crash?
 
Old 01-05-2008, 06:52 AM   #11
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529
Quote:
Originally Posted by lhswanson View Post
I tried everything I could
Could you please post the actual steps, commands, you tried? "Everything" encompasses kinda a lot, from mild cursing to ultimately nuking a small country just in case ;-p


Quote:
Originally Posted by lhswanson View Post
Could putting an AGP v2 into 4x mode be what's causing the crash?
I can't see if this is related to Direct Rendering Management (DRM), AGP or something else in the background. If we don't get anywhere (and I hope somebody will chip in some good ideas) you could try booting the Fedora CD in rescue mode (or a Live CD like KNOPPIX) and manually changing Xorg.conf to use a vanilla 2D video driver while you work on fixing things. For suggestions on what to use we should get the specs of the video card from you so we can determine the chipset used.
 
Old 01-05-2008, 09:55 AM   #12
DragonSlayer48DX
Registered User
 
Registered: Dec 2006
Posts: 1,454
Blog Entries: 1

Rep: Reputation: 74
Quote:
Originally Posted by lhswanson View Post
Could putting an AGP v2 into 4x mode be what's causing the crash?
Not if it's working properly... v2 is 4X. Read here.

As unSpawn mentioned, it would be beneficial to know the exact chipset for your video.
 
Old 01-05-2008, 09:26 PM   #13
lhswanson
LQ Newbie
 
Registered: Jan 2008
Location: Marysville, WA
Distribution: Ubuntu (so far)
Posts: 29

Original Poster
Rep: Reputation: 15
video card info

Thanks guys....

By "everything" I meant within my small skillset. I tried every combination of keystrokes that was mentioned and was not able to boot into single user, nor could I bring up a command console.

Even with explore2fs I did not know exactly where to look for an error log that would cover the boot process (I have since located at least a couple, the abbreviated contents follows).I downloaded a knoppix live cd and a simplymepis live cd that I can actually load and use (if I knew what to do with it!)

It looks like the radeon video card driver is the problem, but I'm not sure. Here's the info from the log file...

ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1


Quote:
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 4 06:21:21 2008
(==) Using config file: "/etc/X11/xorg.conf"


(WW) No monitor specified for screen "Screen0".
Using a default monitor configuration.


(WW) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(WW) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins


(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7


(--) PCI:*(1:0:0) ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1, Mem @ 0xd0000000/27, 0xe1000000/16, I/O @ 0x9000/8
(--) PCI: (1:0:1) ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) rev 1, Mem @ 0xd8000000/27, 0xe1010000/16


(II) ATI: ATI driver wrapper (version 6.7.195) for chipsets: mach64, rage128, radeon
(II) Primary Device is: PCI 01:00:0
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Reloading /usr/lib/xorg/modules//drivers/radeon_drv.so
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),

(long list of radeon cards here)


ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP)

(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset ATI Radeon 9250 5960 (AGP) found

..................lots of radeon stuff, nothing
negative.......................

(II) RADEON(0): Monitor name: HW191D ..........correct monitor.......
(II) RADEON(0): Serial No: 643GH3CY12435

...............then................

(II) RADEON(0): EDID vendor "HSD", prod id 35217
(II) RADEON(0): Not using default mode "640x350" (bad mode clock/interlace/doublescan)
(II) RADEON(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(II) RADEON(0): Not using default mode "720x400" (bad mode clock/interlace/doublescan)
(II) RADEON(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) RADEON(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan

.................etc......................

(WW) RADEON(0): No crtc mode list for crtc 1,continuing with desired mode
disable montype: 3

(==) RADEON(0): Backing store disabled
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 18
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
(WW) RADEON(0): DRI init changed memory map, adjusting ...
(WW) RADEON(0): MC_FB_LOCATION was: 0xd7ffd000 is: 0xd7ffd000
(WW) RADEON(0): MC_AGP_LOCATION was: 0xffffffc0 is: 0xc07fc000
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0xd7ffd000
(II) RADEON(0): MC_AGP_LOCATION : 0xc07fc000
(II) RADEON(0): Direct rendering enabled
(II) RADEON(0): Render acceleration enabled
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Horizontal and Vertical Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 1202)
(II) RADEON(0): Largest offscreen area available: 1472 x 6986
(II) RADEON(0): No video input capabilities detected and no information is provided - disabling multimedia i2c
(II) Loading sub module "theatre_detect"
(II) LoadModule: "theatre_detect"
(II) Loading /usr/lib/xorg/modules//multimedia/theatre_detect_drv.so
(II) Module theatre_detect: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) RADEON(0): no multimedia table present, disabling Rage Theatre.
(II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/dri/r200_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 408 x 255
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us+inet"
(**) Keyboard0: XkbLayout: "us+inet"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: Core Pointer
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(**) <default pointer>: Sensitivity: 1
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
These are the areas where it seemed to have problems or issue warnings.
Sorry it's so long, but I wasn't sure what I needed to include.

Thanks again for the help
 
Old 01-05-2008, 10:30 PM   #14
Acron_0248
Member
 
Registered: Feb 2006
Location: Venezuela
Distribution: Gentoo
Posts: 453

Rep: Reputation: 33
Wasn't there any entry with this?

(EE)

Warnings usually are common an non fatal. Try to look for any entry starting with (EE) in that log.



Regards
 
Old 01-05-2008, 10:32 PM   #15
Fred Caro
Member
 
Registered: May 2007
Posts: 999

Rep: Reputation: 166Reputation: 166
dear ihswanson,
no expert but you could try a different monitor and keyboard access to the shell is via 'ctl+alt+F2'. Try 'top' and stop the action that uses excessive cpu time.

Roy.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
http://download.fedora.us/fedora/fedora/3/i386/RPMS.os broken! caps_phisto Fedora 3 02-05-2005 05:16 PM


All times are GMT -5. The time now is 02:32 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration