Re: feedback doas / sudo / xfce-extras
I forwarded to landry@ Thank you. Heiko Am 21.08.2015 um 16:16 schrieb Stuart Henderson: On 2015-08-21, Heiko Zimmermann open...@heiko-zimmermann.com wrote: Hello Tedu, I'm using xfce. I tried to pkg_delete sudo because of doas. doas is working fine for me. But I cant remove sudo because of dependencies. xfce-extras - xfce-mount - sudo. So I cant remove sudo without removing xfce-extras. Maybe - in future - there is a chance to integrate doas in xfce? Best Regards, Heiko xfce-mount doesn't really use sudo any more, you can specify to use it but that's done as user configuration. It looks like this dependency can just be removed (and DESCR adjusted so mention doas as well).
RadeonDRM problem in 5.7 (and yes, I fixed machdep + drivers)
Hi guys, I get a black screen when I boot OpenBSD 5.7, just before the console login. I've been able to get to the console login the machine by entering boot -c, disable radeondrm, and then quit at the boot prompt. Based of my internet sleuthing, I've checked that all drivers are up to date (have radeondrm-firmware-2013-1002p0.tgz). I've also created a /etc/sysctl.conf file, and put machdep.allowaperture=2 in there. The CPU is a Haswell i3 4170, and the GPU is an AMD FirePro v4900, featuring a 6670 Turks processor. Everything works fine as long as my Radeon card is disabled. How do I fix this problem? Thanks!
Support for Netgear WNA1000Mv2 USB wireless adapter
Folks, I recently purchased what I thought was a Netgear WNA1000M USB wireless adapter, as I had read it was supported by OpenBSD. Unfortunately, what as delivered was a Netgear WNA1000Mv2 (well, Realtek), which was not recognised by the urtwn driver. More in hope than expectation, I added definitions to support this adapter in usbdevs and if_urtwn.c. I was delighted to find the patched driver did indeed support v2 of the adapter: urtwn0 at uhub1 port 4 Realtek WNA1000Mv2 rev 2.00/2.00 addr 2 urtwn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr a4:2b:8c:f0:31:2e priority: 4 groups: wlan egress media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active ieee80211: nwid hydrus chan 11 bssid 00:1d:68:e9:65:d5 -68dBm nwkey not displayed inet 192.168.0.105 netmask 0xff00 broadcast 192.168.0.255 Here are the diffs, against 5.7 source files: --- usbdevs Thu Aug 20 13:13:04 2015 +++ /usr/src/sys/dev/usb/usbdevs Thu Aug 20 13:14:54 2015 @@ -3095,6 +3095,7 @@ product NETGEAR WNA1100 0x9030 WNA1100 product NETGEAR WNA1000 0x9040 WNA1000 product NETGEAR WNA1000M 0x9041 WNA1000M +product NETGEAR WNA1000Mv2 0x9043 WNA1000Mv2 /* Netgear(2) products */ product NETGEAR2 MA101 0x4100 MA101 --- if_urtwn.cThu Aug 20 13:13:04 2015 +++ /usr/src/sys/dev/usb/if_urtwn.c Thu Aug 20 13:17:32 2015 @@ -110,6 +110,7 @@ { USB_VENDOR_IODATA, USB_PRODUCT_IODATA_WNG150UM }, { USB_VENDOR_IODATA, USB_PRODUCT_IODATA_RTL8192CU }, { USB_VENDOR_NETGEAR, USB_PRODUCT_NETGEAR_WNA1000M }, + { USB_VENDOR_NETGEAR, USB_PRODUCT_NETGEAR_WNA1000Mv2 }, { USB_VENDOR_NETGEAR, USB_PRODUCT_NETGEAR_RTL8192CU }, { USB_VENDOR_NETGEAR4,USB_PRODUCT_NETGEAR4_RTL8188CU }, { USB_VENDOR_NETWEEN, USB_PRODUCT_NETWEEN_RTL8192CU }, Is it appropriate to send this information as a suggested enhancement via sendbug(1)? Best Regards, Mark Willson
Re: problems compiling latest 5.7 patches
On Fri, Aug 21, 2015 at 9:18 AM, luke...@onemodel.org wrote: ... === gnu/usr.bin/binutils *** Parse error in /usr/src/gnu/usr.bin/binutils: Malformed conditional (${BINUTILS_VERSION} == binutils-2.17) (Makefile.bsd-wrapper:13) *** Parse error: Need an operator in 'binutils-2.17' (Makefile.bsd-wrapper:13) This system appears to have -current from after 2015-06-01 installed on it, or at least the files in /usr/share/mk/ are from -current. The supported path from -current to -stable is to reinstall. Philip Guenther
Re: open bsd 5.7 and 5.8 cd ordering questions
On 08/22/15 21:32, Danny Nguyen wrote: Hi, I want to order these two compact discs (see subject line) and have few questions: 1. Is there tamperproof tape on the OpenBSD compact discs mailed from the openbsd store? 2. Royal Mail takes how long to arrive to California? Is it being sent as a letter? Thank you. oh and in answer to question 2. the Royal Mail claim to deliver in 5-7 working days to the rest of the world, which includes the US. hth Fred
Video card detected but does not initialize leading to black display during kernel probing
Hello, Recently I install OpenBSD 5.7 (amd64) on a iMac 12, 1 (15” iMac from 2011). I applied all 5.7 errata and am current as of August 23, 2015. The full dmesg follows this -email, but a snippet shows the kernel is having trouble with the video card: error: [drm:pid0:ni_init_microcode] *ERROR* ni_cp: Failed to load firmware radeon-turks_pfp error: [drm:pid0:evergreen_startup] *ERROR* Failed to load firmware! drm:pid0:evergreen_init *ERROR* disabling GPU acceleration drm:pid0:radeon_bo_unpin *WARNING* 0xff026eb6e2b0 unpin not necessary drm:pid0:radeon_bo_unpin *WARNING* 0xff026eb6e2b0 unpin not necessary error: [drm:pid0:evergreen_init] *ERROR* radeon: MC ucode required for NI+. drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU init radeon_hwmon_fini stub ttm_pool_mm_shrink_fini stub drm0 detached radeondrm0 detached vga1 at pci1 dev 0 function 0 ATI Radeon HD 6600M rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) On the first line I noticed “Failed to load firmware” in relation to the video card (ATI Radeon HD 6600M). My questions are: 1. Is a firmware blob needed that I must acquire and then provide to the kernel ? 2. In a worst case scenario, can I configure the kernel to not probe the video card and stick with the standard VGA output ? The video works when booting from the install RAM disk and while there is not a lot of room for displaying text, it’s still more usable in that state. DMESG follows =-=-=-=-=-=-=-= OpenBSD 5.7 (GENERIC.MP) #2: Sat Aug 22 22:22:41 EDT 2015 RTC BIOS diagnostic error 64ROM_cksum,config_unit,invalid_time real mem = 8548204544 (8152MB) avail mem = 8316731392 (7931MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (61 entries) bios0: vendor Apple Inc. version IM121.88Z.0047.B21.1506101610 date 06/10/15 bios0: Apple Inc. iMac12,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG SSDT SSDT SSDT acpi0: wakeup devices P0P2(S4) GFX0(S4) EC__(S4) HDEF(S4) GIGE(S4) RP01(S4) ARPT(S4) RP02(S4) RP03(S4) RP05(S4) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.41 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC 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.1.0, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.02 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC 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) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.02 MHz 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC 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) Core(TM) i5-2400S CPU @ 2.50GHz, 2500.02 MHz 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-155 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 3 (RP02) acpiprt4 at acpi0: bus 4 (RP03) acpiprt5 at acpi0: bus 5 (RP05) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpicpu2 at acpi0: C3, C2, C1, PSS acpicpu3 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB cpu0: Enhanced SpeedStep 2500 MHz: speeds: 2501, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800,
Re: bpf_mtap/SRP on -current/amd64 panics after a few minutes
On Aug 22, 2015, at 12:22 PM, Mattieu Baptiste mattie...@gmail.com wrote: acpicpu0 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS acpicpu1 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS These look suspicious. Perhaps the acpicpu driver is the culprit. 5.8 appears to of added the following: acpicpu(4) http://www.openbsd.org/cgi-bin/man.cgi?query=acpicpusec=4 uses ACPI C-state information to reduce power consumption of idle CPUs. A âcoolâ feature imho that might add life to a fanless.
Re: problems compiling latest 5.7 patches
On Sat, Aug 22, 2015 at 02:21:49PM -0600, luke...@onemodel.org wrote: OK, I must have run an errant CVS command somewhere. (Sigh.) Thanks much for seeing that pointing it out. While you're at it, you should try running 'make -j num'. I noticed you're using GENERIC.MP but running 'make build'. My kernel compiles normally take 50s with make -j8. Without -j8, it takes around 150s. The best -j num depends on your hardware so try a few settings.
Re: problems compiling latest 5.7 patches
On 08/22/15 13:53, Philip Guenther wrote: This system appears to have -current from after 2015-06-01 installed on it, or at least the files in /usr/share/mk/ are from -current. The supported path from -current to -stable is to reinstall. Philip Guenther OK, I must have run an errant CVS command somewhere. (Sigh.) Thanks much for seeing that pointing it out.
Re: bpf_mtap/SRP on -current/amd64 panics after a few minutes
On Sat, Aug 22, 2015 at 9:18 PM, Patrick Dohman patrick_doh...@comcast.net wrote: On Aug 22, 2015, at 12:22 PM, Mattieu Baptiste mattie...@gmail.com wrote: acpicpu0 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS acpicpu1 at acpi0: !C2(0@100 io@0x841), C1(@1 halt!), PSS These look suspicious. Perhaps the acpicpu driver is the culprit. 5.8 appears to of added the following: acpicpu(4) http://www.openbsd.org/cgi-bin/man.cgi?query=acpicpusec=4 uses ACPI C-state information to reduce power consumption of idle CPUs. A “cool” feature imho that might add life to a fanless. That'll make his box idle cooler, but that's unrelated to a panic in the SRP bits. Philip Guenther
Re: RadeonDRM problem in 5.7 (and yes, I fixed machdep + drivers)
Hello, Gautam What no /var/run/dmesg.boot and /var/log/Xorg.0.log:') I've checked that all drivers are up to date \ (have radeondrm-firmware-2013-1002p0.tgz) This is some what unclear. Lets start by making sure all firmware has been unpacked correctly. I've been able to get to the console login the machine by entering \ boot -c, disable radeondrm, and then quit at the boot prompt. ^ ^ ^^ ^ ^^ Boot the machine as above. Make sure you have a properly configured connection to the internet. Log in as root, (or a sudo(8) enabled user). Run, /usr/sbin/fw_update -a Have you added a /etc/X11/xorg.conf? Disable it. /bin/mv /etc/X11/xorg.conf /etc/X11/xorg.conf.DISABLED Remove any previous /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. /bin/rm /var/log/Xorg.0.log* Reboot the machine. /sbin/reboot Do not boot -c, disable radeondrm If this fixes the radeon issue great. Problem solved. If not. Post your /var/run/dmesg.boot and /var/log/Xorg.0.log. Make sure you post the right Xorg.0.log. If you reboot using the integrated Intel HD Graphics 4400, this will move the previous Xorg.0.log with the radeon probe to Xorg.0.log.old. GPU is an AMD FirePro v4900, featuring a 6670 Turks processor. I see your hardware is in the man(1) page ( /usr/bin/man radeon ). Although I do not see Xorg probing for AMD FirePro v4900, 6670. Regards, Gerald Hanuer
Re: Support for Netgear WNA1000Mv2 USB wireless adapter
On Sat, 22 Aug 2015 17:20:24 +0200 Stefan Sperling s...@stsp.name wrote: On Sat, Aug 22, 2015 at 11:57:42AM +0100, Mark Willson wrote: Is it appropriate to send this information as a suggested enhancement via sendbug(1)? Already taken care of. Thank you. Stefan, Much appreciated. Thank you. -mark
open bsd 5.7 and 5.8 cd ordering questions
Hi, I want to order these two compact discs (see subject line) and have few questions: 1. Is there tamperproof tape on the OpenBSD compact discs mailed from the openbsd store? 2. Royal Mail takes how long to arrive to California? Is it being sent as a letter? Thank you.
Re: open bsd 5.7 and 5.8 cd ordering questions
On 08/22/15 21:32, Danny Nguyen wrote: Hi, I want to order these two compact discs (see subject line) and have few questions: 1. Is there tamperproof tape on the OpenBSD compact discs mailed from the openbsd store? 2. Royal Mail takes how long to arrive to California? Is it being sent as a letter? Thank you. Hi Danny, The CD's come in a DVD case which has a plastic film cover which has to be removed to access the CD's from the case. They also come in padded envelopes that are obvious if they have been tampered with. However, if you have an adversary who has lots of money these protection methods can be subverted - but the signify key will then allow you to see if they have tampered with the product. Although the truly paranoid can check the signify key printed on their disks with the one on the OpenBSD website. hth Fred
Re: open bsd 5.7 and 5.8 cd ordering questions
On Sat, 22 Aug 2015 22:28:48 +0100 Fred open...@crowsons.com wrote: Although the truly paranoid can check the signify key printed on their disks with the one on the OpenBSD website. ...unless of course they've poisoned your dns and are sending you to an alternate site for just such an event... Maybe you should just drive up to Calgary and get them in person. But yeah, they'll probably just swap the cds in your car while they're strip searching you when you're trying to get back in... *sigh*
bpf_mtap/SRP on -current/amd64 panics after a few minutes
Hi, I just upgraded my main router to -current (a PC-Engine APU, dmesg at the end). It panics after 5 minutes or so. It seems relative to the commit making bpf_mtap using SRPs. I'm bridging vlan/vether interfaces: $ cat /etc/hostname.bridge0 add re0 add vether0 up $ cat /etc/hostname.bridge1 add vlan0 add vlan3 up $ cat /etc/hostname.re0 inet 192.168.42.1 255.255.255.0 NONE group internal inet6 alias 2a01:::::1 64 $ cat /etc/hostname.vether0 inet 192.168.42.2 255.255.255.0 NONE group internal -inet6 $ cat /etc/hostname.vlan0 vlan 100 vlandev re0 -inet6 $ cat /etc/hostname.vlan3 vlan 100 vlandev re2 -inet6 Here are the panic, trace, ps and dmesg: panic: srp_leave: unexpected ref 0x80235700 via 0x80077448 Stopped at Debugger+0x9: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb{0} trace Debugger() at Debugger+0x9 panic() at panic+0xfe srp_leave() at srp_leave+0x48 _bpf_mtap() at _bpf_mtap+0x9f bpf_mtap_ether() at bpf_mtap_ether+0x39 if_input() at if_input+0x80 bridge_process() at bridge_process+0x2f5 bridgeintr() at bridgeintr+0x4c netintr() at netintr+0xa7 softintr_dispatch() at softintr_dispatch+0x8b Xsoftnet() at Xsoftnet+0x1f --- interrupt --- end of kernel end trace frame: 0x8, count: -11 0x: ddb{0} ps PID PPID PGRPUID S FLAGS WAIT COMMAND 7312 19078 16851 1000 30x83 selectssh 19078 16851 16851 1000 7 0x3cvs 16851 19066 16851 1000 30x8b pause sh 22942 12034 12034 1000 30x83 kqreadtail 26179 8406 26179 1000 30x83 ttyin ksh 32407 8406 32407 1000 30x83 ttyin ksh 22216 8406 22216 1000 30x83 ttyin ksh 5782 8406 5782 1000 30x83 ttyin ksh 13232 22589 22589 1000 30x83 kqreadtail 30965 8406 30965 1000 30x83 ttyin ksh 12034 8406 12034 1000 30x8b pause ksh 19066 8406 19066 1000 30x8b pause ksh 22589 8406 22589 1000 30x8b pause ksh 8406 1 8406 1000 30x80 kqreadtmux 3546 14481 14481 1000 30x83 kqreadtmux 14481 26328 14481 1000 30x8b pause ksh 26328 20622 20622 1000 30x90 selectsshd 20622 28780 20622 0 30x92 poll sshd 16424 1 16424 0 30x83 ttyin getty 5420 1 5420 0 30x80 poll cron 2642 1 2642 0 30x80 kqreadapmd 6503 1 6503 0 30x80 netio openvpn 21664 1 15856566 30x90 kqreadtor 21467 1 21467 32767 30x90 netconpfstatd 10586 1 10586 71 30x90 kqreadftp-proxy 7148 30502 30502 95 30x90 kqreadsmtpd 3050 30502 30502 95 30x90 kqreadsmtpd 17014 30502 30502 95 30x90 kqreadsmtpd 6238 30502 30502 95 30x90 kqreadsmtpd 23058 30502 30502 95 30x90 kqreadsmtpd 22647 30502 30502103 30x90 kqreadsmtpd 30502 1 30502 0 30x80 kqreadsmtpd 31180 1 31180 92 30x90 poll rtadvd 27245 1 27245 77 30x90 poll dhcpd 5519 1 5519577 30x90 poll openvpn 20054 1 20054 0 30x80 kqreadifstated 28780 1 28780 0 30x80 selectsshd 27854727 27854 0 30x80 netio npppd 727 1727 82 30x90 kqreadnpppd 890 3611 3611 68 30x90 selectisakmpd 3611 1 3611 0 30x80 netio isakmpd 20108 18369 9603 83 30x90 poll ntpd 18369 9603 9603 83 30x90 poll ntpd 9603 1 9603 0 30x80 poll ntpd 21695 12104 12104 74 30x90 bpf pflogd 12104 1 12104 0 30x80 netio pflogd 20324 5352 5352 73 30x90 kqreadsyslogd 5352 1 5352 0 30x80 netio syslogd 23494 1 23494577 30x90 poll openvpn 16206 1 16206577 30x90 poll openvpn 7113 0 0 0 3 0x14200 pgzerozerothread 9098 0 0 0 3 0x14200 aiodoned aiodoned 6467 0 0 0 3 0x14200 syncerupdate 13114 0 0 0 3 0x14200 cleaner cleaner 17351
Re: Support for Netgear WNA1000Mv2 USB wireless adapter
On Sat, Aug 22, 2015 at 11:57:42AM +0100, Mark Willson wrote: Is it appropriate to send this information as a suggested enhancement via sendbug(1)? Already taken care of. Thank you.