Description of problem: In Openchrome SVN 740, which was used for the build of Fedora's package is a bug, that causes a conflict with b43 module. After using DPMS or Standby it is not possible to connect to any WLAN. Version-Release number of selected component (if applicable): 0.2.903-6.fc10 How reproducible: ever Steps to Reproduce: 1. connect to WLAN 2. go to standby 3. Actual results: no connection to WLAN Expected results: Connection to WLAN Additional info: There is a patch avaibiale: http://openchrome.org/trac/attachment/ticket/288/openchrome_741_hp_2133.patch I compiled this one against SVN 751, which seems to work.
Only the first half of the patch is correct and has been committed. The second one is wrong. I'm a bit surprised you say svn rev. 751 works, but anyway I'll push a new build soon.
Thank you. Please let me know, as soon I can download builds from koji. I will test it then. (slightly off-topic): Maybe a new build will work also in F11. I do not know -that's why I did not write a bug report yet- GNOME crashes after few minutes of use. The processes/apps continue to work, but you are not able to move any windows or change to another one. I am not sure, if openchrome is responsible for this. Might be interesting to test though. I was also suprised to see, that rev. 751 was succesfully compiled because I tried a few days earlier in F11 without success.
F-10 : http://koji.fedoraproject.org/koji/taskinfo?taskID=1424035 F-11 : http://koji.fedoraproject.org/koji/taskinfo?taskID=1424031 Rawhide : http://koji.fedoraproject.org/koji/taskinfo?taskID=1424023
xorg-x11-drv-openchrome-0.2.903-11.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.903-11.fc11
xorg-x11-drv-openchrome-0.2.903-7.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.903-7.fc10
I tested the new build in F-10. It is ok now, to use standby/hibernate, but not to log off (and relogin). The moment you log off, the conflict occurs again (see attached kernel traces). The only solution is to reboot then. But defenitly an approvement to the build before.
I reinstalled my own builded and patched driver. There logoff/login as well standby/hibernate do work.
Created attachment 348647 [details] kernel trace after logoff from X 2.6.29
Created attachment 348648 [details] kernel trace after logoff from X 2.6.27 looks identical to mee
I did also a test in F-11. Same results as in #6. Additional problem: Openchrome starts with 174 dpi, which results in awfully large fonts. When use gnome-display-manager to set i.e. to 96, everything is ok.
I was not able to test an own and patched driver within F-11, due I was not able not to build it here: In Datei, eingefügt von via_driver.h:78, von via_accel.c:42: /usr/include/GL/glxint.h:28:19: Fehler: GL/gl.h: Datei oder Verzeichnis nicht gefunden In file included from via_driver.h:78, from via_accel.c:42: /usr/include/GL/glxint.h:95: Fehler: expected specifier-qualifier-list before »GLboolean« make[3]: *** [via_accel.lo] Fehler 1 make[3]: Leaving directory `/root/trunk/src' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/root/trunk/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/root/trunk' make: *** [all] Fehler 2 I tried rev. 751 as well 747. I choose last one, because I know from Ubuntu's launchpad that 747 was succesfully build for Jaunty which also has the new X.Org. Additional info. In F11 there even with new build the issue described in #2. X also behaves very strange when log in in GDM: After clicking on the desired username you do not see the input field for the password. That is independent from the dpi-level. In earlier build you were also not able to see options to set another language, keyboard layout and window manager. This became with the new build possible. I hope, these descriptions help somehow. Currently F-11 is unusable on an HP 2133 (openchrome is not the only issue, there is also some problem with sound).
(In reply to comment #11) > I was not able to test an own and patched driver within F-11, due I was not > able not to build it here: > yum-builddep xorg-x11-drv-openchrome (In reply to comment #10) > I did also a test in F-11. Same results as in #6. > This is expected, F-10 and F-11 spec and patches are exactly the same. > Additional problem: Openchrome starts with 174 dpi, which results in awfully > large fonts. When use gnome-display-manager to set i.e. to 96, everything is > ok. Could you please provide the full xorg log ?
Created attachment 348727 [details] Xorg.0.log after 174 dpi Sometimes gdm presents itself with 174 dpi, sometimes with 96 which is the setting in gnome-display-properties. After this start of X it hat 174 dpi.
Created attachment 348728 [details] Xorg.0.log after 96 dpi here with 96. both logs were take from the same driver build
Now I was able to build the driver within F11. I used again rev 751 and applied the patch. Results are -again without surprise as decribed earlier (#6) concerning the break of WLAN connections: Standby as well log off/relogin possible. Yet, it is interessting to note, that my own build did not crash the window manager (at least not until now). Usually it was sufficent to open some apps and play a litte bit around with them. Now I haven dozends apps open and nothing happend so far. But also my build shows the described strange behaviour at the gdm screen.
xorg-x11-drv-openchrome-0.2.903-7.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-openchrome'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-6806
xorg-x11-drv-openchrome-0.2.903-11.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-openchrome'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6855
Can you confirm or not the package currently in updates-testing does fix the wireless issue ? I'm not sure from your comments above.
xorg-x11-drv-openchrome-0.2.903-12.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.903-12.fc11
xorg-x11-drv-openchrome-0.2.903-8.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.903-8.fc10
xorg-x11-drv-openchrome-0.2.903-12.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-openchrome'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7851
xorg-x11-drv-openchrome-0.2.903-8.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-openchrome'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-7859
xorg-x11-drv-openchrome-0.2.903-12.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
xorg-x11-drv-openchrome-0.2.903-8.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.