View previous topic :: View next topic |
Author |
Message |
BlueShift Tux's lil' helper
Joined: 04 Jun 2002 Posts: 114 Location: Belgium
|
Posted: Wed Jun 26, 2002 9:28 am Post subject: Framebuffer messed up after starting X |
|
|
I have installed Gentoo 1.2 on my shiny new iBook (600MHz with radeon) so far everything works great except for one issue:
I start Gentoo in textmode and everything works OK, I can switch consoles as much as I like without problems, however after I have started X, when I switch back to the text consoles, they look weird (sorry, can't find a better description), it looks as if some parts of the noise I see comes from the X screen. If I then switch to another text-console and back, the screen is OK again untill the text scrolls past the bottom of the screen. At this point it looks "weird" again.
Has anybody else experienced this problem ?
Greeting, |
|
Back to top |
|
|
jonnymalm n00b
Joined: 26 Jun 2002 Posts: 68
|
Posted: Wed Jun 26, 2002 4:38 pm Post subject: |
|
|
I have a g4 ti(radeon mobility m6 ly). I just installed X and am having the same problem. Have you found a solution yet? |
|
Back to top |
|
|
Gerk Retired Dev
Joined: 07 May 2002 Posts: 435
|
Posted: Wed Jun 26, 2002 5:35 pm Post subject: |
|
|
What is your configuration, what kernel version are you running, do you have DRI enabled, etc....
more info would help
|
|
Back to top |
|
|
jonnymalm n00b
Joined: 26 Jun 2002 Posts: 68
|
Posted: Wed Jun 26, 2002 6:52 pm Post subject: |
|
|
I have the latest kernel - 2.4.19-r6 and yes I have DRI enabled.
Really, this is not a big deal. Once you have X started why would you need to switch back to a text console anyway? Don't you normally just type alt-f2 to go to a text-only console? When I type command-fn-f2 I get nothing. Eitherway, now that I have X up and running this is not a big deal to me at least.
Also Gerk, I was going to message you to let you know that Xeasyconf did not work perfectly for me after running it. It created all the right settings but in the Section "Device":
#Option "RingSize" # <i>
#Option "BufferSize" # <i>
#Option "EnableDepthMoves" # [<bool>]
#Option "EnableDepthMoves" # [<bool>]
Modes "1152x768"
#Option "CrtScreen" # [<bool>]
#Option "PanelSize" # [<str>]
It put that extra mode in there. Not a major problem but one that causes X not to run. I did an emerge xeasyconf today, so I am using the current version. Besides that, thanks for the great config tool, I think it has saved a lot of time for many linuxppc users, I know it saved me a lot of time. |
|
Back to top |
|
|
BlueShift Tux's lil' helper
Joined: 04 Jun 2002 Posts: 114 Location: Belgium
|
Posted: Wed Jun 26, 2002 7:09 pm Post subject: |
|
|
Thanks for the reply, I should have posted more information to start with, sorry about that.
So here it goes:
my kernel is version 2.4.19-r6 (from package ppc-sources)
xfree is version 4.2.0-r12
Code: | /usr/X11R6/bin/glxinfo | returns:
Code: | name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: VA Linux Systems, Inc.
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 Mesa 3.4.2
OpenGL extensions:
GL_ARB_multitexture, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 16 tc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x24 16 tc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 None
0x25 16 dc 0 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None
0x26 16 dc 0 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 None |
so I guess dri is not enabled, (which is a different problem, but that's not urgent)
Since this post is getting ridiculously large anyway I might as well paste in the (what I believe) relevant part of XF86Config:
Code: | Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/X11R6/lib/modules"
... a few lines removed for this post ...
EndSection
Section "Module"
Load "extmod"
Load "xie"
Load "pex5"
Load "freetype"
Load "int10"
Load "dri"
Load "dbe"
Load "record"
Load "xtrap"
Load "glx"
Load "speedo"
Load "type1"
EndSection
... a few lines removed for this post ...
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
Identifier "Card0"
Driver "ati"
VendorName "ATI"
BoardName "Radeon Mobility M6 LY"
BusID "PCI:0:16:0"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Modes"
Identifier "Modes0"
# mode generated by Xeasyconf
Modeline "1024x768" 65.003 1024 1048 1184 1344 768 771 777 806 -HSync -VSync
EndSection
|
finally, the modules radeon and agpgart.
I think this is the most relevant information.
jonnymalm posted a reply while I was typing this. My reply to this is:
You can switch to the console with alt+crtl+fn+F1. I definately want the text console because experience has thought me that while X is very stable, it sometimes crashes, and then off course always when you are writing a CD or compiling a large project from an xterm It's also handy for when somebody quitly needs a terminal and your screen is locked (but this is not as much an issue on a notebook)
Greetings, |
|
Back to top |
|
|
Gerk Retired Dev
Joined: 07 May 2002 Posts: 435
|
Posted: Wed Jun 26, 2002 8:48 pm Post subject: |
|
|
that xeasyconf thing is a known issue that I can't workaround ATM |
|
Back to top |
|
|
Gerk Retired Dev
Joined: 07 May 2002 Posts: 435
|
Posted: Wed Jun 26, 2002 8:52 pm Post subject: |
|
|
BlueShift:
Also are you running of console or radeonfb console? I think that the (limited) DRI might solve your problem...of course it may also make it worse but is worth a shot.
(dmesg wil show your console fb if you are looking for it) |
|
Back to top |
|
|
soopurman n00b
Joined: 24 Jun 2002 Posts: 4
|
Posted: Thu Jun 27, 2002 2:59 am Post subject: "Option UseFBdev" ? |
|
|
i had this same problem with my Titanium PowerBook G4 550. to fix it, i compiled frame buffer support into my kernel (under console drivers in make menuconfig) and specifically radeon frame buffer support. then in my XF86Config, under "Device" i turned on "Option UseFBdev" and it cleared everything up.
hope this helps...
- mike _________________ "Yes, you may refer to me as Super Genius." |
|
Back to top |
|
|
BlueShift Tux's lil' helper
Joined: 04 Jun 2002 Posts: 114 Location: Belgium
|
Posted: Thu Jun 27, 2002 8:38 am Post subject: |
|
|
According to dmesg I am running the radeonfb console. It turns out that I have the radeonfb compiled into the kernel so I tried soopurmans sugestion (Option UseFBdev) and now it works as it should but I suppose this is not the clean way of fixing this. (I mean X should not have to work in a framebuffer, right??)
I'll try Gerks suggestion of enableing dri but that will probably have to wait untill the weekend.
Also does anybody have any suggestions on where I start reading to get dri to work?
Thanks for all the help guys, this really is the best Linux distro I have used so far.
Greetings, |
|
Back to top |
|
|
Gerk Retired Dev
Joined: 07 May 2002 Posts: 435
|
Posted: Thu Jun 27, 2002 3:50 pm Post subject: |
|
|
actually the UseFBDev option is a needed part of the configuration... the current radeon X drivers require that option to work (soething to do with errors retreiving info from PCI namespace).
Adding the DRI as I suggested won't help things without that option
Gerk |
|
Back to top |
|
|
|