pulseaudo RTP Streeming was broken

[pulseaudio pulseaudio]

I tried to use pulseaudo for remote desktop.ofcouse X11 remote desktop is
work fine.I need a sound for remote browsing.š/etc/pulse/default.paload-module
module-rtp-recv sap_address=127.0.0.1
load-module module-null-sink sink_name=rtp format=s16be channels=2
rate=44100 sink_properties="device.description='RTP Multicast Sink'"
load-module module-rtp-send source=rtp.monitor destination_ip=127.0.0.1
port=46998 loop=1#or load-module module-rtp-send 
source=rtp.monitorset-default-sink
rtpšš#dopulseaudio
E: [(null)] module-rtp-send.c: IP_MULTICAST_LOOP failed: Invalid argument
E: [(null)] module.c: Failed to load module "module-rtp-send" (argument:
"source=rtp.monitor destination_ip=127.0.0.1 port=46998 loop=1"):
initialization failed.
E: [(null)] main.c: Module load failed.
E: [(null)] main.c: Failed to initialize daemon.

I tried "load-module module-rtp-send source=rtp.monitor" by default.same
error.pulseaudio
E: [(null)] module-rtp-send.c: IP_MULTICAST_LOOP failed: Invalid argument
E: [(null)] module.c: Failed to load module "module-rtp-send" (argument:
"source=rtp.monitor"): initialization failed.
E: [(null)] main.c: Module load failed.
E: [(null)] main.c: Failed to initialize daemon.šplease help.

Re: Routing issue with multiple interface on the same network.

[sven falempin]

i do not think it is.
it makes no sense to have the same network on two interface, this way, IMHO.

On Fri, Apr 22, 2016 at 1:25 PM, Jean-Daniel Dupas 
wrote:

> Hello,
>
> I'm trying to configure a machine with multiple interface on the same
> network
> (one standard interface and one carp interface).
>
> My problem is that if I set the default routing table to the second
> interface,
> the system can't find it and return "no route" for any distant  address
> resolution.
>
> The problem occurs even when using to standard iface (so carp is not
> involved).
>
> Note that my configuration works perfectly well on OpenBSD 5.7. I did test
> the
> problem with 5.9 and current, and both fail.
>
>
> Here is my configuration:
>
> --- ifconfig
> lo0: flags=8049 mtu 32768
> priority: 0
> groups: lo
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
> inet 127.0.0.1 netmask 0xff00
> vio0: flags=8843 mtu 1500
> lladdr 52:54:00:9e:b2:2b
> priority: 0
> media: Ethernet autoselect
> status: active
> inet 10.0.1.2 netmask 0x broadcast 10.0.255.255
> vio1: flags=8843 mtu 1500
> lladdr 52:54:00:fd:df:4c
> priority: 0
> media: Ethernet autoselect
> status: active
> inet 192.168.0.11 netmask 0xff00 broadcast 192.168.0.255
> vio2: flags=8843 mtu 1500
> lladdr 52:54:00:d0:e8:1d
> priority: 0
> groups: egress
> media: Ethernet autoselect
> status: active
> inet 192.168.0.12 netmask 0xff00 broadcast 192.168.0.255
>
>
> --- route -n show
> Routing tables
>
> Internet:
> DestinationGatewayFlags   Refs  Use   Mtu  Prio
> Iface
> default192.168.0.1UGS0   46 - 8
> vio2
> 10.0/1610.0.1.2   UC 3   26 - 4
> vio0
> 10.0.0.1   00:00:5e:00:01:01  UHLc   0   59 - 4
> vio0
> 10.0.1.2   52:54:00:9e:b2:2b  UHLl   0   34 - 1
> vio0
> 10.0.1.15  52:54:00:0e:62:c7  UHLc   0   16 - 4
> vio0
> 10.0.3.10  ac:87:a3:1d:3f:9d  UHLc   1   16 - 4
> vio0
> 10.0.255.255   10.0.1.2   UHb00 - 1
> vio0
> 127.0.0.1  127.0.0.1  UHl0  192 32768 1 lo0
> 192.168.0/24   192.168.0.11   UCP17 - 4
> vio1
> 192.168.0/24   192.168.0.12   UCP00 - 4
> vio2
> 192.168.0.1link#2 UHLc   0   25 - 4
> vio1
> 192.168.0.11   52:54:00:fd:df:4c  UHLl   0   16 - 1
> vio1
> 192.168.0.12   52:54:00:d0:e8:1d  UHLl   03 - 1
> vio2
> 192.168.0.255  192.168.0.11   UHPb   00 - 1
> vio1
> 192.168.0.255  192.168.0.12   UHPb   00 - 1
> vio2
>
> Internet6:
> DestinationGatewayFlags
>  Refs
> Use   Mtu  Prio Iface
> ::1::1UHl
>   0
> 0 32768 1 lo0
> fe80::1%lo0fe80::1%lo0UHl
>   0
> 0 32768 1 lo0
> ff01::%lo0/32  ::1UC
>0
> 1 32768 4 lo0
> ff02::%lo0/32  ::1UC
>0
> 1 32768 4 lo0
>
>
> -- ping 8.8.8.8
> PING 8.8.8.8 (8.8.8.8): 56 data bytes
> ping: sendto: No route to host
> ping: wrote 8.8.8.8 64 chars, ret=-1
> ping: sendto: No route to host
> ping: wrote 8.8.8.8 64 chars, ret=-1
> --- 8.8.8.8 ping statistics ---
> 2 packets transmitted, 0 packets received, 100.0% packet loss
> [1]81614 exit 1 ping 8.8.8.8
>
> If I change the default route to vio1, it works. The problem occurs only
> when
> the default route is on the second interface (vio2, or carp0 in my cases).
>
> Can someone confirm this is a bug in the routing system ?
>
> Regards
> Jean-Daniel.
>
>

