Explain How You Fixed It So Others May Learn From It

Linux not playing with some wireless chipsets...

      I Discovered my wifi dongle isn't supported by ubuntu 16,04.  It was a broadcom  43231 that was ever so marginal in the generic driver support. My other Atheros chipset wifi dongle would light up like a champ ... I had to install a windows driver emulator (ndiswrapper) and install the windows driver via gtk GUI..

       https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

Edited by synergy513, 04 March 2018 - 08:15 PM.

Linux not playing with some wireless chipsets...

 

      I Discovered my wifi dongle isn't supported by ubuntu 16,04.  It was a broadcom  43231 that was ever so marginal in the generic driver support. My other Atheros chipset wifi dongle would light up like a champ ... I had to install a windows driver emulator (ndiswrapper) and install the windows driver via gtk GUI..

 

       https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

synergy513, this would be great to add to the Linux 'How To' section below!

https://www.bleepingcomputer.com/forums/f/100/linux-how-to-and-tutorial-section/

While the issue doesn't arise as much as it once did, when does, seems that a few will ask over the course of 3-4 months. Most are pulling old notebooks out of closets or wherever stashed & installing some Ubuntu type distro, only to discover that their now ancient Broadcom wireless doesn't work. Not because it never did, rather Ubuntu & it's variants no longer includes the drivers in the ISO. Don't know why not, as many other components of those years are supported. 

Most are also 32 bit hardware, which are standing on it's last leg of Ubuntu support, there'll be no 32 bit Ubuntu 18.04, so three more years of 16.04 & other than Puppy releases, the wait is over. Some thought that there's be no 16.04 support, with reluctance, Canonical released their last 32 bit LTS distro. I fully expect Windows to follow suit at some point, probably within the next year or so. Maybe they all were waiting to see who would flinch first, it's now official!

https://itsfoss.com/ubuntu-drops-32-bit-desktop/

Still would be a good add in that section, some will run Ubuntu 16.04, which includes variants such as Mint 18, until EOL & beyond. Some Linux users have ran unsupported distros, as long as current browsers could be installed, 14.04 & Mint 17.3 has just over a year before EOL, many won't let go easily.

Cat

Ok, I went round and round with this one. Apparently user gets one shot to get ndiswrapper installed right, if it don't , it has to be purged and installed again. My broadcom chip is working good now. Not as good as the atheros, but satisfactory nonetheless.

Ok, I went round and round with this one. Apparently user gets one shot to get ndiswrapper installed right, if it don't , it has to be purged and installed again. My broadcom chip is working good now. Not as good as the atheros, but satisfactory nonetheless.

synergy513, Thanks for bumping that Topic, hopefully will assist someone in need.

We cover so many issues that it's impossible to remember all. 

Cat

A friend of mine was struggling with his computer from it constantly switching off. He thought the GPU was bad and bought GPU to replace it, and then he thought power supply was bad so he bought another. I looked at it, and put in an entire new motherboard/ssd/gpu and it still crashed.

It turns out it was a bad reset switch.. It took a lot of guessing, but I found it out.

Edited by dreamdesire, 19 October 2019 - 02:53 PM.

Maybe people don't post about how they fixed there issues because they don't remember how they did it. Maybe things just happen nobody is perfect.

Here's one I have to do after each new build etc. First off when I open an app I want it to have the focus without me clicking on it first. For instance if I open Notepad I dont want to click on it before I start typing, I just want to type. The way that works for me is a little registry tweak.

Open the registry editor by typing regedit in the Search Box.

Then navigate to HKEY_CURRENT_USER - Control Panel - Desktop and in the right hand pane look down the list for ForeGroundLockTimeout.

Double click on it and change the value to 0

Now whenever you open something it will have the focus without you clicking on it.

Just one little annoyance that I didnt like.

Hello all,

Bleeping Computer is a community where people come together to help one another fix any problem which may arrise on their systems. This is the theme of this site. Help one another, and share your wealth of experience.

I read posts here and I am so glad to see that you have gotten your problems fixed. It shows that the people here are here to help you and the advice was well reported to you.

The problem seems to be that many of you get your problems fixed and you then post back saying:

Ok.. I fixed it (on my own), thanks
The problem got taken care of
or... something else to that nature.

How are other people going to learn from your fixes if you don't post back here what you did to fix your problem? People are always wanting answers, and with posts/replies like above will only make people wonder what you did to fix it.

Please explain EXACTLY as much as possible what you did. It could be a new and informative way to do something that has never been discussed before. Don't just get your own stuff fixed and leave everyone else out in the open. Explain how you fixed it, because people want to know... "Well, how did he do it?"

Don't hold back on information that can help others,,, because the information here has helped you. We've all come here for help, and we aught to provide it in return, even in the form of explaining how you got a problem fixed.

It's true that you see that a lot "on the internet", and there may be many reasons for it. Other forums sometimes don't care for your issue, after which I can understand that : if you're not interested in the problem, you're not entitled to the solution. The me-me-me generation is growing up, but there's also an I-dont-care generation, which is not necessarily the same people. You would wonder what they do on a tech forum, but I have found many of those ...

Anyway, so many issues I have looked for long time, sometimes for years. Like the one with the "press key to boot from media", but eventually finding out that my USB power is low on startup, and I could never install Windows using a DVD. Now, that is no longer an issue (even I still have a computer with DVD), but that was annoying. I know a lot of people don't know you can install Windows from a DVD, but used to work for some decades.

So, my USB still doesn't work, BUT ONLY up to the Windows login page, so it's hard to get into BIOS, or in Windows safe mode. But, there's ways to do that from Windows: Click on Start button, press SHIFT during clicking "Restart"

Maybe people don't post about how they fixed there issues because they don't remember how they did it. Maybe things just happen nobody is perfect.

What also happens is that you try 12 different fixes, and you don't know which ones of them are part of the solution.

Some fixes are combinations of actions, sometimes even in a certain sequence ... so that is at least 12x11x10x9x8x7x6x5x4x3x2 number of fixes

That is even not counting the sequence of them

And, that is assuming you are aware of all 12 actions, some of them just run without knowing.

Edited by SwaamiBaami, 02 January 2021 - 11:27 AM.

I remember the days when a restart of the computer fixes most problems... oh wait.. that still happens.

 

That, and clearing browser cache

(if the problem is in the browser area)

But, I also remember fixing a Windows server once, where the "big problem" was that 1 drive was full. And everything failed ...

Cleaned 1 big file, problems solved.

You know how one should always replace inherited permissions with object permissions then edit them, rather than removing inherited permissions, otherwise you remove system access from the folders?

Me too now.   lol.

I don't even know why that's an option.

Hosing my company's payroll folder permissions on pay day was an interesting feeling. There's one way to learn, and then there's the hard way.

How to fix “Failed to Enumerate Objects in the Container”

from an administrative command prompt;

takeown /F X:\FULL_PATH_HERE
takeown /F X:\FULL_PATH_HERE /r /d y
icacls X:\FULL_PATH_HERE /grant Administrators:F
icacls X:\FULL_PATH_HERE /grant Administrators:F /t

then set your user access permissions as you want them.
 

You might get more answers if you post in the general security section. Most of the knowledgeable Security staff hang out there.

Topic closed, not intended to be what it now is.

Louis