Akhirnya setelah sekian lama saya baru sempat ngoprek wifi bcm4312 yang ada di Laptop Lenovo 3000 G410 di OpenSolaris 2009.06, setelah searching dan bertanya kesana kemari saya nemuin tutorial dari teman saya sendiri Rachmat Febrianto. Hmm, pake bahasa inggris nih anak ngblognya, okelah kalo begitu saya tulis saja di blog saya dalam bahasa Indonesia “pikir saya saat ngebaca”. Oke step pertama yang harus kita lakukan adalah download dulu peluru-peluru yang kita perlukan nanti saat installasi driver wifi broadcom menggunakan ndiswraper versi 1.2.3 (ingat: untuk OpenSolaris 2009.06 sebaiknya pake versi 1.2.3 walaupun sudah ada versi yang lebih baru).

Step 1,

Identifikasi dulu sistem yang kita pakai, dengan perintah isainfo :

brokenz@opensolaris:~$ isainfo -v
64-bit amd64 applications
ssse3 cx16 mon sse3 sse2 sse fxsr mmx cmov amd_sysc cx8 tsc fpu
32-bit i386 applications
ssse3 ahf cx16 mon sse3 sse2 sse fxsr mmx cmov sep cx8 tsc fpu

Jika hasilnya seperti diatas maka ikuti langkah berikutnya, namun jika hasilnya seperti ini :

brokenz@opensolaris:~$ isainfo -v
32-bit i386 applications
ssse3 ahf cx16 mon sse3 sse2 sse fxsr mmx cmov sep cx8 tsc fpu

Anda boleh melewati step 2 jika hasilnya seperti diatas.

Step 2,

Edit grub kita dengan menambahkan script ini :

brokenz@opensolaris:~$ pfexec nano /rpool/boot/grub/menu.lst
title OpenSolaris 2009.06
findroot (pool_rpool,1,a)
bootfs rpool/ROOT/opensolaris
splashimage /boot/solaris.xpm
foreground d25f00
background 115d93
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics
module$ /platform/i86pc/$ISADIR/boot_archive
# tambahkan scrptnya di bawah ini

title OpenSolaris 2009.06 32 bit
findroot (pool_rpool,1,a) # angka 1 sesuaikan sendiri
bootfs rpool/ROOT/opensolaris
splashimage /boot/solaris.xpm
foreground d25f00
background 115d93
kernel$ /platform/i86pc/kernel/unix -B $ZFS-BOOTFS,console=graphics
module$ /platform/i86pc/boot_archive

Jika anda lihat sekilas mirip dengan script sebelumnya, yupz memang sama hanya yang membedakan adalah dibaris kernel dan module. Penjelasan lebih lanjut ada disini.

Step 3,

Download driver bcm4312 disini :

Step 4,

Download ndiswrapper versi 1.2.3 disini :

Step 5,

Extrak file bcm4312.tar.gz dan ndiswrapper yang sudah kita download :

brokenz@opensolaris:~$ tar -xvf bcm4312.tar.gz

brokenz@opensolaris:~$ tar -xvf ndis-1.2.3.tar.gz

Step 6,

Copy file bcmwl5.inf dan bcmwl5.sys ke direktori ndis-1.2.3/i386/

brokenz@opensolaris:~$ cp bcm4312/bcmwl5.inf ndis-1.2.3/i386/
brokenz@opensolaris:~$ cp bcm4312/bcmwl5.sys ndis-1.2.3/i386/

Step 7,

Sekarang install paket-paket yang diperlukan :

brokenz@opensolaris:~$ pfexec pkg install SUNWgcc SUNWonbld SUNWflexlex

Note : Untuk proses install paket diatas anda harus koneksi internet

Step 8,

Kita konversi dulu file bcmwl5.inf :

brokenz@opensolaris:~$ cd ndis-1.2.3/i386/
brokenz@opensolaris:~$ iconv -f utf-16 -t ascii bcmwl5.inf > ndis.inf

Step 9,

Kompile file-file diatas :

brokenz@opensolaris:~$ pfexec su -
Sun Microsystems Inc.    SunOS 5.11    snv_111b    November 2008
Script started, file is /var/log/activities/20091122-01:28.00-root.log
root@opensolaris:~# make ndiscvt
root@opensolaris:~# ./ndiscvt -i ndis.inf -s bcmwl5.sys -o ndis.h
root@opensolaris:~# make ndis
root@opensolaris:~# cp bcmndis /kernel/drv/bcmndis
root@opensolaris:~# make ndisapi
root@opensolaris:~# cp ndisapi /kernel/misc

Step 10,

Sekarang load module ndisapi dan attach ke network card kita. Sesuaikan dengan network card anda, ini contoh NIC saya :

root@opensolaris:~# scanpci -v

pci bus 0×0000 cardnum 0×00 function 0×00: vendor 0×8086 device 0×2a00
Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub
CardVendor 0×17aa card 0×383c (Lenovo, Card unknown)
STATUS    0×2090  COMMAND 0×0106
CLASS     0×06 0×00 0×00  REVISION 0×03
BIST      0×00  HEADER 0×00  LATENCY 0×00  CACHE 0×00
MAX_LAT   0×00  MIN_GNT 0×00  INT_PIN 0×00  INT_LINE 0×00
…….

…….

pci bus 0×0004 cardnum 0×00 function 0×00: vendor 0x14e4 device 0x4315
Broadcom Corporation BCM4312 802.11b/g
CardVendor 0×103c card 0×137d (Hewlett-Packard Company, BCM4312 802.11b/g Wireless LAN Controller)
STATUS    0×0010  COMMAND 0×0046
CLASS     0×02 0×80 0×00  REVISION 0×01
BIST      0×00  HEADER 0×00  LATENCY 0×00  CACHE 0×10
BASE0     0xf0000000 SIZE 16384  MEM
BASEROM   0×00000000  addr 0×00000000
MAX_LAT   0×00  MIN_GNT 0×00  INT_PIN 0×01  INT_LINE 0×0a

pci bus 0×0006 cardnum 0×00 function 0×00: vendor 0×14e4 device 0×1713
Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express
CardVendor 0×17aa card 0×3861 (Lenovo, Card unknown)
STATUS    0×0010  COMMAND 0×0046
CLASS     0×02 0×00 0×00  REVISION 0×02
BIST      0×00  HEADER 0×00  LATENCY 0×00  CACHE 0×10
BASE0     0xb8000000 SIZE 65536  MEM
BASEROM   0×00000000  addr 0×00000000
MAX_LAT   0×00  MIN_GNT 0×00  INT_PIN 0×01  INT_LINE 0×0a

root@opensolaris:~# add_drv -i ‘”pci14e4,4315″‘ bcmndis

Step 11,

