Mouse pointer not working + wlan not working

[Florian_13]

I am using bionicpup32

my mouse (corsair harpoon rgb pro is recognized and clicks are registered but the pointer wont move. and no the problem isnt in my mouse or my laptop.

the bigger isuue is that wlan wont work. the output of lspci is:

Code: Select all

06:02.0 Network controller: Broadcom Inc. and subsidiaries BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

and the output of dmesg | grep firm is:

Code: Select all

 dmesg | grep firm
[   29.180206] b43 ssb0:0: Direct firmware load for b43/pcm5.fw failed with error -2
[   29.182599] b43 ssb0:0: Direct firmware load for b43/b0g0initvals5.fw failed with error -2
[   29.184272] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2
[   29.186049] b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2
[   29.283669] udevd[3885]: Process '/sbin/pup_event_backend_firmware' failed with exit code 1.
[   29.285577] udevd[3710]: Process '/sbin/pup_event_backend_firmware' failed with exit code 1.
[   29.293129] b43 ssb0:0: Direct firmware load for b43-open/pcm5.fw failed with error -2
[   29.295912] b43 ssb0:0: Direct firmware load for b43-open/b0g0initvals5.fw failed with error -2
[   29.297410] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[   29.335762] udevd[3885]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.4/0000:06:02.0/ssb0:0/firmware/b43-open!ucode5.fw/loading} for writing: No such file or directory
[   29.351323] udevd[3886]: Process '/sbin/pup_event_backend_firmware' failed with exit code 1.
[   29.352881] udevd[3887]: Process '/sbin/pup_event_backend_firmware' failed with exit code 1.
[   29.380824] udevd[3885]: Process '/sbin/pup_event_backend_firmware' failed with exit code 1.
# 

and i tried to install the firmware but it just got this when installing it:

Code: Select all

# make
     CC       b43-fwcutter
/usr/bin/ld: cannot find /usr/lib/i386-linux-gnu/libc_nonshared.a
collect2: error: ld returned 1 exit status
Makefile:51: recipe for target 'b43-fwcutter' failed
make: *** [b43-fwcutter] Error 1
# 

please help I just can't figure it out

[mikeslr]

I'm not sure any of this will help, but I don't like leaving posts unanswered for long, especially by those new to the Forum. By the way, to the Forum.

Hopefully someone with technical knowledge will respond soon. I'm not a 'tecky', at best an historian, occasionally a system analyst. In the former capacity, I used https://rockedge.org/psearch/ -- a dedicated google search engine for 'everything Puppy'-- which spit out this thread concerning the BCM4318 adapter under bionicpup32, https://oldforum.puppylinux.com/viewtop ... 3#p1052793. Note that drivers are 'kernel' dependent and I'm not sure the version of Bionicpup32 you downloaded uses the 4.9.163-lxpup-32-pae kernel. If not, editing the boot-manager's linux/kernel line might still work.

I'm guessing, [I don't compile] but I think the reason your attempt at compiling failed is because --to keep Puppys small, and few users compile-- the applications needed to compile are not included in the ISO. They are provided by a devx SFS specific to each Puppy. In the case of Bionicpup32 you'll find it here, http://distro.ibiblio.org/puppylinux/pu ... nicpup32/ along with Kernel Headers and Sources. Usage: Download, Right-Click, Select SFS-Load. To unload, repeat: SFS-Load is a toggle.

To help whoever comes along later, please read this post. https://www.forum.puppylinux.com/viewto ... p=816#p816. And after supplying the missing info, while your still waiting, read these:
https://www.forum.puppylinux.com/viewto ... 395#p68395
https://www.forum.puppylinux.com/viewto ... 827#p55827 and
https://www.forum.puppylinux.com/viewto ... 818#p63818

Puppy is substantially different from other Linuxes. Those who come to Puppy with the expectation that it will function like them have a harder time than 'Window refugees' who have no expectations. Others Posts in the 'Getting Starting Section' may also help.

[rcrsn51]

I am using bionicpup32

Please state the exact version and how you installed it.

The package bionicpup32-8.0-uefi.iso has an fdrv.sfs file that appears to contain the required firmware for your BCM4318.

Have you included this file in your install?

[Florian_13]

I'm not sure any of this will help, but I don't like leaving posts unanswered for long, especially by those new to the Forum. By the way, to the Forum.

