similar to: How to make call from asterisk?

Hi All, I hope I'm posting this to the appriopriate list, and that cross posting to two lists is OK. (If not, I'm sure I'll hear about it quickly :)) I'm running Asterisk on my (new) VIA EPIA-V motherboard. This seems to be the ideal platform for a home version of asterisk - its small, quiet, low power, and should have plenty of computing horsepower if only it would work!

Greetings, I am resending this as it doesn't appear in the archives and no one responded...maybe it got routed to /dev/null or something :-) I have asked this question the Scientific Linux mailing list (a few months ago) and got the suggestion I talk to the kernel guys. I pinged a kernel guy I know, and his suggestion was to ask the Nouveau list. So here I am. :-) I have had my work laptop

I''m trying to pass my SATA controller through to a domain and have run into a weird situation. I have two machines with the same general class of hardware (Intel PIIX) and the pass-through works on one machine but not the other. On the non-working system, the SATA controller makes port reads, but they don''t return the correct values. For example, when running it in dom0, when

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia

Hello, A user (cc'd) reported that nouveau's enabling of MSI causes the card to not work on his setup [1]. I think the situation is that MSI is just not supported by the underlying motherboard, even though the card, and probably bridge, support it just fine. It's a very old board. The nouveau code does: pmc->use_msi = pci_enable_msi(device->pdev) == 0; Does it need to do more

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hey hope this opne is a "make senser". Has anyone tried the "Subject line" combo?, I''ve compiled a dozen src.rpm kernel 3.0 and 3.1 packages with no luck to try native upstream Dom0 kernel support with no success, just a kernel oops and constant reboots. I followed Fedora''s wiki on building a custom kernel, even used F16''s .config which also was a

Hello, I am having problems, getting my asterisk-domU to work properly. It consists of the following components: - Debian Etch under Xen-3.1 with a 2.6.18-kernel - Asterisk 1.2.24 - mISDN-1.1.5 I have 2 HFC-ISDN-cards, which I pass through to the Asterisk-DomU in permissive mode. This is working fine. The strange problem is, that the two HFC-ISDN-cards are not beeing initialized by the

Hello, I have a PC Chips A31G board with AGPro slot and found that nouveau does not work properly with it. Console works but reverts to software mode, X11 hangs with mouse cursor only. The slot is physically AGP 1.5V but is wired to PCI bus as the chipset (SiS 761) does not support AGP cards. To further complicate things, the chipset has AGP capability - but only for the integrated video. You can

I mistakenly only replied to Yijing Wang the first time. Here are the further details. uname -a: Linux p5-133 3.15.2-p5-133 #1 Thu Jun 26 22:56:27 EDT 2014 i586 GNU/Linux Here is the output from lspci -vvvxxx: root at p5-133:~# cat lspci.txt 00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 01) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

PC: HP Vetra VL400 Mainbood: Intel815 BIOS: Phonix 4.0 release 6.0 OS: REDHAT 9.0 I installed the X100P in PCI slot 2 and disable the USB port, serial-port and parallel-port in BIOS. I can't found the X100P card in " cat interrupts" But I can found the card in the "cat ioports" use "lspci" I found the X100Pcard use the interrupts 11 too. Who can help me to solve

Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >

I tried to install and boot a 2.6.7 Dom0 xenLinux Kernel on an SMP (Dual-Xeon) Machine with 2 3-ware Controllers installed (1 4-channel Controler and 1 8-channel Controler, both Parallel ATA) and no other HDs present (except the ones connected to the 3ware controlers, of course). First of all I got a compilation error after activating the SMP option in the kernel config. After deactivating the

Hi, I using asterisk 1.2.4 on a CentOS with Linux 2.6.9-22.0.2.ELsmp kernel. I've two x100p cards connected, only one card is reconigzed by asterisk. 02:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface 02:02.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31) 02:03.0 Communication controller: Tiger Jet

Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to

Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with

Yijing, cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting that it supports MSI. However, this "00:0e.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" is a component of the addin card. Wouldn't the lack of support for MSI by the chipset "00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 01)"

Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere

On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: > Hi Brian, > From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this > card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. > > You can check PCI bus whether support MSI like: > >