Hi there, hope you can help me.

I'm using Debian Lenny on a Sun Blade 100 and I can't get gdm run,
gdm starts and stops like 6 times but don't show the login splash
Here is the gdm log:

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux solaris-1 2.6.26-1-sparc64 #1 Sat Jan 10 17:28:04 UTC 2009 sparc64
Build Date: 09 January 2009 04:12:28AM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 6 10:18:10 2009
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ramdac" already built-in
(II) Module "i2c" already built-in
FATAL: Module mach64 not found.
(EE) [drm] drmOpen failed.
(EE) MACH64(0): [dri] DRIScreenInit Failed
AUDIT: Thu Aug 6 10:18:14 2009: 3169 X: client 2 rejected from local host (uid 104)


This is my xorg.conf:

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "ati"
Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
HorizSync 28-33
VertRefresh 48-60
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
DefaultDepth 16
SubSection "Display"
Modes "800x600"
EndSubSection
EndSection

I hope somebody can help me, and thanks by advance.
By the way, my english is not so good but I do my best.

You can try from a command prompt to reconfigure X. Do dpkg-reconfigure xserver-xorg as root. Then select the VESA driver. This should get you a basic system up and running. VESA is a generic driver that works with most video cards.

Additionally, you should do a lspci and find out what video card you have. Then you can google and find the correct driver. Right now it's looking for an ATI driver, but maybe your card needs something different (or a newer version).

I have done this and it just let me configure the keyboard layout, something about the FrameBuffer but can't select a driver to use.

It's a: ATI Technologies Inc 3D Rage XL rev 39

I have to say that I had this machine working like 4 weeks ago, with the same driver, but now that I want to use it again no body can tell me what happened to it.

By the way, I have attached the xorg log

Attached Files

Xorg.0.log.txt (29.4 KB, 1 views)

You can try to manually edit the xorg file and change "ati" to "vesa". If it was working before, I would guess some system update messed things up. Maybe there's a bug in the new version of the driver.

I get the same error, and gdm restarts like 6 times.

The ati driver version is the same one that was working, even the mach64 driver version is the same.

ii xserver-xorg-video-ati 1:6.9.0-1+lenny4 X.Org X server -- ATI display driver wrapper
ii xserver-xorg-video-mach64 6.8.0-1 X.Org X server -- ATI Mach64 display driver

Any Idea? thanks for your help

Maybe try putting mach64 in the xorg file?

It stills the same, it's not working

I'm stumped. Did you restart X each time?

I guess the only other thing would be to try to use module-assistant to rebuild the module.

Is there anything else telling in your xorg.log?

Shure, I've restarted X each time, the gdm is all what I write before and the xorg is attached in the reply #3

Here are the notices, warnings and errors from the xorg log:

...
(--) MACH64(0): PCI bus interface detected.
(--) MACH64(0): ATI Mach64 adapter detected.
(!!) MACH64(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
...
...
(II) MACH64(0): Using 8 MB linear aperture at 0x03800000.
(!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
...
(--) MACH64(0): 8192 kB of SDRAM (1:1) detected (using 8191 kB).
(WW) MACH64(0): Cannot shadow an accelerated frame buffer.
...
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.2.0
ABI class: X.Org Video Driver, version 2.0
(!!) MACH64(0): Using composite sync to match input timing.
...
(II) MACH64(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mach64"
(EE) [drm] drmOpen failed.
(EE) MACH64(0): [dri] DRIScreenInit Failed
...
(II) MACH64(0): DPMS enabled
(WW) MACH64(0): Option "UseFBDev" is not used
...


And about the module-assistant... I have never used before

Looks like there was some sort of bug with Sparc's. The bug report says it has been fixed as of May, but maybe you need to modify some frame buffer options in your xorg.

Unfortunately, I can't be of much help with that. But maybe you can google around and find some suitable options for the "Device" section or some boot parameters like append="video=atyfbff".

Oh, ok, I'll keep searching till make it work.
Anyway thanks a lot!

If it's not a production machine, you could try dist-upgrading to Squeeze and see if that fixes the problem.

Yeah but don't like that idea... I've spend a lot of headaches building some packages due to incompatible libraries and stuff like that. I mean, I need this machine working like some weeks ago.

Cheers

Oh yeah, here's a short piece about how to use module assistant, though I'm skeptical it will help in your case. Basically it's something like this:You can use m-a instead of the whole module-assistant name (I think there's a symlink installed). m-a prepare will probably download kernel headers and build-essential if you don't have them already installed. m-a list is just a way to search through what packages can be created with module-assistant. m-a a-i means "auto-install" and use whatever packagename you found that suits your graphics card.

Good luck. Just thought I'd leave one last effort.

Hi again
Thanks by the explanation about the module-assistant but it didn't work.

It didn't show any results, even I have tried with
and nothing.

Any other idea?
Is there someone else who can help me?