BionicPup32 (UPupBB) (27 June 2020)

[foxpup]

@James Gryphon
I think you are certainly not a noob.
I had very similar remarks when trying out UpupBB, but did not manage to formulate them. I can especially second your last 3 remarks about the missing quickpet and the sfs.
BTW, it's been a while now I've tried Bionic Puppy, so I do not know about the latest fixes.

[jrb]

At the risk of being the noob with a chip on their shoulder, I have to say that I think the current release is actually a step back from Tahr and Xenial pups in overall usability.

As a relative newcomer to the forum, you may not be aware that while Puppy is a team effort, releases are put together by individuals who have the time, energy and ambition for such a project. Over the years several people have done so, but it is exhausting and at times frustrating in that it is impossible to satisfy everybody's wishes. Not that yours are unreasonable but I think PeeBee deserves a great deal of praise and thanks for putting together such a fine and, compared to some other releases, bug free Puppy.

I think it is a worthwhile learning endeavor for any Puppy user to have a go at building a Pup using WoofCE in which you can incorporate any changes you wish. Puppy can also be modified using Remaster although WoofCE does a cleaner job with less chance of including unwanted changes.

I haven't bothered building a custom BionicPup because I find PeeBee's version is working extremely well for me. Possibly the best Puppy I've ever used. But then I've been using Puppy quite a while and don't have the perspective of a newcomer in terms of figuring things out.

Good Luck and Enjoy, J

[B.K. Johnson]

@peebee
Thanks for being so considerate to offer a ndiswrapper with upupbb. I really appreciate the effort. Unfortunately (for me), it isn't working.

I installed the devx although I don't think it is needed.

I installed the pet.
--ndiswrapper appeard in Uninstal in PPM
--ndiswrapper.ko appears at /lib/modules/4.9.96-lxpup-32-pae/misc/ as expected

lsusb returns:
--Bus 001 Device 004: ID 0846:9020 NetGear, Inc. WNA3100(v1) Wireless-N 300 [Broadcom BCM43231]

None of the wizards (Simple Network Setup, Frisbee or Network Wizard) installed via Menu->Setup->Internet Connection Wizard recognizes a wanlo or any other wireless.

When I try to install my Windows driver with Network Wizard, this is the final screen shown..
install_final_shot.png

Screenshot various_screens.png shows various screens when trying to install.

Any ideas?

[peebee]

ndiswrapper with upupbb. I really appreciate the effort. Unfortunately (for me), it isn't working.

Can you do:

Code: Select all

depmod -a
modprobe ndiswrapper

after installing the pet?

What does dmesg and lsmod show? Has ndiswrapper been loaded?

Does your driver work in other pups?

There have been 403 downloads of the pet - but 0 reports its not working....

PB

[B.K. Johnson]

@peebee
Apologies for the delay in answering,
You asked:

Can you do:

Of course, I'm the one who needs it to work.

Code: Select all

depmod -a
modprobe ndiswrapper

after installing the pet?

As stated, the pet is already installed. I have uninstalled and reinstalled it now.

There was no output on invoking the depmod and modprobe commands.

Code: Select all

# depmod -a
# modprobe ndiswrapper
#  

What does dmesg and lsmod show? Has ndiswrapper been loaded?

This is a partial output from dmesg. Note 2 sections: one I recast in red, the other in blue.
The red section references sr1. The system is booted from a SanDisk flash drive which has sr1 as a ROM drive. I don't know if the error noted in the section contributes to the ndiswrapper failure, but I have included it just in case.

The blue section seems to be all ndiswrapper related.

I have the complete dump of dmesg if you want it.

Code: Select all

