users September 2010

users@lists.fedoraproject.org

300 participants
353 discussions

How to override /media as a mount point?
by Neil Bird 02 Sep '10

02 Sep '10

I have a new USB drive I've set up to replace some old internal drives, and I'd like to have it automount it's partitions to where the internal drives were mounted, instead of /media/fslabel. I have to presume it's be some sort of udev config., but I can't for the life of me even see anything *choosing* /media, so I can only guess that it's hard-coded somewhere. lshal does shopw a mount_point field for them, but given that HAL is being deprecated I suspect that's a dead-end, even if it isn't read-only. Is it possible to override, on a per FS/device basis, where devices are auto-mounted? In fact, what is is that even mounts things like that nowadays (I'm on F12), since gnome-mount et al. seems to have gone. For now, I've added the partitions to /etc/fstab, but of course I then have to manually mount the things if the drive is not present on power up. -- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit

2 2

dmesg garbage
by Ankur Sinha 02 Sep '10

02 Sep '10

hi, I need to look at dmesg output for some work. However, my dmesg is filled with garbage: .... [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0306480, nr=0x80, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0xc0406481, nr=0x81, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086409, nr=0x09, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40086482, nr=0x82, dev 0xe200, auth=1 [drm:drm_ioctl], pid=1735, cmd=0x40046483, nr=0x83, dev 0xe200, auth=1 ..... ... .... I checked up what pid 1735 is: [root@070905042 ~]# ps aux | grep 1735 root 1735 6.0 1.3 119464 34240 tty1 Ss+ Sep01 108:16 /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-q4z68C/database -nolisten tcp vt1 Can someone please tell me how to disable this logging so I can make use of dmesg? BTW, I've dont dmesg -c a lot of times and this garbage still turns up :| -- Thanks! Regards, Ankur https://fedoraproject.org/wiki/User:Ankursinha "FranciscoD"

1 0

About ksplice
by Renich Bon Ciric 02 Sep '10

02 Sep '10

Hello, I know that uptrack is providing it's package for Fedora 13... but, also, I know Fedora provides fedora-ksplice. Any idea of how to use the former? It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/

1 0

error message during boot
by L 01 Sep '10

01 Sep '10

hi, my system is F13 2.6.34.6-47.fc13.i686. During boot, it generates many lines of errors they are all related to /etc/udev/rules.d/51-hso-udev.rules. I have this file attached too. It doesn't hurt but annoy. Is it safe to delete this rule file? thanks Y Welcome to Fedora Press 'I' to enter interactive startup. Starting udev: udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:73 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:76 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:77 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:78 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:79 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:80 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:81 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:82 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:83 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:84 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:85 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:86 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:87 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:88 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:89 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:90 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:91 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:92 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:93 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:94 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:95 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:96 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:97 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:98 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:99 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:100 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:101 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:105 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:106 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:107 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:108 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:109 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:110 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:111 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:112 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:113 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:114 udevd[435]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-hso-udev.rules:115 udevd[435]: NAME="%k" is superfluous and breaks kernel supplied names, please remove it from /etc/udev/rules.d/51-hso-udev.rules:124 [ OK ] Setting hostname zhang: [ OK ] Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems sys: clean, 306942/730512 files, 2138183/2893700 blocks data: clean, 41637/5537792 files, 18505569/22121497 blocks (check in 2 mounts) home: clean, 27005/3383296 files, 5256844/13524721 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] Enabling /etc/fstab swaps: [ OK ] Entering non-interactive startup iptables: Applying firewall rules: [ OK ] iptables: Loading additional modules: nf_conntrack_netbios_[ OK ] Starting portreserve: [ OK ] Starting system logger: [ OK ] WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Enabling ondemand cpu frequency scaling: -- Linux Toys http://linuxishbell.wordpress.com/

2 1

Download confirmation now not prompts me!
by Parshwa Murdia 01 Sep '10

01 Sep '10

hi, In a sudden changing manner, now if I try to update the system, using the command, [fedorax@localhost ~]$ su - Password: [root@localhost ~]# yum update It doesn't prompt me to type in 'y' or 'n' if some downloadable update is there unlike earlier when I used to type in 'yes' to download a particular package of some size and update the system. Not only in this command but in some other commands also, I have the same thing repeating when I am not being prompted for tying in 'y' or 'n' for the confirmation of download. Why could this happen all of a sudden? -- Regards, Parshwa Murdia

4 11

CD/DVD
by Patrick Dupre 01 Sep '10

01 Sep '10

Hello, On my new install of Fedora 13, I do not have access to the internal CD/DVD reader (the one that I used to install the distro) ! I even does not show up in the media list. What should I install ? Thank. -- --- ========================================================================== Patrick DUPRÉ | | Department of Chemistry | | Phone: (44)-(0)-1904-434384 The University of York | | Fax: (44)-(0)-1904-432516 Heslington | | York YO10 5DD United Kingdom | | email: pd520(a)york.ac.uk ==========================================================================

2 7

Fedora 13 Evolution and exchange
by Chris Kottaridis 01 Sep '10

01 Sep '10

I was running Ubuntu 9.10 and using evolution with a microsoft exchange server and it was working Ok with mail and calendar and GAL. For unrelated reasons I switched to Fedora Core 13, but brought the same home directory for this user into the Fedora Core 13. Mail seems to be working OK, but the calendar and GAL don't seem to work right. The evolution-dataserver and evolution-exchange crash regularly even though mail still seems to go back and forth. I am not sure what the service is called but the red "police light" icon pops up on the top panel and has a crash dump output of some sort. I have not submitted any of those crash dumps. I have installed: evolution-2.30.3-1.fc13 (x86_64) evolution-data-server-2.30.3-1fc13 (x86_64) evolution-exchange-2.30.3-1.fc13 Is this a known issue that has a known problem ? Is it possible that the previous version of Ubuntu had some file format's that are confusing Fedora Core 13 version ? Any hints or suggestions appreciated. Thanks Chris kottaridis

3 6

F13 LXDE spin fails to even boot on 64-bit dual quadcore
by Ranjan Maitra 01 Sep '10

01 Sep '10

Hi, I have a strange problem. I downloaded the F13 LXDE spin and installed it on a dual-core IBM T61 Thinkpad laptop. It came up ok and I was able to install to hard drive. Next, thinking this would be a 10-minute breeze, I went to a Dell Precision T7400 dual quad-core Xeon Processor X5482 and asked the machine to boot from a live CD. Everything was going as advertised, except that after it goes into grub, the screen goes black and there are some error messages about checksum. (Btw, the Verify and Boot option does nothing.) It then switches off, reboots and goes through the same process. So, I figured that maybe my CD got damaged in the laptop install. So, I burnt a new one and tried my luck on this new one. Same problem. Btw, the specific error message is: [drm: drm_ehid_block_valid] *ERROR* EDID checksum is invalid remainder is 49 [drm: drm_ehid_block_valid] *ERROR* Raw EDID. I wondered if the CD-ROM was bad so put it in the CD-RW. Same problem. The graphics card is a ATI FireGL V3600. Any suggestions? Helpful advice? Best wishes, Ranjan

1 0

GNOME Terminal questions
by Alex 01 Sep '10

01 Sep '10

Hi, I've done a bit of searching for answers to my questions, but haven't really found anything current or relevant to my issue. I have a few usage questions about the default terminal application included with FC13. Perhaps I should instead use a different terminal application for my purposes? - How can I disable the automatic conversion of email address and URLs to hyperlinks? - How can I make the mouse scroll wheel be used for scrolling back through the terminal buffer, rather than acting as an up arrow? - How can I change the terminal bell sound? - It appears that sometimes when I resize the terminal, it is not acknowledged by the remote computer when connected via ssh through a screen session. How do I configure my terminal session so that information is transmitted through to the remote session? Would it pertain to PROMPT_COMMAND and PS1? - How can I configure the terminal so copy is performed by simply highlighting the text with the mouse, and paste is done through shift-insert? I understand the default is to press the mouse scroll wheel, but I would prefer the method I've described, and the scroll wheel on my mouse apparently doesn't always properly work -- sometimes it simply does not paste, and I have to do it a few times. I don't understand why, because it's a brand new mouse (MS Wireless 5000). - I found a link to copy and paste between a terminal and Windows running in a VM, but isn't there a better way than installing and running a separate program on both Windows and Linux for this purpose? http://www.linux-kvm.com/content/copy-and-paste-between-vm-and-host Ideas greatly appreciated. Thanks, Alex

2 1

Fedora lists?
by David 01 Sep '10

01 Sep '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is required to petition for a new Fedora list? Who to ask and how? I ask because I would like to see a list for general FUD, false statements, and Bull$hit so that when those types of subjects appear on the help lists those users can be directed there and leave the lists for their intended purposes. It is a PIMA to have to edit my /null/void daily. :-) - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMfml1AAoJEBm6pib1zR1jxwIQAK7qCX/F2JPRA9W7iivR1Vc3 PqiUo8BnMiDmSmGFwZUO/my0r3V+HrSgdhDQKSGeuDG8eMddGWAZl7aI+d4s4h4o oWZ5xbS7ZHaWqlYcod0sEkopXV0Wrb6FlyjfAdPzCY6WjY00srAg/T8N0pj5rnEj bq/jW3rXEfwIzWLokDYxEFXqDFIkwYMTH0tSBJk3C8fDvxJ0S8Deu4hsF+03cBMx ju5TRXD82h83/ECgmv5pe6ZNPmdA+5bZM3wdS5Ub3+d535VHXQ8wbEAfAzQyOPhL 0wd07L5ajelw6SxKj3jBoy9LZBhijHk1Yq1EKJQklbsaMSAELl2/MLL5Q3UIG5az hU7P+oP5DHmDPafTg0TkM4oNxgp6FzfYPpt/ZQQ/p1ZmOu1ofjMjwaQiqnukBTfj DugRD2ii6qb+kvMp6Z2iNNULH8mSfUJv2hBq5tkXFLFC8oim+CuYsSOSKTPm7In0 CB6kHhe2AVBBlMi65Or/QL093IbmTSy9FnfGrAPUbUZjQAGD6kgZV4mN4GGT/yhu ot3VpVJIe6DTZW8nQW8qOMTpkfvIKmzg6FOeJknVOfPmoCGkhRKP6w7UjGx2jjy/ YhAwf6t5NIq00Ajjk/P4X0z1KOGvxxypZyp4olpVrz3HiSVxMjvP1UXqFgfAia9h IkUyvqSVIJkQb84YAhjw =sMtL -----END PGP SIGNATURE-----

2 2

Jump to page: