install firmware-linux-nonfree. . .operand?
Your dotpet SAYS it downloaded, but I don't see it on the dmesg readout. Here's what it says now:
-> GSI 21 (level, low) -> IRQ 21
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:08:00.0
b44.c:v2.0
eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:1c:23:8e:59:d0
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4311 WLAN found (core revision 10)
b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy0: Selected rate control algorithm 'minstrel'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
pci 0000:01:05.0: power state changed by ACPI to D0
pci 0000:01:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to userspace modesetting.
[drm] Initialized radeon 1.32.0 20080528 for 0000:01:05.0 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading R300 Microcode
platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin
[drm] Num pipes: 1
[drm] writeback test succeeded in 1 usecs
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
b43 ssb0:0: firmware: requesting b43-open/pcm5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43 ssb0:0: firmware: requesting b43-open/b0g0initvals5.fw
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/b0g0initvals5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
Does this mean there is NO driver god or bad?
I think what's confusing me is that you say "IF the dmesg readout says a, then. . ." but my readout says something different, or I'm looking in the wrong place.
-> GSI 21 (level, low) -> IRQ 21
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:08:00.0
b44.c:v2.0
eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:1c:23:8e:59:d0
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4311 WLAN found (core revision 10)
b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy0: Selected rate control algorithm 'minstrel'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
pci 0000:01:05.0: power state changed by ACPI to D0
pci 0000:01:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to userspace modesetting.
[drm] Initialized radeon 1.32.0 20080528 for 0000:01:05.0 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading R300 Microcode
platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin
[drm] Num pipes: 1
[drm] writeback test succeeded in 1 usecs
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
b43 ssb0:0: firmware: requesting b43-open/pcm5.fw
firmware ssb0:0: firmware_loading_store: vmap() failed
b43 ssb0:0: firmware: requesting b43-open/b0g0initvals5.fw
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/b0g0initvals5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri ... cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
Does this mean there is NO driver god or bad?
I think what's confusing me is that you say "IF the dmesg readout says a, then. . ." but my readout says something different, or I'm looking in the wrong place.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Yes, the dmesg errors which I suggested would be seen in situations with LP-PHY-compatible devices are not showing up in your dmesg results. So it's looking like the LP-PHY firmware is incompatible with your device. I don't have access to a Linux computer at the moment, but I will investigate further, later.
I think you should abandon trying to get the standard b43 driver working, and move on to install the proprietary "wl" driver.
I think you should abandon trying to get the standard b43 driver working, and move on to install the proprietary "wl" driver.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Yes, multiple forum members have contributed the prorietary Broadcom wifi driver in the past,
and yes, I see that peebee's version is more recent than piratesmack's version.
The correct link for peebee's wifi driver, compatible with Puppy Lucid 5.1-5.2.8 is here -
http://murga-linux.com/puppy/viewtopic. ... 143#624143
Tip: ignore the "delta" files. Just get the dotpet.
and yes, I see that peebee's version is more recent than piratesmack's version.
The correct link for peebee's wifi driver, compatible with Puppy Lucid 5.1-5.2.8 is here -
http://murga-linux.com/puppy/viewtopic. ... 143#624143
Tip: ignore the "delta" files. Just get the dotpet.
Who's the n00best one of all? ME!
I get a "general error" for the download, and the broadcom_sta_v5.100.82.112_patched_x86_32-multi_inc_pref_logic.pet
won't open.
10 hours I have into this!!!!! To hell with trying to get 5.2.8 to run its wlan0 on a 1501. Which version will "just work", and where do I go to get it?
I get a "general error" for the download, and the broadcom_sta_v5.100.82.112_patched_x86_32-multi_inc_pref_logic.pet
won't open.
10 hours I have into this!!!!! To hell with trying to get 5.2.8 to run its wlan0 on a 1501. Which version will "just work", and where do I go to get it?
Slacko 5.7
I have tried (unsuccessfully) to upload the latest wl driver for 5.2.8, but I recommend Puppy Slacko 5.7 :-
http://distro.ibiblio.org/puppylinux/pu ... NO-pae.iso This should work ootb.
http://distro.ibiblio.org/puppylinux/pu ... NO-pae.iso This should work ootb.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Don't get too disheartened. You're making progress.
I now remember that the administrator of the Puppy Forum changed the attachment filesize limit to 250KB at some stage, thus breaking hundreds of links on the forum.
But you will see that peebee edited the post to include an alternative download link, highlighted in blue as "Use this link if you get FORUM ERROR"
I just checked this link now, it downloads fine.
So if you want to persist with Lucid 5.28, I think you will get there.
But given that your laptop has very respectable specifications, I see no good reason to use an older Puppy such as Lucid.
I think you should be using the latest Slacko, and since you have less than 4GB RAM, get the non-PAE version.
I now remember that the administrator of the Puppy Forum changed the attachment filesize limit to 250KB at some stage, thus breaking hundreds of links on the forum.
But you will see that peebee edited the post to include an alternative download link, highlighted in blue as "Use this link if you get FORUM ERROR"
I just checked this link now, it downloads fine.
So if you want to persist with Lucid 5.28, I think you will get there.
But given that your laptop has very respectable specifications, I see no good reason to use an older Puppy such as Lucid.
I think you should be using the latest Slacko, and since you have less than 4GB RAM, get the non-PAE version.
- Attachments
-
- download-option.jpg
- (34.5 KiB) Downloaded 288 times
And if you struggle with the new one above >> The little gray dwnld button on your left.
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Thanks again for your patience and tips. . .one does get a bit frustrated at times. My Windows 7 shared tower at work is having wifi issues, my mini 10 running Ubuntu 14 is having wifi issues, and my home tower running Ubuntu 12 is having wifi issues. Maybe an NSA thing?
This morning I loaded a new cd of 528.005, it loaded the personal file from the HDD, and said wlan0 down. I did a ram boot. . .no problem. I'm reminded that when I first loaded 528 on this machine, everything was fine. . .for a while. I've done that before, too: load from the cd using pfix ram and it just works (but not always). Someone mentioned this Broadcom version is prone to corruption, and maybe that's the answer.
Tempestuous and Ozsouth: I have a disk of Slacko 5.7 no PAE, and I found I needed to right click on the mousepad to enter anything, and it wouldn't shut off without a hard boot. I also tried Wary, which is fine for the old machines. Bottom line: when 528 works, it's hard to beat.
I'm willing to try 5.7.1 Precise. Is that different from Slacko?
This morning I loaded a new cd of 528.005, it loaded the personal file from the HDD, and said wlan0 down. I did a ram boot. . .no problem. I'm reminded that when I first loaded 528 on this machine, everything was fine. . .for a while. I've done that before, too: load from the cd using pfix ram and it just works (but not always). Someone mentioned this Broadcom version is prone to corruption, and maybe that's the answer.
Tempestuous and Ozsouth: I have a disk of Slacko 5.7 no PAE, and I found I needed to right click on the mousepad to enter anything, and it wouldn't shut off without a hard boot. I also tried Wary, which is fine for the old machines. Bottom line: when 528 works, it's hard to beat.
I'm willing to try 5.7.1 Precise. Is that different from Slacko?
Hi...Walt52 wrote:I have a disk of Slacko 5.7 no PAE, and I found I needed to right click on the mousepad to enter anything, and it wouldn't shut off without a hard boot. I also tried Wary, which is fine for the old machines. Bottom line: when 528 works, it's hard to beat.
I'm willing to try 5.7.1 Precise. Is that different from Slacko?
Precise is a bit different as it is designed with a level of compatibility with Ubuntu and you have access to Canonical's (Ubuntu's) repositories. However, because Puppy is not Debian based, not everything that runs in Ubuntu will work in Puppy. I know from experience.
While Precise might be worth a try, I'm starting to think the issues you are having are related to your hardware (the laptop itself.) What you have said you are experiencing, not counting getting the wireless adapter to work, are not typical in Puppy at all, at least to my knowledge.
Regards...
I made a disk of 5.7.1, and it's working fine. It said Wlan0 was down , but went ahead and connected anyway. (Could my 1501 laptop be psychotic, or possessed, maybe?)
One last question: has anyone heard of a list of laptops with suggested puppy distros? Say, like Asus A1000=Wary, Dell D600=528, Dell 1501=5.7.1, and so on?
One last question: has anyone heard of a list of laptops with suggested puppy distros? Say, like Asus A1000=Wary, Dell D600=528, Dell 1501=5.7.1, and so on?
Hi...Walt52 wrote:I made a disk of 5.7.1, and it's working fine. It said Wlan0 was down , but went ahead and connected anyway. (Could my 1501 laptop be psychotic, or possessed, maybe?)
One last question: has anyone heard of a list of laptops with suggested puppy distros? Say, like Asus A1000=Wary, Dell D600=528, Dell 1501=5.7.1, and so on?
If you're using Frisbee as your network, that message is normal the first time you connect to your network. You shouldn't see it again, although you will probably see a message indicating the ethernet connection is down.
Regarding your second question, none that I've ever seen. I think it's more of a matter of personal choice and what works best with the hardware.
Regards...