Hopefully someone with technical knowledge will respond soon. I'm not a 'tecky', at best an historian, occasionally a system analyst. In the former capacity, I used https://rockedge.org/psearch/ -- a dedicated google search engine for 'everything Puppy'-- which spit out this thread concerning the BCM4318 adapter under bionicpup32, https://oldforum.puppylinux.com/viewtop ... 3#p1052793. Note that drivers are 'kernel' dependent and I'm not sure the version of Bionicpup32 you downloaded uses the 4.9.163-lxpup-32-pae kernel. If not, editing the boot-manager's linux/kernel line might still work.

I'm guessing, [I don't compile] but I think the reason your attempt at compiling failed is because --to keep Puppys small, and few users compile-- the applications needed to compile are not included in the ISO. They are provided by a devx SFS specific to each Puppy. In the case of Bionicpup32 you'll find it here, http://distro.ibiblio.org/puppylinux/pu ... nicpup32/ along with Kernel Headers and Sources. Usage: Download, Right-Click, Select SFS-Load. To unload, repeat: SFS-Load is a toggle.

To help whoever comes along later, please read this post. https://www.forum.puppylinux.com/viewto ... p=816#p816. And after supplying the missing info, while your still waiting, read these:
https://www.forum.puppylinux.com/viewto ... 395#p68395
https://www.forum.puppylinux.com/viewto ... 827#p55827 and
https://www.forum.puppylinux.com/viewto ... 818#p63818

Puppy is substantially different from other Linuxes. Those who come to Puppy with the expectation that it will function like them have a harder time than 'Window refugees' who have no expectations. Others Posts in the 'Getting Starting Section' may also help.

Thank you so much for this and espacially for the search engine. but for the sfs files i already have sfs loaded at boot should i do the same for the kernel headers and sources?

[Florian_13]

I am using bionicpup32

Please state the exact version and how you installed it.

The package bionicpup32-8.0-uefi.iso has an fdrv.sfs file that appears to contain the required firmware for your BCM4318.

Have you included this file in your install?

I have got 19.03 and installed it via cd r. and where can i find the fdrv.sfs file?

[Florian_13]

I'm not sure any of this will help, but I don't like leaving posts unanswered for long, especially by those new to the Forum. By the way, to the Forum.

Hopefully someone with technical knowledge will respond soon. I'm not a 'tecky', at best an historian, occasionally a system analyst. In the former capacity, I used https://rockedge.org/psearch/ -- a dedicated google search engine for 'everything Puppy'-- which spit out this thread concerning the BCM4318 adapter under bionicpup32, https://oldforum.puppylinux.com/viewtop ... 3#p1052793. Note that drivers are 'kernel' dependent and I'm not sure the version of Bionicpup32 you downloaded uses the 4.9.163-lxpup-32-pae kernel. If not, editing the boot-manager's linux/kernel line might still work.

I'm guessing, [I don't compile] but I think the reason your attempt at compiling failed is because --to keep Puppys small, and few users compile-- the applications needed to compile are not included in the ISO. They are provided by a devx SFS specific to each Puppy. In the case of Bionicpup32 you'll find it here, http://distro.ibiblio.org/puppylinux/pu ... nicpup32/ along with Kernel Headers and Sources. Usage: Download, Right-Click, Select SFS-Load. To unload, repeat: SFS-Load is a toggle.

To help whoever comes along later, please read this post. https://www.forum.puppylinux.com/viewto ... p=816#p816. And after supplying the missing info, while your still waiting, read these:
https://www.forum.puppylinux.com/viewto ... 395#p68395
https://www.forum.puppylinux.com/viewto ... 827#p55827 and
https://www.forum.puppylinux.com/viewto ... 818#p63818

Puppy is substantially different from other Linuxes. Those who come to Puppy with the expectation that it will function like them have a harder time than 'Window refugees' who have no expectations. Others Posts in the 'Getting Starting Section' may also help.

and my kernel version is: 4.19.289

[mikeslr]

Let's start again. To quote bigpup, "We only know what you tell us."

Exactly how did you install it? " via cd r" suggests to a CD, but could mean from a previously 'burned' CD to a hard-drive or USB-Key. And using what program/application?

What is the make/model of your computer? Your answer may be important later on; but at this juncture we have to know if your computer employs the UEFI mechanism because not all applications to deploy Puppys work with UEFI computers. So, if you know, tell us if yours does.

Knowing which computer may enable use to suggest a better version of Puppy for your computer before you spend a lot of time with bionicpup32. In that vain, while most Puppys can do things like browse the web and write documents, some Puppys have been created to provide OOTB applications for special interest. Do you have any?

