RE: best practices for using a small SSD boot drive and a big regular one?
anyway, is there a doc that gives one advice about a sane partitioning? it's not really a small SSD -- you can pack a lot into 128G. i'm just looking to be as intelligent about this as possible. Do not know about sane partitioning but I have the same system that I bought with a 160GB ssd and the 750GB spinning rust. I have been running with this partitioning for about seven months. The first disk set-up was let Fedora pick. [agagne@dw-agagne ~]$ df -h Filesystem Size Used Avail Use% Mounted on rootfs 50G 7.7G 40G 17% / devtmpfs7.9G 0 7.9G 0% /dev tmpfs 7.9G 2.1M 7.9G 1% /dev/shm tmpfs 7.9G 884K 7.9G 1% /run /dev/mapper/vg_dwagagne01-lv_root50G 7.7G 40G 17% / tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup tmpfs 7.9G 0 7.9G 0% /media /dev/sda2 497M 114M 358M 25% /boot /dev/mapper/vg_dwagagne01-lv_home81G 11G 67G 14% /home /dev/mapper/vg_dwagagne02-lv_opt 50G 2.0G 46G 5% /opt /dev/mapper/vg_dwagagne02-lv_vmachines 250G 127G 111G 54% /vmachines /dev/mapper/vg_dwagagne02-lv_scratch200G 30G 160G 16% /scratch Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: best practices for using a small SSD boot drive and a big regular one?
/ [agagne at dw-agagne https://admin.fedoraproject.org/mailman/listinfo/users ~]$ df -h // Filesystem Size Used Avail Use% Mounted on // rootfs 50G 7.7G 40G 17% / // devtmpfs7.9G 0 7.9G 0% /dev // tmpfs 7.9G 2.1M 7.9G 1% /dev/shm // tmpfs 7.9G 884K 7.9G 1% /run // /dev/mapper/vg_dwagagne01-lv_root50G 7.7G 40G 17% / // tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup // tmpfs 7.9G 0 7.9G 0% /media // /dev/sda2 497M 114M 358M 25% /boot // /dev/mapper/vg_dwagagne01-lv_home81G 11G 67G 14% /home // /dev/mapper/vg_dwagagne02-lv_opt 50G 2.0G 46G 5% /opt // /dev/mapper/vg_dwagagne02-lv_vmachines 250G 127G 111G 54% /vmachines // /dev/mapper/vg_dwagagne02-lv_scratch200G 30G 160G 16% /scratch / sorry, i'm not sure what's going on up there. first, are you saying that when you installed, you picked both drives as installable devices and you just went with with what the installer chose for the first (SSD) drive? and i'm assuming that you used your entire 2nd drive for the 02 volume group, is that it? Sorry for the lack of clarity. I installed to the first drive only letting Fedora set-up partitioning. The second drive I set-up manually after the os install. Currently the second drive is using 550GB of the 750 for VG 02. 200GB on the second drive is currently being left in reserve. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: way to flush /var/log/message
When I first looked into the man pages et al for iptables, I found the LOG but no way to specify a file. The best I could sort out was using a prefix so I would at least have a token to search for in /var/log/messages. I just did a quick google to see if I missed something. The only thing I see is a level and a link to syslog.conf, which I did not get on first reading (and it didn't feel like where I should be looking to begin with). Can you point me to a link? You could look at sending iptables messages to /var/log/iptables using rsyslog. http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/ Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: way to flush /var/log/message
On 5/21/2012 12:15 PM, Alan J. Gagne wrote: / // You could look at sending iptables messages to /var/log/iptables using // rsyslog. // // http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/ // // Alan // // / Alan: Thanks for the reply. I did an initial read of the page and it looks interesting. That being said, I'm going to have to take a few more passes to make sure I understand it. If I read correctly, it isn't a replacement for logging to /var/log/messages, just a way to filter those logs into another log that only gets what I want to see? You can use it to redirect all iptables messages to a seperate log only. You may want to look at ulogd in the fedora repo. I have used this in the past for saving data to mysql. Alan Name: ulogd Arch: x86_64 Version : 1.24 Release : 15.fc16 Size: 131 k Repo: fedora Summary : The userspace logging daemon for netfilter URL : http://gnumonks.org/projects License : GPLv2 Description : Ulogd is an universal logging daemon for the ULOG target of netfilter, the : Linux 2.4+ firewalling subsystem. Ulogd is able to log packets in various : formats to different targets (text files, databases, etc..). It has an : easy-to-use plugin interface to add new protocols and new output targets. Name: ulogd-mysql Arch: x86_64 Version : 1.24 Release : 15.fc16 Size: 11 k Repo: fedora Summary : MySQL output plugin for ulogd URL : http://gnumonks.org/projects License : GPLv2 Description : Ulogd-mysql is a MySQL output plugin for ulogd. It enables logging of : firewall information into a MySQL database. Name: ulogd-pcap Arch: x86_64 Version : 1.24 Release : 15.fc16 Size: 9.2 k Repo: fedora Summary : PCAP output plugin for ulogd URL : http://gnumonks.org/projects License : GPLv2 Description : ulogd-pcap is a output plugin for ulogd that saves packet logs as PCAP file. : PCAP is a standard format that can be later analyzed by a lot of tools such as : tcpdump and wireshark. Name: ulogd-pgsql Arch: x86_64 Version : 1.24 Release : 15.fc16 Size: 11 k Repo: fedora Summary : PostgreSQL output plugin for ulogd URL : http://gnumonks.org/projects License : GPLv2 Description : Ulogd-pgsql is a PostgreSQL output plugin for ulogd. It enables logging of : firewall information into a PostgreSQL database. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Wired vs (bad) Wireless communications speeds
Between my laptop and my server there is a WiFi modem and an ADSL router and I think the comms is too slow. The device speed for each is: Server: Intel 82567LF Gigabit: 10/100/1000 Mb/s Belkin Wireless F5D7230-4v7: 10/100 Mb/s Belkin ModemRouter F1PI241ENau: 10/100 Mb/s Asus Zenbook UX31: ath9k: 54 Mb/s RJ45 via USB: 10/100 Mb/s and Cat5 cables. On an unloaded network I can get about 6.5 Mb/s when I use the cable connection to the laptop but nothing better than about 1.5 Mb/s for the wireless connection - and even that is when the laptop and the wireless router are only about 1.5m apart (the XFCE network icon shows connection quality is then at about 90%). Anyone know why the wireless performance is not better than this? You could be hitting a a Atheros driver problem. On my laptop I had to use the workaround below to correct horrible wireless performance. I am not familiar with what can be done your system so YMMV. 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: AzureWave Device 2c37 Kernel driver in use: ath9k Kernel modules: ath9k WORKAROUND: rmmod ath9k modprobe ath9k nohwcrypt=1 echo options ath9k nohwcrypt=1 /etc/modprobe.d/ath9k.conf Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Is it me or is it sudo?
That's true. However, as I've explained, that line is commented out while I'm debugging the issue with the username. I suppose, push comes to shove that I can use an empty sudoers file except for that one line in order to make absolutely certain nothing else is interfering, but since Aaron Konstam verified that is /should/ work as I have it (as well as others) I don't think I need to go that drastic. The one thing I haven't done is post my entire sudoers file. I will if anyone thinks it'll help. I'm really not trying to be difficult here, but this is driving me nuts. You could also just add a file to /etc/sudoers.d. I believe these entries get processed last. I use the wheel group set-up with passwd in sudoers file so I just added a file using sudoedit /etc/sudoers.d/utest. Then added a line USERNAME ALL=(ALL) NOPASSWD: ALL This overrides my wheel group entry and works fine. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Unable to upgrade some few softwares
Packages skipped because of dependency problems: firefox-10.0.1-1.fc16.x86_64 from updates gstreamer-plugins-bad-free-0.10.22-2.fc16.2.x86_64 from updates libvpx-1.0.0-1.fc16.i686 from updates libvpx-1.0.0-1.fc16.x86_64 from updates xulrunner-10.0.1-3.fc16.x86_64 from updates There was a problem with that last week that was cleared up. Something with libvpx. Try clearing your metadata. yum clean metadata Then try to update again. I have my system fully updated for those packages no problem. [root@linux0 ~]# rpm -qa | grep gstreamer-plugins-bad gstreamer-plugins-bad-free-0.10.22-2.fc16.2.x86_64 [root@linux0 ~]# rpm -qa | grep firefox firefox-10.0.1-1.fc16.x86_64 [root@linux0 ~]# rpm -qa | grep libvpx libvpx-1.0.0-1.fc16.x86_64 [root@linux0 ~]# rpm -qa | grep xulrunner xulrunner-10.0.1-3.fc16.x86_64 Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: F16-X86_64-Live-KDE won't boot on XPS 17
I have a new Dell XPS17 laptop. (i7, 16 GB RAM, nvidia 555 video device, Windows 7 installed) I am trying to run F16-x86_64-Live-KDE on it via a USB flash device. It find the USB device. grub(2) runs. I can select the kernel. It starts the boot process. It hangs with the following message: udevd[166]: /sbin/modprobe -bv pci: snip [168] terminated by signal 9 (Killed) dracut: starting plymouth daemon The same OS on the same USB flash device runs fine on my i5 server. What video card are you using with the i5 server. Not sure if this is your issue but I just did a lot of research before buying a new 17 laptop and avoided systems with Nvidia video that had the Optimus technology. Seems there is a lot of grief with running Linux with those cards. We have some systems at work with Ubuntu but, they have a mux switch to turn off Optimus in the bios. Couldn't find out if the XPS17 had this option. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: F16-X86_64-Live-KDE won't boot on XPS 17
Thanks for the reply. The laptop has the 3D screen and does NOT have the optimus card. As far as I know, its a plain NVIDIA GeForce GT 555M 3GB graphics card. How could I run lspci prior to booting to find out ? With grub2, is there a way to force a graphical boot that wouldn't invoke the error I'm seeing ? I am going to be really peeved if I can't run Linux on the XPS17. I ran Windows 7 for an hour and it sucks ! How an OS can run so slow on an i7 with 16 GB of RAM is beyond me. Might want to check this out. http://www.nvidia.com/object/product-geforce-gt-555m-us.html GeForce GT 555M Outstanding DX11 graphics performance and long battery life with NVIDIA® Optimus™ technology. Try booting a rescue disk to check hardware out(lspci). Again check your bios to see if you can disable Optimus. There are some efforts out there to make this work with Linux. I think bumblebee might be getting close to working or is. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: F16-X86_64-Live-KDE won't boot on XPS 17
I got it to boot further by selecting start in basic graphics mode under Troubleshooting options in grub2. However, it hangs when starting KDE. However, I am able to command line session going. I am able to log in as liveuser. I am able to su to root. Now what should I do ? How do I do the install from the command line ? Not sure if you can do a text mode install from the live cd. You may need to download one of the other media options. This is from the test mode document. If your system has a graphical display, but graphical installation fails, try booting with the xdriver=vesa option – refer to Chapter 11, Boot Options http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/ch-Installation_Phase_2-x86.html#s1-guimode-textinterface-x86 Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Buy an SSD now, or wait?
I just wondered if anyone here has had any experience in using SSDs in general, and with Fedora in particular? I am thinking about an upgrade, but I am uncertain whether it is worth it to invest in an SSD now, or let the technology ripen for a few more years. I believe the SSD market will expand massively in the coming years, and with that, innovation and development in the field as well, so waiting seems more reasonable at this stage. Any thoughts? I would definitely go for it. I have been using ssd's in a couple of systems for about a year and half. So far I am quite happy with the performance gain they provide. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE:/var/log/messages
Try here ! http://fedoraproject.org/wiki/Systemd -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Stopping VirtualBox sessions
The trouble is, if i login to my remote user desktop, cjremote, here at work and open VirtualBox, I can see the running virtual machine in the VirtualBox management interface but I can't show it or connect to it, and, if I try to pause it, I get an access denied message Is there some way to do this? Check into the command line tools available for VirtualBox. I use these exclusively to start/stop virtualBox remotely. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
question re: multi-head gnome3
Just a warning: that mode is very buggy. I tried it for a while and when I reported various issues to the GNOME developers (directly, not in BZ), I was told that they have no plans to support anything other than the default Only one monitor gets workspaces approach. The more I hear about things like this from the Gnome devs the more it sounds like they're only interested in having Gnome 3 able to do things the devs need and don't care about anybody else. I hope I'm wrong, because if I'm right, it won't be long before Gnome has marginalized itself as the vast majority of users abandon it because they can't get it to do what they need anymore. No Worries. Tablets only have one head currently. :-) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
re: vi ? howto show cursor position
Is this something lost from the compiled distribution or is there some *:set* method that will turn it back on and, if so, would somebody share the magic formula? It does work for me in F14 gnome terminals without doing anything. set ruler should work. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: Routing not working
My next step is finding the digital thermometer we have around here somewhere and measuring the temp on f14 compared to f15 :-). Would that be oral or otherwise? Seems otherwise might be appropriate given the level of fun this release has provided the users. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Ethereal Replacement?
Is there some replacement for the old ethereal program? Wireshark. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: pings with noise
According to the man page whenever you use the -a option on the ping command as in: ping -a ip-address each ping return should cause a noise to be generated. I can't seem to get that too happen. What could be wrong? I just tried this on Fedora14 and it works. You may want check your sound preferences to make sure the alert volume is up and not muted. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: UPnP vs. Fedora 14 firewall
I have several different services on my network that use UPnP, and none of them seem to work unless I disable the Firewall on my Fedora 14 desktops/laptops. Everything I've read says that I should be able to allow UDP on port 1900, but that doesn't seem to help. Can anyone tell me or point me to documentation about what I need to enable to let my Fedora 14 machines to see the services via UPnP? My memory is a bit sketchy but along with IGD I had to add a few firewall rules and a route to allow multicast upnp. This was for a fedora box that I was using as a firewall/gateway system. Some igd docs. http://linux-igd.sourceforge.net/documentation.php Below is a script I used for the firewall rules. [agagne@linux0 tmp]$ cat bin/add-upnpd.sh #iptables -N UPNP #iptables -I FORWARD 2 -j UPNP #iptables -A INPUT -i eth1 -p tcp --dport 2869 -j ACCEPT #iptables -A INPUT -i eth1 -p udp --dport 1900 -j ACCEPT # Good firewalls drop everything that has not been explicitly allowed, # so first create rules to allow other computers to connect to the upnp daemon. iptables -t filter -A INPUT -i eth1 -d 239.0.0.0/8 -j ACCEPT iptables -t filter -A INPUT -i eth1 -p tcp --dport 49152 -j ACCEPT iptables -t filter -A INPUT -i eth1 -p udp --dport 1900 -j ACCEPT # Create chains for the rules to be created by the upnp daemon. iptables -t filter -N UPNP_FORWARD iptables -t filter -I FORWARD 2 -j UPNP_FORWARD iptables -t nat -N UPNP_PREROUTING iptables -t nat -A PREROUTING -j UPNP_PREROUTING Use at your on risk as I am not a firewall expert. I got this working after much googleing on how to set-up igd so my son could play games from another system runnning win7. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: anyone running android sdk to talk to a real phone on fedora 14
I'm pretty sure it really is drawing too much power. I had 3 different systems that all showed the same symptoms, and lots of other Samsung Intercept users have complained of similar problems. If there was some way to just make it talk USB without also insisting on trying to charge the battery when plugged in, it might be OK :-). Sounds like it is similar to a Blackberry. You need a driver that will increase voltage to the usb port you are plugged into. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
OT: bash question
You could try echo $0 from inside you script. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
OT: bash question
My mistake. I forgot to say that the file was invoked from a link. Your proposed solution shows the link's location. I have to discover the target of the link. echo `ls -la $0` -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE; Pcscd
What could cause this? Dec 9 03:24:02 oh1mrr pcscd: winscard.c:285:SCardConnect() Reader E-Gate 0 0 Not Found Dec 9 03:24:02 oh1mrr pcscd: winscard_svc.c:447:ContextThread() CONNECT rv=0x8019 for client 2 I don't have service pcscd running. Mystery... While I do not know what is causing this message. I can tell you it is triggered by something cron.daily runs. Dec 8 03:48:01 linux2 anacron[5804]: Job `cron.daily' started Dec 8 03:48:18 linux2 pcscd: winscard.c:285:SCardConnect() Reader E-Gate 0 0 Not Found Dec 8 03:48:18 linux2 pcscd: winscard_svc.c:447:ContextThread() CONNECT rv=0x8019 for client 2 I don't have any smart card readers on this system so I just removed pcsc-lite to stop these messages. Name: pcsc-lite Arch: i686 Version : 1.6.4 Release : 1.fc14 Size: 151 k Repo: fedora Summary : PC/SC Lite smart card framework and applications URL : http://pcsclite.alioth.debian.org/ License : BSD Description : The purpose of PC/SC Lite is to provide a Windows(R) SCard interface : in a very small form factor for communicating to smartcards and : readers. PC/SC Lite uses the same winscard API as used under : Windows(R). This package includes the PC/SC Lite daemon, a resource : manager that coordinates communications with smart card readers and : smart cards that are connected to the system, as well as other command : line tools. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: iso dvd
On 12/01/2010 09:49 AM, William Stock wrote: You have to burn the DVD as an .iso image. If you burn it as a regular file it won't boot/run. If you're using Brasero it's the bottom button (burn image). I prefer the KISS method: right click on the file in Nautilus and select Write to Disc. Works a charm and gets it Right every time. Come on, have some fun. Open a terminal and growisofs. :-) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: Yum strange behavior after upgrade to Release 14
On Wed, Dec 1, 2010 at 1:07 PM, John Vo jvo at eagle.net wrote: Greetings: I am new to the list so I will apologize for any problem with my post. I upgraded my Fedora 13 to 14 using the yum method. Although that method is pseudo-supported, I would try preupgrade in the future as recommended by http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum After the upgrade, when I ran yum upgrade, I ran into a few problem: Did you run yum upgrade or yum update? Error: Package: PackageKit-0.6.6-2.fc13.x86_64 (@updates/13) Requires: PackageKit-yum-plugin = 0.6.6-2.fc13 Removing: PackageKit-yum-plugin-0.6.6-2.fc13.x86_64 (@updates/13) PackageKit-yum-plugin = 0.6.6-2.fc13 Updated By: PackageKit-yum-plugin-0.6.9-4.fc14.x86_64 (fedora) PackageKit-yum-plugin = 0.6.9-4.fc14 You could try using --skip-broken to work around the problem And...many many of these.. ** Found 313 pre-existing rpmdb problem(s), 'yum check' output follows: ImageMagick-6.6.4.1-14.fc14.1.x86_64 is a duplicate with ImageMagick-6.5.8.10-6.fc13.x86_64 PackageKit-0.6.9-4.fc14.x86_64 is a duplicate with PackageKit-0.6.6-2.fc13.x86_64 PackageKit-device-rebind-0.6.9-4.fc14.x86_64 is a duplicate with PackageKit-device-rebind-0.6.6-2.fc13.x86_64 PackageKit-glib-0.6.9-4.fc14.x86_64 is a duplicate with PackageKit-glib-0.6.6-2.fc13.x86_64 PackageKit-gtk-module-0.6.9-4.fc14.x86_64 is a duplicate with PackageKit-gtk-module-0.6.6-2.fc13.x86_64 I'm a casual Fedora users. Help please. Don't take this the wrong way as it can be difficult to discern tone in an email but, the site I referenced specifically states: Although upgrades with yum works, it is not explicitly tested as part of the release process by the Fedora Project. If you are not prepared to resolve issues on your own if things break, you should probably use the recommended installation methods instead. There may be a more automated method but I ran into some issues orphaned packages after upgrading with preupgrade and did the following for each problem package: Uninstall the old package: rpm -e --nodeps package Install the new package: yum install package Richard I used preupgrade, but yum distro-sync did a great job of cleaning up the packages identified by running package-cleanup --orphans. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: Ganglia - gmetad segfaults after starting gmond [SOLVED]
After upgrade to fedora 14 from 13 gmetad process segfaults when updating rrd graphs. Anybody seeing this problem ? [linux2 ~]# rpm -qa | grep ganglia ganglia-web-3.1.7-2.fc14.i686 ganglia-gmetad-3.1.7-2.fc14.i686 ganglia-3.1.7-2.fc14.i686 ganglia-gmond-3.1.7-2.fc14.i686 To get around this problem I compiled ganglia 3.1.7 from source The problem was with rrdtool-1.3.8-4. The new version of rrdtool-1.4.4-1.fc14.i686 fixes this issue. See https://bugzilla.redhat.com/show_bug.cgi?id=654246 for details. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: One satisfied customer with f14!
Jerry Feldman wrote: On 11/17/2010 11:36 AM, Bill Davidsen wrote: Just a in my experience note, running an upgrade from a DVD/USB has been far more successful than preupgrade for me. Older installs had a small /boot and often don't work well due to lack of room. YMMV. When I installed F13 from DVD, I specifically allocated a larger /boot for this specific reason. My /boot is 485MB. If preupgrade runs in that I'd love to know how much stuff it installs. And doesn't change my feelings about the inherent complexity of doing an in-place upgrade on a running system. On three machines I just upgraded to F14 from F13 they have 300MB /boot. I took all three down to just the running kernel prior to using preupgrade. Just before the reboot to the actual upgrade it reports I have 60MB left on /boot and need 26MB for the kernel. I think next time around I will need to do fresh installs so I can resize my /boot. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: anacron broken after upgrade from 13 to 14 [Solved]
A new crontabs package was released that fixed this problem. crontabs-1.11-1.2010git.fc14.noarch Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
anacron broken after upgrade from 13 to 14
None of the daily or weekly jobs have run since upgrading to fedora 14. Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts). I am waiting to see if the daily/weekly jobs run after manually executing anacron by running /etc/cron.hourly/0anacron [linux0]# uname -r 2.6.35.6-48.fc14.x86_64 Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: anacron broken after upgrade from 13 to 14
/ None of the daily or weekly jobs have run since upgrading to fedora 14. // Jobs in /etc/cron.d are working (denyhosts,sa-update,lmsensor_charts). / I go to a lot of trouble to disable anacron, so I've had to discover how it is enabled in order to disable it. It starts with /etc/cron.d/0hourly which has the line that runs the anacron stuff via cron every hour. This is installed by package cronie. That is what makes the /etc/cron.hourly/0anacron script run, and that, in turn, examines the /etc/anacrontab file. (At least the last time I figured it out, that was the way it worked - it keeps changing :-). Thanks All the bits seem to be in place as you describe so it should be working. I downgraded crontabs back to crontabs.noarch 0:1.10-33.fc14 on one of the two machines. I am in the process of run diffs on the files to see what changed. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: anacron broken after upgrade from 13 to 14
After seeing this bug, I checked on my cron jobs and found they were not working either. After a bit of investigation I found the crontabs problem: https://bugzilla.redhat.com/show_bug.cgi?id=653132 Work around: Find any crontab that is using run-parts and make sure you add a trailing / to the directory name passed as an argument. (I think :-). Ya, I found this from the diffs of the old run-parts and new. I added the slash and am waiting to see if things work. OLD: for i in $(LC_ALL=C; echo $1/*[^~,]) ; do --- NEW: for i in $(LC_ALL=C; echo $1*[^~,]) ; do Thanks Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: Ganglia - gmetad segfaults after starting gmond
After upgrade to fedora 14 from 13 gmetad process segfaults when updating rrd graphs. Anybody seeing this problem ? [linux2 ~]# rpm -qa | grep ganglia ganglia-web-3.1.7-2.fc14.i686 ganglia-gmetad-3.1.7-2.fc14.i686 ganglia-3.1.7-2.fc14.i686 ganglia-gmond-3.1.7-2.fc14.i686 To get around this problem I compiled ganglia 3.1.7 from source. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Ganglia - gmetad segfaults after starting gmond
After upgrade to fedora 14 from 13 gmetad process segfaults when updating rrd graphs. Anybody seeing this problem ? [linux2 ~]# rpm -qa | grep ganglia ganglia-web-3.1.7-2.fc14.i686 ganglia-gmetad-3.1.7-2.fc14.i686 ganglia-3.1.7-2.fc14.i686 ganglia-gmond-3.1.7-2.fc14.i686 [linux2 ~]# rpm -qa | grep rrdtool rrdtool-1.3.8-8.fc14.i686 Working ganglia prior to upgrade. [linux2 ~]# grep ganglia /var/log/yum.log Feb 06 12:37:45 Installed: ganglia-3.1.2-4.fc12.i686 Feb 06 12:37:45 Installed: ganglia-gmetad-3.1.2-4.fc12.i686 Feb 06 12:37:47 Installed: ganglia-web-3.1.2-4.fc12.i686 Feb 06 13:39:38 Installed: ganglia-gmond-3.1.2-4.fc12.i686 [linux2 ~]# grep rrdtool /var/log/yum.log Feb 06 12:37:43 Installed: rrdtool-1.3.8-4.fc12.i686 Remove existing rrd's [linux2 ~]# rm -rf /var/lib/ganglia/rrds/* gmetad: debug 10 [linux2 ~]# service gmetad start Starting GANGLIA gmetad: Going to run as user ganglia Sources are ... Source: [Home, step 15] has 1 sources ip.xxx.xxx.xxx xml listening on port 8651 interactive xml listening on port 8652 Data thread 3029039984 is monitoring [Home] data source ip.xxx.xxx.xxx cleanup thread has been started data_thread() got no answer from any [Home] datasource data_thread() got no answer from any [Home] datasource data_thread() got no answer from any [Home] datasource [Home] is a 2.5 or later data stream hash_create size = 1024 hash-size is 1031 hash_create size = 50 hash-size is 53 hash_create size = 50 hash-size is 53 rrd_dontneed: Argument 'rrd_file' is NULL. /bin/bash: line 1: 1361 Segmentation fault /usr/sbin/gmetad [FAILED] Crashes shortly after starting gmond. dmesg [270478.078104] gmetad[1361]: segfault at c ip 0029ee96 sp bf8df050 error 4 in librrd.so.4.0.7[27d000+31000] from /var/log/messages: Nov 10 13:23:41 linux2 kernel: [270478.078104] gmetad[1361]: segfault at c ip 0029ee96 sp bf8df050 error 4 in librrd.so.4.0.7[27d000+31000] -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: Workspace switcher crashes at 20
The backtrace disagrees with you. It aborts due to an assertion that the workspace name isn't NULL. No indication of not enough memory or heavy memory usage when enabling 20 workspaces. I ran into this issue when increasing from 14 to 18 workspaces. You could switch between spaces with the mouse but as soon as you use ctl+alt+arrows metacity would crash with the assertion failure. I found a way to get around this by naming the workspaces. Currently I have 20 workspaces configured. Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
re: Xorg - High CPU - Desktop hung
Anybody seeing an issue with Desktop hangs with Xorg using 90% CPU. This started for me with the latest kernel. Aug 03 09:54:35 Installed: kernel-2.6.33.6-147.2.4.fc13.i686 Runs fine using previous kernel. (2.6.33.6-147.fc13.i686) Snip from Xorg log. [104476.705] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [104476.705] Backtrace: [104476.705] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80ddfac] [104476.706] 1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80d91b7] [104476.706] 2: /usr/bin/Xorg (xf86PostButtonEventP+0xcf) [0x80b535f] [104476.706] 3: /usr/bin/Xorg (xf86PostButtonEvent+0x6c) [0x80b540c] [104476.706] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x34a000+0x341b) [0x34d41b] [104476.706] 5: /usr/bin/Xorg (0x8048000+0x739e0) [0x80bb9e0] [104476.706] 6: /usr/bin/Xorg (0x8048000+0x10fd04) [0x8157d04] [104476.706] 7: (vdso) (__kernel_sigreturn+0x0) [0x292400] [104476.706] 8: (vdso) (__kernel_vsyscall+0x2) [0x292416] [104476.706] 9: /lib/libc.so.6 (ioctl+0x19) [0x8bd0b9] [104476.706] 10: /usr/lib/libdrm.so.2 (drmIoctl+0x2e) [0x4b55a7e] [104476.707] 11: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3c) [0x4b55e0c] [104476.707] 12: /usr/lib/libdrm_nouveau.so.1 (0x181000+0x2a9a) [0x183a9a] [104476.707] 13: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xf1) [0x183c91] [104476.707] 14: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x34) [0x183d64] [104476.707] 15: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x1b5000+0x3a36) [0x1b8a36] [104476.707] 16: /usr/lib/xorg/modules/libexa.so (0x3cc000+0x3521) [0x3cf521] [104476.707] 17: /usr/lib/xorg/modules/libexa.so (0x3cc000+0x66ad) [0x3d26ad] [104476.707] 18: /usr/lib/xorg/modules/libexa.so (0x3cc000+0xf7f5) [0x3db7f5] [104476.707] 19: /usr/lib/xorg/modules/libexa.so (0x3cc000+0xd37e) [0x3d937e] [104476.707] 20: /usr/bin/Xorg (0x8048000+0xc8d77) [0x8110d77] [104476.707] 21: /usr/bin/Xorg (CompositePicture+0x290) [0x81030e0] [104476.708] 22: /usr/bin/Xorg (0x8048000+0xc1fa5) [0x8109fa5] [104476.708] 23: /usr/bin/Xorg (0x8048000+0xbeb34) [0x8106b34] [104476.708] 24: /usr/bin/Xorg (0x8048000+0x50ab7) [0x8098ab7] [104476.708] 25: /usr/bin/Xorg (0x8048000+0x1a595) [0x8062595] [104476.708] 26: /lib/libc.so.6 (__libc_start_main+0xe6) [0x7fecc6] [104476.708] 27: /usr/bin/Xorg (0x8048000+0x1a181) [0x8062181] I have a record up time so far on this kernel (2.6.33.6-147.2.4.fc13.i686) of 21 hours. Currently I am running with the boot parameter nouveau.noaccel=1 based on information from the following Bugzilla entry. https://bugzilla.redhat.com/show_bug.cgi?id=596330 Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Xorg - High CPU - Desktop hung
Anybody seeing an issue with Desktop hangs with Xorg using 90% CPU. This started for me with the latest kernel. Aug 03 09:54:35 Installed: kernel-2.6.33.6-147.2.4.fc13.i686 Runs fine using previous kernel. (2.6.33.6-147.fc13.i686) Snip from Xorg log. [104476.705] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [104476.705] Backtrace: [104476.705] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80ddfac] [104476.706] 1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80d91b7] [104476.706] 2: /usr/bin/Xorg (xf86PostButtonEventP+0xcf) [0x80b535f] [104476.706] 3: /usr/bin/Xorg (xf86PostButtonEvent+0x6c) [0x80b540c] [104476.706] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x34a000+0x341b) [0x34d41b] [104476.706] 5: /usr/bin/Xorg (0x8048000+0x739e0) [0x80bb9e0] [104476.706] 6: /usr/bin/Xorg (0x8048000+0x10fd04) [0x8157d04] [104476.706] 7: (vdso) (__kernel_sigreturn+0x0) [0x292400] [104476.706] 8: (vdso) (__kernel_vsyscall+0x2) [0x292416] [104476.706] 9: /lib/libc.so.6 (ioctl+0x19) [0x8bd0b9] [104476.706] 10: /usr/lib/libdrm.so.2 (drmIoctl+0x2e) [0x4b55a7e] [104476.707] 11: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3c) [0x4b55e0c] [104476.707] 12: /usr/lib/libdrm_nouveau.so.1 (0x181000+0x2a9a) [0x183a9a] [104476.707] 13: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xf1) [0x183c91] [104476.707] 14: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x34) [0x183d64] [104476.707] 15: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x1b5000+0x3a36) [0x1b8a36] [104476.707] 16: /usr/lib/xorg/modules/libexa.so (0x3cc000+0x3521) [0x3cf521] [104476.707] 17: /usr/lib/xorg/modules/libexa.so (0x3cc000+0x66ad) [0x3d26ad] [104476.707] 18: /usr/lib/xorg/modules/libexa.so (0x3cc000+0xf7f5) [0x3db7f5] [104476.707] 19: /usr/lib/xorg/modules/libexa.so (0x3cc000+0xd37e) [0x3d937e] [104476.707] 20: /usr/bin/Xorg (0x8048000+0xc8d77) [0x8110d77] [104476.707] 21: /usr/bin/Xorg (CompositePicture+0x290) [0x81030e0] [104476.708] 22: /usr/bin/Xorg (0x8048000+0xc1fa5) [0x8109fa5] [104476.708] 23: /usr/bin/Xorg (0x8048000+0xbeb34) [0x8106b34] [104476.708] 24: /usr/bin/Xorg (0x8048000+0x50ab7) [0x8098ab7] [104476.708] 25: /usr/bin/Xorg (0x8048000+0x1a595) [0x8062595] [104476.708] 26: /lib/libc.so.6 (__libc_start_main+0xe6) [0x7fecc6] [104476.708] 27: /usr/bin/Xorg (0x8048000+0x1a181) [0x8062181] -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
re: Xorg - High CPU - Desktop hung
Since no one else is reporting this (at least not that I have seen), it is probably caused by the graphics chip driver used by Xorg. What is your graphics chip brand and model? lspci | grep VGA 01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200 64M] (rev a1) Using nouveau driver, no xorg.conf. Looks a lot like Bug 559791. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE:preupgrade 12 to 13 error
eed a little help to determine next step. After reboot from running preupgrade I get the following message. Error downloading kickstart file. Then I am being requested to modify the following parameter. ks=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/ks.cfg This machine is a fully updated fresh install of F12 with a 300mb /boot on mdraid. FROM GRUB: title Upgrade to Fedora 13 (Goddard) kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/ks.cfg stage2=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/install.img initrd /upgrade/initrd.img title Fedora (2.6.32.12-115.fc12.x86_64) root (hd0,1) kernel /vmlinuz-2.6.32.12-115.fc12.x86_64 ro root=/dev/mapper/vg_linux8-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us quiet rdblacklist=nouveau vga=791 elevator=noop initrd /initramfs-2.6.32.12-115.fc12.x86_64.img FROM FSTAB: # /etc/fstab # Created by anaconda on Mon Apr 5 20:18:40 2010 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/vg_linux8-lv_root / ext4 noatime,errors=remount-ro1 1 UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8 /boot ext4 noatime,errors=remount-ro1 2 /dev/mapper/vg_linux8-lv_swap swap swapdefaults 0 0 tmpfs /dev/shmtmpfs defaults,noatime,mode=1777 0 0 tmpfs /tmptmpfs defaults,noatime,mode=1777 0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults 0 0 proc/proc procdefaults 0 0 /dev/vg_linux8_1/lv_opt/optext4defaults 1 2 I am able to determine that the error is due to being unable to mount the drive. (/dev/d99009ca-09f4-4607-9176-c3a6f6863fa8) So I tried to use /dev/md126p2 but it is still unable to mount the drive to access the ks.cfg. I can see the above information using alt+f3 when I get to the error dialogue screen when trying to boot into the preupgrade kickstart. [aga...@linux0 ~]$ uname -r 2.6.32.12-115.fc12.x86_64 [aga...@linux0 ~]$ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_linux8-lv_root 68509224 7532824 57496236 12% / tmpfs 3059132 652 3058480 1% /dev/shm /dev/md126p2297485205636 76489 73% /boot tmpfs 3059132 2520 3056612 1% /tmp /dev/mapper/vg_linux8_1-lv_opt 72082768 51480996 16940156 76% /opt Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
RE: preupgrade 12 to 13 error
On Mon, Jun 07, 2010 at 16:22:49 +0300, Doron Bar Zeevdoronbr770 at gmail.com https://admin.fedoraproject.org/mailman/listinfo/users wrote: / On Mon, Jun 7, 2010 at 16:14, Alan J. Gagnealanjgagne at gmail.com https://admin.fedoraproject.org/mailman/listinfo/users wrote: // // // //This machine is a fully updated fresh install of F12 with a 300mb /boot on //mdraid. // // // // I think that /boot must not be on a raid, which may be the problem. / Raid 1 is OK. I am actually running raid 0 (BIOS RAID) using two 80GB ssd drives split into three partitions. (Win7 on md126p1 and F12 on md126p2 - /boot,md126p3 LVM for / and swap) Alan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
{Disarmed} RE: preupgrade 12 to 13 error
On Mon, 2010-06-07 at 16:52 +0100, Bryn M. Reeves wrote: / On 06/07/2010 04:43 PM, Craig White wrote: //BIOS RAID sounds suspiciously like fake RAID which meant that you had to //load a specific device driver/kernel module just to get Fedora 12 //installed and that specific driver is not included in the reboot process //of preupgrade so it won't work. // // That's not quite true. Most of the proprietary BIOS RAID (aka // ata-RAID, fake RAID etc.) formats have been supported for quite a long // time now by the dmraid project: // // http://people.redhat.com/heinzm/sw/dmraid/ // // Some of the formats (as is the case with Intel ISW on F13) are now using // MD RAID but it's been quite a while since you had to use non-standard // proprietary drivers or kernel modules to use these things. / good to know - mostly I use Fedora for desktop and RHEL or CentOS for servers so I hadn't seen the change but I am generally very careful about which RAID controller I pick for servers. Craig Yes this is Intel fake raid with fedora using mdraid to support it. No special drivers or kernels needed. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
preupgrade 12 to 13 error
Need a little help to determine next step. After reboot from running preupgrade I get the following message. Error downloading kickstart file. Then I am being requested to modify the following parameter. ks=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/ks.cfg This machine is a fully updated fresh install of F12 with a 300mb /boot on mdraid. FROM GRUB: title Upgrade to Fedora 13 (Goddard) kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade ks=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/ks.cfg stage2=hd:UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8:/upgrade/install.img initrd /upgrade/initrd.img title Fedora (2.6.32.12-115.fc12.x86_64) root (hd0,1) kernel /vmlinuz-2.6.32.12-115.fc12.x86_64 ro root=/dev/mapper/vg_linux8-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us quiet rdblacklist=nouveau vga=791 elevator=noop initrd /initramfs-2.6.32.12-115.fc12.x86_64.img FROM FSTAB: # /etc/fstab # Created by anaconda on Mon Apr 5 20:18:40 2010 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/vg_linux8-lv_root / ext4 noatime,errors=remount-ro1 1 UUID=d99009ca-09f4-4607-9176-c3a6f6863fa8 /boot ext4 noatime,errors=remount-ro1 2 /dev/mapper/vg_linux8-lv_swap swap swap defaults 0 0 tmpfs /dev/shmtmpfs defaults,noatime,mode=1777 0 0 tmpfs /tmptmpfs defaults,noatime,mode=1777 0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults 0 0 proc/proc proc defaults 0 0 /dev/vg_linux8_1/lv_opt/optext4defaults 1 2 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
