F9: [unsupported] rt2870 now works, but requires restarting named & httpd after (re)boot?
by Dan Thurman
First, I know F9 is no longer supported, but wanted to
ask if there is a workaround to this problem.
I finally got rt2870 to work on F9, however, I noticed
during a reboot, httpd complained that it could not find
the host's domain, so it chose 127.0.0.1, and secondly
named responded only to localhost queries. I discovered
that restarting named and httpd, in that order, after a
reboot, restored normalcy. The key issue seems to be
that named is not properly started before services? Or
perhaps amanda and/or dnsmasq is interfering with
named?
Is there a fix or a workaround for this issue?
Thanks-
13 years, 11 months
[F13] AVerMedia Volar Black HD/A850
by Joachim Backes
Hi,
I'm planning to purchase an USB TV stick (for DVB-T). I saw that the
AVermedia AVerTV Black HD/-A850 USB is running properly under Ubuntu.
Can somebody confirm that is runs properly under F13 too?
Kind regards and thanx in advance
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
http://www.rhrk.uni-kl.de/~backes
13 years, 11 months
vim-latex trouble
by Ankur Sinha
hi,
I recently came across what looks like an awesome tool : vim-latex.
I've installed the fedora packages using yum.
[Ankur@localhost ~]$ rpm -qa | grep vim
vim-latex-doc-1.8.23-1.20100129.r1104.fc13.noarch
vim-latex-1.8.23-1.20100129.r1104.fc13.noarch
vim-minimal-7.2.411-1.fc13.x86_64
vim-common-7.2.411-1.fc13.x86_64
vim-vimoutliner-0.3.4-12.fc12.noarch
vim-enhanced-7.2.411-1.fc13.x86_64
vim-X11-7.2.411-1.fc13.x86_64
I'm trying to follow the official tutorial[1]. It doesn't seem to work.
The tutorial says : "If the installation went well, you should see a new
set of menus appear. Goto Tex-Suite > Templates." Creating a new file
newfile.tex doesn't cause this to happen. Am I missing out something?
On a related note, the tutorial is for the gui version of vim (vim-X11).
Would someone know how to use this on a terminal version of vim here?
[1]
> http://vim-latex.sourceforge.net/documentation/latex-suite-quickstart.htm...
--
Thanks!
Regards,
Ankur
https://fedoraproject.org/wiki/User:Ankursinha
"FranciscoD"
13 years, 11 months
Re: HELP! Installed some rawhide packages and now system will not boot! [SOLVED]
by Richard Shaw
On Thu, Jul 29, 2010 at 3:22 PM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
> Well I installed parted/libparted from rawhide to get version 2.3 as I
> was bitten by the resize bug and some other issues with the current
> version in Fedora 12/13. It pulled in a few dependencies and one of
> them broke my system, I'm thinking it was dev-mapper.
>
> On reboot LVM was able to find all 4 of my logical volumes but then
> the boot process fails and I get a message that I need to run e2fsck.
> The actual problem is that for some reason only two of my four LVs are
> showing in /dev/mapper... I booted System Rescue CD and it was able to
> mount the LVs fine and they all checked out clean.
>
> I have the following LVM layout:
>
> VG: vg-hobbes
> LVs: lv-root, lv-var, lv-swap
>
> VG: vg-home (whole disk VG, no dos partition)
> LV: lv-home
>
> Only lv-home and lv-var are showing up in /dev/mapper
>
> My plan at this point is to boot a Fedora LiveCD, mount my LVs and
> chroot to it. I'm hoping rpm and yum will work properly from a
> chroot'ed environment.
The short version is the chroot worked. For those of you who want to
know the gory details read on:
I didn't have any x86_64 boot discs handy so I ended up burning one
from my desktop by booting to my System Rescue CD that I've got
installed on my /boot partition, burning a F13 64bit install DVD and
booting it into rescue mode.
After that I:
- chroot'd to /mnt/sysimage which rescue mode automatically mounts
your existing file system. If you don't use a Rescue mode you'll have
to do that part manually.
- figured out what the offending packages were by 'grep fc14
/var/log/yum.log > fc14_packages.txt'
- Edited the resulting file removing everything but the base package name
- Did a "yum downgrade `cat fc14_packages.txt`"
- (probable unnecessary steps) exited the chroot and did a 'sync'
- Rebooted
On the first reboot it wanted to so a selinux relabel on the whole
file system. Not sure why.. but everything came up normally on the
second reboot!
Next time I try packages from rawhide I think I'll setup a LVM
snapshot first although I think I still would have to boot to a Rescue
disk or other Live system to drop the snapshot and I'm not sure if
snapshot merging is available yet in Fedora.
Richard
Richard
13 years, 11 months
HELP! Installed some rawhide packages and now system will not boot!
by Richard Shaw
Well I installed parted/libparted from rawhide to get version 2.3 as I
was bitten by the resize bug and some other issues with the current
version in Fedora 12/13. It pulled in a few dependencies and one of
them broke my system, I'm thinking it was dev-mapper.
On reboot LVM was able to find all 4 of my logical volumes but then
the boot process fails and I get a message that I need to run e2fsck.
The actual problem is that for some reason only two of my four LVs are
showing in /dev/mapper... I booted System Rescue CD and it was able to
mount the LVs fine and they all checked out clean.
I have the following LVM layout:
VG: vg-hobbes
LVs: lv-root, lv-var, lv-swap
VG: vg-home (whole disk VG, no dos partition)
LV: lv-home
Only lv-home and lv-var are showing up in /dev/mapper
My plan at this point is to boot a Fedora LiveCD, mount my LVs and
chroot to it. I'm hoping rpm and yum will work properly from a
chroot'ed environment.
Any ideas would be greatly appreciated.
Richard
13 years, 11 months
F12: tail -f <filename> inside .gvfs filesystem fails?
by Dan Thurman
I cannot get a tail -f <filename> inside of .gvfs with
a remote mounted ntfs filesystem as done via
Nautilus->Places->Network - this has worked prior
to F12.
Has anyone tried this on F12/13 and got it to work?
13 years, 11 months
SE Linux issue: "Error checking policy version." (sealert -s)
by Christofer C. Bell
When I start the SE Linux Troubleshooter, it does not display any
alerts and the following error appears at the bottom of the window;
Error checking policy version.
I don't see a bug on this in bugzilla, at least that I can find, and
the tool seems to be working for a friend of mine. I've ensured I
have all available patches installed and I have done an auto-relabel
reboot:
# touch /.autorelabel
# reboot
without any change in status. Does anyone have any ideas what may be
causing this?
Thank you.
--
Chris
13 years, 11 months
Preupgrade F11 ---> F12 ?
by Peter Diercks
Hello List,
I am running a server under F11. It is a remote machine which I have no
physical access to. It has a network connection. I wanted to upgrade to
F12 using preupgrade again, but this time I am afraid I'll run into
problems due to the size of /boot (194M, 153M free space).
Does anybody know if this issue has been fixed?
Greetings,
Peter
13 years, 11 months
Still no kmod for new Nvidia
by Michael Miles
Hello
I have been using Fedora 12 and I like the nvidia driver as it makes my
card work like it should.
My question is the last update for Nvidia driver195.36.31-2 seems to
have no kmod for 2.6.32.16_141.
The kmod is there but they list as 2.6.32.16_141-1 and the same as the
kmod for 2.6.32.14_127 also ends with -1
The driver 195.36.31-2 is a update to the 195.36.31-1 but the kmods have
not been updated.
Will these kmods works ok if I manually install them but they are not
being identified because of the different endings driver has a -2, the
kmods end with -1 still.
Also I have sent this to RPM Fusion with no luck with any answer as by
the looks of things all the questions on the mailing list there ( about
20 for a month) have all come from this list.
I just want to know if it is safe to even go ahead with this new driver
as it is an and is mislabelled. That's why Fedora update is not picking
it up.
I know there is no support here, but I hope someone knows the answer to
the question above
Thank you
Michael
Fedora 12 x86_64
Nvidia 9400GT
13 years, 11 months
