rpm -vhF foomatic fails
by Harry Putnam
rpm -qa|grep foomatic
foomatic-3.0.1-2
rpm -vhF /mnt/exp/fed2/RPMS/foomatic-3.0.1-6.i386.rpm
(That directory is my mirror of rawhide)
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such file or directory
error: Failed dependencies:
perl(:MODULE_COMPAT_5.8.4) is needed by foomatic-3.0.1-6
I can't find any perl module by that name, but it doesn't really
appear to be the package name anyway. It should be though shouldn't
it? How might I track this dependency down without a name.
I've tried all file names inside rpmdb-fedora-2-0.20040716.i386.rpm
Which is the current rawhide pkg containing the full distro data base.
I keep a list of all file names on hand so looked for `grep -e
module_compat homemade_file.db' and come up with zip.
What use is this reference and what does it point to?
19 years, 10 months
Re: SATA boot whish for FC3
by Dima Gutzeit
I have a question regarding this issue ...
Today I've installed FC2 on computer with SATA as the only harddisk. For the
installation matter I've connected a CDROM to ide interface. The
installation went just ok, but now the computer refuses to boot if I detach
the cdrom drive. It does not matter what cd is in, with cdrom attached it
books OK from SATA drive , but when detaching the device it fails with :
Kernel panic: VFS unable to mount root on unknown-block(0,0)
Anyone has a solution for it ?
Thanks in advance.
----- Original Message -----
From: "Bjorn Andersen" <ba(a)linuxin.dk>
To: <fedora-test-list(a)redhat.com>
Sent: Tuesday, July 20, 2004 12:06
Subject: SATA boot whish for FC3
> Hi
>
> Since Fedora Core 1 and the support of SATA disks there haw been a
> problem in detection of standard boot device.
> The Fedora installer dont detect what device the bios will boot on.
> Annaconda standard boot on /dev/hda if it is present, but the people
> that have a SATA disk as primary boot device, will have to switch the
> boot loader to that device. If not, the bootloader will not boot,
> because it is set on hda (the secondary harddisk).
>
> It would be a god idea to have Anaconda detect what primary bootdevice
> from the bios. (like SuSE)
>
> I have seen a lot of frustrated newbees telling me that Fedora 2 dont
> support SATA disks, and thats a shame.
>
>
>
> Regards
> Bjorn Andersen
>
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> To unsubscribe:
> http://www.redhat.com/mailman/listinfo/fedora-test-list
>
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
19 years, 10 months
Advice to swithc to xorg from XFree86-4.3.0-59
by Harry Putnam
I'd like to finally make the switch from XFree to xorg at this late
date. Its starting to cause too many dependancy problems with updates
or yum. Like updating to newest mozilla, dependancy problems crop
up.
I've gotten along for quite some time with `rpm [Ui]vh --nodeps' on
some updates I thought would work like that, but need to get this
cleaned up. The trouble is I don't want to go the clean install
route.
Its just too many tweaks and customizations involved on my main box.
I'm supposedly running fed2t1:
cat /etc/fedora-release
Fedora Core release 1.90 (FC2 Test 1)
But am actually running many rawhide packages. Its been going on so
long now that I don't even know for sure what is running from rawhide
anymore.
So cutting to the chase... and understanding my predicament is due to
sloth (that is, of my own making)... can someone help me devise a
stategy to get rid of XFree and get started running xorg in a
manner likely to leave me with an operable OS.
If I loose X for awhile that is not a big problem as I'm comfortable
in text mode. It does get to be a drag trying to browse quickly on
line in text but I can manage all config etc from the command line.
I really doubt it could be as easy as:
rpm -e --nodeps 'XFree' then
yum install xorg-x11.
I tried that last part to see what would happen, and yum tells me:
yum install xorg-x11
Unable to find pid
Gathering header information file(s) from server(s)
Server: Rawhide Development
Finding updated packages
Downloading needed headers
Resolving dependencies
.Package XFree86-tools needs XFree86, this is not available.
Package XFree86-twm needs XFree86, this is not available.
Package XFree86-Xnest needs XFree86 = 4.3.0-59, this is not available.
Package XFree86-xdm needs XFree86 = 4.3.0, this is not available.
All those packages are actually installed but that isn't the goal.
rpm -qa|grep XFree:
XFree86-tools-4.3.0-59
XFree86-xauth-4.3.0-59
XFree86-4.3.0-59
XFree86-base-fonts-4.3.0-59
XFree86-truetype-fonts-4.3.0-59
XFree86-xdm-4.3.0-59
XFree86-Mesa-libGLU-4.3.0-59
XFree86-Mesa-libGL-4.3.0-59
XFree86-font-utils-4.3.0-59
XFree86-libs-data-4.3.0-59
XFree86-twm-4.3.0-59
XFree86-xfs-4.3.0-59
XFree86-75dpi-fonts-4.3.0-59
XFree86-Xnest-4.3.0-59
XFree86-devel-4.3.0-59
XFree86-libs-4.3.0-59
XFree86-100dpi-fonts-4.3.0-59
So that route looks fraught with troubles. I wonder how it would go
if I did `rpm -e --nodeps' all XFree pkgs first. But would like to
hear some input before taking the leap.
19 years, 10 months
Failed hard disk install
by Pedro Fernandes Macedo
I'm trying to install FC3 test 1 here...
First , all cds have the right md5. Burnt cd1 , placed the isos on
/dev/hdc1 (fat32 partition that I always used in disk installs , except
in fedora core 2 test 2 , when I had to use a dvd disk).
After booting with linux askmethod selinux=0 xfs jfs hde=noprobe
hdf=noprobe hdg=noprobe hdh=noprobe (to test both xfs and jfs and dont
have to wait to sata probing), I got a failure message when I selected
the right directory and device , saying that the iso files werent found.
Switching to the other vts , there was this message:
<4> VFS: Can't find ext2 filesystem on dev hdc1
<4> Unable to load NLS charset ascii
<3> fat: IO charset ascii not found
I decided to give another try and copied the isos to my home xfs
partition (dont have any ext2/3 partitions here.. only xfs). Again ,
same options and same error...
As I said before , the same fat partition has been used to install all
the fedora stable and test releases since fedora core 1 on my computer ,
except for fedora core 2 test 2 , which asked me for a driver to use the
harddisk , so I installed from a dvd... Also , I havent changed anything
on this partition (it's where I keep all my iso files and a few other
things that I dont change very often)
Just added this to bugzilla , under bug number 128135 .
--
Pedro Macedo
19 years, 10 months
SATA boot whish for FC3
by Bjorn Andersen
Hi
Since Fedora Core 1 and the support of SATA disks there haw been a
problem in detection of standard boot device.
The Fedora installer dont detect what device the bios will boot on.
Annaconda standard boot on /dev/hda if it is present, but the people
that have a SATA disk as primary boot device, will have to switch the
boot loader to that device. If not, the bootloader will not boot,
because it is set on hda (the secondary harddisk).
It would be a god idea to have Anaconda detect what primary bootdevice
from the bios. (like SuSE)
I have seen a lot of frustrated newbees telling me that Fedora 2 dont
support SATA disks, and thats a shame.
Regards
Bjorn Andersen
19 years, 10 months
PHP5
by Si Jones
Ello,
Is there any chance that PHP5 will be included in FC3, as 5 is now in
it's final release.
Cheers,
19 years, 10 months
Mount Point / busy FC3 T1 - Soundcard Detection
by Si Jones
Hi All,
1.
When rebooting / shuting down a message near the end says Mount / is busy.
Is this a bug with something still using the hard drive that shouldn't
be or is this normal now?
2.
If you have 2 sound cards, if you select one as the primary it does not
change the modprobe.conf
to reflect this and the sound will not work.
I.E
I have onboard Nvidia audio and a soundblaster, the soundblaster is
always detected first on install,
during the install i said i wanted it to be the primary soundcard but it
isn't and i have to manually
go into modprobe and change the soundcards around.
Regards,
Simon Jones
19 years, 10 months
rpm -vhF foomatic fails
by Harry Putnam
rpm -qa|grep foomatic
foomatic-3.0.1-2
rpm -vhF /mnt/exp/fed2/RPMS/foomatic-3.0.1-6.i386.rpm
(That directory is my mirror of rawhide)
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such file or directory
error: Failed dependencies:
perl(:MODULE_COMPAT_5.8.4) is needed by foomatic-3.0.1-6
I can't find any perl module by that name, but it doesn't really
appear to be the package name anyway. It should be though shouldn't
it? How might I track this dependency down without a name.
I've tried all file names inside rpmdb-fedora-2-0.20040716.i386.rpm
Which is the current rawhide pkg containing the full distro data base.
I keep a list of all file names on hand so looked for `grep -e
module_compat homemade_file.db' and come up with zip.
What use is this reference and what does it point to?
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
19 years, 10 months
Good Install of FC3T1 - So Far
by Clyde Kunkel
Did a clean install except for /boot partition. No problems with media
checks all 4 discs. Used same device as burned the ISOs--Sony DVD RW
DRU-530A. First minor problem was KVM crazy mouse--plugged a separate
mouse in directly to PS/2 port to get thru install. Had tried to use
psmouse.proto=imps at inital boot: prompt, but wouldn't take. Had to
wait for install to finish. My Firewire drive and USB drive are both
seen, can't mount yet since they are NTFS spindles. Disabled selinux
during install.
Only other current problem is SAMBA. Get following errors when
executing system-config-samba:
Traceback (most recent call last):
File "/usr/share/system-config-samba/system-config-samba.py", line 38,
in ?
mainWindow.MainWindow(debug_flag)
File "/usr/share/system-config-samba/mainWindow.py", line 75, in
__init__
self.samba_data = sambaParser.SambaParser(self)
File "/usr/share/system-config-samba/sambaParser.py", line 40, in
__init__
self.parseFile()
File "/usr/share/system-config-samba/sambaParser.py", line 71, in
parseFile
token = self.createToken(line)
File "/usr/share/system-config-samba/sambaParser.py", line 143, in
createToken token = sambaToken.SambaToken
(sambaToken.SambaToken.SAMBA_TOKEN_KEYVAL, (name, value), self.parent)
File "/usr/share/system-config-samba/sambaToken.py", line 36, in
__init__
raise AttributeError, value
AttributeError: ('cups options', 'raw')
Couldn't find anything in bugzilla, still looking in archives. Anyone
seen anything like this?
Continuing with testing....
19 years, 10 months
Yet another FC3 wishlist
by Michel Salim
Hi,
Would it be possible to include support for the Intel Pro Wireless
2100 and 2200 wireless cards? (The drivers are available at
ipw2100.sf.net and ipw2200.sf.net respectively)
Most Centrino laptops come with either of these cards, so it would be
a nice addition. There might be license problems with bundling the
binary firmware, but it is packaged separately from the drivers and
from SuSE 9.1 install reports it seems that SuSE just bundles the
drivers and tell their users to get the firmware themselves.
Thanks,
- Michel
19 years, 10 months