New Kernel in Fedora 12 - Page 3

Boricua · #31 28th October 2009, 11:46 PM

Quote:

Originally Posted by AdamW

you may need to boot to runlevel 3 and use 'startx' to get into X. That way, if it is X crashing, it won't automatically respawn and go back to gdm, it'll crash back to the console and you'll hopefully have console messages and an X log to explain what went wrong.

I will try that tomorrow and report back.

Boricua · #32 28th October 2009, 11:51 PM

Quote:

Originally Posted by typerlc

How much effort are you willing to put in to this? If you are technically competent, and willing, there is a better way. It requires running gdb on your X server after it starts to trap the crash and extract debug information.

I can provide more info if you want to attempt this. But it's not trivial, and it's easier (though not essential) if you have another PC that you can ssh from to login to the FC12 box.

Hmmm, sorry I am not at that level yet. I'm just an attorney who happens to love Fedora

. I will try however AdamW's suggestion and see what I can find. The last time a crash took place was this morning. Around 12 hours have passed without further incidents.

asheguy79 · #33 29th October 2009, 01:57 AM

Faster booting, no problems after rebooting 5 times in a row and doing complete system shut down twice. All installs have gone smoothly as well as updates and removels.

Boricua · #34 29th October 2009, 08:38 PM

It just happened again, even after today's bunch of updates. I restarted the machine in level 3, logged in as root and started the X server. Then checked the xorg.9.log file and found the following lines at the very end, although I'm not sure if it's helpful

:

Code:

I) UnloadModule: "evdev"
(II) Sleep Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) NOUVEAU(0): NVLeaveVT is called.
(II) NOUVEAU(0): Closed GPU channel 1

JohnnyLinux · #35 29th October 2009, 08:49 PM

Quote:

Originally Posted by Francisco_PR

It just happened again, even after today's bunch of updates. I restarted the machine in level 3, logged in as root and started the X server. Then checked the xorg.9.log file and found the following lines at the very end, although I'm not sure if it's helpful

:

Code:

I) UnloadModule: "evdev"
(II) Sleep Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) NOUVEAU(0): NVLeaveVT is called.
(II) NOUVEAU(0): Closed GPU channel 1

I'm waiting to see how the experts diagnose this... especially because of this other thread

http://forums.fedoraforum.org/showthread.php?t=232850

I'm gonna go get me some cookies and vodka, and just enjoy the show. OR The problem has nothing to do with what is on my mind, nevertheless I'm still curious.

**AdamW** · #36 29th October 2009, 09:45 PM

Um, we don't want you to restart X after the crash happens. The point of booting to runlevel 3 is to *avoid* X starting up again, so that the X log is from the crash. Every time X starts, it overwrites the log file, losing the potentially useful information within

What I want you to do is boot to runlevel 3, startx, then use it normally and wait for the problem to happen. Hopefully when the problem happens it will dump you back at the console where you ran startx and leave you there. Ideally there'll be some juicy messages on the console indicating what went wrong, and possibly the same / more messages in /var/log/Xorg.*.log . Is that clearer now? Sorry to be unclear

Boricua · #37 29th October 2009, 09:50 PM

Quote:

Originally Posted by AdamW

Um, we don't want you to restart X after the crash happens. The point of booting to runlevel 3 is to *avoid* X starting up again, so that the X log is from the crash. Every time X starts, it overwrites the log file, losing the potentially useful information within

What I want you to do is boot to runlevel 3, startx, then use it normally and wait for the problem to happen. Hopefully when the problem happens it will dump you back at the console where you ran startx and leave you there. Ideally there'll be some juicy messages on the console indicating what went wrong, and possibly the same / more messages in /var/log/Xorg.*.log . Is that clearer now? Sorry to be unclear

Ahh, ok, my bad. I am actually running the machine starting in level 3 and then executed startx. Message clear

. I hope to bring something juicier next time

.

DCOH · #38 1st November 2009, 04:10 AM

Finally installed F12 last night so far not the best of the installs first tried to upgrade F11 using i386 DVD install went fine reboot to black screen. Next reinstalled using LiveCD i686 all ok updated with package manager installed the 96 kernel.
This morning went to get on computer when came off screensaver crashed and rebooted to a non ending return to login screen. Can login only using 56 kernel.
Logins with the nouveau driveris crazy first screen is 1280x1024 right, then jumps to 1024x768 left when you login before desktop the background is in four sections to the right.
This is my 8th Fedora and so far the most trouble. system sounds are screeches, must have put a ghost in.

Computer:
PCchips M848a motherboard
Nvidia GeForce 6200 video
Ram 1.5 gigs.
Everything worked fine in F11

Problem solved backgrounds I was using overloaded video drivers.

troyatlarge · #39 1st November 2009, 04:58 PM

Today I am loading multiple operating systems and having a large data partition which can be loaded from all systems. I would very much like to help here by loading this new Fedora. Is it ok to do so - I mean if something goes south I won't need to worry about losing important data in my data partition will I???

CiaW · #40 1st November 2009, 06:37 PM

Hi Troy,

when I installed using the live cd (x86_64) it defaulted to wanting to overwrite the current linux OS (CentOS) and use the whole drive; but it did have an option for custom layout which I selected. It had the 'default' LVM using the whole drive which I deleted and then selected 'restore' which made it look at and show the current partitioning setup. I selected /dev/sda6 for /boot and sda7 for / (not even giving it the format option) and it installed just fine. My shared partition is sda5 -- it was not overwritten.

After you delete the LVM it wants to create, after selecting custom layout, select 'restore' so you don't have to muck around with defining the partitions you already have. It should work...

troyatlarge · #41 1st November 2009, 07:02 PM

Thanks - I'll give it a try (I tried earlier to load Fedora 12 Alpha, early on, and couldn't get it to load at all - probably better by now).

Boricua · #42 1st November 2009, 08:10 PM

Quote:

Originally Posted by AdamW

Um, we don't want you to restart X after the crash happens. The point of booting to runlevel 3 is to *avoid* X starting up again, so that the X log is from the crash. Every time X starts, it overwrites the log file, losing the potentially useful information within

What I want you to do is boot to runlevel 3, startx, then use it normally and wait for the problem to happen. Hopefully when the problem happens it will dump you back at the console where you ran startx and leave you there. Ideally there'll be some juicy messages on the console indicating what went wrong, and possibly the same / more messages in /var/log/Xorg.*.log . Is that clearer now? Sorry to be unclear

Hi AdamW. After several days starting the machine in runlevel 3, I can report that I was not bumped back to the console. What I got (on two occasions) was a Black Screen of Death of sorts. The computer freezes with a black screen and no response, forcing me to execute a manual hard reboot. Didn't found anything significant in the xorg.log. Hope this helps for something.

**AdamW** · #43 1st November 2009, 11:14 PM

francisco: can you be more specific about "Didn't found anything significant in the xorg.log"? After hitting the BSOD, did you reboot back to runlevel 3 and check /var/log/Xorg.0.log *before* starting X again?

Boricua · #44 2nd November 2009, 12:09 AM

Quote:

Originally Posted by AdamW

francisco: can you be more specific about "Didn't found anything significant in the xorg.log"? After hitting the BSOD, did you reboot back to runlevel 3 and check /var/log/Xorg.0.log *before* starting X again?

Nope, I let it go directly to runlevel 5 and found the same normal stuff as before. But I will start again with runlevel 3 from now on and check the log after the next BSOD

.

**AdamW** · #45 2nd November 2009, 06:17 PM

every time X starts up, the log gets overwritten; so yep, if you boot back to runlevel 5, the log will get overwritten by a boring log from the new - so far working - startup

. So indeed you have to boot back to runlevel 3 after you hit the problem, so you can take a copy of the Xorg.0.log from the failure, before it gets overwritten.