search for: p200mmx

...tel(msg->address_hi, base + PCI_MSIX_ENTRY_UPPER_ADDR); > writel(msg->data, base + PCI_MSIX_ENTRY_DATA); > ...... > >> shouldn't. I don't know all the details about MSI, but doesn't the CPU >> or (L)APIC have to support it? In this case, it's a P200MMX on a 430FX >> chipset board. Both quite ancient... > > MSI in x86 always send to specific interrupt address(0xfeexxxx), most x86 CPU > should support MSI, but I am not sure, I don't know hardware much. To put things in perspective, P200MMX was released in early 1997. It looks li...

Looking at installing Asterisk and have not been able to find any info on "minimum" or "recommend" system hardware. I have a box P200MMX 128mb 4.5gb HDD which is running Redhat 8.0 fine. Noticing on the Digium web site it mentions that the single fxo card (Wildcard X100P) requires a minimum pIII 500. Is my intended box going to be too slow? My application is a small level, single port only system. I hope to be able to connect the...

...in this list's archives. I thought I'd let you know that I tested Asterisk using IAX (not IAX2) to make a phone call from an analog phone hooked up to an Asterisk system behind a Linksys router connected to a Gilat VSAT satmodem, and it worked. The "other end" (gateway) is a P200MMX with a X100P FXO card. I have bi-directional calling set up so that the VSAT-phone can make outbound calls using the X100P in the gateway, and if the X100P gets a ring it answers and transfers the call to the analog phone on the other side of the VSAT. There is about a 1-2 second propagation d...

...hi, base + PCI_MSIX_ENTRY_UPPER_ADDR); >> writel(msg->data, base + PCI_MSIX_ENTRY_DATA); >> ...... >> >>> shouldn't. I don't know all the details about MSI, but doesn't the CPU >>> or (L)APIC have to support it? In this case, it's a P200MMX on a 430FX >>> chipset board. Both quite ancient... >> >> MSI in x86 always send to specific interrupt address(0xfeexxxx), most x86 CPU >> should support MSI, but I am not sure, I don't know hardware much. > > To put things in perspective, P200MMX was released...

...ENTRY_UPPER_ADDR); >>> writel(msg->data, base + PCI_MSIX_ENTRY_DATA); >>> ...... >>> >>>> shouldn't. I don't know all the details about MSI, but doesn't the CPU >>>> or (L)APIC have to support it? In this case, it's a P200MMX on a 430FX >>>> chipset board. Both quite ancient... >>> >>> MSI in x86 always send to specific interrupt address(0xfeexxxx), most x86 CPU >>> should support MSI, but I am not sure, I don't know hardware much. >> >> To put things in perspective...

I live in Tennessee, USA, and work 1000km away in Texas. Thanks to the wonders of broadband I never leave home (well, not for WORK, that is. :) I'm setting up an Asterisk system whereby I'll have an extension in Texas, so clients can reach me at a local telephone number. We have a VPN set up already (OpenVPN, which I highly recommend to anyone needing such a thing.) It does

...all my 242 Type1 fonts from X. I don't find it useful > to have any limitation in using fonts. So, I dropped an idea to make > fully functional PageMaker workstation under Linux with X. Although > Adobe PageMaker 6.5 Russian Edition works very well for me under Wine. That was true for P200MMX, 128 Mb RAM, RH 6.0, kernel 2.2.16, XFree86 3.3.6 On weekend, I installed 325 Type1, all TrueType fonts borrowed from Win2000 plus some bitmap fonts installed by XFree 4.0.2. Now I have the following machine: PIII 667, 256 Mb RAM, RH 6.2, kernel 2.2.16, XFree 4.0.2 and... COMPLETE SUCCESS! For...

...he same file the improvement was from 1 minute to open a 600K file, to around 8 seconds to open the same file. I need someone else to verify these settings, if it works on more than one machine, then PLEASE email me so that I may get ahold of someoneto get this put into a faq ASAP. System Specs: P200MMX Slackware Linux 3.4 kernel 2.0.35 NE2000 network card. client P266 3com 3c905 WinNT 4 SP3. Thank you

Hi. I have a base 10 hub, a SAMBA 2.2.6 server on a p200mmx, and a win98se box. Everything in DIAGNOSTICS.txt checks out fine, and everything seems to work ok until i try to send an iso image across. That is when smbd crashes (about halfway/300M), and win gives the error 'cannot copy or replace <filename>: the resource or device is no longer ava...

...ooting with "pci=nomsi". But as you say, it's unreasonable to add quirks for all old systems. Brian, can you open a report at http://bugzilla.kernel.org and attach a complete dmesg log, /proc/cpuinfo contents, and "lspci -vvv" output? If I understand correctly, you have a P200MMX with a 430FX chipset. I'm not a hardware guy, but sounds like that might be a 200MHz Pentium with MMX (P54CS), which does have an integrated LAPIC, according to wikipedia. >From the PCI host bridge's perspective, an incoming MSI just looks like a normal DMA write. As long as that write...

...quot;. But as you say, > it's unreasonable to add quirks for all old systems. > > Brian, can you open a report at http://bugzilla.kernel.org and attach > a complete dmesg log, /proc/cpuinfo contents, and "lspci -vvv" output? > > If I understand correctly, you have a P200MMX with a 430FX chipset. > I'm not a hardware guy, but sounds like that might be a 200MHz Pentium > with MMX (P54CS), which does have an integrated LAPIC, according to > wikipedia. > > From the PCI host bridge's perspective, an incoming MSI just looks > like a normal DMA writ...

Hello lartc, Testing some rules I found out that any rules are slowing down large pings! For example: tc qdisc add dev eth0 root handle 1: htb tc class add dev eth0 parent 1: classid 1:1 htb rate 100Mbit prio 1 ceil 100Mbit tc class add dev eth0 parent 1:1 classid 1:2 htb rate 100Mbit prio 2 ceil 100Mbit tc filter add dev eth0 parent 1:0 prio 5 u32 \ match ip src 10.10.10.1 \ match ip

...200 80 200 300 250 ..... To get informations about latency i am marking ping packets with iptables. I want to play during other users downloading and i want to keep my voicechat useable ... i need low latency It would be nice if you could help ... I am happy about every answer :) using: gentoo p200mmx 64mb ram 2.4.20 kernel my script: ### Traffic Shaper ## down 768kbit ## up 128kbit tc qdisc add dev $EXTIF root handle 1:0 htb default 13 tc class add dev $EXTIF parent 1:0 classid 1:1 htb rate 16kbps ceil 16kbps prio 0 # Gamevoice tc class add dev $EXTIF parent 1:1 classid 1:11 htb rate 3kb...

...ed various variations on the parameters, but doesn't seem to make a lot of difference. Am I missing something? Old Server - FreeBSD 3.2 + Samba 2.0.5 - P2/300 with 128Mb RAM New Server - RedHat Linux 7.2 + Samba 2.2.6 - Duron 1200 with 768Mb RAM Workstations - MS-DOS 6.22 + MS-Client v3.0 - P200MMX/P233MMX with 64Mb Problem: simulating multi-user access to a file, when program hits a locked record (cobol reply 9/68 - record locked) both machines freeze for some considerable time (15 - 30 mins) before they continue. Program reply test has a delay loop built in such that it will wait before...

...systems on the server, restarted rsyncd, tried the rsyncd executable from the old server on the new server with no difference. Now I'm back with a fresh configure and compile of rsync, and things are misbehaving consistently. What else might I try? client end: Red Hat Linux release 7.2, P200mmx, 64MB ram, 128MB swap. rsync uses 6MB ram when running before it crashes, all ext3. rsync 2.5.6 from the rsync site, plain old configure, make, make install. 3c509 ethernet over a 11mbps 5.8ghz radio link that is rock solid. HP switches on both ends. [root@bht /]# /usr/local/bin/rsync -avvW --d...

>From the <samba>/var/log/<client>.log file: doing parameter domain controller = AZPHXNT01 Unknown parameter encountered: "domain controller" Ignoring unknown parameter "domain controller" >From the smb.conf file: # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use

...nouveau does generally work for most people :) And it works fine here if MSI is forced off. The problem here is that pci_enable_msi() succeeds, but it probably shouldn't. I don't know all the details about MSI, but doesn't the CPU or (L)APIC have to support it? In this case, it's a P200MMX on a 430FX chipset board. Both quite ancient... So given that the PCI device itself supports MSI, how do we tell that it shouldn't actually get turned on? -ilia > > On 2014/7/4 8:35, Brian Becker wrote: >> I mistakenly only replied to Yijing Wang the first time. Here are the fu...

...WER_ADDR); writel(msg->address_hi, base + PCI_MSIX_ENTRY_UPPER_ADDR); writel(msg->data, base + PCI_MSIX_ENTRY_DATA); ...... > shouldn't. I don't know all the details about MSI, but doesn't the CPU > or (L)APIC have to support it? In this case, it's a P200MMX on a 430FX > chipset board. Both quite ancient... MSI in x86 always send to specific interrupt address(0xfeexxxx), most x86 CPU should support MSI, but I am not sure, I don't know hardware much. > > So given that the PCI device itself supports MSI, how do we tell that > it should...

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-