My display drives me nuts

I use an Apple TiBook with a Radeon LY which has a video out as well. This card drives me nuts. First: I seem only to be able to start X-server with fbdev and not the radeon driver. Second: I cannot start things like vlc. When i start it in a console I get a “display cannot be opened error”.

Also the BusID is somewhat funny:

lspci says:

0000:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY

But in xorg.conf I need to use BusID “0:16:0” in the Section “Device” cause when I use 00:10:00 X-server crashes. Or is there any change in numerative system I don’t know from?

hwinfo --display gives

12: PCI(AGP) 10.0: 0300 VGA compatible controller (VGA)         
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_1002_4c59
  Unique ID: _tDW.jGBruYkgeeF
  SysFS ID: /devices/pci0000:00/0000:00:10.0
  SysFS BusID: 0000:00:10.0
  Hardware Class: graphics card
  Model: "ATI Radeon LY"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x4c59 "Radeon LY"
  SubVendor: pci 0x1002 "ATI Technologies Inc"
  SubDevice: pci 0x4c59 
  Driver: "radeonfb"
  Driver Modules: "radeonfb"
  Memory Range: 0xb8000000-0xbfffffff (rw,prefetchable)
  I/O Ports: 0x400-0x4ff (rw)
  Memory Range: 0xb0000000-0xb000ffff (rw,non-prefetchable)
  Memory Range: 0xf1000000-0xf101ffff (ro,prefetchable,disabled)
  IRQ: 48 (no events)
  Module Alias: "pci:v00001002d00004C59sv00001002sd00004C59bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: radeon
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #12

Questions:
Why can’t I use the “radeon” driver?
Why do i get the “cannot open display” error?

On Fri, 15 Aug 2008 14:46:04 GMT
Peter Srp <Peter_Srp@no-mx.forums.opensuse.org> wrote:

> I use an Apple TiBook with a Radeon LY which has a video out as well.
> This card drives me nuts. First: I seem only to be able to start
> X-server with fbdev and not the radeon driver. Second: I cannot start
> things like vlc. When i start it in a console I get a “display cannot
> be opened error”.

Are you talking about a text console, as in ‘CTRL-ALT-F1/F2/F3’ etc?
If so, they’re not ‘connected’ to the graphic display (CTRL-ALT-F7), thus the
‘DISPLAY’ cannot be opened to write data to it.

> Also the BusID is somewhat funny:
> --------------------
> 0000:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon
> --------------------

{Grin} Welcome to hexadecimal counting!

10h (or 0x10) is 16 decimal.

lspci outputs the device identifiers as hex digits.

Actually, you’ll see hex numbers quite often when dealing with the hardware
side of linux. Since most hardware components have ID numbers… it’s sort
of a convention to name/number them in hex.

Anything starting with “0x” (or “OX”) is considered hexadecimal (base 16)
Anything starting with a single ‘0’, is considered octal (base 8)

> Questions:
> Why can’t I use the “radeon” driver?

I haven’t any idea why the radeon driver doesn’t work for you. :frowning:

Loni


L R Nix
lornix@lornix.com

Right so they really “mix” dec and hex, this I was considering but not sure if they would mix that. I kind of have a weak memory about that grin like Ah = 10d aso … oh man thanks for pushing my nose back into that lol

But much more interesting is why the radeon driver is not working. Ah yes and the console is not connected to any display.

But can you tell me why, if i start vlc nothing happens? lol No really if I use a console under Gnome it should work, right? I start and nothing happens. Is there a reason that it would not work with an fbdev? I had YLC running on the same machine with X-server also as fbdev and that version of YLC worked there… I know its not the same but just as an idea.

Which log could give me an idea, as message will not?

On Sat, 16 Aug 2008 12:56:04 GMT
Peter Srp <Peter_Srp@no-mx.forums.opensuse.org> wrote:

> But much more interesting is why the radeon driver is not working.

Again, search the forum for Radeon, especially posts in the last few days, as
there have been some good breakthroughs discovered. I’m afraid I’m an NVidia
Girl and despite their occasional quirks, I’ll choose NV over ATI anyday)

> Ah yes and the console is not connected to any display.

