Discuss

discuss@lists.centos.org

34753 discussions

What is connect-debounce wrt usb?
by Robert Moskowitz 15 Jan '08

15 Jan '08

I get the following message on a Centos 5 system (really a Trixbox 2.4 build on Centos 5): Jan 14 00:12:28 sip2 kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled What does this mean? This message occurs about 30 times/sec for about 45 sec. Then my Bluetooth token starts up. Jan 14 00:12:28 sip2 kernel: hub 1-0:1.0: connect-debounce failed, port 1 disabled Jan 14 00:13:00 sip2 last message repeated 18 times Jan 14 00:14:01 sip2 last message repeated 35 times Jan 14 00:15:02 sip2 last message repeated 35 times Jan 14 00:16:03 sip2 last message repeated 35 times Jan 14 00:17:04 sip2 last message repeated 35 times Jan 14 00:18:05 sip2 last message repeated 35 times Jan 14 00:19:06 sip2 last message repeated 35 times Jan 14 00:20:07 sip2 last message repeated 35 times Jan 14 00:21:08 sip2 last message repeated 35 times Jan 14 00:22:10 sip2 last message repeated 35 times Jan 14 00:23:11 sip2 last message repeated 35 times Jan 14 00:24:12 sip2 last message repeated 35 times Jan 14 00:25:13 sip2 last message repeated 35 times Jan 14 00:26:15 sip2 last message repeated 35 times Jan 14 00:27:16 sip2 last message repeated 35 times Jan 14 00:28:17 sip2 last message repeated 35 times Jan 14 00:29:18 sip2 last message repeated 35 times Jan 14 00:30:19 sip2 last message repeated 35 times Jan 14 00:31:20 sip2 last message repeated 35 times Jan 14 00:32:21 sip2 last message repeated 35 times Jan 14 00:32:44 sip2 last message repeated 13 times Jan 14 00:32:44 sip2 kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2 Jan 14 00:32:44 sip2 kernel: usb 1-1: configuration #1 chosen from 1 choice Jan 14 00:32:45 sip2 kernel: Bluetooth: HCI USB driver ver 2.9 Jan 14 00:32:45 sip2 hcid[1826]: HCI dev 0 registered Jan 14 00:32:45 sip2 hcid[1826]: Register path:/org/bluez/hci0 fallback:0 Jan 14 00:32:45 sip2 kernel: usbcore: registered new driver hci_usb Jan 14 00:32:45 sip2 hcid[1826]: HCI dev 0 up Jan 14 00:32:45 sip2 hcid[1826]: Device hci0 has been added Jan 14 00:32:45 sip2 hcid[1826]: Starting security manager 0 Jan 14 00:32:45 sip2 hcid[1826]: Device hci0 has been activated a hciconfig -a gets: hci0: Type: USB BD Address: 00:0D:18:01:20:B9 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:8862 acl:38 sco:0 events:393 errors:0 TX bytes:2358 acl:38 sco:0 commands:154 errors:0 Features: 0xff 0xff 0x8f 0xf8 0x18 0x18 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'sip2' Class: 0x000100 Service Classes: Unspecified Device Class: Computer, Uncategorized HCI Ver: 1.2 (0x2) HCI Rev: 0x512 LMP Ver: 1.2 (0x2) LMP Subver: 0x512 Manufacturer: Cambridge Silicon Radio (10) CSR is considered good... Then I try and pair my Treo 650. I picked up the following to make the token discoverable: dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable ouch! Now then, hcitool scan mostly fails. But hcitool info 00:07:E0:24:5A:94 gets: Requesting information ... BD Address: 00:07:E0:24:5A:94 Device Name: RGM LMP Version: 1.1 (0x1) LMP Subversion: 0x700 Manufacturer: Broadcom Corporation (15) Features: 0xbf 0xfe 0x0d 0x00 0x00 0x00 0x00 0x00 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <sniff mode> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <power control> <transparent SCO> After a bit of work, I can get the phone to prompt me for the PIN. But hcitool con comes up empty. I try hcitool cc 00:07:E0:24:5A:94 and the phone shows connecting, but hcitool con shows an empty list. Of course when I get into Asterisk's CLI and try a mobile show device, it lists the Treo (I did put a section for it in the mobile.conf file) put shows NO for Available. Can anyone help me get direction on getting my phone paired with my system?

4 3

Kickstart install with a degraded raid array
by Rick Barnes 15 Jan '08

15 Jan '08

Is it possible to install CentOS 5 with a degraded RAID 1 array using kickstart? I have the kickstart file already created but the "server" I want to use only has 1 hard drive in it at the moment. Until I can order a 2nd drive, I wanted to install the OS then once I received the replacement drive "fix" the array. I have seen instructions how to do this manually, but so far have not been able to get it to work using kickstart. Anyone tried this in the past? Thanks, Rick

2 1

LIMITING NUMBER OF KERNEL VERSIONS RETAINED
by Chris Geldenhuis 14 Jan '08

14 Jan '08

Hi Some time ago there was a discussion on the above subject. I have scanned the past few month's mailing list archives and cannot find the relevant mail(s). Could somebody please repost the solution or point me at the correct resource. I would also appreciate advice on how to do this on a RHEL4 server being updated with up2date. Is it safe just to delete the old kernel and initrd files from the boot partition and the grub conf file? TIA ChrisG

8 8

Strange: wireless card shouldn't work, but it works ?!?
by Niki Kovacs 14 Jan '08

14 Jan '08

Hi, I know this is a rather unusual request. Normally, people would complain about a card that *should* work, but here goes. I have a series of machines in a computer room, all equipped with a RT2561 wireless card. CentOS doesn't include support for that card, so what I usually do to install a system: 1) Install a *very* minimal base system (the bare minimum). 2) Install some development tools (gcc, kernel-devel) from the CentOS install CDs. 3) Copy over the driver source (rt2561-cvs-daily.tar.gz) downloaded on another machine. 4) Compile that driver and install it (plain make && make install). 5) Configure my network to use the wireless card. 6) yum update my base system once I have network. This method has the advantage of avoiding having to pull 20-meter Ethernet cables only to configure wireless :oD Now one thing puzzles me. I have the install CD set from 5.0. The default kernel is 2.6.18-8.el5. Once I updated the whole base system and rebooted on it, I'm using the updated kernel, e. g. 2.6.18-53.1.4.el5 at this date. As far as I understand, each kernel has its own set of kernel modules under /lib/modules/`uname -r`. A quick ls on /lib/modules effectively shows me the two directories for the two kernels. I installed my wireless driver on the old kernel, which means normally after rebooting I'd have to build and install it again for my new kernel. Bu strangely enough, when I reboot on the new kernel, my wireless card still works without me having rebuilt the driver. I'm clueless about this. Niki

2 2

CentOS Book
by Niki Kovacs 14 Jan '08

14 Jan '08

Hi, I'm using CentOS on server and desktop since 4.2, and I'm quite happy with it. Can you recommend some complete documentation besides the RHEL Deployment Guide? For example, I have a big fat paper book "FreeBSD Unleashed", 700 pages chock full of useful information. Now I wonder if you can recommend something similar for CentOS (RHEL / Fedora). cheers, Niki

2 2

PHP 5.2.5 when ?
by Santa Claus 14 Jan '08

14 Jan '08

Hi When (some) expected rpm package for the upgrade php to version 5.2.5(CentOS4) ? Who knows? -- wbr

10 20

winbind - 32bit vs 64bit
by Bleier Thomas 14 Jan '08

14 Jan '08

Hi all, I've running a CentOS 5 64bit server that hosts VMware Server and uses authentication via Samba/Winbind. The problem is that authentication in the VMware Server web interface does not work because apparently it is a 32bit application and CentOS 5 x86_64 provides only a 64bit version of the pam_winbind.so library. At least that what I conduct from the following message I get in /var/log/security: Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM unable to dlopen(/lib/security/pam_winbind.so) Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM [error: /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory] Jan 14 18:10:45 ittvm1 vmware-authd[7946]: PAM adding faulty module: /lib/security/pam_winbind.so And when I look into the filesystem I find a pam_winbind.so in /lib64/security and none in /lib/security. Of course the module is in the samba-common.i386 package, but since it also contains a lot of other tools and utilities I don't want to install it in addition to the 64bit version. Any advice/hints? Best regards, __ /homas -- Thomas Bleier, DI Information Management Austrian Research Centers GmbH - ARC HG Wien - FN 115980i - ATU14703506 2444 Seibersdorf, Austria Mobile: +43 (664) 8251279 E-Mail: thomas.bleier(a)arcs.ac.at <mailto:thomas.bleier@arcs.ac.at>

1 1

"find" switch to find files of a certain size?
by techlists＠comcast.net 14 Jan '08

14 Jan '08

Is there a switch in "find" (or some other command besides find) that'll let you find files larger than a specified size? My file system is 88% full and I'd like to see where the biggest space hoggers are. PG

6 7

CentOS 5.1 and Xen HVM guest networking problem
by James Fidell 14 Jan '08

14 Jan '08

I've asked this on the Xen users list, but had no response so far: I'm running CentOS 5.1 with all current updates: xen-libs-3.0.3-41.el5 xen-3.0.3-41.el5 kernel-xen-devel-2.6.18-53.1.4.el5 kernel-xen-2.6.18-53.1.4.el5 and have a domU config file from another (5.0) server which works. The difference is that on the new machine I want to use routed rather than bridged networking. In bridging mode the domU works fine, but I can't use bridging on this particular server because of the external network configuration. I have modified /etc/xen/config.sxp, commenting out (network-script network-bridge) (vif-script vif-bridge) and uncommenting (network-script network-route) (vif-script vif-route) I've also changed the vif line in the domU config file to: vif = [ 'ip=aaa.bbb.ccc.ddd, vifname=veth1' ] The domU now boots, but has no eth0 interface (the driver doesn't load in the domU because it can't find a suitable device). Is there anything obvious I might have done wrong or missed out? There are no ethernet-related or network device errors in the logs that I can see. James

1 0

CentOS-announce Digest, Vol 35, Issue 6
by centos-announce-request＠centos.org 14 Jan '08

14 Jan '08

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-2007:1176 Important CentOS 5 i386 autofs Update (Karanbir Singh) 2. CESA-2007:1176 Important CentOS 5 x86_64 autofs Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Sun, 13 Jan 2008 19:05:52 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2007:1176 Important CentOS 5 i386 autofs Update To: centos-announce(a)centos.org Message-ID: <20080113190552.GA19432(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2007:1176 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1176.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 003005a1904e2d7b86c7e78752ae91b6 autofs-5.0.1-0.rc2.55.el5.2.i386.rpm Source: dbed45d348006960ac0976c68e01fa46 autofs-5.0.1-0.rc2.55.el5.2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Sun, 13 Jan 2008 19:05:52 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2007:1176 Important CentOS 5 x86_64 autofs Update To: centos-announce(a)centos.org Message-ID: <20080113190552.GA19445(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2007:1176 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1176.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 2bc04b0f86bc0b0a9a31bf5d8bd2d0b0 autofs-5.0.1-0.rc2.55.el5.2.x86_64.rpm Source: dbed45d348006960ac0976c68e01fa46 autofs-5.0.1-0.rc2.55.el5.2.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 35, Issue 6 **********************************************

1 0

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