Hp 2230s resolutions issue and fatal kernel error

Kaya Saman · #1 6th November 2009, 11:22 AM

Hi all,

am running Fedora 11 x86_64 build on a Core2Duo based laptop with 6GB RAM.

I have a few operating systems on here, a mixture of Sun Solaris and Linux which all show the display properly using Gnome2 apart from Fedora 11 :-(

Somehow the resolution is all screwed up as the window sizes seem to be 1024x768 or 640x480 - basically they're huge in comparison to all other Gnome2 environments I have on the system!

I have the latest 'stable' Xorg installed on both F11 and Ubuntu 9.04 (Jaunty), can't remember Ubuntu's version but F11 is 2.7...... Ubuntu should be similar.

Before I forget the GFX adapter is an Intel GM4500MHD using the GM45 chipset and the screen is a 12.1".

xrandr shows this:

Code:

# xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
   1280x800       60.0*+
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 unknown connection (normal left inverted right x axis y axis)
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9

already things are weird as no way can this GPU support resolutions of 8192x8192!!

Xorg.log shows this:

Code:

(II) intel(0): EDID for output VGA1
(II) intel(0): EDID for output LVDS1
(II) intel(0): Manufacturer: SEC  Model: 4941  Serial#: 0
(II) intel(0): Year: 2008  Week: 0
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): Max Image Size [cm]: horiz.: 26  vert.: 16
(II) intel(0): Gamma: 2.20
(II) intel(0): No DPMS capabilities specified
(II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.580 redY: 0.340   greenX: 0.310 greenY: 0.550
(II) intel(0): blueX: 0.155 blueY: 0.155   whiteX: 0.313 whiteY: 0.329
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported detailed timing:
(II) intel(0): clock: 69.3 MHz   Image Size:  261 x 163 mm
(II) intel(0): h_active: 1280  h_sync: 1296  h_sync_end 1344 h_blank_end 1415 h_border: 0
(II) intel(0): v_active: 800  v_sync: 801  v_sync_end 804 v_blanking: 816 v_border: 0
(WW) intel(0): Unknown vendor-specific block f
(II) intel(0):  SAMSUNG
(II) intel(0):  121AT02-A01
(II) intel(0): EDID (in hex):
(II) intel(0): 	00ffffffffffff004ca3414900000000
(II) intel(0): 	00120103801a10780a87f594574f8c27
(II) intel(0): 	27505400000001010101010101010101
(II) intel(0): 	010101010101121b0087502010301030
(II) intel(0): 	130005a3100000190000000f00000000
(II) intel(0): 	00000000002387026400000000fe0053
(II) intel(0): 	414d53554e470a2020202020000000fe
(II) intel(0): 	00313231415430322d4130310a200018
(II) intel(0): EDID vendor "SEC", prod id 18753
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0   69.30  1280 1296 1344 1415  800 801 804 816 -hsync -vsync (49.0 kHz)
(II) intel(0): Printing probed modes for output LVDS1
(II) intel(0): Modeline "1280x800"x60.0   69.30  1280 1296 1344 1415  800 801 804 816 -hsync -vsync (49.0 kHz)
(II) intel(0): EDID for output DVI1
(II) intel(0): EDID for output TV1
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output TV1
(II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)

xsession errors are these:

Code:

# cat .xsession-errors
GNOME_KEYRING_SOCKET=/tmp/keyring-5SKo3C/socket
SSH_AUTH_SOCK=/tmp/keyring-5SKo3C/socket.ssh
Window manager warning: Failed to read saved session file /home/kaya/.config/metacity/sessions/106eaebb0086f5bff1125750497838994100000020970023.ms: Failed to open file '/home/kaya/.config/metacity/sessions/106eaebb0086f5bff1125750497838994100000020970023.ms': No such file or directory
Initializing nautilus-gdu extension

** (nautilus:2277): WARNING **: Unable to add monitor: Not supported

Also when booted I get a strange fatal kernel error has occurred message which then sends information to the developers?? I just upgraded to the Livna repo which actually upgraded the kernel and the error went away for one boot but is now back :-(

Why does this happen even?? What data should I provide since the machine I assume sent a backtrace already to the F11 team??

My current kernel:

Code:

# uname -a
Linux Hp-Compaq-2230s 2.6.30.9-96.fc11.x86_64 #1 SMP Wed Nov 4 00:02:04 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

Many thanks for any help, I really appreciate it!

Kaya Saman · #2 6th November 2009, 04:24 PM

Not sure if more information will help anybody help me out:

dmesg shows:

Code:

# dmesg | grep intel
 [<ffffffff816c0781>] intel_iommu_init+0x16/0x76f
agpgart-intel 0000:00:00.0: Intel Mobile Intel® GM45 Express Chipset
agpgart-intel 0000:00:00.0: detected 65532K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
fb0: inteldrmfb frame buffer device
platform microcode: firmware: requesting intel-ucode/06-17-0a
platform microcode: firmware: requesting intel-ucode/06-17-0a

xdriinfo shows:

Code:

# xdriinfo
Screen 0: i965

lsmod shows:

Code:

# lsmod
Module                  Size  Used by
fuse                   57632  2 
nfsd                  275600  9 
lockd                  71300  1 nfsd
nfs_acl                 3120  1 nfsd
auth_rpcgss            41312  1 nfsd
exportfs                4512  1 nfsd
rfcomm                 71440  4 
bridge                 54000  0 
stp                     2692  1 bridge
llc                     6352  2 bridge,stp
bnep                   19408  2 
sco                    19924  2 
l2cap                  38944  16 rfcomm,bnep
sunrpc                189864  11 nfsd,lockd,nfs_acl,auth_rpcgss
ip6t_REJECT             5824  2 
nf_conntrack_ipv6      22168  2 
ip6table_filter         3984  1 
ip6_tables             19600  1 ip6table_filter
ipv6                  297768  38 ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand        8040  2 
acpi_cpufreq           10432  0 
freq_table              4832  2 cpufreq_ondemand,acpi_cpufreq
dm_multipath           16904  0 
uinput                  9024  0 
snd_hda_codec_intelhdmi    14880  1 
snd_hda_codec_analog    76736  1 
arc4                    2128  2 
ecb                     3232  2 
iwlagn                148212  0 
iwlcore               160916  1 iwlagn
snd_hda_intel          29144  2 
snd_hda_codec          71856  3 snd_hda_codec_intelhdmi,snd_hda_codec_analog,snd_hda_intel
snd_hwdep               9128  1 snd_hda_codec
rfkill                 11284  2 iwlcore
snd_pcm                81544  2 snd_hda_intel,snd_hda_codec
lib80211                6404  1 iwlcore
mac80211              214264  2 iwlagn,iwlcore
btusb                  16884  2 
snd_timer              22512  1 snd_pcm
snd                    67160  11 snd_hda_codec_intelhdmi,snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
uvcvideo               58220  0 
videodev               35632  1 uvcvideo
bluetooth              93380  9 rfcomm,bnep,sco,l2cap,btusb
cfg80211               62472  3 iwlagn,iwlcore,mac80211
soundcore               7152  1 snd
snd_page_alloc          9536  2 snd_hda_intel,snd_pcm
sky2                   48436  0 
iTCO_wdt               12896  0 
iTCO_vendor_support     3524  1 iTCO_wdt
v4l1_compat            14020  2 uvcvideo,videodev
serio_raw               6580  0 
joydev                 11952  0 
pcspkr                  2896  0 
hp_accel               11504  0 
wmi                     7248  0 
lis3lv02d               9344  1 hp_accel
v4l2_compat_ioctl32    10704  1 videodev
i915                  177880  2 
drm                   209284  2 i915
i2c_algo_bit            6020  1 i915
video                  23164  1 i915
output                  3312  1 video
i2c_core               31632  3 i915,drm,i2c_algo_bit

lspci shows:

Code:

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

It might seem from the output that nothing is wrong, but the windows are huge and test barely readable say for example from Seamonkey while writing this. I just tried torcs game right now which ran really slowly unlike on Ubuntu 9.04. CPU was maxed out and only managed about 6fps while on Ubuntu I get at least 25fps??

I really don't know what is going on but something is definitely up only I have no idea where to begin figuring out what! I had a look at my kernel error in the mean time also and actually it turns out that Fedora claims that my machine has a bios error although is unlikely since every other OS on here seems to work fine!

What is going on and will I be able to keep using Fedora or will I have to let it go?

Many thanks!

Kaya Saman · #3 8th November 2009, 12:54 PM

After a bit more research the kernel error turned out to be that F11 didn't like my BIOS and thought that there was an error with that!

Also I think my res is ok after comparison with Ubuntu 9.04 modelines, however the Gnome2 panels and application windows are still huge??

It would be nice to get a reply and see what someone has to say about that!! Gterm for example takes up nearly the whole screen while on Ubuntu I can get 2 terminals side by side..... in view the same size is set on both which means that something somewhere is hinkey just what I do not know..... :-(

Anyone??? Replies??

Nokia · #4 8th November 2009, 02:43 PM

Do you have the same issues in F12 and Ubuntu 9.10 ? Because UXA is used on both. Also, F12 comes with xorg-x11-server-common-1.7.1-7.fc12.i686 and 1.7.2 seems to be a few weeks away. Try F12 using ftp.lug.ro:/fedora/linux/development/i386/os/images/boot.iso or see the thread on this forum about the Release Candidates cd/dvd's

Kaya Saman · #5 10th November 2009, 12:45 AM

Many thanks for the response and many apologies for being so late to respond myself!!!

I don't have F12 or Ubuntu 9.10 installed as I have no more space or partitions to install them as I'm already running 9 operating systems on my laptop.

However, even with Ubuntu 9.04 I have issues with the KDE4 environment as I actually run KUbuntu so I had to switch over to Gnome2......

Not sure if I should upgrade F11 to F12 as F11 is meant to be stable, but nonetheless the problem seems to either be with the screen itself not being recognized or the GFX card itself which is a GM45MHD with hybrid semi shared memory of 256MB hardwired and 128MB dynamically allocated from the systems on RAM......

Because of this new GPU design I actually feel that the bios issue which is making the kernel fail is linked in to this?? - somehow!

Nokia · #6 10th November 2009, 05:23 AM

F12 has gone gold.

Official release is on the 17th.
Given your problems, do not upgrade. Do a new install instead. Also, if having any more problems report it on https://bugzilla.redhat.com so it can be addressed quickly and swiftly.

Intel is one of the most Linux-friendly manufacturers out there. Most likely, your errors might be related to some kernel configuration switches kernel guys should tweak in a new manner to address your issue(s). However they can't help in the absence of a detailed bug report.

Kaya Saman · #7 11th November 2009, 01:11 PM

Quote:

F12 has gone gold. Official release is on the 17th.
Given your problems, do not upgrade. Do a new install instead. Also, if having any more problems report it on https://bugzilla.redhat.com so it can be addressed quickly and swiftly.

Thanks Nokia for all your responses!!!

Hmm... so looks like F12 is going stable then - that's good to hear!

Ok so you suggest to re-install..... How then can I identify which packages I have in the system??

Something like yum info * >> yum.list I assume?

Quote:

Intel is one of the most Linux-friendly manufacturers out there. Most likely, your errors might be related to some kernel configuration switches kernel guys should tweak in a new manner to address your issue(s). However they can't help in the absence of a detailed bug report.

I have always had issues with Intels of some sort! Mostly with GPU, on Solaris with NIC's

GPU's have wrong res mostly, and also xorg doesn't seem to detect screens either?

Oh well let's hope this get's solved with F12!

Can I quickly ask what the major advantage of F12 is over F11? Just a quick one liner or summary would do of course packages are going to be upgraded.

Nokia · #8 12th November 2009, 12:15 AM

Quote:

Originally Posted by Kaya Saman

Thanks Nokia for all your responses!!!

Hmm... so looks like F12 is going stable then - that's good to hear!

Ok so you suggest to re-install..... How then can I identify which packages I have in the system??

Something like yum info * >> yum.list I assume?

I have always had issues with Intels of some sort! Mostly with GPU, on Solaris with NIC's

GPU's have wrong res mostly, and also xorg doesn't seem to detect screens either?

Oh well let's hope this get's solved with F12!

Can I quickly ask what the major advantage of F12 is over F11? Just a quick one liner or summary would do of course packages are going to be upgraded.

Code:

rpm -qa > rpm-qa
less rpm-qa
wc -l < rpm-qa # To get an idea of haw many packages are installed on your system

For F12 think new Intel drivers and new Xorg...among other added benefits

Kaya Saman · #9 19th November 2009, 04:52 PM

Hi Nokia, thanks for the response and sorry for the late reply things are just a bit nuts right now!!

wc -l < rpm-qa shows:

[code]
# wc -l < rpm-qa
1273
[/quote]

I am guessing now that I have all the installed packages listed in rpm-qa I can simply edit the version and system information out of that file and save it to say rpm-qa-mod.

Then use something like rpm -i << rpm-qa-mod

to re-install all required packages!!

What's your verdict?

Of course something which I do quite often when rebuilding systems is to tar -cf /home/user then untar after full-reinstall so that I don't loose any user information. Then I guess afterwards I will have a complete up to date system!!