Sekarang tinggal reboot sistem saja, dan masuk ke pilihan OpenSolaris 2009.06 32 bit :

root@opensolaris:~# reboot

Step 12,

Scan wifi dengan perintah ini :

root@opensolaris:~# wificonfig scan

essid    bssid          type        encryption    signallevel
K23    00:14:bf:24:89:c4 access point    none        12

Sumber : www.rachmatfebrianto.com

I worked 20 hours straight to prepare an old Gateway tower with 280 gig drive for an Ubuntu 9.10 install. The Gateway was hopelessly unbootable in Windows because of some operating system problem (not hardware problem). I realized that I should drop down to C: and type format, to just reformat the entire drive which took about 30 minutes. I forgot that I should have typed FDISK first, to set up the necessary partitions, but it was too late.

I downloaded an ISO image for GNOME partition and burned it to a bootable CD.

I booted the GNOME partition utility. It took me literally hours to guess at what I should do.

Finally I realized that Ubuntu expects THREE partitions. The first is referred to as ROOT but the actual name you give it in the partition process is simpl “/” (forward slash omitting the double quotes).

The second partition will have NO name, but you will designate its format TYPE as swapfile, and that will become the system swap file.
The third partition is called /home.

I had no idea how much space to allocate, so I gave 512 for root and 512 for swap, and the huge remainder for /home.

The software warned me that root and swap were too small. Just for the heck of it, I changed root and swap to 5000, and it worked.

Then it took me dozens of tries installing Ubuntu. I had a 2008 Ubuntu disc and a 9.10 disc I had created last week. Time after time, I would boot from each one, say INSTALL UBUNTU, and it would chug away for a long time, and then die with no messages. FINALLY, but why or how I dont know, the 9.10 unstall brought up an Ubuntu desktop with what looked like all kinds of error messages. There were TWO icons on the desktop which I had never seen before. One said EXAMPLES which I never looked at. I was about to give up in dispair when I decided to click on the icon marked Ubuntu. AS IT TURNS OUT, that is the icon which COMPLETES the install process, and it first brings you into its OWN partition software. I cant exactly remember what I did next. I do remember that GNOME partition utility offered me literally 20 DIFFERENT format types to choose from for each partition (one of which is swap-file). I had no clue what to choose. I did some google searching on my other machine (and you NEED a windows machine attached to the internet to look these things up). I discovered that format type ext3 is good for Debian Linux (and Ubuntu is a flavor of Debian) so I went with ext3.

Finally, I had a working bootable pure Ubuntu 9.10 machine.

My next Sisyphean agony task was to connect it to the Internet. The tower already had an Ethernet card. I was informed that IF I connected a cable from the ethernet to the router, then Ubuntu would automatically sense the ethernet connection and configure it. The ethernet board DID light up and pulse when I connected the cable to my Westell router. But Ubuntu never recognized it. Later I read that only certain ethernet cards will be automatically recognized, so I guess the one in my tower was not a compatible one. My next choice was to try and get my Belkin USB WiFi adapter working. I went to ADMINISTRATION -> SYNAPTIC PACKAGE MANAGER and keyed ndiswrapper into the search. I was prompted to place the Ubuntu install cd into my drive. It kept giving me errors. I placed my Belkin adapter install cd in the drive and looked around for the ini driver file, but could not see it. Finally, out of despair, I plugged the Belkin wifi adapter into the USB and LIKE MAGIC Ubuntu recognized it, asked me to choose a connection and enter the WEP key, which I have now done many times with other machines and during the Wubi Ubuntu install on Windows. So now I had a working Ubuntu machine connected to the Internet.

I went to J&R computer store up the street and found a $10 USB 4 gig memory stick by http://www.dane-elec.com which is REALLY cheap. I recently discovered that the Sancor memory sticks that I love actually have a lot of SOFTWARE on them, which only works under windows, AND if you have a password set on the device, then Ubuntu wont even read it.

I had to go into synaptic manager and search on usb for some installs. Again, it was trial and error, and I dont know what finally made it work, but finally, Ubuntu recognized the memory stick.

TODAY, I had to meet my step-son near at Borders Book Store next to Penn Station. This was lucky for me, because while I waited for him, I browsed the computer book section on the second floor. I found a $9 small Linux handbook reference of commands by Daniel J. Barrett (O Reilly publishers) so I got that to practice all the hundreds of Linux commands that I dont know but need to know.

I browse various books on Ubuntu and Mysql.

I found the key thing I needed to know for my next project, to install LAMP (Linux Apache MySQL PhP) on my new Ubuntu desktop.

All one needs to do is enter TERMINAL, and key in

sudo tasksel

(you will be prompted for your system password next)

A task selection window will pop up with many packages available for install, one of which is LAMP. Now here is a mystery that took me an hour to solve. You can arrow down to highlight LAMP, but you dont have a clue in the world as to how to CHECK it for install. Google revealed the secret: YOU SIMPLY PRESS THE SPACE BAR AND IT IS MARKED CHECKED FOR INSTALL. Then you press ENTER and the install proceeds, Apache, MySQL and PhP. You will be prompted for the MySQL admin password.

Next I wanted to install phpmyadmin to administrate mysql, creating databases, tables, etc. I went to SYSTEM-> Synaptic Manager and searched on phpmyadmin. I think there is only one. BUT HERE IS A SECRET. Once your LAMP install finishes, then power down and boot back up; otherwise, certain files will remain locked by processes and the phpmyadmin install will fail.

Once phpmyadmin installs (and you will again be prompted for that pesky password), then you can open firefox and key in http://localhost/phpmyadmin

You will be PROMPTED FOR A USER NAME AND PASSWORD. This is tricky and confusing. You have to key in the user name “root” without quotes, and then give the password that you have been using all along throughout this. Now you are in phpmyadmin, and you can go to Privileges, and create a new user and give him all possible privileges.

Then, I found a $50 book, also by O’Reilly, entitled
“Head First – PHP & MySQL”. THIS book looks like the perfect way to teach myself how to develop php mysql applications which will have proper security (which is a very complex topic).

I didnt purchase that book tonight, because I wanted to come home and see first if I could successfully install LAMP and phpmyadmin, which I just now finished.

The Head First book gave me links to try the book on line free for 45 days. Money is kind of tight, so I decided to see how far I can go without any additional purchases, but if I get things working, I will buy the book one day. It is interesting that O’Reilly also offers a link to an on line university which can grant degrees in computer science.

I signed up at Oreilly for a trial access of the electronic version of the above-mentioned book.

