You are not logged in.
Pages: 1
When booting up it gives me
(none)/bin/login:
When I try to login
error libpam_misc.so.0 file or directory not found
I've tried updating from a chrooted environment and I've checked and made sure the file is there and linked.
Offline
Tried to copy everything to /lib now It sees it but it says the file is to short....
Offline
Not sure what to do from here.... Can tell if it's a corrupt package or a messed up configuration file
Offline
I feel like I've seen this somewhere before, but can't remember where. libpam_misc.so.0 belongs to pam so what happens if you reinstall that from a chroot? What does your partition scheme look like?
Offline
What happened immediately before the reboot and the error appearing? A full system update? If so what was updated?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I forgot to mention that it was caused by a yoaurt update.... The problem was an update to mkinitcpo in that it now needed a usr hook it now will boot into my system but X won't start
Offline
You're going to have to give us more information than that. Are you saying the above problem is now fixed and you can login to a terminal but X won't start? The relevant info from starting X (Xorg.0.log, etc.) would be useful...
Offline
You're going to have to give us more information than that. Are you saying the above problem is now fixed and you can login to a terminal but X won't start? The relevant info from starting X (Xorg.0.log, etc.) would be useful...
was planning on it... I'm doing that now...
and that's exactly what I'm saying.. it now ends with a terminal login screen... which I can succesfully log in to
no error messages from slim it just doesnt load... ill check its log too
Last edited by runny6play (2012-06-08 20:49:56)
Offline
I think I've found the problem when I was troubleshooting I did update the and tree and reupdate my aur packages during which a certain nvidia package was updated as of which one I am unaware but... this seems to be the problem
(==) matched nvidia as autoconfigured driver 1
(==) matched nv as autoconfigured driver 2
(==) matched vesa as autoconfigured driver 3
(==)matched fbdev as autocondigured driver 4
(==) assigned the driver to the x86configlayout
(WW) warning couldn't open module nouveau
(II) unloading module nouveau
(EE) Failed to load module "nouveau"
it then repeats this with all other drivers...
Offline
Pages: 1