This comes from the days of yore…

There were “Terminals” (y’know, green screen, 80x25, glass TTY’s), and there
were “X-Terminals”… High-end graphics systems with some smarts. (Yes, High
end for their day…) Each was used to connect to the main unix system.

Using the DISPLAY environment variable, you could direct the output of a
graphically aware program to your X-terminal, to your neighbor’s X-terminal,
across the country to your friend’s X-terminal… and so on.

Connecting to the server with an X-terminal (Xt) was essentially the same as
connecting to the computer with a text-only terminal, with the exception that
you set the DISPLAY env variable to point to your Xt. These were the days of
honesty and integrity with the occasional joke… there was little to no
security on the Xt’s… just about ANYONE could connect to your Xt on port
6000 and sniff your keystrokes, watch your mouse movements, grab screen
snapshots, display things… so on, so forth. But it was COOL!

Skip forward a few years… change the users to lusers, and having no
security on your Xt meant you kept getting bothered, so authentication was
implemented, along with some other things…

Today, when you start up the GUI, it automatically sets up the DISPLAY
variable so your programs show up on your screen. Also sets up
authentication and other stuff to prevent someone else from popping a pr0n
filled window up.

Using a console (C-A-F1 → C-A-F6) allows you to log in… but no DISPLAY
variable is automatically defined… so any GUI type programs you try to run,
either nothing works, or they complain about “DISPLAY not set” or something.

If you set the variable by hand, as long as YOU are logged in to the Xt
(GNOME, KDE, Xfce, etc), then YOU may connect from a console on the SAME
machine. But if Mary were logged in to your machine too (via ssh for
instance), she would be unable to do the same, due to the security.

A cool feature (which I’m using right now actually!) is that you can be
sitting in front of a low-end system, ssh into another computer (my big
system!) and point DISPLAY back to the computer you’re sitting at… and run
applications like firefox, claws-mail, gimp, etc. They’re running on the big
machine with lots of power and storage and ram… but they’re DISPLAYING on
your low-end system in the other room next to the comfy chair and the purring
kitty. Yup, cool feature.

Whew! I’m long-winded… does this help?

> But can you tell me why, if i start vlc nothing happens? lol No really
> if I use a console under Gnome it should work, right? I start and
> nothing happens.

{Grin} Think I got that one…

> Is there a reason that it would not work with an fbdev?

framebuffers enable graphics to be used… but are not set up nor considered
Xt’s… so there’s a difference. SOME programs will autodetect the
presence of an active framebuffer and use that automatically. mplayer is one
I know of that does this.

> Which log could give me an idea, as message will not?

Actually, just about EVERYTHING (in a general sense) is logged
in /var/log/messages, while more detailed or more restricted
information is routed to certain other logs.

Have a look in /var/log and dig around some… some of the logs are
interesting, others pretty boring. But all useful at some point in time.
(You’ll probably need to be root to read some of them… BE CAREFUL!!!)

Loni


L R Nix
lornix@lornix.com

Don’t get me wrong but I am an old days guy myself, but not so on UX. Used to drive things like S36 and ol’ XTs and stuff. So I somehow know some of that what you say :wink: Oh and how I know to hate that terminals, bnc cabled and when something went wrong with that the whole string went down. lol

And yeah I prefer nVidia as well … you can smell the word “BUT” in the air I guess. My old PowerBook has that ATI video card and it would not make sense to do nothing against that. That thing is ages old, was '92 when I bought it I guess, and now I try to bring it back to lilfe again. But as it only drives up to MacOS X 10.4.2 and that I would have to buy and even the MacOS X 10.1 I got drives dead slow I gave Linux a shot. I was trying YDL but that has far to much trouble still. It can not even log out of E17 clean. So openSUSE 11.0 PPC seemed to be an option. Well it is indeed. But BTT.

In the /var/log, especially the message nothing is written about why vlc would not work. But now here it comes. All part of a bigger picture I found out now. Why? The same with Audactiy and the SUSE-help. All these are starting (rattling my HD) and then… nothing. Not even an error message. Well I need to look for the black IT-hole (/dev/null lol) if something is there :slight_smile: