| 2009-04-05 23:36:10 |
MarMarAba |
bug |
|
|
added bug |
| 2009-04-05 23:36:10 |
MarMarAba |
attachment added |
|
uname, dmesg, Xorg.logs and more info http://launchpadlibrarian.net/24847314/resolution_problem.tar.gz |
|
| 2009-04-05 23:39:37 |
MarMarAba |
description |
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)
/*
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-------------
| * |
* Este es el área de escritorio que yo veo... * |
| * |
* Limitado por los asteriscos * |
| * |
* * |
| * |
* * |
| * |
* * |
| * |
* (1024x600) * |
|*********************************************** |
|Este es el área de escritorio que queda fuera de |
|mi pantalla. El servidor X lo gestiona pero no aparece |
|dentro de los márgenes de la pantalla |
-----------------------------------------------------------
(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. |
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)
/*
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-----------
| * |
* Este es el área de escritorio que yo veo... * |
| * |
* Limitado por los asteriscos * |
| * |
* * |
| * |
* * |
| * |
* * |
| * |
* (1024x600) * |
|*********************************************** |
|Este es el área de escritorio que queda fuera de |
|mi pantalla. El servidor X lo gestiona pero no aparece |
|dentro de los márgenes de la pantalla |
-----------------------------------------------------------
(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. |
|
| 2009-04-05 23:45:15 |
MarMarAba |
description |
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)
/*
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-----------
| * |
* Este es el área de escritorio que yo veo... * |
| * |
* Limitado por los asteriscos * |
| * |
* * |
| * |
* * |
| * |
* * |
| * |
* (1024x600) * |
|*********************************************** |
|Este es el área de escritorio que queda fuera de |
|mi pantalla. El servidor X lo gestiona pero no aparece |
|dentro de los márgenes de la pantalla |
-----------------------------------------------------------
(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. |
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. |
|
| 2009-04-09 19:10:39 |
Bryce Harrington |
attachment added |
|
Xorg.0.log.incorrect-resolution http://launchpadlibrarian.net/25135883/Xorg.0.log.incorrect-resolution |
|
| 2009-04-09 19:13:11 |
Bryce Harrington |
affects |
xorg (Ubuntu) |
xserver-xorg-video-openchrome (Ubuntu) |
|
| 2009-04-09 20:10:06 |
Bartosz Kosiorek |
bug watch added |
|
http://www.openchrome.org/trac/ticket/289 |
|
| 2009-04-09 20:10:06 |
Bartosz Kosiorek |
bug task added |
|
openchrome |
|
| 2009-04-09 20:15:23 |
Bug Watch Updater |
openchrome: status |
Unknown |
New |
|
| 2009-04-10 17:22:19 |
MarMarAba |
attachment added |
|
dmesg.log http://launchpadlibrarian.net/25217234/dmesg.log |
|
| 2009-04-10 17:22:45 |
MarMarAba |
attachment added |
|
lspci-vnvn.log http://launchpadlibrarian.net/25217238/lspci-vnvn.log |
|
| 2009-04-10 17:23:32 |
MarMarAba |
attachment added |
|
uname-a.log http://launchpadlibrarian.net/25217251/uname-a.log |
|
| 2009-04-10 17:24:05 |
MarMarAba |
attachment added |
|
version.log http://launchpadlibrarian.net/25217269/version.log |
|
| 2009-04-10 17:26:38 |
MarMarAba |
attachment added |
|
Xorg.0.log.correct-resolution http://launchpadlibrarian.net/25217333/Xorg.0.log.correct-resolution |
|
| 2009-04-10 19:16:59 |
MarMarAba |
attachment added |
|
Xorg.0.log.incorrect-resolution http://launchpadlibrarian.net/25219999/Xorg.0.log.incorrect-resolution |
|
| 2009-04-11 15:24:45 |
MarMarAba |
attachment removed |
uname, dmesg, Xorg.logs and more info http://launchpadlibrarian.net/24847314/resolution_problem.tar.gz |
|
|
| 2009-04-20 21:57:52 |
Bryce Harrington |
xserver-xorg-video-openchrome (Ubuntu): status |
New |
Confirmed |
|
| 2009-04-21 22:25:39 |
Bryce Harrington |
description |
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. |
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]
|
|
| 2009-06-04 18:56:55 |
Bartosz Kosiorek |
summary |
resolution problem starting X with the wlan network controler activated |
[P4M900] resolution problem starting X with the wlan network controler activated |
|
| 2009-06-07 18:06:31 |
Bartosz Kosiorek |
bug task added |
|
linux (Ubuntu) |
|
| 2009-06-07 18:07:01 |
Bartosz Kosiorek |
summary |
[P4M900] resolution problem starting X with the wlan network controler activated |
[P4M900] [HP 2133] resolution problem starting X with the wlan network controler activated |
|
| 2009-06-07 18:27:18 |
fuy |
removed subscriber fuy |
|
|
|
| 2009-06-09 11:36:02 |
Bartosz Kosiorek |
bug task added |
|
linux |
|
| 2009-06-15 08:12:00 |
Bartosz Kosiorek |
bug task added |
|
bcmwl (Ubuntu) |
|
| 2009-06-15 08:18:20 |
Bartosz Kosiorek |
bug watch added |
|
http://bugzilla.kernel.org/show_bug.cgi?id=13478 |
|
| 2009-06-15 08:18:20 |
Bartosz Kosiorek |
linux: importance |
Undecided |
Unknown |
|
| 2009-06-15 08:18:20 |
Bartosz Kosiorek |
linux: status |
New |
Unknown |
|
| 2009-06-15 08:18:20 |
Bartosz Kosiorek |
linux: remote watch |
|
Linux Kernel Bug Tracker #13478 |
|
| 2009-06-15 21:04:48 |
Bug Watch Updater |
linux: status |
Unknown |
Confirmed |
|
| 2009-06-19 12:41:00 |
Bartosz Kosiorek |
xserver-xorg-video-openchrome (Ubuntu): importance |
Undecided |
Low |
|
| 2009-06-19 12:41:51 |
Bartosz Kosiorek |
xserver-xorg-video-openchrome (Ubuntu): status |
Confirmed |
Triaged |
|
| 2009-06-20 19:11:30 |
Bartosz Kosiorek |
attachment added |
|
openchrome_741_hp_2133.patch http://launchpadlibrarian.net/28149428/openchrome_741_hp_2133.patch |
|
| 2009-07-09 12:29:55 |
Bartosz Kosiorek |
attachment added |
|
openchrome-switch-on-lvds-pads-only-for-active-channels.patch http://launchpadlibrarian.net/28846195/openchrome-switch-on-lvds-pads-only-for-active-channels.patch |
|
| 2009-07-09 14:29:14 |
fuy |
removed subscriber fuy |
|
|
|
| 2009-07-20 12:58:29 |
Jayden |
attachment added |
|
Xorg log with openchrome 758 revision http://launchpadlibrarian.net/29280580/Xorg.0.log |
|
| 2009-09-03 15:42:37 |
Jayden |
attachment added |
|
Xorg.0.log http://launchpadlibrarian.net/31276811/Xorg.0.log |
|
| 2009-09-11 12:31:27 |
Bartosz Kosiorek |
attachment added |
|
panel_unify.patch http://launchpadlibrarian.net/31651815/panel_unify.patch |
|
| 2009-09-12 12:01:51 |
Jayden |
attachment added |
|
Xorg.0.log http://launchpadlibrarian.net/31717100/Xorg.0.log |
|
| 2009-09-16 16:04:32 |
Bartosz Kosiorek |
linux (Ubuntu): status |
New |
Invalid |
|
| 2009-09-16 16:07:15 |
Bartosz Kosiorek |
bcmwl (Ubuntu): status |
New |
Invalid |
|
| 2009-09-16 16:21:27 |
Bartosz Kosiorek |
bcmwl (Ubuntu): status |
Invalid |
Won't Fix |
|
| 2009-09-21 11:50:49 |
Bartosz Kosiorek |
attachment added |
|
via_panel.c http://launchpadlibrarian.net/32150116/via_panel.c |
|
| 2009-09-21 11:58:53 |
Bartosz Kosiorek |
attachment added |
|
panel_resolutions.patch http://launchpadlibrarian.net/32150308/panel_resolutions.patch |
|
| 2009-09-21 12:00:15 |
Bartosz Kosiorek |
attachment removed |
via_panel.c http://launchpadlibrarian.net/32150116/via_panel.c |
|
|
| 2009-09-21 20:46:55 |
Bartosz Kosiorek |
linux: status |
Confirmed |
Invalid |
|
| 2009-09-22 07:46:27 |
Bartosz Kosiorek |
xserver-xorg-video-openchrome (Ubuntu): assignee |
|
Bartosz (gang65) |
|
| 2009-09-22 08:22:06 |
Bug Watch Updater |
openchrome: status |
New |
Fix Released |
|
| 2009-09-22 11:28:54 |
Bug Watch Updater |
linux: status |
Invalid |
Confirmed |
|
| 2009-09-22 17:08:54 |
Bartosz Kosiorek |
xserver-xorg-video-openchrome (Ubuntu): status |
Triaged |
In Progress |
|
| 2009-12-21 22:45:00 |
Bartosz Kosiorek |
xserver-xorg-video-openchrome (Ubuntu): status |
In Progress |
Fix Released |
|
| 2011-02-04 12:42:26 |
Bug Watch Updater |
linux: importance |
Unknown |
Medium |
|
| 2012-06-09 11:18:32 |
Bug Watch Updater |
linux: status |
Confirmed |
Expired |
|
