Discuss

discuss@lists.centos.org

34753 discussions

Supsend/hibernate on Samsung NC10
by Mathieu Baudier 20 Dec '09

20 Dec '09

Hi, I cannot have suspend and hibernate working on a Samsung NC10 (netbook) running CentOS 5.4 i386. When I try suspending/hibernating the screen becomes black (with a few logs, like "shrinking memory" for hibernate) and then the computer hangs and I have to force a shutdown with the power button. This wiki page seems to say that it should work out of the box: http://wiki.centos.org/HowTos/Laptops/Samsung/NC10 I tried to add the kernel arguments described here, to no avail: http://lists.centos.org/pipermail/centos/2007-June/040633.html Anyhow the problems doesn't seem to be the resume but rather getting into the suspended/hibernated state. When I log after a failed attempt, GNOME shows a popup saying that apparently we failed to recover from a suspend/hibernate state and that this may be a driver problem. A few more information about my settings which may be useful: - the root filesystem is installed on an LVM - I use the NetworkManager and not the network service - I disabled bluetooth (in order to remove all unused devices that may impact this problem) - [mbaudier@localhost ~]$ lshal | grep suspen org.freedesktop.Hal.Device.SystemPowerManagement.method_execpaths = {'hal-system-power-suspend', 'hal-system-power-suspend-clear-error', 'hal-system-power-hibernate', 'hal-system-power-hibernate-clear-error', 'hal-system-power-shutdown', 'hal-system-power-reboot', 'hal-system-power-set-power-save'} (string list) power_management.can_suspend_to_disk = true (bool) power_management.can_suspend_to_ram = true (bool) power_management.can_suspend = true (bool) Thanks in advance if somebody can tell me how I can analyse further / solve this. Cheers, Mathieu

2 1

mdadm help
by James Bensley 20 Dec '09

20 Dec '09

Hey List, So I had a 4 drive software RAID 5 set up consisting of /dev/sdb1, /dev/sdc1, /dev/sdd1 and /dev/sde1. I reinstalled my OS and after the reinstall I made the mistake of re-assembling the array incorrectly by typing "sudo mdadm --assemble /dev/md0 /dev/sdb /dev/sdc /dev/sdd /dev/sde" in a moment of stupidity. Obviously this didn't work and the array wouldn't mount and after a short period I realised my mistake and re-issuing the same command but specifying each drive partition (sdb1, sdc1 etc) instead of the drives (sdb, sdc etc) meant the raid would assembled and mount just dandy. My problem is that when I issue "sudo mdadm -E --scan" I get the following results: ARRAY /dev/md0 level=raid5 num-devices=4 UUID=fde94900:3f3f3bf6:e368bf24:bd0fce41 ARRAY /dev/md0 level=raid5 num-devices=4 UUID=3a2f1919:52f73b40:e368bf24:bd0fce41 These entries aren't in mdadm.conf but mdadm keeps picking up my first mistake and tries to make a raid out of my four drives and not the four partitions (the bottom line is the four UUIDs for the partitions on each drive, the top line is the four UUID for the drives). So now every time I restart the machine, the array isn't mounted because mdadm (I guess) doesn't know what to do as it has two sets of devices defined as /dev/md0. I can issues "sudo mdadm --stop /dev/md0" and "sudo mdadm --remove /dev/md0" and then re-assemble specifying the four partitions and carry on as normal but I can't work out how to tell mdadm to "forget" about the the top line of those results, if that makes any sence? I have removed the entries from fstab and from mdadm.conf so when I boot up the machine doesn't automatically try and mount the incorrect device but I still can't remove the top line from the results of "mdadm -E --scan" no matter what I do. I have rebooted and issued the command "sudo mdadm --assemble /dev/md1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1" and I can mount my array as normal but I was hoping that now there wouldn't be a clash in the results of "sudo mdadm -E --scan" (which there isn't, the second lines says "/dev/md1"), meaning that after a reboot the array would mount properly but that isn't the case. It is still trying to assemble the top line. Does anyone have any idea how I can rectify this? Thanks for reading. -- Regards, James ;) Ted Turner - "Sports is like a war without the killing." - http://www.brainyquote.com/quotes/authors/t/ted_turner.html

1 1

Removable drive configuration
by Bob McConnell 20 Dec '09

20 Dec '09

I have a box running CentOS 5.3 with two Dataport removable drive bays installed on the second IDE interface (/dev/hdc and hdd). I want to configure it so I can plug in and mount various drives at different times, including different size drives. So far it will only recognize the first drive I plug in, and only if I boot the box after inserting the drive. Is there any way to set it up so I can mount different size drives freely without having to reboot each time? Thank you, Bob McConnell N2SPP

