No network after installation

[steve7233]

The b43 driver is no longer avalible at that page!

[steve7233]

I just tried to upload a screen shot showing the dmsg error messages. I used my Amazon Kindle Fire. i can't use my phone as kdeconnect needs android plugin.

Didn't work! :confused Probably incompatable with the Fire.

[steve7233]

I went to broadcoms web site and download a 64 bit driver for the BCM4322. Its the STAdriver but I read that it supports the 4322. It's a .gz file. Does Neon have a specific package or Kubuntu or Ubuntu? I thought I should check before I compile since 99.88% of the time custume packages are best. Less chance of hosing your system! Lol.

[GreyGeek]

This computer has NO INTERNET ACCESS. Nether wlan0 nor eth0 as stated above.

Obviously, but no need to shout. There is always the sneaker net to get things into an unconnected computer.

By the way, have you asked yourself why both the wired and wireless chips do not work? They both can't be the fault of bcm43-whatever.

[steve7233]

I wasnt shouting just emphasing those three words. The rest of the sentence was normal. I thought doing it like that would make it obvious that I was emphasding rather than shouting.

I lknow a lot of things about Linux, but I am a a very light weight when it comes to Linux networking. Got any suggestions of what to look for besides the driver being the wrong one?

[Snowhog]

Long thread, so I'll just ask: Does; assuming you even can; networking work when booting to a Live Environment? If the answer is 'Yes and Yes', your hardware or the Kernel aren't the problem.

[steve7233]

Kubuntu 17.04 had both eth0 and wlan0 working after install. Kubuntu 16.10 had no eth0 nor wlan0 on live. I was able to use divermanager to get WiFi working on live. After install there was no networking and diver manager wasn't working! Neon had nothing on live or after install.

[steve7233]

I just I'd mention the only blockage that I see left when I look at rfkill list or what ever command I used elier in this thread to apparently get the WiFi switch working again, is a soft block on the blue tooth. I don't think its related but since I don't know much about networking then I thought I'd mention it, in case it gives any ideas.

[jlittle]

Kubuntu 17.04 had both eth0 and wlan0 working after install...16.10 had no eth0 nor wlan0... Neon had nothing...

This suggests that the newer kernel in 17.04 has support for your hardware, not present in 16.10, or 16.04 which is what Neon is based on. In theory you could install a newer kernel on Neon, but without internet access this is problematic.

Thinking out loud in the chance it might be useful for you...

If your alternative internet access is only the kindle fire, I suggest installing 17.04, and if you really want Neon, install it as well and multiboot. Either use btrfs subvolumes for the different installs, or set up another partition. Then you can boot into 17.04 to download stuff for the Neon install.

[steve7233]

I am currently running the live Yakaty DVD since that one will at least let me run DriverManager. I can install the Broadcom STA driver and get the wireless working. Still no wired. If I install it then no networking and since the installed DeviceManager doesn't work then I would not be able to have Internet.

I will bun the 16.04LTS and see If that works.

Since I have a small HD then I will have to wait until I have money for a new laptop/desktop then I can buy big SSD's. Then I can use the Microproccesors Hypervisor to VM several distros. I can help test 17.10 or whatever is being worked on at the time. I see no point in trying to get Yakaty to work since it will be at EL in a few weeks.

BTW: can you belive Nion dosn't have K3b!!!!

[steve7233]

Great K3b in Yakaty crashes everytime I click on start to burn the 16.10LTS iso.