Here is something I tried which crashed my Ubuntu. I wanted to copy the introduction to the book, from the OReilly site, and PASTE it into an Open Office Document. The first time Open Office died, and the file was shown as requiring recovery. I did the recovery, opened it again with Open Office Document, and then the whole Ubuntu system crashed. I rebooted, and had to go through a long complicated reconstruct procedure. I thought perhaps I would have to install everything from scratch, but fortunately, Ubuntu repaired itself. Moral to story is paste into GEDIT and save, which I guess eliminates whatever hidden characters are in the webpage which cause Open Office to crash the system.

There, I found a link to download all the source code from the book.

I downloaded the zipped file of all the source code.

Next, I went to the source code for chapter 1. They have a beginning version (which I guess you make changes to, and then a final version).

I tried to copy and paste report.html to var/www which is where Apache wants to find pages loaded from local host. I was not allowed to paste because I do not have superuser privileges. So, I went to terminal and typed SUDO GEDIT, which gets me into gedit with super powers, so I can now navigate to the unzipped code in my DOCUMENTS in a special folder I created, open report.html, then do a save as to var/www.

THIS WORKED, because now, when I open Firefox and key in localhost/report , it runs the Chapter 1 example webpage.

FOR MY NEXT TRICK, I must figure out how to copy a chapter 1 tutorial image of a dog (fang.jpg) from the location where it unzipped (in a folder in my Documents) and copy it into var/www where I do not have Admin privileges. SO, I open my OReilly handbook of Linux commands and find the CP command. I open a TERMINAL session and key in SUDO CP which I know will executed it with super admin privileges, but NOW I do not have a clue as to what the PATH names are for the file source and destination.

I am permitted to copy fang.jpg from the unzipped file into DOCUMENTS, just to simplify things.

Using PLACES -> COMPUTER, which brings up the FILE BROWSER, I first navigate to home/Documents and I RIGHT CLICK on the fang.jpg image, and click on PROPERTIES which will SHOW ME that the path is
/home/bryan/Documents/fang.jpg (I use bryan as my user name, but that is my step-son’s name). Next I do the same right click trick on any file which is already in var/www such as report.html, and I discover THAT path, which tells me that the command I should issue in TERMINAL is

sudo cp /home/bryan/Documents/fang.jpg var/www/fang.jpg

BUT IT HANGS… NOTHING HAPPENS.

Then I realize that I should close my other applications, because they are somehow LOCKING UP something that the CP command needs. Sure enough, once I close a bunch of applications, the SUDO CP command asks me for the PASSWORD and then copies fang.jpg to var/www

I can now bring up the image by opening Firefox and typing

localhost/fang.jpg

into the browser address field.

NOW that fang.jpg is in var/www, if I once again open Firefox and type
localhost/report.html

the exercise 1 page loads and also shows the picture of the little dog fang.jpg

I still need to copy report.php and style.css from the place where they unzipped to var/www. Since I can launch gedit with sudo and have superadmin powers, I may open them in that fashion and do a save as.

I ran the finished example, hoping that it would actually send me an email.

I realized that I must examine my php.ini and somehow reconfigure it. I went to some pains to locate that file, but did not post notes as I went, and now I must reconstruct what I did. I still have not succeeded in getting the app to actually send an email through php. But I feel it is more essential for me to move on to other lessons in the HEAD FIRST book.

It was an UTTERLY awesome experience.

I had to redo each and every step of the way about 10 or 20 times, guessing about different tricks, before each stage would work, because there is little documentation, and the intall utilities are not intuitively obvious.

It took a few hours of playing around to realize that Windows was a lost cause.

Then, I tried to install Ubuntu from a CD about 20 times. I then realized I had to drop to drive C: and say FORMAT, and reformat the entire drive.

Then, I remembered too late that I should have first used FDISK, to adjust the PARTITIONS.

So, I burnd an ISO image cd of a linux utility which can repartition the drive. There is little documentation on how to do this. PLUS, you mentioned that your mouse was so old. Well, it was doing weird stuff, like I had to RIGHT click instead of left click. Finally, I switched to the newer usb mouse, and it worked FIND.

I had to try repartitioning the drive about 4 times. FInally I realized from obscure error messages that what it WANTS me to do and NEEDS ME TO do is to create THREE partitions in your 280 gig drive. The first is called ROOT, which makes everything in Linux run, except you simply name it “/” (forward slash, without the quotes).

Root has to be a certain size but not too big. I chose 512 and at the end of the process, it made me go back, saying that was too small, so I made it 5000. The second partition is what is called the SWAP partition. You do not give it a name, but with each partition you are offered 20 different flavors of format. I had to google to learn that ext3 is preferred for Ubuntu/Debian linus. So the second partition you do not name at all, and you choose the type SWAP-FILE, and it automatically makes that your swap file. Then, the third and humungous partion of 200 gig is called /home and is format type ext3. Then you finalize it, and it chugs away formatting and testing the drive.

Next, you put in the Ubuntu install and boot from that. I have a 2008 Ubuntu disk, and one created last week. I tried both of them over and over. They would run 30 minutes and then stop. FINALLY, the recent ubuntu disk actually INSTALLED itself and came up with the Ubuntu desktop, but it had alll sorts of error warning that make me think it had failed. But on the desktop was a strange folder saying INSTALL UBUNTU. Out of curiosity, I clicked on that, and low and behold, that was the part that would finish the install. It dumped me into a different partition utility. Finally, Ubuntu is installed, but no internet connection. I plugged a cable from the router to the ethernet card. I was told by forum members that Ubuntu would just automatically sense the Ethernet card and attach to internet. Didnt work. Then I followed a Youtube tutorial on how to install a Belkin USB adaptor. I did it several times. It didnt seem to work. But then, out of curiosity I plugged in the Belkin to the USB (which I had done earlier and nothing happend). Suddenly, I had internet connection.

Thanks you so much for giving me this machine, and making possible an experience with Ubuntu which I have wanted for several years, but never had a spare machine to take chances with.

ANd this machine is SUPER FAST on the internet, even though it is only a WiFi connection. Ethernet hardwire is supposed to be much faster. Anyway, I will sleep for a couple of hours, and be over in the afternoon to pick up that Mybook for repair.

I feel like superman with this success, or Dante, crawling through all of hell and pergatory, and finally getting a glimpse of Ubuntu heave.

I know I must run to J&R to get another $10 Belkin laser mouse, because your old mouse is so weird. And another belkin wifi adaptor. Then, all we need is a monitor at some point because we have 4 computers and 3 monitors.

Even my headphones and mic work in this Ubuntu. THey would not work on my Wubi install of Ubunu on top of windows.

Also, I am going to buy a cheap $7 memory stick and see how it works. Those sancor have SOFTWARE On them, which makes them more expensive. But the cheap ones are simply USB devices, and should serve my needs.

But your old Gateway was so trashed in Windows, it was hopeless. And now it is brand spanking new with a fresh Ubuntu install, and no viruses, no firewalls, no antivirus overhead. Apparently, Ubuntu is not as susceptible to viruses.

