[opensuse] The system crashes directly after login
Hello Just after my login screen the system crashes to console and returns with a login screen. I tried adding a new user and trying to log in with that, I let xorgconfig generate a new xorg.conf (saved the old) to no avail. The console doesn't report any problems. I use OpenSUSE 10.2 with Gnome on a dmraid 0 system (on a Intel 82801ER Sata (fake)Raid controller). I am quite new in Linux, and would dearly like to post the needed logs, but dont kow where to find them (in Gnome I would be able to, but I cant start gnome atm) Thanks Neil Boekend -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Just after my login screen the system crashes to console and returns with a login screen. I tried adding a new user and trying to log in with that, I let xorgconfig generate a new xorg.conf (saved the old) to no avail. The console doesn't report any problems.
I use OpenSUSE 10.2 with Gnome on a dmraid 0 system (on a Intel 82801ER Sata (fake)Raid controller). I am quite new in Linux, and would dearly like to post the needed logs, but dont kow where to find them (in Gnome I would be able to, but I cant start gnome atm)
I have had this when I have had misconfigured video drivers (when the monitor was set out of range, the binary video drivers were not installed properly etc). What video card are you using? Are you using the default of the binary drivers provided by the video card manufacturer? Did this start happening after you played with the video settings? Or has it been this way from a fresh install? You could try logging in into a terminal and running sax2 and reconfiguring your video settings to see if that helps. These are the general steps I follow when I am chasing down a video problem.... Go to a terminal login (press Ctrl+Alt+F1). Log in as root. Type: init 3. This drops you out of graphical mode... press enter to get your prompt back. Now type: sax2 When it starts you will get a message to accept things as they are or change them. You want to select the option to change the settings. Once you are into the main interface, you can look at the settings and see if any need to be changed. Once you are done there, make sure you Test the settings. If it passes the test, Save and exit. Now, to test things further, switch to a new terminal (Ctrl+Alt+F2). Log in as your regular user. Type: startx If all is OK, your GUI (KDE/Gnome etc) will start. If it fails, you will be dropped back to the command line with hopefully some information about why X is not starting up. Report back to the list with the error message.... If it all works, exit the GUI, log out. Switch back to the terminal where you logged in as root (Ctrl+Alt+F1) and type: init 5 This should move you back to run level 5, and start GDM/KDM and you will get your usual graphical login screen. You should be able to log in and start X normally now. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks for the verry quick reply, 20 minutes!
On 10/29/07, Clayton
What video card are you using? A Nvidia Geforce 6200 on AGP and a Nvidia Geforce FX 5200 on PCI Are you using the default of the binary drivers provided by the video card manufacturer? I used the drivers provided by Nvidia succesfully up to yesterday. This morning (when gnome failed to start properly) I tried rewriting xorg.conf with xorgconfig and the default drivers. This failed (or I wouldnt have mailed). Did this start happening after you played with the video settings? Yesterday I got my wacom up and running, so I edited xorg.conf manually. I restarted suse succesfully after that Or has it been this way from a fresh install? nope
You could try logging in into a terminal and running sax2 and reconfiguring your video settings to see if that helps.
These are the general steps I follow when I am chasing down a video problem....
the results of the steps described below (for as far as I could perform them) After I typed sax2 it tried to start X. This failed a couple of times, so Sax2 gave me this error message: ups lost during card probing Something went wrong while x was called with --probeonly
Go to a terminal login (press Ctrl+Alt+F1). Log in as root. Type: init 3. This drops you out of graphical mode... press enter to get your prompt back. Now type: sax2 When it starts you will get a message to accept things as they are or change them. You want to select the option to change the settings. Once you are into the main interface, you can look at the settings and see if any need to be changed. Once you are done there, make sure you Test the settings. If it passes the test, Save and exit.
Now, to test things further, switch to a new terminal (Ctrl+Alt+F2). Log in as your regular user. Type: startx If all is OK, your GUI (KDE/Gnome etc) will start. If it fails, you will be dropped back to the command line with hopefully some information about why X is not starting up. Report back to the list with the error message....
If it all works, exit the GUI, log out. Switch back to the terminal where you logged in as root (Ctrl+Alt+F1) and type: init 5 This should move you back to run level 5, and start GDM/KDM and you will get your usual graphical login screen. You should be able to log in and start X normally now.
C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2007-10-29 at 10:54 +0100, Neil wrote:
Hello
Just after my login screen the system crashes to console and returns with a login screen. I tried adding a new user and trying to log in with that, I let xorgconfig generate a new xorg.conf (saved the old) to no avail. The console doesn't report any problems.
I use OpenSUSE 10.2 with Gnome on a dmraid 0 system (on a Intel 82801ER Sata (fake)Raid controller). I am quite new in Linux, and would dearly like to post the needed logs, but dont kow where to find them (in Gnome I would be able to, but I cant start gnome atm)
Thanks Neil Boekend
What does Xorg.log reveal? What error message do you get if you manually start xorg with startx? -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed Thanks annyways -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed
Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
well it's on the same as the rest of / but I thought to put it this
way since emptying /tmp solved the problem
On 10/29/07, Clayton
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed
Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-10-29 at 12:20 +0100, Clayton wrote:
Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
It doesn't matter if it is a separate partition or not. Just fill up / completely and you will have the same symptoms. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHJdBltTMYHG2NR9URAmq0AJ0dEM+DOzMXY4HHbOn3CYDv0TmhiQCeK1IS cs0FJ9Lj7hticMPidMJMceI= =xe2J -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed
Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
/tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too. Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition when I set up a system (just eliminates one more source of possible filesystem corruption on the root filesystem in event of power failure or kernel glitch. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
Clayton wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed
Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
/tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition
I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk. Ken -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider wrote:
Aaron Kulkis wrote:
Clayton wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
/tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition
I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk.
Really? So if the /tmp directory is corrupted, and it is on its own partition (and therefore, a separate filesystem), this corrupts the root filesystem how, exactly? Filesystem corruption (data) is MUCH more common than disk errors (hardware). But yes, if I have the resources available, /tmp is also on a completely different disk than the root filesystem. Unfortunately, this is not practical on most laptop systems, but separation onto a separate partition/filesystem can be done even on a single hard-disk system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Clayton wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use.
/tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition
I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk.
Really?
So if the /tmp directory is corrupted, and it is on its own partition (and therefore, a separate filesystem), this corrupts the root filesystem how, exactly?
You weren't talking about corruption but only disk I/O. Disk corruption is another matter. Disk I/O affects all partitions on the disk not just one. If the disk is writing to a /tmp partition it _is_ going to affect the / partition due to head movement etc. Ken -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider wrote:
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Clayton wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use. /tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk. Really?
So if the /tmp directory is corrupted, and it is on its own partition (and therefore, a separate filesystem), this corrupts the root filesystem how, exactly?
You weren't talking about corruption but only disk I/O.
A filesystem can't get corrupted if there's no write activity on it.
Disk corruption is another matter.
No, they're directly related.
Disk I/O affects all partitions on the disk not just one.
the overall wear of read/write head and it's controller arm is effected, along with the data on the particular partition/filesystem being written to. Remember, it's a physical device doing a physical activity...MODIFYING the data at a specific location on the physical platter(s).
If the disk is writing to a /tmp partition it _is_ going to affect the / partition due to head movement etc.
But that corrupts the / partition how, exactly? You're not an engineer, are you? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Clayton wrote:
> Problem solved: I filled the partition with /tmp on it, so nothing > could be parked there. I found out when I tried running the sax2 man > page which crashed but gave me the info I needed Interesting. I hadn't considered that a full /tmp partition would do it. I don't have it on a separate partition on any of the systems I run, so this never came up. I'll be tucking that bit of info away for future use. /tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk. Really?
So if the /tmp directory is corrupted, and it is on its own partition (and therefore, a separate filesystem), this corrupts the root filesystem how, exactly?
You weren't talking about corruption but only disk I/O.
A filesystem can't get corrupted if there's no write activity on it.
DUH!
Disk corruption is another matter.
No, they're directly related.
Disk I/O affects all partitions on the disk not just one.
the overall wear of read/write head and it's controller arm is effected, along with the data on the particular partition/filesystem being written to.
Which affect the other partitions because they _cannot_ be written to at the same time, duh!
Remember, it's a physical device doing a physical activity...MODIFYING the data at a specific location on the physical platter(s).
If the disk is writing to a /tmp partition it _is_ going to affect the / partition due to head movement etc.
But that corrupts the / partition how, exactly?
You are the one that brought up corruption, not me.
You're not an engineer, are you?
You don't have to be an engineer to realize you can't perform write operations to two different partitions at the same time on the same disk. I still say I/O is I/O, you're either writing to or reading from a specific place on one platter of the disk which prevents reading/writing from any other place on the disk ( I/O ). Ken -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 30 October 2007 19:09:17 Ken Schneider wrote:
You don't have to be an engineer to realize you can't perform write operations to two different partitions at the same time on the same disk.
Not that this discussion has anything to do with engineering, but I say you do have to be an engineer to realize that. A hard drive has multiple read/write heads, and while it might not be currently possible, there is certainly nothing that says in future, they can perform I/O operations independently from each other. Perhaps they even can today, I don't know. There is most definitely no law of physics preventing it Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 30 October 2007 11:20, Anders Johansson wrote:
On Tuesday 30 October 2007 19:09:17 Ken Schneider wrote:
You don't have to be an engineer to realize you can't perform write operations to two different partitions at the same time on the same disk.
Not that this discussion has anything to do with engineering, but I say you do have to be an engineer to realize that. A hard drive has multiple read/write heads, and while it might not be currently possible, there is certainly nothing that says in future, they can perform I/O operations independently from each other. Perhaps they even can today, I don't know. There is most definitely no law of physics preventing it
I anxiously await the day this hideous business of rotating magnetic media is relegated to the last entry in a low row of museum exhibits. Check out this article from Tom's Hardware Guide: http://www.tgdaily.com/content/view/34065/118/ Most interesting is the third slide from the sequence starting at http://www.tgdaily.com/picturegalleries/gallery-20070926.html. It's still very expensive, but once that comes down by a factor of 10, I'll be saying goodbye to the conventional disk drive forever.
Anders
Randall Schulz
Ken Schneider wrote:
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Ken Schneider wrote:
Aaron Kulkis wrote:
Clayton wrote: >> Problem solved: I filled the partition with /tmp on it, so nothing >> could be parked there. I found out when I tried running the sax2 man >> page which crashed but gave me the info I needed > Interesting. I hadn't considered that a full /tmp partition would do > it. I don't have it on a separate partition on any of the systems I > run, so this never came up. I'll be tucking that bit of info away > for > future use. /tmp can fill up even if it's on the root partition...of course, if that happens, then your root partition is full, too.
Personally, I don't like ANY unnecessary file I/O on my root partition, so /tmp always gets its own partition I/O is still I/O that has to be handled by the _disk_ not the _partition_, so it matters not if /tmp is on it's own partition unless it is also on a different disk. Really?
So if the /tmp directory is corrupted, and it is on its own partition (and therefore, a separate filesystem), this corrupts the root filesystem how, exactly?
You weren't talking about corruption but only disk I/O. A filesystem can't get corrupted if there's no write activity on it.
DUH!
so then why did you imply otherwise? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 30 October 2007 15:12:01 Aaron Kulkis wrote:
A filesystem can't get corrupted if there's no write activity on it.
Of course it can. Underneath it's hardware, and hardware can go bad. Effects such as bit flips can cause file system corruption at any time That's one reason for regularly checking your file systems Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Tuesday 30 October 2007 15:12:01 Aaron Kulkis wrote:
A filesystem can't get corrupted if there's no write activity on it.
Of course it can. Underneath it's hardware, and hardware can go bad.
Which usually effects the entire drive, not just one filesystem on it.
Effects such as bit flips can cause file system corruption at any time
on a modern disk drive, base level encoding system is so redundant (error detecting/correcting codes) that the likelihood of a bit error actually making it up to the level that an fsck can detect it is, over the course of a year, is less than 1 in a billion. Why? Precisely because a single bit-flip could be so destructive otherwise.
That's one reason for regularly checking your file systems
The far greater corruption risk is an intermittent bug in the kernal or device driver creating a data or meta-data corruption error, or power failure during a write sequence, or a kernal crash during the same. This is why I use journalled filesystems for everything except for /tmp. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Neil wrote:
Problem solved: I filled the partition with /tmp on it, so nothing could be parked there. I found out when I tried running the sax2 man page which crashed but gave me the info I needed Thanks annyways
You can configure your system to automagically clear out stuff over a specified age and also on reboot. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Neil wrote:
Hello
Just after my login screen the system crashes to console and returns with a login screen.
It sounds like only X11 or maybe your graphical login shell crashes. If your SYSTEM was crashing, the entire system would be dead until you do a power reset.
I tried adding a new user and trying to log in with that, I let xorgconfig generate a new xorg.conf (saved the old) to no avail. The console doesn't report any problems.
I use OpenSUSE 10.2 with Gnome on a dmraid 0 system (on a Intel 82801ER Sata (fake)Raid controller). I am quite new in Linux, and would dearly like to post the needed logs, but dont kow where to find them (in Gnome I would be able to, but I cant start gnome atm)
/var/log You have to be logged into root to get into the directory.
Thanks Neil Boekend
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Aaron Kulkis -
Anders Johansson -
Aniruddha -
Carlos E. R. -
Clayton -
James Knott -
Ken Schneider -
Neil -
Randall R Schulz