Red Hat / Fedora :: Boot Hangs After SELinux: Disabled At Runtime?
Mar 8, 2010My Redhat box hangs on boot up after "SELinux: Disbled at runtime" Code: raid1: raid set md0 active with 2 out of 2 mirrors
[Code]...
My Redhat box hangs on boot up after "SELinux: Disbled at runtime" Code: raid1: raid set md0 active with 2 out of 2 mirrors
[Code]...
My Redhat box hangs on boot up after "SELinux: Disbled at runtime" ...
Code:
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
[Code]....
how to restore them properly.
I've just installed Fedora 12 (32 bit) KDE on my test system and have a couple of issues.I haven't played with Fedora for a couple of years, so I'm not very familiar with it. I haven't had the problems with Kubuntu, OpenSUSE nor Mandriva, so I'm a bit in the dark here. I'll see if someone can help me with my sound issue, before moving on to the next problem. I've read seveal posts about sound issues, but not sure exactly if any are the same as I'm having.
After installing Fedora 12, sound was all working fine. I think installed all the available updates, which is when the problem began. Basically, I have sound in Hulu, Firefox videos such as CNN, etc. But, I have no sound at startup or shutdown....system sounds, I suppose I should say. I have disabled SELinux and the firewall, before I began updates. Looking in KInfoCenter under Audio, I see:
Audio Devices: NOT ENABLED IN CONF VIA8247 with ALC655 at 0xc400 IRQ11 In System Settings>Multimedia I see Internal Audio Analog Stereo as the only device shown. I have unchecked Mute and have all volume controls up all the way in KMix, which shows HDA Nvidia on the tab.
am trying to Selinux in enforcing mode, but its giving below error.I have Ubuntu server 10.10root@ubuntu:/common# setenforce 1setenforce: SELinux is disabled
View 1 Replies View RelatedYou can find a list of all the booleans for SELinux (Fedora 10) using getsebool -a My question is, is there a reference online that describes each one. Most of obvious but it's one of those "I have to know because it's there situation).
View 5 Replies View RelatedAfter installing Fedora 14 and being satisfied with the behaviour and the packages installed for it, i want to replicate the same installation in a few more PCs, so i installed Revisor to make with it an iso file that reflects my actual installation.
The problem is that if i run the software from Applications->System tools->Revisor, nothing happens after giving the user password.
Then i run it from a consele and this error is produced after giving my password: "Cannot find anaconda-runtime in /usr/lib/anaconda-runtime"
But anaconda is the environment used for installation, so it is installed from the very begining. Why this happens?
I get a SELinux relabel often even without changing stuff. SELinux troubleshoot doesn't show any error nor are there any messages in /log/messages that give any clue. Where should I look to see whats happening ?
2.6.31.12-174.2.22.fc12.x86_64
selinux-policy-3.6.32-103.fc12
After I do a recommended SELinux change from an alert:
'grep blender /var/log/audit/audit.log | audit2allow -M mypol'
the next time I boot, I have to add the rule again. How would I make this permanent? Can this only be done with the SELinux Policy Generation Tool? I've tried making bug reports for some SELinux warnings.
So, I had fun with this one the past week. I had an FC11 system running just fine. Then one day it would not boot - it was hung somewhere inside the init script of the initrd image. CTRL-ALT-DEL would reboot the system. Using grub editor, I could temporarily delete the initrd line and boot into the system OK. But what was going on?
mkinitrd was of no help to me. I even did a yum update, which got a new kernel, which also generated a new initrd - no joy. I extracted the initrd file system and edited the init script. I eventually hit on this tidbit: If I commented out this line:
daemonize --ignore-missing /bin/plymouthd and rebuild the initrd image - the system would finally at least tell me what the problem was: mount failed for selinuxfs on /selinux. No such file or directory.
So, I examine the root (the real root, not the initrd temporary root) - and sure enough, no /selinux. I make one and reboot. The system goes into a "targeted policy relabel" operation, reboots, and I am back in business - even with my original, unmodified, initrd.
I have no idea what happened to my /selinux directory, but I think the initrd "init" script needs to check for this directory's existance, and make it if necessary. Or at least report that it isn't there. In FC11 right now the system just HANGS without this directory being present, without any clue as to what the problem is!
I am trying to install the Matlab 7.5 compiled runtime for 64-bit Linux (MCRInstaller.75.glnxa64.bin) and keep getting a "No Java Runtime Environment(JRE) was found on this system." error message.
I understand the JRE is bundled with MCRInstaller and will self-compile/install. However, I don't have admin access, could this be the source of the problem? If so, how could I fix it (not sure how to direct it to install locally without going into the source code)?
I got around this error before, but stupid me didn't write down what I did and I forgot.
ted my old laptop with windows xp home ed and Fedora (xp was installed first). When I boot to Fedora OS to fill in initial settings (user name, password, network etc) to get it up and running the mousepad doesn't work (there is no cursor). It still works fine in Windows.Anyone know how to get this sorted? The laptop is an HP Pavillion ze2000. No external USB mouse or similar has been used.
View 3 Replies View Relatedi am trying to install centos 5.5 x86_64 as a guest OS in vmware server 2.0.2 using netinstall iso. Installation runs fine until the point, when it tries to install selinux-policy-targeted-2.4.6-279.el5.noarch, the whole virtual pc hangs at this.any ideas? i tried to google few things about this, but i have found nothing. this has happened 3 times in row, whole virtual pc always hangs at the same package. i dont have any other problems with vmware, gentoo runs and installs fine in it.i would prefer to do installation using netinstall.iso, it would take a lot of time to download all cds or whole dvd and all i require is a very basic set of packages.
View 7 Replies View RelatedI have been using F10 since its release and have not had any trouble until now. During my last session, I ran an update. Today when I boot my desktop (single boot btw), it hangs just after the boot loader. The only sort of warning is:
eth0: link up, 100Mbps, full-duplex, 1pa 0x45E1
I have browsed the forums to no avail. Other have the same issue, but with no posted solution. I have tried disabling NetworkManager, but I think it may be the service that runs after NetworkManager.
i've installed nvidia driver by
Code:
yum install akmod-nvidia
every thing went ok , but after reboot the system hangs right after
[code]...
Boot-up hangs at black screen with blinking cursor in upper left corner for over 2 minutes before continuing. I select F 14 with grub hit the enter key and go straight to a black screen with blinking cursor. Hitting the esc key does nothing until boot-up actually starts. Afterwards, boot-up is perfect. I had this problem a few upgrades ago and the fix was simple but I can't remember what I did. I've searched every phrase I can think of and can't find a thread that addresses my problem.
I have a F 13 kernel on my machine and have no problem booting it.
Dual-boot, F 14 and windows 7, 64 bit.
After doing a reinstall, and then upgrading, I have a problem: as the boot script comes to ATD, it hangs. Someone suggested doing an interactive start ---- and it worked! Just say no to ATD, and boot goes well. Of course, I don't really want to do that each time. How do I remove it? That is, get it out of the init.d or rc.d boot procedure
View 4 Replies View RelatedWhenever I boot fedora core 13 it starts Plymouth and a txt progress bar starts at the bottom. Whenever it gets to 100% it flickers a little bit then does nothing. The system doesn't hang I can still crrl-alt-delete and it shows the processes stopping. When it displays the programs starting it gets to jexec and nothing happens.
View 1 Replies View RelatedI have just completed a dual boot installation of FC10. The install was done from CD's I downloaded from the Fedora website. The installation (seemed to have) went fine, and the machine still boots into XP if selected from the menu. The Fedora installation does not complete the boot process. I have three bars that move across the bottom of the screen, and the Fedora 10 graphic tuns white, and then the system hangs. I have let it sit at this screen for as long as 30 minutes. The screen will blank occasionally, but returns to the same place if I hit a key on the keyboard.
I have it installed on an old HP E800 netserver, running dual P3-866mHz processors, 2GB ram, a ATI Radeon 7000 video card, and three 36GB SCSI drives, non-raid. I know FC10 will run on this machine, as I have a friend running it on another E800 without any problems. This machine does have on-board video that is disabled only by plugging a different video card in (Phoenix BIOS).
In F10 the boot sequence hangs just after loading anacron. I booted with interactive mode and after saying 'yes' to starting anacron I'm prompted to start 'local'. When I say yes, my system hangs.
I've seen quite a few posts regarding very similar issues that people were having. None of them seem to have a clear cut solution.
Some posts mentioned about the wrong video drivers, however I've been using the same video drivers for a couple of months now and never experienced this problem.
I looked at /etc/rc.local and all it has in it is 'touch /var/lock/sybsys/local'
I also looked at the file above and there is nothing in it.
Any ideas/solutions? Everything was working just fine the other day. so I'm completely baffled.
Running kernel-PAE-2.6.29.6-217.2.7.fc11.i686
Boot hangs on 'starting atd'
Select 217.2.3 and it boots OK.
This is one of those newbie questions about where I look to find error messages so that I can understand what the issues might be. My Fedora 12 setup invariably always hangs whenever I login following a cold boot. I login to x/g-nome, the screen clears and the initial background appears and then that's it.
I've been getting out of this by switching to another TTY (CTRL + ALT + 2), login as root and issue "shutdown -r now". System re-boots and I can login normally. I can see a stream of messages, I think relating to x scroll up the screen rapidly after the shutdown command. I'm not fast enough on the Pause button to read them. My question(s) then is... is there somewhere I can look to see what those messages might be? From the symptoms described initially, anyone have any thoughts on what the issue is likely to be?
I have just upgraded my F11 x86_64 system using the DVD ISO.
After rebooting as requested:
1) Cupsd fails to start - it can't find libaudit.so.1 (this doesn't worry me in itself).
2) Boot process proceeds until starting hald. This gets an OK response, but then the process hangs. No further output appears on the console. Pressing [ENTER] just causes a blank line to appear on the console. Pressing CTRL-ALT-DEL causes a reboot, and the same symptoms re-occur.
I'm tempted to boot with the rescue disk, save a few critical data directories, then start afresh with a clean install, but is there anything I can do to salvage the upgrade?
I currently dual-boot Windows Vista and Suse 11.2 on my Gateway desktop machine. I'd like to try out Fedora in a triple-boot situation.
My trouble is that the F13 Live CD hangs during boot. I've checked the hashes of the downloaded ISO files, and done burns on multiple media. During booting with the Live CD, my box hangs and I have to use the physical power button to turn off the box.
I've tried the 64-bit KDE spin (my preferred choice), the 64-bit GNOME version, and also the 32-bit KDE spin, and all of them hang at the same point. Removing the "quiet" boot option shows that it hangs after setting up my built-in card reader. When I installed Suse 10.3 on this same machine, I had to use the flags "acpi=off" and "brokenmodules=pata_it821x". Would the syntax be the same if I wanted to try with those boot options with the F13 Live CD?
Using the ISO files in VirtualBox inside my working Suse install works just fine.
After Gnome logon it may hangs in any moment (window scroll, app start, opening url)
If sound was playing in that moment it continuously repeats last sample (about 1 second length), but do not respond to mouse move/click or keyboard. If to let it stay in this state nothing change - sound sample still repeats and no response to input. I need to reboot it by reset button. Sometime when I press reset nothing happen then after couple of seconds computer turns off, after 1-2 sec on and then starts booting.
During first 15-20 minutes after booting it may hangs multiple times but after that it works without problems.
Tried do not logon 20 minutes after boot - do not help, it hangs anyway. Only helps logon and do nothing for awhile.
This behavior have started after F12 installation. F13 installation changed nothing, only F11 worked perfectly.
I recently upgraded through 'YUM' from Fedora 14 to Fedora 15. The upgrade appeared to be successful until it re booted, ever since then it hangs at
Code:
Started SYSV: Enable monthly update of smolt.
I have downloaded the ISO and burned it to DVD on another system which I used to try to rescue the installation, so far to no avail. My system specs are in my signature below (Laughlin is what I upgraded from).
I am installing Fedora 15 as a guest machine on virtual box. the installation completes fine, but it gets hanged on the date and time screen during first boot. Even on clicking "Forward" button it doesn't work and just gets stuck there.
I am using windows 7 as the host machine and I have given 1 GB ram and 8 GB hard disk to guest fedora OS.
Before the installation, I checked the media also it was shown to be correct. The media I am using is virtual clone drive for DVD ISO image. VirtualBox version 4.1.2 was used.
I installed fedora on my second hdd, the other one had xp before fedora, now in grub it shows xp as other and wont boot into it, just hangs there. SDC is an external drive and sdb is the xp drive as you can tell by the filesystem.
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x836db2c4 .....
I'm attempting to install F12 64 bit. I currently have F10 running on this system. I'd like to do a clean install. I'm using the DVD. I boot the computer with the DVD in. I choose the first option (Install or upgrade). It starts the boot process and then it hangs. [URL]
After asking at #Fedora I was given the advice to boot with `intel_iommu=off`. That gets me slightly further in the process. It gets to the point where anaconda is starting. Then all heck breaks loose. It appears the monitor loses the signal from the computer (power light turns red just like if the computer was off). The caps lock and the scroll lock lights on the keyboard blink about once a second. The DVD drive continues to spin for about a minute and then stops. Since I have no display, I have no idea what's going on.
I was using Ubuntu 9.10, until I got a new graphics card (Nvidia GeForce 9800 GT). After I got that upgrade, Ubuntu no longer supported that card for some reason, so I decided to try Linux Mint since it was a close relative to Ubuntu. Still no support for the video card.
I've always wanted to try Fedora so I decided to grab the x86_64 live cd and burn it. I stick it into my disk drive and it boots where it shows me the options to "Boot" "Verify and Boot" "Boot from Hard Disk" and one other option.
I tried the Boot option, and after selecting that, everything stalls, and my display turns off (not the entire monitor, just the display). I tried Verify and Boot, and still no luck.
I have also tried the i686 live cd and the same issue. It can not be the way I am burning it, cause I've gotten other live cd's to work with the same method of burning. Is it that Fedora does not support the card?
I am trying to get the GNOME version up and running.
I'm using Fedora 12 on my Thinkpad X200 and had no major problems since Installation of the Release Candidate. Unfortunately, since a week Fedora makes trouble when booting:
The system boots some times without any problems, some other times it hangs in the following way:
Code:
Gdracut: Mounted root filesystem /dev/sda1
dracut: Switching root
Welcome to ^[[0;34mFedora
Press 'I' to enter interactive startup
[Code]....