Moblin 2.1 WiFi Hp Mini 110-1020nr

Well I just bought my first netbook last night and I am proud to say the OS that shipped with it never had a chance to boot on it. I initially tried to load the Hp MIE Linux but to no avail. I'm not sure what the problem is -- it would hang somewhere around 25% through the boot sequence.

Anyways, I moved on pretty quickly to Moblin (v2.1). Everything works perfectly with the exception of the WiFi. Fortunately for me, there is another fellow who developed a work-around for his Dell Mini 9 that uses the same chipset as my new netbook.

His method can be seen here:

http://slaine.org/_slaine/Dell_Mini_9.html

Thanks Glen!

UPDATED 23 NOV 09:

In case slaine decides to take down his post for whatever reason here is a copy of the instructions of his site -- again this is all his work, I'm just re-posting for ease-of-access:

1. 1)Activate the moblin toolbar and select the applications icon
   

2. 2)Choose the Accessories section and select Terminal
   

3. 3)Install the various tools you’ll need
   

sudo yum install rpmdevtools

4. 4)Install the compilers and other tools,
   

sudo yum groupinstall “Development Tools”

5. 5)Install the kernel-netbook-devel package.
   

sudo yum install kernel-netbook-devel

6. 6)Now we’re ready to build and install the new broadcom drivers
   

wget http://slaine.org/files/moblinv2/wl-kmod-5.10.91.9.3-1.moblin.src.rpm

(This build will download the broadcom driver archive directly from their site)

rpmbuild --rebuild --target=i586 wl-kmod-5.10.91.9.3-1.moblin.src.rpm

7. 7)Install the resulting rpm,
   

sudo rpm -ivh ~/rpmbuild/RPMS/i586/wl-kmod-5.10.91.9.3-1.moblin.i586.rpm

Webcam on Linux Mint (Ubuntu) Quick and Easy

With thanks to binselam of Ubuntu Forums, I was able to get my webcam working in no time flat. Below is his post originally located on Ubuntu Forums.


November 20th, 2006
binselam
5 Cups of Ubuntu
Join Date: Nov 2006
Beans: 15
Thanks: 0
Thanked 0 Times in 0 Posts

[How to] Logitech Quickcam IM/Connect webcam on Kubuntu 6.10 (Edgy Eft)
I have been trying to install Logitech Quickcam IM/Connect webcam on Kubuntu 6.10 (Edgy Eft). So, I have searched the ubuntuforms and how-to's. Although, what I have found in both sites was very helpful, but it was not specific to my webcam and step by step approach. I wanted to contribute to community by posting this.

I followed the ubuntu-community`s Spca5xx documentations and Yoriko post with little modifications.

It worked for me. I hope this helps you.



STEP 1: First, I have used lsusb to find out:
1) Vendor Id and Product ID
2) to see do I have usb support, and check the driver files for device support. The supportted device list is available at the Michael Xhaard's homepage ("http://mxhaard.free.fr/ ").

This list shows the lsusb result.
Bus 001 Device 005: ID 046d:08d9 Logitech, Inc.
Bus 001 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical


STEP 2: Download latest Spca5xx source code to your home directory from Michael Xhaard's homepage. At the time of writing this installation guide, the latest source code version was spca5xx-20060501.
NOTE: There might be a newer version of the driver by the time you install. Please check the web page :" http://mxhaard.free.fr/ ".
Latest driver is:gspcav1-20070508.tar.gz (swejuggalo indicated that works fine on Ubuntu 7.04). Make sure you substitue correct driver name in the following steps, if you use a different driver.
(You can see the instructions for the new driver in following post: http://ubuntuforums.org/showthread.p...09418#poststop).

cd ~
wget http://mxhaard.free.fr/spca50x/Downl...01.orig.tar.gz


STEP 3: Become root. To do that, you need to open a terminal window and enter following command(Please enter user password when it is prompted. In each terminal window, you just need to enter sudo
command and password once (for the first time).

sudo -s
Password:########

Note: Prompt should change to: root@yourmachine:


STEP 4: Download the necessary packages. The following packages are needed from the Ubuntu repositories for compiling.
1. linux-headers-`uname -r`
2. linux-restricted-modules-`uname -r`
3. build-essential

uname -r
Identifies the version of running kernel. Exp: 2.6.17-10-generic

apt-get install linux-headers-`uname -r` linux-restricted-modules-`uname -r` build-essential


STEP 5: Compile the spca5xx source code. The linux stuff (drivers/programs) is installed under /usr/src. The downloaded driver files need to be placed to proper directory under linux. So, please type following commands to change directory, move downloaded source files, unpack the source files and change into directory. (NOTE: This step assumes you downloaded the driver file to your home directory.)

cd /usr/src
mv ~/spca5xx-220060501.orig.tar.gz .
tar xfvz spca5xx-20060501.orig.tar.gz
cd spca5xx- 20060501


STEP 6: Set the environment variable CC for spac5xx Makefile. In my case, Ubuntu Edgy Eft uses gcc 4.1 as kernel compiler. (NOTE: your system might use gcc-4.0. if you use version gcc4.0, you need to modify the command as "export CC=gcc-4.0" So, please make sure of your compiler version.)

export CC=gcc-4.1


STEP 7: Set a link back to source code(headers).

ln -s /usr/src/linux-headers-`uname -r` /lib/modules/`uname -r`/build

STEP 8: Now, we need to compile spca5xx source code, remove the old driver(from memory and hard drive), install the new driver and load the new driver. Please enter the following commands in the order given.

make
modprobe -r spca5xx
rm -rf /lib/modules/`uname -r`/kernel/drivers/usb/media/spca5xx*
make install
modprobe spca5xx

If everything went accordingly, there should be no error messages. When you type dmesg, you should get something like shown above.

[17191980.272000] usbcore: deregistering driver spca5xx
[17191980.276000] drivers/media/video/spca5xx/spca5xx-main.c: driver spca5xx deregistered
[17192035.756000] Linux video capture interface: v1.00
[17192035.768000] /usr/src/spca5xx-20060501/drivers/usb/spca5xx.c: USB SPCA5XX camera found. Logitech QC IM/Connect
[17192035.768000] /usr/src/spca5xx-20060501/drivers/usb/spca5xx.c: [spca5xx_probe:5480] Camera type JPEG
[17192036.860000] /usr/src/spca5xx-20060501/drivers/usb/zc3xx.h: [zc3xx_config:558] Find Sensor HV7131R(c)
[17192036.872000] /usr/src/spca5xx-20060501/drivers/usb/spca5xx.c: [spca5xx_getcapability:1765] maxw 640 maxh 480 minw 176 minh 144
[17192036.872000] usbcore: registered new driver spca5xx
[17192036.872000] /usr/src/spca5xx-20060501/drivers/usb/spca5xx.c: spca5xx driver 00.60.00 registered
root@eagel:/usr/src/spca5xx-20060501#


GOOD LUCK!
_____________

rsync - Once again why Linux is better.

Linux has this little easy command called rsync. Basically what it did for me today was went through all the music on my computer, compared it with the saved music on my external hard drive, and then copied anything over to the external that wasn't already there.

See, I use my laptop to listen to music and when I get a new cd I put it on my laptop. But then I need to make sure my external is keeping a good/up-to-date backup of all my music in case something happens to my laptop.

Thanks to linuxquestions.com I found a quick and easy way to do that with rsync.

The command I used was:

rsync -avuz /home/awesome/Music/ /media/My\ Book/My\ Music/
(laptop music dir) (ext. music dir)


rsync is the command.
"a" option archives the files to the new directory
"v" verbose?
"u" update - this causes it to skip files that are newer on the destination - that way you don't copy old info over new info (in my case this is a "just in case")
"z" compresses files during data transfer - to speed transfer


Wow, that's excellent.

Kopete Does Everything, Even Google Talk

Here are instructions on how to add you Gmail google talk account into Kopete. Yes it's awesome.

Kopete: Access Google Talk

Thanks to Tech-Recipes for this awesome little HowTo.

Powered by ScribeFire.

Media in OpenSuSE 10.2

Awesome how to:

http://suseforums.net/index.php?showtopic=36351

Peace.

Even Microsoft's mice are stupid!

For some reason the forward and back buttons on my Microsoft Intellimouse don't automatically work with my OpenSuSE 10.2 distro. So all you do to fix this is:

edit /etc/X11/XF86Config

and add a line under this section:

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "Name" "Microsoft IntelliMouse Optical"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7" #ADD THIS LINE
EndSection


Also, just as a small side note. Be sure to save a backup of XF86Config before making any changes so you don't mess something up and have to reinstall your OS (speaking from personal experience).

And I bid you all - a good day.

Wireless on OpenSuSE 10.2 with Broadcom

Once again fighting the good fight and trying to get this chipset to work properly with OpenSuSE 10.2.

As always thanks to this skittle loving guy's website: http://nextgen.no-ip.org/~andrew/linux/ndiswrapper/ndiswrapperinfo-gui.php for not only explaining the process but having an explanation that was even specific to OpenSuSE 10.x (and in my case 10.2).

In addition to his instructions I would add not to use ndisgtk, just run the commands manually (as superuser of course):
'ndiswrapper -i bcmwl5a.inf'
'modprobe ndiswrapper'
And furthermore I took these steps to not only ensure a working card, but also have it accurately show link/signal quality and load at boot:
edit /etc/modprobe.d/ndiswrapper and add change 'wlan0' to 'eth1'
and
edit /etc/init.d/network adding 'modprobe ndiswrapper' somewhere in the beginning

**Added 14Aug07*** Make sure to configure the wireless device in YaST. Do not use the pre-configured card, make a new wireless device.

I will also mention that when I list installed ndiswrapped windows drivers I do get this annoying output: ndiswrapper -l
bcmwl5a : driver installed
device (14E4:4318) present (alternate driver: bcm43xx)

However as far I as can tell it seems to make no difference what-so-ever. In addition, I tried to correct this output by blacklisting 'bcm43xx' to which my computer said it was then 'ignoring blacklist rule bcm43xx' or something that effect. So whatever.

Do I absolutely now how what I did affected my computer? Absolutely not. Does my wireless start at boot and work with accurate link/signal quality? Yes.

Correction...

On my last post I mentioned how quote "Linux working = No money for MS". Due to recent news I should now post a correction.

Because the machine I was posting about is using OpenSUSE (by Novell) and Novell was just bought out by Microsoft then my logic no longer stands.

Let's now go with: Non-Novell Distro's of Linux working = No money for MS.

Thanks to Eric for his copy of The Wall Street Journal's article publicizing the whole event.

Did I mention I was only like 4 or 5 months late on this story?

WTF.

Seriously, WTF?

I decided to try using ndiswrapper to get my wireless working on my openSUSE 10.2 machine. Pain in the ...

It works, but for some god-forsaken reason it thinks the wireless card is an ethernet card and shows it as eth1 vs. wlan0.

To install the driver and use ndiswrapper I followed this gents page. Very nice page, excellent info, but it doesn't say one thing about having to reboot your computer to have it recognize your wireless card (which of course is true in my case). You should be able to just modprobe ndiswrapper as far as I understand. WTF. Then I followed some other helpful fellow's instructions on using bcm43xx-fwcutter in order to get my Broadcom wireless card to show up as wlan0 -- no dice. I even blacklisted bcm43xx in /etc/modprobe.d/blacklist (I think that's it) as another gent had mentioned still to no avail!

OpenSUSE vs. Broadcom -- Broadcom wins. OpenSUSE got in some excellent blows by being able to actually connect to the net, but Broadcom dominated the battle by never submitting to wlan0. Hope you didn't have money riding on that fight.

Whatever...

I'm so tired of screwing with it that as long as I have wireless I don't care. As far as I'm concerned I win.

The transitive property: a=b=c so a=c. My version:

Linux working = Not using MS Windows which = MS doesn't get my Money
so...
Linux working = No money for MS

Hooray for Linux. Job well done.