Fedora X86/64bit :: Installation Failure With 11 X64
Aug 18, 2009
When I attempted to install 64-bit Fedora from my DVD, it failed while installing packages with the unhandled exception:
"
Traceback:
File /usr/lib/anaconda/users.py, line 163, in setRootPassword, self.admin.setpassUser(rootuser,cryptPassword(pass word,algo=algo),True)
File /usr/lib/anaconda/instdata.py,line 171, in write,algo=self.getPassAlgo()
[code]...
I know Python quite well but I have no idea why None is being passed as the first argument to self.admin.setpassUser when a non-None value is needed. The other curious thin is that the trace does not show the call to setpassUser() from the entry after it but rather to 'getPassAlgo(). Needless to say this but has kept me from installing Fedora 11 on my 64-bit machine.
UPDATE: decided to reinstall and run the partitioner to get rid of the raid. Not worth dealing with this since seems to be lower level as /dev/mapper was not listing any devices. Error 15 at grub points to legacy grub. So avoiding the problem by getting rid of raid for now. So ignore this post. Found a nice grub2 explanation on the wiki but didn't help this situation since probably isn't a grub problem. Probably is a installer failure to map devices properly when it only used what was already available and didn't create them during the install. I don't know, just guessing. Had OpenSuSE 10.3 64bit installed with software raid mirrored swap, boot, root. Used the alternate 64bit Ubuntu iso for installation. Since partitioning was already correctly setup and the raid devices /dev/md0,1,2 were recognized by the installer, I chose to format the partitions with ext3 and accept the configuration:
Installation process failed at the point of installing grub. It had attempted to install the bootloader on /dev/sda2 and /dev/sdb2. I moved on since it would not let me fiddle with the settings and I got the machine rebooted with the rescue option on the iso used for installing. Now, I can see the root partition is populated with files as expected. dpkg will list that linux-image-generic, headers, and linux-generic are installed with other supporting kernel packages. grub-pc is installed as well. However, the /boot partition or /dev/md1 was empty initially after the reboot. What is the procedure to get grub to install the bootloader on /dev/sda2 and /dev/sdb2, which represent /dev/md1 or /boot?
Running apt-get update and apt-get upgrade installed a newer kernel and this populated the /boot partition. Running update-grub results in a "/usr/sbin/grub-probe: error: no mapping exists for 'md2'". grub-install /dev/md2 or grub-install /dev/sda2 gives the same error as well. Both commands indicate that "Autodetection of a filesystem module failed, Please specify the module with the option '--modules' explicitly". What is the right modules that need to be loaded for a raid partition in initrd? Should I be telling grub to use the a raid module?
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
Just got the latest kernel update 2.6.31.6-162 for fedora 12 64bit and it won't boot on my PC. I just get a black screen with some text that doesn't mean anything to me. Computer is a s775 E7200 with nvidia 730i/9300 integrated graphics. I am NOT using hardware graphics drivers at the moment, having decided to stick with Nouveau drivers for a time. What system log tools do I need to identify the problem?
Running VirtualBox 3.2.6 under some host OS (should be irrelevant which one, right?), I created a machine, intending to install Fedora 13 on it. Got the Fedora 13 Live CD iso image, and an 8.6 GB virtual hard drive, completely blank. I set the machine to boot off the Live CD image. The Live CD boots nicely and I get to its desktop. I open "Install to Hard Drive"...and nothing happens. No error message, zip, nada. Inspection of the system shows a series of odd file systems, but I have no clue what they are for and whether they're usable or not.
The sticky [URL] mentions that the blank virtual hard disk should be partitioned and formatted beforehand...So I did, using the Live CD's Disk Utility (Applications: System Tools: Disk Utility). Although the sticky states the small /boot partition should be ext2 or ext3, the Live CD installer proposes to reformat it as ext4. Shouldn't we have formatted it as ext4 right away, then? Also, the installer set the /boot partition's size to 524 MB, not 200 MB as recommended by the sticky.
OBSERVATION: This was not easy because VirtualBox sets the display to 800x600 at most, and the Disk Utility spills beyond those confines WITHOUT PROVIDING SLIDERS. It was sheer luck that the required buttons (create partition, format partition) were barely reachable (at the bottom edge of the screen). This is a serious problem, because increasing the VirtualBox display size can only be done *after* installation (see for instance[URL] - since this guest addition requires rebooting the guest OS, it probably won't stick to the Live CD).
Once those two partitions are prepared and the virtual machine rebooted, "Install to Hard Drive" works as expected.
OBSERVATION: It is absolutely inexcusable that the Live CD installer (Anaconda?) does not propose to do this partitioning and formatting for the user. It is even more inexcusable that it should fail without giving any feedback whatsoever to the user.
Aside: VirtualBox's guest additions does not work correctly (for 3.2.6 anyway). The Devices: Install Guest Additions menu merely mounts a CD image VBOXADDITIONS_3.2.6_63112) without any feedback (expected feedback because the menu ends with an ellipsis). The CD, once opened, has an Open Autorun Prompt button...which fails to do anything. Manually running autorun.sh also fails. I had to manually invoke VBoxLinuxAdditions-x86.run from a terminal to get anywhere. Even then I was unable to go higher than 1024x768.
When tried to install Chromium from add./remove programs, the following error crops up
Dependency resolution failed: A package could not be found that allows the action to complete:
libicui18n.so.40()(64bit) is needed by package chromium-.0.252.0-0.1.20091119svn32498.fc11.x86_64 (chromium) libicudata.so.40()(64bit) is needed by package chromium-.0.252.0-0.1.20091119svn32498.fc11.x86_64
I just completed the latest updates to Fedora 14 - I have mono and wine on the system as well - so they were also updated. Now the only screen I can get is the failsafe (bash).
How do I recover my KDE desktop? (I noticed there were some updates for the KDE as well). I suspect something has failed during the update (selinux was also updated).
P**sed right off now, tested this upgrade on two test systems before hand to make sure this would work.Upgrade my server from FC9 to FC10, it had two Encrypted XFS volumes on totalling 1.5TB of files which I don't have space to backup anywhere else.Have now upgraded and the Encrypted volumes are showing as not existing "volume name does not exist"
BFO install via USB[URL]..I get through all of the initial menus, and to the main installer, after which is says "starting installation" (this is perhaps 2 hours into the installation). About 3/4 of the way through I get a dialog: "The file libssh2-1.2.4-1.fc13.i686.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source. If you exist, your system will be left in an inconsistent state that will likely require reinstallation. Reboot or Retry"
[screenshot attached] I have clicked retry several times and it doesn't continue. I have previously had no problem installing Fedora 13 beta with the same hardware.
I had a power failure during the portion of the upgrade after the reboot where it was upgrading the packages.I tried restarting the machine with the upgrade line in the bootloader but it says it cant find the bootloader. So I rebooted into the working install and ran preupgrade again, and after it reboots, it gives an error the it cant find "root" of the previous installation.even thought the machine boots and works, I cant tell what state I am in. the boot option lines, shows a fc12 kernel designation and the "about this computer" says "release 13"Also the add remove software doesn't show anything.
I was having problems performing an update yesterday that failed on dovecot dependancies and after a few tries I removed dovecote (it wasn't being used) from the installation and tried again. Everything seemed to be going OK then the update (about 160MB) hung and the screen went black a few times and I think then shutdown automatically. The PC then fails to reboot and displayes the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" I have tried to get the PC to boot with the super grub disc but without success (probably my in experience) I have also tried a suggestion from one of the forums to start the PC with a live CD and typed su -c 'grub-install /dev/sda at the terminal again without sucess. I have looked at the files with the live CD there are grub, menu and kernel files there (some are in lost + found, b ut don't know wheer these should be so have not changed anything.
Is there an easy way for the in-experienced to repair the boot process ?
The PC is a pentium 4 running Fedora 13 There is a 200MB boot partition formated as Ext3 and a 19GB partition formated as a LVM with Ext4 There is a CD drive but no DVD
Everything has worked OK for the past year through two online upgrades.
I have followed the Nvidia driver guide exactly. I did not see any errors during the four-step process. However, on the last reboot the system gets as far as the fedora "f" on the startup screen and hangs. This appears completely fatal. I have tried the procedure a couple of times now and the result has been to reinstall Fedora 14 from scratch each time. I have been able to access the system files after the crash using the system rescue option on the installation disk. I am on the Gnome X86_64 installation. My graphics card is NVIDIA GeForce GTS 240.
I,ve tried upgrade from F14 to F15 using preupgrade, but I run into serious problem. Preupgrade downloaded all packages without problem and prompt me to reboot. After reboot installation process went ok. It was upgrading cca 1650 packages. But installation hung around package 1600 (almost on end) with message that openjpeg-devel-1.4-6.fc15.i686 cannot be installed and only option to end installer. After reboot I ended up with "kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)". It is still possible to enter grub menu, where I can choose upgrade to F15, but it fails again on that openjpeg-devel package. When I enter terminal after failure, I can see package is downloaded in preupgrade repo (and after moving somewhere else and running upgrade again it I got message that package is missing). Is there any possibility to skip this package installation or only option is fresh reinstall?
I'm using couple of Intel Core i7 based workstations. Here is one such example:Processor: Core i7-870 (Lynfield) Motherboard: Gigabyte P55A-UD6RAM: Corsair DDR3-1600 - 8GB (4 sticks). Graphics: Sapphire Toxic ATI 5850 - 2GB - DDR5Am always used to 32-bit Linux installation. Now I would like to go with the FC14 64-bit on this workstation. My question is:a) How different would be a FC 64-bit compared to 32-bit (8GB RAM issues I faced in Windows 7 32-bit)b) What would be potential problems during the installation and/or post installation. I get these questions in my mind because of Motherboard and Graphics card support and also thinking about applications (issues) on FC14.
Just to reiterate on the title, the installation of Fedora 10 i386 (DVD) on a 32bit PC. Is failing on me after the media check (whether or not I do it), so not even making it to the language selection. Currently running a nvidia AGP video card was previously using an ati PCI card but swapping has done little to help.
The only argument that lets me passed this point is noprobe, which then fails a bit later as it can't pick up the install media. I've also tried a live CD which seems to be a bit hit and miss as to whether or not it even loads. It then either fails to even let me run the install to HDD or it comes up some error about failures in python code (Don't have the exact error as the last few times haven't even booted). Below is a couple of errors I get from the standard installer
My laptop died while installing F12, without completing installation. Now I can not boot the computer from HD, CD, or USB. I have flashed the BIOS with the most recent ROM. I can access the BIOS setup and exhausted all my options there, which is mainly boot order. At the moment, the boot process goes to a blinking cursor and does not allow for input. The laptop in question is a lenovo Y510 that was previously running F10 with a single partition.
I just installed Fedora 12 on HP Pavilion (dual boot with Windows vista). I made it all the way through the installation and created my user account. A few seconds later I got the login screen asking for my password. I enter the password and get "Authentication Failure."
The name that shows up on the login screen is my full name, not the user name that I created. Is that wrong?
I have installed fedora 14 in my computer. I installed some applications from root. I created a user id. I am unable to install my internet (broadband connection) now. every time it shows the error "Authentication failure" "install from root" something like that. How can I switch between user and root. Or how can I login as root again?
Been running Fedora for a while now, iterating up through versions to 12. Decided to to a clean install upgrade to 14. Apparently, bug mistake. Everything seems to be progressing fine, but after 'transferring install image to harddrive', the 'Starting Install Process' fails withsystem-config-lvm-1.1.15-1.fc14.narach.rpm cannot be opened.I have no idea what to do with this. I've reburned the install disk a couple of times (and checked the HASH) -- no apparent problems with the install media.Tech details: x86_64 install on a multi-pro box with a 3ware raid 5 controller (5 disk). I've never run LVMs. Two simple hard partitions (/ and /home). Fedora 12 installed with no problems (as did every other version of Fedora <=12).---------- Post added at 12:29 PM ---------- Previous post was at 11:54 AM ----------Some additional information:1 tried Fedora 13 -- wouldn't even recognize my disks. Installer hung at trying to find basic storage. Not a good sign2 tried my old Fedora 12 install DVD -- again, worked like a charm. Expect that F12 repos are now closed.
So, it seems as if some 'change' between F12 and F13/14 has made some part of the install process choke on my 'hardware' (I'm guessing something related to 3ware RAID card). ---------- Post added at 01:51 PM ---------- Previous post was at 12:29 PM ----------I just tried CentOS 5.5 (x86_64). Also installed fine. For some reason, Fedora >= 13 absolutely won't let me get past the problem noted in the OP. I suppose I could go with CentOS (for long EOL support), but I need some of the newer compiler/dev libs in Fedora 14 for some projects I'm working on.
I downloaded Fedora 15 Live and Fedora 14 Live to try to see where Linux is for music and broadcast audio on a laptop. It turns out I have to use 14. 14 and 15 both sort of work as live out of the box, although why they ship with the common Broadcom wifi driver missing and the touchpad tap disabled beats me. I also never found the magic button to close down 15. There must be one, but blow me I couldn't find it. Then I tried to follow the instructions at [URL] which mostly seemed to work. I need to keep Win 7 as this is the 32-bit test machine. I used EasyBCD v2.1 rather than the older version the guide is written for.
Booting into Win7 at first worked, then a boot into Linux stopped at a line that said something about a kernel thread helper Then Win 7 blue screened on boot, although it would boot to Safe Mode. Removed Veriface from the Lenovo laptop and it would boot Win 7. Tried setting Drive in EasyBCD to "Boot" rather than "C:" for Fedora. Now booting Fedora gave a Windows missing file message and croaked. Repairing startup with the Win 7 boot CD cured Win 7. Repeated the loop with the same failures. Re-partitioned and re-installed Fedora and just the same - a screen of text that stops. I can now boot to Windows and need help to sort out the Linux boot. How do I start to investigate the screen of text saying things like "__bad_area_nosemaphore" ?
I have failed to install an AT&T Sierra Wireless Aircard 881 on a Compaq 8510p running RHEL5 Server (Linux version 2.6.18-164.9.1.el5,gcc version 4.1.2 20080704, Red Hat 4.1.2-46. )
As seen in the dmesg output below, the OS detects the modem, connects it to ttyUSB0 - ttyUSB3. However, kppp is unable to access the modem.
I have followed Sierra Wireless instructions located at sierra wireless's website. (I would post it, but I've not made enough posts yet to link it in this message.) However, I was not able install the TRU-Install patch. The unusual_devs.h is absent on the machine, so patching was unsuccessful.
I'm stumped on what to try next. Is there a FAQ or guide on how to get a 3G modem running with RHEL5 Server? Ideally, I'd like to find something like the Internet Connection manager on Ubuntu. The modem works on that distro with no problems. I'm not able to migrate due to application and security certification dependencies on RHEL5 Server.
lsusb output: Bus 009 Device 001: ID 0000:0000 Bus 008 Device 002: ID 1199:6851 Sierra Wireless, Inc. AirCard 881 Device Bus 008 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000
Downloaded from here: [URL] then ,it is 32-bit and I need to know what all 32-bit libs are needed as dependency for skype to work. I am on Gnome Fedora and purposefully selected static version of skype to prevent installation of libqt4.
I just bought sony vaio laptop(EB16) couple of days before.I had window 7 OS. Two days before i downloaded Fedora-12-x86_64-DVD & installed in my PC.Everything is working fine except when i play any video or audio file such as .avi, .mp3 from any player such as vlc player, movie player ,xine etc , i don't get any sound.I tried to search this problem in internet but still i am not able to resolve this problem.
Im trying to set up my 3G modem to recive and send sms but I had no luck so far
Code:
Bus 002 Device 010: ID 19d2:0031 ONDA Communication S.p.A. ZTE MF636Im I tried with gnokii and wammu and many other things and did not want anything to do
I just upgraded via preupgrade-cli (from FC10), rebooted, the upgrade process completed, then the system rebooted and I just see a blinking white cursor now.I was able to boot up from a live cd of FC11, but I'm not sure how I can repair the system.
I'm running a P4 system with Dual ATI Radeon 2900HD Graphics cards. When I try to install F11, the graphical interface fails to start and I end up in a text install. I've seen plenty of information on how to fix the problem post install, however I'm not nearly advanced enough to then continue the installation (the text install does not install much, particularly doesn't install the graphical interface). Is there a way to work around this (IE a more complete text install, or somehow getting it to install in graphical user interface?)
