f10 alpha: disk killer! :-).
by Tom Horsley
So, my system sata disk just died. I hope it is merely
a conincidence that I recently installed f10 alpha on one
of the partitions :-). Now I have to use my Windows box
till I get a new disk genned (what an incentive to get
the disk replaced!). Fortunately I have a USB drive chock
full of backups.
15 years, 8 months
system-config-authentication gives plymouth error (rawhide)
by Jerry Amundson
Upon click of "OK" to exit s-c-a :
[root@jerry-opti755 ~]# system-config-authentication
Xlib: extension "RANDR" missing on display "localhost:10.0".
Starting NIS service: [ OK ]
Boot splash control client....... [FAILED]
USAGE: plymouth [--help] [--debug] [--newroot=<string>] [--quit]
[--ping] [--sysinit] [--show-splash] [--hide-splash]
[--ask-for-password] [--update=<string>] [--wait] [subcommand
[options]...]
--help This help message
--debug Enable verbose debug logging
--newroot=<string> Tell boot daemon that new
root filesystem is mounted
--quit Tell boot daemon to quit
--ping Check of boot daemon is running
--sysinit Tell boot daemon root
filesystem is mounted read-write
--show-splash Show splash screen
--hide-splash Hide splash screen
--ask-for-password Ask user for password
--update=<string> Tell boot daemon an update
about boot progress
--wait Wait for boot daemon to quit
Available subcommands:
ask-for-password Ask user for passowrd
--command=<string> Command to send password to via standard input
--
Some people say I have A.D.D. but they just don't understand. Oh look!
A chicken!
15 years, 8 months
Kernel 2.6.26.2-3.fc8: new PCI message, is this normal??
by Gilbert Sebenste
Just installed 2.6.26.2-3.fc8 from Koji.
I get a warning message upon boot up, just after the kernel prompt which
lets me choose which one I want to use. It simply says:
PCI: NOT USING MMCONFIG
Is this normal? Never saw that message before.
Otherwise, everything else seems fine.
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste(a)weather.admin.niu.edu ***
web: http://weather.admin.niu.edu **
*******************************************************************************
15 years, 8 months
Very slow password validation
by Clyde E. Kunkel
After rawhide update of 20080726, validation of root password is taking
(subjectively) a very long time, about 20-25 seconds.
Anyone else seeing this?
--
---------------------------------
Regards,
Old Fart
15 years, 8 months
Re: yum -y update kdepim gave Transaction Check Error
by yunus
Hi Kevin
> yunusf9 tester <yunus.tji.nyan <at> gmail.com> writes:
> > Have anybody found the same problem as mine?
>
> You have to update everything, not just some packages.
On my system, issueing
#yum update
make me have to download updates with total size : 513 M.
Currently I use my HP Nokia 6120 as a modem. I will try this latter when
I get USB Modem Huawei E220 next month (I hope this modem will just work
fine with F9)
>
> > file /usr/share/icons/crystalsvg/16x16/actions/kalarm.png from install
> > of kdepim-3.5.9-10.fc9.x86_64 conflicts with file from package
> > crystalsvg-icon-theme-4.0.3-3.fc9.x86_64
> etc.
>
> -> You have to update at least kdelibs3 for that. There's a kdelibs3 build
> which obsoletes the crystalsvg-icon-theme which was built from kdeartwork 4
> (because the crystalsvg in current versions of kdeartwork is no longer
> compatible with KDE 3). As the crystalsvg in kdelibs3 doesn't include those
> kdepim icons, we readded them to kdepim. So the packages have to be upgraded
> together.
yes, it works.
after running:
#yum update kdelibs
I could run below command succesfully:
#yum groupupdate 'KDE'
> > file /usr/share/icons/hicolor/16x16/apps/kipi.png from install of
> > kdegraphics-4.1.0-3.fc9.x86_64 conflicts with file from package
> > libkipi-0.1.5-4.fc9.x86_64
> etc.
>
> -> You have to update at least libkipi for that one, for similar reasons.
> (kdegraphics now includes a KDE 4 version of libkipi, and the conflicting icons
> were removed from the KDE 3 libkipi.) Please do a complete yum update from the
> stable updates before trying KDE 4.1 from testing.
>
> Kevin Kofler
Thanks Kevin for letting me know.
yunus
15 years, 8 months
usb keyboard disabled?
by Tom Horsley
I just typed "reboot" in fedora 10 alpha after updating the
kernel, and something apparently disabled my USB keyboard
input so hard that it wouldn't function when I got back
to the grub screen. It did work once the default fedora 8
kernel booted, so I'm able to type this mail now :-).
Has anyone else seen anything like this? I don't really think
I ought to do a bugzilla till I see it at least one more time,
but I'm curious if it has happened to others.
15 years, 8 months
Odd behavior for yum update with f10a x86_64
by shmuel siegel
I upgrade my FC9 to f10a x86_64 on an AMD 3800+ based machine. I was up
to date on rawhide as of Sunday.
This morning I tried doing yum update kernel*. Test transaction consumed
all memory and then failed. This happened twice. Thinking that maybe my
problem came from the flash.i386 plugin (don't ask why I thought that) I
ran yum remove glibc.i386. The yum update kernel* succeeded. The only
other 32bit module that I knowingly had on my machine was wine. I hope
that this gives someone some ideas. I don't think that I can easily
reproduce the faulty environment.
15 years, 8 months