3 2

Re: [CentOS] Optimizing CentOS for gigabit firewall
by sadas sadas 20 Dec '09

20 Dec '09

The syntax is not a problem. The problem is in the performance. I suppose that if I configure OpenBSD to process the in/out packets only to layer 2 the performance will be much more than linux with iptables. >> I don't know jack about IPSet, but I know enabling or disabling hosts in >> bare stock PF without the gui in front of it is about as easy as it gets. > >IPTALES is the same; > >iptables -A [INPUT/FORWARD] -d -j [REJECT/DROP] > >> The PF configuration file syntax was designed from the ground up to be >> sane, unlike iptables, which typically needs some decent sysadmin scripting >> or using fwbuilder to make any good sense of. > >I beg to differ here. IPTABLES is not that hard when you understand it. Like >anything else, once you know what you are doing it isn't that hard. And no, >I have never used any GUI program to configure my firewalls. > >> There is no finer opensource firewall product on the market, in terms of >> performance, ease of configuration and use, and other issues. > >This is all subjective to the user. I would say that PF is a nightmare and >IPTABLES is easier to use. > >> If you're not opposed to vi, for what you're looking to accomplish, moving >> to BSD and pf is a no-brainer. PF can definitely handle a list of 500 >> hosts and anything else you've mentioned. It's absolutely capable, easier, >> and in general, for anything that involves packet filtering at all, about >> as good as it gets. > >Again this is all subjective to the user. > > >-- > >Regards >Robert > >Linux User #296285 >http://counter.li.org >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >http://lists.centos.org/mailman/listinfo/centos >

4 4

xen domu not starting
by Peter Peltonen 20 Dec '09

20 Dec '09

After running out of swap and memory and freezing, a domU called web02 won't start up. Both dom0 and domU are running CentOS release 5.4. dom0's kernel is 2.6.18-164.el5xen and I'm running the stock xen from CentOS: xen-3.0.3-94.el5 After issuing 'xen create web02' I see the following in the xen console: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) vmalloc area: ee000000-f4ffe000, maxmem 2d800000 Memory: 1031328k/1056768k available (1478k kernel code, 16784k reserved, 548k data, 132k init, 311296k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Security Scaffold v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 6144K Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU 1 irqstacks, hard=c0344000 soft=c0324000 Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 1232k freed Grant table initialized NET: Registered protocol family 16 Initializing CPU#1 Brought up 2 VCPUs But after that it just hangs. SSH won't respond either. 'xm list' shows: web02 25 1023 2 -b---- 0.9 All I see in dom0's xend log is: Dec 20 13:18:10 kr kernel: device vif25.0 entered promiscuous mode Dec 20 13:18:10 kr kernel: ADDRCONF(NETDEV_UP): vif25.0: link is not ready Dec 20 13:18:12 kr kernel: blkback: ring-ref 8, event-channel 9, protocol 1 (x86_32-abi) Dec 20 13:18:12 kr kernel: ADDRCONF(NETDEV_CHANGE): vif25.0: link becomes ready Dec 20 13:18:12 kr kernel: xenbr0: topology change detected, propagating Dec 20 13:18:12 kr kernel: xenbr0: port 5(vif25.0) entering forwarding state In dom0's /var/log/messages I see: Dec 20 13:18:12 kr kernel: blkback: ring-ref 8, event-channel 9, protocol 1 (x86_32-abi) Dec 20 13:18:12 kr kernel: ADDRCONF(NETDEV_CHANGE): vif25.0: link becomes ready Dec 20 13:18:12 kr kernel: xenbr0: topology change detected, propagating Dec 20 13:18:12 kr kernel: xenbr0: port 5(vif25.0) entering forwarding state xm dmesg reports nothing unusual except these at the end: (XEN) mm.c:649:d22 Error getting mfn 3b6 (pfn 55555555) from L1 entry 00000000003b6025 for dom22 (XEN) mm.c:3341:d22 ptwr_emulate: fixing up invalid PAE PTE 00000000003b6025 But I've no idea when those messages have been created. I've disabled selinux in dom0. Other domUs are running fine, although I haven't tried rebooting them. Any ideas what could be wrong with the domU? Regards, Peter

1 0

unverified files in 5.4
by ken 20 Dec '09

20 Dec '09

