users March 2012

users@lists.fedoraproject.org

247 participants
303 discussions

Anyone got three monitors working?
by thomas cameron 04 Jun '12

04 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Howdy All - I have Gigabyte EP43-UD3L motherboard with a single PCI Express 2.0 x16 slot. It currently has a decent NVidia card - a GeForce 7300 GT. I've got two monitors attached, one via the VGA port and one via the digital video port. It works well, I get accelerated X and wobbly windows and all that silliness. Guilty pleasure: I like eye candy. I'd *really* love to do triple head - the monitor in front of me for my main work, and the two side screens for supporting stuff. I am wondering, since my motherboard has a four PCI Express x1 ports and I see PCI Express x1 video cards for decent prices, if I can either replace my single card with two identical two-port X1 cards, or just add a single X1 video card to what I already have and get triple head. Has anyone done this? Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iEYEARECAAYFAk7SknEACgkQmzle50YHwaCHXgCgh5OPtqXsUZnn5F6hnuTvJYH6 0Q4An29A0m4znOWxWIgni3wv/l8zCAyr =nFLx -----END PGP SIGNATURE-----

9 19

The death of Hibernate?
by Geoffrey Leach 28 May '12

28 May '12

It appears that among some kernel maintainers there's an opinion that the hibernate (suspend to disk) capability is of insufficient interest to users to justify the difficulty of maintenance. See https://bugzilla.redhat.com/show_bug.cgi?id=781749 Will anyone for whom hibernate is important please add a note to the bug report, so that the maintainers will know that their efforts are much appreciated? Thanks.

27 82

F16 failure to completely boot - hangs at 'Started Display Manager'
by Gregory P. Ennis 09 May '12

09 May '12

Everyone, Help!!!! I have a laptop with F16 that now refuses to boot into the logon screen this morning. The boot sequence pauses at Starting Display Manager..... Started Display Manger There is one error message displayed before the above line items: Failed to start LSB: Builds and install new kmods from akmod packages See 'systemctl status akmods.service' for details When systemctl.... is executed the results are : akmods.service - LSB: Builds and install new kmods from akmod packages Loaded: loaded (/etc/rc.d/init.d/akmods) Active: failed since Sat, 10 Mar 2012 20:05:39 -0600; 16h ago Process: 1022 ExecStart=/etc/rc.d/init.d/akmods start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/akmods.service If any of you can give me a starting place to debug this I would appreciate your efforts. Thank you, Greg Ennis P.S. Yesterday there were some yum updates that occurred : Mar 10 07:37:08 Updated: 1:libreoffice-ure-3.4.5.2-8.fc16.x86_64 Mar 10 07:37:21 Updated: wine-core-1.4-1.fc16.x86_64 Mar 10 07:37:22 Updated: wine-common-1.4-1.fc16.noarch Mar 10 07:37:23 Updated: wine-cms-1.4-1.fc16.x86_64 Mar 10 07:37:24 Updated: wine-wow-1.4-1.fc16.x86_64 Mar 10 07:37:24 Updated: wine-alsa-1.4-1.fc16.x86_64 Mar 10 07:37:24 Updated: wine-pulseaudio-1.4-1.fc16.x86_64 Mar 10 07:37:25 Updated: wine-ldap-1.4-1.fc16.x86_64 Mar 10 07:37:26 Updated: wine-twain-1.4-1.fc16.x86_64 Mar 10 07:37:26 Updated: wine-openal-1.4-1.fc16.x86_64 Mar 10 07:37:27 Updated: wine-capi-1.4-1.fc16.x86_64 Mar 10 07:37:29 Updated: 1:kde-plasma-networkmanagement-libs-0.9.0-1.fc16.x86_64 Mar 10 07:37:31 Updated: 1:kde-plasma-networkmanagement-0.9.0-1.fc16.x86_64 Mar 10 07:37:34 Updated: 1:libreoffice-opensymbol-fonts-3.4.5.2-8.fc16.noarch Mar 10 07:37:34 Updated: wine-small-fonts-1.4-1.fc16.noarch Mar 10 07:37:37 Installed: system-config-keyboard-base-1.3.1-6.fc16.x86_64 Mar 10 07:37:37 Updated: wine-system-fonts-1.4-1.fc16.noarch Mar 10 07:37:38 Updated: wine-symbol-fonts-1.4-1.fc16.noarch Mar 10 07:37:38 Updated: wine-courier-fonts-1.4-1.fc16.noarch Mar 10 07:37:39 Updated: wine-marlett-fonts-1.4-1.fc16.noarch Mar 10 07:37:39 Updated: 1:autocorr-en-3.4.5.2-8.fc16.noarch Mar 10 07:37:41 Updated: graphite2-1.1.1-1.fc16.x86_64 Mar 10 07:38:15 Updated: 1:libreoffice-core-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:20 Updated: 1:libreoffice-presenter-screen-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:22 Updated: 1:libreoffice-impress-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:23 Updated: 1:libreoffice-graphicfilter-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:24 Updated: 1:libreoffice-draw-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:25 Updated: 1:libreoffice-pdfimport-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:25 Updated: wine-ms-sans-serif-fonts-1.4-1.fc16.noarch Mar 10 07:38:26 Updated: wine-tahoma-fonts-1.4-1.fc16.noarch Mar 10 07:38:26 Updated: wine-fonts-1.4-1.fc16.noarch Mar 10 07:38:27 Updated: wine-systemd-1.4-1.fc16.noarch Mar 10 07:38:28 Updated: 1:libreoffice-math-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:28 Updated: 1:libreoffice-kde-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:31 Updated: 1:libreoffice-calc-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:32 Updated: 1:libreoffice-langpack-en-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:32 Updated: 1:libreoffice-xsltfilter-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:35 Updated: 1:libreoffice-writer-3.4.5.2-8.fc16.x86_64 Mar 10 07:38:53 Updated: system-config-keyboard-1.3.1-6.fc16.x86_64 Mar 10 07:38:53 Updated: 1:kde-plasma-networkmanagement-vpnc-0.9.0-1.fc16.x86_64 Mar 10 07:38:54 Updated: 1:kde-plasma-networkmanagement-openvpn-0.9.0-1.fc16.x86_64 Mar 10 07:38:54 Updated: 1:kde-plasma-networkmanagement-pptp-0.9.0-1.fc16.x86_64 Mar 10 07:39:00 Updated: wine-devel-1.4-1.fc16.x86_64 Mar 10 07:39:00 Updated: wine-sysvinit-1.4-1.fc16.noarch Mar 10 07:39:03 Updated: 1:dovecot-2.0.18-1.fc16.x86_64 Mar 10 07:39:04 Updated: pycairo-1.8.10-4.fc16.x86_64 Mar 10 07:39:06 Updated: 1:php-pear-1.9.4-5.fc16.noarch Mar 10 07:39:08 Updated: icedtea-web-1.2-1.fc16.x86_64 Mar 10 07:39:08 Updated: perl-HTTP-Message-6.03-1.fc16.noarch Mar 10 07:39:09 Updated: openjpeg-libs-1.4-12.fc16.x86_64 Mar 10 07:39:14 Updated: tzdata-2011n-4.fc16.noarch Mar 10 07:39:17 Updated: xiphos-3.1.5-1.fc16.x86_64 Mar 10 07:39:19 Updated: tzdata-java-2011n-4.fc16.noarch Mar 10 07:39:28 Updated: wine-core-1.4-1.fc16.i686 Mar 10 07:39:29 Updated: wine-desktop-1.4-1.fc16.noarch Mar 10 07:39:29 Updated: wine-capi-1.4-1.fc16.i686 Mar 10 07:39:30 Updated: wine-cms-1.4-1.fc16.i686 Mar 10 07:39:31 Updated: wine-alsa-1.4-1.fc16.i686 Mar 10 07:39:32 Updated: wine-pulseaudio-1.4-1.fc16.i686 Mar 10 07:39:34 Updated: wine-openal-1.4-1.fc16.i686 Mar 10 07:39:34 Updated: wine-twain-1.4-1.fc16.i686 Mar 10 07:39:35 Updated: wine-ldap-1.4-1.fc16.i686 Mar 10 07:39:36 Updated: wine-1.4-1.fc16.x86_64

3 6

Sata device in a USB docking station problems.
by George R Goffe 08 May '12

08 May '12

