Hello everybody.
I'm trying to install Puppy on my EeePC 1015PEM. Everything works just fine, except the wireless network adapter. If I'm not mistaken, my adapter is BCM4313. According to this page, the Broadcom 802.11 Linux STA driver should work. I've downloaded it from here and used tgz2pet to convert it to a .pet file and install it. It installed fine, but the wireless adapter was still not detected. I then downloaded the Windows driver from Asus at the EeePC 1015PEM driver download page, extracted the Windows XP files to a folder, and used ndiswrapper to open the .INF file. The module loaded successfully, but it's still not detected.
Backtrack r5(my main OS) detects it just fine. So does Puppeee 4.4.
Is there a way I can copy the working drivers from Puppeee 4.4 to Puppy 5.2.8? Otherwise, what steps can I take to fix my issue?
I would greatly appreciate any kind of help.
-EDIT-
Here's what to do -
Boot Puppy 528.
Go to the following link -
http://www.murga-linux.com/puppy/viewto ... 596#421596
And download piratesmack's "broadcom_sta-5.6.48.36-i486.pet"(attached to the post)
Install broadcom_sta-5.6.48.36-i486.pet.
Blacklist b43 and ssb(seems to be done automatically).
Reboot.
The interface should be detected now.
[SOLVED]Puppy on Asus EeePC 1015PEM
[SOLVED]Puppy on Asus EeePC 1015PEM
Last edited by Silent on Sat 10 Sep 2011, 13:41, edited 3 times in total.
- Thanks, Mike.
My website - [url]http://husky.co.cc/[/url]
My website - [url]http://husky.co.cc/[/url]
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
The kernels used in Puppeee and 5.x are too old for all the Eee 1XXX series. I own an Eee PC 1001PX and I had to use my own kernel.
Try Fatdog, Snow Puppy, Dpup Exprimo, Slacko or any other recent Puppy. Puppy 5.3 and above should have kernel 2.6.37.x or above, which should work just fine.
EDIT: try this, it's 5.2.8 with 5.3's kernel.
Try Fatdog, Snow Puppy, Dpup Exprimo, Slacko or any other recent Puppy. Puppy 5.3 and above should have kernel 2.6.37.x or above, which should work just fine.
EDIT: try this, it's 5.2.8 with 5.3's kernel.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
No. Drivers (kernel modules) are highly kernel version sensitive.Silent wrote:If I'm not mistaken, my adapter is BCM4313
...
Is there a way I can copy the working drivers from Puppeee 4.4 to Puppy 5.2.8?
First you should try installing the Broadcom LP-PHY firmware, from here -
http://www.murga-linux.com/puppy/viewto ... 464#448464
Reboot, then you may find that the b43 driver works properly.
If not, try the proprietary "wl" Broadcom wifi driver supplied by forum member piratesmack here
http://www.murga-linux.com/puppy/viewto ... 596#421596
I suggest you download the dotpet, the "delta" upgrade files are a little complicated.
sfeeley - I think you'll love your new system ![Very Happy :D](./images/smilies/icon_biggrin.gif)
I have just tried installing the b43 driver tempestuous provided on Puppy 528, no luck - after rebooting and loading the module no new interfaces were detected. I have then tried ndiswrapper. After loading the ndiswrapper module no new interfaces were detected, too.
I downloaded Three-Headed Dog and booted it. Interface was not detected. I have tried the b43 driver and ndiswrapper, same results. I have then downloaded piratesmack's "wl" Broadcom wifi driver .PET package. Once I click OK to install the package, nothing happens. The installation finished dialog does not pop up.
Basically, I'm stuck again![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
-EDIT-
I've also tried Slacko and Fluppy. Fluppy detects the wireless adapter fine, Slacko doesn't.
![Very Happy :D](./images/smilies/icon_biggrin.gif)
I have just tried installing the b43 driver tempestuous provided on Puppy 528, no luck - after rebooting and loading the module no new interfaces were detected. I have then tried ndiswrapper. After loading the ndiswrapper module no new interfaces were detected, too.
I downloaded Three-Headed Dog and booted it. Interface was not detected. I have tried the b43 driver and ndiswrapper, same results. I have then downloaded piratesmack's "wl" Broadcom wifi driver .PET package. Once I click OK to install the package, nothing happens. The installation finished dialog does not pop up.
Basically, I'm stuck again
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
-EDIT-
I've also tried Slacko and Fluppy. Fluppy detects the wireless adapter fine, Slacko doesn't.
- Thanks, Mike.
My website - [url]http://husky.co.cc/[/url]
My website - [url]http://husky.co.cc/[/url]
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
To be clear; I didn't provide a driver in this case. I provided alternative firmware for the b43 wifi driver which Puppy 5.2.8 already contains.Silent wrote:I have just tried installing the b43 driver tempestuous provided on Puppy 528
That's not what I suggested. ndiswrapper has a relatively low success rate.Silent wrote:I have then tried ndiswrapper.
As the second option, I suggested you install the proprietary "wl" driver in Puppy 5.2.8.
Let's check what you mean by this. First, I hope you mean you tried to install the broadcom dotpet in Puppy 5.2.8 - that's what it's compatible with. Three Headed Dog has a different kernel version, so that particular driver will certainly be incompatible.Silent wrote:I have then downloaded piratesmack's "wl" Broadcom wifi driver .PET package. Once I click OK to install the package, nothing happens.
Also I just checked piratesmack's broadcom dotpet - it installs fine.
And be careful - your Puppy 5.2.8 installation now has a failing ndiswrapper configuration, which is likely to conflict with any other broadcom driver you might try. You would be best to delete your pupsave file (in Puppy 5.2.
![Cool 8)](./images/smilies/icon_cool.gif)
And when you install the proprietary broadcom driver, be sure to follow the instructions in piratesmack's post - especially the part about blacklisting the "ssb" module.