ClintD
2007-04-08, 09:07 PM CDT
I recently created a new computer, and since I need linux for some of my school simulation packages, decided to create a dual boot for Windows XP & Fedora Core 6. The computer specs are as follows: (Im not sure which will be needed to diagnose and fix, so I'd figure I'd list what I know)
Motherboard: MSI RX480_Neo2
Video card: ATI Radeon X1650
Processor: AMD Athlon 64 X2 Dual
Monitor: LG L1952TX LCD Monitor (there will be 2, but don't have both yet)
1 GB, Ram, 250 GB hard drive, DVD burner, etc.
Initial Problem #1: Monitor out of range
First, after I installed FC6, and it booted up the first time, I got an error on my monitor saying the signal was out of range. This seems like a common problem. I searched the net, found some suggestions, tried editing command that executing when booting up, but was not able to get it working. There were generally some more advanced fixes to this problem, but since I am new to Linux they didn't seem to make sense to me.
Instead, I hooked up my TV as the monitor through the video card's S cord connector. I was able to log in and adjust the settings temporarily so that it would display to my monitor. But on each reboot, it would not display the login page (I think, but wasn't able to test out on time, that if I waited a few minutes after the 'signal out of range' error popped up, I could have probably blindly logged in and then it would have adjusted its resolution after the login screen.)
I was hoping that if I did all the updates and maybe installed the correct ATI drivers, the problem would go away.
Initial Problem #2: Mouse issues
Once loaded into FC6, randomly the mouse would screw up and I would be unable to move it off the left side of the screen. I could move it up and down, and a little to the right, but it would always push back to the left. I tried two different mice, one USB, one PS/2. Once the error occurred, the only way it would go back to being normal was after a reboot.
I think I may have solved the problem after applying all the available updates, as it didn't seem to happen during the last two runs. However, since the error occurred randomly during use, I am not sure if the problem was fixed, or if it simply didn't have enough time to occur.
Current Problem: ???
So I performed all the updates, and trying to install the proper drivers for my ATI card, downloaded the files and followed the instructions here (http://ati.amd.com/support/drivers/linux/linux-radeon.html).
Afterwards, it suggested I reboot, and doing so encountered this problem:
"Failed to start X server..."
Looking at the extra details, it showed (I only wrote some of it down, hope I got the right parts):
X Windows System Version 7.1.1
...
X Protocol Version 11, Revision 0, Release 7.1.1
...
(EE) Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) no drivers available
Fatal server error:
no screens found
and loging in as root, the system seemed to try to fix itself, but wasn't able to...
couldn't start X server on card 0
couldn't start X server on card 1
couldn't start X server with old config, trying with a fresh configuration
After which the monitor gives the "signal out of range" error again, but this time, if I hook up the TV as the monitor, it wont display on the TV anymore.
I am clueless at this point. I know that at some point the ATI instructions (https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.35.5-inst.html) mentioned uninstalling the fglrx stuff, but I assumed that since I completed the remaining instructions, everything would be ok.
Two other things seemed weird... not sure how they fit into the puzzle... First, the ATI Catalyst Software wouldn't load even though the drivers were installed correctly (I had more resolution options available), though this isn't really that important to me since their software seems unnecessary. Second, when I downloaded the software from them on that page, it ends in x86_64, which seems to imply thats its for the 64 bit version even though I selected the standard 32 version. (I guess I was naively hoping that since both weren't available, the one package would determine which I had and install the proper version-- or that it just didn't matter)
Any help would be greatly appreciated as I have no idea what to do next. (oh, and if you could explain it slowly--no short cuts--that would help too :D , since I don't know my way around the OS very well yet).
Motherboard: MSI RX480_Neo2
Video card: ATI Radeon X1650
Processor: AMD Athlon 64 X2 Dual
Monitor: LG L1952TX LCD Monitor (there will be 2, but don't have both yet)
1 GB, Ram, 250 GB hard drive, DVD burner, etc.
Initial Problem #1: Monitor out of range
First, after I installed FC6, and it booted up the first time, I got an error on my monitor saying the signal was out of range. This seems like a common problem. I searched the net, found some suggestions, tried editing command that executing when booting up, but was not able to get it working. There were generally some more advanced fixes to this problem, but since I am new to Linux they didn't seem to make sense to me.
Instead, I hooked up my TV as the monitor through the video card's S cord connector. I was able to log in and adjust the settings temporarily so that it would display to my monitor. But on each reboot, it would not display the login page (I think, but wasn't able to test out on time, that if I waited a few minutes after the 'signal out of range' error popped up, I could have probably blindly logged in and then it would have adjusted its resolution after the login screen.)
I was hoping that if I did all the updates and maybe installed the correct ATI drivers, the problem would go away.
Initial Problem #2: Mouse issues
Once loaded into FC6, randomly the mouse would screw up and I would be unable to move it off the left side of the screen. I could move it up and down, and a little to the right, but it would always push back to the left. I tried two different mice, one USB, one PS/2. Once the error occurred, the only way it would go back to being normal was after a reboot.
I think I may have solved the problem after applying all the available updates, as it didn't seem to happen during the last two runs. However, since the error occurred randomly during use, I am not sure if the problem was fixed, or if it simply didn't have enough time to occur.
Current Problem: ???
So I performed all the updates, and trying to install the proper drivers for my ATI card, downloaded the files and followed the instructions here (http://ati.amd.com/support/drivers/linux/linux-radeon.html).
Afterwards, it suggested I reboot, and doing so encountered this problem:
"Failed to start X server..."
Looking at the extra details, it showed (I only wrote some of it down, hope I got the right parts):
X Windows System Version 7.1.1
...
X Protocol Version 11, Revision 0, Release 7.1.1
...
(EE) Failed to load /usr/lib/xorg/modules/drivers/fglrx_drv.so
(EE) Failed to load module "fglrx" (loader failed, 7)
(EE) no drivers available
Fatal server error:
no screens found
and loging in as root, the system seemed to try to fix itself, but wasn't able to...
couldn't start X server on card 0
couldn't start X server on card 1
couldn't start X server with old config, trying with a fresh configuration
After which the monitor gives the "signal out of range" error again, but this time, if I hook up the TV as the monitor, it wont display on the TV anymore.
I am clueless at this point. I know that at some point the ATI instructions (https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_8.35.5-inst.html) mentioned uninstalling the fglrx stuff, but I assumed that since I completed the remaining instructions, everything would be ok.
Two other things seemed weird... not sure how they fit into the puzzle... First, the ATI Catalyst Software wouldn't load even though the drivers were installed correctly (I had more resolution options available), though this isn't really that important to me since their software seems unnecessary. Second, when I downloaded the software from them on that page, it ends in x86_64, which seems to imply thats its for the 64 bit version even though I selected the standard 32 version. (I guess I was naively hoping that since both weren't available, the one package would determine which I had and install the proper version-- or that it just didn't matter)
Any help would be greatly appreciated as I have no idea what to do next. (oh, and if you could explain it slowly--no short cuts--that would help too :D , since I don't know my way around the OS very well yet).