Hi, I'm having a bit of a problem with some SATA drives in docking stations connected to USB ports. The problem seems to be unrelated to heavy I/O and occurs randomly. Once, without the drive even being mounted. Here's a sample of output from /var/log/messages: Mar 12 20:54:07 joker kernel: [396376.705286] usb 2-1.3.1: reset high-speed USB device number 8 using ehci_hcd Mar 12 20:54:15 joker kernel: [396384.983920] sd 6:0:0:0: Device offlined - not ready after error recovery Mar 12 20:54:15 joker kernel: [396384.983972] sd 6:0:0:0: [sdb] Unhandled error code Mar 12 20:54:15 joker kernel: [396384.983978] sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Mar 12 20:54:15 joker kernel: [396384.983988] sd 6:0:0:0: [sdb] CDB: Read(10): 28 00 2a 8d e8 58 00 00 08 00 Mar 12 20:54:15 joker kernel: [396384.984016] end_request: I/O error, dev sdb, sector 713943128 Mar 12 20:54:15 joker kernel: [396384.984268] sd 6:0:0:0: rejecting I/O to offline device Mar 12 20:54:15 joker kernel: [396384.984497] usb 2-1.3.1: USB disconnect, device number 8 Mar 12 20:54:15 joker kernel: [396385.052205] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.053693] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.053745] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.058106] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.058144] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27041406: block 108005895: comm ls: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.257785] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.257841] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.260088] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.260144] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.266710] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.266766] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039895: block 108005801: comm ls: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.319579] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.319636] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.321703] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.321758] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm differ: unable to read itable block Mar 12 20:54:15 joker kernel: [396385.330217] EXT4-fs (sdb1): previous I/O error to superblock detected Mar 12 20:54:15 joker kernel: [396385.330299] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #27039963: block 108005805: comm ls: unable to read itable block Mar 12 20:54:17 joker kernel: [396386.455141] usb 2-1.3.1: new high-speed USB device number 9 using ehci_hcd Mar 12 20:54:17 joker kernel: [396386.542050] usb 2-1.3.1: New USB device found, idVendor=152d, idProduct=2336 Mar 12 20:54:17 joker kernel: [396386.542054] usb 2-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Mar 12 20:54:17 joker kernel: [396386.542056] usb 2-1.3.1: Product: JM20336 SATA, USB Combo Mar 12 20:54:17 joker kernel: [396386.542058] usb 2-1.3.1: Manufacturer: JMicron Mar 12 20:54:17 joker kernel: [396386.542059] usb 2-1.3.1: SerialNumber: 61B888888888 Mar 12 20:54:17 joker kernel: [396386.544168] scsi7 : usb-storage 2-1.3.1:1.0 Mar 12 20:54:17 joker mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1" Mar 12 20:54:17 joker mtp-probe: bus: 2, device: 9 was not an MTP device Mar 12 20:54:18 joker kernel: [396387.546454] scsi 7:0:0:0: Direct-Access ST975042 0AS PQ: 0 ANSI: 2 CCS Mar 12 20:54:18 joker kernel: [396387.551247] sd 7:0:0:0: Attached scsi generic sg2 type 0 Mar 12 20:54:18 joker kernel: [396387.551433] sd 7:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB) Mar 12 20:54:18 joker kernel: [396387.552554] sd 7:0:0:0: [sdc] Write Protect is off Mar 12 20:54:18 joker kernel: [396387.553693] sd 7:0:0:0: [sdc] Asking for cache data failed Mar 12 20:54:18 joker kernel: [396387.553697] sd 7:0:0:0: [sdc] Assuming drive cache: write through Mar 12 20:54:18 joker kernel: [396387.557552] sd 7:0:0:0: [sdc] Asking for cache data failed Mar 12 20:54:18 joker kernel: [396387.557556] sd 7:0:0:0: [sdc] Assuming drive cache: write through Mar 12 20:54:18 joker kernel: [396387.605119] sdc: sdc1 Mar 12 20:54:18 joker kernel: [396387.609143] sd 7:0:0:0: [sdc] Asking for cache data failed Mar 12 20:54:18 joker kernel: [396387.609146] sd 7:0:0:0: [sdc] Assuming drive cache: write through Mar 12 20:54:18 joker kernel: [396387.609153] sd 7:0:0:0: [sdc] Attached SCSI disk Mar 12 20:54:18 joker ata_id[7747]: HDIO_GET_IDENTITY failed for '/dev/sdc': Invalid argument Mar 12 20:54:20 joker kernel: [396389.683950] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm differ: reading directory lblock 0 Mar 12 21:01:52 joker kernel: [396841.458607] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3649: inode #24248321: block 96993312: comm ls: unable to read itable block Mar 12 21:01:52 joker kernel: [396841.458614] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4467: IO failure Mar 12 21:01:58 joker kernel: [396847.074007] Aborting journal on device sdb1-8. Mar 12 21:01:58 joker kernel: [396847.074020] Buffer I/O error on device sdb1, logical block 91258880 Mar 12 21:01:58 joker kernel: [396847.074021] lost page write due to I/O error on sdb1 Mar 12 21:01:58 joker kernel: [396847.074027] JBD2: I/O error detected when updating journal superblock for sdb1-8. Mar 12 21:02:01 joker kernel: [396850.173099] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm bash: reading directory lblock 0 Mar 12 21:05:09 joker kernel: [397037.916573] EXT4-fs error (device sdb1): ext4_put_super:818: Couldn't clean up the journal Mar 12 21:05:09 joker kernel: [397037.916578] EXT4-fs (sdb1): Remounting filesystem read-only I also have made a couple of bug reports which appear to be getting no attention. [Bug 802607] New: reset high-speed USB device (sata drive and USB connection) I've started loosing data now. Does anyone have any clues? The system is running FC 16 x86_64 fully up to date. The problem has persisted across several kernels including the current kernel. Any help would be greatly appreciated. Thanks, George... "It's not what you know that hurts you, It's what you know that ain't so." Will Rogers... Will would say, "STIFF THE FED"!!!

