(old)Puppy Linux Discussion Forum

Thanks Jim3630. This is good news. Yes, I typed the questions automatically, The brcm80211 drivers of course are in the build preinstalled, part of the kernel. I fixed my post so that there is no more confusion what I meant.
Thank you very much !
Could you do one more thing. In console lspci -nnv and post the 3-4 rows concerning your broadcom wireless. I would like to make a note about the revision number and ID of your broadcom chip.

pemasu wrote:Thanks Jim3630. This is good news. Yes, I typed the questions automatically, The brcm80211 drivers of course are in the build preinstalled, part of the kernel. I fixed my post so that there is no more confusion what I meant.
Thank you very much !
Could you do one more thing. In console lspci -nnv and post the 3-4 rows concerning your broadcom wireless. I would like to make a note about the revision number and ID of your broadcom chip.

I mentioned the id in previous post but here you go.

03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:145c]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at b2400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-12-ff-ff-1d-ac-81
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: brcmsmac

Thank you. It also helps to have it documented here. If someone uses google search with that revision number + murga-linux, he might find your post.

Yes, your chip revision number is in the list.

pemasu wrote:Thank you. It also helps to have it documented here. If someone uses google search with that revision number + murga-linux, he might find your post.

Yes, your chip revision number is in the list.

do you know if the new broadcom driver will be included in all new linux kernels or only the new woof kernels?

xcompmgr got left out. installed it, no problems.

Barrys new 2.6.39.4 kernel has it in Wary Racy or what ever it was. Posted today. You just need the firmware pet for it. Maybe it is enabled in Iguleders 2.6.39.4 kernel also, I dont know. Ask him or just install the firmware and check.
All the 2.6.39.4 and 3.0.X kernels have it, I am sure, but you need to enable it though during kernel compiling time. It resides in staging drivers section and compilers dont notice it straight. I knew about it because Tempestuous posted about it.

Dave S. Strange. I need to check out my specs. It should have been in. Sorry. But good pick if it isnt. Yes, the woof havent processed it properly. I need to find out why not.

pemasu wrote:Barrys new 2.6.39.4 kernel has it in Wary Racy or what ever it was. Posted today. You just need the firmware pet for it. Maybe it is enabled in Iguleders 2.6.39.4 kernel also, I dont know. Ask him or just install the firmware and check.
All the 2.6.39.4 and 3.0.X kernels have it, I am sure, but you need to enable it though. It resides in staging drivers section and compilers dont notice it straight. I knew about it because Tempestuous posted about it.

thanks for the info it's good to know.

Dave S. Woof problem fixed. Xcompmgr will be in my original Dpup Exprimo 5.X.7. I hope that others test the apps they use and report if something does not work. I can then fix it for next build.

pemasu wrote:Dave S. Woof problem fixed. Xcompmgr will be in my original Dpup Exprimo 5.X.7. I hope that others test the apps they use and report if something does not work. I can then fix it for next build.

Cool.

pemasu hope don't mind i posted the firmware pet and linked backed to here.

http://murga-linux.com/puppy/viewtopic. ... 809#564809

No problem. The firmware compressed package was originally provided by Tempestuous. I only made pet of it. You should add the url link for supported chips, which I posted. People get from that link the understanding for whom those firmwares are needed.

There is just so much here to like

The date48.png in /usr/local/lib/X11/themes/Trinity is a 24-pixel image, and looks very small when linked to "Plan" on the JWM desktop.

Radky. Yes I know. I thought I had fixed it but it seems I havent moved the fix to the woof. I will now.
Thank you. I have replacement anyway already picked.

Radky, and others. What do you think this replacement for JWM-Pinboard.

Edit. Blue Step Humanity still has the problem. Originally I needed the change because e17 needed better icon, the original was only black patch.

Oh well, it needs more investigation. I dont like tempering with icons used with several instances, but these are the mandatory ones for e17.

Maybe I change e17 to the Openbox-Fbpanel and make link to the Dave S great tuning thread.

pemasu wrote: Maybe I change e17 to the Openbox-Fbpanel and make link to the Dave S great tuning thread.

Dave's Openbox-Fbpanel Desktop works great in Dpup Exprimo.
http://www.smokey01.com/pemasu/pet_pack ... o-1.30.pet
http://www.smokey01.com/pemasu/pet_pack ... mo-1.1.pet

jim3630 wrote:The new brcm80211 worked after installing only the firmware pet. the driver is pre-installed in the kernel.

That's good news.

pemasu, I would now make the bold suggestion that you remove the proprietary broadcom_sta driver driver from the first post, so that all users of modern Broadcom wifi devices will then have only one option - the brcm80211 drivers. I have several reasons:

i) for consistency and to avoid confusion - you don't want users reporting Broadcom wifi errors and getting confused about which driver is actually being used. They might not understand the difference, and inadvertently report wrong information.

ii) the proprietary driver will continue to conflict with the underlying ssb driver, and potentially cause problems with other hardware that depends on the ssb driver - such as USB interfaces.

iii) we should be encouraging the use of opensource drivers, whenever possible.

I suggest you add the brcm-firmware to future releases.

Tempestuous. I will do as you suggested. Straight logic behind your reasoning.

only error found so far is when connecting a usb storage device then maybe 12 gtkdialog idrive pannels appear repeating some of the drives. upon disconnecting 3 duplicate gtkdialog boxes appear showing idrive pannel with current available drives.