-- 
-
() ascii ribbon campaign - against html e-mail
/\

Routing issue with multiple interface on the same network.

[Jean-Daniel Dupas]

Hello,

I'm trying to configure a machine with multiple interface on the same network
(one standard interface and one carp interface).

My problem is that if I set the default routing table to the second interface,
the system can't find it and return "no route" for any distant  address
resolution.

The problem occurs even when using to standard iface (so carp is not
involved).

Note that my configuration works perfectly well on OpenBSD 5.7. I did test the
problem with 5.9 and current, and both fail.


Here is my configuration:

--- ifconfig
lo0: flags=8049 mtu 32768
priority: 0
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
inet 127.0.0.1 netmask 0xff00
vio0: flags=8843 mtu 1500
lladdr 52:54:00:9e:b2:2b
priority: 0
media: Ethernet autoselect
status: active
inet 10.0.1.2 netmask 0x broadcast 10.0.255.255
vio1: flags=8843 mtu 1500
lladdr 52:54:00:fd:df:4c
priority: 0
media: Ethernet autoselect
status: active
inet 192.168.0.11 netmask 0xff00 broadcast 192.168.0.255
vio2: flags=8843 mtu 1500
lladdr 52:54:00:d0:e8:1d
priority: 0
groups: egress
media: Ethernet autoselect
status: active
inet 192.168.0.12 netmask 0xff00 broadcast 192.168.0.255


--- route -n show
Routing tables

Internet:
DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
default192.168.0.1UGS0   46 - 8 vio2
10.0/1610.0.1.2   UC 3   26 - 4 vio0
10.0.0.1   00:00:5e:00:01:01  UHLc   0   59 - 4 vio0
10.0.1.2   52:54:00:9e:b2:2b  UHLl   0   34 - 1 vio0
10.0.1.15  52:54:00:0e:62:c7  UHLc   0   16 - 4 vio0
10.0.3.10  ac:87:a3:1d:3f:9d  UHLc   1   16 - 4 vio0
10.0.255.255   10.0.1.2   UHb00 - 1 vio0
127.0.0.1  127.0.0.1  UHl0  192 32768 1 lo0
192.168.0/24   192.168.0.11   UCP17 - 4 vio1
192.168.0/24   192.168.0.12   UCP00 - 4 vio2
192.168.0.1link#2 UHLc   0   25 - 4 vio1
192.168.0.11   52:54:00:fd:df:4c  UHLl   0   16 - 1 vio1
192.168.0.12   52:54:00:d0:e8:1d  UHLl   03 - 1 vio2
192.168.0.255  192.168.0.11   UHPb   00 - 1 vio1
192.168.0.255  192.168.0.12   UHPb   00 - 1 vio2

Internet6:
DestinationGatewayFlags   Refs
Use   Mtu  Prio Iface
::1::1UHl0
0 32768 1 lo0
fe80::1%lo0fe80::1%lo0UHl0
0 32768 1 lo0
ff01::%lo0/32  ::1UC 0
1 32768 4 lo0
ff02::%lo0/32  ::1UC 0
1 32768 4 lo0


-- ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: No route to host
ping: wrote 8.8.8.8 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote 8.8.8.8 64 chars, ret=-1
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
[1]81614 exit 1 ping 8.8.8.8

If I change the default route to vio1, it works. The problem occurs only when
the default route is on the second interface (vio2, or carp0 in my cases).

Can someone confirm this is a bug in the routing system ?

Regards
Jean-Daniel.

Re: 5.9 discs in the wild. Europe/Germany

[Solène Rapenne]

Received in France today !

Thanks you for all of this ! :)

Re: Apr 4th amd64 snapshot problems, SOLVED

[Chris Bennett]

On Tue, Apr 12, 2016 at 05:34:36PM -0500, Chris Bennett wrote:
> I have successfully installed this snap on an old 1GB flash drive and it
> boots and can install packages.
> Happy to know that the snap and my computer work fine together.
> 
> Proper dmesg:
> Oops, just noticed I need to reboot for firmware. Will send this anyway.
> 
> Chris Bennett
> 
> OpenBSD 5.9-current (GENERIC.MP) #1983: Mon Apr  4 21:50:41 MDT 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Problem solved using this snapshot:

OpenBSD 5.9-current (GENERIC.MP) #1996: Wed Apr 20 14:57:08 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Can't use sshfs as user

[Thuban]

Hi,
I try to mount a directory with sshfs as non-root, but I get the
following error :

fuse_mount: Permission denied

I don't get it. I have "kern.usermount=1" in /etc/sysctl.conf, but
according to [1] I need to use some option about uid. But which ones?

Regards.

[1] :
http://openbsd-archive.7691.n7.nabble.com/sshfs-as-non-root-fuse-mount-Permis
sion-denied-td253224.html
--
/Thuban/

[demime 1.01d removed an attachment of type application/pgp-signature which had 
a name of signature.asc]

Re: Unable to boot on APU2C4

[Bryan C. Everly]

Much appreciated Stefan.  I'm up and running with this little rig and
am quite impressed.

Thanks,
Bryan


On Fri, Apr 22, 2016 at 9:19 AM, Kapfhammer, Stefan  wrote:
> Hello Bryan, hello Christer,
>
> what I forgot to mention:
> During installation process you are asked wheather you
> want the default console to be set to 'com0'.
> Let it stand at 'com0' (or answer 'yes'?!)
>
> In case you misconfigured your network, you will still
> be able to access your APU2 via serial console, without
> typing the commands for 'stty' and 'set' manually.
> Sometimes after a long time from install on, they
> are simply forgotten ...
>
> Regards,
> Stefan
>
>
> -Ursprüngliche Nachricht-
> Von: Bryan C. Everly [mailto:br...@bceassociates.com]
> Gesendet: Freitag, 22. April 2016 14:42
> An: Christer Solskogen 
> Cc: Kapfhammer, Stefan ; misc 
> Betreff: Re: Unable to boot on APU2C4
>
> Thank you so much. Worked perfectly.
>
> Thanks,
> Bryan
>
>
> On Thu, Apr 21, 2016 at 4:40 PM, Christer Solskogen
 wrote:
>> On Thu, Apr 21, 2016 at 9:23 PM, Kapfhammer, Stefan 
wrote:
>>> You have to type at boot prompt:
>>> stty com0 115200
>>> set tty com0
>>> boot /bsd.rd
>>>
>>
>> Aha, much better.
>> Thanks!

Re: Unable to boot on APU2C4

[Kapfhammer, Stefan]

Hello Bryan, hello Christer,

what I forgot to mention:
During installation process you are asked wheather you
want the default console to be set to 'com0'.
Let it stand at 'com0' (or answer 'yes'?!)

In case you misconfigured your network, you will still
be able to access your APU2 via serial console, without
typing the commands for 'stty' and 'set' manually.
Sometimes after a long time from install on, they
are simply forgotten ...

Regards,
Stefan


-Ursprüngliche Nachricht-
Von: Bryan C. Everly [mailto:br...@bceassociates.com]
Gesendet: Freitag, 22. April 2016 14:42
An: Christer Solskogen 
Cc: Kapfhammer, Stefan ; misc 
Betreff: Re: Unable to boot on APU2C4

Thank you so much. Worked perfectly.

