I'll chalk it up to an outside influence at this point, but regardless, I don't feel there was much opportunity for me to have not run into the issue other than not having done an Syu that particular day.
]]>Please post the output of uname -a
and of pacman -Qi linux
First, you should re-read ngoonee's post. It's a statement of fact (upgrading without looking is bad practice but it happens to everyone once in a while) and a helpful suggestion (check your pacman logs). As it is, you are gunning for a ban.
As for your problem, please post your video card model, Xorg log, and the output of `ip link` and `lspci`.
Actually, that was sarcasm more then it was a purely statement of fact.
I just hope there will be less of that, and more actual to-the-point-statements in the future.
.
On the actual topic, it is sort of one of the most important points when chosing to run arch - that you need to read more, and spend more time and attention to upgrades,
wheter it be pacman-file-upgrades, or changed policies in the underlying programs themselves.
This lesson is one we all learn at one point when/if straying from it. : )
I just want to confirm, lspci does show your network devices, but ip link only shows lo. What about the drivers (lsmod)?
lspci shows everything (not a hardware problem - both wlan and eth are no longer accessible). Re: drivers, I posted earlier that manually trying to load the e1000e driver gets me nothing - wasn't even going to attempt the wireless at that point. The lsmod output showed that the driver wasn't loaded. Too messed up to consider even trying fixing. Doing a rebuild today.
]]>My last ditch effort was to boot into the live system one last time and do a `arch-chroot /mnt/mytemproot pacman -Syu base base-devel`. Nada - still no interfaces available and X fails. At this point I don't trust the installed system and have pulled all my data back down and will reinstall tomorrow. I'd love to have gotten to root cause, but there was no indication anywhere that I've been able to see.
]]>[Edit]: You might find that a thread title more explanatory than "System B0rked" would result in more people being willing/able to help.[/Edit]
All the best,
-HG
]]>Video card is integrated Intel 3000, ip link only shows loopback (can't manually bring up any physical interface anymore) and as for dmesg I'll have to post it later.
I did try booting the system from the live disc, mounting my /root partition, doing a pacman -Sy, then doing a pacman --root /to/my/root/mount -Syu which, worked. But only updated a couple outdated packages and had no impact. I think I'll take juray's advice and dig into systemd when I get home.
I do appreciate any insight and suggestions as much as the next person - I'm not looking for someone to flat out solve my problem, just looking for pointers or suggestions. Seems stuffy 'round these parts. Guess I'll hit up IRC next time I have a lame problem... I find it odd that I've entirely borked my entire system doing an upgrade, I've never experienced anything this full of fail with Arch in the past 6 years. Then again, maybe it's the driver.
EDIT:
And, yes, I would have posted a bunch of logs already - but with no network I figured I'd ask first. Didn't have any removable media with me at the time to sneakernet it over to something I could post from.
As for your problem, please post your video card model, Xorg log, and the output of `ip link` and `lspci`.
]]>Suggestion number one: Don't insult the moderators.
Suggestion number two: Don't choose a user name that implies you have no respect for other operating systems
To #1: Thank you, but I'm not a lemming. He/She took the time to post the first condescending message
To #2: I'm not sure you read my handle the correct way, but I've been using it for well over 10 years and it has nothing to do with operating systems. Yours could mean that there are too many dogs in the world and that you want to get rid of all of them. On neither point do I have a concern with you - but belaboring your point of assumptions being made incorrectly.
Hi,
i dont know if it help you, ..
in my pacman log from 18.01.2013 i see this:
( 9/14) upgrading systemd [######################] 100% ==> Persistent net naming rules have been shipped as disabled. See /etc/udev/rules.d/80-net-name-slot.rules for more detail
This is content of this file in my PC
# This file masks persistent renaming rules for network devices. If you # delete this file, /usr/lib/udev/rules.d/80-net-name-slot.rules may # rename network devices according to ID_NET_NAME_{ONBOARD,SLOT,PATH} # properties of your network devices, with priority in that order. See # the output of 'udevadm test-builtin net_id /sys/class/net/$interface' # for details on what that new name might be. # # http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
Check this out...
My version of systemd is now:
systemd 197-4
Everytime if i have similar problems with X (last time when i setting up two monitors), i find hint for solution in X logs
/var/log/Xorg.0.log
I think that really good practice is to preform system update every day, and log from this update save to individual file. It yelds relative short pacman log after each update and better overview of changes in system...
j.
Thanks juray! I am going to dig back into systemd this afternoon, I'm guessing this may be the root of my problems since networking, X and some other things have completely failed after the upgrade. Odd thing is - I didn't see any systemd upgrades in the pacman log file. The udevadm is a new one for me, so hopefully that sheds some light. Thanks!
My X log doesn't have anything interesting in it - just "no screens found".
Much appreciated for the insight and suggestions!!!
]]>log from this update save to individual file
You can get the same thing with
cat /var/log/pacman.log | grep <year>-<month>-<date>
Will save you from having lots of redundant log files.
]]>Suggestion number two: Don't choose a user name that implies you have no respect for other operating systems (see "Respect other Distributions and Operating systems": https://wiki.archlinux.org/index.php/Fo … g_Systems)
And no, not everyone proactively monitors their upgrades. You can see many posts here from people who failed to do so.
]]>