BionicPup32 (UPupBB) (27 June 2020)

[B.K. Johnson]

@perdido
The post date and the driver got my immediate attention. and on that I made my post. After that, I did see the commands and in fact captured them to look at when I switch back into upupbb. I haven't done so yet. I should have mentioned that in my post. My apologies.

I am surprised to read that

The driver has not been needed since version 1.57 of ndiswrapper.

1. Development is still occurring over at ubuntu - now up to 1.60.6, used with "trusty" and being used in cooperation with "Cuttlefish", the next Ubuntu. Sorry, I don't have the link readily at hand.
2. bcmhigh5.inf/? is the Windows 32 bit driver, so it is still being used. It would seem that the mechanics of setting ndiswrapper up properly is the problem. The commands intend to fix it.
3. So it would seem, those cl commands are not replacing the need for ndiswrapper; the commands do not obviate the need for a regular driver. Regardless of the version of ndiswrapper, the windows driver will have to be accessed somehow.

Thanks again. As soon as I can, I'll try those commands and report bacl.

[perdido]

3. So it would seem, those cl commands are not replacing the need for ndiswrapper; the commands do not obviate the need for a regular driver.
Regardless of the version of ndiswrapper, the windows driver will have to be accessed somehow.

Hi B.K. Johnson,
I mis-spoke, I should have said the custom compilation of ndiswrapper is no longer needed after version 1.57, the wireless driver from windows is still needed.
Sorry about the confusion.

It will be interesting to see if any of those terminal commands work.

.

[B.K. Johnson]

@perdido
As promised, feedback on the cli commands issued by the poster.

bcmwlhigh5 that the poster refers to is the Windows driver. During the processing of Network Wizard, I navigate to where it is located because a driver for Broadcom BCM43231 is not among those listed.

The author states: "...driver may not be loaded" or "matching with device may be wrong." yet the driver is listed as installed with

Code: Select all

ndiswrapper -l

. Fuzzy logic! When I issue the same command, what I get is

Code: Select all

ndiswrapper: command not found

Clearly, the driver is not loaded; IT ISN'T EVEN INSTALLED. Where should it be? The ndiswrapper.ko is in the correct location. But what is in it? I don't have a hex dump software to find out. All the other commands in the post are then meaningless because they are based on the positive response from ndiswrapper -l.

[EDIT]
In your last post, you wrote:

Code: Select all

.I should have said the custom compilation of ndiswrapper is no longer needed after version 1.57, the wireless driver from windows is still needed.
Sorry about the confusion.

OK. And by "custom compilation" we mean it does not have to be compiled with a particular kernal? Then version 1.57, for example, could be used OOTB on any puppy? Where can I find it?

[perdido]

@perdido
As promised, feedback on the cli commands issued by the poster.

bcmwlhigh5 that the poster refers to is the Windows driver. During the processing of Network Wizard, I navigate to where it is located because a driver for Broadcom BCM43231 is not among those listed.

The author states: "...driver may not be loaded" or "matching with device may be wrong." yet the driver is listed as installed with

Code: Select all

ndiswrapper -l

. Fuzzy logic! When I issue the same command, what I get is

Code: Select all

ndiswrapper: command not found

Clearly, the driver is not loaded; IT ISN'T EVEN INSTALLED. Where should it be? The ndiswrapper.ko is in the correct location. But what is in it? I don't have a hex dump software to find out. All the other commands in the post are then meaningless because they are based on the positive response from ndiswrapper -l.

[EDIT]
In your last post, you wrote:

Code: Select all

.I should have said the custom compilation of ndiswrapper is no longer needed after version 1.57, the wireless driver from windows is still needed.
Sorry about the confusion.

OK. And by "custom compilation" we mean it does not have to be compiled with a particular kernal? Then version 1.57, for example, could be used OOTB on any puppy? Where can I find it?

Hi B.K. Johnson,
ndiswrapper is kernel specific.
ndiswrapper just no longer needs to be compiled with

Code: Select all

 wstdcall NTSTATUS WIN_FUNC(IoUnregisterPlugPlayNotification,1) 
(void *tag)
{
      TRACE2("%p", tag);
      TODO(); /* Probably Not, legacy function abandoned in Windows 7 */
      IOEXIT(return STATUS_SUCCESS); /* Linux doesn't use it either */
}

added to the ntoskernal_io.c source file
since version 1.57 of ndiswrapper.

I installed ndiswrapper to upup bionic and got same result as you with terminal commands.
Perhaps the info on that page is obsolete as rcrsn51 suggested.

.

[B.K. Johnson]

Hello perdido
This conversation is drawing to a close, but one last question. What version of ndiswrapper did you compile?

[peebee]

It does rather look like the ndiswrapper .pet is malformed and is missing some binaries which should be in /sbin and /usr/sbin.....

I will investigate.....

Surprising that nobody out of 400+ downloads has reported a problem before tho!!

[OscarTalks]

Hi PeeBee,

In case it helps, the ndiswrapper 1.61.1 which I compiled for several kernels installs /sbin/loadndisdriver and /usr/sbin/ndiswrapper which is a perl script, plus /usr/sbin/ndiswrapper-buginfo

[B.K. Johnson]

peebee wrote:

It does rather look like the ndiswrapper .pet is malformed and is missing some binaries which should be in /sbin and /usr/sbin.....

Whew! I know there are folks who don't relish me arguing a point relentlessly. But I'm a logical, critical thinker. I do feel vindicated.

I will investigate.....

Thank you, good sir. What was it that spurred you on?

Surprising that nobody out of 400+ downloads has reported a problem before tho!!

No surprise to me. Like I said, of the regulars here, only myself, OscarTalks and rcrsn51 have used ndiswrapper in the last 4 years. It is either downloaded without the immediate need (guilty of that myself) or more seriously, they are Windows refugees who tried it, had it fail and moved on with a bad puppy experience. Our developers and the community should be mindful of the fact that many refugees will have modems that don't have Linux drivers. One way of welcoming them is to have ndiswrapper that works for every puppy, there is one for every kernel. I must confess to a little selfishness. When upupbb was released, I tried it; it failed and mindful of the belittering and urgings to simply buy a Linux modem, I said nothing. It was only when posts began to promote upupbb as the "official" puppy that I felt I could not ignore the possibility of refugees regretting trying. I'm off my soapbox now. I don't feel as guilty.

[perdido]

Hello perdido
This conversation is drawing to a close, but one last question. What version of ndiswrapper did you compile?

Hi B.K. Johnson,
I had not done a compile, just tried the 1.61 version from this thread.

After you asked, I compiled a fresh ndiswrapper 1.61 and am attaching it to this post.
----

Attachment deleted.

[peebee]

Here is my updated pet

There is a subtle difference between the 2 pets - so if BKJ can test both that would be great.....

[B.K. Johnson]

@perdido Yours did not work. On the ndiswrapper -l command, I received a "not found" error.

@peebee
Close but no cigar! The collage of windows in the screenshot, collage.png, are typical screens in a successful installation and invocation except for that at the bottom left which is intermittent.

collage.png
The post perdido referenced.

So, I tried the commands in the post perdido referenced.
Whereas the poster did not get any response from the ndiswrapper -l command, I did.

Code: Select all

# ndiswrapper -l
bcmwlhigh5 : driver installed
    device (0846:9020) present

You can see the entire dmesg -c dump in the attachment dmesg-c-dump.html, but this excerpt I think is the informative section.

There were several instances of:

Code: Select all

pup_event_backend_modprobe' failed with exit code 1

specific reference to ndiswrapper

Code: Select all

ndiswrapper: loading out-of-tree module taints kernel.
ndiswrapper: module verification failed: signature and/or required key missing - tainting kernel
Disabling lock debugging due to kernel taint
ndiswrapper: module license taints kernel.
ndiswrapper version 1.61 loaded (smp=yes, preempt=no)
udevd[2876]: Specified group 'input' unknown
udevd[2876]: /etc/udev/rules.d/55-cups.rules:5: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
usbcore: registered new interface driver ndiswrapper
usb 1-3: USB disconnect, device number 2
usb 1-4: new high-speed USB device number 9 using ehci-pci
udevd[13878]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
# 

