urgent 0.0!!!

ok so i decided i wanted to make my aspire ask for a password upon startup and when i did what one of the threads on here said, i commented out the autologin and ran something else in its place, i rebooted and my AA1 stayed on the aspire one screen, the blue one!!!!!

how can i get back in to fix it :?: :?: :?:
please help

 

all i can get when i start my machine up is the bios and boot list and the startup logs or something on the blue screen i mentioned

please help, if its not to optimistic id like it fixed for tomorrow :? lol

thanks

 

Could you be more expliccit about what you've done? 'What one of the threads' said isn't all that helpful - no-one has the time to search through several thousand threads using guesswork as to what you mean.

And did you take any precautions (like backing up, or enabling a second console, or enabling sshd) before doing something which might well lead to a failure in the startup process?

If there's no ssh and no ALT-F2 console, then you may well be left with no option but to use the recovery system; if the desktop hasn't started you can't otherwise get to a console to sort anything else out.

 

ok , well the thread i was referring to was the one on disabling the autologin so i can log in each time i start up: viewtopic.php?f=39&t=363 <-this lol

also, no i stupidly did not back up, dont worry i will from now XD, ive learnt my lesson

i guess im gonna have to recover the whole system arent i? XD, *sigh*

 

One of the posst in that thread is this one: http://www.aspireoneuser.com/forum/viewtopic.php?f=39&t=363#p3710 which suggests commenting out the DontVTSwitch line in /etc/X11/xorg.conf - did you do that?

If so, try pressing CTRL-ALT-F1 (and if that doesn't work there's no harm in trying the other F-buttons with CTRL-ALT - I thought I'd seen CTRL-ALT-F2 as the right option somewhere!) and see if you get up a rudmentary console screen. If you do there's hope yet!

 

oh damn, its too late now anyway lol, i just rebooted it , thanks anyway

actually, i dont think i did get the console thing, or rather i got something similar but no matter what i typed it did nothing lol, it was just saying the things that happened in startup

 

also, sorry for seemingly wasting your time

 

No problem; sorry if you've lost anything by needing to recover.

I think it would be a good idea for everyone to enable that second console (i.e. uncomment the 'DontVTSwicth' line - goodness knows why Acer disabled it! It's a useful line of defence if everything else fails, as it does at least provide you with a way to get a console and thus to start fixing stuff.

 

yeah thanks lol, i happen to have found a large percentage of my files back on my old PC, i still lost a few needed things but im beginning to lose interest in college lol

anyway, what do you mean by second console? is it another terminal sorta thing? ive heard of it before but to be honest, nobody has told me what it is lol, also, is it in that file i had to change to get the login screen (or what i thought was that lol)? also, do you recomend me enabling the second console?

 

Basically, Linux comes from being used on servers where a lot of people could be logged in at once, so it allows for more than one login at once. A standard Linux installation on a desktop machine would come with anywhere from five to twelve 'consoles' enabled.

The graphical system starts in one of those consoles, so on a desktop machine you'd have a few others available to swicth to. Most of the time on a desktop they aren't much use, but they are still there if you want them for anything. They are just like the terminal you can get to in the graphical interface, but full-screen.

Acer locked the system down to provide only two consoles, then took it further by disabling the way of switching between them. If you edit the file /etc/X11/xorg.conf and find the line which says something like "Option DontVTSwitch Yes" and just put a '#' at the beginning of that line, then you'll be able to switch between consoles again - pressing CTRL-ALT-F1 will get you from the graphical interface to a full-screen (well, nearly) console.

It's only really useful if something goes wrong with the graphical side. The problem with Acer having effectvely locked users out of the 'spare' console is that if the graphical system fails to start properly, it locks the whole thing up (as you've found!) - and you can't then get to a console to sort it out. Changing that setting just gives you a safety belt if something goes wrong.

 

well im not too sure if the graphical side did fail, from what i can gather, it was just the autologin that stopped working, i was just left there on a blank screen with no way of getting in rofl

and yeah id heard a little about the server based linux (originated from unix right?) but i still found it confusing, i still do a little but i understand a heck of a lot more lol, the reason i came over to linux from windows was because microsoft bought lionhead studios (random reason but it annoyed me, they are an awesome game studio, or they were until microsoft lol)

 

The autologin is part of getting the graphical interface going, so if that fails the graphical interface doesn't start. Then you're stuck, unless you can get to a console.

 

ahh, im learning loads from this forum lol thanks ^_^

 

can you tell me how did you solved your problem with blue screen?

 

ah you got t same problem?

sorry but what i did was rebooted it, i think maybe there was a way around it, or some people may have gotten the wrong idea of what my problem was and thought there was a way to fix it but i tried everything and nothing worked im afraid, perhaps someone else will have the answer