similar to: usb 1-2: device not accepting address 2, error -71 - CENTOS 5

Displaying 20 results from an estimated 2000 matches similar to: "usb 1-2: device not accepting address 2, error -71 - CENTOS 5"

2007 Sep 20
1
ata1 bootup errors
> ata1: port is slow to respond, this delay is known to occur on vacant SATA ports > ata1: port failed to respond (30 secs) > ata1: SRST failed (status 0xFF) > ata1: SRST failed (err_mask=0x100) > ata1: softreset failed, retrying in 5 secs > ata1: SRST failed (status 0xFF) > ata1: SRST failed (err_mask=0x100) > ata1: softreset failed, retrying in 5 secs > ata1: SRST
2009 Jul 26
2
SATA DVD Burner / AHCI / CentOS 4.7 (kernel: 2.6.9-78.0.22.EL)
OK, it seems that the kernel I have (stock CentOS 4.7: 2.6.9-78.0.22.EL i686) seems to gronk the nVideo SATA controller in AHCI mode. It is NOT able to deal with the SATA DVD Burner I have. It is a "Sony Optiarc DVD Burner with LightScribe Black SATA Model AD-7241S-0B LightScribe Support". Is there some special magic I need to do? Here is the relevant bit from the boot up (SATA ports
2019 Jun 24
2
Issue with dvd/cdrom drive
> > > > > [root at darkness ~]# ls -al /dev/sr* > > ls: cannot access /dev/sr*: No such file or directory > > [root at darkness ~]# ls /dev/s* > > /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr > > /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin > > /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout > > [root at
2010 Apr 11
7
dom0 crash, require assistance interpretting logs and config suggestions
Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being
2009 Jul 06
3
Small site survivability
We are currently moving away from a wide-spread Cisco CallManager deployment to Asterisk. For many of our small sites we have the routers configured for what Cisco calls SRST so if we have a WAN failure, the router acts as a SCCP registrar. We are converting to SIP, and from what I can tell Cisco wants a license for each router to run SRST over SIP... So my question to the group is: What are
2008 Nov 29
24
pv_ops dom0 testing
I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on:
2019 Jun 24
2
Issue with dvd/cdrom drive
On Mon, Jun 24, 2019 at 3:35 AM Pete Biggs <pete at biggs.org.uk> wrote: > On Sun, 2019-06-23 at 22:13 -0400, doug schmidt wrote: > > Hi, > > I'm having an issue with my Thinkpad P70 laptop/workstation. This system > is > > a dual boot, > > windows 10 pro and centos 7. I have not needed to use the cdrom until > now, > > however the system does not
2010 Sep 11
0
AHCI and VT-d related problem
Hello, I have an issue with my XEN system. I suspect that it might be a bug, but I''m no linux expert, so I don''t know. Here is my problem: I have an ASUS P7P55D-E Premium motherboard, and a Western Digital Caviar Black SATA-III 1TB hdd. I am trying to use AHCI. The dom0 is an Arch Linux. The dom0 boots fine until Intel VT-d is enabled in the BIOS. When I enable it Arch
2011 Oct 31
5
Xen 4.1.1 HVM guest cdrom trouble, lost interrupts, ata failed commands (frozen)
Hello, I was testing Fedora 16 (rc2) Xen host, with included Xen 4.1.1 rpms and Linux 3.1.0 dom0 kernel. Fedora 16 PV domUs seem to work nicely. I noticed a problem with Fedora 16 Xen HVM guests though. The F16 guest kernel (Linux 3.1.0) fails with the qemu-dm emulated DVD-ROM drive.. Full HVM guest kernel dmesg attached to this email. See the end of this email for Xen cfgfile for the
2005 May 09
3
VOIP/SATELLITE
Hi, I have a Asterisk with two Cisco ATA connected with each other . Cisco ATA1 is connected via satellite link Cisco ATA2 is connected via leased line The problem is CISCO ATA2 can call CISCO ATA2 with no problem But CISCO ATA1 cannot call CISCO ATA2 . Any suggestion please Rabii -------------- next part -------------- An HTML attachment was
2011 Apr 30
3
Identifying physical disks
I am sure this is really simple. I have a setup of 2 disks (sda, sdb) which are outwardly identical, and are mirrors of each other. Together they form 3 raid1 devices. Both disks can boot. Now sda has bad sectors, and I should replace it. But which one of the physical disks is sda?? The machine boots fine from either one of the disks, (and the booting disk of course is always called sda).
2013 Nov 25
1
Lots of DMA messages on FreeBSD 10
Hello all. I just updated my machine from 9-STABLE to 10-Stable today. beasty ~ # uname -a FreeBSD beasty.schavemaker2.local 10.0-BETA3 FreeBSD 10.0-BETA3 #0 r258543: Mon Nov 25 13:23:31 CET 2013 root at beasty.schavemaker2.local:/usr/obj/usr/src/sys/KRNL amd64 After a reboot, the console gets cluttered with a lot of messages. ata2: FAILURE - zero length DMA transfer attempted ata2: setting
2005 Feb 28
1
x101p + Nortel ATA2
Hi, Does anyone have any experience connecting Asterisk to a Meridian system using an ATA2 and x101p? The basics work -- I can make outbound calls, receive inbound, and use flash to transfer calls, but certain things do not work, specifically with calls from internal extensions. - Does the Meridian/ATA2 pass any kind of callerid info? We do not have external callerid, but I'm not even
2010 May 12
0
Xen 4.0.0 - dom0_mem differs from dom0''s memory
Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all
2007 May 04
1
CentOS 5 + Nforce 4 SLI Intel SATA problems
I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector
2019 Jun 24
0
Issue with dvd/cdrom drive
> > [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.183893] ata3.00: qc timeout (cmd 0xec) > [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.183960] ata4.00: qc timeout (cmd 0xa1) > [ 7.183974] ata4.00: failed to IDENTIFY (I/O error,
2012 Mar 07
2
hardware issues? driver issues?
Got a bunch of servers from Penguin. Supermicro m/b's H8QG6. We put a 3tb drive in for additional workspace for the users, and some of them won't read, others will go for weeks, then spit out DRDY errors. lshw shows the controller as an ATI SB7x0/SB8x0/SB9x0 SATA. I did notice that it shows *-storage description: SATA controller product: SB7x0/SB8x0/SB9x0 SATA
2006 Sep 21
12
Hard drive errors
One of my CentOS boxes has started giving me errors. The box is CentOS-4.4 (i386) fully updated. It has a pair of SATA drives in a software raid 1 configuration. The errors I see are: ata1: command 0xca timeout, stat 0x50 host_stat 0x24 ata1: status=0x50 { DriveReady SeekComplete } Info fld=0x1e22b8, Current sda: sense key No Sense ata2: command 0xca timeout, stat 0x50
2004 Jul 23
1
Norstar ATA2 signalling protocol?
Does anyone know which signalling protocol works when connecting the output of a NT8B90AL Norstar ATA2 analog terminal adapter to an FXO card? (fxsks, fxsgs, fxsls?) I'm trying to add an Asterisk branch to my Norstar PBX as outlined at http://www.voip-info.org/wiki-Asterisk+Nortel. - Mike
2003 Jul 09
3
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
Before reading below: I am considering a new install rather than an upgrade of our servers. However, now I just want to beat this problem. :) At 02:19 PM 7/8/2003 +0000, Phil Pennock wrote: >On 2003-07-08 at 14:09 +0000, Phil Pennock wrote: > > There was a fairly major update to the IDE disk device handlers which > > required new device nodes. Bringing in the new MAKEDEV script