iwconfig did not find the wireless, wlano

Code: Select all

# iwconfig
lo        no wireless extensions.

enp2s8    no wireless extensions.

Next up was ndiswrapper -v.
You should find significant clues in the result.

Code: Select all

#  ndiswrapper -v
/sbin/loadndisdriver: /sbin/loadndisdriver: cannot execute binary file
utils version is too old!
utils version '' is incompatible with utils version needed by driver ('1.9')!
utils version: '', utils version needed by module: '1.9'
module details:
filename:       /lib/modules/4.9.96-lxpup-32-pae/misc/ndiswrapper.ko
version:        1.61
vermagic:       4.9.96-lxpup-32-pae SMP mod_unload modversions 686

You may need to upgrade driver and/or utils to latest versions available at
http://ndiswrapper.sourceforge.net

[peebee]

utils version '' is incompatible with utils version needed by driver ('1.9')!

Is odd! Looks like version number is not set....no idea why!

[B.K. Johnson]

utils version is too old!

I am not in upupbb ATM so can't look, but looking in tahr-6.0.2 at /sbin/, I see loadndiswrapper-1.9.
Where/How can we get an updated loadndiswrapper?

[peebee]

7024ef81c21ffbf33cfd28aa47df4eb8 upupbb-18.05+13.iso

{delta} to be applied to original 18.05.iso

[peebee]

New ndiswrapper pet above and in post #3

Hope this one works.....@BKJ?

[perdido]

Latest VirtualBox 5.2.18 SFS for Upup Bionic 18.05
http://murga-linux.com/puppy/viewtopic. ... 10#1005510

.

[Billtoo]

I installed to the hard drive of my Acer laptop:

System: Host: puppypc23791 Kernel: 4.9.96-lxpup-32-pae i686 bits: 32 Desktop: JWM 2.3.7 Distro: UPupBB 18.05
Machine: Device: laptop System: Acer product: Aspire V5-571P v: V2.17 serial: NXM49AA03531512EC36600
Mobo: Acer model: Aspire V5-571P v: V2.17 serial: NBM491100831501E946600
UEFI [Legacy]: Phoenix v: V2.17 date: 02/27/2013
Battery BAT0: charge: 26.9 Wh 95.5% condition: 28.1/37.0 Wh (76%)
CPU: Dual core Intel Core i3-3227U (-MT-MCP-) speed/max: 900/1901 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.Org 1.19.6 driver: intel Resolution: 1366x768@60.10hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile x86/MMX/SSE2 version: 4.2 Mesa 18.0.5
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom Limited BCM43228 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 515.6GB (3.0% used)
Weather: Conditions: 48 F (9 C) Time: September 23, 1:13 PM EDT
Info: Processes: 194 Uptime: 59 min Memory: 192.6/5865.4MB Client: Shell (bash) inxi: 2.3.56

Added some applications with PPM.
Touchscreen is supported.

Thanks.

[oldaolgeezer]

peebee:

I have a problem when a USB flash drive is plugged into my Woof-CE 32bit Ubuntu Bionic Beaver:

On my DELL 1545 laptop, I don't get the traditional Puppy behavior when
I plug in my USB flash drive.

Basically, it appears nothing happens !

The sda1 icon (of the boot drive) is always displayed in the
upper left side of the screen, but the sdb1 icon never displays.

Note: I am booting with grub4dos from my Sandisk 32 gig SD card
(booting from the built-in SD card slot frees up a USB port for me.
My laptop has only three USB ports (one is used for my mouse)
and I have no hard disk in the laptop.)

I have "discovered" a work-around (after plugging in my USB flash drive)
by refreshing the pMount utility window and then I can mount my sdb1
flash drive files and have ROX copy files without any problem.

(booting the same laptop and choosing slacko 5.7.0 with grub4dos
shows the expected old Puppy USB flash drive behavior (the sdb1 icon
shows up at the bottom left of the screen) and clicking on that icon opens ROX filer.)

Thanks for any help

===

Displaying my dmesg log shows the following messages:

usb 2-3: new high-speed USB device number 3 using ehci-pci
usb-storage 2-3:1.0: USB Mass Storage device detected
udevd[2783]: Specified group 'input' unknown
udevd[2783]: /etc/udev/rules.d/55-cups.rules:5: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
scsi host1: usb-storage 2-3:1.0
udevd[12652]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
scsi 1:0:0:0: Direct-Access SanDisk Cruzer Edge 1.26 PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI removable disk
udevd[12677]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
udevd[12677]: Process '/usr/local/pup_event/frontend_change add sdb1' failed with exit code 1.

===

I downloaded UPupBB 18.05 and verified the checksum from:
http://distro.ibiblio.org/puppylinux/pu ... -18.05.htm

===

My 32bit Ubuntu Bionic Beaver (18.05) hardware info:

Motherboard Vendor: Dell Inc.
Product Name: 0G848F

BIOS Vendor: Dell Inc.
Version: A06
Release Date: 04/09/2009

Genuine Intel(R) CPU 585 @ 2.16GHz
Max Speed: 2167 MHz
Current Speed of Core
Core Count: 1
Thread Count: 1

Personal Storage File:
Name: /upupbb-18/upupbbsave.4fs
Total Size: 768 MB
Free Space: 195 MB
Location: partition sda1

Memory Allocation:
Total RAM: 1976 MB
Used RAM: 1833 MB
Free RAM: 143 MB

Development:
Bash: 4.4.19
Geany: 1.29
Gtkdialog: 0.8.4
Perl: 5.26.1
Python: 2.7.15rc1
Yad: 0.40.3 (GTK+ 2.24.32)
--
busybox: 1.28.3
dhcpcd: 6.7.1
Glibc: 2.27
OpenSSL: 1.1.0g 2 Nov 2017, built on: reproducible build, date unspecified
wpa_supplicant: 2.6

===

[peebee]

Hi @oldaolgeezer

Plugging a usb flash drive into a pristine install of upupbb works OK for me....

...however there are errors in dmesg which shouldn't be there so I've raised a woof-ce issue

If you go into System -> Puppy Event Manager

are both the 2 boxes ticked?

Is your system a pristine install or have you added stuff? Can you test a pristine install please?

[oldaolgeezer]

Thanks peebee for answering so quickly.

On my UPupBB with my save file, I think I only installed:
palemoon 28.1.0 32 bit (I may have let it update
itself), calibre 2.18 and a wallpaper jpg.

and yes, in Puppy Event Manager, both boxes are checked.

only the sda1 icon is displayed on upper left side of screen,
when my flash drive is plugged in, the sda1 icon remains
(as expected, but the pMount utility window also displays
without me clicking on anything but only offers to mount sdb1.
The pMount window does not show sda1.)

================

After rebooting UPupBB with pfix=ram and setting only my time zone:
when my flash drive is plugged in, both the sda1 icon
and sdb1 icon display on upper left side of screen
(as expected, but the pMount utility window also displays
without me clicking on anything but only offers to mount sdb1.
The pMount window does not show sda1.)

With the with pfix=ram test, dmesg shows:

usb 2-3: new high-speed USB device number 3 using ehci-pci
usb-storage 2-3:1.0: USB Mass Storage device detected
scsi host1: usb-storage 2-3:1.0
udevd[8593]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
scsi 1:0:0:0: Direct-Access SanDisk Cruzer Edge 1.26 PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI removable disk
udevd[8621]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
udevd[8649]: Process '/usr/local/pup_event/frontend_change add sdb1' failed with exit code 1.
#

======================

When I reboot using the same SD card to load the older Puppy
slacko 5.7.0, and I plug in the same flash drive mentioned above,
both the sda1 icon and sdb1 icon display on lower left side of screen.
and the pMount utility does not display on its own.

Thanks for any help or comments.