Thanks,
Bryan


On Thu, Apr 21, 2016 at 4:40 PM, Christer Solskogen
 wrote:
> On Thu, Apr 21, 2016 at 9:23 PM, Kapfhammer, Stefan  wrote:
>> You have to type at boot prompt:
>> stty com0 115200
>> set tty com0
>> boot /bsd.rd
>>
>
> Aha, much better.
> Thanks!

[demime 1.01d removed an attachment of type application/pkcs7-signature which 
had a name of smime.p7s]

Re: Unable to boot on APU2C4

[Bryan C. Everly]

Thank you so much. Worked perfectly.

Thanks,
Bryan


On Thu, Apr 21, 2016 at 4:40 PM, Christer Solskogen
 wrote:
> On Thu, Apr 21, 2016 at 9:23 PM, Kapfhammer, Stefan  wrote:
>> You have to type at boot prompt:
>> stty com0 115200
>> set tty com0
>> boot /bsd.rd
>>
>
> Aha, much better.
> Thanks!

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

[Nick Holland]

On 04/21/16 21:25, Ultramedia Libertad wrote:
> hello
> 
> I am upgrade OpenBSD 5.8 to 5.9 and after to reboot
> 
> i have follow errors in remote console :

...[deleting big block of blank lines]...

> *init: daemon: unknown class (failed)syslogdsu: daemon: unknown class
> (failed)pflogdsu: daemon: unknown class (failed)ntpdsu: daemon: unknown
> class (failed)starting RPC daemons:.savecore: no core dumpcheckin quotas:
> done.clearing /tmpkern.securelevel: 0 -> 1creating runtime link editor
> directory cache.preserving editor files.startings networks daemons: sshdsu:
> daemon: unknown class (failed)smtpdsu: daemon: unknown class
> (failed)sndiodsu: daemon: unknown class (failed).Thu apr 21 20:06:24
> CDI 2016*
> 
> 
> y more
> 
> please help me attach image

both the lists and I block images images...

> [demime 1.01d removed an attachment of type image/png which had a name of 
> Screenshot_2016-04-21_21-14-18.png]
> 

sounds like somewhere along the line you deleted or mangled your
/etc/login.conf file.  I'm guessing it had nothing to do with the
upgrade, but probably more with the reboot (i.e., you hosed the file
some time ago, if you had rebooted without an upgrade, you would have
seen the same problem).

sysmerge may help.

Nick.

Re: upgrade OpenBSD 5.8 to 5.9 daemon: unknown class

[Daniel Gillen]

On 22.04.2016 03:25, Ultramedia Libertad wrote:
> hello
> 
> I am upgrade OpenBSD 5.8 to 5.9 and after to reboot
> 
> i have follow errors in remote console :
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *init: daemon: unknown class (failed)syslogdsu: daemon: unknown class
> (failed)pflogdsu: daemon: unknown class (failed)ntpdsu: daemon: unknown
> class (failed)starting RPC daemons:.savecore: no core dumpcheckin quotas:
> done.clearing /tmpkern.securelevel: 0 -> 1creating runtime link editor
> directory cache.preserving editor files.startings networks daemons: sshdsu:
> daemon: unknown class (failed)smtpdsu: daemon: unknown class
> (failed)sndiodsu: daemon: unknown class (failed).Thu apr 21 20:06:24
> CDI 2016*
> 
> 
> y more
> 
> please help me attach image
> 
> --
> editor de sueños
> 
> [demime 1.01d removed an attachment of type image/png which had a name of 
> Screenshot_2016-04-21_21-14-18.png]
> 

Could it have something to do with a damaged /etc/login.conf file?

Can you please post the content of that file.

-- 
Unix _IS_ user friendly - it's just
selective about who its friends are!

ehci: port reset timeout

[Kirill]

after some manipulations (assign address and ping it) with the urndis
device and unplug it usb port stops work.

dmesg  
OpenBSD 5.9-stable (GENERIC.MP) #0: Mon Apr 18 13:50:24 MSK 2016
r...@work.nightbbs.ru:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2056990720 (1961MB)
avail mem = 1990508544 (1898MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe9f80 (85 entries)
bios0: vendor Hewlett-Packard version "786G1 v01.08" date 08/25/2008
bios0: Hewlett-Packard HP Compaq dc7900 Small Form Factor
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC ASF! MCFG TCPA SLIC HPET DMAR
acpi0: wakeup devices COM1(S4) COM2(S4) PCI0(S4) PEG1(S4) PEG2(S4)
IGBE(S4) PCX1(S4) PCX2(S4) PCX5(S4) PCX6(S4) HUB_(S4) USB1(S3) USB2(S3)
USB3(S3) USB4(S3) USB5(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3159.18 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 6MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 332MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3158.72 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 6MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf400, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG1)
acpiprt2 at acpi0: bus -1 (PEG2)
acpiprt3 at acpi0: bus 32 (PCX1)
acpiprt4 at acpi0: bus -1 (PCX2)
acpiprt5 at acpi0: bus 48 (PCX5)
acpiprt6 at acpi0: bus -1 (PCX6)
acpiprt7 at acpi0: bus 7 (HUB_)
acpicpu0 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1)
acpicpu1 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1)
acpibtn0 at acpi0: PBTN
cpu0: unknown Enhanced SpeedStep CPU, msr 0x0616492206004922
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 3159 MHz: speeds: 24333, 2000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel Q45 Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0: msi
inteldrm0: 1280x1024
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel Q45 Video" rev 0x03 at pci0 dev 2 function 1 not configured
"Intel Q45 HECI" rev 0x03 at pci0 dev 3 function 0 not configured
pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA
(unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI
pciide0: using apic 1 int 18 for native-PCI interrupt
pciide0: channel 0 ignored (not responding; disabled or no drives?)
pciide0: channel 1 ignored (not responding; disabled or no drives?)
puc0 at pci0 dev 3 function 3 "Intel Q45 KT" rev 0x03: ports: 1 com
com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo
com4: probed fifo depth: 15 bytes
em0 at pci0 dev 25 function 0 "Intel ICH10 D BM LM" rev 0x02: msi,
address 00:23:7d:4e:a2:5c
uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20
uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22
ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 22
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801JD HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1884A
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801JD PCIE" rev 0x02: msi
pci1 at ppb0 bus 32
ppb1 at pci0 dev 28 function 4 "Intel 82801JD PCIE" rev 0x02: msi
pci2 at ppb1 bus 48
uhci3 at pci0 dev 29 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20
uhci4 at pci0 dev 29 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21
uhci5 at pci0 dev 29 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22
ehci1 at pci0 dev 29 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 20
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xa2
pci3 at ppb2 bus 7
pcib0 at pci0 dev 31 

Re: 5.9 discs in the wild. Portugal/Lisbon

[Pedro Caetano]

CDs just arrived in Lisbon, Portugal.

Thank you for the tireless effort to get this release out!

BR,
Pedro Caetano

Re: Firefox Crashes; slow xfce

[Guillaume Simon]

Unless your current user is in the daemon login class (which is
unlikely), it shouldn't.
Have a look to the manual page of login.conf(5) to understand how it works.
When you edit your login.conf, you have to login again for your
modifications to take effect.
It may explain a difference between the theorical value of your
login.conf file, and the real current value.


Le 04/20/16 18:29, Daniel Boyd a écrit :
> openfiles-cur is set to 128 under daemon in my login.conf.  Could that be
> affecting it?
>
> On Wed, Apr 20, 2016 at 10:51 AM, Guillaume Simon <
> guillaume.si...@mailoo.org> wrote:
>
>> Your nofiles(descriptors) may be too low.
>> You should consider increasing it to 512 or more
>> The weird thing is it doesn't match the "openfiles-cur" of your default
>> login class (2048, according to your first email).
>>
>> Le 04/20/16 16:41, Daniel Boyd a écrit :
>>> $ ulimit -a
>>> time(cpu-seconds)unlimited
>>> file(blocks) unlimited
>>> coredump(blocks) unlimited
>>> data(kbytes) 3584000
>>> stack(kbytes)4096
>>> lockedmem(kbytes)2701637
>>> memory(kbytes)   8101908
>>> nofiles(descriptors) 128
>>> processes256

Re: umsm(4) for Sierra Wireless EM7455 in ThinkPad X260

[Stuart Henderson]

On 2016-04-21, Bryan Vyhmeister  wrote:
> Assuming MBIM is something that would be worked on, would it make sense
> to extend umsm(4) to support it or would it make more sense to have a
> new driver like umbim(4) or something?

It provides a network-type interface rather than a serial interface,
so wouldn't be part of umsm(4). Conceptually it's closer to (but isn't
compatible with) cdce or urndis.