Archive for September 10th, 2009

Some priceless wireless stuff & my switch from wireless ipw3945 driver to iwl3945, how to make iwl3945 driver work much more decent

Thursday, September 10th, 2009

Since I upgraded to the latest Debian unstable I was forced to switch from the good old ipw3945 wireless driver to the newer one with which I had a bunch of unpleasent experienced, that was a good reason for me to kept myself back to the ipw3945. Anyways all my attempts to port the already 2 years old ipw3945 without a development to my 2.6.30-1-amd64 left void.Therefore I had to unwillingly switch to the iwl3945 driver. To do so I had to:
1. edit /etc/modprobe.d/00local.conf and remove the line

install iwl3945 /bin/true

2. edit /etc/modprobe.d/blacklist.conf and comment the line

blacklist iwl3945

3. edit /etc/modprobe.d/ipw3945.conf and comment out
install ipw3945 /sbin/modprobe –ignore-install ipw3945 ;
sleep 2 ; /sbin/ipw3945d –quiet
remove ipw3945 /etc/init.d/ipw3945d modprobe-stop && modprobe -r –ignore-remove ipw3945
4. edit /etc/udev/rules.d/70-persistent-net.rules and comment out
SUBSYSTEM==”net”, DRIVERS==”ipw3945″, ATTR{address}==”00:1c:bf:bd:24:59″, ATTR{type}==”1″, NAME=”wlan0″SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:1c:bf:bd:24:59″, ATTR{type}==”1″, KERNEL==”wlan*”, NAME=”wlan0″
5. Last but not least:
rmmod iwl3945; modprobe iwl3945;

That so far was required to switch from ipw3945 to iwl3945.

Unfortunately after the switch I was pretty unhappy of the behaviour of the iwl3945 driver.
Like for example the driver won’t detect many of the wireless networks during scan compared to the one detected by the old ipw3945 driver.
I googled and found in Google many contradictions considering which driver (ipw3945 or iwl3945) prooves to be better. Some praised ipw3945 and tended to hold unto it while others were proclaiming that iwl3945 works in a much better manner.
Again some Googling and thinking over the created problem led me to a website which suggsted a helpful tip on how to intialize
the iwl3945 driver. That tip IMPROVED A LOT! the scanning behaviour of the iwl3945 driver.
Here is the tip itself:
Edit /etc/modprobe.d/iwl3945.conf and add to it the following: alias wlan0 iwl3945# the line below disables iwl3945 wireless driver hardware scanningoptions iwl3945 disable_hw_scan=1# extend the network channels detected to 13options lbm_cw_cfg80211 ieee80211_regdom=EU

After all is done the only left thing is to:
reload the iwl3945 driver
rmmod iwl3945modprobe iwl3945
And Hooray! It works Again! You will notice now much more networks are being detected
and apart from that scanning returns results every time you scan for wireless networks
To conclude the post I’ll say a few words on the line:
options lbm_cw_cfg80211 ieee80211_regdom=EU
as well as explain briefly about wicdMany of you would wonder what is that about, well it’s about that on how many channels
would wireless networks be detected. For example in the European Union wireless networks
could be configured to work on channels up to 13, just to compare in the USA less channels
are available thus the default behaviour of the iwl3945 driver is not to detect wireless
networks on channels above 10 (I believe?). The above example communicates to the cfg80211 kernel
module that more wireless channels are available since we’re in the EU (European Union).
For kernels below version 2.6.24 you might need to use the variable:
options lbm_cw_cfg80211 ieee80211_regdom=EU instead of the one I add above.

.Well let me conclude the post with some handy wireless manager I use some time ago.
Longly I (suffered) with Gnome’s default gnome-network-manager, nevertheless it’s proven thatpain doesn’t waste forever.
Mine would not too:

I Googled just to know if there are Good alternatives to gnome-network-manager and I found the nifty Wicd manager. Which behaviour I like much more than the classicwifi-radar or gnome-network-manager.
This days I heavily use the nice Wicd peace of soft.
So in case if you still don’t have it installed on your GNU/Linux go for it!
If you want to give some credits for this I hope helpful post please give them to God :)END—–

Debian (Unstable) Squeeze / Sid /usr/lib32/alsa-lib/libasound_module_pcm_pulse.so linked to missing libraries

Thursday, September 10th, 2009

While playing with my installed programs on my recently updated Debian I stepped into a problem with /usr/lib32/alsa-lib/libasound_module_pcm_pulse.so. It seems the library was linked to two non-existing libraries: /emul/ia32-linux/lib/libwrap.so.0 as well as /emul/ia32-linux/usr/lib/libgdbm.so.3. A temporary solution to the issue is pointed out in Debian of the Debian Bug reports . As the report reads to solve that it’s required to:

1. Download libwrap0_7.6.q-18_i386.deb and libgdbm3_1.8.3-6+b1_i386.deb.

2. Extract the packages:dpkg -X libwrap0_7.6.q-18_i386.deb /emul/ia32-linux/dpkg -X libgdbm3_1.8.3-6+b1_i386.deb /emul/ia32-linux/

3. echo /emul/ia32-linux/lib >> /etc/ld.so.conf.d/ia32.conf

4. Execute /sbin/ldconfig

5. Check if all is properly linkedExecute ldd /usr/lib32/alsa-lib/libasound_module_pcm_pulse.so|grep -i “not found”Hopefully all should be fixed now.

Debian Squeeze / Sid ( Unstable ), Skype 2.0.0.72 and pulseaudio fix microphone and sound issues

Thursday, September 10th, 2009

After I’ve recently upgraded to the latest current Debian Unstable release I stumbled upon many problems, many of which are discussed and fixes provided on the prevoius posts. One of the many terrible things I had to fix MANUALLY (I’m starting to hate that word), are the issues with sound and microphone in Skype. I’m using Skype 2.0.0.72, because skype_static-2.1.0.47 gives me worries, crashing every now and then. To fix my problems with sound and microphone while Googling I found this nice Aryn’s Blog post .
Here is what worked for me to fix the issues.
Execute1. apt-get install libsdl1.2debian libsdl1.2debian-alsa libsdl1.2debian-pulseaudio2. apt-get install libsdl1.2debian-pulseaudio3. apt-get install paprefs pavucontrol padevchooserNext 4. open gnome-alsamixer and make sure your “Mic” is not muted (in some cases it might be some capture field muted ain’t sure?)5. Start pavucontrol and make sure in the Input Devices the mute button is not selected6. Go to the gnome panel System -> Preferences -> Sound and make sure in the Input menu Microphone is not muted7. start aumix and Make sure your Microphone is “Mic” and “Igain” is not set to low volume8. Execute: alsactl store to make sure that alsa settings are not lost on system restart9. In your home directory edit ~/.asoundrcAnd add— SNIP —pcm.card0 { type hw card 0}ctl.card0 { type hw card 0} —–10. Edit /etc/libao.conf and make sure it contains default_driver=pulse11. Edit ~/.profile and add: export SDL_AUDIODRIVER=pulse to it12. Open Skype go to “Sound Devices” and set sound in, sound out and ringing options to:HDA Intel (hw:intel,0)
If you’re lucky with God’s help and grace your skype’s sound output and input via mic should be working just fine :)END—–

Ubuntu 9.04 (Jaunty) on Toshiba Satellite L40 14B ACPI problem ACPI loading problem and workaround

Thursday, September 10th, 2009

As you have noticed in my previous posts I'm playing a bit with Toshiba Satellite L40 14B updates this days. I've came across an ugly problem with ACPI on Ubuntu Jaunty. It's really a big issue because acpi stalls and keeps loading the system on 100% leaving it with 0% idle all the time. The solution I’ve found is suggested on the following Ubuntu bug launchpad . As it describes the solution comes to this:

1. rm -f /etc/acpi/events/asus-wireless-on

2. rm -f /etc/acpi/events/asus-wireless-2

the next two steps are added by meto prevent some problems caused by acpidupgrades.

3. touch /etc/acpi/events/asus-wireless-2

4. touch /etc/acpi/events/asus-wireless-on

Enable Ctrl + Alt + BackSpace in Ubuntu Jaunty (9.04)

Thursday, September 10th, 2009

The current latest stable version of Ubuntu 9.04 Jaunty. Does have the same annoying issue as in the latest Debian Unstable. What I mean is Ctrl + Alt + BackSpace doesn’t work anymore. So people who has since the early days of linux get used to that just like man gets used to food, get seriously annoyed by that. The fix to the problem is explained on UbuntuGeek’s website . There are a couple of approaches man could partake. The most common especially is ubuntu is to install the small proggie:
dontzap and use sudo dontzap –disable . Another possible solution is to directly edit /etc/X11/xorg.conf and enable the feature directly to the Xorg server.
If you want that edit the xorg.conf file and add:

Section ServerFlagsOption DontZap “false”EndSection
Have phunEND—–

Ubuntu 9.04 Restoring the Shut Down entry to the System Menu

Thursday, September 10th, 2009

After upgrade of Ubunto to Jaunty (9.04) release, I came across an annoying issue. The System menu on the gnome-panel is missing the “Log Out” and “Shutdown Entries”. I’ve red in Google in ubuntuforums where discussion emerged about the topic. It seems that this missing entries are not a bug but a feature in this release of Ubuntu. To simply restore back the entries it’s necessery to remove the fast user switcher from the panel. Here is a link to a blog describing the whole problem and what is causing it Ubuntu 9.04 restoring the Shut Down entry to the System menu END—–

Safely upgrade Ubuntu 8.04 (Hardy Heron) to 8.10 (Intrepid Ibex)

Thursday, September 10th, 2009

I’ve used the following Ubuntu 8.04 to 8.10 upgrade tutorial to safely upgrade ubuntu to Intrepid Ibex (8.10). The only thing that seemed a bit broken on the first view is splashy which seemed not to show up properly anymore.END—–