Unable to install libX11
by SriLatha
Hey i found that two files in /etc/yum.repos.d which are adobe-linux-i386.repo and yum-iisc-f11.repo.
Also try looking in the directory
/etc/yum.repos.d/
Do you have the following two files there?
fedora.repo
fedora-updates.repo
What are their contents?
As the other responders said, you haven't shown us the real error yet.
K.Srilatha
Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com
14 years, 7 months
problems posting
by Paul Allen Newell
Over the last 3 months, I noticed that I have posted and not gotten any
responses. Fair enough, maybe the posts aren't worth it.
But I just did a check of the archives and I don't see any of my posts.
Don't know if I am incorrectly posting or, in worse case, blacklisted.
So, I am sending out a test with the hopes that someone at least tells
me that it was seen.
I posted this on 27jul09 and didn't hear anything, so I dug in a bit
deeper with my email provider and think I have it sorted out. So, I am
cut-and-pasting (with the addition of this paragraph) and trying again.
If no answer, then at least I have something to go back to the
fedora-lists and/or my email provider to go "huh?"
Thanks in advance,
Paul
14 years, 7 months
Re: convert ico to svg or png
by Hiisi
Gerhard Magnus
Wed, 02 Sep 2009 14:20:42 -0700
>
>Does anyone know a program for FC11 that will convert Windows icon
files
>(.ico) into a format accepted by gnome (.svg or .png)?
>
I asked nearly the same question recently on this list. I was suggested
to use mogrify. It's a part of image-magick project
(www.imagemagick.org). Works excellent! It is in fedora' repos.
--
Hiisi.
Registered Linux User #487982. Be counted at: http://counter.li.org/
14 years, 7 months
Re: X wont start for install on an hp pavilion HDX-16 1370us
by Steven I Usdansky
I had a similar problem with my HP S3707c desktop (GeForce 9100M graphics).
Ended up booting into text mode with kernel parameter nouveau.modeset=0,
logged in as root (no password), ran Xorg -configure, edited the resulting file
to use the vesa driver and copied it to /etc/X11/xorg.conf, then ran startx.
14 years, 7 months
using ant-conrib.rpm
by Christoph Höger
Hi,
has anybody any idea how to use the ant-contrib.rpm?
It sits there in /usr/share/java but ant reports an error on:
<taskdef resource="net/sf/antcontrib/antlib.xml"/>
Suggestions?
Thanks
Christoph
14 years, 7 months
Fedora 11 boot fails on md with two HBAs
by S Murthy Kambhampaty
[Fixed typo in header line, etc.; added info at end.]
With Fedora 11 on IBM x3650 M2 (x86_64), I am having problems booting after adding a second, add-in, SAS controller with 12 SAS disks in an external enclosure. Without the add-in SAS controller, the system boots fine and provides file sharing over samba, etc.
The main problem with this machine is that it has an EFI BIOS which appears to bind the external/add-on SAS HBA before the internal one on which the system drives are hosted (they are both LSI SAS 3801e HBAs - the internal one has an IBM part number, while the external one is LSI). Changing the BIOS order in the option ROMs and disabling boot services on the external/add-on HBA does not seem to affect the adapter binding order, and the EFI BIOS does not provide any mechanism for controlling this. Which brings us to the bootup issues.
Note that after booting into rescue mode from the installer image mdadm works as expected, with raid arrays detected and started without any problems on the disks located on both controllers. The md configuration is :
/boot is on /dev/md0 with devices /dev/sd[mn]3, raid1
/root is on /dev/md1 with devices /dev/sd[op]1, raid1
/usr, /var and swap are on an LVM vg on /dev/md2 with devices /dev/sd[m-p]2, raid10
/boot/efi is on /dev/md64 with devices /dev/sd[mn]2, raid1
A separate vg for the data volume is on /dev/md127 with devices /dev/sd[a-l], raid6 (whole disks)
/dev/sd[m-p] are hosted on the internal HBA, and appear as /dev/sd[a-d] when the add-in HBA is disabled. /dev/sd[a-l] hang of the add-in HBA. Note that in rescue mode, the disks start at /dev/sdc, as I'm booting from a virtual console, and /dev/sda and /dev/sdb are assigned to virtual USB disks.
The problem seems to be that during bootup the raid arrays are autodetected rather than using mdadm. If the raid456 module is not included in the initrd image, booting fails with raid6 personality not detected, when the boot process tries to start /dev/md1 incrementally with /dev/sda as its first member. (This appears not to reference /etc/mdadm.conf in the initrd at all.)
If the raid456 module is included in the initrd image (using --with=raid456), booting fails with /dev/sda added incrementally to /dev/md1 and /dev/sdb added incrementally to /dev/md2; it appears autodetect fails because the raid device was built from rescue mode, so the components are listed with different letters in the superblock.
If I put a line in /etc/mdadm.conf in the initird image, to only scan partitioned disks (DEVICE /dev/sd*[1234]), boot hangs after loading the raid modules. (Potentially on the call to mkblkdevs after scsi_wait_scan is rmmod-ed.)
Partitioning /dev/sd[a-l] and setting the partition type to other than 'raid' does not seem to make any difference, during bootup the kernel still tries to assemble the root raid device (/dev/md1) from /dev/sda (though it is on /dev/md[op]1.
This seems to suggest that the md devices are being started by kernel raid autodetection rather than mdadm. Simply switching to mdamd would likely solve the problem, given it works fine in rescue mode. Alternative suggestions are welcome, of course.
Thanks for the help,
Murthy
14 years, 7 months
X wont start for install on an hp pavilion HDX-16 1370us
by Kevin Kempter
Hi all;
My son bought an hp Pavilion (HDX-16 1370us) laptop, with a 16" screen.
Upon trying to start the anaconda installer Fedora 10 says 'X failed to start
reverting back to text mode"
Thoughts? anyone have any hp experience similar they can share (hopefully with
solutions)?
Thanks in advance
14 years, 7 months
Fedora 11 boot faisl on md with two HBAs
by S Murthy Kambhampaty
With Fedora 11 on IBM x3650 M2 (x86_64), I am having problems booting after adding a second, add-in, SAS controller with 12 SAS disks in an external enclosure. Without the add-in SAS controller, the system boots fine and provides file sharing over samba, etc.
The main problem with this machine is that it has an EFI BIOS which appears to bind the external/add-on SAS HBA before the internal one on which the system drives are hosted (they are both LSI SAS 3801e HBAs - the internal one has an IBM part number, while the external one is LSI). Changing the BIOS order in the option ROMs and disabling boot services on the external/add-on HBA does not seem to affect the adapter binding order, and the EFI BIOS does not provide any mechanism for controlling this. Which brings us to the bootup issues.
Note that after booting into rescue mode from the installer image mdadm works as expected, with raid arrays detected and started without any problems on the disks located on both controllers. The md configuration is :
/boot is on /dev/md0 with devices /dev/sd[mn]3, raid1
/root is on /dev/md1 with devices /dev/sd[op]2, raid1
/usr, /var and swap are on an LVM vg on /dev/md2 with devices /dev/sd[m-p]2, raid10
/boot/efi is on /dev/md64 with devices /dev/sd[mn]2, raid1
A separate vg for the data volume is on /dev/md127 with devices /dev/sd[a-l], raid6 (whole disks)
/dev/sd[m-p] are hosted on the internal HBA, and appear as /dev/sd[a-d] when the add-in HBA is disabled. /dev/sd[a-l] hang of the add-in HBA. Note that in rescue mode, the disks start at /dev/sdc, as I'm booting from a virtual console, and /dev/sda and /dev/sdb are assigned to virtual USB disks.
The problem seems to be that during bootup the raid arrays are autodetected rather than using mdadm. If the raid456 module is not included in the initrd image, booting fails with raid6 personality not detected, when the boot process tries to start /dev/md1 incrementally with /dev/sda as its first member. (This appears not to reference /etc/mdadm.conf in the initrd at all.)
If the raid456 module is included in the initrd image (using --with=raid456), booting fails with /dev/sda added incrementally to /dev/md1 and /dev/sdb added incrementally to /dev/md2; it appears autodetect fails because the raid device was built from rescue mode, so the components are listed with different letters in the superblock.
If I put a line in /etc/mdadm.conf in the initird image, to only scan partitioned disks (DEVICE /dev/sd*[1234]), boot hangs after loading the raid modules. (Potentially on the call to mkblkdevs after scsi_wait_scan is rmmod-ed.)
This seems to suggest that the md devices are being started by kernel raid autodetection rather than mdadm. Simply switching to mdamd would likely solve the problem, given it works fine in rescue mode. Alternative suggestions are welcome, of course. I will try partitioning the 12 disks, with ext2 partitions rather than raid-auto partitions, to see if this gets me past this issue. However, it would be nice to be able to create the raid devices on whole disks, and avoid the extra step.
Thanks for the help,
Murthy
14 years, 7 months
Re: Argh!! Html is on again!
by g
Patrick O'Callaghan wrote:
> In fact it was multipart/signed, sorry.
accepted. my apoligies for not reading full thread be for replying to your
post to my reply.
in addition, i agree 100% with anne. no email client should have 'text/html'
as a default.
--
peace out.
tc,hago.
g
.
****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****
14 years, 7 months