[color=red]sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf c0 00 00 02 00
blk_update_request: I/O error, dev sr1, sector 196352
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf c0 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 196352
Buffer I/O error on dev sr1, logical block 49088, async page read
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf c1 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 196356
Buffer I/O error on dev sr1, logical block 49089, async page read
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fc 00 00 02 00
blk_update_request: I/O error, dev sr1, sector 196592
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fc 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 196592
Buffer I/O error on dev sr1, logical block 49148, async page read
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 bf fd 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 196596
Buffer I/O error on dev sr1, logical block 49149, async page read
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 be 80 00 00 3c 00
blk_update_request: I/O error, dev sr1, sector 195072
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 be bc 00 00 04 00
blk_update_request: I/O error, dev sr1, sector 195312
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 be 80 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 195072
Buffer I/O error on dev sr1, logical block 48768, async page read
sr 3:0:0:1: [sr1] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
sr 3:0:0:1: [sr1] tag#0 Sense Key : Hardware Error [current]
sr 3:0:0:1: [sr1] tag#0 Add. Sense: No additional sense information
sr 3:0:0:1: [sr1] tag#0 CDB: Read(10) 28 00 00 00 be 81 00 00 01 00
blk_update_request: I/O error, dev sr1, sector 195076
Buffer I/O error on dev sr1, logical block 48769, async page read
Buffer I/O error on dev sr1, logical block 49146, async page read
Buffer I/O error on dev sr1, logical block 49147, async page read
sr 3:0:0:1: [sr1] GET_EVENT and TUR disagree continuously, suppress GET_EVENT events
Buffer I/O error on dev sr1, logical block 49148, async page read
Buffer I/O error on dev sr1, logical block 49149, async page read[/color]
coretemp coretemp.0: Using relative temperature scale!
coretemp coretemp.0: Using relative temperature scale!
udevd[7004]: Process '/sbin/pup_event_backend_modprobe' failed with exit code 1.
ip_tables: (C) 2000-2006 Netfilter Core Team
FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[color=blue]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)
usbcore: registered new interface driver ndiswrapper
udevd[2959]: Specified group 'input' unknown
udevd[2959]: /etc/udev/rules.d/55-cups.rules:5: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
#[/color]

This is the lsmod dump. I saw nothing unusual.

Code: Select all

# lsmod
Module                  Size  Used by
ndiswrapper           170775  0
iptable_filter          1379  0
ip_tables               9689  1 iptable_filter
coretemp                4712  0
hwmon                   6646  1 coretemp
snd_hda_codec_realtek    52969  1
snd_hda_codec_generic    49222  1 snd_hda_codec_realtek
snd_hda_intel          19109  0
snd_hda_codec          68483  3 snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core           40189  4 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
snd_seq_dummy            975  0
snd_seq_oss            23638  0
snd_seq_midi            4030  0
snd_seq_midi_event      4484  2 snd_seq_midi,snd_seq_oss
i915                 1082852  2
snd_rawmidi            14869  1 snd_seq_midi
snd_seq                39399  6 snd_seq_midi_event,snd_seq_dummy,snd_seq_midi,snd_seq_oss
snd_pcsp                6269  0
snd_pcm_oss            33623  0
snd_seq_device          2516  4 snd_seq,snd_rawmidi,snd_seq_midi,snd_seq_oss
snd_mixer_oss          12029  1 snd_pcm_oss
snd_pcm                68161  5 snd_pcm_oss,snd_hda_intel,snd_pcsp,snd_hda_codec,snd_hda_core
snd_timer              15553  2 snd_seq,snd_pcm
snd                    45044  12 snd_pcm_oss,snd_hda_intel,snd_pcsp,snd_mixer_oss,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_generic,snd_seq_device,snd_seq_oss,snd_pcm
i2c_algo_bit            4708  1 i915
e100                   26323  0
lpc_ich                13224  0
drm_kms_helper         99798  1 i915
mii                     3763  1 e100
i2c_i801               11796  0
soundcore               4259  1 snd
sg                     25220  0
syscopyarea             2990  1 drm_kms_helper
sysfillrect             3258  1 drm_kms_helper
i2c_smbus               2489  1 i2c_i801
sysimgblt               2031  1 drm_kms_helper
fb_sys_fops             1034  1 drm_kms_helper
drm                   229096  4 i915,drm_kms_helper
ppdev                   5606  0
parport_pc             21066  0
parport                28570  2 parport_pc,ppdev
#