And why bionicpup32? Why 32-bit? It's increasingly difficult to obtain 32-bit web-browsers that can access most of the current Web; and their days are numbered and counting. 5 years ago, when bionicpup32 was first published, it was 'top of the line' built from the binaries of Ubuntu Bionic Beaver. Ubuntu has declared that Bionic Beaver has reached END of LIFE and archived its repositories. The contents of archived repositories can be downloaded; but not easily. And by now Puppy Fans/Devs have published many applications which are easy to obtain. However, bionicpup32 is primarily maintained for those who have computers which can't use newer Puppys. Identifying your computer will help us know what limitations it has.

Is your bionic32 the bionicpup32-8.0-uefi.iso rcrsn51 referred to? If not, it should be. The uefi designation signifies that it includes the files required to boot from a computer using the uefi mechanism. But when deployed to a computer which doesn't those files are ignored. So it can be deployed to both.

"but for the sfs files i already have sfs loaded at boot" seems to refer to the devx.sfs. For now we're concerned with the fdrv.sfs and zdrv.sfs. These contain, respectively, the firmware and drivers. See https://www.forum.puppylinux.com/viewtopic.php?t=5818. bionicpup32's initrd.gz --the first thing that loads after vmlinuz-- contains instruction to AUTOMATICALLY copy into RAM the files-systems named fdrv_upupbb_19.03.sfs and zdrv_upupbb_19.03.sfs at bootup IF they are present. You can see if they are by file-browsing to the location where the other system files --i.e. initrd.gz, vmlinuz and puppy_upupbb_19.03.sfs-- are located. If one or the other are missing, that could explain either or both your mouse and wifi issues. Their absence would suggest either a bad download or a bad 'burn'.

Lastly, have you tried editing the linux/kernel boot line. My sometimes flaky recollection is that 'black-listing' other drivers is necessary whenever Broadcom drivers are involved. Follow the link in my original reply for instructions on how to black-list drivers.

[Florian_13]

Let's start again. To quote bigpup, "We only know what you tell us."

Exactly how did you install it? " via cd r" suggests to a CD, but could mean from a previously 'burned' CD to a hard-drive or USB-Key. And using what program/application?

What is the make/model of your computer? Your answer may be important later on; but at this juncture we have to know if your computer employs the UEFI mechanism because not all applications to deploy Puppys work with UEFI computers. So, if you know, tell us if yours does.

Knowing which computer may enable use to suggest a better version of Puppy for your computer before you spend a lot of time with bionicpup32. In that vain, while most Puppys can do things like browse the web and write documents, some Puppys have been created to provide OOTB applications for special interest. Do you have any?

And why bionicpup32? Why 32-bit? It's increasingly difficult to obtain 32-bit web-browsers that can access most of the current Web; and their days are numbered and counting. 5 years ago, when bionicpup32 was first published, it was 'top of the line' built from the binaries of Ubuntu Bionic Beaver. Ubuntu has declared that Bionic Beaver has reached END of LIFE and archived its repositories. The contents of archived repositories can be downloaded; but not easily. And by now Puppy Fans/Devs have published many applications which are easy to obtain. However, bionicpup32 is primarily maintained for those who have computers which can't use newer Puppys. Identifying your computer will help us know what limitations it has.

Is your bionic32 the bionicpup32-8.0-uefi.iso rcrsn51 referred to? If not, it should be. The uefi designation signifies that it includes the files required to boot from a computer using the uefi mechanism. But when deployed to a computer which doesn't those files are ignored. So it can be deployed to both.

"but for the sfs files i already have sfs loaded at boot" seems to refer to the devx.sfs. For now we're concerned with the fdrv.sfs and zdrv.sfs. These contain, respectively, the firmware and drivers. See https://www.forum.puppylinux.com/viewtopic.php?t=5818. bionicpup32's initrd.gz --the first thing that loads after vmlinuz-- contains instruction to AUTOMATICALLY copy into RAM the files-systems named fdrv_upupbb_19.03.sfs and zdrv_upupbb_19.03.sfs at bootup IF they are present. You can see if they are by file-browsing to the location where the other system files --i.e. initrd.gz, vmlinuz and puppy_upupbb_19.03.sfs-- are located. If one or the other are missing, that could explain either or both your mouse and wifi issues. Their absence would suggest either a bad download or a bad 'burn'.

Lastly, have you tried editing the linux/kernel boot line. My sometimes flaky recollection is that 'black-listing' other drivers is necessary whenever Broadcom drivers are involved. Follow the link in my original reply for instructions on how to black-list drivers.

I burned it to a cd using k3b and im using a HP Pavilion dv5000 (ES264EA#ABZ) I used a 32 bit os because my cpu (Mobile AMD Sempron(tm) processor 3000+) doesnt support 64 bit. when starting up it says "loading fdrv file" and "loading zdrv file" and they are also present in the folder. I dont really know what you mean with editing the kernel boot line. btw sorry if I dont know a lot of things but I'm pretty new to linux and esspecially to puppy linux

[Florian_13]

Is your bionic32 the bionicpup32-8.0-uefi.iso rcrsn51 referred to? If not, it should be.

I downlloaded that iso from the website but the iso was empty and had a readme file in it and there was a link to github and on there there was another iso so I downloaded that the name is: bionicpup32-19.03-230815.iso

[rcrsn51]

the name is: bionicpup32-19.03-230815.iso

I looked at this ISO and it appears to have LESS b43 firmware than previous versions. A member of the Bionic team needs to look at this. There may be a separate package of b43 firmware somewhere on the forum.

[mikeslr]

Edit: First try rerwin's firmware-b43_complete.pet from here, viewtopic.php?p=34278#p34278. AFAIK, firmware is both kernel and architecture 'agnostic', although the 'user-merge' rule now applies to debian/ubuntu. But bionicpup32 was published before that rule came into effect.

The following was written before the first cup of coffee: All things were possible, but not necessarily practical or even realistic.

There are links to other, smaller firmware packages from here, https://www.forum.puppylinux.com/viewto ... 777#p51777 and you may want to try them later. But I'd start with one of gyrog's large packages from here, https://www.mediafire.com/folder/k2j223jzddy9x/firmware as they will more likely include the specific firmware you need. Procedure:
Download the SFS and Right-Click it. Select Rename. For 32-bit Bionicpup, name it fdrv_upupbb_19.03.sfs. Replace the current fdrv with the new, renamed sfs.

[Puppys are very efficient in their use of RAM. However, a 300 Mb package when you only actually need one small file from it is wasteful. There used to be a 'firmware-cutter', now lost. And I don't have programming skills to re-create it].

For your consideration because 32-bit web-browsers capable of accessing today's websites are few and moribund:

"im using a HP Pavilion dv5000 (ES264EA#ABZ) I used a 32 bit os because my cpu (Mobile AMD Sempron(tm) processor 3000+) doesnt support 64 bit."

Not to drive you 'nuts', but are you sure? That your computer came with a 32-bit Windows operating system does not mean its hardware was limited to only running 32-bit operating systems. After the manufacture of 64-bit CPUs became feasible it did not make economic sense for manufacturers to run two production lines, one for 32-bit and one for 64-bit. Microsoft, however, had a lot of 32-bit Windows CDs yet unsold, and could obtain greater profits by selling 64-bit systems at a premium. A 64-bit CPU can run a 32-bit operating system. Hence the practice of only installing 32-bit Windows to computers capable of running 64-bit Windows.

The HP Pavilion dv5000 was manufactured with:
"AMD Turion 64: This is a derivative of the Athlon 64 with SSE3 with nx storage protection, 32 and 64 bit support, integrated memory controller for PC3200 memory, mode for low capacity, HT800 and 2 variants ML with 35 Watt and MB with 25 Watt consumption. Regarding the consumption MT might be very similar to a Pentium M. The speed is moderate and approximately as fast as an Pentium M with equivalent clock speed." https://www.notebookcheck.net/HP-Pavili ... 657.0.html

And while you've indicated that your CPU is a Mobile AMD Sempron(tm) processor 3000+, that CPU has a Data width of 64-bits. https://www.cpu-world.com/CPUs/K8/AMD-M ... KX2BX.html

On the other hand, I may be misinterpreting the above information.

How much RAM does your computer have? Although almost as RAM efficient as 32-bit OS versions, Puppy 64-bit OSes are not quite as efficient: 2 Gb's vs. 1 Gb minimum with 4 Gbs recommended.

[Florian_13]

How much RAM does your computer have? Although almost as RAM efficient as 32-bit OS versions, Puppy 64-bit OSes are not quite as efficient: 2 Gb's vs. 1 Gb minimum with 4 Gbs recommended.

I've got 512 mb of ram

[Florian_13]

@mikeslr THANK YOU SO MUCH IT FINNALY WORKS!!! now all I need is to get my mouse working!