Fedora :: F15 Works But Causes Next Reboot (into Any OS) To Crash?
Jul 19, 2011
I haven't seen anything like it before. I have F15 installed dual-boot with Windows Vista, and I've updated packages. Booting into F15 works fine, no issues.
However: if I shut down and reboot into either (a) Windows or (b) even just the BIOS config screen, the system crashes abruptly after about 1 minute (with no warning/error) and tries to reboot. Booting straight back into F15 sometimes seems to cause the issue, but not always.
The reboot then fails, it doesn't even get to BIOS screen - all that happens is disk lights (HDD, DVD-ROM) keep thrashing. Manual reboot (hold power button for 4 seconds until shutdown; press power button to restart) doesn't help; reboot still stalls. Only disconnecting from mains power, reconnecting, and rebooting works.
It might not even be a Fedora issue - I've tried recent Ubuntu and Mint 11 live CDs, and they cause the same problem - but I'm posting here since I like my F15 installation and want to keep it I've noted that older distros on live CD (eg. F14, SuSe 11.3) don't seem to cause this problem. Maybe a recent kernel issue?
How can something in F15 persist across soft reboot and crash a completely different OS?
after playing games using WINE, I noticed that the system went Black screen of death.
I had to hard boot the system and now system is hanging. However, I can ssh into the system from another machine so I know only X windows hung.
I can log in using NX client without any issue, but can not log in from the console.
This is the entry from .xsession-errors: GNOME_KEYRING_SOCKET=/tmp/keyring-4P86Nb/socket SSH_AUTH_SOCK=/tmp/keyring-4P86Nb/socket.ssh Window manager warning: Failed to read saved session file /home/stranger/.config
it stuck after loading. should got login window. instead it show me a blank page and a blinking courser i can only press ctrl+alt+del it will reboot my laptop n stuck after the loading process
I have install fedora11 live and the mouse work well when installing.When you reboot the mouse works ok until the welcome screen apears then the mouse stops working and I cannot continue with the postinstall. I have a 1TB usb externalHD that I am installing fedora11 and have partitioned it so that I have 500Gb free for fedora, system is doucore 2.4,4gb RAm, I tryed doing this with three differend mice and connectting the mouse to different usb ports
After a system crash while watching a video with vlc and downloading somthing, i can't reboot my system.In the secure mode i get this informations[4.774621] device-mapper: dm-rai45: installized v0.2594b[ 1166.832045] ACPI: EC: non-query interrupt recived, switching to interrupt modeNow the scree is black (20 minnutes later
I have a gentoo distribution and need to store the information of dmesg collected until a system crash. At present, after a reboot or a crash the information in dmesg are lost and are not available at the next reboot. How can I save all the information in dmesg until a crash and read them after the succeed reboot?I also checked for dmesg.x files in /var/log or similar files but with no success.
OpenSuSE 11.4 KDE 4.6.00 "release 6" Intel(R) Core(TM)2 Quad CPU 3.0GHz 8GB RAM nVidia GeForce 9500 dual monitor Graphics card
This is a relatively new install. I had a RAID failure that required a complete rebuild from the ground up. Anyhow what happens is I can burn a CD or DVD using my burner and k3b. But only once, then in order for it to work again I have to reboot the system. I don't like rebooting as this is a work system and I just want to use it as such.
Anyone else have this issue? How do I correct it. Ironically I had this very same issue with 11.2 and 11.3.
This was my first experience with Ubuntu, I was told to switch the hard drives on my computer and put the Windows drive in a safe place for the install. The first time I did the install on the hard drive (which was the clean second hard drive that came with my computer), I either didn't realize I believe I didn't realize I had to click a button and thought the install had gotten stuck, and therefore cut off the install midway through. The second time around the install went without a hitch, and I was able to boot to desktop once. There, I was notified that I needed/should install NVIDIA drivers, I believe version 173 was listed as the next most recent drives (the other was "current"), I have an NVIDIA GeForce 7350LE graphics card, and after installing the drivers, I went to the restart menu as directed and clicked restart, not shut down but restart, and there were several listed errors on the text/DOS screen, shutdown errors I believe (the errors were 5 digits and were something like 56759 or something like that, I can't be certain if I'm remembering right, though, but there were two errors going over again). I then proceeded to turn off the computer manually, and upon it coming on again, instead of the normal Ubuntu flash screen before login, a more choppy Ubuntu 10.10 screen popped up and it led me to the DOS mode, where I was able to login, but it did me no good because I don't know command logic for Ubuntu. The best I did (its the best I ever do when these things happen) is get menus to pop up that are basically useless. I turned the computer off and on again three times, and tried booting directly from disk, but that failed.
I'm actually using the same computer I just reinserted the Windows drive back in after the frustrating experience. Windows has been giving me problems itself, and I really wanted to switch to Ubuntu but I need to know that this is a fluke and not the norm. I can live with this sort of thing being so uncommon I must have did something that was very strange and out of the ordinary to my computer. But if its commonplace, I want to know that too, because that's just something I can't live with.
used these drivers(dident work at all without it, no lights even): [URL]
and i first tryed it out on my netbook (aao, intel atom ubuntu 10.04 32bit), i ran make, then make install, done! i pugged it in and im happly using a 300mbps wifi network.
then i try it on my desktop (custom, AMD phenom x4, ubuntu 10.04 64bit), i install, no errors, then when i plug in the wifi usb, it lights up, then stops, the mouse also stops working(bouth keyboard and mouse is usb) but the kb still works. aftor restarting keeping it pluged in, ubuntu never finishes the splash screen, just stops their, i try again without the wifi and it works, i keeped trying and now the whole comp frezes, even the kb, and i see the system monetor is also frozen, what do i do?
one last thing, it works on bouth my netbook and desktop under windows 7, only on my desktop it wont work on ubuntu.
Basically i set up a webserver using this tutorial but installed ubuntu 10.10 [URL]
im using charter cable and it has that ubee router. when i tried to set up the static ip the closest thing i saw was an option called static ip lease in which input my servers local address and mac address and checked enable. then i applied dmz to my servers local ip. after that i typed in my public ip and to my excitement it worked. so i began creating the website. i dont know if all that is relevant but just in case i didnt want to leave anything out. this is my first time with linux and servers and ive only been at it for about 5 days. anyways i made the website and everything was going good then i needed to reboot the server so i did. after reboot i logged into the server then went back to the other room where i worked on the server using putty from a pc and flashfxp and tried to navigate to the website in firefox. it didnt work. if i try to go to the website address from a computer on my network i get a problem loading page error from firefox and if im on a different network it shows my router page to login and configure. i dont understand how it was working then after reboot it all of a sudden doesnt.
o also i installed gnump3 today before reboot if that is important
When I mount Debian 8 live into VMWare Player 7.1.2 64bit, it works awesome with and without graphics acceleration enabled i.e I can get into the desktop and all that.
But, when I installed it, the reboot is just a blank screen. I am not sure how I can proceed from now.
I'm having a problem with my wireless connection. When it runs, it's perfect, but every once in a while (and increasingly more often) it randomly disconnects and doesn't reconnect when I click reconnect, even if I manually disconnect it. Every time this happens, I have to reboot the system, after which it works perfectly. Then it dies again.
I've checked around the forums, there are some similar threads but they seem to be specific to the wireless card. The reboot method works, but I'd really like to find a way to solve the problem without having to resolve to the Vulcan nerve pinch. I'm a real newbie to Linux and the more complex side of computers in general, and I hardly know what is what, so please excuse me if I seem a bit thick.
I'm using Ubuntu 9.10, and a usb webcam that is shown as 'Bus 001 Device 005: ID 0ac8:3450 Z-Star Microelectronics Corp.' by lsusb.
The problem is that on connecting the cam, it just works with the first program I start (skype, tokbox, messenger), and if I disconnect it or switch to another program, it stops to work and I have to restart my computer to make it work again.
Is there some good solution to reset the camera without rebooting to make it work again?
I'm running Fedora 15 with current updates and kernel. I do not have anything special or non-standard about my configuration or setup. I use grsync to sync my home folder files to a remote rsync server on my network. I've checked my hard drives and my memory and everything else I can think. Here is the problem:
grsync will run for some time and once it nears completion it will crash. This, however, is no standard crash. It literally shuts my computer "OFF". I have shared the remote rsync folder through CIFS as well and I can copy those exact same files through nautilus with drag and drop without issue. I have had a few occasions where the rsync process will complete without issue, but this is a rare occasion. Since it powers my computer completely off I do not enjoy the luxury of having any log files or messages to attempt to diagnose from.
So I puts my shinny new F12 install on my new computer. It's a little climb for me but for the most part easier then some of the other F's that I have tried to install.
One problem I have right now is my inkscape crashes as soon as I try to put some text on a page. I tried the automatic bug report thingy but it complained about me not having a log in. inksacpe is really becoming a very important application for me, I have been trying to shy away from the Windows programs I have been using.
I must say, F12 seems to really be advancing the fedora project into a nice desktop system.
after mistyping my session passwd at the kdm login, I retried again and the greeter instantaneosly crashed and X died on tty1 (black screen, blinking cursor in upper left corner) Switching to tty2, I tried to login again but did not succeed to start X again, so I rebooted the system and looked at Xorg.0.log.old. There I found: xf86CloseConsole: VT_WAITACTIVE failed: Interrupted system call
Here we go again!
P.S.: I do not know how long this error exists, I noticed it only yesterday and the updates today didn't help.
I have recently installed Fedora 9 about a dozen times and everytime I apply the recommended system updates, the system crashes upon reboot, leaving me at a dead "GRUB" message (not a prompt). I would love to be able to update my version; suggestions?
I am using sda1 as /, which is a bootable drive. I do not know if my problem is that I did not create a /boot drive. After removing the iso dvd, I tried to reboot and I get this back: -bash: /sbin/reboot: input/output error Then it returns me to the terminal prompt.
Fedora 10 64bit install from DVD. Working my way through the how to's, this is my first linux experience!When I choose the user switcher > other OR system > Logout user > Switch user my system goes to a blank screen and I can only get it back by using the reset switch (or power off)If user1 logs out, user2 can then log on and vise versa.I can go to applications > terminal as user1 and su user2 no problem ( and back to user1)but if I use the user switcher = problem.I am fairly sure that the users are set up correctly, they all work individually.I searched the forums and there seems to be no current similar problems mentioned.My system is a gigabyte GA K8VM800M (onboard graphics and sound) AMD Sempron 1GB ram 40GB HD I used the DVD to install on to previously used HD with no other OS on it, I chose the 'use the whole hard drive for fedora' option and had no reported problems with the install.Have I got something set up incorrectly? or where should a look for help on this.
Almost everyday my notebook freezes. I know the kernel is still up and running because I see my hd led activity lit from time to time and when I pressed the wifi/bluetooth button it also lit on and off with no problem.
The problem is my XWindows, it's just freezes and there's nothing I can do with it. I still can move my mouse cursor but I can't click anything because the screen is just freezes.
I tried to pressed Ctrl + Alt + F2->F5 to go into console mode. Not working.
The only workaround is turn-off and turn it on again.
This happened after I installed F11. with F10 I have never seen such problem
I have a crash that occurred after first install while updating. The update was 1.2GB Had to reboot 5 times to complete the update downloading process. Much of what I read suggests KDE, xorg and qemu as part of what is causing the crash, but I haven't found a similar issue. After the update completed installation the crashes were less severe but still occur when updating.
Code: yum update The latest crash occurred after yum update and left a large amount of information in konsole. It disables wireless networking so not sure how the bug is related. During the first yum update I had to reboot the system to get full functionality back. After the first update I just had to wait for system to return to normal.
Code: Complete! [Whereareyou@Iamhere ~]$ kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so <unknown program name>(2413)/ KStartupInfo::createNewStartupId: creating: "Iamhere;1274481784;509281;2413_TIME0" : "unnamed app" kbuildsycoca4 running... Error: "/var/tmp/kdecache-Whereareyou" is owned by uid 500 instead of uid 0. kbuildsycoca4(6739) kdemain: Reusing existing ksycoca kbuildsycoca4(6739) KBuildSycoca::recreate: Recreating ksycoca file ("/var/tmp/kdecache-Whereareyou/ksycoca4", version 162) kbuildsycoca4(6739) KBuildSycoca::createEntry: new: "screensaver.desktop" kbuildsycoca4(6739) VFolderMenu::pushDocInfo: Menu "applications-kmenuedit.menu" not found. kbuildsycoca4(6739) VFolderMenu::mergeFile: VFolderMenu::mergeFile: "/etc/xdg/menus/applications-merged/ggz.merge.menu" kbuildsycoca4(6739) VFolderMenu::mergeFile: VFolderMenu::mergeFile: "/etc/xdg/menus/ggz.menu" ................................cut out info to fit post requirement kbuildsycoca4(6739) KMimeAssociations::parseAllMimeAppsList: Parsing "/usr/share/kde-settings/kde-profile/default/share/applications/mimeapps.list" kbuildsycoca4(6739) KBuildSycoca::save: Saving kbuildsycoca4(6739) kdemain: Emitting notifyDatabaseChanged ("services", "apps") --Cursor stays here, hanging out--
I upgraded from F12 i686 to F13 (I should say clean install). And now ever so often my computer locks up...... I will wait for an update or something this week but if it continues after I may have to go back to F12 (on another HDD)
I tried upgrade with dvd media and preupgrade from F12 but in both cases there is anaconda exception. I have dual boot windows xp (/dev/sda1) and F12 (/dev/sda2).
sudo fdisk -l /dev/sda: Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xa070b627
I've just installed F14 64bit on my desktop and I tried to run Open Office Writer. As a result, GNOME crashed and the rendering of the desktop was messed up. I had to force a reboot, and now everytime I login the Open Office recover dialog causes a crash again. I suppose it has something to do with the opensource nvdia drivers and OO.o's toolkit but I can't look at it with the crash-on-login thingy there (I suppose I can install the closed source drivers from a tty now that I am thinking it again....)
---------- Post added at 07:27 PM ---------- Previous post was at 07:24 PM ----------
Uh... actually I can't install the closed source drivers. Yum finds no mirrors for rpmfusion >( ...or the Fedora repos :