Has ndiswrapper been loaded?

I assume not, but really don't know how to check.

Does your driver work in other pups?

Yes! I recall some Slacko versions, but more recently, tahr-6.0, 6.0.2 (currently using), tahr-6.0.5 and tahr-6.0.6.

There have been 403 downloads of the pet - but 0 reports its not working...

Doesn't mean it is being used, PB. And looked at from the opposite perspective, there are 0 reports of success. The only persons I recall claiming to use ndiswrapper are OscarTalks and rcrsn51. And I don't think either of the two use it regularly anymore.

Some time ago while researching ndiswrapper, I saw reference in another forum to tainted kernel - see blue section above. I'll see if I can find it.
[EDIT]
code does not allow for colours within. Sorry!

[peebee]

Hi @BKJ

Maybe there is now native Linux support for your wifi and that driver is claiming your device stopping ndiswrapper using it? (Although I don't see anything likely in the lsmod output). See screenie from net-wiz....

ndiswrapper is installing correctly as shown by the lsmod output - the kernel taints are just warnings that "something uncertified" is being added to the kernel and can be ignored.

Cheers PB

[perdido]

@peebee

--Bus 001 Device 004: ID 0846:9020 NetGear, Inc. WNA3100(v1) Wireless-N 300 [Broadcom BCM43231]

More info about your driver & ndiswrapper

http://ndiswrapper.sourceforge.net/wiki ... ar_WNA3100

.

[rcrsn51]

The only persons I recall claiming to use ndiswrapper are OscarTalks and rcrsn51. And I don't think either of the two use it regularly anymore.

I used to own the same Netgear adapter as B.K. I can't remember the last time I saw it work with ndiswrapper - possibly with an early 4-series kernel.

@perdido: Check the date at the bottom of that web page.

[B.K. Johnson]

Thanks for the response, perdido, but as rcrsn51 notes it's old and I got a 404 when I tried to download the driver.

[perdido]

@perdido: Check the date at the bottom of that web page.

Did not see a "use by" date, figured it could be useful info.

Thanks for the response, perdido, but as rcrsn51 notes it's old and I got a 404 when I tried to download the driver.

T̶h̶e̶ ̶d̶r̶i̶v̶e̶r̶ ̶h̶a̶s̶ ̶n̶o̶t̶ ̶b̶e̶e̶n̶ ̶n̶e̶e̶d̶e̶d̶ ̶s̶i̶n̶c̶e̶ ̶v̶e̶r̶s̶i̶o̶n̶ ̶1̶.̶5̶7̶ ̶o̶f̶ ̶n̶d̶i̶s̶w̶r̶a̶p̶p̶e̶r̶.̶ ̶
I thought you might be interested in some of the terminal commands farther down the page, not the driver.

Code: Select all

bcmwlhigh5 works under ndiswrapper. However driver may not be loaded by default or matching with device may be wrong. If this is the case, when you list installed drivers, you will see an output similar to this:

felmas@fachoper:~$ ndiswrapper -l
bcmwlhigh5: driver installed

You won't see this line after above output:

device (0846:9020) present

To fix it, you should run:

felmas@fachoper:~$ ndiswrapper -a 0846:9020 bcmwlhigh5

Moreover, driver can require some configuration.

felmas@fachoper:~$ dmesg -c
Jan 15 17:12:28 fachoper kernel: [67654.005971] ndiswrapper (iw_set_freq:437): setting configuration failed (00010003)

In my case, I checked correct values in another machine that is already connected.

felmas@veteran:~$ iwconfig
lo    no wireless extensions.

eth0  no wireless extensions.

wlan0 IEEE 802.11abg ESSID:"your ID"
      Mode:Managed Frequency:2.412 GHz Access Point: "some MAC"
      Bit Rate="some rate" Tx-Power=15 dBm
      Retry logn limit:"some trial number" RTS thr:off Fragment thr:off
      Power Management:off

.

.

[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.....