Re: dhclient could not allocate memory
On 02/28/2013 06:58 PM, Marc Peters wrote: > Hi misc, > > i am using OpenBSD on my home router connected to cable internet. A re > nic is facing the wild and gets its public IP via DHCP from my ISP. I > have running a 5.3-beta from Feb. 1st, as this one has the powersaving > fix for athn in HostAP (realised it then, was committed already in > August). This router was running happily 5.2-RELEASE until then, 24/7, > without any issues. However, this night dhclient died unexpectedly and > /var/log/daemon says: > > Feb 27 22:05:56 router dhclient[22805]: sysctl retrieval of routes: > Cannot allocate memory > Feb 27 22:05:56 router dhclient[10969]: dispatch_imsg in main: pipe closed > > dhclient gone and with it my internet connection, too. > > I wonder, what could have caused this. The machine has two AMD APUs and > 8GB of memory (dmesg attached) and dhclient shouldn't run out of it (and > it had no issues like that before with 5.1 and 5.2), but maybe i am > totally wrong and looking in the wrong place at all. > > I know that Realtek cards have had a great history (joking!) and i try > to avoid them, but this one is onboard and Intel NICs with double > interfaces aren't as cheap as the PCIe one port desktop grade card i > already added. > > mbufs are also unremarkable: > marc@router > ~ $ netstat -m > 133 mbufs in use: > 87 mbufs allocated to data > 14 mbufs allocated to packet headers > 32 mbufs allocated to socket names and addresses > 22/356/6144 mbuf 2048 byte clusters in use (current/peak/max) > 64/73/6144 mbuf 4096 byte clusters in use (current/peak/max) > 0/8/6144 mbuf 8192 byte clusters in use (current/peak/max) > 0/8/6144 mbuf 9216 byte clusters in use (current/peak/max) > 0/8/6144 mbuf 12288 byte clusters in use (current/peak/max) > 0/8/6144 mbuf 16384 byte clusters in use (current/peak/max) > 0/8/6144 mbuf 65536 byte clusters in use (current/peak/max) > 1284 Kbytes allocated to network (25% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > Maybe someone can shed some light on it and knows which knob to turn. > > Cheers, > Marc > > > Uptime provided for reference, not measurement of private parts ;) > > marc@router > ~ $ uptime > 6:54PM up 24 days, 2:41, 1 user, load averages: 0.24, 0.19, 0.1 > > dmesg: > OpenBSD 5.3-beta (GENERIC.MP) #25: Fri Feb 1 16:29:00 MST 2013 > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8167034880 (7788MB) > avail mem = 7927136256 (7559MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeaf40 (52 entries) > bios0: vendor American Megatrends Inc. version "0306" date 08/18/2011 > bios0: ASUSTeK Computer INC. E45M1-I DELUXE > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT > acpi0: wakeup devices SBAZ(S4) PS2K(S4) PS2M(S4) UAR1(S4) P0PC(S4) > UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) > PE21(S4) RLAN(S4) PE22(S4) PE23(S4) BR14(S4) PWRB(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD E-450 APU with Radeon(tm) HD Graphics, 1650.36 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC > cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu0: 8 4MB entries fully associative > cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > cpu0: apic clock running at 199MHz > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD E-450 APU with Radeon(tm) HD Graphics, 1649.90 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC > cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu1: 8 4MB entries fully associative > cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins > ioapic0: misconfigured as apic 3, remapped to apid 0 > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318180 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 3 (PE20) > acpiprt2 at acpi0: bus 4 (PE21) > acpiprt3 at acpi0: bus -1 (PE22) > acpiprt4 at acpi0: bus -1 (PE23) > acpiprt5 at acpi0: bus -1 (BR15) > acpiprt6 at acpi0: bus -1 (PCE6) > acpiprt7 at acpi0: bus -1 (PCE7) > acpiprt8 at acpi0: bus -1 (PCE8) > acpiprt9 at acpi0: bus 1 (BR14) > acpicpu0 at acpi0: C2, PSS > acpicpu1 at acpi0: C2, PSS > acpibtn0 at acpi0: PWRB > cpu0: 1650 MHz: speeds: 1650 1320 825 MHz > pci0 at mainbus
Re: Precisions on ZFS (was: Millions of files in /var/www & inode / out of space issue.)
On Sat, Feb 23, 2013 at 1:59 AM, Miod Vallat wrote: > > Please, please, please, can someone port ZFS, just to end this endless > > thread...? > > Please someone port HAMMER instead. We are only interested in free > software, with no strings attached. > YAY!!! http://leaf.dragonflybsd.org/mailarchive/users/2012-02/msg00020.html
Re: pf and apache
Thus said Matt Morrow on Thu, 28 Feb 2013 23:07:30 -0600: > Apache is running on a slackware box. I can access apache just fine > internally by using the ip address of that server (192.168.1.70), but > if I access the ip of the openbsd box (192.168.1.60) I just get an > error that the server is not available. It should be forwarding port > 80 to the slackware box. I'm going to guess from your description that you are trying to rdr-to on the same interface. The documentation says: Redirections cannot reflect packets back through the interface they arrive on, they can only be redirected to hosts connected to different interfaces or to the firewall itself. The next section discusses using NAT... might be what you're after. Andy -- TAI64 timestamp: 4000513040c3
Re: preventing amd from fetch files from nis server
On Thu, Feb 28, 2013 at 12:30 PM, Friedrich Locke wrote: ... > But for a particular client machine, while it should retrieve the list > of users/groups/etc from the nis server i don't want it to retrieve > the amd.home from the nis server, but instead, uses the amd.home from > /etc/amd/amd.home. > Is that possible ? > Do you know if it may be done? amd uses the amd.home map because that's what /etc/amd/master indicates. To change what it uses, change that file. Philip Guenther
Re: EIGRP implementation?
On Thu, Feb 28, 2013 at 09:48:45PM +0200, Kostas Zorbadelos wrote: > Claudio Jeker writes: > > > I see no need to support it, I would first consider > > ISIS > > Do you have thoughts or plans on producing an ISIS implementation on > OpenBSD? > I think I answered this already. In short it is at the bottom of my todo list but it is there after fixing bgpd, ospfd, ospf6d, and ldpd. Since I'm not working full time on OpenBSD anymore I have much less time and so don't expect anything soon. -- :wq Claudio
Re: EIGRP implementation?
Claudio Jeker writes: > I see no need to support it, I would first consider > ISIS Do you have thoughts or plans on producing an ISIS implementation on OpenBSD? -- Kostas Zorbadelos twitter:@kzorbadeloshttp://gr.linkedin.com/in/kzorba () www.asciiribbon.org - against HTML e-mail & proprietary attachments /\
preventing amd from fetch files from nis server
Hi folks, i have a set of computer on my network that is configured as a nis client. The nis server is working 100% ok, and it is serving a map called amd.home. But for a particular client machine, while it should retrieve the list of users/groups/etc from the nis server i don't want it to retrieve the amd.home from the nis server, but instead, uses the amd.home from /etc/amd/amd.home. Is that possible ? Do you know if it may be done? Thanks in advance.
Carp issues
I have two firewalls running OpenBSD 5.1 with a 5.2 kernel amd64. I am running the 5.2 kernel because of another, unrelated bug. I have 4 ethernet interfaces (em0-4). em0 and em1 are in a failover trunk mode on trunk0 while em2 and em3 are members of trunk1 in failover mode. On trunk0, I have 3 VLANs (2,3,4) and on trunk1, I have 2 VLANs(10,11). I am running carp on each of these vlan interfaces. I am also running pfsync. I have an ipsec vpn configured which is using sasync between the two firewalls. We had fw1 kernel panic and die yesterday. Everything seemed to switch over as expected to fw2. When we restarted fw1, all carp interfaces switched back to master on fw1 and *most* switched to backup on fw2. However, carp2 (carp for vlan2) stayed master on fw2. This was obviously an issue because it was also master on fw1. This caused lots of dropped packets since two machines are claiming the same IP address. I ifconfig carp2 down'd the carp interface and traffic was passing as it should again. However, as soon as I ifconfig carp2 up'd the carp interface, the carp2 interface on fw2 went to master mode again, and carp2 on fw1 stayed master as well. I have all carp interfaces on fw2 configured with an advskew of 128 and I have preempt enabled. I had to reboot fw2 for things to go back to normal with all interfaces on fw2 in backup mode while all on fw1 were in master mode. Below are my hostname.* config files as well as the carp sysctl values. Please let me know if anyone needs more information or if you have any suggestions on how to avoid this in the future. === FW1 == ** hostname.em0 ** up ** hostname.em1 ** up ** hostname.em2 ** up ** hostname.em3 ** up ** hostname.trunk0 ** up trunkproto failover trunkport em0 trunkport em1 ** hostname.trunk1 ** up trunkproto failover trunkport em2 trunkport em3 ** hostname.vlan10 ** up inet x.x.x.27 255.255.255.248 NONE vlan 10 vlandev trunk1 ** hostname.vlan11 ** up inet x.x.x.131 255.255.255.248 NONE vlan 11 vlandev trunk1 ** hostname.vlan2 ** up inet 172.16.20.2 255.255.255.0 NONE vlan 2 vlandev trunk0 ** hostname.vlan3 ** up inet x.x.x.210 255.255.255.240 NONE vlan 3 vlandev trunk0 ** hostname.vlan4 ** up inet x.x.x.98 255.255.255.224 NONE vlan 4 vlandev trunk0 ** hostname.carp10 ** up inet x.x.x.26 255.255.255.248 x.x.x.31 vhid 10 pass xxx carpdev vlan10 ** hostname.carp11 ** up inet x.x.x.130 255.255.255.248 x.x.x.135 vhid 11 pass xx carpdev vlan11 ** hostname.carp2 ** up inet 172.16.20.1 255.255.255.0 172.16.20.255 vhid 2 pass x carpdev vlan2 ** hostname.carp3 ** up inet x.x.x.209 255.255.255.240 x.x.x.223 vhid 3 pass x carpdev vlan3 ** hostname.carp4 ** up inet x.x.x.97 255.255.255.224 x.x.x.127 vhid 4 pass x carpdev vlan4 ** hostname.pfsync0 ** up syncdev vlan2 syncpeer 172.16.20.3 === FW2 ** hostname.em0 ** up ** hostname.em1 ** up ** hostname.em2 ** up ** hostname.em3 ** up ** hostname.trunk0 ** up trunkproto failover trunkport em0 trunkport em1 ** hostname.trunk1 ** up trunkproto failover trunkport em2 trunkport em3 ** hostname.vlan10 ** up inet x.x.x.28 255.255.255.248 NONE vlan 10 vlandev trunk1 ** hostname.vlan11 ** up inet x.x.x.132 255.255.255.248 NONE vlan 11 vlandev trunk1 ** hostname.vlan2 ** up inet 172.16.20.3 255.255.255.0 NONE vlan 2 vlandev trunk0 ** hostname.vlan3 ** up inet x.x.x.213 255.255.255.240 NONE vlan 3 vlandev trunk0 ** hostname.vlan4 ** up inet x.x.x.99 255.255.255.224 NONE vlan 4 vlandev trunk0 ** hostname.carp10 ** up inet x.x.x 26 255.255.255.248 x.x.x 31 vhid 10 pass carpdev vlan10 advskew 128 ** hostname.carp11 ** up inet x.x.x 130 255.255.255.248 x.x.x 135 vhid 11 pass carpdev vlan11 advskew 128 ** hostname.carp2 ** up inet 172.16.20.1 255.255.255.0 172.16.20.255 vhid 2 pass carpdev vlan2 advskew 128 ** hostname.carp3 ** up inet x.x.x 209 255.255.255.240 x.x.x.223 vhid 3 carpdev vlan3 pass advskew 128 ** hostname.carp4 ** up inet x.x.x..97 255.255.255.224 x.x.x.127 vhid 4 pass carpdev vlan4 advskew 128 ** hostname.pfsync0 ** up syncdev vlan2 syncpeer 172.16.20.2
Re: dhclient could not allocate memory
On Thu, Feb 28, 2013 at 12:58 PM, Marc Peters wrote: > dhclient I've noticed a lot of dhclient changes in cvs over the past few weeks.You might try a newer snapshot. Chris
Re: OpenBGP Issues. :-(
Alex Mathiasen a écrit :
>Dear recipients,
>
>I have been using OpenBGP for a while with OpenBSD - And I am very
>satisfied
>with the performance and amazed by the ease of configuration.
>
>My BGPD is configured against a Danish ISP called TDC - And we were
>previously
>configured to receive a full routing table.
>
>However a few months ago I ran into an issue where my BGPD stopped
>working
>properly.
>
>It appeared the BGPD kept receiving the routing tables, and then start
>all
>over.
>
>Looking into the log files, it appeared BGPD received a certain route
>in the
>routing table, and then grumbled about the prefix, apparently for some
>reason
>the result was BGPD kept reloading when it reached this route. The
>result was
>of course my network was down.
>
>As TDC (My ISP) couldn't resolve which route that caused this issue
>(They told
>me: "That's what happened when you use third party software", so no
>help
>there...), we agreed that my connection would be set to Default
>candidate,
>instead of receiving a full routing table.
>
>So now I have configured a static route to forward all my traffic to
>this
>route. However this is not the result I wanted, as I am about to have
>one more
>connection, so I have 2 connections outbound.
>
>But the automatic failover switch / load balancing won't work, as long
>as I
>have my static route.
>
>This is why I want to go back to receiving a full routing table.
>
>Is there any way of configuring BGPD to ignore a specific route in case
>of
>"corrupted" prefix, so this won't happened again?
>
>I hope that some of you have an answer for this...
>
>Here you can see my bgpd.conf:
>
>AS
>router-id 000.000.000.000
>network 000.000.000.00/00
>
>neighbor 000.000.000.000 {
>remote-as
>descr TDC
>local-address 000.000.000.000
>passive
>holdtime180
>holdtime min3
>tcp md5sig password 00
>}
>
>log updates
Hi,
Please have a look in archives for a similar thread i did initiate.
Re: OpenBGP Issues. :-(
On 2013-02-28, Alex Mathiasen wrote: > Looking into the log files, it appeared BGPD received a certain route in the > routing table, and then grumbled about the prefix "grumbled about" is not very exact, actual log entries would be a lot more helpful. It would be even better if you could capture the actual update messages causing the problem (tcpdump -i em0 -w bgp.pcap -s 1500 port 179 and host $foo) > As TDC (My ISP) couldn't resolve which route that caused this issue (They told > me: "That's what happened when you use third party software", so no help > there...), Every BGP implementation has problems from time to time, IMHO anyone running this really needs to keep track of development of their chosen implementation/s (at least keep an eye on changelogs / cvs commits / mailing lists etc) and general network problems (nanog, local network operator groups, etc), and when they do have problems provide good information to the (vendor | developers | 3rd party support org). Also see everything that Benno wrote. :)
dhclient could not allocate memory
Hi misc, i am using OpenBSD on my home router connected to cable internet. A re nic is facing the wild and gets its public IP via DHCP from my ISP. I have running a 5.3-beta from Feb. 1st, as this one has the powersaving fix for athn in HostAP (realised it then, was committed already in August). This router was running happily 5.2-RELEASE until then, 24/7, without any issues. However, this night dhclient died unexpectedly and /var/log/daemon says: Feb 27 22:05:56 router dhclient[22805]: sysctl retrieval of routes: Cannot allocate memory Feb 27 22:05:56 router dhclient[10969]: dispatch_imsg in main: pipe closed dhclient gone and with it my internet connection, too. I wonder, what could have caused this. The machine has two AMD APUs and 8GB of memory (dmesg attached) and dhclient shouldn't run out of it (and it had no issues like that before with 5.1 and 5.2), but maybe i am totally wrong and looking in the wrong place at all. I know that Realtek cards have had a great history (joking!) and i try to avoid them, but this one is onboard and Intel NICs with double interfaces aren't as cheap as the PCIe one port desktop grade card i already added. mbufs are also unremarkable: marc@router ~ $ netstat -m 133 mbufs in use: 87 mbufs allocated to data 14 mbufs allocated to packet headers 32 mbufs allocated to socket names and addresses 22/356/6144 mbuf 2048 byte clusters in use (current/peak/max) 64/73/6144 mbuf 4096 byte clusters in use (current/peak/max) 0/8/6144 mbuf 8192 byte clusters in use (current/peak/max) 0/8/6144 mbuf 9216 byte clusters in use (current/peak/max) 0/8/6144 mbuf 12288 byte clusters in use (current/peak/max) 0/8/6144 mbuf 16384 byte clusters in use (current/peak/max) 0/8/6144 mbuf 65536 byte clusters in use (current/peak/max) 1284 Kbytes allocated to network (25% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Maybe someone can shed some light on it and knows which knob to turn. Cheers, Marc Uptime provided for reference, not measurement of private parts ;) marc@router ~ $ uptime 6:54PM up 24 days, 2:41, 1 user, load averages: 0.24, 0.19, 0.1 dmesg: OpenBSD 5.3-beta (GENERIC.MP) #25: Fri Feb 1 16:29:00 MST 2013 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8167034880 (7788MB) avail mem = 7927136256 (7559MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeaf40 (52 entries) bios0: vendor American Megatrends Inc. version "0306" date 08/18/2011 bios0: ASUSTeK Computer INC. E45M1-I DELUXE acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT acpi0: wakeup devices SBAZ(S4) PS2K(S4) PS2M(S4) UAR1(S4) P0PC(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) RLAN(S4) PE22(S4) PE23(S4) BR14(S4) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD E-450 APU with Radeon(tm) HD Graphics, 1650.36 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD E-450 APU with Radeon(tm) HD Graphics, 1649.90 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic0: misconfigured as apic 3, remapped to apid 0 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (PE20) acpiprt2 at acpi0: bus 4 (PE21) acpiprt3 at acpi0: bus -1 (PE22) acpiprt4 at acpi0: bus -1 (PE23) acpiprt5 at acpi0: bus -1 (BR15) acpiprt6 at acpi0: bus -1 (PCE6) acpiprt7 at acpi0: bus -1 (PCE7) acpiprt8 at acpi0: bus -1 (PCE8) acpiprt9 at acpi0: bus 1 (BR14) acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpibtn0 at acpi0: PWRB cpu0: 1650 MHz: speeds: 1650 1320 825 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00 vga1 at pci0 dev 1 function 0 "ATI Radeon HD 6320" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: a
Re: no sound azalia(4)
On 02/28/13 18:33, Alexandre Ratchov wrote: On Thu, Feb 28, 2013 at 06:19:14PM +0100, Martijn van Duren wrote: On 02/28/13 09:53, Alexandre Ratchov wrote: as Jan said, the sound card is getting the signal; but according to the mixerctl output, your card has 3 independent stereo dacs, so you could try to kill sndiod and start it as follows: sudo sndiod -dd -c0:5 to force it to send the signal to all outputs (hopefully the speaker is one of them). Then try to play any audio file. It should display: $ sndiod -dd -c0:5 snd0.default: rec=0:1 play=0:5 vol=5931520 dup snd0: 48000Hz, s24le4msb, play 0:5, rec 0:1, 2 blocks of 960 frames ogg0: 48000Hz, s16le, play 0:1, 10 blocks of 960 frames snd0: device started (note the second "play 0:5" string). As we're at it, crank the volume of all dacs to the maximum, just in case the sound is not loud enough: mixerctl inputs.dac-0:1=255 mixerctl inputs.dac-2:3=255 mixerctl inputs.dac-4:5=255 If you have headphones or an amp, try all output jacks to figure out if at least one is getting the signal. HTH -- Alexandre This helped. Major thanks. Is there any way to make this permanent? you could add: sndiod_flags="-c0:5" in your rc.conf.local and possibly add, if necessary, the mixer adjustments in mixerctl.conf And is there any way to achieve working defaults? this would require to figure out why the sound card doesn't expose the speakers dac. Is there any way I can help with this? any way to produce some helpful debugging output, trying patches, etc? -- Alexandre
Re: no sound azalia(4)
On Thu, Feb 28, 2013 at 06:19:14PM +0100, Martijn van Duren wrote: > On 02/28/13 09:53, Alexandre Ratchov wrote: > >as Jan said, the sound card is getting the signal; but according to > >the mixerctl output, your card has 3 independent stereo dacs, so > >you could try to kill sndiod and start it as follows: > > > > sudo sndiod -dd -c0:5 > > > >to force it to send the signal to all outputs (hopefully the > >speaker is one of them). Then try to play any audio file. It should > >display: > > > >$ sndiod -dd -c0:5 > >snd0.default: rec=0:1 play=0:5 vol=5931520 dup > >snd0: 48000Hz, s24le4msb, play 0:5, rec 0:1, 2 blocks of 960 frames > >ogg0: 48000Hz, s16le, play 0:1, 10 blocks of 960 frames > >snd0: device started > > > >(note the second "play 0:5" string). As we're at it, crank the > >volume of all dacs to the maximum, just in case the sound is not > >loud enough: > > > >mixerctl inputs.dac-0:1=255 > >mixerctl inputs.dac-2:3=255 > >mixerctl inputs.dac-4:5=255 > > > >If you have headphones or an amp, try all output jacks to figure > >out if at least one is getting the signal. > > > >HTH > > > >-- Alexandre > > > > This helped. Major thanks. > Is there any way to make this permanent? you could add: sndiod_flags="-c0:5" in your rc.conf.local and possibly add, if necessary, the mixer adjustments in mixerctl.conf > And is there any way to achieve working defaults? this would require to figure out why the sound card doesn't expose the speakers dac. -- Alexandre
Re: no sound azalia(4)
On 02/28/13 09:53, Alexandre Ratchov wrote: as Jan said, the sound card is getting the signal; but according to the mixerctl output, your card has 3 independent stereo dacs, so you could try to kill sndiod and start it as follows: sudo sndiod -dd -c0:5 to force it to send the signal to all outputs (hopefully the speaker is one of them). Then try to play any audio file. It should display: $ sndiod -dd -c0:5 snd0.default: rec=0:1 play=0:5 vol=5931520 dup snd0: 48000Hz, s24le4msb, play 0:5, rec 0:1, 2 blocks of 960 frames ogg0: 48000Hz, s16le, play 0:1, 10 blocks of 960 frames snd0: device started (note the second "play 0:5" string). As we're at it, crank the volume of all dacs to the maximum, just in case the sound is not loud enough: mixerctl inputs.dac-0:1=255 mixerctl inputs.dac-2:3=255 mixerctl inputs.dac-4:5=255 If you have headphones or an amp, try all output jacks to figure out if at least one is getting the signal. HTH -- Alexandre This helped. Major thanks. Is there any way to make this permanent? And is there any way to achieve working defaults?
intel X driver shared memory size
Cannot say for all sandybridge chips, but for intel g550 with 2000 integrated graphics, memory size should not be set over 128 mb. As far as <128, works. Best regards Zoran
Re: OpenBGP Issues. :-(
Alex Mathiasen(a...@mira.dk) on 2013.02.28 14:51:25 +0100: > Dear recipients, > > I have been using OpenBGP for a while with OpenBSD - And I am very satisfied > with the performance and amazed by the ease of configuration. > > My BGPD is configured against a Danish ISP called TDC - And we were previously > configured to receive a full routing table. > > However a few months ago I ran into an issue where my BGPD stopped working > properly. Was this in November by any chance? > It appeared the BGPD kept receiving the routing tables, and then start all > over. > > Looking into the log files, it appeared BGPD received a certain route in the > routing table, and then grumbled about the prefix, apparently for some reason > the result was BGPD kept reloading when it reached this route. The result was > of course my network was down. > > As TDC (My ISP) couldn't resolve which route that caused this issue (They told > me: "That's what happened when you use third party software", so no help > there...), we agreed that my connection would be set to Default candidate, > instead of receiving a full routing table. > > So now I have configured a static route to forward all my traffic to this > route. However this is not the result I wanted, as I am about to have one more > connection, so I have 2 connections outbound. > > But the automatic failover switch / load balancing won't work, as long as I > have my static route. > > This is why I want to go back to receiving a full routing table. > > Is there any way of configuring BGPD to ignore a specific route in case of > "corrupted" prefix, so this won't happened again? No there is not such a feature, and the bgp protocol mandates session teardown in certain cases anyway. Your report lacks a few details, please send with dmesg next time. And your bgpd.conf is not valid. My guess is that your problem is fixed by the patch available on http://www.openbsd.org/errata52.html You could also update to -current. /Benno
Re: OpenBGP Issues. :-(
Alex Mathiasen [a...@mira.dk] wrote: > > It appeared the BGPD kept receiving the routing tables, and then start all > over. > You don't mention which version of openbsd you are using. There are some problems like this in older versions of bgpd which are now fixed. You may want to try a new snapshot.
OpenBGP Issues. :-(
Dear recipients,
I have been using OpenBGP for a while with OpenBSD - And I am very satisfied
with the performance and amazed by the ease of configuration.
My BGPD is configured against a Danish ISP called TDC - And we were previously
configured to receive a full routing table.
However a few months ago I ran into an issue where my BGPD stopped working
properly.
It appeared the BGPD kept receiving the routing tables, and then start all
over.
Looking into the log files, it appeared BGPD received a certain route in the
routing table, and then grumbled about the prefix, apparently for some reason
the result was BGPD kept reloading when it reached this route. The result was
of course my network was down.
As TDC (My ISP) couldn't resolve which route that caused this issue (They told
me: "That's what happened when you use third party software", so no help
there...), we agreed that my connection would be set to Default candidate,
instead of receiving a full routing table.
So now I have configured a static route to forward all my traffic to this
route. However this is not the result I wanted, as I am about to have one more
connection, so I have 2 connections outbound.
But the automatic failover switch / load balancing won't work, as long as I
have my static route.
This is why I want to go back to receiving a full routing table.
Is there any way of configuring BGPD to ignore a specific route in case of
"corrupted" prefix, so this won't happened again?
I hope that some of you have an answer for this...
Here you can see my bgpd.conf:
AS
router-id 000.000.000.000
network 000.000.000.00/00
neighbor 000.000.000.000 {
remote-as
descr TDC
local-address 000.000.000.000
passive
holdtime180
holdtime min3
tcp md5sig password 00
}
log updates
Re: BSD-friedly companies producing embedded x86 computers
Congatec, although I don't know about BSD-friendly. They are at least, Linux friendly. Might look into it. On Mon, Feb 25, 2013 at 12:09 PM, Voland Levit wrote: > I know about Soekris and Alix. Please tell me if there is anyone else > worthy > of attention. > > Thanks!
Re: ZTE mf626 USB modem support
On 2013-02-28, Maximo Pech wrote: > The patch that Stuart provided worked for my ZTE MF668 device. > > I got this on dmesg: > > umsm0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated > ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2 > umsm0 detached > umsm0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated > ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2 > ucom0 at umsm0 > umsm1 at uhub0 port 3 configuration 1 interface 1 "ZTE,Incorporated > ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2 > ucom1 at umsm1 > umsm2 at uhub0 port 3 configuration 1 interface 2 "ZTE,Incorporated > ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2 > ucom2 at umsm2 > umsm3 at uhub0 port 3 configuration 1 interface 3 "ZTE,Incorporated > ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2 > > I think when it says "umsm0 detached" is when it does the mode > switching because it didn't appear before and also the device takes a > few seconds more to be ready. > > Thanks for all the help. > > Problem with this patch is that it breaks another device with the same vendor/product ID, ZTE K3565-Z.
Re: /tmp/aucat*
On Feb 28 09:31:06, a...@caoua.org wrote:
> On Wed, Feb 27, 2013 at 08:47:20PM +0100, Jan Stary wrote:
> >
> > The audio plays fine, but why is this:
> >
> > /tmp/aucat-1000/aucat0: No such file or directory
> >
> > Indeed, there is no /tmp/aucat-1000/aucat0 (1000 is my userid),
> > but there is /tmp/aucat/aucat0; is this something from the
> > past of sndio, when it used userid in the socket name?
>
> programs using libsndio try to connect to the per-user sndiod
> server first, then the system-wide server. This allows any regular
> user with no root privileges to bypass the system-wide server and
> use her/his own setup.
Thanks for the explanation. Can we slightly
unconfuse the DEBUGing user with the diff below?
Index: aucat.c
===
RCS file: /cvs/src/lib/libsndio/aucat.c,v
retrieving revision 1.56
diff -u -p -r1.56 aucat.c
--- aucat.c 23 Nov 2012 07:03:28 - 1.56
+++ aucat.c 28 Feb 2013 09:07:55 -
@@ -361,6 +361,7 @@ aucat_connect_un(struct aucat *hdl, unsi
break;
}
hdl->fd = s;
+ DPRINTF("%s: connected\n", ca.sun_path);
return 1;
}
The DEBUGing output then becomes
/tmp/aucat-1000/aucat0: No such file or directory
/tmp/aucat/aucat0: connected
(Should something similar go to aucat_connect_tcp() as well?)
Jan
Re: Changing Architecture from amd64 to i386
ch...@nmedia.net (Chris Cappuccio), 2013.02.27 (Wed) 20:57 (CET): > Jes [jjje...@gmail.com] wrote: > > In my experience it's perfectly possible to move from one > > architecture to another one. > > > > I do the following: > > > > - backup /etc (only for security) > > - remove all installed packages (I save a list of installed packages > > to figure out what to install again after) > > - sysmerge for etc and xetc > > - update the system with the new architecture (update, not install) > > - adjust $PKG_PATH and reinstall packages deinstalled at the > > beginning, or new ones of your election. > > > > No major problems detected. > > > > one more step to add: delete old binaries (including previous versions of > shared libs) + PostgreSQL dump/restore (that one bit me once when going from i386 to amd64, there are probably others...) Bye, Marcus > !DSPAM:512e656f308021576019301!
Re: no sound azalia(4)
as Jan said, the sound card is getting the signal; but according to the mixerctl output, your card has 3 independent stereo dacs, so you could try to kill sndiod and start it as follows: sudo sndiod -dd -c0:5 to force it to send the signal to all outputs (hopefully the speaker is one of them). Then try to play any audio file. It should display: $ sndiod -dd -c0:5 snd0.default: rec=0:1 play=0:5 vol=5931520 dup snd0: 48000Hz, s24le4msb, play 0:5, rec 0:1, 2 blocks of 960 frames ogg0: 48000Hz, s16le, play 0:1, 10 blocks of 960 frames snd0: device started (note the second "play 0:5" string). As we're at it, crank the volume of all dacs to the maximum, just in case the sound is not loud enough: mixerctl inputs.dac-0:1=255 mixerctl inputs.dac-2:3=255 mixerctl inputs.dac-4:5=255 If you have headphones or an amp, try all output jacks to figure out if at least one is getting the signal. HTH -- Alexandre
Re: /tmp/aucat*
On Wed, Feb 27, 2013 at 08:47:20PM +0100, Jan Stary wrote: > > The audio plays fine, but why is this: > > /tmp/aucat-1000/aucat0: No such file or directory > > Indeed, there is no /tmp/aucat-1000/aucat0 (1000 is my userid), > but there is /tmp/aucat/aucat0; is this something from the > past of sndio, when it used userid in the socket name? programs using libsndio try to connect to the per-user sndiod server first, then the system-wide server. This allows any regular user with no root privileges to bypass the system-wide server and use her/his own setup. The "aucat" string is from the past and should probably be renamed to "sndio". -- Alexandre
