LinHES Forums http://forum.linhes.org/ |
|
Augh I'm cursed - id "c7" respawning too fast http://forum.linhes.org/viewtopic.php?f=6&t=13863 |
Page 1 of 1 |
Author: | hurnik [ Fri Jan 26, 2007 10:27 pm ] |
Post subject: | Augh I'm cursed - id "c7" respawning too fast |
Twice this has happened in the last week or so. Live TV kicks out to the KnoppMyth menu (like if you hit ESC and exit KnoppMyth you get X). Reboot the system and I see: INIT: id "c7" respawning too fast: disabled for 5 minutes. The first time a simple reboot and it went away. But this time, it's not. I've not changed any Nvidia drivers or anything (maybe that's the problem). Here's what my xorg.log shows (at the end): Code: (II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (**) NVIDIA(0): Option "UseEdidDpi" "FALSE" (**) NVIDIA(0): Option "DPI" "100 x 100" (**) NVIDIA(0): Enabling RENDER acceleration (II) NVIDIA(0): NVIDIA GPU GeForce 6150 at PCI:0:5:0 (--) NVIDIA(0): VideoRAM: 262144 kBytes (--) NVIDIA(0): VideoBIOS: 05.51.22.33.07 (--) NVIDIA(0): Interlaced video modes are supported on this GPU (--) NVIDIA(0): Connected display device(s) on GeForce 6150 at PCI:0:5:0: (--) NVIDIA(0): Proview LT582s (CRT-0) (--) NVIDIA(0): Proview LT582s (CRT-0): 350.0 MHz maximum pixel clock (II) NVIDIA(0): Assigned Display Device: CRT-0 Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x84) [0x80c4354] 1: [0xb7f26420] Fatal server error: Caught signal 4. Server aborting I've tried turning off APCI (no difference). Do I need to update the video card drivers? The process seems a bit daunting (one thread says to do it one way and another is all bits and pieces and says to do it a diff. way). I've even tried changing the xorg.conf to say "vesa" instead of "nvidia" but that doesn't make any difference. I think I shall stick my head in the oven now. |
Author: | jmairs [ Sat Jan 27, 2007 3:17 pm ] |
Post subject: | |
I got this problem AFTER I updated my nVidia drivers on an R5E50 updated machine. I reinstalled the drivers and it went away but now my 0.2 Air2PC capture card doesn't work. I'm getting ready to just slick the whole box and start over fresh. |
Author: | wsweier [ Sat Jan 27, 2007 4:33 pm ] |
Post subject: | |
I was tweaking my xorg.conf file for my TV and after a reboot I ran in to this problem. Fortunately, I had only changed one thing so I knew what to disable. I had added this line: Code: Option "UseEvents" "True"
After commenting it out. I did not have the "respawning" problem. Of note, I have not updated my NVIDIA drivers. XvMC seems to be working ok for me so I have not tried to upgrade. |
Author: | hurnik [ Sat Jan 27, 2007 7:56 pm ] |
Post subject: | |
Well ironically after the 5th reboot it's all fine now. How strange is that? If I had the "definitive" steps for upgrading the video card drivers, I would attempt it (actually got stuff backed up so I guess I'll try it anyway). I see two diff. threads on upgrading the drivers and it seems to be quite a nasty process. |
Author: | ebeighe [ Mon Feb 19, 2007 4:22 pm ] |
Post subject: | Re: Augh I'm cursed - id "c7" respawning too fast |
Suddenly, my system too fell victim to the dreaded: INIT: id "c7" respawning too fast: disabled for 5 minutes. Rebooting numerous times doesn't seem to have helped. My xorg.conf file is unchanged. The hardware seems to be fine -- as a test, I did a fresh install to another hard drive and that comes up just fine. The graphics are just an integrated i810, and this is all with KM 5E50. It is just a test system, but I am wondering what the root cause could be? or what is a less disruptive (than a new auto-install) way to recover? I made a half-hearted attempt at doing a knoppmyth backup, from the working installation. And then tried to untar the backup file over top of the drive that was suffering from the "respawning" problem. After that i never really got it going, so I gave in and reloaded everything from CD. EDIT / UPDATE : After another fresh software install from CD, the next day when I booted up my whole hda1 partition was messed up. So, in my particular case, I think I was suffering from some sort of hardware failure... Probably a bad a hard disk. |
Author: | hurnik [ Mon Feb 19, 2007 5:58 pm ] |
Post subject: | |
I did finally get the problem to go away by upgrading the video card drivers (I did finally figure out the steps). Of course, after upgrading the video card drivers, after the 2nd reboot, it trashed my SQL database, so I reinstalled all from scratch. Haven't had it happen again. |
Author: | neutron68 [ Thu Feb 22, 2007 1:47 pm ] |
Post subject: | happened to me too! |
I had this EXACT thing happen to me last night during the painful nvida upgrade process. I was following this thread: http://mysettopbox.tv/phpBB2/viewtopic. ... highlight= and after the nvidia driver scirpt finished and I rebooted, I started getting the "INIT: id "c7" respawning too fast: disabled for 5 minutes. " message. I was so scared that I had hosed my system up. In a panic, I went back to the thread and found my solution near the bottom of page 1. MrFahrenheit posted that he had to run the following commands: update-rc.d -f install-nvidia-debian remove update-rc.d -f nvidia-glx remove update-rc.d -f nvidia-kernel remove and then re-run the nvidia driver script. After a reboot, all worked. I wonder why the person who started the thread didn't have the "id c7" happen to him??? It is certainly happening to many others! |
Author: | steeve [ Fri Feb 23, 2007 11:19 am ] |
Post subject: | Re: happened to me too! |
neutron68 wrote: I had this EXACT thing happen to me last night during the painful nvida upgrade process.
I was following this thread: http://mysettopbox.tv/phpBB2/viewtopic. ... highlight= and after the nvidia driver scirpt finished and I rebooted, I started getting the "INIT: id "c7" respawning too fast: disabled for 5 minutes. " message. I was so scared that I had hosed my system up. In a panic, I went back to the thread and found my solution near the bottom of page 1. MrFahrenheit posted that he had to run the following commands: update-rc.d -f install-nvidia-debian remove update-rc.d -f nvidia-glx remove update-rc.d -f nvidia-kernel remove and then re-run the nvidia driver script. After a reboot, all worked. I wonder why the person who started the thread didn't have the "id c7" happen to him??? It is certainly happening to many others! I have seen this error message twice during my tweaking of xorg.conf or XF86Config-4. The problem, in my particular case, was that my text-editing was being done on a Mac, and apparently the different line-wrap and end-of-line functions in the Mac text editor caused Linux to barf up X. Once I edited using a Linux-based text editor (actually, I edited using the File Manager in Webmin), everything was fine. -sTv |
Author: | ceenvee703 [ Fri Feb 23, 2007 11:30 am ] |
Post subject: | Re: happened to me too! |
steeve wrote: The problem, in my particular case, was that my text-editing was being done on a Mac, and apparently the different line-wrap and end-of-line functions in the Mac text editor caused Linux to barf up X.
Kinda off-topic, but if you want to edit on your Mac and retain proper line endings, use the free TextWrangler from Bare Bones software: http://www.barebones.com/products/textwrangler/ If you do a Save As you have options for either Mac, DOS, or Unix style line breaks. |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |