I have some programs, that will only install on i586 architecture (opposed to x86_64). My CPU is 64-bit architecture. Can I install FC12/11 with i586 kernel on the hardware? How? Any disadvantages except the fact that I'm supposedly not able to use the 64-bit feature of the CPU?
View 3 RepliesI just upgraded to Fedora 12 x86_64 via yum upgrade. However I have problems with booting. The new FC12 kernel won't boot. Boot output is something like
Code:
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sda to RAID set "sil_ajabaccaaidg
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sdb to RAID set "sil_ajabaccaaihe
No root device found Boot has failed
I resized boot partition to 400MB, formatted it as ext4 and recopied all files, modified fstab to update boot partition's UUID. Tried to set a boot flag on boot, still, I can only boot with the old kernel from Fedora 11. Is it a Fedora 12 kernel's bug or something wrong with my setup? I don't use any RAID, and the sil error is present with Fedora 11 kernel also.
I'm try to install: tora-2.1.0-1.fc12.remi.i586.rpm with yum but I keep getting depsolving problems.
I'm running Fedora 12. Here are some of the steps I've taken as per website:[URL]
yum -y install qt-devel qscintilla-devel qscintilla (OK, it worked)
then install the oracle instant client
yum -y localinstall oracle-instantclient11.2-basic-11.2.0.1.0-1.i386.rpm --nogpgcheck (OK, it worked)
next, add the LD_LIBRARY_PATH to your $USER profile
echo "export LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client/lib" >> ~/.bash_profile
and finally install tora itsel
yum -y localinstall --nogpgcheck tora-2.1.0-1.fc12.remi.i586.rpm (NO GO???)
yum localinstall tora-2.1.0-1.fc12.remi.i586.rpm
(here's the output)
Loaded plugins: presto, refresh-packagekit
Setting up Local Package Process
Cannot open file: resolvedep. Skipping.
[Code].....
Use 2.6.32.11-99.fc12.i686 kernel,
A package needs same kernel source to build.
Add/Remove Software show only: 2.6.32.12-115.fc12... & 2.6.31.5-127.fc12...
How to get kernel-devel-2.6.32.11-99.fc12.i686?
I had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10
(hd0, 1) 120GB : /home
(hd0, 2) 30GB : /
> First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
---
default=0
timeout=0
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
hiddenmenu
[Code].....
We bought a board with vortex 86x processor. we tried to install RHEL6 beta version. when we select the installation choice we were getting below error: "This kernel requires an i586 cpu, but only detected an i486 cpu. Unable to boot please use a kernel appropritate for your cpu."
We have contacted the board personal. he said(in his words)"If you need to use redhat, you have to use the config & patch file provided in the development note to develop a kernel which is suitable for redhat."
I was helping my cousin move to the GNU Linux world and I was faced with the following problem: He has a MSI nVidia GeForce FX5200 PCIe (128MB vRam) Graphics card. I followed a couple of instructions here in getting that card to work, but the drivers that I was able to load up to his 23 bit system refused to load after system boot up (white flashing letters would come up, X server refusing to load). I was only able to load the system with full 3D hardware accelerated support when I loaded the old xxxxx.i586 based kernel from the GRUB list, while the current kernel that was being used was xxxx.i686 based one.
Currently there was two kernels in the list, so I manually edited the GRUB file to change the boot identifier number from 1 (xxxx.i686) to 0 (xxxx.i586) so every time that the computer would be powered on, it would load that kernel up automatically without having to reselect it manually each time.
Yesterday, my cousin picked up his computer, he was fine and happy with his fedora core (version 11, because Version 12 had major problems with this graphics card, its on the "test" list still, and the developers of fedora, or the developers of that other 3rd party software source seems to be in the middle of testing it for FC12 compatibility)
He told me today that after he ran the "updates" for fedora and installed them, when he rebooted the system, he would see that same while characters in the top left section of the screen flashing and it would get stuck there, he told me that he was able to solve the problem by rebooting and selecting the xxxxxx.i586 kernel from the list. He also told me that he saw three kernels from the list.
For what I see here, this driver will only load with the i586 based kernel, and I also am seeing that each time that he updates his system he may have to go thru this again. My question is this: Will fedora 11 change his default kernel each time that he runs Fedora Updates? If so, what can I do to prevent that change from occurring.
Also, is there a limit on the kernels that appears on the GRUB list, if each updates brings a new kernel entry on the GRUB list, will the list get very large one day? or will Fedora remove one or more kernels, in other words, what is the maximum number of Kernels Fedora keeps on the GRUB list? and will there be a point that Fedora updates will delete that working i586 kernel leaving him with a non booting system? Or will that nvidia driver "magically" start working with some future update after the developers fix/improves what ever is keeping that nVidia driver from loading with the latest updates?
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
View 10 Replies View RelatedNot wanting to speculate why, in the repositories, Fedora doesn't *also* provide a on-KVM enabled kernel counterpart to the default KVM enabled kernel that *is* supplied, I must say I'm frustrated that they haven't done this simple thing.
Considering that everyone who upgrades to KVM enabled FC12 from a previous non-KVM release of Fedora (like FC10) ... considering that these people will be guaranteed to no
longer be able to run VirtualBox or VMWare Workstation after upgrading, is a disappointing oversight by / or intent of Fedora (one that manifests in *lost productivity*).
And try though you may to install the kernel source RPM and compile it after running "make xconfig" to disable KVM support, you usually can't! Fedora kernel compile attempts often die very early in the "make" process, indicating something like ...
"Kernel compile error: No rule to make target `missing-syscalls'
or some other silliness. And when you successfully compile a "kernel.org" kernel, and try to boot it, you get all kinds of missing library errors (etc).
Given that it would be simple to provide both a KVM enabled kernel (as they do), and also a non-KVM enabled kernel (which they don't) so the rest of us can seamlessly continue to run VirtualBox and/or VMWare Workstation after an upgrade - and avoid getting entangled with deciding whether use KVM or XEN for guest O/S's... it's a frustrating misstep to not have done this basic thing (i.e. include a non-KVM kernel). It was a rude awakening when we tried to launch VirtualBox only to have it fail after the upgrade.
Anyway, has anyone successfully compiled their own kernel for FC12 and not get errors after boot? If so, which sources did you use; and what kernel version? In the meantime I'll try out other kernels and compile options.
Having just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 2.6.32.19-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
View 10 Replies View RelatedAfter updating to 2.6.32.14-127.fc12 kernel my computer is slow.
View 4 Replies View Relatedwhen i try to install any program i always have this type of erreur messagehow to solve that ?
chec du tchargement :
Failed to download ./i586/libcodeblocks0-r6185-1.1.i586.rpm from Index of /repositories/devel:/tools:/ide/openSUSE_11.2
[code]....
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
I can't seem to find the kernel source for 2.6.31.12-174.2.22.fc12.i686. This should be a simple task, what am I missing?
View 5 Replies View RelatedForgive me if I have posted this in the wrong forum, first time poster with Fedora. I have been using Linux for some time now, mostly Mint, but Fedora 12 @ work. Anyway, I receive the following error in my /var/log/boot.log:
Code:
nvidia.ko for kernel 2.6.32.9-70.fc12.i686 was not found
and the driver does not load (My xorg.conf file is not loaded), but once I am at a
[code]...
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
I'd like to have a shot at building FBReader 12.1 from source for use within F12 (kernel 2.6.31.9-174.fc12.i686.PAE) but am having problems locating the following .rpm files:
libz and libbz2 -- libraries for zip and bzip2 (de)compression
libfribidi -- for bidirectional text support
lincurl, version >= 7.17 -- for network libraries integration
I had fedora 12 installed on a Macbook pro Intel first generation with ATI Radeon graphics card (see the attachment). Compiz crash when trying to watch *.wmv movie codified with wmvvc1dmo on kernel-PAE-2.6.32.9-67.fc12.i686. I want to convert the film to *.mpg, then I download the mplayer codecs in order to see the film, I can do it without problems with the on kernel-PAE-2.6.31.12-174.2.22.fc12.i686. But I updated my system last Saturday and when I was trying to see the movie again the computer began to respond really slow, then I began to close applications and when I tried to restart I got the message: "compiz is not responding".
I tried again but the same problem. Other thing that I noticed is that when the computer go to sleep, when I wake up it, the display show horizontal black spikes, it is like it doesn't have the appropriate refreshing rate. I think that the problem is related with the acceleration on graphic card. Yesterday, I booted on kernel-PAE-2.6.31.12-174.2.22.fc12.i686, and I watched the film, and the wake up was without problems. That is the reason I call it a regression.
[Code]...
kernel-2.6.32.10-90.fc12 seems to break 802.11n with my intel 4965 chip on my thinkpad t61p. Anyone else seeing the same thing? iwconfig shows extremely low bit rate. dmesg doesn't show anything at all unusual.
View 10 Replies View RelatedI downloaded a live KDE-CD and will install from that on hard disk. My box has 4 GB RAM so I understand I need a *-pae kernel ("Physical Address Extension") to be able to use the memory fully.
Can I install the kernel e.g. from [URL] via YAST, or does it need other libraries / software as well and so the system becomes unstable, would anybody know?
I just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).
Installation went fine, but upon the initial boot, I get:
Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)
I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from
I have a tricky problem which I could soIve with a c program. I wrote one and found I didnt have gcc so I tried to install it. I was told I needed to install packages. I acknowledged and an error was generated gcc-4.4.2-7.fc12.i686 requires libgomp = 4.4.2-7.fc12 I try to install libgomp and go round again.
View 2 Replies View RelatedI did a clean install of fedora 13 on my sys, however when i run
Code:
rpm -qa |grep fc12
lots of and lots of fc12 packages pop up. below is the list. if there is fc13 version of these packages, and if there is (which I suspect for at least some of them there should be) why my sys doesn't update to those packages?
here is the list of fc12 packages:
Code:
~$ rpm -qa |grep fc12
ctan-cm-lgc-fonts-common-0.5-17.fc12.noarch
plexus-compiler-1.5.2-4.3.fc12.noarch
texlive-texmf-errata-fonts-2007-7.fc12.noarch
[code]....
I'd like to reproduce the way I got to f12 from f11, but obviously to f13 basically I started out on the f11 rawhide repos, then as f12 got released a yum update updated my fedora-release and then hey presto I was automatically upgraded to f12 final release if I now turn on my rawhide repos, as f13 is nearing completion, will I be updated to the latest f13 release (RC3 I believe) and then as f13 gets released my fedora-release will be updated and i will then be upgraded to f13 final as happened before?I don't want to download a whole dvd iso and then upgrade when f13 is final, I'd like to do a gradual transition ie..
f12 -> f13 RC3 via rawhide
f13 RC3 -> f13 Final via yum update
i am not sure where to post this issue since i am using RC4 of FC12 so posting it here.I am using the Live-CD to install FC12-RC4, it is gnome x86_64. The issue is as follows:I never had this with OpenSuSE. Mandriva & Ubuntu all of which is the latest release. Why the installer has to initialize the hard disk?
View 9 Replies View RelatedI decided to upgrade finally. It didn't go smoothly and right now I'm not really sure what is going on. During the install when it was scanning my disks it threw a timeout error but continued anyway. I completed the install but one thing that seemed odd to me is that I wasn't asked about packages or anything and it never prompted me for any other CDs. I wasn't sure what was going on. I did a re-install but same results.
So I figured fine I'll just configure things myself. I went to mount my other partitions and was unable to. I'm not sure what was done but I've not been able to get to my old data. I'm not even sure where to start because things are so different. I ran fdisk -l and I see these devices:
/dev/sda
/dev/sdb
/dev/dm-0
/dev/dm-1
Under /dev/sda It shows /dev/sda1 but tells me that partition 1 does not end on cylinder boundary it then shows /dev/sda2. This has a System of Linux LVM. Same with my /dev/sdb1. I am guessing this is where my 2 old partitions went. I looked up LVM which I didn't know anything about before. Previously I was about to mount my partitions directly so I'm pretty sure they were not LVM. So somehow these got converted?
I don't know what /dev/dm-0 and /dev/dm-1 are but I do get errors on them:
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
Right now I'm trying to simply get to my data once again or determine if it's unrecoverable. At this point I'm at a loss as to how to proceed. I know I didn't tell the install to format anything other than the first partition. Oh and after the two Fedora installs I did take a peek at Unbuntu. I started that install and it told me that the partition I was installing on was too small. So I canceled it. It showed the other partitions but I could see no way to read them.
When I install Fedora core 12 from DVD (I downloaded iso file from Internet and burned it to DVD). After the first screen display, I choice the first command (and the other time, I choice the second), and then, the installation began. But, about 1 minute after, the installation paused (may be stopped) and never continue. I don't know why. I installed Windows 7 before and I want to install Fedora 12 as a second OS. My laptop is HP Pavilion dv4.
View 1 Replies View RelatedWhat to do? After preupgrade and update fc11->fc12, system has a mixture (oh yeah) of fc11 packages and fc12 new ones. Dependencies problems, and even by removing, reinstalling packages sometimes it's picking up fc11 ones.I tried yum clean etc to no avail. Is there any script or anything to solve this automatically? I suppose the solution is to manually erase all the fc11 packages (assuming they are really installed and not simply reported as such)?
View 14 Replies View RelatedTook an FC12 system to FC13 via 'preupgrade'There was a REALLY old version of gimp-print-cups in RPM, and the installer announced "a fatal error occurred". However, everything else seemed to download properly and I allowed the upgrader to reboot the system.
a) grub boots the kernel, then the kernel can't find root and panics. It does this because it can't root file system with root=UUID= kernel option. If I manually tweek the grub line to use root=/dev/sdx, kernel finds its root and boots up to the next problem.
b) GUI environment not launched. Init scripts die on "error loading modules.dep". Sure enough - one is not there. Ran "depmod" to generate it ,and rebooted. System reboots into GUI, where I login to find the next problem.
c) Evolution won't start. Reason turns out the evolution-data-server from FC12 is still present. Did a check on just how many other FC12 RPM's are present: 1100. Yeah - over 1000. About 850 of the FC12 RPM's also had FC13 replacements installed. Did an "rpm -e" on these. Also had to do some remove action on mkinitrd, nash, plymouth-scripts-0.8.0, and parted-1.9.0 as there are replacements for these utilities under different package names. That cleaned up the system some, to present me with the next problem.
d) yum package repository still linked into FC12. Removed fedora-release-12-2.noarch and then I could "yum install" evolution and a few other packages properly.
I've done one other FC12->FC13 upgrade today, and that went flawlessly. So, I think in general the upgrade works fine. It just looks like if preupgrade finds anything amiss, it doesn't take care of a lot of things and generally leaves you with an unbootable mess to clean up.
I had a fairly smooth upgrade process using PreUpgrade on my main workstation, but I still have a huge bunch of fc12, some of which have fc13 analogs installed, some of which don't (a total of 317 packages). Also, I still have the Constantine gdm theme, probably as a symptom of these lingering packages. Can I just yum erase these? Do I need to check which have analogs in fc13? I don't know which step of the upgrade I forgot, but it seems I'm stuck somewhere in between, although
Code:
joel@localhost: ~> cat /etc/fedora-release
Fedora release 13 (Goddard)