Queste sono le differenze tra la revisione selezionata e la versione corrente della pagina.
| karmic_on_hp_pavilion_tx2500 2010/01/09 09:22 | karmic_on_hp_pavilion_tx2500 2010/06/13 07:06 versione corrente | ||
|---|---|---|---|
| Linea 1: | Linea 1: | ||
| **My experience with an HP Pavilion tx2500 and karmic.** | **My experience with an HP Pavilion tx2500 and karmic.** | ||
| - | Please tell me if you find errors, missing information or a "more institutional" wiki to host this page: toobaz [at] email [dot] it. | + | Please tell me if you find errors, missing information or a "more institutional" wiki to host this page: me [at] pietrobattiston [dot] it. |
| ====== General info ====== | ====== General info ====== | ||
| Linea 35: | Linea 35: | ||
| exit $? | exit $? | ||
| - | |||
| - | |||
| ====== Thermal sensors ====== | ====== Thermal sensors ====== | ||
| The dsdt of the BIOS (I have no idea of what it is) is flawed, and thinks only Windows is eligible to access it; while under Jaunty the problem could be solved by following [[https://wiki.edubuntu.org/LaptopTestingTeam/HPdv5z|this procedure]], now because of (non-) [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/395239|bug 395239]], the procedure stopped working. | The dsdt of the BIOS (I have no idea of what it is) is flawed, and thinks only Windows is eligible to access it; while under Jaunty the problem could be solved by following [[https://wiki.edubuntu.org/LaptopTestingTeam/HPdv5z|this procedure]], now because of (non-) [[https://bugs.launchpad.net/ubuntu/+source/linux/+bug/395239|bug 395239]], the procedure stopped working. | ||
| The "solution" is probably to recomplile the kernel, but I didn't try. | The "solution" is probably to recomplile the kernel, but I didn't try. | ||
| + | |||
| + | The real solution would be that HP releases a fixed BIOS. I already wrote to the support asking for it, but with no chance. Some owner of a laptop still covered by warranty may have a better luck. | ||
| ====== Audio ====== | ====== Audio ====== | ||
| Linea 46: | Linea 46: | ||
| A temporary solution is to run "sudo killall slmodemd" in a terminal. A permanent one, if you don't use the modem, is to disable the "SmartLink modem daemon" driver at all. | A temporary solution is to run "sudo killall slmodemd" in a terminal. A permanent one, if you don't use the modem, is to disable the "SmartLink modem daemon" driver at all. | ||
| - | |||
| ====== Wireless ====== | ====== Wireless ====== | ||
| - | In "Hardware Drivers" (System -> Administration -> Restricted Drivers), just enable the "wl" driver. | + | I followed the procedure described in [[https://bugs.launchpad.net/ubuntu/+bug/208183|launchpad bug 208183]], namely: |
| + | |||
| + | * download the driver from HP website (I took it from [[http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-76368-1&lc=en&dlc=it&cc=it&lang=it&os=228&product=3747931|here]]), it's called "sp36684.exe" | ||
| + | * run it with wine : "wine sp36684.exe" | ||
| + | * always click "next", until the installer crashes | ||
| + | * install ndisgtk, run it: "sudo ndisgtk" | ||
| + | * click "install new driver" | ||
| + | * browse to /home/yourusername/.wine/drive_c/SWSetup/SP36684A and select "bcmwl5.inf" | ||
| + | |||
| + | **Warning**: if you enable the driver in "Hardware Drivers" (System -> Administration -> Restricted Drivers), which is the proprietary driver developed by Broadcom for Linux, it //will// work reasonably, but you will occasionally experience (depending on the wireless networks, I think) important slowdowns when resuming from suspend, frequent losses of wireless functionality, and also occasional freezes. Moreover, it seems to me that the signal strenght is better with ndiswrapper, but this //may// be just my sensation. | ||
| ====== Touchscreen ====== | ====== Touchscreen ====== | ||