4 4

is fvwm orphaned in F17?
by Ranjan Maitra 08 May '12

08 May '12

Hi, I have filed a couple of BZ requests over the past year suggesting a move to the stable branch of fvwm (even second digit: 2.6.4) instead of the developmental (odd second digit: 2.5.30) and never got even an acknowledgment. I noticed also that fvwm is not in rawhide? Does this mean that this is (being) orphaned? Many thanks and best wishes, Ranjan

4 7

oovoo.com
by Gregory P. Ennis 25 Apr '12

25 Apr '12

Dear List, I was asked to assist connecting a Fedora linux system for video conferencing with oovoo.com. It is apparent that they support Mac and Windows. Does anyone have any experience in using the Mac installation for oovoo for Fedora? Can anyone make recommendations for connections that allow video conferencing with Fedora. Thanks much -- Greg Ennis PoMec Corporation www.PoMec.net

4 8

Firewall disabled; yet "connection refused"
by Braden McDaniel 24 Apr '12

24 Apr '12

I'm trying to set up dovecot on a fresh installation of Fedora 16. This is an obvious problem: $ telnet rail 143 Trying 10.0.0.21... telnet: connect to address 10.0.0.21: Connection refused localhost works: $ telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. After first trying to permit traffic on port 143 in the firewall configuration, I've now disabled it altogether: $ systemctl status iptables.service iptables.service - IPv4 firewall with iptables Loaded: loaded (/lib/systemd/system/iptables.service; disabled) Active: inactive (dead) start condition failed at Sat, 27 Mar 1999 03:25:13 -0500; 13 years and 0 months ago CGroup: name=systemd:/system/iptables.service $ systemctl status ip6tables.service ip6tables.service - IPv6 firewall with ip6tables Loaded: loaded (/lib/systemd/system/ip6tables.service; disabled) Active: inactive (dead) start condition failed at Sat, 27 Mar 1999 03:25:13 -0500; 13 years and 0 months ago CGroup: name=systemd:/system/ip6tables.service ? yet I still get "connection refused" as above. If not the firewall, what's the culprit here? -- Braden McDaniel e-mail: <braden(a)endoframe.com> <http://endoframe.com> Jabber: <braden(a)jabber.org>

5 11

External eSATA drive not recognized on 2nd power up
by Patrick Lists 14 Apr '12

14 Apr '12

Hi, I have an up-to-date F16 x86_64 box with 2 eSATA ports on the back powered by a JMicron JMB362 chip. When I attach an external SATA drive to the eSATA port and power up the drive it is recognized fine. But when I power down that drive, wait 2 minutes, and power it up again the drive is no longer recognized. Also there are no messages related to the 2nd power up in /var/log/messages. All SATA controllers are set to AHCI in the BIOS. No idea where to go from here. Anyone have any suggestions how I can fix this? Thanks and regards, Patrick

4 7

.bash_history in F15/16 randomly truncated/incomplete/damaged
by Franta Hanzlík 10 Apr '12

10 Apr '12

I'm accustomed have longer bash history - usually my HISTSIZE=10000. Never from Redhat 4 epoch was problems with this, but now at F15 and F16 I in several cases I found weirdness, when my commands are missing in history, in one case I had .bash_history completely empty. IMO it is problem in newer bash versions, but yet more I suspect when it may be any cripled systemd behavior at init 0/6 (sorry, i want say poweroff.target/reboot.target ;), whether systemd (in order to halt/reboot computer several microseconds faster) kill bash before it is able save their stuff. Have You met someone with this problem? Any idea how diagnose it? Thanks, Franta

8 15

EasyCAP driver.
by Erik P. Olsen 09 Apr '12

09 Apr '12

I've boroughed an easycap device in order to perform VHS2DVD conversion of my old VHS-tapes. I am therefore seeking a driver for Fedora 14 or 16. Does anybody have experience with this device? [erik@epohost ~]$ lsusb Bus 001 Device 009: ID 05e1:0408 Syntek Semiconductor Co., Ltd STK1160 Video Capture Device -- Erik

3 4

Jump to page: