Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 15 Jul 2018, 17:30
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
bcm43xx driver does not work
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [7 Posts]  
Author Message
drongo


Joined: 10 Dec 2005
Posts: 378
Location: UK

PostPosted: Sat 02 Aug 2008, 12:42    Post subject:  bcm43xx driver does not work  

Hi,
I have a Dell Precision M70 work laptop. Since the bcm43xx driver was first included in Puppy (round about 2.1something) this has worked fine. Doesn't work with the latest 4.1 alpha5, although I'm pretty sure it worked with 4.0 Dingoes.

Everything (including wireless) works fine on my home laptop (cheap Medion) so I'm pretty sure it's not a network wizard problem or a problem with my Wifi router.

The network wizard picks up that the bcxm43xx is loaded. I'm slightly reluctant to experiment as my WiFi was extremely flakey after booting back into XP, so I assume the Linux driver does something extremely low level to the Broadcom chip that XP doesn't even read/set. (I'm not imagining this, I have seen similar effects with other live Linuxes on this machine.)

Anything I can try to aid diagnosis?

I have deliberately not put this in the Network Wizard thread as I don't believe that is where the problem lies. (But I am probably wrong!)

drongo
Back to top
View user's profile Send private message 
drongo


Joined: 10 Dec 2005
Posts: 378
Location: UK

PostPosted: Sat 02 Aug 2008, 12:44    Post subject:  

Rats, this was supposed to be part of the 4.1 alpha 5 thread.

Apologies.

drongo
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5470
Location: Australia

PostPosted: Fri 08 Aug 2008, 18:58    Post subject:  

http://www.murga-linux.com/puppy/viewtopic.php?p=222118#222118
Back to top
View user's profile Send private message 
drongo


Joined: 10 Dec 2005
Posts: 378
Location: UK

PostPosted: Sat 09 Aug 2008, 16:18    Post subject:  

Thanks tempestuous,

I guess I can just manually load the driver and blacklist the deprecated one.

Just one question, though. I was running "puppy pfix=ram" as I always do on alphas. Why does the kernel select the wrong driver?

Regards

drongo
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5470
Location: Australia

PostPosted: Sat 09 Aug 2008, 21:52    Post subject:  

It's not a case of being wrong. The problem is that in the latest Puppy alphas there can be two modules competing for the same device. The best solution is to use the "PREFLIST" function, rather than blacklisting. I just posted instructions here -
http://www.murga-linux.com/puppy/viewtopic.php?t=32331
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2307
Location: Wyoming, USA

PostPosted: Thu 14 Aug 2008, 11:07    Post subject:  

So... will standard Puppy 4.1 be delivered with a PREFLIST already set up? It would be better to have drivers like this already sorted in order of preference so it will "just work" for most users. Maybe keep the less preferred ones around for people to try if the more preferred ones don't work?

The bcm43xx did not work on a Dell laptop I tried; probably it belongs at the end of the list.

Or are the questionable drivers simply going to be tossed?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5470
Location: Australia

PostPosted: Thu 14 Aug 2008, 12:33    Post subject:  

You Broadcom wifi owners need to report your findings to Barry, and ask to have the problem fixed.

I don't think that PREFLIST will fully deal with this particular problem, because Broadcom wifi support since kernel 2.6.23 is now split across two different modules: b43 and b43legacy - obviously this means new/old devices. The pci id's claimed by each module should be completely different, but the old bcm43xx module will claim pci id's which span both of these new drivers.

So I think the best solution would be to completely remove the bcm43xx module from Puppy 4.1.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [7 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1527s ][ Queries: 11 (0.0277s) ][ GZIP on ]