no network after manual cancellation of package installation

I went to install the xorg server package and I was given a warning that the package was already installed. I was then prompted with 37 packages and asked to choose a number between 1 and 37. I tried the zero and none keywords but I couldn't escape. So I hit controll + c and started receiving this error:

Code:

nohz local_softirq_pending 08

Now I have no network. I've tried pinging Google and no network.
I used

Code:

dchpcd eth0

and it times out and says there's no router available.

How do I fix this? I would rather not do a fresh install.

So I had to pull out my windows 7 hard drive to activate a friends iPod and it fixed the network issue.

I would love to know why it fixed it!! Anyone know why?

Dude, I know you want to get your problems solved; I don't blame you for that.

However, posting on multiple forums at the same time is a breach of etiquette.

Stop being a jerk to the people willing to help you.

[Edit]
Also, there is probably no more active "IRC" than those that offer support with "GNU/Linux" problems.
[/Edit]

Soma

"DUDE", I honestly didn't think it was improper ettiquet or let alone would offend someone. I still see nothing wrong with it.

Cross posting is far from being a jerk. I think your the jerk here bro!

[Edit]
And by the by, if you didn't know that posting the same question is multiple forums at the same time was a problem you've never read the guidelines posted at almost every forum everywhere.

You should get right on that.

If you look at this forum you'll see "Forum Guidelines" which explicitly asks you not to do that sort of thing. You'll find similar at the other forums where your posting these "Gnu/Linux" questions.
[/Edit]

Cross posting is far from being a jerk.

Posting the same problem on multiple forums duplicates resolution efforts; it takes time to try and resolve a problem; wasting peoples time makes you a jerk.

I think your the jerk here bro!

Thanks for the information.

Soma

And by the by, if you didn't know that posting the same question is multiple forums at the same time was a problem you've never read the guidelines posted at almost every forum everywhere.

I knew "SOME" people had, as you call it, a "problem" with cross posting. Did'n tknow it was a rule. Just thought it was a pet peeve of some. If it is a rule then I owe you an apology!

Posting the same problem on multiple forums duplicates resolution efforts; it takes time to try and resolve a problem; wasting peoples time makes you a jerk.

I do not agree. I am not wasting anyone times, Not one bit!

I don't care how mad you are, there was no reason to call me out of my name! It's annonymous or Anthony. Thanks!

I don't care if you don't agree and neither does anyone trying to help you!

It takes time to write out all the steps you may need to take to solve a problem. One group is wasting their time if two groups are writing the same steps for you at different forums because they are unaware of the separate effort to help. It doesn't matter if you "don't agree" just because you want to get help as fast as possible. The people volunteering their time is having their work duplicated just because you are being selfish. It doesn't even matter of the groups involved are "okay" with this duplicated effort as the time spent on this duplicated effort could be spent helping others with a problem.

This is not you "not agreeing"; this is you being a selfish jerk.

Soma

Originally Posted by Annonymous

It's annonymous or Anthony.

LAWL! Not so annonymous now, are we, Anthony

@Anduril, That gave me a good laugh lol Your a funny guy!

Anywho, I did a fresh I stall and noticed I wasn't adding the "network" keyword in the hooks params in the mkinitcpio.conf file and I wasn't enabling the network daemon to run on boot with the @ symbol.

Finally finished the full install too. Feels great!

Originally Posted by Annonymous

and I wasn't enabling the network daemon to run on boot with the @ symbol.

'@' marks the daemon for backgrounded start, not just enable... just it being there is enabling (unless you have '!' in front of the name).
Btw, I use the networkmanager daemon instead of the more 'primitive' one provided by default and it works great.

Originally Posted by manasij7479

'@' marks the daemon for backgrounded start, not just enable... just it being there is enabling (unless you have '!' in front of the name).
Btw, I use the networkmanager daemon instead of the more 'primitive' one provided by default and it works great.

That's what I said lol

Anywho, using the network keyword works fine for me. Is there a significant difference in using network manager over network?

Originally Posted by Annonymous

That's what I said lol

Anywho, using the network keyword works fine for me. Is there a significant difference in using network manager over network?

If network works fine now, don't disturb it. I use network manager because I have a slightly complicated home network.. and writing scripts for everything was getting tedious.
https://wiki.archlinux.org/index.php/Networkmanager

Yeah network works fine as of now. I'm using my wired connection and haven't set up my wireless as of yet. Mainly because I only use Arch at night. You know, tweaking, fixing, and breaking things lol I use Ubuntu during the day and Android on the go. So I havent really had any use for the wifi on Arch... "YET". I have read there are lots of issues with Arch and wireless though. Especially on upgrades, users lose it. So, network daemon works fine. No need for networkmanager ya know? I just installed the cairo dock too.

Originally Posted by Annonymous

. You know, tweaking, fixing, and breaking things lol

That is quite a myth.
After you have finished installing Arch, you basically do not have to worry about it.
In the 5 months I have been using it, I had to manually do something during an upgrade only once.
(had to manually remove a redundant file).

I have read there are lots of issues with Arch and wireless though. Especially on upgrades, users lose it.

I haven't encountered one, yet.
If you are concerned about that, use the LTS kernel instead of the latest one.
(By latest, I really mean latest..)