Anyway, thanks and talk to you later, and see you today to pick up that Mybook. I will make it my Holy Grail to retrieve the data, and you will be my Dulcinea, my Beatrice (remember, Quixote, and Dante).

Later !!!

Istället för att installera Eeebuntu på min Eee pc igen så testade jag igår Ubuntu 9.04 “Jaunty”.

Funkade lika bra som Eeebuntu, behövde bara uppdatera kerneln till en nyare så att det trådlösa kom igång. Det tråkiga var att jag med standard drivrutinerna får ca 50% sämre signalstyrka på det trådlösa i Ubuntu jämfört med i Windows XP. Har letat runt lite och en del menar att ndiswrapper, ett “program” till Ubuntu som gör att du kan köra med drivrutiner gjorda för Windows även i Ubuntu, skulle göra signalstyrkan bättre.

Men eftersom ndiswrapper är någon slags “emulator” (om jag fattat rätt) lär väl det istället ta mer på processorns prestanda än om jag kör med “standard” drivrutinerna i Ubuntu.

Så jag tvingas alltså välja mellan: Dålig signalstyrka, normal prestanda. Eller bra signalstyrka, men sämre prestanda. Nu vet jag ju inte säkert om jag förstått allting rätt och jag är som sagt helt ny på Ubuntu och Linux överhuvudtaget så att…

Jag tröttnade iallafall på att försöka lösa problemet, och googla runt i timmar efter svar. Gick heller inte att få ner drivrutiner till nätverkskortet från Atheros. Så jag återställde datorn och sitter nu återigen med Windows XP.

Jag tycker om Windows XP väldigt mycket, och det är inte något jag direkt saknar med det. Duger gott och väl till det jag använder datorn till. Men det hade ändå varit roligt att få igång ett Ubuntu på datorn som fungerar minst lika bra som XP, åtminstone vad gäller prestanda (som t.ex signalstyrkan) så jag kunde testa lite linux. Kan väl hända att det går att fixa på något sätt också, men hade iallafall inte nog med tålamod till det igår.

Kommer säkert att ge det fler försök, men just nu orkar jag bara inte. Känns som att det kan vara ett rätt stort steg att gå över från Windows som man använt sen man typ var foster, till någon linuxdist.

Förresten, om någon kunnig människa har förslag på hur man skulle kunna fixa till det trådlösa nätverkskortets signalstyrka i Ubuntu på en Eee PC 1005HA, så får denna gärna lämna en kommentar;)

Nätverkskortet är ett Atheros AR9285.

A friend of mine use to have Micro$oft Windows XP on his old laptop. Not so bad after all for being 3-4 years old: AMD single core processor – I don’t remember the clock -, 512 MB Ram, A GeForce FX with 64MB dedicated memory… a perfect linux candidate machine. Well, the laptop was at the point that when you turn it on and the system loads you’ve got the time to have a coffee, smoke a sigarette and pee. And when you righ click on “My Computer”… blue screen of death.

So I took the friend’s laptop and I erased everything on it, only saved a couple video and 4GB songs. I installed Ubuntu – much simpler for beginners – and after the Nvidia driver installation graphics were clean, smooth and almost quite fast. Everything worked out-of-the-box… except the wireless card: IPN2220 of my ****.

There was no way to bring it to life using native linux modules so I used windows drivers instead by wrapping them with ndiswrapper.  The step to follow to make this card work are the following:

1. Open a terminal and (assuming you are using a debian based distro)
   
   sudo apt-get install ndiswrapper-utils-1.9 ndiswrapper-common

2. Downlaod the drivers from this link, they worked as a charm for me.
3. Extract archive somewhere, then open a terminal in the location you extracted the files, then
   
   sudo ndiswrapper -i net2200.inf

4. Verify your installation with the command:ndiswrapper -lit should tell you wich drivers are installed and for each one of them if the hardware is found on the system.
5. Now run the following commands to make the module load into the kernel
   
   sudo depmod -a
   sudo modprobe ndiswrapper
   sudo ndiswrapper -m
   
   The last command create an alias on /etc/modprobe.d/ndiswrapper so that the module will automatically load in your kernel at system startup.
6. Run
   
   sudo /etc/init.d/networking restart
   
   to restart your networks. Or just restart the system. Your IPN2220 wireless card should work fine now.

This is all. I have experimented no connection dropouts or slowdowns but if you find something similar let me know

Six.

My new 64-bit slackware is having internet/ndiswrapper problems. Namely, a kernel oops that kills ndiswrapper and in turn, my internet connection, as quickly as 1-10 minutes after bootup.

However, I read this guy seems to be using my current wireless adapter (WUSB600N) with success using open-source drivers! It seems to be the source inside the tarball, so here’s hoping it will compile correctly as 64-bit and work natively.

Update –

Well, I’ve compiled and configured the driver module, and I have good news and bad.

First, I’d like to note that the driver is hardly user-friendly, and requires manual editting of the makefiles before compiling. The regular `make` compile needs to be done as superuser, or else it fails (because it makes files in the root directory), and then the readme asks you to copy a .dat file to /etc/Wireless/RT-something (which means you have to make those directories first). I don’t see the point in copying that file over there yet, anyways, because I insert the module directly from the make’d source.

The good news, however, is that it works! I’m connected to the neighbor’s internet right now. Why, you ask, my neighbor’s internet? Because I kept getting timeouts on my home encrypted network (WEP as far as I remember). This (unsecure) one connected right away, however, which leads me to believe that I configured the makefile incorrectly before compiling. The readme was a little confusing. But, there were two options, so I suppose I’ll just go back and pick the other one, and recompile (hopefully with WEP support this time).

Procedura da terminal:

sux -

Prima password e poi crea la directory con:

 mkdir /lib/windrivers

quindi download del driver Windows per BCM4306 da: http://www.silfreed.net/download/hpzt3000cto/SP23107A.tar.gz ed inserirlo in /lib/windrivers:

 mv PATH_TO_DRIVER /lib/windrivers

Vai alla cartella con i driver:

 cd /lib/windrivers

eseguire

 tar -zxvf NAME_OF_DRIVER.tar.gz
Quindi

 cd NAME_OF_DRIVER

Controlla che non ci siano altri moduli ndiswrapper caricati:

 ndiswrapper -l

In questo caso vanno rimossi:

 ndiswrapper -e NAME_OF_MODULE

Installazione quindi del drivermodule con

 ndiswrapper -i bcmwl5.inf

e carica il modulo con

 modprobe ndiswrapper

Infine Riavvio

J’ai du installer une carte Wifi dans mon pc de bureau, j’avais une carte Wifi Netgear mais bien sur pas de driver Linux…

La solution se trouve avec Ndiswrapper mais le driver fourni est un exécutable et impossible de l’extraire avec les outils habituels.

J’ai donc rusé, je vous explique comment :

1) Installer Wine

2) Installer Ndiswrapper

3) récupérer le driver *.exe

4)En console taper :

wine /chemine/vers/votrefichier.exe

5)On cherche le driver ayant l’extension *.INF avec find :

find /home/votrelogin -name *F -print

6) Installation du pilote, on se déplace dans le bon répertoire

ndiswrapper -i nomdufichier.INF

Puis on vérifie la bonne installation du driver

ndiswrapper -l

Installation en tant que module

ndiswrapper -m

On régénère les dépendances entre les modules

depmod -a

7) Enfin connectez-vous avec Wicd ou NetworkManager

Je précise que j’ai fais l’installation sous Archlinux mais elle est certainement valable pour les autre distributions

O procedimento que descrevo a seguir foi realizado em um notebook Acteon modelo M-5 com placa wi-fi modelo Realtek 8187b e funcionou maravilhosamente bem. Creio que também deve funcionar em versões mais recentes do Kubuntu.

1) Desabilite o wi-fi usando as hotkeys. No meu caso: Fn + F10. No notebook, o led (a “luzinha”) que indica o uso do wi-fi deve ficar apagado.
2) Instale o ‘ndiswrapper’ a partir do repositório.

Existem 2 formas fáceis de se instalar o ‘ndiswrapper’:

OPÇÃO 1 (se o pc ou notebook ainda não está conectado à internet por meio de cabo):

a) Clique no botão ‘Menu K’ na extremidade esquerda da barra de tarefas.
b) Vá em ‘Sistema’ > ‘Gerenciador do Adept’.
c) Coloque o cd do Kubuntu no cd-rom.
d) No ‘Gerenciador do Adept’ vá no menu superior e clique em ‘Adept’ > ‘Gerenciar repositórios’. Isso fará abrir a janela ‘Software sources’. Clique na aba ‘Thirdy-Party software’ e marque o quadradinho ao lado de ‘cdrom:[Kubuntu 8.04_Hardy Heron_ – Release…’ (tc, etc, etc…).OBS: se a sua versão do Kubuntu for diferente o texto também o será. O importante é selecionar a opção ‘cdrom’.
e) Feche a janela ‘Software sources’.
f) Ainda no ‘Gerenciador do Adept’ vá no campo ‘Busca’ e digite ‘ndiswrapper’ (sem as aspas). Deve aparecer os seguintes pacotes:
ndiswrapper-common
ndiswrapper-utils-1.9
g) Clique sobre o ‘ndiswrapper-utils-1.9′ e, em seguida, no botão ’solicitar instalação’ que surgirá logo abaixo.
h) Vá na barra de ferramentas, na parte superior da janela, e clique em ‘Aplicar mudanças’.
i) Aguarde a instalação e o ‘ndiswrapper’ já estará pronto para ser utilizado.

OPÇÃO 2 (se o pc ou notebook já está conectado à internet por meio de cabo):

a) Clique no botão ‘Menu K’ na extremidade esquerda da barra de tarefas.
b) Vá em ‘Sistema’ > ‘Gerenciador do Adept’.
c) No ‘Gerenciador do Adept’ vá no campo ‘Busca’ e digite ‘ndiswrapper’ (sem as aspas). Deve aparecer os seguintes pacotes:
ndiswrapper-common
ndiswrapper-utils-1.9
d) Clique sobre o ‘ndiswrapper-utils-1.9′ e, em seguida, no botão ’solicitar instalação’ que surgirá logo abaixo.
e) Vá na barra de ferramentas, na parte superior da janela, e clique em ‘Aplicar mudanças’.
f) Aguarde a instalação e o ‘ndiswrapper’ já estará pronto para ser utilizado.

Após a instalação do ‘ndiswrapper’ vamos voltar ao procedimento:

3) Baixe os drivers realtek 8187 do site da Realtek ou simplesmente digite a partir do terminal:
wget ftp://202.65.194.212/cn/wlan/RTL8187B_driver_only.zip
4) Após baixar o driver, extraia o arquivo zipado.
5) Abra o terminal (digitando: Ctrl + F2) e, dentro do mesmo, vá para o diretório aonde vc extraiu os drivers.
6) Entre com seguintes comandos:
sudo ndiswrapper -i net8187b.inf
sudo ndiswrapper -m
sudo ndiswrapper -ma
sudo ndiswrapper -mi

7) Habilite o wi-fi usando as mesmas teclas hotkeys do passo 1. No meu caso: Fn + F10.
8.) Reinicie o computador.

9) Vá na barra de tarefas e clique com o botão direito do mouse sobre o ícone do Network-Manager (ao lado do ícone do alto-falante). Vai abrir uma janela ‘KNetworkManager’. Clique em ‘Configuração manual’. Na aba ‘Interfaces de rede’ selecione ‘wlan0′ e clique no botão ‘Configurar interface’.
10) Na janela que se abre ‘Configurar Dispositivo wlan0′ na opção ‘Endereço TCP/IP’ selecione ‘Automático’ e ‘DHCP’. Marque o quadradinho ‘Ativar quando o computador iniciar’.
11) Ainda na mesma janela ‘Configurar Dispositivo wlan0′ no ítem ‘Configuração da rede Wireless’, se vc souber do que se trata coloque o ESSID, Chave WEP (a senha para conectar à rede sem fio) e o tipo de chave. Se não souber esses dados ainda, deixe esses campos em branco. Em seguida clique em ‘OK’.
12) Após voltar para a janela ‘Configurar – Módulo de Controle do KDE’. Clique em ‘OK’.
13) Vá mais um vez até a barra de tarefas e clique com o botão direito do mouse sobre o ícone do ‘NetworkManager’. A essa altura já deverá estar visível a barra de sinal (na cor azul) da rede ou redes que estiverem ao alcance do seu desktop ou notebok.
14) Clique com o botão ESQUERDO do mouse sobre a rede na qual vc quer conectar.
15) Espere a conexão ser completada.

Daí então é só correr pro abraço!

Um abraço e boa sorte!

Benneh Carvalho (SemPirataria.wordpress.com)

Esta dica é para aqueles que adquiriram o adaptador wireless Linksys WSB11 V4.0, para saber o chipset dele basta rodar o comando:

$ lsusb

Vai aparecer o resultado:

Bus 002 Device 002: ID 13b1:000b Linksys WUSB11 v4.0 802.11b Adapter

Baixe o último Ndiswrapper 1.55 e instale o build-essential para compilar o Ndiswrapper:

$ sudo apt-get install build-essential

Entre na pasta que vc baixou o ndiswrapper-1.55 pelo terminal e descompacte:

$ tar -xzvf ndiswrapper-1.55.tar.gz

$ cd ndiswrapper-1.55

$ sudo make

$ sudo make install

Baixe o driver do adaptador:

ftp://ftp.linksys.com/pub/network/WUSB11v4_08272004.exe

Caso o link da Linksys esteja inoperante, use o CD de instalação que vêm com o adaptador, pois nele está o .exe para extrair os arquivos .inf e .sys como mostrado mais abaixo.

Instale o cabextract e unzip:

$ sudo apt-get install cabextract unzip

Entre na pasta onde salvou o driver do adaptador e descompacte o .exe.

$ cabextract WUSB11v4_08272004.exe

Ou usando o unzip:

$ unzip WUSB11v4_08272004.exe

Quando descompactar surgirão dois arquivos importantes, um .inf e um .sys, nessa pasta onde estão esses dois arquivos vc instala o .inf com o ndiswrapper rodando o seguinte comando:

$ sudo ndiswrapper -i wusb11v4.inf

Confira se ele foi instalado com:

$ sudo ndiswrapper -l

Se aparecer driver “present” ele foi instalado.

Refaça os módulos com:

$ sudo depmod -a

Suba o ndiswrapper no módulo com:

$ sudo modprobe ndiswrapper

Reinicie a máquina e rode o comando:

$ iwconfig

Se aparecer a interface wlan0 seu adaptador já está instalado, é só configurar a conexão com o WICD de preferência.

Boa Sorte!

NDISwrapper es un envolvedor de controladores open source, que permite el uso de la mayoría de las tarjetas inalámbricas en el sistema operativo Linux utilizando la APIs del kernel de Windows, enlazando de forma dinámica el controlador de Windows a esta implementación.

Este proyecto es de gran importancia ya que muchos fabricantes no distribuyen controladores para Linux en sus tarjetas inalámbricas.

Para instalar NDISwrapper en fedora 11 hacemos lo siguiente:

$ yum install ndiswrapper akmod-ndiswrapper

Posteriormente debes buscar el driver de windows en el cd que obtuviste al comprar la antena wifi (OJO: debe ser el driver correspondiente a la arquitectura de tu pc, es decir, si tu computador tiene sólo un procesador ocupas el driver para 32 bits; si tu computador tiene doble procesador ocupas el driver para 64 bits. Debes tener mucho cuidado con esto puesto que si ocupas el driver incorrecto no funcionará tu wifi aunque realices todo el procedimiento correctamente)

También recuerda que puedes buscar el driver para tu antena wifi en la página oficial del fabricante.

Además ten presente que los drivers en windows tienen extensión .inf, por lo que tu driver tendrá por nombre algo como: driver.inf

Una vez tengas claro cuál es el driver que necesitas lo copias en tu home y siempre como root, ejectutas el siguiente comando:

$ ndiswrapper -i /home/tucarpeta/driver.inf

Con ese comando el driver debió instalarse o cargase en el sistema, para comprobar esto ejecutas el siguiente comando:

$ ndiswrapper -l

Te debería mostrar qué driver está actualmente cargado, si dice algo como driver no cargado o driver no encontrado es porque cometiste algún error al cargar el mismo, si esto ocurre fíjate en el directorio dónde está el driver e indica bien dónde se encuentra este al momento de cargarlo, este es un error muy común.

Para cargar el módulo al sistema ejecuta:

$ depmod -a

$ modprobe ndiswrapper

Luego configuras modprobe para que se cargue ndiswrapper cuando la interface de la tarjeta wireless este activada:

$ ndiswrapper -m

Por último configuras para que al arrancar el sistema cargue ndiswrapper, para ello abres y editas el archivo /etc/modules:

en gnome:

$ gedit /etc/modules

en KDE:

$ kwrite /etc/modules

Añades ndiswrapper al final del archivo, guardas los cambios, cierras, reinicias y ahora debería funcionar tu tarjeta wifi.

A continuación algunas interfaces gráficas que sirven para manejar ndiswrapper de forma más fácil

ndisgtk

http://jak-linux.org/projects/ndisgtk/

Allí vas a la sección de paquetes para RedHat y descargas el paquete rpm que te sirva.

NdisInstaller

http://sourceforge.net/projects/ndisinstaller/

Para este programa no encontré paquetes rpm así que tendrías que compilar.

kndiswrapper

http://sourceforge.net/projects/kndiswrapper/

Este es un GUI (interfaz gráfica) que ocupa Qt por lo tanto es para KDE. Al parecer tampoco tiene paquete rpm para fedora por lo que tendás que compilarlo.

Saludos.

Bugün Pardus 2009 depolarına mod-ndiswrapper paketinin eklendiğini gördüm. Hemen işlemlere koyuldum ve kurulum için konsoldan

ndiswrapper -i TUSB1150.INF

ndiswrapper -l

modprobe ndiswrapper

echo “ndiswrapper”>> /etc/modules.autoload.d/kernel-2.6

komutlarını sırası ile vererek kurulum işlemini tamamladım ve şuanda da kablosuz bağlantı üzerinden yazıyı yamaktayım. Kurulumun 2008′ den hiç bir farkı yok. Pardus 2009 gümbür gümbür geliyor. Bu kadar kararlı bir Alfa sürüm inanılması çok zor ama gerçek. Geliştiricilerin emeklerine ve ellerine sağlık.

Esta cuestión me surge a raiz de un post que leí hace unos dias en untuxsuelto y que a su vez venía de linuxadictos.
Para contestar me basaré en el único factor objetivo, en mi propia experiencia

Primeramente he de retroceder unos cuantos años en el tiempo, justo hasta cuando empecé a estudiar este mundillo. Por aquel entonces el único sistema operativo que había era ms-dos, todo era a base de comandos y todo era aprendértelos y saber como usarlos.
¿Era dificil? claro que si, y mucho, pero éra lo único que había asique no quedaba otra.

Con el paso del tiempo llegaron las versiones gráficas de aquel sistema operativo, llamadas Windows donde todo era mucho más sencillo, rara vez se utilizaban los comandos y todo era a base de doble clicks del ratón.
Las versiones fueron evolucionando, y no entraré en si fueron a peor, se fueron simplificando, sobre todo para los usuarios con pocos conocimientos y era lo que el mercado pedía, todo el mundo quería un ordenador y que llevase un sistema operativo bonito y que no fuese muy complejo.
Además contaban con el apoyo de todas las compañías importantes de hardware que tenían controladores certificados para todos sus componentes.
¿Que más se podía pedir?

Pero la evolución siguió su curso y basándose en unix aparecieron las primeras versiones de linux, un sistema operativo sólido pero poco vistoso porque se volvía a los comandos.

Como no interesaba vender equipos con éste sistema operativo, porque no era tan lucrativo y era más complicado, se estandarizó y pupularizó Windows como sistema operativo único en los equipos de sobremesa.

Y ahora llego a la segunda parte, mis pasos en linux.
Mis primeros acercamientos fueron puramente autodidactas, me descargué varias distros y quise instalarlas. Ahí ya me surgieron los primeros problemas, las particiones del disco duro. Teniendo la referencia de Windows, ésto se me complicaba mucho más porque hay que asignar varias particiones con distintos tamaños y me encontré desbordado. Pero bueno, como era un sistema operativo que era experimental para mi y en aquellos momentos no ofrecía mucho interés, se quedó en una anécdota, una espinita de un intento que no resultó.

Pero poco a poco ese sistema operativo también se fué simplificando y gracias a distros como ubuntu fué haciéndose más familiar y llegando hasta más manos.
Yo, llamado por la curiosidad y por el afán de aprender, hice un curso y decidí ponerme nuevamente manos a la obra.

Instalé una distro de ubuntú y gracias a mis escasos conocimientos y al gran abanico que ofrece internet, fuí logrando instalar programas, cambiarle el aspecto gráfico al entorno y en definitiva, a poder manejarme en el entorno linux de una manera básica.

El gran reto me llegó hará unos quince dias, cuando un amigo me trajo su equipo para que se lo mirase porque le iba muy lento. Cuando encendí el equipo y ví la cantidad de virus, troyanos y spyware que albergaba ni me pensé que después de apagarlo ipso facto iba a empezar el típico proceso de formateo y reinstalación, pero me embarqué en algo más arriesgado.
Mi amigo me comentó que ese equipo solamente lo utilizaba para bajarse cosas de internet, que usaba el emule, el utorrent y poco más. Como no tenía datos que salvarle pero sí tiempo de por medio, decidí que era una buena manera de poner en práctica mis conocimientos y poder desmitificar el oscuro mundo linux.

Le instalé la última versión de ubuntu y lo primero que hice al terminar la instalación fue arremangarme y ponerme a pelear con la tarjeta wireless y ndiswrapper. Pero cual fué mi sorpresa cuando ví que la había reconocido automáticamente, bien.
Una vez hecho esto, todo se volvió más sencillo, con conexión a internet, le instalé el soporte para el idioma, actualicé el sistema, le instalé el Amule, el azureus y algunas otras mejoras que encontré en esta guia.
Cuando terminé y comprobé que los programas que iba a utilizar funcionaban sin problemas, le llamé, se lo comenté y algo asustado vino a por él.
Desde entonces, cada vez que hablamos, me dice que está encantado, que va mucho más rápido y mejor que antes.

Por lo tanto, después de semejante repertorio, llego a la respuesta de la pregunta del enunciado.
¿Linux es dificil? SI
Pero claro, es en este momento cuando se tiene que valorar si vencer esa dificultad merece la pena o no.

Our sprints are on a day-to-day basis, but the list of activities are given at the start of the week. For our first sprint week, we’re assigned to work on the following: study the framework, create a trac, report on the status of each functionality for a particular module of the DMS, and populate the database with real data.

Similar to a test matrix, a trac serves as bug tracker, minus the listing of the visible controls in each window dialog. A trac is made up of tickets, which define very specific errors or enhancements. For database population, we’re given Excel files, which need to be converted to SQL statements. We’re thinking of exporting them into csv files and parsing them using C#.

As for the demo unit, we were asked earlier to put a Wireless LAN Adapter on it. Since, there’s no available Linux driver for the particular adapter that we have (SURECOM EP-9321-g/g1 802.11g 54M WLAN PCI Adapter), our workaround was to get one for Windows and install it using Ndiswrapper. While it can already detect network connections, it still has problems establishing an actual connection. The proposal is already due on May 10 and we only got ’til Friday to work on the demo unit so we really need to hustle.

Mounted WLAN PCI Adapter

Due to these things, I haven’t had much progress in Sharepoint. However, since .NET is also the framework which DMS is built on, I get to be familiarized more with the said framework.

-Anna

I have recently switched over from MS vista to Ubuntu. Since I bought my Dell inspiron laptop with OEM installed OS, I could not change the disk size in Windows Vista. If you have also bought a laptop with OEM installed operating system, then, you cannot do more partitions unless, you format the entire disk again and start from the scratch. Precisely, this is what I did. I used windows vista recovery disk ,and used DISKPART.exe to create new partitions; and again installed MS vista on primary partition.

Pernah punya pengalaman setelah menginstall ubuntu atau distro linux lainnya WiFi Card anda tidak terdetect? padahal di windows berjalan dengan baik? Coba gunakan ndiswrapper untuk mengatasi masalah tersebut. Tool Ndiswrapper ini sangat berguna apabila WiFi Card anda tidak dapat terdeteksi di sistem linux. Dengan Ndiswrapper anda dapat menggunakan driver WiFi Card Windows yang disertakan dalam CD penjualan. Berikut cara penggunaannya:

1. Install paket ndiswrapper-common dan ndiswrapper-utils menggunakan Synaptic atau dari terminal ketikkan; $ sudo apt-get install ndiswrapper-common ndiswrapper-utils
2. Pada terminal, masuk ke folder tempat anda menyimpan windows driver wifi card (jika masih di CD copykan terlebih dahulu ke harddisk), cari file yang berekstensi .inf/.INF,
3. kemudian ketikkan perintah; $sudo ndiswrapper -i [nama_driver].INF
4. Untuk melihat driver yang telah terinstall dengan benar di sistem ketikkan perintah;  $sudo ndiswrapper -l
5. Selanjutnya masukkan ndiswrapper ke dalam modul agar dapat diload ketika booting pertama kali dengan perintah; $sudo ndiswrapper -m
6. Untuk menghindari konflik dengan driver bawaan pada Ubuntu (kadang hal ini terjadi), Non-aktifkan driver bawaan Ubuntu tersebut dengan memasukkannya kedalam   /etc/modprobe.d/blacklist.
7. Restart komputer anda untuk melihat perubahan

]]> http://maurosc3ner.wordpress.com/2009/03/09/ubuntu-810-sobre-cq50-la103/ Mon, 09 Mar 2009 21:36:25 +0000 maurosc3ner http://maurosc3ner.wordpress.com/2009/03/09/ubuntu-810-sobre-cq50-la103/

Hola, despues de mi falta de tiempo en febrero para postear, me reivindicare posteando unos tips (tutorial) sobre tener linux apunto en esta maquina del demonio (cq50), agrego que no habia visto maquina mas rara para manejar los dispositivos que esta, todo porque maneja las irq de forma diferente.

Bueno para que nuestro ubuntu arranque y no nos bote kernel panic al inicio, simplemente en la pantalla de opciones para instalar o probar el S.O, apretamos la tecla F6, y agregamos en la linea de comandos lo siguiente:

all_generic_ide

acpi=off

con estas opciones ya podremos probar o instalar en nuestra maquina sin mayores problemas el S.O, hasta ahora estos pasos son necesarios en ubuntu, ya que en fedora y opensuse corre sin problemas debido a que incluian de fabrica una version del kernel mas nueva.

Una vez hayas completado la instalacion, lo normal es que no tengas ni la tarjeta grafica (Geforce 8200m) ni la tarjeta wifi (atheros) funcionando, para la grafica pues procedemos a actualizar la lista del aptitude, descomentando los repositorios comentados:

repositorios:

$nano /etc/apt/sources.list

actualizando el aptitude:

$sudo apt-get update

Ahora …

procedemos a instalar el envy (bella herramienta de un gra colaborador) que nos instala de forma facil e intuitiva el driver de la tarjeta grafica y reiniciamos:

instalacion de envy en gnome:

$sudo apt-get install envyng-gtk

instalacion de envy en kde:

$sudo apt-get install envyng-qt

Ya es hora de proceder con nuestra wifi, es importante decir que tenemos muchos metodos para hacerlo (madwifi,ndiswrapper), pero como se trata de hacerlo lo mas facil posible pues me decidi por el ndisgtk, dicha aplicacion es un modo grafico sencillito del ndiswrapper, donde solo necesitamos nuestro driver en windows de la tarjeta wifi y solo es agregar el .inf y reiniciar:

instalar ndisgtk:

$sudo apt-get install ndisgtk

y con esto tenemos nuestro portatil totalmente funcional en ubuntu 8.10

Espero les haya gustado y obviamente bienvenidas las correcciones.

Mas Informacion | UbuntuForums

I’ve just come off #fedora..

This is what I was helping out with.. Installing ndiswrapper on a machine without access to the internet..

What a PAIN!!

Hunt mirrors for the packages matching the kernel.. Then , there are deps that also need to be downloaded..

Go search for them , more mirrors..

Ask the person on the other side to get them.. Never happens in the first try.. Today it took 3 attempts to successfully install ndiswrapper..

All this while youve got to be careful that the deps etc are right, and that the right files have been downloaded, at the other end.. Ndiswrapper had 3 files needed. I found two of them on the mirrors and one using RPMbone.. It’s taken me time before.. Today it took almost TWO hours to help this guy set it up..

The only thing that’s worth this war is the satisfaction that you get when you get this, “It works!! “

Guess that’s how we work.. lol.. cheers all..

How to get your wifi working on an atheros card:

I have an acer aspire 4720z laptop with an Atheros AR5BXB63 wireless network card. Although Ubuntu 8.10 shows this hardware driver for Atheros based 802.11 wireless LAN cards it wasn’t able to help me get it working.
So i tried Madwifi as an option. Here although it got my card detecting and connecting to networks it used to give awfully slow speeds almost to the point of disconnection.
Then i finally tried to install ndiswrapper which wasn’t as difficult as i had thought.
I followed the following tutorial from ubuntuforums:

http://ubuntuforums.org/showthread.php?t=512828

I will be recapping the whole tutorial in respect of the steps i took which were essentially the same:
First of all make sure you have another alternative to get your Internet working as in an Ethernet cable. Only then can this tutorial prove helpful.
Once that’s done you would need two packages:

1. ndiswrapper package
2. atheros package

First get onto the desktop with the following command:

cd Desktop
(Easier to keep track of where all the files are)

The following two commands will get you the tarballs of the two packages:

Ndiswrapper(1.51):
wget http://wifix.sourceforge.net/software.php?title=ndiswrapper

AR5007EG windows drivers:
wget http://blakecmartin.googlepages.com/ar5007eg-32-0.2.tar.gz

Extract both the archives onto the desktop with the following:

tar xvf ndiswrapper-1.51.tar.gz
(the actual name of the file will depend on the version you have downloaded)

tar xvf ar5007eg-32-0.2.tar.gz

After this is done you will get two folders with the same names as the archives. Now you need to see if your system’s up-to-date with its kernel headers and packages for compiling:

First get your kernel version by :

uname -r

Whatever you get you need to fill that in the subsequent [INSERT] field.

sudo aptitude update

sudo aptitude install linux-headers-[INSERT] build-essential
or
sudo aptitude install linux-headers-$(uname -r) build-essential

The above two commands will download and install headers and it won’t be a very small download for the linux headers.
After this we need to blacklist the ath_pci kernel module in the blacklist file present in /etc/modprobe.d folder under the filesystem:

echo “blacklist ath_pci” | sudo tee -a /etc/modprobe.d/blacklist

To see the appended line just open the file in any of the text editors like gedit:

gedit /etc/modprobe.d/blacklist

Now cd into the ndiswrapper folder that was created after extracting:

cd ndiswrapper-1.51

Now compile:

sudo make uninstall
make
sudo make install

cd.. (Back to Desktop)

cd ar5007eg-32-0.2

sudo ndiswrapper -i net5211.inf

The net5211.inf can also be used by an application called Windows wireless Drivers to make it installed.

Once this is done, we need to make sure that ndiswrapper is loaded in the startup of ubuntu:

sudo modprobe ndiswrapper

Now open the modules file:

sudo gedit /etc/modules

And append ndiswrapper at the end of the file. My file now look like this:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with “#” are ignored.

fuse
lp
sbp2
ndiswrapper

It’s all done!
Now simple restart your system and hopefully it will work. The LED wasn’t working for me so remember whether your wifi is on or not.

After about ten installs, much research and effort, I’ve given up. I understand that Apple lacking behind in accepting Linux, or there are not enough people out there who want to develop Linux for Apple computers.

The installation of Ubuntu on my Macbook was very smooth of course, it’s the drivers that hit me hard. rEFIt makes it really easy to boot into Linux, it also makes the boot screen customizable, so you can change those crappy looking images. Notable things during installation for me were:

• Making a partition with Boot Camp,
• Choosing “Use the Largest Continuous Free Space” option for Linux setup,
• Making sure to install GRUB to the partition and not the MBR, as the installation would do automatically.

Attaining drivers became a problem, especially the wireless driver. Ndiswrapper and FWCutter turned out to be very unreliable and did not function to their purpose for me. I am looking for an alternative solution, a better solution too. Hope someone figures out a driver for Apple computers. Furthermore, the trackpad and keys were not supported, so they were a bit fragile in performance.

To ease the displeasure, I am using a nice wallpaper on my Mac OS, which I am content with, no doubt.

All in all, can’t wait to write my own drivers and run Linux where ever I wanted. (Or, others to get busy and write some.)