Re: torrent downloads
Let's say, you provide a torrent for the .fs and .iso files. Who trusts a SHA256.sig file from an unofficial torrent ? If you look at the errata page, you see, that you have to patch the system to keep it up to date and, there are no official updates of the .fs and .iso files after a patch. Even there are sometimes binary patches - this happened not for all platforms. At the end, a torrent is useless if you have to use again a mirror for the patches, for cvs or, for firmware updates. IMHO A better idea would be a mirror - if there is need for one. Am 27. April 2017 13:55:42 MESZ schrieb Thuban : >Hello, >I was wondering if there is any particular reason explaining why there >is no torrent file to retrieve OpenBSD *.fs and *.iso.
Re: torrent downloads
True but let me be a littlebit paranoid. Would it not be possible to create a new .fs / .iso with new keys in /etc/signify/* and new SHA256 / .sig files to place bad content and distribute it using a torrent ? I came across this idea as I readed long time ago some ideas how goverments could distribute the here in Europe called trojan of the state (Staatstrojaner). Just a idea and, maybe I am wrong - back to the topic. Am 27. April 2017 17:43:03 MESZ schrieb Ted Unangst : >Christoph R. Murauer wrote: >> Let's say, you provide a torrent for the .fs and .iso files. Who >trusts a SHA256.sig file from an unofficial torrent ? > >The whole point of signing the SHA256 is you don't have to trust the >person >who gives it to you.
Re: torrent downloads
@Ted : Good to know, thanks for details. @Theo : I am not the OP of the torrent topic. The topic was from thuban. I have no need for a torrent but had only this ideas / doubts about it. Am 27. April 2017 18:43:29 MESZ schrieb Theo de Raadt : >> Christoph R. Murauer wrote: >> > True but let me be a littlebit paranoid. Would it not be possible >to create a new .fs / .iso with new keys in /etc/signify/* and new >SHA256 / .sig files to place bad content and distribute it using a >torrent ? I came across this idea as I readed long time ago some ideas >how goverments could distribute the here in Europe called trojan of the >state (Staatstrojaner). >> >> Don't verify with the key inside the thing you're veriyfing. There is >some >> difficulty bootstrapping from nothing, but that's life. > >Correct. > >And Christoph, you may have noticed I stopped making official CDs >which did solve that particular problem. It was too much of a pain >for the gain. This feels like a request to handle all this pain for >torrent people. I stopped the build process for CDs because it was a >lot of work for almost no financial gain, and a distraction against >other things I'd rather do. Now I'm supposed to continue doing the >same, for no gain at all? Allow me to express my disinterest. As Ted >said. Bootstrapping problem is bootstrapping problem.
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
As already recommanded in another post www.1984.is They are located in Reykjavík / Iceland. I had in the past a OpenBSD VPS there (now shared hosting but maybe again a VPS). They provide by default Ubuntu / Debian but you also could use .ISO's. Drop them a mail about the .ISO's, they are friendly but thats are Debian people and they are unexperienced about OpenBSD - as they host using Debian / KVM. Remember, it is a island and sometimes they are not reachable or slow (based on my location). > Hi, > > Anyone know a good non-DMCA-compliant (outside US) VPS hosting, > OpenBSD-firendly? Traffic is mostly torrent-related. > > Good bandwidth and Bitcoin payments also a plus. > > Most offshore VPS providers offers default ubuntu-debian or centos iso > images, some even FreeBSD iso, but OpenBSD is being a bit hard to > find. In > the past i saw some provider offering to mount your own custom iso via > a > webpanel, but this contact I have no more. > > If have any tips, will be welcomed. > > cheers. > > x9p > >
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
It is not OpenBSD related. The OP meaned the Digital Millennium Copyright Act - as the question was related to non US hosting locations. See https://en.m.wikipedia.org/wiki/Digital_Millennium_Copyright_Act > Non-dcma a bit confusing for me becouse of I'm totally stranger those > things. I've a vps on TransIP and they support OpenBSD. > > On 16 Oct 2017 4:21 a.m., "x9p" wrote: > >> Hi, >> >> Anyone know a good non-DMCA-compliant (outside US) VPS hosting, >> OpenBSD-firendly? Traffic is mostly torrent-related. >> >> Good bandwidth and Bitcoin payments also a plus. >> >> Most offshore VPS providers offers default ubuntu-debian or centos >> iso >> images, some even FreeBSD iso, but OpenBSD is being a bit hard to >> find. In >> the past i saw some provider offering to mount your own custom iso >> via a >> webpanel, but this contact I have no more. >> >> If have any tips, will be welcomed. >> >> cheers. >> >> x9p >> >> >
Re: WPA2 and KRACK
See https://marc.info/?l=openbsd-misc&m=150814941311682&w=2 Use the search box for the mailing list - saves you time. > As it seems, WPA2 should be considered broken > > [1] https://www.krackattacks.com/ > [2] > https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt > > according to [1] OpenBSD has silently released a patch > > G > > >
Re: About WPA2 compromised protocol
The patch is there since 6.1 027 on the errata page. Saw the comic yesterday at Libertree. > On Tue, 17 Oct 2017 19:09:29 +0200 > "Stephane HUC \"PengouinBSD\"" wrote: > >> Just for the fun: >> http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/ > > I saw somebody share that on Mastodon this morning. :) > > On a more serious note; am I correct in assuming that the patch is > already in 6.2? >
Re: Guess what today is
Oh, yes. Happy birthday. > Happy birthday to OpenBSD--22 years old! > >
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
FYI : 1984.is provides in the settings of the VPS OpenBSD 5.9 and 6.1. > Thanks Ajitabh, Christoph > > will give a try with the small island. > > cheers. > > x9p > > >> As already recommanded in another post www.1984.is They are located >> in >> Reykjavík / Iceland. I had in the past a OpenBSD VPS there (now >> shared >> hosting but maybe again a VPS). They provide by default Ubuntu / >> Debian but you also could use .ISO's. Drop them a mail about the >> .ISO's, they are friendly but thats are Debian people and they are >> unexperienced about OpenBSD - as they host using Debian / KVM. >> >> Remember, it is a island and sometimes they are not reachable or >> slow >> (based on my location). >> > >
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
Sorry for the noise but I thought not, that they process my E-Mail so fast. Now also 6.2 is available. > FYI : 1984.is provides in the settings of the VPS OpenBSD 5.9 and 6.1. > >> Thanks Ajitabh, Christoph >> >> will give a try with the small island. >> >> cheers. >> >> x9p >> >> >>> As already recommanded in another post www.1984.is They are located >>> in >>> Reykjavík / Iceland. I had in the past a OpenBSD VPS there (now >>> shared >>> hosting but maybe again a VPS). They provide by default Ubuntu / >>> Debian but you also could use .ISO's. Drop them a mail about the >>> .ISO's, they are friendly but thats are Debian people and they are >>> unexperienced about OpenBSD - as they host using Debian / KVM. >>> >>> Remember, it is a island and sometimes they are not reachable or >>> slow >>> (based on my location). >>> >> >> > > >
Re: PostgREST post in OpenBSD
Have a look at https://hackage.haskell.org/package/postgrest I have not trieb but could do that later but a cabal install ... should make it. > Looks like Haskell code. if you are familiar with Haskell app built > using cabal just give it a try. Haskell itself, i.e. posgrest should > not be issue here probably. What you may hit are various possible > issues in GHC's runtime. But honestly, GHC runs very nicely on OpenBSD > so well, good luck and give it a try and report back... > > On Thu, Oct 19, 2017 at 6:26 AM, Tito Mari Francis Escaño > wrote: >> Hi everyone! I'd like to ask if somebody already tried or is working >> on a port of PostgREST (https://github.com/begriffs/postgrest) in >> OpenBSD. It has a working FreeBSD port but of course I prefer it >> running on arguably the most secure OS on the planet. >> I'm not confident I can make a port on my VM hosting OBSD, anybody >> tried this approach before? >> Thanks in advance. >> > >
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
To the other things spoken here (which I don't quote to keep it more short). Hetzner is a German company, which is part of the EU. There are not so many OpenBSD friendly hoster outside the USA and the EU. See 1984s TERMS OF SERVICE at https://www.1984.is/tos/ The torrents and illegal topic will also maybe depend on the content of the torrents. If you share something highly illegal - every provider on this planet will give you a kick (earlier or later). > nice to know. i had seen 5.9 and 6.1 only. > > cheers. > > x9p They add the image today in the morning (European time).
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
> At the risk of sounding stupid, what is an "OpenBSD friendly hoster"? This question is better answered by the OP (it was part of the original question IIRC). For me a OpenBSD .iso to use with their VPS. > > When th admins of the company are able to give telephone support > regarding openBSD? For me not. At 1984 they had no idea of OpenBSD related things. As I wrote in a post before, that are Debian people. But on the other hand, they are open minded to provide OpenBSD .iso's.
Re: DMCA Free OpenBSD VPS Hosting, multiple payment methods
> Thank you. > In the past I only chose hosters where I was able to install from > uploaded iso. I thought this was standard. > But I think some hosters don´t let their customers istall what they > want. > > At 1984 you have also only a given list of .iso's but they write explicit, if you don't see your prefered OS, talk to them - but no, Windows will never happen.
Re: iPhone tethering ?
The only 2 options you have is, get a Android device then you can use USB tethering over urndis(4) or, buy one of this round 10 Euro or less mini USB WIFI dongles which use the urtwn(4) firmware, then you can use your iPhone and tether using WIFI. The Edimax with a RTL8188CUSe and, the TP-LINK with a RTL8188EU work. Used booth in the past. > Hi everyone ! > > Does iPhone tethering work with OpenBSD? In other words, is there an > equivalent or alternative to FreeBSD & DragonFlyBSD¡¯s usbmuxd in > OpenBSD? The only thread about ¡°tethering¡± that I found in the > mailing list archives is about a Palm Treo. > > I will be thankful for any advise! > > RS.- > >
Re: Why openbsd use only 2 of my 4 CPU ?
Check sysctl hw.smt https://www.mail-archive.com/source-changes@openbsd.org/msg99141.html > Hello, > > I've migrated to -current to test the auto-join, but since then, my > system > is slow. Specially with libreoffice, firefox, ... > > By looking at top, I've saw that only 2 CPU are actually running. > > (Should I say that with OpenBSD-6.3 this was not the case.) > > What can I do ? > In which direction could I search for a solution ? > > The dmesg and Top are here after. > > regards > > ANNEXES: > -- > > Top > - > load averages: 2.06, 0.88, > 0.38 > e5450.home.lan 19:46:08 > 45 processes: 1 running, 42 idle, 2 on > processor > up 0:06 > CPU0 states: 56.3% user, 0.0% nice, 18.0% sys, 5.8% spin, 0.6% > intr, > 19.4% idle > CPU1 states: 50.6% user, 0.0% nice, 21.0% sys, 3.4% spin, 0.0% > intr, > 25.0% idle > CPU2 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% > intr, > 100% idle > CPU3 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% > intr, > 100% idle > Memory: Real: 753M/1649M act/tot Free: 6171M Cache: 628M Swap: > 0K/4220M > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU > COMMAND > 49990 vi590 405M 360M onproc/0 - 0:30 76.27% > firefox > 49459 vi 20 362M 276M sleep/0 poll 0:29 24.56% > firefox > 69993 vi 20 31M 54M run/0 poll 0:12 4.98% > Xorg > 16268 vi 20 216M 136M sleep/0 poll 0:06 2.69% > firefox > 58451 vi 20 1524K 3048K sleep/1 select0:03 1.71% > compton > 9141 vi 20 188M 99M sleep/1 poll 0:03 1.56% > firefox > 41741 vi 20 3560K 15M sleep/1 select0:05 0.44% > tint2 > 43511 vi 20 8036K 14M sleep/0 select0:01 0.00% > xterm > 1 root 100 404K 444K idle wait 0:01 0.00% > init > 78121 vi 20 5596K 17M sleep/0 poll 0:01 0.00% > openbox > > > > > DMESG: > --- > OpenBSD 6.3-current (GENERIC.MP) #140: Wed Jul 25 08:37:02 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8456654848 (8064MB) > avail mem = 8191193088 (7811MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed750 (89 entries) > bios0: vendor Dell Inc. version "A11" date 11/18/2015 > bios0: Dell Inc. Latitude E5450 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! > SSDT > SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR > acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) > PEG2(S4) > PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) > RP04(S4) > PXSX(S4) RP05(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) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.16 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,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 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.77 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R)
Re: 'UEFI install to USB' fail
Hello ! This post worked perfect for me (Shuttle UEFI only machine with a 64 GB SanDisk Extreme USB 3 stick). BUT as written there, use [OpenBSD] in disklabel instead whole disc. I had the problem, that fdisk reports, that the used device was not there even console log shows, that it was there. Solution : run fdisk -i -b 960 sdX on a working -current machine and, reboot - select install ... and again at disklabel use [OpenBSD]. Continue as described in the blog post. Am 13. Oktober 2015 08:53:26 MESZ, schrieb Tuyosi Takesima : >Hi,all . >i confess my failure . > >i read https://blog.jasper.la/openbsd-uefi-bootloader-howto/ >the reason why i cannot follow this site is that ' fdisk -i -b 960 >sd1' is >imposible in my case . > > >i write down my failure >--> > >1) boot by install58(snapshots).iso > >2)install (to USB memory ) > >3)keyboad layout > >4)use wholedisk > >custom > >a i > >size 960 > >fstype msdos > >mount point none > >a a ... > >5)follow instalation > >6)when # appers , > >/mnt/sbin/newfs_msdos sd1i >mount /dev/sd1i /mnt2 >mkdir -p /mnt2/efi/boot >cp /mnt/usr/mdec/BOOTX64.EFI /mnt2/efi/boo > > >7)halt > > >8) >i stick this USB into *another* PC ,power on , but PC cannot be >booted . >and more this PC cannot boot even with openbsd CD . >bios may die . > >what process is wrong ? >what is correct procedure ? >are there any way to re-live this PC even if PC is not respond to push >Function Key ? > >i hesitate to try until UEFI installation is matured > >tuyosi
Re: 'UEFI install to USB' fail
> 2)boot PC by openbsd CD op install58(amd64 snapshots) > install openbsd by ordinal procedure . Why you don't use OpenBSD's fdisk if you can boot from a CD ? I ask because you don't wrote this or, I missed it. > what about this ? > there may be some imcopleteness , then help me. Does it work for you this way ? If yes, then it should be complete.
Re: 'UEFI install to USB' fail
> thanks for reply . No problem. I try it but, I also know only parts of it. > 1st ) efi area should be formated fat32 . Yes, the newfs_msdos does this. This part I don't know because, the man page say's nothing about the default format - I know, you can specify it using -F. I think, it is a FAT32 but on the other hand, it is not important because the system boots on a EFI machine. > so, if openbsd's newfs_msdos equals mkfs.msdos , fail comes . > s mkfs.fat may go bad. > so i adopt linux's mkfs.vfat . Check disklabel YourDevice the i should be MSDOS. > openbsd's newfs_msdo may or may not equal mkfs.vfat. > i don't know . See above. > 2) openbsd's fdisk is **strict , and ***hard*** to use for amature > like me . > it can destroy MBR (i expirienced ). > so i use easy linu's fdisk . fdisk will write a new MBR and askes you about that. See the man page for it. The -b creates the needed boot partition for EFI. -b can only be used with -i ! > 3) install is ***OpenBSD AREA***. > > |Does it work for you this way ? If yes, then it should be complete. > yes , only 2GB USB run openbsd . I don't understand how you mean the 2 GB. But fdisk creates partitions - in this case the EFI and the OpenBSD. Check fdisk YourDevice Disklabel creates the filesystems for OpenBSD. There you also see the i from before. BUT it is a big difference to create i with fidsk or with disklabel. For the exact terms see the FAQ's. There is also explained, that the / filesystem must have a given or special size - this is a hardware and not a OpenBSD limitation. As you found out, if you use whole disk, it will not work because the EFI partition is missing. BUT in disklabel you can use custom layout and resize partitions (you must not delete them). Use ? for available commands.
Re: 'UEFI install to USB' fail
> thanks for great knowledge . ;-) > |I don't understand how you mean the 2 GB. But fdisk creates partitions - > |in this case the EFI and the OpenBSD. Check > > my experimental USB is only 2GB. > > that is > dmesg | grep sdb > [ 1268.887376] sd 3:0:0:0: [sdb] 3915776 512-byte logical blocks: (2.00 > GB/1.86 GiB) > > > this is not practical only expirimental > the next step is to install openbsd into usb ***harddisk *** > > > regards Sounds good, here an example for an SanDisk Extreme USB 3 USB stick with 64 GB. # fdisk sd1 Disk: sd1 geometry: 7628/255/63 [122544516 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: EF 0 1 2 - 0 16 16 [ 64: 960 ] EFI Sys 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 16 17 - 7627 254 63 [1024: 122542796 ] OpenBSD # disklabel sd1 # /dev/rsd1c: type: SCSI disk: SCSI disk label: Extreme duid: ba584401973042a0 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 7628 total sectors: 122544516 boundstart: 1024 boundend: 122543820 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2097152 1024 4.2BSD 2048 163841 # / b: 10950110 2098176swap # none c:1225445160 unused d: 8388576 13048288 4.2BSD 2048 163841 # /tmp e: 14185984 21436864 4.2BSD 2048 163841 # /var f: 4194304 35622848 4.2BSD 2048 163841 # /usr g: 2097152 39817152 4.2BSD 2048 163841 # /usr/X11R6 h: 14980544 41914304 4.2BSD 2048 163841 # /usr/local i: 960 64 MSDOS j: 4194304 56894848 4.2BSD 2048 163841 # /usr/src k: 4194304 61089152 4.2BSD 2048 163841 # /usr/obj l: 57260364 65283456 4.2BSD 2048 163841 # /home # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd1a 1005M 65.4M889M 7%/ /dev/sd1l 26.9G4.5G 21.0G18%/home /dev/sd1d 3.9G 12.0K3.7G 0%/tmp /dev/sd1f 2.0G368M1.5G19%/usr /dev/sd1g 1005M204M750M21%/usr/X11R6 /dev/sd1h 7.0G2.1G4.5G32%/usr/local /dev/sd1k 2.0G2.0K1.9G 0%/usr/obj /dev/sd1j 2.0G2.0K1.9G 0%/usr/src /dev/sd1e 6.7G 11.7M6.3G 0%/var # Check also the FAQ's and the corresponding manual pages. And partition resizing during install. Good luck.
Re: openbsd UIFI boot by preparing ONLY openbsd
I don't understand the question. The described way is exactly the one jasper wrotes in his blog post which you linked too at the beginning of your question. > a person tells me that he can do it by using only OpenBSD . > he says that you do not use 'whole disk '. > > i was given a goot hint . > > not using linux? > > 0)i wii install openbsd to USB HDD (sd1). > > 1) boot PC by openbsd 5.8 snapshot CD. > > 2) install but Partway > > 3) when install cd0 , cd1 appear , push ctrl +c and go to shell . > > 4) fdisk -i -b 960 sd1 > > 5) agein restart install by 'install' > > 6) when # appear , > > newfs_msdos /dev/rsd1i > > mount /dev/sd1i /mnt2 > > mkdir -p /mnt2/efi/boot > > cp /mnt/usr/mdec/BOO* /mnt2/efi/boot > > 7) reboot PC > > there may be mistake , please tell them . No, see at the beginning. > and > there must be more more sophistcated way . Sure, read the FAQ and, use ! instead of ctrl+c to get a shell without to re-run the installer. > > addition > A) look with *LINUX* > fdisk -l /dev/sdb > > /dev/sdb1 641023 480 ef EFI > (FAT-12/16/32) > /dev/sdb4 *1024 240107489 120053233 a6 OpenBSD > > > B) openbsd has ***grub*** package . > use this to boot linux > sarcasm/ My prefered way for Linux users : 1.) sudo cd / && rm -R * 2.) drink a coffee or a beer or more. 2a.) Coffee tastes perfect if you have http://www.linux-onlineshop.de/Fanartikel/Tassen-/-Keramik/Tasse-I-love-Linux.geek 3.) throw the UEFI machine out of the window. 4.) Use or buy a machine without UEFI. 5.) Install OpenBSD without tweaking around. 6.) Be happy till you are old and frey. /sarcasm Sorry, but I needed that.
Re: Because Theo and various users told them that the projects GnoBSD and Comixwall were worthless and that they weren't contributing to OpenBSD?
> I always find it amusing how OpenBSD is "audited", yet there's not one > audit > report on the OpenBSD website. The closest answer I've been able to find > on > the mailing list is to review all of the CVS commit logs. Yeah, that's not > opaque in the slightest... Yes, thats it. The audit of the project is the reputation of Theo de Raadt and the developers in the project. As a coder, you can look at the CVS tree, as a none developer you have to trust the project, as you would trust Microsoft, Apple, Ubuntu or other operating system creators. What helps, if you get a certified by - nothing. On the project website is a line of text kept in red - thats it. Why ? Simple because with every change a user made to the system the audit is destroyed. > The bigger problem with OpenBSD is it's community. In the FreeBSD world, > you > have PC-BSD and pfsense, both of which are generally welcomed by the > community. With OpenBSD, there were two sister projects that tried to > target > a similar audience: GnoBSD and Comixwall. Comixwall was the equivalent of > pfsense for easy router/firewall management and GnoBSD was an attempt to > make an easy-to-use desktop. Both, however, ended up shutting down after > Theo and various users told them that their projects were worthless and > that > they weren't contributing to OpenBSD. I readed only parts of the posts but, the main reason was, that this projects tried to use misc@ for promoting their projects. What they gave back ... code, donations from their userbase ... I don't know. So, if they did, it would maybe change the situation. > Because Theo and various users told them that their projects were > worthless > and that they weren't contributing to OpenBSD? I think worthless is the wrong word. To create a GUI installer is something like to reinvent the wheel. A better way would be a discussion about what people want or need. In OpenBSD are some unwritten rules - I think. OpenBSD had no GUI installer and, will not have one ... for what, the existing does the job well. If a user wants a GUI installer, there is PC-BSD, Ubuntu and so on. Gnome, many people like it and, many hate it. Whats wrong with a cool configured fvwm ? I think, people had to re-learn functionality. If someone wants to create a Live-CD, people could find the project using Google.
Question about core dumps and swap space.
Hello ! I readed the FAQ 4.8 about partioning my drive but have a little problem of understanding. The machine has 32 GB physical RAM, the disc is a 256 GB SSD (yes, I know, I should not use swap on a SSD) and, I installed the latest snapshot from yesterday. So far so good. Disklabel likes to create in auto layout b: swap with 23,2 GB and e: /var with 30,2 GB. If I follow the FAQ, then core dumps should not work. I could resize swap and /var to have the same (or bigger size) as the physical RAM which is also no problem. My question - or better the things I don't understand (I found no informations and also had no panic message till now) are, which size had a core dump and, will core dumps work, if swap (on /var is enough place to copy the core dump file from swap to /var/crash after a reboot) is smaller then the physical RAM ? My question is meaned, that swap is only used for core dumps - nothing more. Thanks for your answers. Regards, Christoph
Re: Question about core dumps and swap space.
Thanks for your answer. > On Mon, October 19, 2015 8:01 pm, Joel Rees wrote: >> >> I have lots of core dumps sitting around. I have not seen any the size >> of physical memory. Nothing close. Even firefox doesn't leave that >> much of a dump when it bombs. >> >> Hmm. Xombrero, from when I was playing with that, left a coredump of >> 512M. Firefox left one at 197M. Time to rm those. >> >> Why do you have 32G of RAM? What kind of working sets do you expect >> the applications you'll be running to have? >> > > He's referring to savecore(8) dumps when the kernel crashes, not > application crashes. > > Tim. Yes, thats true. But no problem to answer that.
Re: Question about core dumps and swap space.
Thanks for your answer. > 2015/10/20 6:29 "Christoph R. Murauer" : >> >> Hello ! >> >> I readed the FAQ 4.8 about partioning my drive but have a little problem >> of understanding. >> >> The machine has 32 GB physical RAM, > > Wow. Way cool. Yep. > >> the disc is a 256 GB SSD > > That's not shabby, either. It was there, I prefer a good old HD. >> (yes, I know, >> I should not use swap on a SSD) > > Have you been reading this thread? > > http://marc.info/?t=144492611700013&r=1&w=2 Yes, I readed it in parts but, thanks for the link. >> and, I installed the latest snapshot from >> yesterday. So far so good. >> >> Disklabel likes to create in auto layout b: swap with 23,2 GB and e: >> /var >> with 30,2 GB. >> >> If I follow the FAQ, then core dumps should not work. > > 2G RAM, 4G swap on my netbook running openbsd. > > I have lots of core dumps sitting around. I have not seen any the size > of physical memory. Nothing close. Even firefox doesn't leave that > much of a dump when it bombs. > > Hmm. Xombrero, from when I was playing with that, left a coredump of > 512M. Firefox left one at 197M. Time to rm those. Yes, Xombrero is nice, I hate Firefox (maybe it is because my first browser was Mosaic / Netscape). >> I could resize swap >> and /var to have the same (or bigger size) as the physical RAM which is >> also no problem. My question - or better the things I don't understand >> (I >> found no informations and also had no panic message till now) are, which >> size had a core dump and, will core dumps work, if swap (on /var is >> enough >> place to copy the core dump file from swap to /var/crash after a reboot) >> is smaller then the physical RAM ? My question is meaned, that swap is >> only used for core dumps - nothing more. > > So, you don't plan on using swap for deep sleep or powered-down system > suspend? Nope, because suspend works but resume not. I will send a dmesg later, maybe someone is interested. A user at bsdforen.de told me, that is because of the optimus (you can't switch off the discrete GPU in the BIOS) in the machine (I don't know whether this is true or not). But it is not important because even I had in the past another operating system, I used it not really. > Why do you have 32G of RAM? What kind of working sets do you expect > the applications you'll be running to have? I bought the machine (a ThinkPad W541 with optical drive) as offered (the only ThinkPad with optical drive at this time) at the European u:book project, where you can buy hardware (twice a year) with round 20 % discount. At the time I bought it, I hadn't decided whether I stay (I came from Mac OS X) with Linux (because of the hardware support) or FreeBSD. After playing around, I remembered, that I saw round 1997 (or maybe it was a littlebit later - can't remember) the OpenBSD website (cool time with ISDN) and I gave it a try. What should I say, it simple worked out of the box and, does what I want / need (thanks to all developers). So, the machine is already there - now it will be used with OpenBSD. > Do you expect chain-reaction core dumps, where one application hits an > uncaught exception and dumps core and then its parent or some other > application that is communicating with it bombs and dumps core, too? ;-) > In other words, do you expect to ever have all 32G filled with stuff > that all at once dies and dumps core? Nope, but as I wrote, it is already there.
Re: Question about core dumps and swap space.
Thanks for your answer and, the detailed explanations. > The core dumps in question here are for when the OS panics. Core dumps > can be used by developers to look at what went wrong, but in order to do > so, you may need everything that was in RAM at the time of the panic. That answered my question fully, thanks. > So...the kernel can dump to swap (whatever was in swap wasn't in RAM, > thus wasn't part of what caused the panic). On next boot, savecore will > find the dump in swap, and save it to /var. > > So that means swap has to be at least the size of RAM and you have to > have AT LEAST that much space FREE on your /var partition. Your 256G > SSD just got ~70G smaller. Ouch. Yes, that I understood. > ... or ... > > you can look at the big picture and realize... > 1) you probably aren't a developer. > 2) you probably haven't seen a core dump. Yep, true. > 3) you probably wouldn't know what to do with the core dump. Me not (who knows what comes in the future) but, a developer. > 4) if you got a core dump and wanted to send it to a developer, a 32G > core dump would probably create a lot of problems for everyone. Yes, from the view of a user (I have no problems to admit, that I don't know things), I don't expected, that a core dump really could have 32 GB of size. As you say before - Ouch. > 5) that's a freaking big chunk of your SSD devoted to stuff you are > unlikely to ever do anything with! Yep, I will delete swap and use it for other things. > and thus, I'll suggest you just don't worry about it. IF you manage to > find a way to panic your machine, drop the memory wy down to 2G or > so, reproduce it and worry about a 2G core dump. Not possible, there are 4 x 8 GB in it. Where we are again at the size problem from before. > And -- even if you do have a system panic, very often developers can > make sense out of what went wrong from the output of the debugger's > trace and ps commands, rather than having to dig through an entire core > dump. This is always what they ask for FIRST. Ok, I use OpenBSD only for some weeks / months more or less often. I got back my ThinkPad from repair and took now more time to read things and play around ... it is like a puzzle where you come across this kind of questions.
Re: Question about core dumps and swap space.
Hello ! Thanks for your answer. > Nick, In this case boot.conf: > > machine memory=2G > > would be enough? or should one get other ram sticks...? > > Thanks I keep it as option. For now and till I experienced no panic, I will use the SSD without swap. If I replace the SSD with a normal (big size) HD, I will not care of 32 + something GB for swap.
Re: Question about core dumps and swap space.
> Forgot about that... [ ... ] Yep, I will do that and, keep that > But still -- remember what developers ask for most often: a good problem > report: panic message, trace and ps output, a dmesg and info about how > to repeat the problem. If people would reliably provide that, they'd > make developers very very happy. in mind. Thanks.
Re: Question about core dumps and swap space.
Thanks for your answer. > One of the nice things about having a successful savecore(8) is that > the captured dump can provide all the critical bits. So dumps are very > useful to have. Tools like ps(1) and dmesg(8) have -N and -M options > for > post-mortem analysis. > > The crash(8) man page has been extremely helpful to me over the years. > And, there's > also very helpful guidance in FAQ 2.4. > > I've never sent anyone a crash dump, but I've certainly pulled info > from them to make a dish of copypasta. At the first crash, I will come back to that.
Re: Question about core dumps and swap space.
Thanks for your answers. The best would be, to use the man pages if needed. For now, my main question is answered - all other things will come from alone. >> And -- even if you do have a system panic, very often developers can >> make sense out of what went wrong from the output of the debugger's >> trace and ps commands, rather than having to dig through an entire core >> dump. This is always what they ask for FIRST. > > Exactly. > So how do you extract this information from a modern laptop without > serial? Your question is true. But let's stop this on this point because it will end in argue or a flame. I forgot in the OP to tell, that the ThinkPad has no serial port.
ThinkPad W541 resume doesn't work.
Hello ! Don't tread this post as bug. If it works nice - if not also no problem because I don't need it really. I have a W541 where suspend works but resume not. The machine has no serial port. But beside the i7 a nVidia optimus which can't be switched off in the bios. If I close the lid after a normal installation it suspends but, if I open the display it doesn't resume. Even not, if I press some keys, the power button is blinking and, the display stays black. The only way is, to press the power button till it switches off. If I switch it on again, it doesn't boot. Instead I have to press and hold the power button again, till it is really off. If I set in rc.conf.local apmd_flags="-C" I can reproduce it using zzz and ZZZ. In booth the same. The only difference is, that in one of them (I can't remember which one but I think you know which it is) I have only press the power butten once to switch it off. At the moment I set in sysctl.conf machdep.lidsuspend=0 and, can confirm, that the display switch on after I open it for something like 1 centimeter. If someone is interested to look at it and, more informations are needed, let me know. Regards, Christoph dmesg : OpenBSD 5.8-current (GENERIC.MP) #1527: Sun Oct 18 14:40:13 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33939300352 (32367MB) avail mem = 32906575872 (31382MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (69 entries) bios0: vendor LENOVO version "GNET73WW (2.21 )" date 03/12/2015 bios0: LENOVO 20EFS00B00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA UEFI POAT ASF! BATB FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 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) i7-4810MQ CPU @ 2.80GHz, 798.33 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 798.15 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 798.15 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 798.15 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 798.15 MHz cpu4: 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 2, package 0 cpu5 at mainbus0: apid 5 (application processor) cpu5: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 798.15 MHz cpu5: FPU,VME,DE,PS
Re: ThinkPad W541 resume doesn't work.
Ops, typo in the email adress. Answer is below. >> Try *completely* disabling the Trusted Platform Module (TPM) in the >> BIOS. > > Thanks @all for your answers. > Yes, TPM which is named in BIOS Security Chip was enabled. Got the > ThinkPad back on friday from Lenovo from a repair and don't checked > the settings because everything worked. > > Machine resumes with a (my first) kernel panic and a ddb prompt. I > have to read the related docs to report the needed things.
Re: iPhone?
> I just connected an iPhone to my OpenBSD box and it doesn't seem > possible to access its memory. Is there any way to make this work? In > fact, is there anything at all that can be done with OpenBSD and an > iPhone...? I have tried that with a up to date Ubuntu and a iPhone 4 running iOS 6 without jailbreak and it worked. They use libimobiledevice for that. There is a git repo (named openbsd-wip) out there https://github.com/jasperla/openbsd-wip/tree/master/devel/libimobiledevice I haven't tried it because I have no need for it but maybe it helps - or, maybe someone else could help you (check out http://www.libimobiledevice.org/ for supported devices and, supported iOS versions).
Re: Advices for a new laptop
> Thinkpads are over my budget (i find them starting with the E550 at > 758⬠> on my usual reseller). It depends whether you want a new or a refurbished model. Here in Europe refurbished X201 with Intel i5 / i7 are available for round 300 Euro (depends on, what is in it). > What about the B50-80 (80LT003C): i3, Intel HD 4400, wifi B/G/N/AC, > Gigabit Ethernet, 2x USB3. > Unfortunately i can't find for sure which wireless cards is used > (probably Intel Dual Band Wireless-AC 3160). > If it can allow me to do the little 3D editing i need, it would be a > good fit. > > Any information about OpenBSD support for this thing? > (From what i gathered the Intel HD 4400 should work, right?) My Intel HD 4600 (i7) in a W541 works with 2880x1620.
Re: Linus Torvalds thoughts on Linux Security
> On 08/11/15 04:26, Eric Furman wrote: > I'm not a troll. Just saw the thread on Slashdot and thought it > would be interesting to see what other people thought. > > I'll refrain from posting such things in the future if the only > response I get is being called a troll (which is a really > unimaginative insult by the way). > You used the words *provoke a bit of a debate* in your OP. If you remember back, as you readed FAQ 1.5 *It's also worth mentioning one of the most important ways you should not try to "help" the OpenBSD project: do not waste your time engaging in operating system flame wars. It does not help the project to find new users and can cause substantial harm to important relationships that developers have with other developers.* Also, as you subscribed to the list, you readed the *Netiquette* - specially *Respect differences in opinion and philosophy*. If you try to start a flame or something else, it will end in a virtual kick in the ass. Compare it - what will happen if you start somewhere a discussion like Vim versus Emacs or MySQL versus PostgreSQL ? Don't be insulted - simple do your homework as expected. What I think about *Linus Torvalds thoughts on Linux Security* ... the best security solution is, if the Penguin stays at its natural habitat - Antarktika.
Re: can't boot from USB3.0 flash memory
See http://www.openbsd.org/mail.html *The only mailing list that allows attachments is the ports list, they will be removed from messages on the other mailing lists.* > gmail didn't show any attachment. > On Nov 27, 2015 3:20 PM, "Tati Chevron" wrote: > >> On Fri, Nov 27, 2015 at 02:31:32PM +0200, Ville Valkonen wrote: >> >>> On 26 November 2015 at 15:26, wrote: >>> >>> I have USB3.0 flash memory.(SANDISK) "OpenBSD 5.8 amd64/i386 on USB3.0" 1.USB3.0 flash memory connect to USB2.0/1.0 boot: It's fine. 2.USB3.0 flash memory connect to USB3.0 boot: can't boot! anyone don't need boot from USB3.0? >>> Hi, >>> >>> do you happen to have an HP machine? >>> >> >> Didn't you read the attached dmesg? >> >> -- >> Tati Chevron >> Perl and FORTRAN specialist. >> SWABSIT development and migration department. >> http://www.swabsit.com
Re: can't boot from USB3.0 flash memory
> On 27 November 2015 at 12:31:32, Ville Valkonen > wrote: > > Thanks for your good hints:) > > some laptop pc have this problem :< [ ... ] > manula is almost good. but, some same problem issues didn't share on. > mailing list is good means. but latest machine problems are stacked > and > no improvement. I am no developer but have you already posted a dmesg (inline in the email ?). See http://www.openbsd.org/mail.html section Include important information. *The dmesg(8) tells us exactly what is IN your machine, not what stickers are on the outside.* How to get a dmesg - simple read the FAQ 4.10. > who makes driver or good improvement. but beginer and newest user > didn't > know how to get answer. I am also a new user and have no problems to get a answer, as long as you ask the right questions and, provided the needed infrmations. > dmesg is no answer. who get kernel panic... "how to get debuging..." > (these todo couldn't get answer...) dmesg would be no answer for you - but for developers it helps. Kernel panic, debugging - start reading FAQ 7.6 about serial consoles and http://www.openbsd.org/report.html section How to create a problem report. > some mailing list responses are like "read man" "man 4 ..." :< > and get no answer... Sure, there are people out there who wrote the FAQ, there are people out there who wrote the text for the mailinglist page ... and, there are users out there, which are simple not interested to read existing informations. If you ask a question like, I have problem X and readed manual page Y but I simple don't understand it - I think, you will get a answer. If you expect, that others do your work - you will be very disappointed about what you get. > if "no answer", say "no answer" or "I don't know". > problem must store and announcement. See the above. > Just my complaint. > > Theo de raadt is greatest programer. I love him. I think, he will be very happy if you read the FAQ and provide the minimum informations which are needed to answer your questions.
Re: A branded USB stick as an alternative to the CD set?
>> Em 30-11-2015 19:03, Tati Chevron escreveu: >> > Again, the original idea wasn't mine. I commented on the thread, >> but in >> > my mind, I imagined receiving the install source on a medium that >> had the >> > same bar to tampering as a CD, such as masked rom. I wasn't >> thinking of >> > a standard USB flash device with a glued write-protect switch. My >> > original >> > post was a mixture of various thoughts that shouldn't really have >> been >> > posted >> > without further consideration. >> I don't know if most people are aware of this, but this has been >> discussed on this list many times. The income of CD sales are what >> "kind >> of" pays for Theo full time involvement with OpenBSD. I say "kind >> of" >> because sales, as he already mentioned, are going down and down each >> release. > > These days the CD revenue is about what a cashier at a store makes. > > It seems to keep shrinking, but I will try to keep doing it unless it > nears zero; at which point the artwork will stop also. > > I'm not doing any of this as a business. I believe the research and > development that happens within OpenBSD is very important. That's why > I continue doing this. > > I cannot help but be insulted to the core when random 'people on the > internet' selfishly or unthinkingly misunderstand the focus of OpenBSD > as a R&D project, and recommend an even more broken business plan > which nobody needs or wants. Frankly, it ruins my day. As more as I read, as more I understand you. > For the time, I am on a small bursary as well from some people who > understand the importance, otherwise I'd be looking for a cashier job. Please, continue it for the people which understand it or, which are interested in it. Thanks.
Re: A branded USB stick as an alternative to the CD set?
> How about a series of 'Corporate' CDs, with a sliding scale of prices, > incrementing on a traditional per user/account/cpu/etc basis? > > Management & purchasing people are accustomed to this. [ ... ] I (only my personal opinion) think this contradicts with the main goal (Free) of the project. See FAQ 1.4 and the donations page *Such contributions are considered strictly gifts to the OpenBSD Project, [ ... ]* If a company pays in a kind like you suggest, then they expect something like a service contract or a way to influence the project.
Re: A branded USB stick as an alternative to the CD set?
> I don't see any issue with a company wanting custom work done on the > project as long as it doesn't contradict the goals of the project. > > For example, a company might want to pay more to improve particular > hardware drivers, is that really a problem? > > Consulting could be a good way to raise funds for the project while > also > encouraging usage. See tedu@'s suggestion in the next message (I don't want to replay twice). There are 2 other points. First, Theo's day has only 24 hours (who should do it ?) and second, does he want to do that (that his project go this way) ? If you like to start a project like that and, if you find people who help you - great (serious meaned !). From the income you could donate direct a part to Theo.
Re: Wifi Configuration | Realtek RTL8191SE
Hello ! As workaround you could look - for example - at the following USB WiFi adapter. TP-LINK WN725NN (should be that model but I am not 100% sure) Edimax EW-7811Un Booth work (not perfect) with urtwn. I had to many WiFi networks around me so, I switched back to a Android tablet and use USB tethering for my internet connection (LTE). > Stefan, >Thank you very very much for your attention. When i grow up, i > would > like to be like you =P. Unfortunatelly I don't program anymore, to get > the > knowledge to do this i'll spend a lot of time, but it's my intention > to > come back to study computer programming and maybe in a future helps > the > OpenBSD team. > I understand your cares to keep the originality of the OS and > that's > what makes me and others to prefer to use the OpenBSD. > > Thank you very much! > > > > Luiz Diego Fernandes de Moraes > > > 2015-12-11 15:28 GMT-02:00 Stefan Sperling : > >> On Fri, Dec 11, 2015 at 02:37:54PM -0200, Luiz Moraes wrote: >> > Hi Stefan, >> > I already downloaded from >> http://firmware.openbsd.org/firmware/5.8/ >> the >> > firmwares *rtwn*, *rsu and* u*rtwn *and installed them all with >> *fw_update*, >> > later i restarted the laptop but the status on *dmesg *is the >> same. >> >> There's a difference between driver and firmware code. >> The driver runs on the OpenBSD kernel (it's part of the /bsd file) >> and the firmare is loaded into the device as part of making >> the device operational. >> >> The rtwn(4) driver only supports RTL 8188CE devices at present. >> Your chip is a cousin of that chip, but it's different and the >> driver does not know how to make it work yet. Once the driver >> supports your chip, the required firmware will also be shipped >> in the rtwn-firmware package. >> >> > I really would like to can keep OpenBSD as the main OS, but >> maybe >> i'll >> > have to get FreeBSD to use the *ndisgen (*Is the ndiswrapper for >> FreeBSD >> > and DragonflyBSD). >> >> You could also use a support USB wireless device, for now. >> Run this command: >> man -k wireless >> to see a list of drivers and look at the USB ones. >> >> With some effort you'll be able to find a supported device, for >> sure. >> I often find supported devices on ebay for just 1 euro + shipping. >> >> You can also find some USB devices supported by run(4), urtwn(4), >> or athn(4) sold new in some stores around the world. But with >> used devices chances of support are somewhat higher. >> >> If your machine is a laptop that has a cardbus or express card slot, >> you could also try to find a cardbus card supported by drivers such >> as ath(4) and ral(4) (+ cardbus -> express card adapter if needed). >> These tend to work very well. >> >> Note that the time you would spend on hunting down a supported >> device >> is very small compared to the time it takes to add code to the >> driver >> to support your device. Eventually somebody (maybe me) may find time >> to add this support. It would take me at least a week of sitting >> down >> and working hard. I'd need to take that time out of other things in >> life, so I cannot promise anything. Developers who have never done >> this before would need even more time. >> That said, my plan already was, before your mail, to support more >> realtek >> devices in rtwn(4) eventually. I just don't know when it will >> happen. >> >> > Can i get the *ndisgen *from FreeBSD and run on OpenBSD? (I >> woulnd >> like >> > to change it, but if the OpenBSD doesnt give me options i'll have >> to >> find a >> > way to keep me with it) >> >> No. There is no support for binary blobs in OpenBSD, and there never >> will >> be. >> We prefer writing code that makes blobs unnecessary.
Current #1740 on a MacBook Pro 9,1.
Hello ! If the message is not correct formated, I am sorry (SquirrelMail from my provider is not available at the moment). I tried the latest snapshot #1740 from today on a MacBook Pro 9,1 (mid 2012, the last one with optical drive and without Retina display). Boot from USB worked, installed the first time with all default values from the installer - everything till X worked out-of-the-box. Second try with full disc encryption and GPT fails after the passphrase was entered with *can't read disk label, failed(96)* (full output message could be provided if someone needs it). Third install with MBR and full disc encryption worked without any problems till X (wrote this email on the machine). asmc works including keyboard backlight (for the sensors see dmesg below). Suspend works, resume doesn't work. When I close the lid the machine suspends as it should. When I open the lid, the display stays black and the keyboard backlight is off. Pressing the power button for short time results in a shutdown - with no filesystem check at the next reboot. Resolution in X after install : $ xrandr -q xrandr: Failed to get size of gamma for output default Screen 0: minimum 1680 x 1050, current 1680 x 1050, maximum 1680 x 1050 default connected 1680x1050+0+0 0mm x 0mm 1680x1050 0.00* USB tethering using urndis worked without problems (dhclient needs - as always - two tries to get a connection using a Nexus 7). If more informations are needed, let me know. dmesg : OpenBSD 5.8-current (GENERIC.MP) #1740: Fri Dec 11 11:38:58 MST 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error df real mem = 8509272064 (8115MB) avail mem = 8247255040 (7865MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe1010 (83 entries) bios0: vendor Apple Inc. version "MBP91.88Z.00D3.B08.1208081132" date 08/08/2012 bios0: Apple Inc. MacBookPro9,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 SSDT SSDT SSDT DMAR MCFG acpi0: wakeup devices P0P2(S3) GFX0(S3) PEG1(S3) EC__(S4) GMUX(S3) HDEF(S3) RP01(S3) GIGE(S3) SDXC(S3) RP02(S3) ARPT(S3) RP03(S3) EHC1(S3) EHC2(S3) XHC1(S3) ADP1(S4) [...] 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) i7-3820QM CPU @ 2.70GHz, 1197.48 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,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz, 1197.29 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,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT 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) i7-3820QM CPU @ 2.70GHz, 1197.29 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,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT 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) i7-3820QM CPU @ 2.70GHz, 1197.29 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,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz, 1197.29 MHz cpu4: 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,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cp
Re: text-mode gui
> I don't know the best way, but I like how there are "check-boxes", > from what I recall, in lynx webpages. Means in short, you like lynx. There was a long discussion at misc@ why lynx was removed from the base system. See http://marc.info/?l=openbsd-misc&r=1&w=2 to search for it. > Maybe full-disk encryption and maybe home folder encryption if it > is available are the only remaining installer options that you > don't have to have prior specialized knowledge to perform, that you > can't do after you boot into the system. Not all people want / need full disc encryption. It is no problem to configure it during installation using a shell. If full disc encryption is provided by default, how you like to handle the point if users came with the question ... can you help, I forgot my passphrase / lost my keydisc ? Counter question, what is the benefit to encrypt the home folder and the rest of the system not (see also discussions about security, pysical access to a machine and also about JavaScript) ? > But maybe the OpenBSD way is about no surprises, but it doesn't seem > right to only be able to boot into the system in the way you > want, if you have the mindset of a Computer Scientist like us, and > read the right configuration webpages. OpenBSD don't wants to be like other operating systems and, it provides the freedom to do everything you like / need / want. > Things like not having softdep mounted file systems by default > really tripped me up for a couple versions. I think, that is the same discussion as full disc encryption - do really all poeple need / want it ? There is many documentation out there like for example for full disc encryption : http://www.bsdnow.tv/tutorials/fde or books like : http://www.openbsd.org/books.html and, I think noone will bite you if you ask.
Re: HUAWEI dongle
>>Please send dmesg and the output of: > >>usbdevs -dv > >>Both while the Huawei dongle is plugged into your machine, of >> course... > > > Would love to be able to do that. Anybody had any success mounting an > OpenBSD > file system in linux? > > > 0x00 > > Use a USB stick, create a new FAT32 filesystem using newfs_msdos under OpenBSD, copy your dmesg and the output of the other commands there and plug it in at your $PENGUIN box ... worked for me some months ago with Ubuntu. If the steps are required let me know.
Re: text-mode gui
> I don't need a special need case. I have already configured the system > I need, but it would have been nice to know about these configuration > options earlier. Just curious, if you have already a configured system why you then complain about things like that ? The entry point for OpenBSD is RTFM (Read The Fucking Manual). I pointed you to 2 links with informations about things you want which are there already for some years. Counter question, instead of complaining - do you run a website or wiki to provide useful informations for new users ... or are you doing other things ? > Anyway, my point is that OpenBSD doesn't need to be a research OS as > Theo has stated. The point is, OpenBSD is Theo and vice versa. Theo created that, what this community wants and needs. > It could have some minor tweaks to the install that undoubtedly > could persuade users to continue. The main problem is, many people are not interested to read informations or to spend money for books and so on. If people had problems, they could ask. > But maybe that is the mindset of the OpenBSD hacker. Make it hard > and difficult for everybody that doesn't want to spend their life > away searching for commands they don't know about. Comeon, I am also a normal user and have a working system with full disk encryption. So, what is so difficult ? > If my Asus laptop, which I figured out at the time needed to disable > a configuration option, would have accepted feeebsd, I suspect I > would have gone with them. Not because they had more up to date > software systems like kde, but because their system doesn't put up a > fight against the user and doesn't self-destruct any time it needs to > fsck: By Default. I started with Linux and continued with FreeBSD and experienced this things there. It is really a pain in the ass to get in FreeBSD a console with german umlauts - which I had in OpenBSD by default after the install. I run OpenBSD for round 8 months with breaks. In this time I hade no fsck and 1 kernel panic which was my fault. The main point is, noone force people to use OpenBSD ... as Theo would say, if it is not for you, choose another operating system. The rest of the discussion is useless but, as more as I read at mics@ I understand, why developers really get pissed-off from time to time.
Re: text-mode gui
> You are a normal user and have full disk encryption. You must have > read the man page on how to do that? I was curious and asked my favourite search engine for *openbsd full disc encryption* and got results like http://www.bsdnow.tv/tutorials/fde, readed them and found the needed commands. Yes, after that I looked in the man page what the people there had done. > Found the installer option did you. Don't know, what you exactly mean. > I have read several books on openbsd and all the man pages I could > find and didn't find out how to do it anywhere else other that how to > webpages. Really, *Absolute OpenBSD - Unix for the practical paranoid, second edition* page 166 *Encrypted Disk Partitions*, page 167 the bioctl command including required switches. IMHO you wrote on 2015-12-21 (taken from marc.info) *I can do that. [ ... ] Easy Peasy!* - the community and the developers will judge you based on your words. If you don't hold your promise, you have earned the virtual kick in the ass.
Re: if I were to make a pkg-add diff
Luke, ... Are you sure that you're not in politics ? > I suppose folks could opt for the more stable yet higher latency > official mirrors even if they aren't local to canada and they would > never be surprised. It may not be too much trouble for me to implement > a mere stdout statement in the perl pkg-add to advise the user to > update PKG-PATH to randomly offer one of the official mirrors as the > PKG-PATH (as an easy to implement fix) and steer the user to install a > web-browser to discover the current list of http/ftp package mirrors > if Firefox or lynx exists on the system; since they don't by default. > It wouldn't be too dissimilar to the kind of messages delivered by > pkg-add itself to rm folder contents at the end of a run. > > On 12/25/15, Luke Small wrote: >> I suspect that if you did, it wouldn't check whether there was an >> astronaut ready to control the on-board computer and would sit there >> continuously trying to rev the rocket engines with no jet fuel. That >> is the way pkg-add acts right now. I felt pretty ridiculous >> wondering >> why pkg-add wasn't working only to figure out I was working with a >> mirror that was no longer active this week. >> >> On 12/24/15, Theo de Raadt wrote: I wanna make a c program that checks for a PKG_PATH that exists and connects to a workable link for pkg_add(). >>> >>> and I wanna build a rocket ship... >>> >> >> >> -- >> -Luke
Re: if I were to make a pkg-add diff
Quote from dan mclaughlin : [ ... ] > (i am really starting to feel for the devs. this gets wearying.) [ ... ] > whenever i want something to work the way i want, i just script around > it. > the beauty of unix. Explains it very good. I personally think, OpenBSD is simple not for Luke. What Luke does, is simple unfair towards the developers and also towards new users which are willing to learn and maybe use OpenBSD only as users. For Luke, read the following : http://www.openbsd.org/mail.html Do your homework before you post [ ... ] the FAQ and the relevant man pages (start with afterboot(8)), and check the mailing list archives. We want to help, but we wouldn't want to deprive you of a valuable learning experience, and no one wants to see the same question on the lists for the fifth time in a month. Respect differences in opinion and philosophy Intelligent people may look at the same set of facts and come to very different conclusions. Repeating the same points that didn't convince someone previously rarely changes their mind and irritates all the other readers. http://www.openbsd.org/faq/index.html 8.14 - What web browsers are available for OpenBSD? - for lynx and the relevant discussions about it at misc@. 14.6 - Soft Updates - for softdep 8.21 - Does OpenBSD support any journaling filesystems? - for softdep yes or no. 1.11 - Why is/isn't ProductX included? Why isn't there a graphical or curses(3) based installer? For a number of reasons, including the goal of keeping the installation boot media able to be a single floppy disk, the fact that one installer can be used on all platforms in all configurations, and the fact that after the second or third OpenBSD install, most users find the OpenBSD installation system among the fastest and easiest installers of any OS. Most developers and users greatly prefer the speed, power, and ease of use of the current installer to any of the more "colorful" or "pretty" installers on some other platforms. In most cases, these topics have been discussed in painful detail on the mail lists, please see archives if you need more information. - for your (Javascript) installer idea. 14.2 - Using fdisk(8) 14.3 - Using OpenBSD's disklabel(8) 14.21 - How do I use softraid(4)? + man page - for full disc encryption. And yes, it is expected, that you can handle this tools befor installing the system ! 15.2.2 - Making things easy: PKG_PATH - to define more then one mirrors. You should stop to reninvent the wheel or, to create problems where are none. You should start to RTFM (Reed The Fucking Manuals) or, buy a OpenBSD relevant book - as others also did. You also should do the following *shutup and hack* instead of always complaining. Let's say your idea for pkg_add is cool, let's say you make a clean install or a update using bsd.rd and, let's also say, that you have no supported network device - without the firmware from firmware.openbsd.org ... what's next ?
Re: if I were to make a pkg-add diff
> Come to think about it, it might to be good to do tiny standalone > program called pkg_ping and then I could make it in C like I'd prefer. > I'd hope to make a port maybe, but then it would functionally defeat > the intent. I find it not usefull to continue this kind of conversation because you don't listen to others. Make what you have planned, send a diff and, let's wait what the future brings. Personally I see no benefit in this ideas.
Re: if I were to make a pkg-add diff
> I guess I didn't really answer your question. It wouldn't rely upon > the ramdisk. It is meant to run after install. So it would presumably > have all the firmware. Then I think, you have to be more clear. Because it is not to modify the installer and also not, to modify pkg_add - as you wrote before. If you like to check the fastest mirror you also have to keep in mind things like, is the interface up, geolocation, is Tor or a VPN used and so on ... P.S. What is then with the main idea for new users ?
Question about urndis_decap invalid buffer len 1 < minimum header 44
Hello ! Could someone tell me please, where I could find more informations about the following message in /var/log/messages ? Jan 3 00:48:38 thinkpad-w541 /bsd: urndis0: urndis_decap invalid buffer len 1 < minimum header 44 Jan 3 00:49:13 thinkpad-w541 last message repeated 8 times The ThinkPad is connected over USB with a TP-Link M7350 LTE modem. Internet is configured using /etc/hostname.urndis0 which contains only the line dhcp. /etc/pf.conf is unmodified and, kept as after installing 5.8 -release. Thanks for answers. OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33939300352 (32367MB) avail mem = 32906813440 (31382MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (68 entries) bios0: vendor LENOVO version "GNET73WW (2.21 )" date 03/12/2015 bios0: LENOVO 20EFS00B00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI POAT ASF! BATB FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 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) i7-4810MQ CPU @ 2.80GHz, 2793.92 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz cpu4: 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 2, package 0 cpu5 at mainbus0: apid 5 (application processor) cpu5: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz cpu5: 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 2, package 0 cpu6 at mainbus0: apid 6 (application processor) cpu6: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz cpu6: 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,
Re: Question about urndis_decap invalid buffer len 1 < minimum header 44
> On 01/02/16 18:03, Christoph R. Murauer wrote: >> Hello ! >> >> Could someone tell me please, where I could find more informations >> about the following message in /var/log/messages ? >> >> Jan 3 00:48:38 thinkpad-w541 /bsd: urndis0: urndis_decap invalid >> buffer len 1 < minimum header 44 > > I think its due to an ethernet header not being of the correct size. Thanks for your answer. I think, the message came because this device doesn't work with the urndis driver. It is no complain against the driver or OpenBSD - I simple like to know, what causes the message (a Android table before, doesn't show the message). Because all other things works in round 99% and, the device itself provides no options to change. >> Jan 3 00:49:13 thinkpad-w541 last message repeated 8 times >> >> The ThinkPad is connected over USB with a TP-Link M7350 LTE modem. >> Internet is configured using /etc/hostname.urndis0 which contains >> only >> the line dhcp. /etc/pf.conf is unmodified and, kept as after >> installing 5.8 -release. I tried to add to pf.conf the line match in all scrub (no-df max-mss 1440) from The book of pf without a result (maybe it was the wrong idea). At the end, I added one TP-Link USB micro Wi-Fi adapter and the message wasn't shown again. It is not perfect but it works (it is simple the wrong hardware).
Re: Newbie question: Proxy for appearing in Sweden for on demand streaming?
> Hi all! > > My mom lives in Sweden but spends loads of time in Spain. She likes > the > public service online TV streaming service, which cannot be watched > abroad > for various reasons. I thought I'd try to setup a proxy of some sort > that > she could turn her iPad to, and appear as if in Sweden while in fact > in > Spain. I live in Sweden and have a 5.8-stable box handy. > > How would I do that? Can relayd help here? What do I need in terms of > network setup etc? > > Any pointers would be appreciated (except flames). > > Happy new year! > Andreas > > Hello ! Keep in mind, that it is not legal in the EU to bypass geolocation limitations (but, that is your problem). Basically to your question (you don't write something about your internet connection in Sweden and, the internet connection in spain), you need in Sweden a public IP. Setup on your box in Sweden a VPN server and connect from the iPad using one of the VPN clients out there ... or, pay a commercial VPN provider.
Re: ls cant print higher UTF-8 chars
> Hello misc! > > In an attempt to get a better idea on how to make all non-ascii chars > appear correctly in windows/samba, ssh and the local console I get the > impression that UTF-8 is the charset that is mostly used in general > and > also most growing. > > Using UTF-8 in samba and ssh on a OpenBSD 4.9 i386 generic machine > that is > about to retire works as expected, tested with swedish and icelandish > letters outside the 7bit ascii range. > > However, the new machine to replace the 4.9-box, running OpenBSD 5.6 > on > amd64 generic.mp #333, shows questionmarks when doing ls in ssh (using > PuTTY set to UTF-8 in translation). The funny thing is that > autocomplete > using tab shows the expected letters. pwd shows expected letters and > even > ls | cat shows correct letters. > > Is this a known problem? Is there a solution to make ls print correct > UTF-8? Yep, use colorls instead of ls. Works for german umlauts. http://openports.se/sysutils/colorls
Re: ls cant print higher UTF-8 chars
> Use -current. I fixed ls(1) recently to correctly handle UTF-8. > On May 1, 2016, upgrade to OpenBSD 5.9 if you want to use -stable. > Do not forget to upgrade to OpenBSD 6.0 on November 1, 2016. > UTF-8 support is likely to improve further between 5.9 and 6.0. > > Yours, > Ingo Thanks for the work and the information.
Questions to the snapshot from January 9 2016 ?
Hello ! Yes, I know, there is a newer snapshot out already but I had no time to update it. Dmesg is below. Everything I tried, worked well but I have some questions / informations. I use a 2TB drive, where I use for /home a 1,7TB disklabel. If I run mount this disklabel is shown as FFS. What I readed, disklabels bigger then something like 1TB should be FFS2. I am just curious, is FFS2 also shown as FFS (I found no information about it) ? user@thinkpad-w541 ~ $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd2a 1005M 58.4M896M 6%/ /dev/sd2k 1.7T3.1G1.6T 0%/home /dev/sd2d 3.9G 12.0K3.7G 0%/tmp /dev/sd2f 2.0G729M1.2G38%/usr /dev/sd2g 1005M210M745M22%/usr/X11R6 /dev/sd2h 9.8G3.0G6.3G32%/usr/local /dev/sd2j 2.0G2.0K1.9G 0%/usr/obj /dev/sd2i 2.0G2.0K1.9G 0%/usr/src /dev/sd2e 66.2G 15.5M 62.8G 0%/var tmpfs 8.0G4.0K8.0G 0%/home/ports/wrkobjdir user@thinkpad-w541 ~ $ mount /dev/sd2a on / type ffs (local) /dev/sd2k on /home type ffs (local, nodev, nosuid) /dev/sd2d on /tmp type ffs (local, nodev, nosuid) /dev/sd2f on /usr type ffs (local, nodev) /dev/sd2g on /usr/X11R6 type ffs (local, nodev) /dev/sd2h on /usr/local type ffs (local, nodev) /dev/sd2j on /usr/obj type ffs (local, nodev, nosuid) /dev/sd2i on /usr/src type ffs (local, nodev, nosuid) /dev/sd2e on /var type ffs (local, nodev, nosuid) tmpfs on /home/ports/wrkobjdir type tmpfs (local) When I switch from X to ttyC0 the display brightness is set to a minimum (near as if the display is blanked). The message *error: [drm:pid0:intel_dp_set_idle_link_train] *ERROR* Timed out waiting for DP idle patterns* is shown and if I press fn F6 it is back at 100 %. This happened only at the first switch and also if I shutdown the machine (xterm, shutdown). The change of the display brightness doesn't happened with 5.8 -release. Is there a simple way to automatically re-run /etc/rc.local after a resume ? I run atactl there and, it looks as if it is not running after resuming the machine (checked the load / unload cycle counts with atactl after resuming) ? OT and only for the archive : iwm0 works not (dhcp ends always with no link ... sleeping) with a TP-Link M7350 (4G / LTE modem), also urndis0 produces error messages (posted before about it). I used as reference a Nexus 7 with Android 4 where this things doesn't happened. This is NOT a OpenBSD problem. Maybe I have a monday product - if not, save the 100 and invest it in other hardware. Thanks for answers. dmesg : OpenBSD 5.9-beta (GENERIC.MP) #1807: Sat Jan 9 13:46:21 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33939300352 (32367MB) avail mem = 32906575872 (31382MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (69 entries) bios0: vendor LENOVO version "GNET73WW (2.21 )" date 03/12/2015 bios0: LENOVO 20EFS00B00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI POAT ASF! BATB FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 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) i7-4810MQ CPU @ 2.80GHz, 2794.07 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT 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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 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,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 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-
Re: Questions to the snapshot from January 9 2016 ?
> On Wed, Jan 13, 2016 at 01:20:08PM +0100, Christoph R. Murauer wrote: >> OT and only for the archive : iwm0 works not (dhcp ends always with >> no >> link ... sleeping) with a TP-Link M7350 (4G / LTE modem) > > Not very off-topic since development for 11n support is on-going. > > Can you please check if it works as expected if you run one of > these commands? > > ifconfig iwm0 media autoselect mode 11a > > ifconfig iwm0 media autoselect mode 11g > > If either command fixes it, you're probably seeing an interoperability > problem in 11n mode with this particular AP. > Hello ! Thanks for your answer. Default output after reboot using /etc/hostname.iwm0 ifconfig iwm0 iwm0: flags=8843 mtu 1500 lladdr cc:3d:82:52:2b:5a priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid TP-LINK_M7350_6D1625 wpakey wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip more /etc/hostname.iwm0 nwid TP-LINK_M7350_6D1625 wpakey 21154320 dhcp No worry, factory defaults. Content is a copy of /etc/hostname.urtwn0. Booth lines have no effect with this AP. Output for urtwn0 using /etc/hostname.urtwn0 also since reboot. urtwn0: flags=8843 mtu 1500 lladdr c4:e9:84:06:6c:a7 priority: 4 groups: wlan egress media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active ieee80211: nwid TP-LINK_M7350_6D1625 chan 9 bssid 3c:46:d8:6d:16:25 20dBm wpakey wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip inet 192.168.0.104 netmask 0xff00 broadcast 192.168.0.255 ifconfig iwm0 scan works. If I switch back to b it works with the Nexus 7 (also not with a and g). ifconfig iwm0 media autoselect mode 11b dhclient iwm0 iwm0: no link ... got link DHCPREQUEST on iwm0 to 255.255.255.255 DHCPACK from 192.168.43.1 (02:1a:11:f4:84:91) bound to 192.168.43.89 -- renewal in 1800 seconds. ifconfig iwm0 iwm0: flags=8843 mtu 1500 lladdr cc:3d:82:52:2b:5a priority: 4 groups: wlan media: IEEE802.11 autoselect mode 11b (DS1 mode 11b) status: active ieee80211: nwid AP chan 6 bssid 02:1a:11:f4:84:91 100% wpakey wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip inet 192.168.43.89 netmask 0xff00 broadcast 192.168.43.255 Tried the TP-Link AP with b again with the same result. Maybe it helps.
Re: Questions to the snapshot from January 9 2016 ?
Please give me a day or so. My nearest CVS (Vienna) is not really
fast. The last time it refuses the connection during fetching.
> On Wed, Jan 13, 2016 at 02:18:47PM +0100, Christoph R. Murauer wrote:
>> > On Wed, Jan 13, 2016 at 01:20:08PM +0100, Christoph R. Murauer
>> wrote:
>> >> OT and only for the archive : iwm0 works not (dhcp ends always
>> with
>> >> no
>> >> link ... sleeping) with a TP-Link M7350 (4G / LTE modem)
>> >
>> > Not very off-topic since development for 11n support is on-going.
>> >
>> > Can you please check if it works as expected if you run one of
>> > these commands?
>> >
>> > ifconfig iwm0 media autoselect mode 11a
>> >
>> > ifconfig iwm0 media autoselect mode 11g
>> >
>> > If either command fixes it, you're probably seeing an
>> interoperability
>> > problem in 11n mode with this particular AP.
>> >
>>
>> Hello !
>>
>> Thanks for your answer.
>> Default output after reboot using /etc/hostname.iwm0
>>
>> ifconfig iwm0
>> iwm0: flags=8843 mtu 1500
>> lladdr cc:3d:82:52:2b:5a
>> priority: 4
>> groups: wlan
>> media: IEEE802.11 autoselect
>> status: no network
>> ieee80211: nwid TP-LINK_M7350_6D1625 wpakey
>> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp
>> wpagroupcipher tkip
>>
>> more /etc/hostname.iwm0
>> nwid TP-LINK_M7350_6D1625
>> wpakey 21154320
>> dhcp
>>
>> No worry, factory defaults. Content is a copy of
>> /etc/hostname.urtwn0.
>>
>> Booth lines have no effect with this AP.
>>
>> Output for urtwn0 using /etc/hostname.urtwn0 also since reboot.
>>
>> urtwn0: flags=8843 mtu 1500
>> lladdr c4:e9:84:06:6c:a7
>> priority: 4
>> groups: wlan egress
>> media: IEEE802.11 autoselect (OFDM54 mode 11g)
>> status: active
>> ieee80211: nwid TP-LINK_M7350_6D1625 chan 9 bssid
>> 3c:46:d8:6d:16:25 20dBm wpakey wpaprotos
>> wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
>> inet 192.168.0.104 netmask 0xff00 broadcast
>> 192.168.0.255
>>
>> ifconfig iwm0 scan works.
>>
>> If I switch back to b it works with the Nexus 7 (also not with a and
>> g).
>>
>> ifconfig iwm0 media autoselect mode 11b
>> dhclient iwm0
>> iwm0: no link ... got link
>> DHCPREQUEST on iwm0 to 255.255.255.255
>> DHCPACK from 192.168.43.1 (02:1a:11:f4:84:91)
>> bound to 192.168.43.89 -- renewal in 1800 seconds.
>>
>> ifconfig iwm0
>> iwm0: flags=8843 mtu 1500
>> lladdr cc:3d:82:52:2b:5a
>> priority: 4
>> groups: wlan
>> media: IEEE802.11 autoselect mode 11b (DS1 mode 11b)
>> status: active
>> ieee80211: nwid AP chan 6 bssid 02:1a:11:f4:84:91 100%
>> wpakey
>> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers
>> tkip,ccmp wpagroupcipher tkip
>> inet 192.168.43.89 netmask 0xff00 broadcast
>> 192.168.43.255
>>
>> Tried the TP-Link AP with b again with the same result.
>>
>> Maybe it helps.
>
> Please try this diff.
> I suspect this bug is causing all sorts of problems.
>
> Index: ieee80211.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211.c,v
> retrieving revision 1.57
> diff -u -p -r1.57 ieee80211.c
> --- ieee80211.c 12 Jan 2016 09:28:09 - 1.57
> +++ ieee80211.c 13 Jan 2016 14:19:26 -
> @@ -749,8 +749,10 @@ ieee80211_setmode(struct ieee80211com *i
> modeflags = chanflags[mode];
> for (i = 0; i <= IEEE80211_CHAN_MAX; i++) {
> c = &ic->ic_channels[i];
> - if (mode == IEEE80211_MODE_AUTO ||
> - (c->ic_flags & modeflags) == modeflags)
> + if (mode == IEEE80211_MODE_AUTO) {
> + if (c->ic_flags != 0)
> + break;
> + } else if ((c->ic_flags & modeflags) == modeflags)
> break;
> }
> if (i > IEEE80211_CHAN_MAX) {
> @@ -764,8 +766,10 @@ ieee80211_setmode(struct ieee80211com *i
> memset(ic->ic_chan_active, 0, sizeof(ic->ic_chan_active));
> for (i = 0; i <= IEEE80211_CHAN_MAX; i++) {
> c = &ic->ic_channels[i];
> - if (mode == IEEE80211_MODE_AUTO ||
> - (c->ic_flags & modeflags) == modeflags)
> + if (mode == IEEE80211_MODE_AUTO) {
> + if (c->ic_flags != 0)
> + setbit(ic->ic_chan_active, i);
> + } else if ((c->ic_flags & modeflags) == modeflags)
> setbit(ic->ic_chan_active, i);
> }
> /*
Re: Questions to the snapshot from January 9 2016 ?
> Please try this diff.
> I suspect this bug is causing all sorts of problems.
>
> Index: ieee80211.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211.c,v
> retrieving revision 1.57
> diff -u -p -r1.57 ieee80211.c
> --- ieee80211.c 12 Jan 2016 09:28:09 - 1.57
> +++ ieee80211.c 13 Jan 2016 14:19:26 -
> @@ -749,8 +749,10 @@ ieee80211_setmode(struct ieee80211com *i
> modeflags = chanflags[mode];
> for (i = 0; i <= IEEE80211_CHAN_MAX; i++) {
> c = &ic->ic_channels[i];
> - if (mode == IEEE80211_MODE_AUTO ||
> - (c->ic_flags & modeflags) == modeflags)
> + if (mode == IEEE80211_MODE_AUTO) {
> + if (c->ic_flags != 0)
> + break;
> + } else if ((c->ic_flags & modeflags) == modeflags)
> break;
> }
> if (i > IEEE80211_CHAN_MAX) {
> @@ -764,8 +766,10 @@ ieee80211_setmode(struct ieee80211com *i
> memset(ic->ic_chan_active, 0, sizeof(ic->ic_chan_active));
> for (i = 0; i <= IEEE80211_CHAN_MAX; i++) {
> c = &ic->ic_channels[i];
> - if (mode == IEEE80211_MODE_AUTO ||
> - (c->ic_flags & modeflags) == modeflags)
> + if (mode == IEEE80211_MODE_AUTO) {
> + if (c->ic_flags != 0)
> + setbit(ic->ic_chan_active, i);
> + } else if ((c->ic_flags & modeflags) == modeflags)
> setbit(ic->ic_chan_active, i);
> }
> /*
>
Hello !
I tried the patch with the snapshot from yesterday but the result was
the same - no link ... sleeping in a, b and g mode.
Re: Questions to the snapshot from January 9 2016 ?
Thanks for your answer. > See the apmd(8) manual about /etc/apm/resume. I will have a look at it, thanks. > Use a different one. anoncvs.fr.openbsd.org and > anoncvs.spacehopper.org > update fairly fast. I used your mirror which was really fast (the initial checkout for src, ports and xenocara needs less then 15 minuts).
Re: Questions to the snapshot from January 9 2016 ?
> Can you please capture a beacon from this AP for me? > That is, one line from the output of: > > tcpdump -n -i iwm0 -y IEEE802_11_RADIO -s 1500 -vvv subtype beacon > > where the SSID of the beacon matches your AP, and while the iwm0 > interface is associated in 11b mode or while it is scanning. > > Thanks. > Yep, needs a littlebit to find the device. The ssid is correct and checked based on the MAC adress of the device. # ifconfig iwm0 scan iwm0: flags=8943 mtu 1500 lladdr cc:3d:82:52:2b:5a priority: 4 groups: wlan media: IEEE802.11 autoselect mode 11b status: no network ieee80211: nwid TP-LINK_M7350_6D1625 wpakey 0x15e08e2fd1fb0c86efe13dd3878a80395bb91315a49ff70fb9cdfbab7d4d5f14 wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip nwid 0x chan 6 bssid 3c:46:d8:6d:16:25 100% 54M privacy,short_preamble,short_slottime,wpa2 nwid AND SO ON ... The beacon : 17:03:22.158084 802.11 flags=0<>: beacon, timestamp 4390707584, interval 100, caps=2061, ssid 0x, rates 1M 2M 5M 6M 9M 11M 12M 18M, ds (chan 6), tim 0x0102, erp 0x00, xrates 24M 36M 48M 54M, htcaps=<20/40MHz,SGI@20MHz,SGI@40MHz,A-MSDU 3839,DSSS/CCK@40MHz,A-MPDU max 8191,RxMCS 0x>, htop=<40MHz chan 6:5,protect non-HT,basic MCS set 0x>, vendor 0x0050f2010150f2020250f2040050f2020150f202, rsn 0x010fac02020fac04000fac02010fac020c00, vendor 0x0050f202010183a427a442435e0062322f00, 74:14 0x14000a002c01c800140005001900, 127:1 0x01, vendor 0x0050f204104a0001101044000102, 17:03:22.352092 802.11 flags=0<>: beacon, timestamp 1802032436154, interval 100, caps=2021, ssid (PBS-445EF9), rates 1M 2M 5M 11M 18M 24M 36M 54M, ds (chan 11), tim 0x0102, country 'EU ', erp 0x00, 47:1 0x00, xrates 6M 9M 12M 48M, htcaps=<20MHz,greenfield,SGI@20MHz,SGI@40MHz,A-MSDU 7935,DSSS/CCK@40MHz,A-MPDU max 65535,A-MPDU spacing 8.00us,RxMCS 0x>, htop=<20MHz chan 11,STA chanw 20MHz,RIFS,non-greenfield STA,basic MCS set 0x>, vendor 0x0010180201f02c, vendor 0x0050f2010150f2020250f2040050f2020150f2020c00, vendor 0x0050f202010103a427a442435e0062322f00,
dpb question for understanding.
Hello ! I used today dpb and readed also the man page. But I have a question as none developer / coder. I followed the FAQ and put 3 ports in the localfile. Everything builds fine. dpb is runned as root on a local drive used a tmpfs to build. All 3 ports are builded but only the first was installed (tried it re-running make install in the other port directories to verify everything was builded). I also have no lock files in /usr/ports/logs/amd64/locks/. My question (maybe a stupid one) is now, how find I out, why dpb builds everything but installes only the first port (could someone point me please to the right logfile and for what I should watch there) ? Thanks for answers. P.S. : I let the dmesg this time.
Re: dpb question for understanding.
Thanks for your answer. > See the -I option in the dpb(1) man page. That installs a path or > list of paths to install. I tried again -I instead of -P and now, it worked as it should. At my first try, I also used the -I switch but miss interpreted the use of it. My fault sorry.
Re: Correct contact address?
See http://www.openbsd.org/ftp.html and, use mirrors-disc...@openbsd.org for contacts. But for CVS mirrors, there is a different adress. See http://www.openbsd.org/mail.html about misc@ > Dear OpenBSD admins, > > it seems www@ is nonexisting, and misc@ is a list I need to subscribe > to > (or at least acknowledge my own mail). This is not exactly what is > what > I have in mind for a contact address that might also be used in case > of > mirror emergencies. Do you have a more suitable contact address? > > Best regards, > Carsten > -- > Dr. Carsten Otto > http://verify.rwth-aachen.de/otto/ > > [demime 1.01d removed an attachment of type application/pgp-signature > which had a name of signature.asc]
Re: if I were to make a pkg-add diff
> here you go! Enjoy! > > -Luke > > On Tue, Jan 19, 2016 at 2:57 AM, Erling Westenvik < > erling.westen...@gmail.com> wrote: [ ... ] > > [demime 1.01d removed an attachment of type text/x-csrc which had a > name of pkg_ping.c] Luke RTFM. http://www.openbsd.org/mail.html *The only mailing list that allows attachments is the ports list, they will be removed from messages on the other mailing lists.*
bsd.rd from -current Jan 18 fails to boot on MacBook4.1.
Hello ! Maybe someone is interested. I tried today to boot the Snapshot #1850 from January 18 on a MacBook 4.1 and it fails duribg boot with the following message. The install59.fs file works without problems and is also used before to setup a ThinkPad and a Shuttle XS35V4. Message : probing: pc0 mem[572K 64K 3031M 72K 172K 368K 4M 52K 28K 716K 292K 40K 16K 88K 4M 28K 20K 236K 5M 3M 144K 40K 3072M] disk: hd0 hd1 hd2 >> OpenBSD/amd64 EFIBOOT 3.29 boot> cannot open hd0a:/etc/random.seed: No such file or directory booting hd0a:/5.9/amd64/bsd.rd: 3293880+1404264+2409472+0+569344 [72+368520+240610]=0x7e8e38 entry point at 0xf000160[7205c766, 3404, 24448b12, a680a304] Then the machine reboots. dmesg from 5.8 which is currently running on the machine : OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 6389174272 (6093MB) avail mem = 6191644672 (5904MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (42 entries) bios0: vendor Apple Inc. version "MB41.88Z.00C1.B00.0802091535" date 02/09/08 bios0: Apple Inc. MacBook4,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices ADP1(S3) LID0(S3) ARPT(S3) GIGE(S3) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) UHC5(S3) EHC1(S3) EHC2(S3) EC__(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)2 Duo CPU T8300 @ 2.40GHz, 1197.19 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-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 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz, 1197.00 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu1: 3MB 64b/line 8-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 0xf000, bus 0-255 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP05) acpiprt2 at acpi0: bus 3 (RP06) acpiprt3 at acpi0: bus 4 (PCIB) acpicpu0 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpibat0 at acpi0: BAT0 not present acpivideo0 at acpi0: GFX0 cpu0: Enhanced SpeedStep 1197 MHz: speeds: 2400, 2200, 2000, 1800, 1600, 1400, 1200, 800 MHz memory map conflict 0xf00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xfffa/0x3 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x03 vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xc000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1280x800 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM965 Video" rev 0x03 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 16 ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x03: apic 1 int 21 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 82801H HD Audio" rev 0x03: msi azalia0: codecs: Realtek ALC885 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x03: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev 0x03: msi pci2 at ppb1 bus 2 "Broadcom BCM4321" rev 0x03 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 5 "Intel 82801H PCIE" rev 0x03: msi pci3 at ppb2 bus 3 mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2 EC Ultra rev. B0 (0x3): apic 1 int 17 msk0 at mskc0 port A: address 00:1e:c2:1d:d9:4d eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1 uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 16 uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 18 uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x03: ap
Re: VAX - are we dropping support in 5.9?
Hello ! I have no VAX but I am interested in the discussion about supporting old platforms. Quotes taked from Christian Weisgerber : > It's the comparatively popular platforms like powerpc and sparc64 > that are in dire need of help if OpenBSD is not to turn into an > amd64-only platform. > Going by previous experience, it's conceivable that somebody else > will step in to build the release and possibly a few packages. I don't know, which platformes are planned to be supported in the future but are there enough people out there, to invest time / money providing missing builds for SUN / SGI ? The question is meaned serious and not against this platforms. Let's say someone will build releases and packages, would the project accept this builds or is there the need to host them self (security / trust and so on) ?
FYI Intel Bay Trail dmesg -current Jan 18.
Hello ! Maybe someone is interested, a dmesg of a Shuttle XS35V4 (Intel Bay Trail TXE) using the Snapshot from January 18. The machine is fanless and provides UEFI only. The only thing which doesn't work is the by default integrated Wi-Fi card. Weird behaviours : I used the machine before using a HDMI cable and a xorg.conf which is not needed since some Snapshots. If you boot the machine, after some time it switches to VGA only instead of HDMI. Yesterday I installed the Snapshot again on a SSD - using only a VGA cable - and saw a kind of flickering as I booted the installer (installation was not done). If are booth cables VGA and HDMI are connected I don't saw this behaviour (I don't / can't try the display port). Maybe this doesn't happen in a newer Snapshot. Thanks for the good work. $ xrandr -q Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 VIRTUAL1 disconnected (normal left inverted right x axis y axis) HDMI and VGA is connected. bsd.sp : OpenBSD 5.9-beta (GENERIC.MP) #1850: Mon Jan 18 13:38:16 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error f real mem = 7970746368 (7601MB) avail mem = 7724994560 (7367MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) bios0: vendor American Megatrends Inc. version "1.11 x64" date 08/26/2014 bios0: Shuttle Inc. XS35V4 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG LPIT SLIC HPET SSDT SSDT SSDT UEFI acpi0: wakeup devices UAR5(S4) UAR8(S4) XHC1(S4) EHC1(S4) PXSX(S4) PXSX(S4) RLAN(S5) PXSX(S4) PXSX(S4) PWRB(S0) 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) Celeron(R) CPU J1900 @ 1.99GHz, 2000.37 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 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 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins acpimadt0: bogus nmi for apid 0 acpimadt0: bogus nmi for apid 2 acpimadt0: bogus nmi for apid 4 acpimadt0: bogus nmi for apid 6 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus 3 (RP03) acpiprt4 at acpi0: bus 4 (RP04) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C
Re: VAX - are we dropping support in 5.9?
> Christoph R. Murauer wrote: >> Let's say someone will build releases and packages, would the >> project >> accept this builds or is there the need to host them self (security >> / >> trust and so on) ? > > It takes more than just someone willing to type a few commands. You > have investigate and understand the failures. > > If the first reply to this thread was not "hey, I noticed snapshots > were > missing too so I started building them on my own, here's a link" then > I'm not > very optimistic. Not to be all Debbie Downer, but most problems in > OpenBSD > aren't fixed by people who need to be told the nature of the problem. > I totally agree. My question was more meaned like, is it worth in theese days to invest time and money to learn this things on a old platform like a Sun or SGI or, is it better to buy cheap amd64 hardware and, let it as it is. Also not meaned as decission what a person should do (code or not code) - more like, it was good but now it is dead and we go on or as long, as there are XYZ people out there we keep it alive. I know, noone could answer that for me ... it was a try, maybe in the hope, that others had similar minds.
Re: VAX - are we dropping support in 5.9?
> Or looking a bit into the future, I'll mention the elephant in the > room and say that architectures without clang support are doomed. Sounds realistic. > Would you like the project to accept builds from a random stranger? As I am not part of the project / no developer, my personal opinion about it is not important.
Re: Hi There! I am trying to install OpenBSD
Hello ! > This is my first message on the list so, first of all, hello > everybody! :) > > I've recently bought a dedicated PC, planning to use it as a firewall > by > installing OpenBSD on it. > > I have downloaded the install80.iso, checked the sha sum, and read the > installation guide. > I have burned the iso to a cd-rom and checked the sha sum again on the > machine I am trying to install. > I have tested the hardware and the general functionality of the > machine > with common open source tools (memtest and succesfully installing a > linux distro). > > When I boot the i386 OpenBSD 5.8 CD, it loads the kernel and writes a > lot of blue stuff, then stops at: > > wdc_atapi_intr: warning: reading only 0 of 18 bytes > > For those who have a browser, here is a full screenshoot: > http://imagebin.ca/v/2VR8MRMArdG7 > > I've tried to look for this error using a search engine, but I > surprisingly got zero results. I have no solution for you but some search results http://daemonforums.org/showthread.php?t=4752 http://openbsd-archive.7691.n7.nabble.com/Atapiscsi-problem-on-VIA-NAB7100-VIA-VT6420-td184350.html http://openbsd-archive.7691.n7.nabble.com/Second-SATA-channel-in-Via-VT3237S-td191011.html Reduce your search to something like *wdc_atapi_intr: warning: reading only* and, you will get more results. I haven't looked at the pic but as you wrote, that you installed linux, look at the reported chipset / or the documentation of the hardware. > > Any help will be appreciated. > > Thank you! > > Gabriele Tozzi
No keymap selection on macppc -current from Feb 8.
Hello ! Sorry if the format of the message is not, as it should be. I tried today the latest snapshot on a PowerMac G5. The installation worked without problems but at the installer the first question about to choose the keymap is missing. It is possible to set the keymap after login using kbd de or wsconsctl keyboard.encoding=de but the setting is gone after a reboot. Thanks for ideas. dmesg : $ (dmesg; sysctl hw.sensors) [ using 562036 bytes of bsd ELF symbol table ] console out [NVDA,Display-B] console in [keyboard], using USB using parent NVDA,Parent:: memaddr 9800, size 800 : consaddr 98004000 : ioaddr 9100, size 100: width 1360 linebytes 1536 height 768 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2016 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.9 (GENERIC.MP) #1003: Mon Feb 8 20:06:13 MST 2016 dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC.MP real mem = 3221225472 (3072MB) avail mem = 2022199296 (1928MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root: model PowerMac7,3 cpu0 at mainbus0: 970 (Revision 0x202): 1800 MHz cpu1 at mainbus0: 970 (Revision 0x202): 1800 MHz mem0 at mainbus0 spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 spdmem1 at mem0: 1GB DDR SDRAM non-parity PC3200CL3.0 spdmem2 at mem0: 512MB DDR SDRAM non-parity PC3200CL3.0 spdmem3 at mem0: 512MB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: u3 rev 0xb3 kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 lmtemp0 at iic0 addr 0x4a: ds1775 maxtmp0 at iic0 addr 0x4c: max6690 maxtmp1 at iic0 addr 0x4e: max6690 "cy28508" at iic0 addr 0x69 not configured "cy2213" at iic0 addr 0x65 not configured fcu0 at iic0 addr 0xaf "pca9556" at iic0 addr 0x18 not configured adc0 at iic0 addr 0x2c: ad7417 "24256" at iic0 addr 0x50 not configured "pca9556" at iic0 addr 0x19 not configured adc1 at iic0 addr 0x2d: ad7417 "24256" at iic0 addr 0x51 not configured "dart" at memc0 offset 0xf8033000 not configured "mpic" at memc0 offset 0xf804 not configured mpcpcibr0 at mainbus0 pci: u3-agp pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 "Apple U3 AGP" rev 0x00 appleagp0 at pchb0 agp0 at appleagp0: aperture at 0x0, size 0x1000 vgafb0 at pci0 dev 16 function 0 "NVIDIA GeForce FX 5200 Ultra" rev 0xa1 wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) ht0 at mainbus0: u3-ht, 6 devices pci1 at ht0 bus 0 hpb0 at pci1 dev 1 function 0 "Apple U3" rev 0x00: 85 sources pci2 at hpb0 bus 1 macobio0 at pci2 dev 7 function 0 "Apple K2 Macio" rev 0x60 openpic0 at macobio0 offset 0x4: version 0x4614 feature 770302 LE macgpio0 at macobio0 offset 0x50 "pmu-interrupt" at macgpio0 offset 0x9 not configured "programmer-switch" at macgpio0 offset 0x11 not configured "modem-reset" at macgpio0 offset 0x1d not configured "modem-power" at macgpio0 offset 0x1e not configured "fcu-interrupt" at macgpio0 offset 0x15 not configured "fcu-hw-reset" at macgpio0 offset 0x3a not configured "slewing-done" at macgpio0 offset 0x23 not configured "codec-input-data-mux" at macgpio0 offset 0xb not configured "line-input-detect" at macgpio0 offset 0xc not configured "codec-error-irq" at macgpio0 offset 0xd not configured "dig-hw-reset" at macgpio0 offset 0x14 not configured "line-output-detect" at macgpio0 offset 0x16 not configured "headphone-detect" at macgpio0 offset 0x17 not configured "codec-irq" at macgpio0 offset 0x18 not configured "headphone-mute" at macgpio0 offset 0x1f not configured "amp-mute" at macgpio0 offset 0x20 not configured "hw-reset" at macgpio0 offset 0x24 not configured "line-output-mute" at macgpio0 offset 0x25 not configured "codec-clock-mux" at macgpio0 offset 0x26 not configured "escc-legacy" at macobio0 offset 0x12000 not configured zs0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zs0 channel 0 zstty1 at zs0 channel 1 kiic1 at macobio0 offset 0x18000 iic1 at kiic1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 "timer" at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 apm0 at adb0: battery flags 0x9, 0% charged piic0 at adb0 iic2 at piic0 "fans" at macobio0 offset 0x4c not configured ohci0 at pci2 dev 8 function 0 "Apple K2 USB" rev 0x00: irq 27, version 1.0, legacy support ohci1 at pci2 dev 9 function 0 "Apple K2 USB" rev 0x00: irq 28, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 "Apple OHCI root hub" rev 1.00/1.00 addr 1 usb1 at ohci1: USB revision 1.0 uhub1 at usb1 "Apple OHCI root hub" rev 1.00/1.00 addr 1 ppb0 at pci1 dev 2 function 0 "Apple U3" rev 0x00 pci3 at ppb0 bus 5 ohci2 at pci3 dev 11 function 0 "NEC USB" rev 0x43: irq 63, version 1.0 ohci3 at pci3 dev 11 function 1 "NEC USB" rev 0x43: irq 63, version 1.0 ehci0 at pci3 dev 11 function 2 "NEC USB" rev 0x04: irq 63 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 "
Re: No keymap selection on macppc -current from Feb 8.
> On 09/02/16(Tue) 23:28, Christoph R. Murauer wrote: >> Hello ! >> >> Sorry if the format of the message is not, as it should be. >> >> I tried today the latest snapshot on a PowerMac G5. The installation >> worked without problems but at the installer the first question >> about to choose the keymap is missing. >> >> It is possible to set the keymap after login using kbd de or >> wsconsctl keyboard.encoding=de but the setting is gone after a >> reboot. >> >> Thanks for ideas. > > You can simply do > > # echo de > /etc/kbdtype > > This is documented in kbd(8) feel free to check it ;) > > Martin > Thanks for your answer. Yes, that's a way. I thought, I report it to get the keymap question back to the installer because it is more easy to type special characters if the keyboard and the keymap is the same.
Current #189 Nov 1 panic ONLY at first boot.
Hello ! I think I miss some informations for a bug report so, I post here. I did a upgrade from a snapshot (which was a clean install 2 or 3 days ago) and also a clean install of this snapshot (booth with install62.fs instead of bsd.rd). The result was in booth cases a panic and I ended in ddb. But this happened only at the first boot - not on following boots. I have at boot time no internet connection as the script tries to download the firmware. The bug happened also only with that snapshot and with none before (there I had also no internet connection). ddb trace and ddb boot reboot messages (with ps) as pictures are here http://www.nawi.is/images/trace.jpg http://www.nawi.is/images/boot.jpg Thanks for answers.
Re: Current #189 Nov 1 panic ONLY at first boot.
Thanks for your fast answer. I wait for the next snapshot. > Hello, > > On 01/11/17(Wed) 13:38, Christoph R. Murauer wrote: >> I think I miss some informations for a bug report so, I post here. >> >> I did a upgrade from a snapshot (which was a clean install 2 or 3 >> days >> ago) and also a clean install of this snapshot (booth with >> install62.fs instead of bsd.rd). The result was in booth cases a >> panic >> and I ended in ddb. But this happened only at the first boot - not >> on >> following boots. >> >> I have at boot time no internet connection as the script tries to >> download the firmware. The bug happened also only with that snapshot >> and with none before (there I had also no internet connection). >> >> ddb trace and ddb boot reboot messages (with ps) as pictures are >> here >> >> http://www.nawi.is/images/trace.jpg >> http://www.nawi.is/images/boot.jpg > > This has been fixed already, please updated from source or wait for > the > next snapshot. > >
Re: 3g modem
See for example https://man.openbsd.org/umb or, https://man.openbsd.org/umsm.4 > My isp leaves a lot to be desired. I'm into possible backup plans for > when > the connection is unbearable. Are there any 3g usb dongles or mini pci > devices which work on openbsd? > > Thanks, > > Edgar > >
Current #197 Nov 5 umb0 ucom0 umodem0 detached.
Hello ! Today I experienced, that umb0 ucom0 umodem0 detached at the same time. I can't reproduce it but saw it 1 time with snapshot #194 but before not. If I lost the connection in the past, I saw a timeout message at the xconsole and could simple re-connect. At this time umb0(4) is not longer shown with ifconfig(8) and I had to reboot to fix it. /var/log/messages show the following : Nov 6 23:55:45 thinkpad-w541 /bsd: umb0 detached Nov 6 23:55:45 thinkpad-w541 /bsd: ucom0 detached Nov 6 23:55:45 thinkpad-w541 /bsd: umodem0 detached Nov 6 23:56:02 thinkpad-w541 /bsd: uhub0: port 10, set config 0 at addr 4 failed Nov 6 23:56:02 thinkpad-w541 /bsd: uhub0: device problem, disabling port 10 Which other informations are need to help to debug ? Thanks for your answers. OpenBSD 6.2-current (GENERIC.MP) #197: Sun Nov 5 12:48:36 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33938599936 (32366MB) avail mem = 32903180288 (31378MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (69 entries) bios0: vendor LENOVO version "GNET81WW (2.29 )" date 11/24/2016 bios0: LENOVO 20EFS00B00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI POAT ASF! BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 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) i7-4810MQ CPU @ 2.80GHz, 2794.09 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache acpihpet0: recalibrated TSC frequency 2793557357 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 MHz cpu4: 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,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 2, package 0 cpu5 at mainbus0: apid 5 (application processor) cpu5: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.53 MHz cpu5: 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,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PE
Re: Error : page Ports - Working with Ports
Quote from the FAQ. Summary: Some ports are split into several packages. make install will only install the main subpackage. To list the different packages built by a port, use: $ make show=PKGNAMES make install will only install the main subpackage. To install them all, use: $ make install-all Yes, normal. The first is labeled as summery. Later make install and make install-all is meaned. IMHO (it is not meaned bad) save yourself time and use diffs. Before, work with ports, that helps to understand the context. > > > Le 11/07/17 à 12:34, Rodrigo Mosconi a écrit : > (...) >>> " >>> By twice: "make install will only install the main subpackage". >>> Normal? >>> >> >> [make install] is a command that is writen in the shell. realize >> that is >> in mono-spaced font, so it is something from terminal >> >> > > I'm sorry, but you didn't understand me. > I like to point out that it is written twice, as an unfortunate > repetition. Normal? > > >
Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem
If I understood your question correct ... > Running: OpenBSD6.2-release > > Goal: To run a secure and functional web server. > (the server is currently up and running and used by > the public at large) If you apply the patches from the errata page using syspatch(8) (if you are on i386 / amd64) then you have a up to date and secure -stabe installation. > Previously: Only installing needed packages as binaries via pkg_add. > > Now: The thought is that the third-party packages being used > by the server should be kept up to date. If there are security related patches or things needed to be fixed, that the package works as it should, you can simple run pkg_add -iu > databases/mariadb,-main# 10.0.32v1 -> 10.0.33v1 > databases/mariadb,-server # 10.0.32v1 -> 10.0.33v1 > ... The question is, do you need the things which are provided from this new versions - for security see above. > complain when running 'make update' (in this case mariadb). e.g.: > Fatal: /usr/ports/pobj must be on a wxallowed filesystem\ > (in lang/python/2.7) You can add wxallowed to a already mounted filesystem using mount(8). > Is it not worth it to update ports in this way; meaning, is it better > to simply wait for OpenBSD6.3 and stick with binary packages only > (as recommended on the openbsd.org site)? That depends on your requirements. See above. > Also, is there an easy/sane way to remove packages that were only > required for building once the ports have been updated? A port is a package. See make clean and so on for builded ports and pkg_delete -a for packages. IMHO Who say, that something unneeded is installed ? It also has no effect to the system if build deps. are kept in the ports tree.
Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem
> Thanks for your replay Christoph.
>
> Please correct me if I'm wrong, but as I understand things, this only
> works if one is following OpenBSD-current. I am running -release.
> This is an in-use production server; I don't feel wise running
> -current.
If you install for example OpenBSD 6.2 you have a -release version. On
the errata page https://www.openbsd.org/errata62.html you find the
available patches for the -release base system. If you apply this
patches with syspatch(8) you have a -stable system. -current (also
called snapshots is something different).
>> You can add wxallowed to a already mounted filesystem using
>> mount(8).
>
> In theory, I don't like this; I would rather keep preventing
> everything
> not mapped from /use/local from being able to have both writable and
> executeable pages, even if it's only temporary.
That was only meaned as information. I have enough RAM and use it to
build things. There are many ways todo things.
> ...
> Some software builds and integrates from original sources more easilym
> that is, the usual:
> ./configure {reasonable options} -> make -> make install
> procedure goes off withotu a hitch, or at least without too many
> edits.
IMHO sure, you can build all things you need manually. The point is,
ports (from what you talked) have maintainers. If you use a
./configure switch, it means not, that the maintainer also will go
this way for port updates or, provide a flavour for the port using
this switch. Security things or broken things from a port should be
fixed upstream - if not and, if you like to see updated ports, work on
it.
>
> I understand that the ports system first builds and packages a port,
> and then installs it.
>
> I could be doing something wrong, but it seems that some ports install
> dependencies to the system (pkg_add-style) that are required to
> *build*
> the package from source, but that aren't required to *run* the package
> (e.g. cmake).
>
> So, I definitely don't mind leaving the built packages in the ports
> tree, but I *do* mind leaving them installed on the system.
>
See my pkg_add -a mention and, the answer from espie@
Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem
Sorry, typo. Meaned pkg_delete -a
Re: Keeping up to date with ports and putting ports/pobj on wxallowed filesystem
>> >> If there are security related patches or things needed to be fixed, >> that the package works as it should, you can simple run pkg_add -iu > > You can do this *if* you have a source of updated packages, e.g. via > mtier's openup, or packages that you've built yourself. Thanks for clarification, my fault. I thought, I readed somewhere in the past, that there is also a new version of the related packages. > >>> databases/mariadb,-main# 10.0.32v1 -> 10.0.33v1 >>> databases/mariadb,-server # 10.0.32v1 -> 10.0.33v1 >>> ... >> >> The question is, do you need the things which are provided from this >> new versions - for security see above. > > Those are security updates. -stable doesn't get "normal" version > updates. In this case yes. The OP wrote in the first post "Now: The thought is that the third-party packages being used by the server should be kept up to date.". I interpreted it like, if there is a new version, if it is not security relevant and, if I don't need the functions which are provided in this update - why update the package. Then the question should be something like, latest stable packages or, latest experimental packages of third-party packages.
Re: Current #197 Nov 5 umb0 ucom0 umodem0 detached.
Thanks for your answer. Sorry for the delay. In /cc to mpi@. > The first thing I see when looking at your report, is that your USB > devices were plugged in via USB3 (XHCI). It is a m.2 card in a ThinkPad. Yes, as it looks, they use USB3 internal. > Please recompile your kernel with XHCI_DEBUG, and share the debug > output here (and with mpi@) when you have it, when the error happened > next time. Ok? Build is done with the snapshot #220 from Nov 17 and the CVS from yesterday Nov 18 evening. Off topic : for my understanding, I followed the FAQ for buiding a custom kernel and used GENERIC.MP instead of GENERIC because it is a multiprocessor machine. What is the difference of bsd and bsd.gdb what is shown at the end of the build ? Output of /var/log/messages Nov 18 23:32:47 thinkpad-w541 pkg_add: Added git-2.15.0 Nov 19 00:00:01 thinkpad-w541 syslogd[73165]: restart Nov 19 05:11:27 thinkpad-w541 xlock: xlock: unable to open display . Nov 19 05:11:27 thinkpad-w541 xlock: Stop: root, wheel, unknown display, 0m 0s Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: port=10 change=0x00 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci_abort_xfer: xfer=0xff087b6491e0 status=IN_PROGRESS err=CANCELLED actlen=0 len=31744 idx=103 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_stop_ep dev 3 dci 5 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci_event_xfer: stopped xfer=0xff087b6491e0 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_tr_deq_async dev 3 dci 5 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 3 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 3 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci_abort_xfer: xfer=0xff087b6490f0 status=IN_PROGRESS err=CANCELLED actlen=0 len=24 idx=13 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_stop_ep dev 3 dci 3 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci_event_xfer: stopped xfer=0xff087b6490f0 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_tr_deq_async dev 3 dci 3 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 3 Nov 19 13:51:44 thinkpad-w541 /bsd: umb0 detached Nov 19 13:51:44 thinkpad-w541 /bsd: ucom0 detached Nov 19 13:51:44 thinkpad-w541 /bsd: umodem0 detached Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 3 Nov 19 13:51:44 thinkpad-w541 /bsd: xhci0: xhci_cmd_slot_control Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: port=10 change=0x00 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: port=10 change=0x00 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: xhci_cmd_slot_control Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: dev 7, input=0xff00022cc000 slot=0xff00022cc020 ep0=0xff00022cc040 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: dev 7, setting DCBAA to 0x022cd000 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci_pipe_init: pipe=0x80fec000 addr=0 depth=1 port=10 speed=3 dev 7 dci 1 (epAddr=0x0) Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_address BSR=1 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_address BSR=0 Nov 19 13:51:50 thinkpad-w541 /bsd: xhci0: dev 7 addr 7 Nov 19 13:51:55 thinkpad-w541 /bsd: xhci_abort_xfer: xfer=0xff087b6490f0 status=IN_PROGRESS err=TIMEOUT actlen=0 len=2 idx=38 Nov 19 13:51:55 thinkpad-w541 /bsd: xhci0: xhci_cmd_stop_ep dev 7 dci 1 Nov 19 13:51:55 thinkpad-w541 /bsd: xhci_event_xfer: stopped xfer=0xff087b6490f0 Nov 19 13:51:55 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_tr_deq_async dev 7 dci 1 Nov 19 13:52:00 thinkpad-w541 /bsd: xhci_abort_xfer: xfer=0xff087b6490f0 status=IN_PROGRESS err=TIMEOUT actlen=0 len=0 idx=40 Nov 19 13:52:00 thinkpad-w541 /bsd: xhci0: xhci_cmd_stop_ep dev 7 dci 1 Nov 19 13:52:00 thinkpad-w541 /bsd: xhci_event_xfer: stopped xfer=0xff087b6490f0 Nov 19 13:52:00 thinkpad-w541 /bsd: xhci0: xhci_cmd_set_tr_deq_async dev 7 dci 1 Nov 19 13:52:00 thinkpad-w541 /bsd: uhub0: port 10, set config 0 at addr 4 failed Nov 19 13:52:00 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 7 Nov 19 13:52:00 thinkpad-w541 /bsd: xhci0: xhci_cmd_slot_control Nov 19 13:52:00 thinkpad-w541 /bsd: uhub0: device problem, disabling port 10 Nov 19 18:00:01 thinkpad-w541 syslogd[73165]: restart Nov 19 21:00:02 thinkpad-w541 syslogd[73165]: restart Nov 19 22:24:32 thinkpad-w541 /bsd: xhci0: port=11 change=0x00 Nov 19 22:24:32 thinkpad-w541 /bsd: ugen2 detached Nov 19 22:24:32 thinkpad-w541 /bsd: xhci0: xhci_cmd_configure_ep dev 4 Nov 19 22:24:32 thinkpad-w541 /bsd: xhci0: xhci_cmd_slot_control Nov 19 22:24:32 thinkpad-w541 /bsd: xhci0: port=11 change=0x00 Nov 19 22:24:32 thinkpad-w541 /bsd: xhci0: port=11 change=0x00 Nov 19 22:24:33 thinkpad-w541 /bsd: xhci0: xhci_cmd_slot_control Nov 19 22:24:33 thinkpad-w541 /bsd: xhci0: dev 8, input=0xff00676d4000 slot=0xff00676d4020 ep0=0xff00676d4040 Nov 19 22:24:33 thinkpad-w541 /bsd: xhci0: dev 8, setting DCBAA to 0x676d5000 Nov 19 22:24:33 thinkpad-w541 /bsd: xhci_pipe_init: pipe=0x80fec000 addr=0 depth=1 port=11 speed=2 dev 8 dci 1 (epAddr=0x0) Nov 19
Re: MacOS High Sierra. Anyone can login as "root" with empty password
Am 29. November 2017 08:36:27 MEZ schrieb Ilya Abimael : >Hello, > >https://news.ycombinator.com/item?id=15800676 > >The mentioned news is _NOT_ OpenBSD related. It just got something in >my mind to ask: You forgot a important detail. The root user is there in all Mac OS X, OS X and macOS versions. It is disabled by default and, it has no password by default. You set the root password if you activate the root account the first time. Which brings the next problem. The first by default created user on a Mac OS X (see above) machine is a administrator. Any administrator could activate the root account and, the most normal users did not create a user for daily jobs. The idea of Apple is, buy it, switch it on and use it. > > >The question: Would it be a good thing to MANDATORY disable any >passwordless login? IMHO a useless question in theese days. In Mac OS X (as you refer to it) you can use the profile manager or parential control to limit things if you really need passwordless accounts like a public kiosk system or for people with disabilities - but there you also have assistive technologies like VoiceOver and Braile support. > >OpenBSD would probably never have similar issue, but maybe it would be >a good mitigation? Search for the discussion about SSH login passwords / keys. > > >Thanks.
Re: New default setup for touchpads in X
Hello ! I tried the touchpad with -current #261 from Dec 8. But wsconsctl still reports mouse.type=synaptics. Should that be ? If it is as it should be, the touchpad worked as before (but I had not much time to play around with it). IMHO the touchpad on this machine is sometimes a kind of sluggish. Specially with the pinch to zoom (ctrl and 2 finger to scale). If all works as it should, I also could try it on a MacBook Pro the next days. thinkpad-w541# wsconsctl | grep 'mouse' wsconsctl: Use explicit arg to view keyboard.map. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1266,5676,1096,4758,0,45,68 mouse.tp.tapping=1 mouse.tp.scaling=0.160 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 I changed the tapping as you suggested and, I don't have a xorg.conf in /etc. Search with wildcard to get a result. thinkpad-w541# find / -name 'xorg.conf*' /usr/X11R6/man/man5/xorg.conf.5 /usr/X11R6/man/man5/xorg.conf.d.5 /usr/X11R6/share/X11/xorg.conf.d /usr/xenocara/xserver/hw/xfree86/man/xorg.conf.d.man /usr/xenocara/xserver/hw/xfree86/man/xorg.conf.man dmesg : OpenBSD 6.2-current (GENERIC.MP) #261: Fri Dec 8 11:22:29 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33938599936 (32366MB) avail mem = 32903114752 (31378MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7cd2d000 (69 entries) bios0: vendor LENOVO version "GNET81WW (2.29 )" date 11/24/2016 bios0: LENOVO 20EFS00B00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI POAT ASF! BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 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) i7-4810MQ CPU @ 2.80GHz, 2794.06 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache acpihpet0: recalibrated TSC frequency 2793530785 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz cpu4: 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,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 2, package 0 cpu5 at mainbus0: apid 5 (application processor) cpu5: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2793.54 MHz cpu5: FPU,VM
Re: New default setup for touchpads in X
Hello Ulf ! Thanks for your answer. > I assume that your touchpad is actually running with ws, and that no > xorg ".conf" file - in /etc or in /usr/X11R6/share/X11/xorg.conf.d/ - > overrides the default ;-) If that is the case, then "works-as-before" is a good result, Yes, I can confirm, that it is ws. Because I had synclient settings including tabbing in my .xsession file which had no effect after upgrading to the last snapshot. No, there is no xorg.conf (see search results below from my original email). I experienced no differences compared to the synaptics driver from before. > I had no intention to break user expectations. I know. > Maybe you want give it a try on your MacBook, which has MT support ;-) Yes, I wait for a new battery (I hope only the battery is died). Just give me some days. > I'm not sure what your comparison is based on. I remember that some > reviewers were unhappy with the touchpads of the w540 series, > especially > because of the button handling. Or do you refer to the fact that > there > is no support for "smooth" scrolling? (The classical scroll-method is > event-based, that is, wheel movements on a mouse - or scroll gestures > on a touchpad - are translated into a series of button events, which > is > coarse compared to coordinate-based scrolling.) It is not really a comparison, the experience is like, if I zoom in or out the zoom steps are bigger. Like if you zoom - lets say in 10% steps instead of something like 1 or 2% steps. Yes, I readed that about the touchpad experiences but after I bought it already ;-) I will try it with the MacBook as soon as possible and then report a comparison about that. Is the new ws driver also in the macppc port included ? I have no idea which hardware is in it but maybe I have the chance to try it out on a G4 PowerBook. Regards, Christoph >> thinkpad-w541# find / -name 'xorg.conf*' >> /usr/X11R6/man/man5/xorg.conf.5 >> /usr/X11R6/man/man5/xorg.conf.d.5 >> /usr/X11R6/share/X11/xorg.conf.d >> /usr/xenocara/xserver/hw/xfree86/man/xorg.conf.d.man >> /usr/xenocara/xserver/hw/xfree86/man/xorg.conf.man
Re: New default setup for touchpads in X
Hello Ulf ! > I'm afraid you are out of luck with a Powerbook. ... No problem. Just good to know. > BTW, xorg configuration files in >/usr/X11R6/share/X11/xorg.conf.d/ Yes, you are right, there was a /usr/X11R6/share/X11/xorg.conf.d/70-synaptics.conf (- instead of _). After removing the file and reboot the machine, the outupt of thinkpad-w541# wsconsctl | grep 'mouse' wsconsctl: Use explicit arg to view keyboard.map. mouse.type=synaptics mouse.rawmode=0 mouse.scale=1266,5676,1096,4758,0,45,68 mouse.tp.tapping=0 mouse.tp.scaling=0.160 mouse.tp.swapsides=0 mouse.tp.disable=0 mouse1.type=ps2 IMHO From my side I see now no need to compare ws to synaptics. Tabbing after switching it on using wsconsctl mouse.tp.tapping=1, pointer movement and 2 finger scroll (left, right, up, down, in a circle) works for me good (quick tested using Xmonad, XTerm and qutebrowser). I will compare it with a fresh install on a MacBook Pro as I sayed as soon as possible. Pinch to zoom, only tested in qutebrowser, zooms in and out in round 23% steps but I think, that depends on the touchpad (we will see). Maybe someone could test pinch to zoom in XFCE using the integrated magnifier from the composting (I also try to have a look at it as soon as possible).
Re: New default setup for touchpads in X
Hello Ulf ! As promised, the information from a MacBook Pro using -current #289 Dec 17. Scrolling up, down, left, right, in a circle works. Tapping works only in the center and in the corners of the touchpad. I can't try pinch to zoom as Apple uses another keyboard layout. For example from a German keyboard, on a PC keyboard the @ is available with AltGr q which is on a Apple keyboard alt l. So, it does not work or, the key is not remapped - I had no time to look whether there is already a Apple keyboard remapping out there. Regards, Christoph wsconsctl | grep 'mouse' wsconsctl: Use explicit arg to view keyboard.map. wsconsctl: Use explicit arg to view keyboard1.map. mouse.type=usb mouse.rawmode=1 mouse.scale=0,0,0,0,0,0,0 mouse1.type=elantech mouse1.rawmode=0 mouse1.scale=-4750,5280,-150,6730,0,0,0 mouse1.tp.tapping=1 mouse1.tp.scaling=0.075 mouse1.tp.swapsides=0 mouse1.tp.disable=0 mouse2.type=usb mouse2.rawmode=1 mouse2.scale=0,0,0,0,0,0,0 mouse1 is the touchpad, mouse2 is a external USB mouse (to copy and paste text). dmesg with sensors - asmc(4) - below : OpenBSD 6.2-current (RAMDISK_CD) #289: Sun Dec 17 00:02:34 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8509263872 (8115MB) avail mem = 8247615488 (7865MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe1010 (83 entries) bios0: vendor Apple Inc. version "MBP91.88Z.00D7.B00.1708080744" date 08/08/2017 bios0: Apple Inc. MacBookPro9,1 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT DMAR MCFG acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz, 2694.33 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,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins , remapped to apid 2 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 5 (PEG1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus 3 (RP02) acpiprt5 at acpi0: bus 4 (RP03) acpicpu at acpi0 not configured "APP0001" at acpi0 not configured "APP0003" at acpi0 not configured "ACPI0008" at acpi0 not configured "ACPI0001" at acpi0 not configured "ACPI0002" at acpi0 not configured "APP000B" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0C" at acpi0 not configured "APP0002" at acpi0 not configured "PNP0C0E" at acpi0 not configured memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xffe7/0x3 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 ppb0 at pci0 dev 1 function 0 "Intel Core 3G PCIE" rev 0x09: msi pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor "NVIDIA", unknown product 0x0fd5 rev 0xa1 vga1: aperture needed wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) vendor "NVIDIA", unknown product 0x0e1b (class multimedia subclass hdaudio, rev 0xa1) at pci1 dev 0 function 1 not configured ppb1 at pci0 dev 1 function 1 "Intel Core 3G PCIE" rev 0x09: msi pci2 at ppb1 bus 5 ppb2 at pci2 dev 0 function 0 "Intel 82524EF Thunderbolt" rev 0x00 pci3 at ppb2 bus 6 ppb3 at pci3 dev 0 function 0 "Intel 82524EF Thunderbolt" rev 0x00: msi pci4 at ppb3 bus 7 "Intel 82524EF Thunderbolt" rev 0x00 at pci4 dev 0 function 0 not configured ppb4 at pci3 dev 3 function 0 "Intel 82524EF Thunderbolt" rev 0x00: msi pci5 at ppb4 bus 8 ppb5 at pci3 dev 4 function 0 "Intel 82524EF Thunderbolt" rev 0x00: msi pci6 at ppb5 bus 9 ppb6 at pci3 dev 5 function 0 "Intel 82524EF Thunderbolt" rev 0x00: msi pci7 at ppb6 bus 58 ppb7 at pci3 dev 6 function 0 "Intel 82524EF Thunderbolt" rev 0x00: msi pci8 at ppb7 bus 107 xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured ppb8 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4:
Re: New default setup for touchpads in X
Hello Ulf ! > there seems to be a terminology problem here: Usually, > "pinch gesture" refers to an input with two touches moving > toward each other, or away from each other, and it doesn't > involve keyboard input. Our drivers don't support these > gestures. Many applications permit to zoom in and out by > holding the Ctrl key down and scrolling simultaneously. Is > this what you mean? It should work with any application > that implements it, for the driver, it's just scrolling. Yes, it is what I meaned. I know it from Mac OS X as gestures or 2 finger gestures (or some varaiants of it, depends where you read about it) for zoom in and out without holding a key. As I configured synaptics / synclient the first time I came across a posting where it was called pinch to zoom (Ctrl and move 2 fingers). See below for details. > As to tapping, what you describe sounds weird, but maybe it > isn't: During tests with a MacBookPro8,2 I observed that > tapping with much force may fail because the hardware reports > coordinates that oscillate in a range that is beyond the > distance limit for tapping (that is, if the distance between > the origin and the end point of a touch exceeds a certain > threshold, it isn't treated as tap). I increased that limit > then, but possibly it's still too low for that hardware. Not to force, it is like as if there are dead areas. See below for details. > Can you check whether tapping without force works better, and > also test it with the synaptics driver (which has a much higher > threshold)? I tried today a 6.2 -release for synaptics using fvwm(1) and qutebrowser. Tapping was set using synclients synclient TapButton1=1 (setting tapping using wsconsctl(8) had no effect). Tapping works in the whole area of the touchpad without problems. Zoom in and out using the Ctrl key and 2 fingers (only diagonal - see below) worked also. It was better then on the ThinkPad but makes also not really happy. Then I tried 6.2 -current from Dec 18 also with fvwm(1) and qutebrowser. Tapping was set using wsconsctl(8) - as described in a email before. Increasing the threshold makes tapping more easy but there are still dead areas on the touchpad. In the snapshot from Dec 17 tapping was only possible in the corners and the middle of the touchpad - the field between them was dead. With this snapshot the dead area is smaller but still there. Zoom in and out using Ctrl and 2 fingers had absolutly no effect which I can reproduce. 2 or 3 times I could accidently zoom 1 step but not more. My impression was, as if there is a zoom area which is outside (on the right side) of the touchpad (sorry, I have no better description). I was curious and installed xfce (no extras) as xfce's composting provides a internal magnifier using the alt (no typo) key and the mouse wheel to zoom in and out everywhere. Tested with a mouse works as it should. Tested with the touchpad and ws(4) works very smooth / perfect BUT using the alt key and move 2 fingers (only vertical not as normal diagonal) vertical to zoom in and out. Let me know, if you need more informations. Regards, Christoph
Re: bug tracking system for OpenBSD
>From the original question of the OP > ... and (very important) some reliable response time and ... > Currently I have the impression that you have to be very lucky to be recognized on b...@openbsd.org. This is highly frustrating and discouraging. OpenBSD is developed entirely by volunteers. IMHO And, developers do that in there spare time, they also have a family and a social life. Even there is a bug tracker, if the OP can't be patient the answer will always be like, shutup and hack yourself or, hire someone from the list of commercial service.
Mount AFP (Apple Filing Protocol) share on OpenBSD ?
Hello ! Is there a way to mount a AFP (AirPort Extreme with a external USB HD in a LAN) share from OpenBSD ? Or, is the only way to use NFS (or the netatalk package) and copy the files from a macOS machine to the AFP share ? Thanks for answers Christoph
Re: Kindly support this initiative for a public git repository of OpenBSD source code located at Germany!
Hello ! > I have requested notabug.org to provide 1GB space for openbsd src git > repo. > It would be good to demonstrate that that you also want this idea > implemented. See https://www.openbsd.org/anoncvs.html in detail Setting up an anoncvs mirror There you can read for a complete mirror ... Anoncvs mirrors currently require about 6GB of disk (and it will grow!), For my understanding, why should I get src from your git mirror if I need for ports www xenocara CVS ? Would it not be a better idea to run a CVS mirror (if one is needed) and provide also git if people really need it ? IMHO CVS works fine for me so, why demonstarte that git works ? Regards, Christoph
Re: Community-driven OpenBSD tutorials wiki?
Hello ! No need for flame or complain or something. What I can remember, there is a German wiki at http://wiki.bsdforen.de and posts at http://bsdnow.tv booth are not up to date. And, what you find using your prefered search engine. But OpenBSD only - extreme seldom. If it is useful for YOU and, YOU want it - do it. IMHO I would start it, provide maybe here a table of contents if you didn't start already something and, I would call for / handle that off list. Regards, Christoph > Hi all! > > Thought I'd create an OpenBSD wiki somewhere, where anyone (especially > non-developers like myself) could create and edit tutorials for stuff > non-developers like myself would find useful. I find that sometimes > existing tutorials become outdated, and was thinking that a wiki would > make > updates easier. > > Before I go and create anything - are there already a place similar to > what > I'm describing, where I could get myself involved? (I'm too junior to > start > suggesting changes and updates to the docs on OpenBSD.org, and I'm not > sure > they should be used for what I want to achieve.) > > I know this comes out as yet another "let's start another project no > one is > asking for", but please be gentle with flaming me - I honestly want to > contribute to the community to the extent of my abilities. > > Cheers, > Andreas >
Re: 4G modems for OpenBSD?
Hello ! > Could anyone suggest a USB 4G cell modem ... > I do need a direct USB connection for the purposes of sending SMS > messages directly from the system, ... I don't know, if it is what you are looking for but have a look at man 4 cdce. I use the listet ZTE MF831. Yes, it is connected using USB and it supports 4G / LTE (I have the European version) - even it is listed as Ethernet device. > i.e. I need to be able to send a SMS even if the internet is down, ... The default (you can do that also manually over the web interface) setting is, that the device connects automatically to the network of the SIM (you don't need a internet connection to send SMS but to your phone provider as for all devices to send SMS). I also don't know, how you define SMSTools. You can open a web browser, connect to the stick using the gateway IP and send and recieve SMS (you can also manage kontakts on the SIM). Regards, Christoph
Correct way to report broken link at openiked.org ?
Hello ! I just saw at the startpage of openiked.org, that the link to Posters is broken (links to http://www.openbsd.org/older.html#posters which is a 404 Not Found). The startpages of OpenBGPD, OpenNTPD and OpenSMTPD use only one link and the destination is https://www.openbsdstore.com Thanks for answers.
Re: bug tracking system for OpenBSD
Just curious, could it be, that the problem is only a problem of the OPs from the threads (bug tracker, github mirror and so on) and, not a problem from the OpenBSD developers ? If I read the last section from https://www.openbsd.org/report.html it looks like that for me. I did not search the list but I can't remember, that someone asks which things in sendbug(1) or bugs (or their workflow) does not work for the developers / maintainers (and if there are things like that - IMHO they will fix them). Maybe people also don't want to accept that OpenBSD is not Linux. IIRC Stuart (or others) mentioned not the first time, that a human had to manage a bug tracker - if one is needed. Maybe I am total wrong but thats are my 2 cents about it. > Way to go guys, you've completely misunderstood the problem > and therefore have no solution. > >
Re: bug tracking system for OpenBSD
Thanks for your fast answer. I thought before, that the manual triage was the point. Would the devs accept / use a bug tracker ? I ask because I find start something without the devs is burning time (see the .ru domain, the UI posts ... ). If someone of the developers is interested a off list discussion could maybe help. Regards, Christoph > Hi Christoph, > > Christoph R. Murauer wrote on Sun, Apr 01, 2018 at 01:56:47PM +0200: > >> not a problem from the OpenBSD developers ? > > There *is* an actual problem: Some bug reports are not processed > immediately because at the time they are posted, nobody happens to > find the time to investigate. Later on, when somebody would have > time to look, such unprocessd reports have low visibility because > they are nothing but an old posting on a mailing list, drowning in > a lot of noise from invalid and resolved reports. > > The task of a bugtracker would be > > 1. to collect as FEW as possible tickets - > ideally only valid, unprocessed ones with complete information > > 2. to close them when resolved such that the number of open tickets > stays low > > That's why manual triage and curation is the crucial point. > > Yours, > Ingo >
Re: bug tracking system for OpenBSD
My question was serious. I am not the enemy but I think this thing will only work if the people who use it accept / like to use it and so on. > bug tracking software is 1% of the solution. At least 80% of the work is triage, and noone on this thread is serious about doing that.
Re: bug tracking system for OpenBSD
Thanks Bob, Theo, Chris for your detailed answers. >From Ingos answer : > ... Later on, when somebody would have time to look, such unprocessd reports have low visibility because they are nothing but an old posting on a mailing list, drowning in a lot of noise from invalid and resolved reports. Means for me, that a table of bugs / features are required. Instead of reinventing the wheel and add a new interface, create a table (could be a static site) including posting date, arch (release, stable, current), subject, if it is not enough a description, bug / feature, open / incomplete / WIP / closed. And, also a link back to bugs@. As a new bug / feature is posted at bugs@ add them to the table as open. If a dev answers, change it to incomplete / WIP and, if it is solved then change it to closed. A ideal world would provide complete bug reports so, the user has to provide as much informations as possible. The dev could ask for more informations if needed - if a dev didn´t ask for more details or the user don´t provide them then nothing happened. It is only a idea. I also have no team but maybe it is a option to start for one person (from a given date and, let the past) where others could join. Or, as Theo said, keep it as it is ... and expect, that users ask again about - lets say - forgotten bugs / features. Regards, Christoph
Re: bug tracking system for OpenBSD
I offer to maintain / collect bugs which are posted at bugs@. The idea of this collection is only, that no bugs are forgotten. No extra work for the developers, no new interface / UI. The idea is 1 page per month. In the next month only open, incomplete and WIP bugs are kept. Open and incomplete bugs are only kept as long as syspatch(8) support is given. Looks like : http://www.nawi.is/posts/2018-04-01-OpenBSD-bugs-status-04-2018.html I don't ask about the how but I ask, whether this informations are enough or, what is missing. There is no tracking at the above site so, feedback is needed - thanks. If this is useful (if not, no problem - it was only a offer), help is welcome. As I am alone I can (at the moment) only start from now. Regards, Christoph
