howto remove core
by Nader Mirzaee
Hi all,
i have installed FC5 , after yum update i reboot my machine and there is this
triple boot message :
Fedora 2.6.16-1.2096-FC5
Fedora 2.6.15-1.2054-FC5
Windows XP
it seems that i have 2 cores in my machine , how can i remove the old one ? and i don't want to see it in the boot message as well !
thanks
---------------------------------
Blab-away for as little as 1¢/min. Make PC-to-Phone Calls using Yahoo! Messenger with Voice.
18 years
media does not match checkum
by Jerry
Hi i tryed to update my FC5 a little bit ago it hit every ural with out being able to update,is this on my end if so should i rechech my iso and do a new dvd.iso burn and reinstall this is a on going problem on my end.
Thanks for any help.
__________________________________________________________________
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp
18 years
RE: Testing iso downloads?
by LinuxMedia
> Greetings all,
> I have downloaded the FC5 isos and, after
> burning the first one, I found that the media
> check failed when I booted.
[...]
I had the same problem on my FC3 disks. But during a long google session
that lead down a dirt road and an abondoned farm, I found this...
When booting the CD, at the the prompt, type "linux mediacheck
ide=nodma". This has always results in a succesful check for me. But
remember, I've only used it on FC3 disks.
Rocco
18 years
Re: How to use dvgrab.
by Mike Chalmers
On 4/28/06, Tony Nelson <tonynelson(a)georgeanelson.com> wrote:
> At 10:17 PM -0400 4/28/06, Mike Chalmers wrote:
> ...
> >I will try disabling SE Linux and let you know what happened. How do I
> >disable SE Linux?
>
> As root:
>
> [...]# setenforce 0
>
> To re-enable:
>
> [...]# setenforce 1
>
>
> >"There is an easy way to find out if SELinux is the culprit."
> >What exactly am I doing when I run the commands you listed. Am I
> >disabling SE Linux?
>
> No, it's just installing a (unneccesary) package that separates the AVC
> (SELinux complaint) messages into their own log. To see what's up without
> having it installed, just use, as root:
>
> [...]# tail -f /var/log/messages
>
> which shows the last few lines of the messages log, and then new lines as
> they are added (man tail). So, issue that command, do your thing in
> another terminal or whatever, and see what it says. Exit it with Control-C.
> ____________________________________________________________________
> TonyN.:' <mailto:tonynelson@georgeanelson.com>
> ' <http://www.georgeanelson.com/>
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
Hi,
When I enter the command you gave me into the terminal it tells me
that there is no such command:
------------------------------------------------------------------------------------
# setenforce 0
bash: setenforce: command not found
-------------------------------------------------------------------------------------
Instead I ran the command "system-config-securitylevel" and disabled
SE Linux and rebooted. I then tried Kino and dvgrab and the same thing
happened. Kino shut down when I minimized it then maximized it. It
shut down when I tried to open a avi file captured with dvgrab.
This is what happened when I ran the "tail -f /var/log/messages"
command and then tried the things that were causing Kino to shut down.
This is what it said:
---------------------------------------------------------------------------------------------------------------------
Apr 29 23:39:12 dhcppc0 kernel: [drm] Initialized drm 1.0.1 20051102
Apr 29 23:41:58 dhcppc0 kernel: cdrom: hda: mrw address space DMA selected
Apr 29 23:41:58 dhcppc0 kernel: SELinux: initialized (dev hda, type
iso9660), uses genfs_contexts
Apr 29 23:42:00 dhcppc0 kernel: SELinux: initialized (dev hdb, type
iso9660), uses genfs_contexts
Apr 29 23:42:01 dhcppc0 kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09)
Mounting volume 'REV 35', timestamp 2004/03/25 14:55 (1f10)
Apr 29 23:42:01 dhcppc0 kernel: SELinux: initialized (dev sr0, type
udf), uses genfs_contexts
Apr 29 23:42:01 dhcppc0 gconfd (user1-2968): starting (version
2.13.5), pid 2968 user 'user1'
Apr 29 23:42:01 dhcppc0 gconfd (user1-2968): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
Apr 29 23:42:01 dhcppc0 gconfd (user1-2968): Resolved address
"xml:readwrite:/home/user1/.gconf" to a writable configuration source
at position 1
Apr 29 23:42:01 dhcppc0 gconfd (user1-2968): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
Apr 29 23:53:21 dhcppc0 kernel: audit(1146369201.431:78): avc:
granted { execstack } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:21 dhcppc0 kernel: audit(1146369201.431:79): avc:
granted { execmem } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.347:80): avc:
granted { execstack } for pid=3143 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.347:81): avc:
granted { execmem } for pid=3143 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.531:82): avc:
granted { execstack } for pid=3160 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.531:83): avc:
granted { execmem } for pid=3160 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.595:84): avc:
granted { execstack } for pid=3178 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.595:85): avc:
granted { execmem } for pid=3178 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.639:86): avc:
granted { execstack } for pid=3185 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.639:87): avc:
granted { execmem } for pid=3185 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.691:88): avc:
granted { execstack } for pid=3197 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.691:89): avc:
granted { execmem } for pid=3197 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.743:90): avc:
granted { execstack } for pid=3209 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.743:91): avc:
granted { execmem } for pid=3209 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:22 dhcppc0 kernel: audit(1146369202.991:92): avc:
granted { execmem } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:32 dhcppc0 kernel: audit(1146369212.040:93): avc:
granted { execmem } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:32 dhcppc0 kernel: audit(1146369212.040:94): avc:
granted { execmem } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:32 dhcppc0 kernel: audit(1146369212.040:95): avc:
granted { execmem } for pid=3135 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:53:32 dhcppc0 kernel: audit(1146369212.044:96): avc:
granted { execmem } for pid=3219 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:07 dhcppc0 kernel: audit(1146369247.962:97): avc:
granted { execstack } for pid=3227 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:07 dhcppc0 kernel: audit(1146369247.962:98): avc:
granted { execmem } for pid=3227 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.358:99): avc:
granted { execstack } for pid=3235 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.358:100): avc:
granted { execmem } for pid=3235 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.426:101): avc:
granted { execstack } for pid=3252 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.426:102): avc:
granted { execmem } for pid=3252 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.494:103): avc:
granted { execstack } for pid=3270 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.494:104): avc:
granted { execmem } for pid=3270 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.538:105): avc:
granted { execstack } for pid=3277 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.538:106): avc:
granted { execmem } for pid=3277 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.590:107): avc:
granted { execstack } for pid=3289 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.590:108): avc:
granted { execmem } for pid=3289 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.642:109): avc:
granted { execstack } for pid=3301 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.642:110): avc:
granted { execmem } for pid=3301 comm="ffmpeg"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Apr 29 23:54:08 dhcppc0 kernel: audit(1146369248.814:111): avc:
granted { execmem } for pid=3227 comm="kino"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
--------------------------------------------------------------------------------------------------------------------------------
From,
Mike
18 years
NetworkManager update
by Matthew Saltzman
I don't know if starting a new thread is the best idea, but the other
topic's tree is really dense now, and I didn't want this to get buried.
Here are a couple of things to try:
(1) It occurred to me that most of the people having trouble are probably
using the NM that shipped with FC5. There is a NetworkManager update in
updates-testing that you should really try.
yum --enablerepo=updates-testing NetworkManager
The update has been in testing for nearly a month. I don't know why some
of these updates are taking so long to be rolled out.
(2) You also want the initscripts from updates-testing (also long overdue
to be pushed out, IMO). If your machine has multiple NICs, then the
current initscripts can swap them on boot and cause lots of flakiness.
Once initscripts is updated, clear the DHCP leases from /var/<something
dhcp related> before trying again. If it were me, I'd delete all devices
in system-config-network, reboot, and reconfigure the interfaces as needed
as well.
(3) Some of the reliability issues are due to interactions between NM and
flakey drivers, and are not NM's fault. (Usability is a different
matter.) It might be worth trying the Netdev kernels at
http://people.redhat.com/linville/kernels/fedora-netdev/. They contain
many driver updates.
(4) There are a number of useful hints for NM and ipw2200 at
http://www.ces.clemson.edu/linux. Users of other drivers may find some
useful information there as well.
(4) For real help with NM, send your issues to the developers' list,
networkmanager-list(a)gnome.org (subscribe at http://mail.gnome.org). For
real bugs, file them in Fedora's Bugzilla. The goal of NM is to make
managing connections to multiple networks painless. If it isn't quite
there yet, the developers can use all the help you can provide.
HTH.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
18 years
RE: Laptop Display Problems
by Annette T Robart
Message: 7
Date: Sat, 29 Apr 2006 16:47:27 -0400 (EDT)
From: Matthew Saltzman <mjs(a)ces.clemson.edu>
Subject: Re: Laptop Display problems
To: For users of Fedora Core releases <fedora-list(a)redhat.com>
Message-ID: <Pine.SOC.4.61.0604291646200.2249(a)access.ces.clemson.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sat, 29 Apr 2006, Michael A. Peters wrote:
> On Sat, 2006-04-29 at 08:37 -0400, Terry Snyder wrote:
>> On 4/29/06, Annette T Robart <ARobart(a)hughes.net> wrote:
>> Hi there, please excuse me; I am totally new to this
>> product. I have installed FC1 to my desktop with absolutely
>> no problems. It came with my textbook for my Unix class. Now
>> I am trying to install it on an extra laptop that I don't use.
>> It was a new hard drive so it is the only thing on it. It is
>> an IBM A21P 850Mhz, with 512 ram and a 15 inch monitor. It
>> installs fine, but it stops at the monitor and I'm not sure
>> what to pick?? I don't see anything in the documentation and
>> nothing in the BIOS. I guessed a couple times and when it
>> boots up the X window fails. I get "bad mode clock/interface",
>> hsync out of range, fatal error, no screens found.
>>
>> Does anyone know what I should pick for a monitor and what
>> range I should pick?
>>
>> Thanks so much!
>>
>> Annette
>
> Hi and welcome to Fedora.
>
> Om my IBM Thinkpad T20 - I use Generic LCD at 1024x768 as the monitor -
> and it works.
I believe the 1024x768 Thinkpad display is an "IBM 9514-B TFT Panel".
That's what I use on m T41.
>
> That being said - Fedora Core 1 is really old and no longer supported.
> I suggest you get a copy of Fedora Core 4 or Fedora Core 5 and try that.
>
> Note that installing FC5 on my Thinkpad T20 was a little tricky, FC4
> installs just dandy - both are currently supported with official
> updates. FC5 might install as intended for you though, I don't know.
>
> I do not recommend using FC1 at this point in time.
Seconded.
Well I've tried everything else, I guess you are right. I'll have to go with
Core 4. I just need to find it on a Cd-rom. I found it on the Internet as a
download but it was so many individual files, it was confusing and they were
still too large. I wasn't even sure what I was supposed to download, but it
didn't matter because they were taking forever to download even with my
satellite and I had to quit.
18 years
OT: FC4+Poweredge 850+Perc 4/sc = slow disk performance
by Mike McMullen
Hi All,
I am setting up a Dell PowerEdge 850 with FC4 (customer's app requires it).
It has 2GB of RAM, 3.2GHZ Pentium 4 and a PERC 4/SC (aka megaraid)
raid controller with two seagate SCSI-3 300GB 10,000RPM drives.
I have configured the logical drive as RAID 1 (mirroring) with the defaults for
for a logical drive 0 - StripeSize 64K, Write Policy = Write Through, Read
Policy = Adaptive, Cache Policy = DirectIO.
I have a 250GB partition (per customer's request). When I run
hdparm -t -T on the device I get ~2408MB/sec on cached reads.
On buffered disk reads I get ~35MB/sec which seems awfully slow
given the h/w. I'm running the system in single user mode to eliminate
background processes.
My buffered reads will start at 50MB/sec and after ~8-10 iterations drops
to ~35 MB/sec.
For a test I installed FC5 and there buffered reads were around ~75MB to
start with and after ~8-10 iterations dropped to ~39MB/sec.
Can anyone shed any light on why the i/o appears so slow? On 7500 RPM
SATA with drives I get buffered reads of around ~60-70MB.
I've tried changing parameters in the PERC controller screen but nothing seems
to work.
Any insight appreciated!
Mike
18 years
wifi pcmcia card only works if inserted after booting FC5
by Lonni J Friedman
After fighting with this since upgrading from FC4 to FC5 two weeks
ago, I've finally isolated the problem down a big. Basically the
problem I'm having is that my Linksys WPC11v3 (802.11b) pcmcia wifi
card will only 'see' the network if I physically insert it after FC5
has finished booting fully. If the card is inserted during bootup,
then I _never_ can get it to see anything.
The only thing that I get for an error is:
ADDRCONF(NETDEV_UP): eth1: link is not ready
This card uses the orinoco_cs driver, however for some bizarre reason
the hostap_cs driver is also getting loaded, even though its never
used.
At any rate, this is extremely frustrating, because I have to remember
(and worse tell everyone else who uses this notebook) to physically
remove the card before booting up, or they get no network connection.
This problem did not exist prior to the FC5 upgrade. Help?!?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama(a)gmail.com
LlamaLand http://netllama.linux-sxs.org
18 years
Fedora Core 5 x11vnc
by Chris Bradford
Hi guys,
I can't get x11vnc to compile on my system, and I need to be able to
connect when the login manager (gdm) is loaded for remote admin. I used
to call x11vnc in /etc/X11/gdm/Init/:0 on FC4 and it worked a charm.
Is there a way to get it working in FC5?
Cheers,
Chris Bradford
Systems Administrator
Cambridge Newspapers
This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com
18 years
