LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   Black Lines/ Grid on right side of screen after installing new kernal (https://www.linuxquestions.org/questions/linux-kernel-70/black-lines-grid-on-right-side-of-screen-after-installing-new-kernal-455218/)

penguinman99 06-15-2006 07:46 PM

Black Lines/ Grid on right side of screen after installing new kernal
 
After installing Linux kernel version: 2.6.16-1.2133_FC5 black lines
in the form of a grid on the right side of the screen appear. Strangely enough when I tried to take a screen shot of the grids nothing appeared. But they are there. It is not an urgent matter everything else still works but it can be annoying. The grid is not present while booting up. It does not appear untill after logging in.

Any help is much appreciated.
Thanks.
Screen shoots

Notwerk 06-17-2006 08:49 AM

I'm guess a little here, so please reply with the right information if any of this is not right.

You installed Fedora Core, then installed the 3D card driver and everything was runnign fine. Later you updated the kernel but didn't uninstall the 3D card's driver first.

So now your XServer is setup to use the 3D card driver, and the driver *installed*. However, since the kernel changed, the new kernel won't take the kernel module which is needed to run the 3D card.

If this scenario seems right then all you need to do is to re-install the 3D card's driver for the new kernel :)

If not, then please post your /etc/X11/xorg.conf file and provide the model/brand of the display adapter.

penguinman99 06-19-2006 12:10 AM

Fedora Core 5 Running Gnome. I installed no graphical drivers whatsoever. All the graphics worked thus I had no need to install graphical anything. No 3D drivers no nothing. The problem started occuring after I updated the kernal.
My monitor as you can see below is an ATI Mobility Radeon 9600

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
InputDevice "Mouse0" "AlwaysCore"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "synaptics"
Load "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto-dev"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"

### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "LCD Panel 1600x1200"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 31.5 - 90.0
VertRefresh 60.0 - 60.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "Videocard vendor"
BoardName "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1400x1050" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

Thank you, your assitance is much appreciated

Notwerk 06-19-2006 02:01 AM

OK. Sorry about the ranting in my previous post, just that that scenario happened to me almost evertime I updated the kernel.... lol.

1) Is it an LCD panel or is XServer setup wrong?
Quote:

ModelName "LCD Panel 1600x1200"
2) What resolution were you using before updating the kernel? cause now it's defaulting to 24-bitx1600x1200. Did you try to take the monitor to a lower resolution under gnome? Try 800x600 just to see if it works, then work your way up the available resolutions one by one.
Quote:

DefaultDepth 24
.
.
.
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1600x1200" "1400x1050" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
3) Finally, if you still have the old kernel installed, boot into it and do a:
Code:

#lsmod > /home/USERNAME/old.modules
Then boot into the new kernel and do the same:
Code:

#lsmod > /home/USERNAME/new.modules
And post the results of:
Code:

#diff /home/USERNAME/old.modules /home/USERNAME/new.modules

penguinman99 06-20-2006 12:27 PM

Changing the resolution did it for me. Everything was huge so I just changed it back to 1600X 1200 problem solved. Strangly I tried that before it did not work but now it does. Thanks...


All times are GMT -5. The time now is 02:46 AM.