Update: Ubuntu upgrade works fine / Robor is an idiot! ;-)

[Robor]

Originally posted by: drag
I beleive flxinfo is a GUI program. You need to have X running in order to use it so it's useless from a virtual terminal, right?


Or am I confused here...

Also telinit 3 is a Redhat/Fedora-ism. With Ubuntu you would go:
sudo /etc/init.d/gdm stop

to stop X, I beleive. Unless Ubuntu has changed Debian policy to more closely resemble the Fedora runlevel scemes.

I have very little experiance with the FLGLX stuff. I have a ATI card, but I ain't letting that software get anywere near it.

Try this forum:
http://www.rage3d.com/board/forumdisplay.php?f=61

It's full of ATI enthusiests that use Linux. They should be able to help you figure out how to solve your problems pretty quickly.

I've used 'fglrxinfo' on the command line before and I'm 99% sure I was in the recovery console when I did it so X shouldn't be started (that what I was troubleshooting). It will report back like this:

fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)

I'll have a look over at Rage3D and see if I can find a solution. I'm too tired tonight.

Thanks everyone!!!

 

[n0cmonkey]

Originally posted by: drag
I beleive flxinfo is a GUI program. You need to have X running in order to use it so it's useless from a virtual terminal, right?


Or am I confused here...

Also telinit 3 is a Redhat/Fedora-ism. With Ubuntu you would go:
sudo /etc/init.d/gdm stop

to stop X, I beleive. Unless Ubuntu has changed Debian policy to more closely resemble the Fedora runlevel scemes.

I have very little experiance with the FLGLX stuff. I have a ATI card, but I ain't letting that software get anywere near it.

Try this forum:
http://www.rage3d.com/board/forumdisplay.php?f=61

It's full of ATI enthusiests that use Linux. They should be able to help you figure out how to solve your problems pretty quickly.

Isn't it a sysV-ism?

 

[drag]

I donno much about what is 'Sys-V' or whatnot.

Telinit 3 will indeed send you to runlevel 3 with no problems.. it's just the same exact as other multiuser runlevels. X will still be running.

# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.


It's Debian's policies that runlevels 2-5 are the same and it's up to the local administrator to decide their purpose if the admin feels like changing something.

From what I know there are a few different conventions. The 2 major ones are going to be Debian-style with Debian and Debian-based distros. Then Redhat-style which is what most 'mainstream' style systems use. Slackware has it's own and so does Gentoo. Personally my favorite is Slackware's, but it doesn't lend itself to much in the way of package management flexibility.

although for the sake of application compatability Debian can handle Redhat-style in a compatability manner for the odd rpm-based application.

In the future though it's likely to change. There is a movement of sorts to create the 'next gen' init script system that will be able to track start up dependancies in a more intellegent manner so you can do things like increase startup speed through parrellizations.

 

[DasFox]

Robor you should give Fedora a go, Ubuntu is so over rated.

ALOHA

 

[MmmSkyscraper]

Oops, nm.

 

[Nothinman]

I've used 'fglrxinfo' on the command line before and I'm 99% sure I was in the recovery console when I did it so X shouldn't be started (that what I was troubleshooting). It will report back like this:

fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)

Impossible. The fact that it says "display: :0.0 screen 0" means that it got it's info from the X server on that display, if X isn't running it won't work.

Isn't it a sysV-ism?

Sort-of. Debian doesn't start display managers like most other distros via inittab, in Debian they're normal services so there's no need to switch runlevels, to stop GDM you just do '/etc/init.d/gdm stop'.

 

[badlogic]

I just wanted to say Kubuntu is running fine after the latest updates im also running Nvidia tho. Maybe the problem is just ATI.

 

[n0cmonkey]

Originally posted by: Nothinman
Sort-of. Debian doesn't start display managers like most other distros via inittab, in Debian they're normal services so there's no need to switch runlevels, to stop GDM you just do '/etc/init.d/gdm stop'.

Alright, I'll crawl back in my little BSD hole now.

 

[Robor]

Originally posted by: DasFox
Robor you should give Fedora a go, Ubuntu is so over rated.

ALOHA

I started on FC4 but prefer Ubuntu because I like apt > yum.

 

[Robor]

Updated the Original Post with less whining and more info.

 

[Robor]

Originally posted by: Nothinman

I've used 'fglrxinfo' on the command line before and I'm 99% sure I was in the recovery console when I did it so X shouldn't be started (that what I was troubleshooting). It will report back like this:

fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 2.0.5814 (8.25.18)

Impossible. The fact that it says "display: :0.0 screen 0" means that it got it's info from the X server on that display, if X isn't running it won't work.

Hmmm... I guess I was just running it from a terminal while in X then. I could've sworn I've seen that command used to test my driver 'pre-X' though.

 

[Robor]

Updated original post. Bumping because it's not Ubuntu's fault (I'm an idiot).

 

[imported_LoKe]

:thumbsup: Trial and error. I'm running Edgy right now and it feels pretty damn stable. The official beta release is in less than a week.

 

[drag]

It still may not be your fault.
http://digg.com/linux_unix/Latest_Ubuntu_xorg_core_update_breaks_X

That was from a month ago, I think. But this sort of thing can happen.

If you don't know what happenned then how do you know whose fault it is?

This sort of thing happens to people and is a problem. Ubuntu has had a few Q/A glitches in the past which is why they are spending extra time for the 6.10 release I suppose.

But good you got it working.

 

[Robor]

Originally posted by: drag
It still may not be your fault.
http://digg.com/linux_unix/Latest_Ubuntu_xorg_core_update_breaks_X

That was from a month ago, I think. But this sort of thing can happen.

If you don't know what happenned then how do you know whose fault it is?

This sort of thing happens to people and is a problem. Ubuntu has had a few Q/A glitches in the past which is why they are spending extra time for the 6.10 release I suppose.

But good you got it working.

Yep, that xorg update got me and it was their fault. However, this one is on me I think. Like I said, I had an exact copy of my system from Friday (pre-updates). I put it in, booted it, applied the updates, and rebooted. No problems whatsoever (I didn't test wireless but mine is currently disabled in the BIOS anyway). I was (too) quick to point the finger so I must be just as quick to turn that finger around and accept the blame when I'm wrong.

 

[imported_LoKe]

Upgrading to Edgy has never been consistent for me. Chances are, they had a release of a bad driver or xorg core that you were installing when you were upgrading. Of course, they fix the problems rather quickly, and that may explain why it was working when you upgraded your backup.

 

[Robor]

Originally posted by: LoKe
Upgrading to Edgy has never been consistent for me. Chances are, they had a release of a bad driver or xorg core that you were installing when you were upgrading. Of course, they fix the problems rather quickly, and that may explain why it was working when you upgraded your backup.

Hmmm... Didn't think of that. Still, I think it was probably my screwing around because I did the xorg and driver un/re-installs over and over without success.