Bug 13478 - [P4M900] [HP 2133] resolution problem starting X with the wlan network controler activated
Summary: [P4M900] [HP 2133] resolution problem starting X with the wlan network contro...
Status: CLOSED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: i386 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_i386
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-07 20:44 UTC by MarMarAba
Modified: 2012-06-08 11:42 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.28-11-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description MarMarAba 2009-06-07 20:44:05 UTC
[It is a copy of the bug https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/355918. Follow the link for more details]

--------------------------------------------------------------

My computer is a HP 2133 netbook (FU353EA), with a wlan network controller BCM4312. It has an interrupt to activate/deactivate radio activities (wlan and bluetooth) and the maximum screen resolution accepted by the monitor is 1024x600.

So the problem is these one: if I boot up my computer whit the radio activities deactivated the X server works perfect, and when starts I can see all the area of de desktop, it's normal... but if I boot up the system with the radio button activated the X server detects the maximum resolution of my screen like 1366x768 and some area of the desktop is positioned out of the screen limits.

A description of the situation can be looked in the next schema:

(You should see the "image" commented at C style /* */ in a uniform-width font, like Courier or similar)

/*

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-----------
|···············································*·········|
* These area limited by asterisks is the ·······*·········|
|···············································*·········|
* portion of desktop that is can see············*·········|
|···············································*·········|
*···············································*·········|
|···············································*·········|
*···············································*·········|
|···············································*·········|
|···············································*·········|
|···············································*·········|
* (1024x600)····································*·········|
|************************************************·········|
|These other area is the area of desktop which is·········|
|outside of my screen limits. The X server manages the····|
|area but I can't see it.·································|
-----------------------------------------------------------
            (1366x768)

*/

But at the other hand, if there is no driver (proprietary driver or ndis driver through ndiswrapper) installed on the system the resolution gets correctly but if there is some driver installed the resolution gets wrong.

I hope that you understand the exact problem, it is very strange, and I had very surprised when I noticed the bug...

Good luck.

I had temporally solved the bug with a script which install the ndiswrapper driver for my network card in /etc/rc.local.

I am not exactly sure if the problem comes from the Xorg, but it is very probable that the X server is miss-interpreting the screen model.

[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:0364]
     Subsystem: Hewlett-Packard Company Device [103c:3030]
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01)
     Subsystem: Hewlett-Packard Company Device [103c:3030]
Comment 1 Thomas Gleixner 2009-06-09 18:06:56 UTC
> But at the other hand, if there is no driver (proprietary driver or
> ndis driver through ndiswrapper) installed on the system the
> resolution gets correctly but if there is some driver installed the
> resolution gets wrong.

We can not do anything about interaction between a closed source
driver and the rest of the system.

Which wlan chipset is in that machine ?

Thanks,

	tglx
Comment 4 Bartosz 2009-06-19 12:48:33 UTC
The chipset is Broadcom Corporation BCM4312, and I think it uses bcmwl driver.

The source code is available at:
https://launchpad.net/ubuntu/karmic/+source/bcmwl/5.10.91.9-3

Note You need to log in before you can comment on or make changes to this bug.