b43 was already in that list once and ssb twice.pemasu wrote:Edoc. /etc/rc.d/MODULESCONFIG
Add in that file to SKIPLIST row those 2 modules more.
ssb and b43
SKIPLIST=" ssb b43 arcfb cirrusfb cyber2000fb ..........
And save. That might be enough. Reboot.
Upup Raring 3.9.9.2 with non-PAE 3.9.9 kernel. 13 July 2013
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
OK, deleted b43.conf at that location and rebooted.
No joy.
ssb and wl show in Pup Kview but no more b43.
Still, wifi that works in MS win7 doesn't work in Puppy.
No joy.
ssb and wl show in Pup Kview but no more b43.
Still, wifi that works in MS win7 doesn't work in Puppy.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Edoc. Well....ssb cant be loaded before wl. I hope that I am right with idea that wl is right module for your wireless. It would help if you would know that wl has worked with that laptop in other Puppy, but you havent at least posted so, I suppose it hasnt.
Last resort. Remove also the wl logistic file:
/lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf
And install this pet and reboot. This pet has logistic file for recognizing your chip and it should unload ssb and then load wl. It has the older logistic mechanism but it should work with your chip id.
Last resort. Remove also the wl logistic file:
/lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf
And install this pet and reboot. This pet has logistic file for recognizing your chip and it should unload ssb and then load wl. It has the older logistic mechanism but it should work with your chip id.
- Attachments
-
- remove_ssb_at_start.pet
- (609 Bytes) Downloaded 358 times
@pemasu,edoc -- sorry to quite likely add confusion to confusion (I never like doing that), but WikiDevi (a great info source for matching drivers to wifi cards) says that the b43 driver *should* work for that chipset...
I looked at these two cards:
Dell Wireless 1397 WLAN Half Mini-Card
Dell Wireless 1395 WLAN Mini-Card
Both say to use b43.
Dunno if that helps or just adds to the mess, but I thought I'd throw it out there...
I looked at these two cards:
Dell Wireless 1397 WLAN Half Mini-Card
Dell Wireless 1395 WLAN Mini-Card
Both say to use b43.
Dunno if that helps or just adds to the mess, but I thought I'd throw it out there...
I just stopped the process and booted from a Lucid Puppy DVD - the wifi works fine.pemasu wrote:Edoc. Well....ssb cant be loaded before wl. I hope that I am right with idea that wl is right module for your wireless. It would help if you would know that wl has worked with that laptop in other Puppy, but you havent at least posted so, I suppose it hasnt.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Edoc and Starhawk. Well. Yeah. I play with chip id`s solely.
http://wireless.kernel.org/en/users/Drivers/b43
ID: 14e4:4315
14e4:4315 b43 yes (2.6.33+), alternative wl
Both should work, at these situations, I would go for wl. But my reasoning can be faulty.
Edoc. It would help if you could post what driver worked. I suppose it was b43, but reading it from you is better than assuming.
In that case, disabling wl module loading would be the way to go. Which means opposite as we have done, and as Starhawk suggested.
Blacklisting wl, removing its logistic file, etc...
And yes. My wifi works also fine. Lol.
http://wireless.kernel.org/en/users/Drivers/b43
ID: 14e4:4315
14e4:4315 b43 yes (2.6.33+), alternative wl
Both should work, at these situations, I would go for wl. But my reasoning can be faulty.
Edoc. It would help if you could post what driver worked. I suppose it was b43, but reading it from you is better than assuming.
In that case, disabling wl module loading would be the way to go. Which means opposite as we have done, and as Starhawk suggested.
Blacklisting wl, removing its logistic file, etc...
And yes. My wifi works also fine. Lol.
OK ...
Opened iso and replaced the three Frugal files, also replaced devx, just in case.
Deleted the savefile and rebooted.
I blacklisted wl and added b43 then rebooted again.
Internet Connection Wizard sees the b43 module but will not 'find' the router, neither will Frisbee.
Something in Raring is interfering that is not in Lucid.
Where should I look, please?
Opened iso and replaced the three Frugal files, also replaced devx, just in case.
Deleted the savefile and rebooted.
I blacklisted wl and added b43 then rebooted again.
Internet Connection Wizard sees the b43 module but will not 'find' the router, neither will Frisbee.
Something in Raring is interfering that is not in Lucid.
Where should I look, please?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Edoc. To be sure...I would remove wl logistic file and also wl kernel module. Then reboot. If that does not help....then there isnt much more I can do.
in console.
rm /lib/modules/3.9.9-upup/kernel/drivers/net/wireless/wl.ko
rm /lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf
And then there isnt anymore possibility that wl.ko module interferes.
If this does not help, post pdiag tarball again after unsuccesful trial.
Your b43 chip should be supported without any problems. So...I really dont know what is wrong with this build. I think we will need spiritual session soon....
in console.
rm /lib/modules/3.9.9-upup/kernel/drivers/net/wireless/wl.ko
rm /lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf
And then there isnt anymore possibility that wl.ko module interferes.
If this does not help, post pdiag tarball again after unsuccesful trial.
Your b43 chip should be supported without any problems. So...I really dont know what is wrong with this build. I think we will need spiritual session soon....
resizepfile not working in raring 3.9.9.1
Hi Pemasu!
FInally i can try raring (only version working is 3.9.9.1). Now it works on my Fujitsu laptop laptop
But.. I have found a bug in resizepfile script (this is 0.14 version). It returns an error whatever size of personal resize file increase.
I have patched this with the script of Don570 or older script from Precise.
Can you correct next release of raring with this?
Thanks
FInally i can try raring (only version working is 3.9.9.1). Now it works on my Fujitsu laptop laptop
But.. I have found a bug in resizepfile script (this is 0.14 version). It returns an error whatever size of personal resize file increase.
I have patched this with the script of Don570 or older script from Precise.
Can you correct next release of raring with this?
Thanks
Did it all, rebooted multiple times, no joy. Very odd.pemasu wrote:Edoc. To be sure...I would remove wl logistic file and also wl kernel module. Then reboot. If that does not help....then there isnt much more I can do.
in console.
rm /lib/modules/3.9.9-upup/kernel/drivers/net/wireless/wl.ko
rm /lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf
And then there isnt anymore possibility that wl.ko module interferes.
If this does not help, post pdiag tarball again after unsuccesful trial.
Your b43 chip should be supported without any problems. So...I really dont know what is wrong with this build. I think we will need spiritual session soon....
Here's the pdiag output:
- Attachments
-
- pdiag-20130727.tar.gz
- (129.28 KiB) Downloaded 324 times
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[ 2605.349875] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2645.749879] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2698.997076] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
It does not say that firmware loading has been succesful or something and it tries to load it once before and here 3 times.
Could it be firmware problem. I need to check if 3.9.9 kernel has changed firmware status. Or...if my firmwares has somekind corruption...or then I am barking the wrong tree....deja vu.....
[ 2645.749879] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2698.997076] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
It does not say that firmware loading has been succesful or something and it tries to load it once before and here 3 times.
Could it be firmware problem. I need to check if 3.9.9 kernel has changed firmware status. Or...if my firmwares has somekind corruption...or then I am barking the wrong tree....deja vu.....
No...no new firmwares. When I compiled the b43 firmwares and compared, the size is exactly the same as bytes with the new ones and older ones.
Edoc. Have you tried other wireless manager. If you have used Frisbee, switch to use SNS and vice versa. Right click Connect icon and select Choose internet connection wizard and change the manager to other one.
I am about clueless now. Next I suspect the b43 module, corruption of connection manager, moon and aliens. Tinfoil hat time....
Edoc. Have you tried other wireless manager. If you have used Frisbee, switch to use SNS and vice versa. Right click Connect icon and select Choose internet connection wizard and change the manager to other one.
I am about clueless now. Next I suspect the b43 module, corruption of connection manager, moon and aliens. Tinfoil hat time....
I have been testing back and forth between Internet Connection Wizard and Frisbee.pemasu wrote:No...no new firmwares. When I compiled the b43 firmwares and compared, the size is exactly the same as bytes with the new ones and older ones.
Edoc. Have you tried other wireless manager. If you have used Frisbee, switch to use SNS and vice versa. Right click Connect icon and select Choose internet connection wizard and change the manager to other one.
I am about clueless now. Next I suspect the b43 module, corruption of connection manager, moon and aliens. Tinfoil hat time....
I just tried SNS and same result.
If there is a b43 - Frisbee problem could Frisbee be interfering with the others?
I ask because in other versions there used to be an option to disable/enable Frisbee - presumably for that reason.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
When you ponder this again ...
I just loaded Wheezy.
It defaulted to wl "wlan0 wireless wl pci: Broadcom 802.11b LP PHY
(Note 1: In one spot a message stated that wl is not listed as supporting WPA encryption.)
(Note 2: The device is listed as a BCM4312.)
I tried wl & it failed so I added it to Skiplist in /etc/rc.d modulesconfig
Then I added the b43 module - rebooted and it also failed.
I just loaded Wheezy.
It defaulted to wl "wlan0 wireless wl pci: Broadcom 802.11b LP PHY
(Note 1: In one spot a message stated that wl is not listed as supporting WPA encryption.)
(Note 2: The device is listed as a BCM4312.)
I tried wl & it failed so I added it to Skiplist in /etc/rc.d modulesconfig
Then I added the b43 module - rebooted and it also failed.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603