> On Sun, 18 October 2015, at 7:22 p.m., Mansour Al Akeel > <mansour.alak...@gmail.com> wrote: > > I haven't updated my system "emerge --sync" in a while (2-3 months). > Few days ago I did. > After that I lost my wireless interface.
I apologise, but I'm extremely dubious of this claim. wifi doesn't stop working when you simply update the Portage database - there is no connection between the two things. You updated the Portage database (with `emerge --sync`) *and then did something else* which caused your wifi to stop working. Surely, you updated the Portage database (with `emerge --sync`) and then installed a bunch of updated packages? (something like `emerge -u world`) I don't mean to sound antagonistic, or like I'm attacking you. I'm sorry if this email has a negative tone, but what you wrote raises two issues. 1. It's easier to help you if we know exactly what you did. 2. When you're updating a bunch of packages, you should run `emerge -p` first. When you've done so, there's a good case for identifying system-critical packages (such as anything related to wifi, networking and system init) and emerging them separately (`emerge -1 package`); then you can deal with the package notices or any problems separately, knowing exactly what update you're responding to. Stroller.
