BionicPup32 (UPupBB) (27 June 2020)
Installed onto 3 old laptops....
IBM Thinkpad 600:
Pentium II (Deschutes)
Max Speed: 266 MHz
Current Speed of Core
Memory Allocation:
Total RAM: 141 MB
VGA compatible controller:
+ Neomagic Corporation NM2160 [MagicGraph 128XD] (rev 01)
+ Video RAM: 16M
Boots, runs (incredibly slowly - but look at amount of ram - thrashing swap) but browser bombs as it needs SSE2 (probably)
HP-550:
Intel(R) Celeron(R) CPU 550 @ 2.00GHz
Max Speed: 2000 MHz
Memory Allocation:
Total RAM: 2005 MB
VGA controller [0300]: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a12] (rev 0c)
+ Video RAM: 256M
Boots and runs quite well.
Samsung-NC110:
Intel(R) Atom(TM) CPU N570 @ 1.66GHz
Max Speed: 3300 MHz
Memory Allocation:
Total RAM: 2003 MB
VGA controller [0300]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02)
+ Video RAM: 256M
Also boots and runs quite well
Asus X551:
Intel(R) Celeron(R) CPU N2840 @ 2.16GHz
Max Speed: 2400 MHz
Memory Allocation:
Total RAM: 3834 MB
VGA controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)
• Video RAM: 256M
Boots and runs fine
So I would say that 1.66GHz single core with SSE2 instruction set and 1GB of RAM is probably the minimum specs. unless anyone reports differently....
IBM Thinkpad 600:
Pentium II (Deschutes)
Max Speed: 266 MHz
Current Speed of Core
Memory Allocation:
Total RAM: 141 MB
VGA compatible controller:
+ Neomagic Corporation NM2160 [MagicGraph 128XD] (rev 01)
+ Video RAM: 16M
Boots, runs (incredibly slowly - but look at amount of ram - thrashing swap) but browser bombs as it needs SSE2 (probably)
HP-550:
Intel(R) Celeron(R) CPU 550 @ 2.00GHz
Max Speed: 2000 MHz
Memory Allocation:
Total RAM: 2005 MB
VGA controller [0300]: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a12] (rev 0c)
+ Video RAM: 256M
Boots and runs quite well.
Samsung-NC110:
Intel(R) Atom(TM) CPU N570 @ 1.66GHz
Max Speed: 3300 MHz
Memory Allocation:
Total RAM: 2003 MB
VGA controller [0300]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02)
+ Video RAM: 256M
Also boots and runs quite well
Asus X551:
Intel(R) Celeron(R) CPU N2840 @ 2.16GHz
Max Speed: 2400 MHz
Memory Allocation:
Total RAM: 3834 MB
VGA controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)
• Video RAM: 256M
Boots and runs fine
So I would say that 1.66GHz single core with SSE2 instruction set and 1GB of RAM is probably the minimum specs. unless anyone reports differently....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Upupbb-18.05+11 quite happy on Pentium M with 750 MB RAM.
Frugal install on HD.
Grub4Dos booting in approx. 75sec.
Reporting using the provided Light browser.
Web connection using SNS with TP-Link (Ralink RT73) USB wifi dongle.
Pup-SysInfo Hardware Report (Summary), Tue 11 Sep 2018
Processes: 163 total, 2 running
▶—— BASE SYSTEM ——◀
Product Name: HP Compaq nc8000 (PQ168PA#ABG)
BIOS Vendor: Hewlett-Packard
Version: 68BAR Ver. F.12
Release Date: 08/17/2004
Intel(R) Pentium(R) M processor 1.60GHz
Max Speed: 1600 MHz
Current Speed of Core
meltdown : Vulnerable
spectre_v1 : Mitigation : __user pointer sanitization
spectre_v2 : Mitigation : Full generic retpoline
Personal Storage: RAM Disk
Size Used Free Use%
372M 260M 113M 70%
Memory Allocation:
Total RAM: 743 MB
Used RAM: 684 MB
Free RAM: 59 MB
Buffers: 45 MB
Cached: 407 MB
Total Swap: 0 MB
Free Swap: 0 MB
Actual Used RAM: 232 MB Used - (buffers + cached)
Actual Free RAM: 511 MB Free + (buffers + cached)
Linux Kernel: 4.9.96-lxpup-32-pae (i686)
Kernel Version: #1 SMP Thu Apr 26 11:45:00 +08 2018
Build GCC: 7.3.0
PAE Enabled: Yes
Kernel Command Line:
psubdir=BB forcepae
Distro: UPupBB 18.05
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm
PUPMODE=5
PUPSFS=sda5,ext2,/BB/puppy_upupbb_18.05.sfs
PUPSAVE=
▶—— System Processes (top) ——◀
top - 20:06:07 up 16 min, 2 users, load average: 0.49, 0.65, 0.45
Tasks: 163 total, 1 running, 162 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.5 us, 13.8 sy, 0.0 ni, 71.9 id, 1.7 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem : 761604 total, 69356 free, 229992 used, 462256 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 133312 avail Mem
▶—— Audio Devices ——◀
Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
• Kernel Driver: snd_intel8x0
• Memory Used: 22.84 KB
• Path: /lib/modules/4.9.96-lxpup-32-pae/kernel/sound/pci/snd-intel8x0.ko
• Description: Intel 82801AA, 82901AB, i810, i820, i830, i840, i845, MX440; SiS 7012; Ali 5455
▶—— Video ——◀
Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: radeon
• Loaded Modules: ati dbe dri2 evdev exa fb fbdevhw glx libinput ramdac synaptics
• X.Org version: 1.19.6
Frugal install on HD.
Grub4Dos booting in approx. 75sec.
Reporting using the provided Light browser.
Web connection using SNS with TP-Link (Ralink RT73) USB wifi dongle.
Pup-SysInfo Hardware Report (Summary), Tue 11 Sep 2018
Processes: 163 total, 2 running
▶—— BASE SYSTEM ——◀
Product Name: HP Compaq nc8000 (PQ168PA#ABG)
BIOS Vendor: Hewlett-Packard
Version: 68BAR Ver. F.12
Release Date: 08/17/2004
Intel(R) Pentium(R) M processor 1.60GHz
Max Speed: 1600 MHz
Current Speed of Core
meltdown : Vulnerable
spectre_v1 : Mitigation : __user pointer sanitization
spectre_v2 : Mitigation : Full generic retpoline
Personal Storage: RAM Disk
Size Used Free Use%
372M 260M 113M 70%
Memory Allocation:
Total RAM: 743 MB
Used RAM: 684 MB
Free RAM: 59 MB
Buffers: 45 MB
Cached: 407 MB
Total Swap: 0 MB
Free Swap: 0 MB
Actual Used RAM: 232 MB Used - (buffers + cached)
Actual Free RAM: 511 MB Free + (buffers + cached)
Linux Kernel: 4.9.96-lxpup-32-pae (i686)
Kernel Version: #1 SMP Thu Apr 26 11:45:00 +08 2018
Build GCC: 7.3.0
PAE Enabled: Yes
Kernel Command Line:
psubdir=BB forcepae
Distro: UPupBB 18.05
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm
PUPMODE=5
PUPSFS=sda5,ext2,/BB/puppy_upupbb_18.05.sfs
PUPSAVE=
▶—— System Processes (top) ——◀
top - 20:06:07 up 16 min, 2 users, load average: 0.49, 0.65, 0.45
Tasks: 163 total, 1 running, 162 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.5 us, 13.8 sy, 0.0 ni, 71.9 id, 1.7 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem : 761604 total, 69356 free, 229992 used, 462256 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 133312 avail Mem
▶—— Audio Devices ——◀
Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
• Kernel Driver: snd_intel8x0
• Memory Used: 22.84 KB
• Path: /lib/modules/4.9.96-lxpup-32-pae/kernel/sound/pci/snd-intel8x0.ko
• Description: Intel 82801AA, 82901AB, i810, i820, i830, i840, i845, MX440; SiS 7012; Ali 5455
▶—— Video ——◀
Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: radeon
• Loaded Modules: ati dbe dri2 evdev exa fb fbdevhw glx libinput ramdac synaptics
• X.Org version: 1.19.6
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Yah; I have to agree with perdido. This Puppy is definitely ready to take over the 'flagship' spot.....and Bob's right, too. You detail me one OS that went 'public' without one single bug in it.....and I'll stand you a beer or three at your favourite watering-hole. There's no such thing as perfection in software, no matter how much of its building may be automated.....because in the long run, it was still written by humans at some point....
...and we are fallible.
With regard to the 32-bit vs 64-bit debate.....what difference does that make? I've been running Puppies on a 64-bit machine ever since I started with them 4½ years ago, and my characterisation, quite simply, is this:-
a.) That 32-bit Pups run blazingly fast.
b.) That 64-bit Pups run no faster, but just seem smoother, somehow.....it's kinda hard to explain. (Maybe it's only my specific perceptions that give this impression; I can't say.)
My own interpretation of the mechanics of this are quite simple; that because of the way Puppy runs (in RAM for the duration of a session), a lot of the subjective, 'perceived' operating speed is going to be down to the latencies & access times of whatever generation of RAM your system uses (DDR1, DDR2, DDR3, whatever). Naturally, CPU generation, motherboard design factors, and quantity of RAM, will also contribute.....but the native characteristics of the RAM itself must have a considerable impact on the overall 'experience'.
How many 'Puppians' actually think that far into it?
Most of my favourites are 32-bit, of course, since Puppy's past is full of absolute gems; many of which are still perfectly usable as 'daily drivers'.
But definitely; Upup BB is ready for 'prime time'. Go for it, Peter!
Mike.
...and we are fallible.
With regard to the 32-bit vs 64-bit debate.....what difference does that make? I've been running Puppies on a 64-bit machine ever since I started with them 4½ years ago, and my characterisation, quite simply, is this:-
a.) That 32-bit Pups run blazingly fast.
b.) That 64-bit Pups run no faster, but just seem smoother, somehow.....it's kinda hard to explain. (Maybe it's only my specific perceptions that give this impression; I can't say.)
My own interpretation of the mechanics of this are quite simple; that because of the way Puppy runs (in RAM for the duration of a session), a lot of the subjective, 'perceived' operating speed is going to be down to the latencies & access times of whatever generation of RAM your system uses (DDR1, DDR2, DDR3, whatever). Naturally, CPU generation, motherboard design factors, and quantity of RAM, will also contribute.....but the native characteristics of the RAM itself must have a considerable impact on the overall 'experience'.
How many 'Puppians' actually think that far into it?
Most of my favourites are 32-bit, of course, since Puppy's past is full of absolute gems; many of which are still perfectly usable as 'daily drivers'.
But definitely; Upup BB is ready for 'prime time'. Go for it, Peter!
Mike.
-
- Posts: 6
- Joined: Tue 26 Jun 2018, 03:40
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.
I had a long rant, but I think I can condense it to a few points which are slightly less rambling:
1) There's a lot of unlabelled buttons and icons in the interface, which is bad for discoverability. Some things (like the new-default, non-traditional Puppy desktop, with its unlabelled dock) can be changed (although they shouldn't have to be). Others (like the buttons in the fringes of PupControl) can't be.
2) When it comes to the interface, theming, etc., there's a lot of buttons that send you to the same places as are linked to in another (apparently unrelated) configuration panel, without it being clear that that's where you're going. What's worse, it's possible and very common to then have buttons that go right back to where you came from, so you can very well end up with the same tool in multiple windows. Anything involving pTheme, as well as the Theme Switcher, are good examples of this.
3) Along the same line, there seem to be a lot of configuration tools, options and buttons in various parts of the interface that do or control the same things when just one tool would suffice (or maybe two -- provided that there's one clearly labelled "Quick" setup that actually is easier to use, and then the real, full config tool, with advanced options that aren't available in the other).
4) Desktop Icons arrangement names need some work. For example, it isn't clear exactly what "Minimal" and "Bin" are. What's worse, continuing in the same theme as the last two points, I think there is actually a control panel somewhere else that controls the same thing, offers more options, and has full text descriptions, but it's buried in something like the Event Manager that isn't obviously related to the desktop, and is hard to find if you don't know right where it is.
5) No Quickpet is not good for quick setup.
6) SFS tools seem a bit hit and miss. The package manager and universal installer in the dock's second menu option for the SFS manager didn't do anything when I tried it (admittedly, in VirtualBox). Based on the package manager, though, and the fact that I installed a SFS manager from a Pup repo, I'm not sure it's even built in. If that's so, having a menu option for something that's not included in the base system seems kind of misleading.
7) Not sure if this is a problem with the SFS manager or UPupBB, but I might as well hit on it while I'm here. The SFS manager wants "Puppy to be installed" before it runs. That's a weak error message. Installed to what? If they mean that they need a save file, that's one thing. That said, though, I'm not sure why it should simply refuse to run. If nothing it does gets saved, that's my problem.
I guess this is probably Joe's 'fault', not yours, but I do miss the Motif option and non-gradient window themes. Figured I'd throw that in somewhere.
If you would like more detail or explanation of these complaints, I'd be happy to provide them. Puppy is in my opinion the greatest distro for flash drives. In fact, if Puppy doesn't work out over the long haul, I'm not sure there's anywhere else to go. And I'm not keen on staying with Xenial Ubuntu as a base forever and running increasingly old software just because I don't like new themes/the interface/whatever.
I had a long rant, but I think I can condense it to a few points which are slightly less rambling:
1) There's a lot of unlabelled buttons and icons in the interface, which is bad for discoverability. Some things (like the new-default, non-traditional Puppy desktop, with its unlabelled dock) can be changed (although they shouldn't have to be). Others (like the buttons in the fringes of PupControl) can't be.
2) When it comes to the interface, theming, etc., there's a lot of buttons that send you to the same places as are linked to in another (apparently unrelated) configuration panel, without it being clear that that's where you're going. What's worse, it's possible and very common to then have buttons that go right back to where you came from, so you can very well end up with the same tool in multiple windows. Anything involving pTheme, as well as the Theme Switcher, are good examples of this.
3) Along the same line, there seem to be a lot of configuration tools, options and buttons in various parts of the interface that do or control the same things when just one tool would suffice (or maybe two -- provided that there's one clearly labelled "Quick" setup that actually is easier to use, and then the real, full config tool, with advanced options that aren't available in the other).
4) Desktop Icons arrangement names need some work. For example, it isn't clear exactly what "Minimal" and "Bin" are. What's worse, continuing in the same theme as the last two points, I think there is actually a control panel somewhere else that controls the same thing, offers more options, and has full text descriptions, but it's buried in something like the Event Manager that isn't obviously related to the desktop, and is hard to find if you don't know right where it is.
5) No Quickpet is not good for quick setup.
6) SFS tools seem a bit hit and miss. The package manager and universal installer in the dock's second menu option for the SFS manager didn't do anything when I tried it (admittedly, in VirtualBox). Based on the package manager, though, and the fact that I installed a SFS manager from a Pup repo, I'm not sure it's even built in. If that's so, having a menu option for something that's not included in the base system seems kind of misleading.
7) Not sure if this is a problem with the SFS manager or UPupBB, but I might as well hit on it while I'm here. The SFS manager wants "Puppy to be installed" before it runs. That's a weak error message. Installed to what? If they mean that they need a save file, that's one thing. That said, though, I'm not sure why it should simply refuse to run. If nothing it does gets saved, that's my problem.
I guess this is probably Joe's 'fault', not yours, but I do miss the Motif option and non-gradient window themes. Figured I'd throw that in somewhere.
If you would like more detail or explanation of these complaints, I'd be happy to provide them. Puppy is in my opinion the greatest distro for flash drives. In fact, if Puppy doesn't work out over the long haul, I'm not sure there's anywhere else to go. And I'm not keen on staying with Xenial Ubuntu as a base forever and running increasingly old software just because I don't like new themes/the interface/whatever.
[b]Operating [i]Xenialpup 7.5 CE[/i][/b]
@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.
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.
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.James Gryphon wrote: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.
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
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
@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?
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?
- Attachments
-
- various_screens.png
- collage of screens
- (165.63 KiB) Downloaded 75 times
-
- install_final_shot.png
- last pop-up on installation
- (2.54 KiB) Downloaded 1033 times
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
Can you do:B.K. Johnson wrote:ndiswrapper with upupbb. I really appreciate the effort. Unfortunately (for me), it isn't working.
Code: Select all
depmod -a
modprobe ndiswrapper
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
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
@peebee
Apologies for the delay in answering,
You asked:
There was no output on invoking the depmod and modprobe commands.
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.
This is the lsmod dump. I saw nothing unusual.
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!
Apologies for the delay in answering,
You asked:
Of course, I'm the one who needs it to work.Can you do:
Code: Select all
depmod -a
modprobe ndiswrapper
As stated, the pet is already installed. I have uninstalled and reinstalled it now.after installing the pet?
There was no output on invoking the depmod and modprobe commands.
Code: Select all
# depmod -a
# modprobe ndiswrapper
#
This is a partial output from dmesg. Note 2 sections: one I recast in red, the other in blue.What does dmesg and lsmod show? Has ndiswrapper been loaded?
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]
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
#
I assume not, but really don't know how to check.Has ndiswrapper been loaded?
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.Does your driver work in other pups?
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.There have been 403 downloads of the pet - but 0 reports its not working...
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!
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
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
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
- Attachments
-
- Screenshot.png
- (23.95 KiB) Downloaded 880 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
More info about your driver & ndiswrapperB.K. Johnson wrote:@peebee
--Bus 001 Device 004: ID 0846:9020 NetGear, Inc. WNA3100(v1) Wireless-N 300 [Broadcom BCM43231]
http://ndiswrapper.sourceforge.net/wiki ... ar_WNA3100
.
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.B.K. Johnson wrote: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.
@perdido: Check the date at the bottom of that web page.
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
Thanks for the response, perdido, but as rcrsn51 notes it's old and I got a 404 when I tried to download the driver.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Did not see a "use by" date, figured it could be useful info.rcrsn51 wrote: @perdido: Check the date at the bottom of that web page.
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̶.̶ ̶B.K. Johnson wrote:Thanks for the response, perdido, but as rcrsn51 notes it's old and I got a 404 when I tried to download the driver.
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
.
Last edited by perdido on Mon 17 Sep 2018, 02:18, edited 1 time in total.
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
@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
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.
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
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.The driver has not been needed since version 1.57 of ndiswrapper.
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.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Hi B.K. Johnson,B.K. Johnson wrote: 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.
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.
.
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
@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. Fuzzy logic! When I issue the same command, what I get is
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:
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?
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
Code: Select all
ndiswrapper: command not found
[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.
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
B.K. Johnson wrote:@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. Fuzzy logic! When I issue the same command, what I get isCode: Select all
ndiswrapper -l
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.Code: Select all
ndiswrapper: command not found
[EDIT]
In your last post, you wrote: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?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.
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 */
}
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.
.
-
- Posts: 807
- Joined: Mon 12 Oct 2009, 17:11
Hello perdido
This conversation is drawing to a close, but one last question. What version of ndiswrapper did you compile?
This conversation is drawing to a close, but one last question. What version of ndiswrapper did you compile?
[color=blue]B.K. Johnson
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]
tahrpup-6.0.5 PAE (upgraded from 6.0 =>6.0.2=>6.0.3=>6.0.5 via quickpet/PPM=Not installed); slacko-5.7 occasionally. Frugal install, pupsave file, multi OS flashdrive, FAT32 , SYSLINUX boot, CPU-Dual E2140, 4GB RAM[/color]