New Ubuntu x86-64 installation

Stephen

I've had Ubuntu 5.04 working fine on my 32 bit athlon xp 2800+ system for a while now. I built a new machine a few days ago with the following bits in it:
Abit AN8 (non-SLI) PCI-E/Socket939 motherboard - onboard gbit lan, firewire, sound, etc.
AMD Athlon 64 3200+, venice core
ATI Radeon X800 PCI-E, 256MB.
Everything else in the system (disks etc) is the same as in the old athlon XP system. I'm using the same monitor too, which is a Benq FP71E+ flat panel that was picked up fine by the old ubuntu installation.

I installed Windows XP a few days ago and that's fine, everything's up and running. Last night I installed the 64bit version of ubuntu, but after the install when it tries to bring up the graphical login prompt, X fails to start, giving the following error:

(EE) No devices detected.

Fatal server error:
no screens found

Any idea what to do next? I can log in to a console only environment and have full access to the system as normal.


thanks.

Stephen

Fixed it...

Apparently a known issue with X700/X800 cards and ubuntu - you have to change the driver in xorg.conf from 'ati' to 'radeon'.

Syth

Well now that you fixed that I'm going to hijack this thread for my own nefarious purposes.

I'm currently running 32bit fedora core 3, and I installed ubuntu 5.04 64bit. However it has trouble with my network card. The card works totally fine on a few other distros, but haven't tried it on a 64 bit one yet (till now). It used the tulip driver that's included with the linux kernel. Everything seems normal unti I try to ping my broadband router. It says it can ping and gets a nice return time, but complains that byte #something is 0xsomething and should be 0xsomethignelse. In short it looks like it's getting scrambled along the way.

Can anyone help?

AndrewMc

Syth wrote:

I'm currently running 32bit fedora core 3, and I installed ubuntu 5.04 64bit. However it has trouble with my network card. The card works totally fine on a few other distros, but haven't tried it on a 64 bit one yet (till now). It used the tulip driver that's included with the linux kernel. Everything seems normal unti I try to ping my broadband router. It says it can ping and gets a nice return time, but complains that byte #something is 0xsomething and should be 0xsomethignelse. In short it looks like it's getting scrambled along the way.

Can anyone help?

The tulip driver is sometimes selected as a reasonable guess, but in certain cases it's actually the wrong one to use. I don't have the machine where I saw this before handy, but you need to do something like

sudo echo tulip > /etc/hotplug/blacklist.d/tulip

and reboot (I couldn't find a way to make it work without the reboot, anyway). This tells hotplug to ignore the tulip driver and try something else. I think! If that doesn't work, can you post the output of "lspci" so we can see what actual card you have?

Syth

I'll try that tonight when I get home. I thought the tupil driver was the right one because many distros had used it fine.

Syth

Right I tried that. Forcing people to use sudo can be bad at times, like the above command can't be executed via sudo, because it tried to redirect the output of the sudo into the file, which I don't have permission to access. I put 'tulip' in the file manually using sudo vim. That stopped the tulip driver from loading alright, but my network card is not detected at all.

Here is the output of lspci -vv for the network card only:

0000:02:07.0 Ethernet controller: Accton Technology Corporation EN-1216 Ethernet Adapter (rev 11)
	Subsystem: Standard Microsystems Corp [SMC]: Unknown device a255
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (16000ns min, 32000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at c000 [size=256]
	Region 1: Memory at e9023000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <available only to root>

A friend of mine got a bunch of the x86 CDs for free I'll borrow the LiveCD from that to check if it's a 64bit issue.

AndrewMc

Syth wrote:

Right I tried that. Forcing people to use sudo can be bad at times, like the above command can't be executed via sudo, because it tried to redirect the output of the sudo into the file, which I don't have permission to access.

I've found myself using "sudo bash" on ubuntu quite a bit!

Syth wrote:

I put 'tulip' in the file manually using sudo vim. That stopped the tulip driver from loading alright, but my network card is not detected at all.

Here is the output of lspci -vv for the network card only:

0000:02:07.0 Ethernet controller: Accton Technology Corporation EN-1216 Ethernet Adapter (rev 11)
	Subsystem: Standard Microsystems Corp [SMC]: Unknown device a255
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (16000ns min, 32000ns max), Cache Line Size: 0x08 (32 bytes)
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at c000 [size=256]
	Region 1: Memory at e9023000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <available only to root>

A friend of mine got a bunch of the x86 CDs for free I'll borrow the LiveCD from that to check if it's a 64bit issue.

From what I can find, the tulip driver should be the one for that card, alright. I've no 64-bit machines to know what driver issues can occur, but a bit of googling suggests it's a possibility.

Syth

AndrewMc wrote:

I've found myself using "sudo bash" on ubuntu quite a bit!

That's a great idea. Identical to "su -".

AndrewMc wrote:

From what I can find, the tulip driver should be the one for that card, alright. I've no 64-bit machines to know what driver issues can occur, but a bit of googling suggests it's a possibility.

Yeah it's the 64-bit version. I was able to use the internet fine using the 32bit live CD. I think this is a ubuntu specific problem. I briefly tried athlon64 gentoo using the exact same hardware, and I didn't have any trouble with it.