View previous topic :: View next topic |
Author |
Message |
koffin n00b
Joined: 06 Mar 2003 Posts: 8 Location: San Deigo, CA
|
Posted: Fri Oct 24, 2003 9:43 pm Post subject: Problems with Xfree86 |
|
|
I keep getting "No devices detected". My only guess that I can't seem to work out is that the Creator3d is not being detected properly. I don't see any mention of it in dmesg. So is there something I need to do to get it properly reconized? Or am I posibly missing something in the kernel configuration.
Thanx |
|
Back to top |
|
|
H0bb3z Tux's lil' helper
Joined: 28 May 2003 Posts: 121 Location: in the transmogrifier
|
Posted: Sat Oct 25, 2003 5:06 am Post subject: |
|
|
Well, I don't have a Creator3D card, but my TurboGX issues were similar. I first got it running in console mode: when recompiling my kernel, in Console drivers, I added PROM console and frame buffer support. I chose CGsix SBUS support to get the framebuffer noticed.
In XF86Config, here's my device detail:
Code: | Section "Device"
Identifier "TurboGX"
Driver "suncg6"
Option "UseFBDev" "true"
EndSection |
I'm not sure what the driver spec for a Creator3D is, but that should be the only thing that you need to change... _________________ -H0bb3z-
-----------
Intel QX9770 | 6Gb DDR3 | ATI 4870 HD 1Gb | 2xSeagate 1Tb SATAs
Running Funtoo Core2 build |
|
Back to top |
|
|
Ferris Retired Dev
Joined: 13 Jan 2003 Posts: 426 Location: N. Virginia (USA)
|
Posted: Sat Oct 25, 2003 2:31 pm Post subject: |
|
|
The driver for the Creator (or Elite) card is
dmesg should show something like
Code: |
fb0: Elite 3D at 000001fc00000000 type 3 DAC 0
|
but with "Creator" substituted for "Elite."
Anyway, look for the "fb0:" in the dmesg and see if it says "Creator".
Regards, |
|
Back to top |
|
|
Ferris Retired Dev
Joined: 13 Jan 2003 Posts: 426 Location: N. Virginia (USA)
|
Posted: Sat Oct 25, 2003 10:06 pm Post subject: |
|
|
Now, I am on a system (U2) with a Creator ffb2+(Horizontal) framebuffer in
it, so I can let you know exactly what dmesg says for this particular
configuration:
Code: |
Console: switching to colour frame buffer device 144x54
fb0: Creator 3D at 000001fc00000000 type 83 DAC 10
|
For your reference, this drives it OK in the XF86Config file:
Code: |
Section "Device"
Identifier "Card0"
BoardName "Sun|FFB2+ Horizontal Creator 3D (ffb)"
VendorName "Sun Microsystems"
Driver "sunffb"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 1
EndSubSection
SubSection "Display"
Depth 4
EndSubSection
SubSection "Display"
Depth 8
EndSubSection
SubSection "Display"
Depth 15
EndSubSection
SubSection "Display"
Depth 16
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024"
EndSubSection
SubSection "Display"
Depth 32
EndSubSection
EndSection
|
Most of the stuff in the "Screen" section is garbage, because the Creator
(or sunffb at any rate) allows only depth 24, and the driver will error out
if you try anything else.
Regards, |
|
Back to top |
|
|
labrador Guru
Joined: 04 Oct 2003 Posts: 316
|
Posted: Thu Oct 30, 2003 7:10 pm Post subject: XF86Config is different in Sparc |
|
|
There are several devices that are not well autoprobed by the XF86config tools. At least that was my experience on my Ultra1.
Here are the tricky sections:
Code: |
# Mouse..
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/sunmouse"
Option "Protocol" "BusMouse"
EndSection
|
Code: |
#Keyboard..
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "sun"
Option "XkbModel" "type5"
Option "XkbLayout" "us"
Option "XkbOptions" "ctrl:swapcaps"
EndSection
|
Code: |
# Video (Creator 3D)..
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
Identifier "Creator 3D"
Driver "sunffb"
Option "UseFBDev" "true"
BusID "SBUS:/SUNW,ffb@1e,0"
EndSection
|
Code: |
#If you happen to have this Sun monitor...
Section "Monitor"
Identifier "Sun GDM-20D10"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-92
VertRefresh 50-85
Option "DPMS"
EndSection
|
My preference was to swap the function of the Ctrl and Caps Lock keys
as I'm usually using a PC keyboard on other machines and this
keeps the location consistant with x86 platforms. |
|
Back to top |
|
|
koffin n00b
Joined: 06 Mar 2003 Posts: 8 Location: San Deigo, CA
|
Posted: Thu Nov 13, 2003 10:50 pm Post subject: kernel issue |
|
|
so what options are required in the kernel to get the Creator 3d reconized as I am not getting any message about fb0. I turned on the frame buffer stuff but still nothing?
Thanx |
|
Back to top |
|
|
NewBlackDak Guru
Joined: 02 Nov 2003 Posts: 512 Location: Utah County, UT
|
Posted: Fri Nov 14, 2003 4:26 am Post subject: |
|
|
I can't get the keyboard to work right. After you startx it the key-mappings get al fubar. You have to SSH in, and reboot to get the terminal back. I see a nice pretty fluxbox desktop come up, and the mouse works fine. The KB is still messed up after you kill X though.
Code: |
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "sun"
Option "XkbModel" "type5c"
EndSection |
If I try to add Code: |
Option "XkbLayout" "us" |
it doesn't make any difference. What am I doing wrong? The back of the KB says .
I tried just type5, and it didn't make a diff. |
|
Back to top |
|
|
phygradmarko n00b
Joined: 13 Jul 2003 Posts: 26 Location: Buffalo, NY
|
Posted: Sat Nov 15, 2003 1:45 pm Post subject: |
|
|
This is what I use on my U2.
[code]
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "sun"
Option "XkbModel" "type5"
Option "XkbLayout" "us"
EndSection
[\code]
I also use this on some U5 machines I administer.
Hope this helps... |
|
Back to top |
|
|
Ferris Retired Dev
Joined: 13 Jan 2003 Posts: 426 Location: N. Virginia (USA)
|
Posted: Sat Nov 15, 2003 5:12 pm Post subject: |
|
|
For koffin:
As for the kernel option: It is
Code: |
CONFIG_FB_CREATOR=y
|
And, depending on your system (mine are U2, U60) also SBUS. So, for
example, my kernel .config for the U2 contains the following snippet:
Code: |
# Console drivers
#
CONFIG_PROM_CONSOLE=y
#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_LOGO_TUX is not set
# CONFIG_FB_LOGO_LARRY is not set
CONFIG_FB_LOGO_GENTOO=y
# CONFIG_FB_LOGO_G is not set
# CONFIG_FB_LOGO_PENGUIN is not set
# CONFIG_FB_LOGO_POWEREDBY is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_CLGEN is not set
CONFIG_FB_PM2=y
# CONFIG_FB_PM2_FIFO_DISCONNECT is not set
CONFIG_FB_PM2_PCI=y
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_ATY=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_CT=y
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
CONFIG_FB_SBUS=y
CONFIG_FB_CREATOR=y
# CONFIG_FB_CGSIX is not set
# CONFIG_FB_BWTWO is not set
# CONFIG_FB_CGTHREE is not set
# CONFIG_FB_LEO is not set
CONFIG_FB_PCI=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_CT=y
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_FONTWIDTH8_ONLY=y
CONFIG_FONT_SUN8x16=y
# CONFIG_FBCON_FONTS is not set
#
# Misc Linux/SPARC drivers
#
CONFIG_SUN_OPENPROMIO=y
CONFIG_SUN_MOSTEK_RTC=y
CONFIG_SAB82532=y
CONFIG_OBP_FLASH=m
# CONFIG_SUN_BPP is not set
# CONFIG_SUN_VIDEOPIX is not set
CONFIG_SUN_AURORA=m
|
(The "CONFIG_FB_CREATOR=y" is buried in the middle of all that.)
Some of this (like, the Creator support) I supplied, and some of it the
'make oldconfig' supplied.
If you build the kernel with this, and if you do have a Creator or Elite,
you will see from dmesg something like
Code: |
fb0: Elite 3D at 000001fc00000000 type 3 DAC 0
|
(with Creator substituted, as noted above.)
Out of curiosity, what does 'ls -l /dev/fb0' give you? My systems give
something like
Code: |
antaresia linux # ls -l /dev/fb?
0 lr-xr-xr-x 1 root root 4 Nov 13 18:25 /dev/fb0 -> fb/0
antaresia linux # ls -l /dev/fb/0
0 crw------- 1 root root 29, 0 Jan 1 1970 /dev/fb/0
antaresia linux #
|
(Created at boot: this system was booted on Nov 13, a couple days ago.)
Hope this helps;
Regards, |
|
Back to top |
|
|
|