Whenever 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 RepliesI have a fresh install of 10.04 and i have changed my playmouth theme to spinfinity and now when i boot its plays the animation and then justh the ubuntu logo on the screen.....ice let it sit at this state for hours...when i push the power button on my computer the logo goes away and ubuntu proceeds to shut down.cant log into my desktop to change the theme back to the default....im on another partition at the moment....how do i change my theme back to the default?
View 1 Replies View RelatedI've been playing around in attempt to see how small a usable kernel I can build. The theory is that it should mainly be useful for preparing a recovery disk or some such thing; disk drivers and a few network drivers are what goes in.
I built the kernel with the attached config. It boots, reaches the hdd (if I specify root as /dev/sda5 manually), then dies when it tries to start Plymouth (something about catching a SEGV signal). What needs to be enabled to run Plymouth? Alternatively, has anyone managed to remove plymouth from boot on Maverick?
(That would require a modified mountall version, I know.) I'm using the mainstream kernel 2.6.32.27 sources on Maverick (yes, I know Maverick uses 2.6.35; but this does boot).
Hardware: Wireless-RTL8192SE b/g/n, uses an out-of-tree driver (r8192se_pci, from Realtek; Ubuntu builds in an older version of this driver); r8169 works for ethernet; ATI Radeon Mobility 3200 graphics, AMD Neo X2 cpu; SATA hd in AHCI mode.
I have just installed the F13 XFCE spin on my netbook (Asus Eee 1000ha), and can't boot past where Plymouth is supposed to start. The message I get is below.
[Code]...
I have a dual boot of fedora 12 and vista. Everything worked fine until I tried to install a new booting theme. Here is what I did:
su -
yum install plymouth-plugin-{fade-throbber,label,space-flares,throbgress,two-step}
yum install plymouth-theme-{charge,fade-in,solar,spinfinity}
[code]...
I have successfully installed the Nvidia driver on my FC13 system that is using an Nvidia NV44 (Ge 6200) card. It seems to be working as I see the nvidia driver when I do a lsmod | grep nvidia and the glxgears program works as well as the nvidia-settings program.Basically, I did the following:
Code:
yum install kmod-nvidia-PAE
new-kernel-pkg --mkinitrd --dracut --update $(rpm -q --queryformat="%{version}-%{release}.%
[code]...
I 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 RelatedI'm using Xubuntu 10.10, with 2.6.35-24-generic kernel. I'm 64-bit. If it helps at all, I'm using xorg-edgers, but that doesn't seem to mean anything here.My issue is that Plymouth is doing absolutely nothing on boot. I know this from using bootchart and seeing that Plymouth launches itself three times, but not seeing anything every boot. The only splash I do see is after I log in, the mouse thing, but that's XFCE.
So, how can I either remove Plymouth entirely, get it working, or find a better splash program? The reason why I ask how to get rid of Plymouth is because it may be entangled in some things that apt-get purge wouldn't fix.
I have Fedora (12 plus some rawhide, but mostly 12 because I am not up to date) with the Nouveau driver. I tried to switch to the solar plymouth theme, but I only see the ASCII progress bar at boot. But when I shut down, it work nicely. (I have updated to initrd and menu.lst)
View 2 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.
Since I've been using the nvidia drivers (from rpmfusion) and followed Leigh123's nvidia guide, I don't have a Plymouth graphical boot anymore. Instead I get the black screen and the blue/white bar at the bottom. I installed the plymouth-theme-solar (or whatever) and switched to that, updated initrd too, but no difference - same thing happened. This is an AMD64 system, latest kernel, latest nvidia drivers. Snippet of grub.conf:-
title Fedora (2.6.31.9-174.fc12.x86_64)
root (hd0,2)
kernel /vmlinuz-2.6.31.9-174.fc12.x86_64 ro root=/dev/mapper/vg_undertaker-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet selinux=0
rdblacklist=nouveau
initrd /initramfs-2.6.31.9-174.fc12.x86_64.img
This happens on boot on Fedora 15. Plymouth Boot Screen just stays there and I can't login. Searching around suggested kmod-nvidia to cause this (one moth ago ofc), but here I am with Intel Graphics and the default drivers.
View 6 Replies View RelatedI have searched the forums on this problem and I am still not really clear on the fix for this or even if I should wait for final release. I am running Lucid 64bit and have upgraded through the cycle from Karmic. I am using nvidia proprietary drivers. All the time that the Plymouth boot screen has been available it has been in low resolution. As we are now at beta 2 I am torn between searching a fix or waiting for the final release. So, from what I have read I need the 'nouveau' driver to fix this issue.
1. How do I install this in place of my existing nvidia proprietary driver?
2. I am a little bit confused by the hardware drivers selection panel telling me that I have an nvidia driver installed but that it is not in use-I read that this might be a bug?
I cant get a bootsplash image at all during boot/shutdown. Anyways I tried some solutions and kinda realized I dont have /etc/initramfs-tools/conf.d/splash. Could that possibly be it? And if so, how do I fix this. 10.04 Nvidia graphics Is there another solution to plymouth? I tried splashy and usplash wont install. So anyone else know a way.
View 1 Replies View RelatedI changed the Plymouth Theme following the direction on this page:
[URL]
Basically, I put this in the Terminal: sudo update-alternatives --config default.plymouth
I then selected a theme (I believe it was spinning something or other). Then I entered: sudo update-initramfs -u
Now, when I boot up, it just sits on a blank screen after I select to start up with ubuntu. I can't boot into ubuntu at all.
quite a while ago i decided i wanted to change my splash
View 1 Replies View RelatedI 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.