Hey, Gang! To ensure that a file hasn't been corrupted or tampered with, you can use rpm to verify the package it came from. Well, I found this: rpm -Vv util-linux .... ........ /usr/bin/cal S.?..... /usr/bin/chfn ........ /usr/bin/chrt S.?..... /usr/bin/chsh .... Does anyone else get this? And what would be the proper course of action at this point? Thanks mucho. -- Without music, life would be a mistake. --Friedrich Nietzsche

2 3

Evolution search menu
by Frank Cox 20 Dec '09

20 Dec '09

When I switched my main desktop computer from Fedora to Centos, I moved my email from Sylpheed to Evolution. (Reason: Sylpheed for Centos doesn't boldface unread messages in the message list box and newer Sylpheed versions won't compile on Centos.) Evolution works fine, but I can't figure out how to get rid of the "previous/next" buttons that appear at the bottom of the Evolution window after I do a search. Detail: I enter a search term in the "Search" box over the message list. Two buttons "previous" and "next", plus a "match case" checkbox and "Matches: X" (where X is the number of matches found in the message) appear at the bottom of the Evolution window, just below the message text. That bar is fine while I'm doing the searching, but the only way I can get rid of that after I complete my search is to exit and re-load Evolution. Is there another way to get rid of it? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

1 0

Donation programme
by Yves Bellefeuille 19 Dec '09

19 Dec '09

Is there any decision about the donation programme? The Web page still says: "If you are looking to make a cash dontation to the CentOS Project, please check back here after August 15th, 2009." I assume that donations aren't refused, but is there a suggested amount, as there used to be? -- Yves Bellefeuille <yan(a)storm.ca> "Yves Bellefeuille: Eterna malvenkanto en UEA" -- Heroldo Komunikas, n-ro 389

4 4

CentOS-announce Digest, Vol 58, Issue 6
by centos-announce-request＠centos.org 19 Dec '09

19 Dec '09

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2009:1671 Important CentOS 4 i386 kernel - security and bug fix update (Tru Huynh) 2. CESA-2009:1671 Important CentOS 4 x86_64 kernel - security and bug fix update (Tru Huynh) 3. CESA-2009:1673 Critical CentOS 4 i386 seamonkey - security update (Tru Huynh) 4. CESA-2009:1673 Critical CentOS 4 x86_64 seamonkey - security update (Tru Huynh) 5. CESA-2009:1674 Critical CentOS 4 i386 firefox - security update (Tru Huynh) 6. CESA-2009:1674 Critical CentOS 4 x86_64 firefox - security update (Tru Huynh) 7. CESA-2009:1680 Important CentOS 4 i386 xpdf - security update (Tru Huynh) 8. CESA-2009:1680 Important CentOS 4 x86_64 xpdf - security update (Tru Huynh) 9. CESA-2009:1681 Important CentOS 4 i386 gpdf - security update (Tru Huynh) 10. CESA-2009:1681 Important CentOS 4 x86_64 gpdf - security update (Tru Huynh) 11. CESA-2009:1682 Important CentOS 4 i386 kdegraphics - security update (Tru Huynh) 12. CESA-2009:1682 Important CentOS 4 x86_64 kdegraphics - security update (Tru Huynh) 13. CESA-2009:1648 Moderate CentOS 5 x86_64 ntp Update (Karanbir Singh) 14. CESA-2009:1648 Moderate CentOS 5 i386 ntp Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Dec 2009 20:00:39 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2009:1671 Important CentOS 4 i386 kernel - security and bug fix update To: centos-announce(a)centos.org Message-ID: <20091218190039.GA18708(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2009:1671 kernel security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2009-1671.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/kernel-2.6.9-89.0.18.EL.i586.rpm updates/i386/RPMS/kernel-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-devel-2.6.9-89.0.18.EL.i586.rpm updates/i386/RPMS/kernel-devel-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-hugemem-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-hugemem-devel-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-smp-2.6.9-89.0.18.EL.i586.rpm updates/i386/RPMS/kernel-smp-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-smp-devel-2.6.9-89.0.18.EL.i586.rpm updates/i386/RPMS/kernel-smp-devel-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-xenU-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-xenU-devel-2.6.9-89.0.18.EL.i686.rpm updates/i386/RPMS/kernel-doc-2.6.9-89.0.18.EL.noarch.rpm source: updates/SRPMS/kernel-2.6.9-89.0.18.EL.src.rpm You may update your CentOS-4 i386 installations by running the command: yum update kernel\* Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

DRBD
by Scott McClanahan 19 Dec '09

19 Dec '09

Would any of you be comfortable running the drbd packages from the extras repo? If so, any particular version .. I notice 8.0, 8.2, 8.3. I'll do my own due diligence but just curious if the list has any implementation based feedback. Thanks.

4 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss