Re: ix0: CRITICAL: EXTERNAL PHY OVER TEMP!!
Predrag Punosevac wrote: > Hi, > > I am having an issue with a single 10 Gigabit interface on one of Intel > Xeon D-1541 network servers. Namely after the reboot the interface > appears to be down even with a static route > > phobos# ifconfig ix0 > ix0: flags=8843 mtu 1500 > lladdr ac:1f:6b:19:f7:72 > index 1 priority 0 llprio 3 > groups: egress > media: Ethernet autoselect > status: no carrier > inet 128.2.204.160 netmask 0xfc00 broadcast 128.2.207.255 > > The only thing I can see is > > ix0: CRITICAL: EXTERNAL PHY OVER TEMP!! PHY will downshift to lower pow > er state! > > both in dmesg included at the end of this email as well in log files. > This appears to be a line from a driver code commited few years ago by > Mike Belopuhov > > http://openbsd-archive.7691.n7.nabble.com/Intel-10GbE-ix-driver-update-Looking-for-tests-td308300.html If you check the source code, the top of the file says: Copyright (c) 2001-2013, Intel Corporation It's from their code, handling their part, and you have one of those. You should probably ask Intel
ix0: CRITICAL: EXTERNAL PHY OVER TEMP!!
Hi, I am having an issue with a single 10 Gigabit interface on one of Intel Xeon D-1541 network servers. Namely after the reboot the interface appears to be down even with a static route phobos# ifconfig ix0 ix0: flags=8843 mtu 1500 lladdr ac:1f:6b:19:f7:72 index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect status: no carrier inet 128.2.204.160 netmask 0xfc00 broadcast 128.2.207.255 The only thing I can see is ix0: CRITICAL: EXTERNAL PHY OVER TEMP!! PHY will downshift to lower pow er state! both in dmesg included at the end of this email as well in log files. This appears to be a line from a driver code commited few years ago by Mike Belopuhov http://openbsd-archive.7691.n7.nabble.com/Intel-10GbE-ix-driver-update-Looking-for-tests-td308300.html The server had uptime of about a week before tonigh reboot so I have no resons to believe that the cable CAT 6 is bad but I will replace it tomorrow. I don't own the network equipment but I have many servers connected to the same university switch server rack including identical Xeon D-1541 machines and all appear to work flawlessly. I am not a network engineer so I am quite bewildered by the whole situation. Any hints? Predrag OpenBSD 6.5 (GENERIC.MP) #0: Wed Apr 24 23:38:54 CEST 2019 r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17055797248 (16265MB) avail mem = 16529260544 (15763MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9b0 (39 entries) bios0: vendor American Megatrends Inc. version "1.2" date 04/21/2017 bios0: Silicon Mechanics 1U_SoC_D-1541 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SPMI MCFG UEFI DBG2 HPET WDDT SSDT SSDT SSDT PRAD DMAR HEST BERT ERST EINJ acpi0: wakeup devices IP2P(S4) EHC1(S4) EHC2(S4) RP01(S4) RP02(S4) RP03(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) BR1A(S4) BR1B(S4) BR2A(S4) BR2B(S4) BR2C(S4) [...] 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) Xeon(R) CPU D-1541 @ 2.10GHz, 2100.25 MHz, 06-56-03 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz, 2100.01 MHz, 06-56-03 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz, 2100.01 MHz, 06-56-03 cpu2: 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz, 2100.01 MHz, 06-56-03 cpu3: 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 8 (application processor) cpu4: Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz, 2100.01 MHz, 06-56-03 cpu4: FPU,VME
Re: sndio? aucat -i s.wav: "default: couldn't open audio device"
Thank you Alexandre! I did # sndiod -ddd -r 44100 -f rsnd/1 -m play snd0 pst=cfg.default: play=0:1 vol=23170 dup and went to the other window, did petal# SNDIO_DEBUG=4 aucat -i sound.wav _aucat_open: host= unit=0 devnum=0 opt=default /tmp/sndio-0/sock0: No such file or directory /tmp/sndio/sock0: connected _aucat_rmsg: eof aucat_init: mode refused /dev/audio0: Invalid argument default: couldn't open audio device The first window wrote helper(helper|ini): created worker(worker|ini): created listen(/tmp/sndio/sock0|ini): created sock(sock|ini): created sock,rmsg,widl: AUTH message sock,rmsg,widl: HELLO message sock,rmsg,widl: hello from , mode = 1, ver 7 aucat0: overwritten slot 0 snd0 pst=cfg: device requested worker: send: cmd = 0, num = 0, mode = 1, fd = -1 worker: recv: cmd = 3, num = 0, mode = 0, fd = -1 snd0 pst=cfg: rsnd/1: failed to open audio device sock,rmsg,widl: closing sock(sock|zom): destroyed helper: recv: cmd = 0, num = 0, mode = 1, fd = -1 helper: send: cmd = 3, num = 0, mode = 0, fd = -1 helper(helper|ini): processed in 8874us On Tue, May 14, 2019 at 1:46 AM Alexandre Ratchov wrote: > > On Mon, May 13, 2019 at 03:53:51PM -0500, Juan Zuluaga wrote: > > Hello all, > > > > I have audio trouble: no sound whatsoever, and error messages. > > > > In a first terminal window, as root, I typed > > # sndiod -ddd > > > > The ISA bus (actually the PC-XT DMA controller which didn't evolve > since 1980) is not fast enough for full-duplex. If you don't plan to > record, could you try: > > sndiod -dd -r 44100 -f rsnd/1 -m play > > and see if you manage to play something?
Re: relayd without pf?
FWIW, I also encountered some slightly different error messages, I'll see if I can reproduce those. -Adam On May 14, 2019 4:48:29 p.m. CDT, Reyk Floeter wrote: > >> Am 14.05.2019 um 23:06 schrieb Adam Thompson : >> >>> On 2019-05-14 15:42, Adam Thompson wrote: >>> OK, I'm pretty sure this is a dumb question, but... >>> Does relayd work properly, or at all with pf disabled? (in >6.5-RELEASE) >> >> >> I have partially answered my own question. That last message was >posted prematurely, in more than one way, sorry! >> >> 1. the relayd.conf in the previous message was copied-and-pasted from >the wrong window, in mid-edit. >> >> 2. relayd(8) does not work with pf(4) disabled. I'm unclear if this >is a bug, or by design. With pf disabled, it outputs: >> root@rt:~# relayd -dv >> startup >> relayd: pfe: pf is disabled >> parent: proc_open: imsg_flush: Broken pipe >> ca exiting, pid 37187 >> ca exiting, pid 79962 >> ca exiting, pid 95113 >> root@rt:~# hce exiting, pid 91576 >> relay exiting, pid 26432 >> relay exiting, pid 6966 >> relay exiting, pid 50166 >> >> The message "pfe: pf is disabled" looks like an informational message >to me, I'm not using any pf features, so it shouldn't matter... but it >very much does matter, and relayd exits shortly after starting if pf is >disabled. >> >> Pinging @reyk - is this a bug or deliberate? >> > >It’s a historical reason because redirects existed first. And most >OpenBSD systems keep pf enabled by default. > >But you’re right; it should be easy to fix. > >Reyk -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
_XSERVTransSocketUNIXAccept: accept() failed
Hello, These messages are filling up the Xorg.0.log and xenodm.log to gigabytes and does not allow additional xterm windows to open. I see these messages in /var/log/Xorg.0.log joe:10424$ tail Xorg.0.log [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.045] _XSERVTransSocketUNIXAccept: accept() failed joe:10425$ tail /var/log/xenodm.log _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed Thanks to #openbsd's epony and oldlaptop, the resolution is to: 1. increase daemon openfiles-max to 2048 and openfiles-cur to 1024 in /etc/login.conf 2. cap_mkdb /etc/login.conf 3. re-login. Thanks
Re: relayd without pf?
> Am 14.05.2019 um 23:06 schrieb Adam Thompson : > >> On 2019-05-14 15:42, Adam Thompson wrote: >> OK, I'm pretty sure this is a dumb question, but... >> Does relayd work properly, or at all with pf disabled? (in 6.5-RELEASE) > > > I have partially answered my own question. That last message was posted > prematurely, in more than one way, sorry! > > 1. the relayd.conf in the previous message was copied-and-pasted from the > wrong window, in mid-edit. > > 2. relayd(8) does not work with pf(4) disabled. I'm unclear if this is a > bug, or by design. With pf disabled, it outputs: > root@rt:~# relayd -dv > startup > relayd: pfe: pf is disabled > parent: proc_open: imsg_flush: Broken pipe > ca exiting, pid 37187 > ca exiting, pid 79962 > ca exiting, pid 95113 > root@rt:~# hce exiting, pid 91576 > relay exiting, pid 26432 > relay exiting, pid 6966 > relay exiting, pid 50166 > > The message "pfe: pf is disabled" looks like an informational message to me, > I'm not using any pf features, so it shouldn't matter... but it very much > does matter, and relayd exits shortly after starting if pf is disabled. > > Pinging @reyk - is this a bug or deliberate? > It’s a historical reason because redirects existed first. And most OpenBSD systems keep pf enabled by default. But you’re right; it should be easy to fix. Reyk
Re: When will be created a great desktop experience for OpenBSD?
The GUI verses command line arguments are as old as time itself, or close to it. What constitutes a great desktop experience is a matter of taste, whatever works for you may not work for someone else. Not one desktop or GUI will fit everyone; use whats best for you and live your own computer life. OpenBSD has a massive amount of tools to make any kind of desktop you wish, that's why it is awesome. On Tue, May 14, 2019 at 3:57 PM wrote: > [responding to this little gem I just found in the archives...] > > Ingo wrote on 2019-05-14 13:54:38: > > > That's entirely a matter of taste. > >[snip rant] > > Ingo, we don't often seem to agree, but mecouldn't have said what you > just did any better. > > In particular, me'd like to reinforce this point: > > > Automation is precisely the main advantage of CLIs over GUIs. > > with a translated quote from Gerrit Krol (I only know the quote, not > him, and not his books), as it used to appear in the front of every > book written or published by the somewhat legendary Pim Oets: > > "Computers are needed where the work becomes boring. Work that is > boring and yet has to be done, can be done by a computer. It is > therefore good that computers exist." > > Amen. > > --zeurkous. > > -- > Friggin' Machines! > >
Unbound DNS request timeout
Hello misc, Anybody else encountered this issue: I am using OpenBSD v6.3/6.4 with its Unbound as DNS server in local subnet. It does not do any recursive DNS queries. Reverse lookup works for VMware Esxi and Linux machines but not for Windows 2016 or Dell EMC Compellent SCOS 7.3.x arrays. The Windows console message is: DNS request timed out. timeout was 2 seconds -pekka-
Re: relayd without pf?
On 2019-05-14 15:42, Adam Thompson wrote: OK, I'm pretty sure this is a dumb question, but... Does relayd work properly, or at all with pf disabled? (in 6.5-RELEASE) I have partially answered my own question. That last message was posted prematurely, in more than one way, sorry! 1. the relayd.conf in the previous message was copied-and-pasted from the wrong window, in mid-edit. 2. relayd(8) does not work with pf(4) disabled. I'm unclear if this is a bug, or by design. With pf disabled, it outputs: root@rt:~# relayd -dv startup relayd: pfe: pf is disabled parent: proc_open: imsg_flush: Broken pipe ca exiting, pid 37187 ca exiting, pid 79962 ca exiting, pid 95113 root@rt:~# hce exiting, pid 91576 relay exiting, pid 26432 relay exiting, pid 6966 relay exiting, pid 50166 The message "pfe: pf is disabled" looks like an informational message to me, I'm not using any pf features, so it shouldn't matter... but it very much does matter, and relayd exits shortly after starting if pf is disabled. Pinging @reyk - is this a bug or deliberate? -Adam
relayd without pf?
OK, I'm pretty sure this is a dumb question, but...
Does relayd work properly, or at all with pf disabled? (in 6.5-RELEASE)
It looks like it should as long as I use "relay" instead of "redirect",
but I'm having trouble, and don't want to keep banging my head against a
wall if it's something this simple.
Thanks,
-Adam
--begin relayd.conf--
http protocol rtproxy {
pass quick
}
relay rt4 {
listen on 0.0.0.0 port 80
protocol rtproxy
forward to 127.0.0.1 port 8080
}
relay rt6 {
listen on :: port 80
protocol rtproxy
forward to ::1 port 8080
}
--end relayd.conf--
Re: sh : COMMAND LINE EDITING when relevant?
Hi Ruda, rsyk...@disroot.org wrote on Tue, May 14, 2019 at 07:19:42PM +: > after reading the sh man page I have been wondering: > When is the line editing mode described just after the > 'COMMAND HISTORY AND COMMAND LINE EDITING' heading relevant? Near the beginning, the sh(1) manual page contains this paragraph: This version of sh is actually ksh in disguise. As such, it also supports the features described in ksh(1). This manual page describes only the parts relevant to a POSIX compliant sh. If portability is a concern, use only those features described in this page. In particular, the section "COMMAND HISTORY AND COMMAND LINE EDITING" describes only those features of ksh(1) "Vi editing mode" required by POSIX. Wo do not provide a shell or an execution mode of ksh providing exactly those features and no extensions. I think shells exist that aim for being a minimal implementation of only POSIX features. For example, dash(1) may be one of them (i'm not sure, though). Certainly, ksh(1) isn't one of those shells. > [I know there exist vi and emacs modes, but I cannot make my > ksh shell behave along the lines described in the mentioned > section (i.e different from both emacs and vi modes).] As with any bug report: what *exactly* are you doing, what exactly happens, and what exactly would you expect to happen instead? Yours, Ingo
RE: When will be created a great desktop experience for OpenBSD?
[responding to this little gem I just found in the archives...] Ingo wrote on 2019-05-14 13:54:38: > That's entirely a matter of taste. >[snip rant] Ingo, we don't often seem to agree, but mecouldn't have said what you just did any better. In particular, me'd like to reinforce this point: > Automation is precisely the main advantage of CLIs over GUIs. with a translated quote from Gerrit Krol (I only know the quote, not him, and not his books), as it used to appear in the front of every book written or published by the somewhat legendary Pim Oets: "Computers are needed where the work becomes boring. Work that is boring and yet has to be done, can be done by a computer. It is therefore good that computers exist." Amen. --zeurkous. -- Friggin' Machines!
sh : COMMAND LINE EDITING when relevant?
Dear list, after reading the sh man page I have been wondering: When is the line editing mode described just after the 'COMMAND HISTORY AND COMMAND LINE EDITING' heading relevant? [I know there exist vi and emacs modes, but I cannot make my ksh shell behave along the lines described in the mentioned section (i.e different from both emacs and vi modes).] Thanks for comments Ruda
Re: Pf rdr-to and rdomain issue
So we did manage to make it work by adding a pair in each rdomain and a default route from rdomain 0 using the pair on rdomain 2 as a gateway but it doesn't the seem correct. Is there any better proper way to make the traffic flowing back from one rdomain to another when using an rdr-to rule in pf? From: owner-m...@openbsd.org on behalf of Benjamin Girard Sent: 14 May 2019 18:02 To: Josh Grosse; misc@openbsd.org Subject: Re: Pf rdr-to and rdomain issue Can't we just use pf to move the traffic, rather than using pair? From: Josh Grosse Sent: 14 May 2019 17:42 To: Benjamin Girard Subject: Re: Pf rdr-to and rdomain issue I think pair(4) may come to your rescue.
Re: Blind OpenBSD users
aa...@bolddaemon.com (Aaron Bieber), 2019.05.10 (Fri) 16:05 (CEST): > I am looking to understand / enhance the OpenBSD experience for blind > users. :flan_thumbsup: > Do we have any blind users reading misc that can offer any insight > into their usecases / pain points / work flows / wants? I vaguely remembered the thread and even found it, somewhat dated (2013-07-07): https://marc.info/?l=openbsd-misc&m=137316509908904 and parts of (search for "oyen"): https://marc.info/?t=13729967261 and finally: https://marc.info/?w=2&r=1&s=eric+oyen&q=a Marcus
Re: Pf rdr-to and rdomain issue
Can't we just use pf to move the traffic, rather than using pair? From: Josh Grosse Sent: 14 May 2019 17:42 To: Benjamin Girard Subject: Re: Pf rdr-to and rdomain issue I think pair(4) may come to your rescue.
Pf rdr-to and rdomain issue
Hi, We would like to get a http request coming in on one rdomain moved to a host on another rdomain. How would we go about doing that? Can't seem to get it to work, the return traffic gets lost on rdomain 0 and is not moved back to rdomain 2. pass in on rdomain 2 proto tcp from any to 123.123.123.123/32 port 443 rdr-to 172.30.128.84 rtable 0 pass quick proto tcp from any to 172.30.128.84/32 port 443 Thanks, Ben
Re: Blind OpenBSD users
On 2019-05-14, Marc Espie wrote: > We also have (had?) a speech synthesis system in > audio/festival We deleted that. Somebody would need to create a new port for a more recent release. > I don't think we have any other speech synthesis open source > software in the ports tree. There's audio/espeak, but I can't comment on it. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: When will be created a great desktop experience for OpenBSD?
Hi Ulf, ULF wrote on Tue, May 14, 2019 at 10:07:46AM +0200: > On a mac, on a recent gnome, on a kde, etc. it's easier for a user to keep > track of multiple jobs without thinking about the OS, but rather thinking > about contents. [...] > In 2019, doing all of the above with fvwm, twm, (whatever-tiny)wm not only > feels awkward, but also time consuming and less flexible. The argument that > one just has to type "command &" is not as valid as just clicking an icon > when one of your hands is busy holding the phone or a document. That's entirely a matter of taste. I waste time whenever i have to select anything from any kind of menu, select any icon from any kind of iconbox or desktop background, select any file or directory from any file selection dialogue, or have to click any icon in any dialogue box. I prefer typing commands and use as little menus, clickable icons, selection lists, and dialogue boxes as possible because it is faster, simpler, and requires less looking at the screen. It is also scriptable/programmable, which is the main strength of using computers in the first place. Then again, if you like GUIs as a matter of personal taste, you are certainly welcome to use them. Many people like GUIs (even though i have a hard time understanding why), and that's why many of our developers focus on maintaining software like Gnome and KDE for OpenBSD. But please don't call it a "fact" that GUIs are absolutely better than CLIs. Even for image and video processing, i vastly prefer CLIs over GUIs wherever possible because it is faster and more precise for me. > And, btw, let's say it: fvwm looks like 70s/80s, it's full of > charm for retrocomputing but it's pretty ugly to see in 2019. I couldn't care less. "Ugly" is purely personal taste, and fashion is purely a waste of time and resources, benefiting no one but those who define what the fashion of the year is and making money from selling new products to the public because last year's products now suddenly look old-fashioned for no good reason. > And many people prefer just right clicking on a picture to change > background I would never want to change a background. There is simply no point to that. When i'm working, almost none of the background is visible anyway. Why would i waste screen real estate? And even if there is some screen space i don't currently need, by definition, it doesn't matter how it looks like. > rather than finding which config file they gotta change and then > change it. Because config files are good, but total lack of > automatization for basic activies is just time consuming, Automation is precisely the main advantage of CLIs over GUIs. That is not even a personal preference, but that is a fact for a change. Yours, Ingo
Re: i3bar not working after 6.5 upgrade
On 5/13/19 12:51 PM, Edgar Pettijohn wrote: > On May 13, 2019 2:58 AM, shadrock uhuru wrote: >> >> >> On 5/13/19 1:35 AM, shadrock uhuru wrote: >>> hi everyone >>> since upgrading to 6.5 my i3bar no longer works. >>> i have not changed the configuration in any way >>> when i run the i3status command manually in a terminal the bar is not >>> displayed but the correct infomation that would be on the i3bar is >>> echoed to the terminal. >>> the message on the right hand of the i3bar is >>> error: status_command not found or is missing a library dependency >>> (exit 127) >>> the left hand side of the bar is functioning correctly >>> the following is from the i3 log file. >>> >>> grep i3bar 'i3log-2019-05-12-0-41-37' >>> >>> 05/12/19 00:41:40 - config_parser.c:parse_config:267 - CONFIG(line >>> 152): # Start i3bar to display a workspace bar (plus the system >>> information i3status >>> 05/12/19 00:41:41 - Starting bar process: i3bar --bar_id=bar-0 >>> --socket="/tmp/i3-shadrock.Q7Rfx2/ipc-socket.80799" >>> 05/12/19 00:41:41 - executing: i3bar --bar_id=bar-0 >>> --socket="/tmp/i3-shadrock.Q7Rfx2/ipc-socket.80799" >>> 05/12/19 00:41:41 - WM_CLASS changed to i3bar (instance), i3bar (class) >>> 05/12/19 00:41:41 - WM_NAME changed to "i3bar for output LVDS-1" >>> 05/12/19 00:41:41 - Checking window 0x00e3 (class i3bar) >>> 05/12/19 00:41:41 - Checking window 0x00e3 (class i3bar) >>> [/usr/obj/ports/i3-4.16.1/i3-4.16.1/../i3-4.16.1/i3bar/src/child.c:468] >>> ERROR: Child (pid: 72679) unexpectedly exited with status 127 >>> >>> >> how do i debug for a missing library ? >> shadrock >> > LD_DEBUG=1 thanks found the problem by enabling logging for i3 i had my i3 config file at ~/.i3 instead of at ~/.config/i3 which had an old i3 config file , after copying everything from ~i3 to ~/config/i3 and restarting i3 all is working again. shadrock
Re: When will be created a great desktop experience for OpenBSD?
On Tue, May 14, 2019 at 12:20:52PM +0100, Patrick Harper wrote: > On Tue, 14 May 2019, at 09:09, ULF wrote: > > If from one side is true that many modern interfaces (mostly M$, though) > > are made for people who know nothing about computing, from one another is > > clear that some good ones (in terms of usability) help the user to keep > > concentrated on his work. > > > > On a mac, on a recent gnome, on a kde, etc. it's easier for a user to keep > > track of multiple jobs without thinking about the OS, but rather thinking > > about contents. It's a matter of fact that computers are mostly used to do > > things that have nothing to do with programming and sysadmin, and also > > developers here must, while programming/administering the machine, maybe > > write a letter to the insurance, browse 20+ pages while looking at a > > calendar (maybe shared) during a phone call, opening the accounting program > > for taxes and so on... > > > > In 2019, doing all of the above with fvwm, twm, (whatever-tiny)wm not only > > feels awkward, but also time consuming and less flexible. The argument that > > one just has to type "command &" is not as valid as just clicking an icon > > when one of your hands is busy holding the phone or a document. > > If one's window manager's configuration file is set up to provide shortcuts > to all relevant applications, then there's no need to use a terminal for that. > > > > > And, btw, let's say it: fvwm looks like 70s/80s, it's full of charm for > > retrocomputing but it's pretty ugly to see in 2019. And many people prefer > > just right clicking on a picture to change background rather than finding > > which config file they gotta change and then change it. Because config > > files are good, but total lack of automatization > > for basic activies is just time consuming, not sexy. Not to speak about > > fonts, icons and, especially, different languages (I mean alphabets) > > managing just shifting to a non-latin keyboard becomes hell. > > I think you have a point in there somewhere but I can't find it. I like retrocomputing. At what point does a society say "we want some things, but not the whole nine yards". Sorta like in Matrix III revolutions where the point is made that some machines (dumbed down) are OK, but high tech self-thinking machines like the "machines" in the matrix are not. We had a split before in western society where a group split from car ownership, and machinery in general. They lasted over 100 years I think. I think we may be nearing a split like that again, as we don't need to wait for the singularity to hit us. We can say "stop" where it's at today, or go back a few years or decades. When I started with UN*X in 1995, it became clear to me that I'd have to sacrifice on the trash games I played. I had to sacrifice on other things too. In a way life is about sacrifices and we don't even miss it when we don't think about what we'd be missing out on. Technology wise I'd like to go a bit further still as I am today but not much further where a computer tells me how to live my life, or even tries to hurt me. If I knew fvwm survived 100 years, that'd be a blessing perhaps? Regards, -peter
Re: When will be created a great desktop experience for OpenBSD?
On Tue, 14 May 2019, at 09:09, ULF wrote: > If from one side is true that many modern interfaces (mostly M$, though) > are made for people who know nothing about computing, from one another is > clear that some good ones (in terms of usability) help the user to keep > concentrated on his work. > > On a mac, on a recent gnome, on a kde, etc. it's easier for a user to keep > track of multiple jobs without thinking about the OS, but rather thinking > about contents. It's a matter of fact that computers are mostly used to do > things that have nothing to do with programming and sysadmin, and also > developers here must, while programming/administering the machine, maybe > write a letter to the insurance, browse 20+ pages while looking at a > calendar (maybe shared) during a phone call, opening the accounting program > for taxes and so on... > > In 2019, doing all of the above with fvwm, twm, (whatever-tiny)wm not only > feels awkward, but also time consuming and less flexible. The argument that > one just has to type "command &" is not as valid as just clicking an icon > when one of your hands is busy holding the phone or a document. If one's window manager's configuration file is set up to provide shortcuts to all relevant applications, then there's no need to use a terminal for that. > > And, btw, let's say it: fvwm looks like 70s/80s, it's full of charm for > retrocomputing but it's pretty ugly to see in 2019. And many people prefer > just right clicking on a picture to change background rather than finding > which config file they gotta change and then change it. Because config > files are good, but total lack of automatization > for basic activies is just time consuming, not sexy. Not to speak about > fonts, icons and, especially, different languages (I mean alphabets) > managing just shifting to a non-latin keyboard becomes hell. I think you have a point in there somewhere but I can't find it.
Re: Blind OpenBSD users
On 5/14/19 5:02 AM, Marc Espie wrote: As far as I know, the only software we have for blind people (and not just people with very poor eye sight) is misc/brltty. misc/screen also has support in the form of the shm flavor, which hooks to misc/brltty The main issue for this kind of thing is of course testing. This was done over 10 years ago. I have zero idea if this still works, or if there are better tools these days. We also have (had?) a speech synthesis system in audio/festival Unfortunately, this is research code that predates the C++ standard by years, and thus is thoroughly rotten through. I don't think we have any other speech synthesis open source software in the ports tree. There is flite which works but isn't great. --STeve Andre'
Re: Blind OpenBSD users
As far as I know, the only software we have for blind people (and not just people with very poor eye sight) is misc/brltty. misc/screen also has support in the form of the shm flavor, which hooks to misc/brltty The main issue for this kind of thing is of course testing. This was done over 10 years ago. I have zero idea if this still works, or if there are better tools these days. We also have (had?) a speech synthesis system in audio/festival Unfortunately, this is research code that predates the C++ standard by years, and thus is thoroughly rotten through. I don't think we have any other speech synthesis open source software in the ports tree.
Re: When will be created a great desktop experience for OpenBSD?
If from one side is true that many modern interfaces (mostly M$, though) are made for people who know nothing about computing, from one another is clear that some good ones (in terms of usability) help the user to keep concentrated on his work. On a mac, on a recent gnome, on a kde, etc. it's easier for a user to keep track of multiple jobs without thinking about the OS, but rather thinking about contents. It's a matter of fact that computers are mostly used to do things that have nothing to do with programming and sysadmin, and also developers here must, while programming/administering the machine, maybe write a letter to the insurance, browse 20+ pages while looking at a calendar (maybe shared) during a phone call, opening the accounting program for taxes and so on... In 2019, doing all of the above with fvwm, twm, (whatever-tiny)wm not only feels awkward, but also time consuming and less flexible. The argument that one just has to type "command &" is not as valid as just clicking an icon when one of your hands is busy holding the phone or a document. And, btw, let's say it: fvwm looks like 70s/80s, it's full of charm for retrocomputing but it's pretty ugly to see in 2019. And many people prefer just right clicking on a picture to change background rather than finding which config file they gotta change and then change it. Because config files are good, but total lack of automatization for basic activies is just time consuming, not sexy. Not to speak about fonts, icons and, especially, different languages (I mean alphabets) managing just shifting to a non-latin keyboard becomes hell. On Mon, May 13, 2019 at 8:09 PM Antoine Jacoutot wrote: > On Mon, May 13, 2019 at 02:04:13PM -0400, Nathan Hartman wrote: > > On Mon, May 13, 2019 at 1:26 PM Steve Litt > > wrote: > > > > > As I travel this earth I continue to be amazed at peoples' fascination > > > with tiny fonts. Perhaps that's to pack more stuff on the screen. But > > > then they go on to make the text low contrast in the name of "pretty", > > > thereby locking out those who can't correct to 20/20. And just to rub > > > salt in the wounds, they always make their tiny black background > > > terminals transparent, so random noise can confuse further. > > > > > > SteveT > > > > > > I am similarly amazed. > > > > User interfaces have gotten progressively > > worse over the last 15 years and the trend > > continues. > > Nowadays, computer interfaces are designed for people who don't know nor > care > about computers. > Different times... > > -- > Antoine > >
Re: USB sound card not playing
On Wed, May 09, 2018 at 04:06:41PM +0200, John Wilkes wrote: > > OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP There were a lot of changes in usb audio support, please try -current or at least OpenBSD 6.5
Re: USB sound card not playing
On Tue, May 14, 2019 at 11:29:45AM +0900, Tuyosi T wrote: > i use 6.6 snapshots and USB sound card . > the card play youtube well including sound . > > -- > $ dmesg | grep audio > uaudio0 at uhub2 port 4 configuration 1 interface 1 "C-Media > Electronics Inc. USB Audio Device" rev 1.10/1.00 addr 5 > uaudio0: class v1, full-speed, sync, channels: 2 play, 1 rec, 8 ctls > audio0 at uaudio0 > uaudio0: can't reset interface > uaudio0: can't reset interface > audio0 detached > uaudio0 detached > uaudio0 at uhub3 port 6 configuration 1 interface 1 "C-Media > Electronics Inc. USB Audio Device" rev 1.10/1.00 addr 4 > uaudio0: class v1, full-speed, sync, channels: 2 play, 1 rec, 8 ctls > audio0 at uaudio0 could send the full dmesg, please
