Fedora core 4 and linux nofb
by Tomás Fariña
Hello world, when install Fedora core 4 in acer ferrari 3200, it's
impossible but i try with "linux nofb" i can install fedora what happen ?
Thank you.
18 years, 11 months
Kernel Panic after FC4 upgrade
by Michael DeCleene
Hi, folks,
I recently updated from FC3 to FC4 via CD install. Install went fairly
smoothly, but I now can't get the system to boot--I get a kernel panic.
Relevant section of boot log follows (apologies for any typos--I can't
cut-and-paste this without a working system...)
CODE
Mounting root filesystem
mount: error 6 mounting ext3
Switching to new root
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
unmounting old /proc
unmounting old /sys
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!
Having done some poking here and on google, I'm expecting this is a grub
issue with finding my proper root filesystem, since it seems to have issues
when it tries to mount the root device. Which should be trivial to fix, so
I'm sure I'm missing something obvious here. But I've been at this for
several hours, and can't for the life of me find the issue...
Some configuration info: I'm attempting to boot from a SCSI raid array. That
array has /boot on /dev/sda1, the correct root filesystem on /dev/sda2, and
/swap on /dev/sda3. I'm using the smp kernel because I do have an SMP
system. I know the array is OK because I can properly mount it when booting
into rescue mode.
I've looked at grub.conf and didn't see any obvious issues, though I've
tried a few suggestions I've found online. I've tried reinstalling grub on
/dev/sda. I've run grub and verified that it has setup hd0. I've checked the
device map, which looks OK. I do note fedora is using hd0 in grub, not sd0,
to represent my array, but since the device map correctly points to the
right place, I don't think that would be an issue (especially given that the
system can in fact find the kernel). Basically, I'm stuck here, and looking
for some thoughts/suggestions:
Some possibly useful files follow:
/etc/grub.conf looks like:
CODE
# grub.conf generated by anaconda
#
#Note that you do not have to rerun grub after making changes to this file
#NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd-version.img
#boot=/dev/sda
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.6.11-1.1369_FC4smp)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4smp ro root=/dev/sda2
initrd /initrd-2.6.11-1.1369_FC4smp.img
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/sda2
initrd /initrd-2.6.11-1.1369_FC4.img
/boot/grub/device-map looks like:
CODE
#this device map was generated by anaconda
(fd0) /dev/fd0
(hd0) /dev/sda
/etc/fstab looks like:
CODE
/dev/sda2 / ext3 defaults 1 1
/dev/sda1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defauls 0 0
/dev/sda3 /swap swap defauls 0 0
<more in this file about my IDE hard drives and floppy>
Any suggestions greatly appreciated!!!!
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
18 years, 11 months
Login failure on FC4
by don fisher
I have installed FC4 on my Dell P4 laptop. All went smoothly until I
tried to load a kernel I compiled myself. I have a 2.6.11 kernel that
functioned correctly under FC3 after I applied the udev patch to allow
my console to exist.
I also have a 2.6.12.2 kernel. Both have initrd files. When I attempt
to log in from the console I am allowed to enter my user name and
password. As soon as I enter return for the password I am returned to
the login prompt. This also occurs when root attempts to log in. If I
boot the kernel that came with the FC4 distribution the login is
successful.
The entries from 2.6.12.2 that contain my name from /var/log/messages are:
1. su(pam_unix)[6674]: session opened for user dfisher by dfisher(uid=0)
2. kernel: [ 1094.829499] mtrr: type mismatch for c0000000,8000000
old: uncachable new: write-combining
3. su(pam_unix)[8072]: session opened for user root by dfisher(uid=239)
Under RedHats FC4 kernel:
1. gconfd (dfisher-6896): starting (version 2.8.1), pid 6896 user
'dfisher'
2. gconfd (dfisher-6896): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
3. gconfd (dfisher-6896): Resolved address
"xml:readwrite:/home/dfisher/.gconf" to a writable configuration
source at position 1
4. gconfd (dfisher-6896): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
I do not understand why gconfd is operating under the FC4 kernel and
not my own. But I obviously do not know the details.
Any help would be appreciated. Life was so simple in the insecure days
before pam, ssh,... made system management a security task.
don
18 years, 11 months
FC4:Printing Problems: evince or CUPS?
by Roy Erickson
Hi all:
I did a clean build to 'FC4 release' and have done a yum update (yesterday).
I went to CUPS (http://localhost:631) and added my network connected
printer, an HP 4050N with a ethernet port on it, using a
'socket://192.168.3.63' connection type, I think like I did on my FC2
build a year ago.
All seemed well. The test page came out nicely;)
I then went to print a PDF attachment from my Thunderbird mail agent,
using their 'evince' viewer. In the viewer the document looked great,
but the printout came out lacking all but a basic typewriter font. The
math symbols were replaced with # signs and ! signs.
On FC2 I used xpdf, plus I thought I added my printer via an exact model
name (HP4050), as opposed to just an "HP laser writer" that CUPS wanted.
I tried the Desktop->System Setings->Printing GUI but could not see how
to add a networked non-server based printer.
Any Ideas?
Thanks,
Roy
18 years, 11 months
Change Disk from IDE to SCSI using dd, what else ?
by Eduardo J. Vega A
Hello guys... I got already FC3 installed at /dev/hda but I need to move it
to /dev/scd
I know that I can move them by using dd, but, what else do I may need to
change ?
1) Grub ? Which config files ? Should I do any other stuff rather than
modify the new path at the Config files ?
2) FSTAB ?
3) Others ?
Thanks
--ed
--ed
He who fights with monsters might take care lest he thereby become a
monster. And if you gaze for long into an abyss, the abyss gazes also into
you .Friedrich Nietzsche, Beyond Good and Evil, Aphorism 146
18 years, 11 months
How to tell if an executable is 32-bit or 64-bit on x86-64?
by Jonathan Ryshpan
I have an x86-64 system and sometimes need to find out if a library or
executable is built for 32-bit or 64-bit execution. On FC3,
file foo.so
would produce a message that would do the job, like this:
$ file usr/lib*/libssl3.so
/usr/lib/libssl3.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped
/usr/lib64/libssl3.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), stripped
A similar command on FC4 produces something like this:
$ file /usr/lib*/libssl3.so
/usr/lib/libssl3.so: data, stripped
/usr/lib64/libssl3.so: data, stripped
which is not very useful.
What's the best thing to do: Copy FC3 /etc/magic into FC4? Install the
latest file utility from the GNU fileutils?
I have submitted this as a bug to Red Hat Bugzilla.
jon
18 years, 11 months
FC4 Boot Log
by Rob Kettle
Hi,
anyone know how to get the Boot Log working in FC4 ? Seems it's
intentionally disabled but with no alternative.
Thanks
Rob
**************************************************************************************************
CONFIDENTIAL AND PRIVILEGED INFORMATION
IMPORTANT: This message is intended for the addressee only and is privileged
and confidential. If you are not the addressee, then please DO NOT read, copy
or distribute it, but reply to the sender that you received it in error and
delete it.
Thank you.
Fisher Scientific U.K., Limited.
Registered Office:
Bishop Meadow Road,
Loughborough LE11 5RG
England
Registered in England No: 2883961
18 years, 11 months
Issues with ALSA, FC3, SPDIF output, and VIA 8237 motherboard
by Philip A. Prindeville
I have an MSI K8MM-V motherboard (based on the VIA 8237
and VIA 1617 chips), with an Athalon 64 2800+ processor
(socket 754) and I'm running FC3 on it (all the updates).
I cannot for the life of me figure out how to get the
optional RCA SPDIF output to work.
I know that there's been some churn on the VIA 82xx
drivers lately (I'm not sure the 8237 is still included
in the via82xx drivers in ALSA 1.0.6)... and I'm wondering
if I need to build 1.0.9 from the SRPMS, or if anyone has
already managed to get this working.
Oh, for the days on my ProAudio 16... ;-)
Any suggestions, configs, etc. appreciated.
-Philip
18 years, 11 months
what happenned to system-logviewer
by Claude Jones
In my fresh FC4 install, this is no longer there. I tried copying the
executable from an FC3 box but it just fails with an error. On the boxes I've
upgraded from FC3>FC4 system-logviewer is still there, and works fine. Have I
missed something? Is there a better or newer way to view logs?
--
Claude Jones
Bluemont, VA, USA
18 years, 11 months