

My ATi and linux
Started by
Camaro
, Apr 18 2007 09:09 PM
9 replies to this topic
#1
Posted 18 April 2007 - 09:09 PM
Well as most of you know, I have had an ATi X850XT PE for alittle over a year now. It has been a great card, I bought it second hand an the previous owner kept it in great shape. But I could never get linux to run on it. always a hardware problem when trying to load or install even livecd's. Well I put a Evga 7900GTO in, by the way that card is HUGE compared to the ATi I had to turn my hard drives side ways to fit everything( the drives normally sit from front of the case to back of the case I turned them so they were cross wise), and since putting that 7900 in all distro's I tried took right off an had no problem.
Then the kicker is I put that ATi in my brother computer an now it wont load linux.
While that card faired very well for me I am sorry to see it go but im glad I got this one now, an my brother dont do anything with his computer, he plays some games an thats about it, all the games he plays that ATi kicks a$$ on. He always brings me his computer to fix if an when he gets spyware an other crap on.
Then the kicker is I put that ATi in my brother computer an now it wont load linux.
While that card faired very well for me I am sorry to see it go but im glad I got this one now, an my brother dont do anything with his computer, he plays some games an thats about it, all the games he plays that ATi kicks a$$ on. He always brings me his computer to fix if an when he gets spyware an other crap on.
#2
Posted 18 April 2007 - 10:23 PM
Wrong drivers
And installing ATi Drivers is like.... rocket science if it's the first time!
And installing ATi Drivers is like.... rocket science if it's the first time!
#3
Posted 18 April 2007 - 10:52 PM
I could never get far enough to load drivers. for example I tried using the gentoo livecd this morning on my brothers computer it loaded till it said boot kernal then it just errored. here is what it says starts with loading modules then it says activating mdev making tmpfs attempting to do other things went too fast to see. now it is sitting at the rooot block device is unspecified or not detected. please specify a device to boot or shell for a shell....boot() : :
and Ubuntu starts up then the screen goes all wavy an fuzzy. it says unable to load X server an asks about log something I can't tell anymore because I cant read it clearly. Now this was the 64 bit of Ubuntu, I am going to try the 32bit see if it also does the same.
and Ubuntu starts up then the screen goes all wavy an fuzzy. it says unable to load X server an asks about log something I can't tell anymore because I cant read it clearly. Now this was the 64 bit of Ubuntu, I am going to try the 32bit see if it also does the same.
#4
Posted 18 April 2007 - 10:57 PM
Ok, there's something wrong with your BIOS setting, is it an AGP or PCI-e card?
I'll have a look at what specifications are needed te boot it.
Further, Ubuntu/Kubuntu/Xubuntu needs to be loaded in safe graphics mode on any high-end card
And high end means above GeForce FX series (don't know which ATi series is comparable to that)
I'll have a look at what specifications are needed te boot it.
Further, Ubuntu/Kubuntu/Xubuntu needs to be loaded in safe graphics mode on any high-end card
And high end means above GeForce FX series (don't know which ATi series is comparable to that)
#5
Posted 18 April 2007 - 11:08 PM
Ok some new information, the 32bit version of ubuntu says
udevd-event[2047] : run_program: '/sbin/modprobe' abnormal exit
BusyBox v1.1.3 (Debian 1:1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands/
/bin/sh: can't access tty: job control turned off
(initramfs) [ 182.082437] usbcore: registered new interface driver hiddev
[ 182.190561] input : Logitech USB-PS/2 Optical Mouse as /class/input/input2
[ 182.190601] input : usb hid v1.10 Mouse [Logitech usb-ps/2 optical mouse] on ush-0000:00:1a.0-2
[182.190680]usbcore : registered new interface driver usbhid
[182.190706] drivers/usb/input/hid-core.c: v2.6 :usb hid core driver.
then it just sits there.with a blinking curser but nothing infront of it.
It is a pci-e graphics an it is several years old but it was a very highend at that time.
I did try installing in safe graphics mode.
udevd-event[2047] : run_program: '/sbin/modprobe' abnormal exit
BusyBox v1.1.3 (Debian 1:1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands/
/bin/sh: can't access tty: job control turned off
(initramfs) [ 182.082437] usbcore: registered new interface driver hiddev
[ 182.190561] input : Logitech USB-PS/2 Optical Mouse as /class/input/input2
[ 182.190601] input : usb hid v1.10 Mouse [Logitech usb-ps/2 optical mouse] on ush-0000:00:1a.0-2
[182.190680]usbcore : registered new interface driver usbhid
[182.190706] drivers/usb/input/hid-core.c: v2.6 :usb hid core driver.
then it just sits there.with a blinking curser but nothing infront of it.
It is a pci-e graphics an it is several years old but it was a very highend at that time.
I did try installing in safe graphics mode.
#6
Posted 19 April 2007 - 12:04 AM
Download the Alternate Install CD.
feisty-alternate-amd64.iso
http://cdimage.ubunt.../daily/current/
feisty-alternate-amd64.iso
http://cdimage.ubunt.../daily/current/
#7
Posted 19 April 2007 - 01:08 AM
It seems to be unable to deal with your hardware lay-out, it looks like a graphics card connection problem. This is strange, because it should always be able to fall back to MESA...
What are you system details?
Here are some boot options you could try:
noapic
nolapic
acpi=off
noapic and nolapic can NOT be combined (it will make the kernel totally ignore the CPU, which doesn't work as you might imagine)
What are you system details?
Here are some boot options you could try:
noapic
nolapic
acpi=off
noapic and nolapic can NOT be combined (it will make the kernel totally ignore the CPU, which doesn't work as you might imagine)
#8
Posted 19 April 2007 - 01:17 AM
Sphere, on Apr 18 2007, 08:08 PM, said:
It seems to be unable to deal with your hardware lay-out, it looks like a graphics card connection problem. This is strange, because it should always be able to fall back to MESA...
What are you system details?
Here are some boot options you could try:
noapic
nolapic
acpi=off
noapic and nolapic can NOT be combined (it will make the kernel totally ignore the CPU, which doesn't work as you might imagine)
What are you system details?
Here are some boot options you could try:
noapic
nolapic
acpi=off
noapic and nolapic can NOT be combined (it will make the kernel totally ignore the CPU, which doesn't work as you might imagine)

Now the ATi is connected to a GA-965P-DS3 intel E6400 with 2gb of OCZ's DDR2 800
While I had that card in my machine I tried several boot options noapic, acpi=off. dont think I did the nolapic though.
#9
Posted 19 April 2007 - 01:33 AM
I would try Ubuntu 6.06, I had some issues on acouple boxes with 6.10 freezing on install,
Oddly enough On some distro's Ive had to use another card to install,then put the problem card in and it had no problem.
Unlike new windows versions,linux seems to act like windows 3.1 in alot of instances,it doent deal with IRQ conflicts very well.on some boards I had to set the IRQ's on slots for it to work.
Oddly enough On some distro's Ive had to use another card to install,then put the problem card in and it had no problem.
Unlike new windows versions,linux seems to act like windows 3.1 in alot of instances,it doent deal with IRQ conflicts very well.on some boards I had to set the IRQ's on slots for it to work.
#10
Posted 22 April 2007 - 01:45 PM
viper666, on Apr 18 2007, 08:33 PM, said:
I would try Ubuntu 6.06, I had some issues on acouple boxes with 6.10 freezing on install,
Oddly enough On some distro's Ive had to use another card to install,then put the problem card in and it had no problem.
Unlike new windows versions,linux seems to act like windows 3.1 in alot of instances,it doent deal with IRQ conflicts very well.on some boards I had to set the IRQ's on slots for it to work.
Oddly enough On some distro's Ive had to use another card to install,then put the problem card in and it had no problem.
Unlike new windows versions,linux seems to act like windows 3.1 in alot of instances,it doent deal with IRQ conflicts very well.on some boards I had to set the IRQ's on slots for it to work.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users