Re: Sudden reboot every 5-10 minutes on latest snapshot
On Sat, May 25, 2024 at 12:06:39PM +, Ali Farzanrad wrote: > Ali Farzanrad wrote: > > Alexandre Ratchov wrote: > > > On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote: > > > > Alexandre Ratchov wrote: > > > > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote: [...] > > I have another problem here. My USB keyboard works great in BOOTX64.EFI > > but will not work on kernel config. > > > > I created /etc/bsd.re-config file and rebooted my system twice to > > disable azalia and then checked if it is disabled using config(8) and > > dmesg(8). > > > > Even when azalia is disabled my system gets sudden reboots. > > First sudden reboot was just after playing a music; but next 2 reboots > > was happened without playing anything. > > > > > Then, just do your regular stuff and see if the system reboots. > > I tested again with my patch. When azalia is disabled, it suddenly > reboots after few minutes, without playing anything. When azalia is > enabled, it lives. > This looks to me like you are chasing down a new rabbit hole every time I open one of your emails. I'd suggest you take a step back from all the stuff you seem to be trying without having a firm grasp on how to observe or report reproducibility. Have you tried out sthen@'s advice to check old kernels + snapshots[1]? I may have missed your response to this. You wrote that you rarely got the issue prior 17-May-2024? If that *is correct*, then you should be able to bisect using the snapshot archive around what date things change. I am highlighting *is correct* above because your issue seems to be unpredictable enough that a few minutes of testing don't mean anything. I suggest you try to find a *clear difference*, meaning between a snapshot where no reboot happens for ideally a whole day of use, and the next one where it clearly happens very quickly (and reproducible at least a second or third time). Your reports also make me wonder how much customization you are running. You've mentioned at least compiling custom kernels and setting bsd.re-config. It's easy to find yourself in virtually unsolvable scenarios by configuring too much. It might be best to try a clean install, ideally without activating xenodm/X11. [1] https://marc.info/?l=openbsd-misc=171646884302309=2
Re: No packages found for 7.5 snapshot on arm64
On Sat, Mar 09, 2024 at 02:27:36PM +0500, ofthecentury wrote: > I had a similar problem this week, for amd64. > The 'packages/amd64' folder on the OpenBSD > mirrors for 7.5 snapshot is also empty. So I > just manually set PKG_PATH to 7.4 packages > folder for the time being. This will likely break things. You would be effectively mixing an almost-7.5 base with 7.4 packages. The solution is to point at the snapshots packages directory, which is what -Dsnap does for you. > On Sat, Mar 9, 2024 at 2:15 PM Dmitry Matveyev wrote: > > > > Hi, > > > > I was running an OpenBSD with this description of the iso: OpenBSD > > 7.4-current 2023-11-03 (arm64). A week ago I started getting an error > > trying to install any package: > > > > # pkg_add -Uvi colorls > > Update candidates: quirks-7.12 -> quirks-7.12 > > Update candidates: updatedb-0p0 -> updatedb-0p0 > > quirks-7.12 signed on 2024-03-05T14:52:30Z > > Can't install colorls-7.4 because of libraries > > |library c.99.0 not found > > | /usr/lib/libc.so.98.0 (system): bad major > > Couldn't install colorls-7.4 > > > > Here I have an older version whereas the package requires a newer > > version. > > > > I've read that it might be due to using -current and that I need to > > upgrade my system to the latest snapshot. I have run sysupgrade and now > > uname says that I'm on OpenBSD 7.5 GENERIC.MP#128 arm64. And now I can't > > install anything at all because pkg_add complains that it can't find a > > directory https://ftp.hostserver.de/pub/OpenBSD/7.5/packages/aarch64/. I > > have checked several mirrors at https://www.openbsd.org/ftp.html and > > they indeed don't have any packages under 7.5. > > > > How do I fix this? > > >
Re: Webcam support on Lenovo Thinkpad T14 Gen3 (Intel)
On Sat, Oct 07, 2023 at 07:08:21AM -0300, Crystal Kolipe wrote: > On Sat, Oct 07, 2023 at 08:51:36AM +, Comte wrote: > > The webcam seems well detected but no image is displayed... > > What happens if you run /usr/X11R6/bin/video instead of using ffmpeg? > > > # dmesg | grep "uvideo" > ^ > > Please post a full dmesg next time. > > > uvideo0 at uhub1 port 4 configuration 1 interface 0 "Chicony Electronics > > Co.,Ltd. Integrated Camera" rev 2.01/54.20 addr 3 > > video0 at uvideo0 > > uvideo1 at uhub1 port 4 configuration 1 interface 2 "Chicony Electronics > > Co.,Ltd. Integrated Camera" rev 2.01/54.20 addr 3 > > video1 at uvideo1 > > However, this camera should almost certainly just work anyway. > > > $ ffplay -f v4l2 -input_format mjpeg -video_size 1280x720 -i /dev/video0 >^^^ > > Why? Looks like Comte followed the console instructions at [1] to the letter. It seems to me that jumping right to ffplay recording isn't the best way for you to check the camera is working. Simplest way to test seems to me: $ video -f /dev/video0 And then you should see a window with the video stream... [1] https://www.openbsd.org/faq/faq13.html#webcam
Re: X11 crashing
On Thu, Oct 05, 2023 at 06:23:36AM +, Maria Morisot wrote: > I installed the patch for X11 (October 3rd), then rebooted, > now X is crashing every time I log in on xenodm, > sometimes I get a blue screen with debug messages, > other times I get a square on my screen with a black background, > and it is otherwise completely frozen, and I can't ctrl-alt-Fn > into a terminal. I can do this before I try logging in though, > and I tried reverting the patch but to no avail. > > My wm is xfce, and when I remove my .xsession > everything works normal without crashing. The obvious question that I have right off the bat is what is in your .xsession... Sharing that file or clarifying if anything other than xfce is in there would be a start. > > I'm far from a novice user but I don't know much about > how to properly report issues or what steps I need to take > to isolate where the problem is. There is some useful information on making useful bug reports here: https://www.openbsd.org/report.html
Re: My /usr cleaning campaign..
On Sun, Aug 13, 2023 at 06:40:54PM +0200, Daniele B. wrote: > > Thanks Stuart, as usual. > > Stuart Henderson wrote: > > > > I still do not understand why I have gtk-doc presents on disk but I > > > keep it for myself, not like the mistake on the signature, I mean.. > > > then we go to disturb the developers, bloood.. > > > > Because you installed a package which includes them. > > > > You might not need that package any more, use pkglocate to track down > > which package provides a certain file. > > pkg_info gtk-doc doesn't say me gtk-doc is installed.. I don't think that command tells you anything about the installation status of that package. When I need to check if a package is installed, I use for example: $ pkg_info | grep "gtk.doc" >From pkg_info(1): "If no pkg-name is specified, pkg_info shows the names and one-line comments for all installed packages except internal packages. > But when I launch: > > pkg_locate share/gtk-doc | less > > from the displayed list I think there is no package missing to have > resources installed there.. I'm not sure that that's the command to answer the question that you have. In fact, with wc -l: 14274 this is an exceptionally noisy command and it shows dozens if not hundreds of different packages that install into share/gtk-doc. Note that pkg_locate doesn't limit itself to what you have currently installed, but shows any file from any package, installed or not, that has the string 'share/gtk-doc' in its path. > > > For now I moved doc and gtk-doc with their image files away reaching > > > quota 25% free. If you say it I could probably be happy about it.. > > > > Now you'll have problems when you update packages. > > I move them away linking -s to them onto /usr/local, do you still think > it can cause problems? I think that's asking for trouble and sometimes hard-to-diagnose bugs with packages in the future. I'm still not sure what problem you are trying to solve... You want to upgrade, but are afraid of having too little space in the /usr partition? Frankly, having /usr/local on its own partition is exactly the kind of default that would protect you from /usr/local/share/gtk-docs impinging on your space in the /usr partition... Not sure if that problem situation isn't entirely self-made and you are looking for solving the problems of unsupported customization with even more unsupported customization...
Re: ksh bug or just normal behaviour?
On Wed, Aug 02, 2023 at 12:14:51PM +, Thomas Schweikle wrote:
>
>
> Am Mi., 02.Aug..2023 um 13:45:26 schrieb Peter N. M. Hansteen:
> > On Wed, Aug 02, 2023 at 11:35:39AM +, Ioan Samarul wrote:
> > > Can you please tell me if this is a bug or it is considered normal?
> > >
> > > $ set -A test a b c d e f g h i
> > > $ echo ${test[07]}
> > > h
> > > $ echo ${test[08]}
> > > ksh: 08: bad number `08'
> > > $ echo ${test[8]}
> > > i
> >
> > I strongly suspect you stumbled on to a case of the old convention
> > "numerals with
> > leading zeroes are interpreted as octal notation" (but do check the
> > underlying
> > code to make sure).
>
> Yes, that is it. It is considered octal notation.
And here is the proof:
$ echo ${test[010]}
i
Re: tmux server recent snapshot amd64 100% CPU freeze
On Mon, Jul 17, 2023 at 12:54:05PM +, Jacqueline Jolicoeur wrote: > Hi, > > I thought I would mention I seem to be able to reproduce a tmux lock up > where the tmux server component runs at 100% CPU. I am unable to attach > to it at that point. > > The command I run in order to reproduce this is: > > Enter the tmux command prompt. > > C-b and : > > Run this command. > > movew -r > > It stays locked with the movew command still on screen. I end up having > to kill the server process. I have noticed tmux locking up with my original tmux.conf when closing windows, likely because of renumber-windows on: set-option -g default-terminal "tmux-256color" set-option -g history-limit 3000 set-option -g renumber-windows on set-option -ag window-status-current-style bold set-option -ag window-status-current-style fg=black set-option -ag window-status-current-style bg=blue set-option -ag status-style bg=cyan set-option -g escape-time 50 I have since switched to a more simplistic config that hasn't run into the lock up, but I can still trigger it with movew -r as described above: set-option -g escape-time 50 set-option -g base-index 1 set-option -g pane-base-index 1 > > This started to occur in OpenBSD amd64 snapshots around July 13. > > I am running my OpenBSD amd64 with sysctl vm.malloc_conf=S > > ~/.tmux.conf > > set -g status-keys vi > set -g status-right "%F %R" > set -g status-style "bg=black,fg=white" > setw -g mode-keys vi > > Thanks. >
Re: Can't login after upgrading to 7.3
On Tue, Apr 11, 2023 at 05:12:34PM -0600, Nathan Gilbert wrote: > Hi, > > I ran sysupgrade on a ThinkPad X1 Carbon running 7.2 and am unable to login > afterwards. I’m unable to log in as my normal user in either the WM (LeftWM) > or the terminal, I immediately get kicked back to login. I’m able to login > with root to fvwm or cwm but can’t open a terminal. On the terminal, I get > kicked back to login as well. This system reports that I am on 7.3 at boot. > > Is there any way to debug this issue? I’m at a loss. Going out on a limb here, but this sounds an awful lot like your window manager might error out and kick yo back to xenodm. I can't find LeftWM in the ports - is that a self-compiled window manager? Also can you specify what you mean by "the terminal". If you make it to the xenodm login manager, you should be able to switch to the text console with Ctrl+Alt+F1-F4. If that works, then you could log in there and examine ~/.xsession-errors after a failed xenodm login to see what error messages are produced. > > Thanks! >
Re: Command At Startup
On Sat, Apr 01, 2023 at 04:28:20PM +0200, Peter N. M. Hansteen wrote: > On Sat, Apr 01, 2023 at 11:26:31AM +0200, Computer Planet wrote: > > Hi Guys, OpenBSD 7.2 > > I have no way to get a stupid autorun script to load. Can anyone tell me > > where to put this script? > > In /etc/rc.local it doesn't work... > > The scirtp is located in the path /home/tech > > and contains only this: > > -- > > #!/bin/ksh > > /usr/sbin/apm -C Besides what Peter replied, are you sure the flag is right? $ man apm | grep -- "-C" $ > > -- > > I would think the place to put flags for apm or apmd would be the > to put a line in /etc/rc.conf.local with apmd_flags= and the flags you > want. > > - Peter > > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. >
Re: Making MS teams work on openbsd
On Wed, Jan 18, 2023 at 10:19:25PM +0200, Divan Santana wrote: > Greetings friends :) > > In short MS teams works via chrome on openbsd7.2 for me except for the > camera. I was on an MS Teams meeting a few weeks ago with camera working. The main issue from my experience was the web client auto disconnecting after a while. > > (The camera with webrtc works fine for other sites, just not teams) > > The screen share too works, but not the camera. It detects the camera, > but when you try switch it on, it remains black. I've seen testing/preview camera output being just a black rectangle, but it worked in the meeting itself. I have package libv4l installed; not sure if that is involved. Otherwise, would check that everything has been set up correctly - correct permissions on /dev/video0 (rw), sysctl kern.video.record=1, and chromium running with ENABLE_WASM=1 in the environment. Do other browser-based video calls work? Can test for example with Zoom here: https://zoom.us/test > Anyway, I'm pretty sure a workaround to get teams video to work via > chrome on openbsd is to create a virtual camera with a res up to 720p > and make chrome use that (or buy another camera). It seems anything > higher, and teams has an issue with it. That seems like a painful workaround; check the above if that helps narrow down the problem.
Re: Auto layout for disk partitions - a new user's perspective
On Mon, Apr 18, 2022 at 01:36:18PM -, Stuart Henderson wrote: [...] > > 2) Should there be a /usr/local/pobj partition created with correct mount > > options? (I appreciate building ports is an "advanced" thing to do - but it > > feels weird having to mess with partition layout after a fresh install just > > to > > build them) > > Ports doesn't use /usr/local/pobj by default (you can set it via WRKOBJDIR > in mk.conf, but /usr/local isn't a great place for a filesystem with rapid > changes during a port build). Also, /usr/local/pobj *is* normally wxallowed. > > If you are using ports I would strongly recommend a separate filesystem > for /usr/ports, either with default ports-related directories (i.e. don't > change dirs in mk.conf) and set that wxallowed, or with a separate WRKOBJDIR > on a wxallowed filesystem. I think it might be worth repeating that packages are the recommended way to use third-party software. And that's also a great justification why there is no /usr/ports partition on a default install. Unless you are doing ports development work, you shouldn't need the ports tree. There are rare ports which don't have a package (for license reasons). If you need one of them, CVS has the advantage over git that you can checkout a subdirectory. If you do this for an individual port, the space requirements should be minimal. Still, for regular use you shouldn't need to deal with any of this.
Re: New desktop CPU/chipset recommendation
On Thu, 3 Feb 2022 19:16:55 -0500 Andre Smagin wrote: > Replying to my own thread from months ago. Took some time to get > this done, buying one part per paycheck, but I have a new desktop now. > Ryzen 9 5950x on x570 chipset motherboard, should last ten years at > least. Everything "just works" - NVMe hard drives, SPDIF audio, video, > etc. Does the audio work? No audio hangs/wedging anymore on more than just a few minutes of usage? I have a machine like this, too, but audio would hang with MSI on like previous Ryzen generations. Unlike previous Ryzen generations, patching to switch to legacy interrupts didn't work. That was about 1.5 years ago; it currently serves as a Windows box ... It would be good to know if that issue went away... I wouldn't mind putting a better OS on my machine again *cough*. > > Big thanks to OpenBSD developers! No issues to complain about, fresh > install, copied my configuration files from old desktop, was up and > running in 30 minutes. Day 3 to configure Windows 11 on a second hard > drive (to run 3d CAD software mostly) and now I have to reinstall - > broke something completely while trying to set it up to be usable...
Re: New desktop CPU/chipset recommendation
On Mon, Sep 20, 2021 at 02:56:31PM -0400, Andre Smagin wrote: > Good day. > > I am looking for a hardware advice. > I don't upgrade my desktop very often - last one was about ten > years ago (AMD FX-8350 CPU), which I recently made my home server > running -current, no issues. Now I am looking for a new desktop that > will last another ten years, hence the question: if I buy the latest > available AMD chipset (X570 I think) and Ryzen 9 CPU - are there any > current issues with using it for OpenBSD desktop? I would like to > overkill it with the choice of hardware now, so I don't have to worry > about it for a while. If you need audio, that might be a barrier to recent AMD CPUs: https://marc.info/?l=openbsd-bugs=161221378203609=2 https://marc.info/?l=openbsd-bugs=160112047222899=2 Earlier Ryzen CPUs worked after disabling MSI for azalia(4), but it seems to not be a solution anymore with later models. For desktop, Ryzen 2xxx CPUs seem to be the last ones without the audio limitations. I ran a Ryzen 7-2700 for a while. If you plan to use GPU acceleration, amdgpu(4) still seems to run into poorly predictable "freezes" where the screen stops updating. I most recently experienced this a week or two ago on the Thinkpad X395. This is probably still an issue with dedicated GPUs, too. Using an AMD Radeon card type Northern Island or older would be the only solution I can think of, but that is > 10 year old hardware and doesn't support newer OpenGL or Vulkan. These issues together are the reason why I personally ended up back on Intel hardware. If your goal of "overkill with choice of hardware now" includes using audio and GPU acceleration including newer APIs, a 10th or 11th gen Intel CPU may be the best option. Of course, if you don't use audio and don't need GPU acceleration, then all these points are moot and you could just get the most powerful Ryzen 9 you can afford. (Note you may not get a lot of return on investment for core counts > 8.) > > I am ten years out of touch with hardware development progress, so will > appreciate any input you may have. > > -- > Andre >
Re: kitty termcap entry
On Mon, Jun 21, 2021 at 11:00:54AM -, Stuart Henderson wrote: > On 2021-06-20, Björn Gohla wrote: > > > > hi all, > > > > i have the following problem with the kitty terminal emulator: > > > > > > 15:43:39 bgohla@titanic ~ $ doas pkg_add hello > > doas (bgo...@titanic.my.domain) password: > > failed termcap lookup on xterm-kitty at > > /usr/libdata/perl5/OpenBSD/ProgressMeter/Term.pm line 113. > > 15:44:02 bgohla@titanic ~ $ echo $TERM > > xterm-kitty > > 15:44:17 bgohla@titanic ~ $ > > > > > > it seems the problem is that there is no entry for xterm-kitty in > > /etc/termcap. the above pkg_add invocation works when i set TERM=xterm . > > > > i suppose one could just add a termcap entry that redirects to > > xterm. > > > > would this be a patch in the kitty port, or does this require a change > > to the base system? > > > > -- > > cheers, > > björn > > > > > > It would require a change in the base system, /usr/share/misc/termcap is > a system file and isn't something that can be modified from a port. > Additionally it will get overwritten when the OS is updated. It should be possible to add xterm-kitty from the output of $ infocmp -C xterm-kitty to /usr/share/misc/termcap; similar to what was done over the years for example with rxvt-unicode-256color. The template in src for this seems to be share/termtypes/termtypes.master, but it uses a different format for the entries (commas as separators instead of colons and some differences in capabilities shorthands). termininfo(5) seems to have enough information to construct an entry for termtypes.master if that's desired. Not sure if kitty is important enough to add in there. I've been running with "term xterm-256color" in ~/.config/kitty/kitty.conf for a while without issues. However, xterm-256color doesn't seem to match xterm-kitty 100%. > > Software that uses terminfo will work with kitty as it sets TERMINFO in > the environment pointing at its own special file; that's not possible > with termcap. > >
Re: FVWM terminal emulator transparency issue in -current
On Mon, Feb 15, 2021 at 05:03:55PM -0600, Luke Small wrote: > I'm running fvwm window manager and I just switched to -current. Roxterm is > totally messed up, won't do transparent background and I tried > xfce4-terminal and it says it won't do transparent backgrounds because > compositing is disabled Sure first-world problems, but I REALLY want > fvwm to do transparent terminal emulators! You can just run a compositor. xcompmgr(1) is in the X install. I personally use compton from the package of the same name. picom (also in packages) is supposed to be a successor to compton. They allow more compositor tricks than xompmgr. I've never got application's transparency settings to work well, so my .kshrc (set in ENV in .profile) contains lines calling transset-df from the package of the same name: [ -n "$XTERM_VERSION" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null [ -n "$KITTY_WINDOW_ID" ] && transset-df --id "$WINDOWID" 0.85 > /dev/null
Re: Chromium with WebAssembly flavor?
On Fri, Jan 29, 2021 at 09:44:26PM -0600, Charlie Burnett wrote: > Hi, > I wasn't sure if this was worthy of ports or not, so I wanted to throw this > out here first. I don't like Zoom, and I understand WebAssembly has some > inherent issues in it, but I imagine a good number of people don't have a > choice and have to use it as well in light of the current state of things. > On top of this, Citrix apps need it enabled as well. Wouldn't it be > reasonable to make a flavor with ENABLE_WASM set for chromium then? I think you misunderstand how this works. ENABLE_WASM is for the runtime environment; you don't need to rebuild the whole port. In fact, if set ENABLE_WASM for a build of the port, it likely still won't enable WebAssembly. Take an example webpage that checks for WebAssembly (for example [1]): $ chrome => "WebAssembly is not supported in your browser" $ ENABLE_WASM=1 chrome => "WebAssembly is supported in your browser" > Compiling chrome manually with the flag is a beast, and my laptop will > usually throw a kernel panic before it'll finish compiling, plus as a > package it's updated quite regularly which means it needs to be recompiled > quite regularly. > Best regards, > Charlie [1] https://d2jta7o2zej4pf.cloudfront.net/
Re: gpt/uefi
On Fri, Sep 18, 2020 at 03:15:21AM -0300, Gustavo Rios wrote: > Hi folks! > > I would like to install on my notebook 3 operating systems: OpenBSD, > Linux and Windows 10. > > Do you know any tutorial on how the create the partitions using GPT > before i install any of the 3 OSes ? I would like to boot via UEFI; is > there any special partition for the UEFI booting ? May the 3 OSes use > the UEFI boot partition ? > > This will be my first experience with GPT/UEFI so i need a little > help. May you point me in the right direction? The most pertinent section of the FAQ would be [1]. For what it's worth, I dual-boot Windows 10 and OpenBSD on my laptop, using MBR and BCD. A PBR for Linux could probably be added without problems. Note that this depends on third-party software out of our control, and therefore (quoting the FAQ): "you are completely on your own." [1] https://www.openbsd.org/faq/faq4.html#Multibooting
Re: USB Camera
On Thu, Sep 17, 2020 at 03:46:25PM +0200, Jan Stary wrote: > Can people please recommend an USB camera > that is known to work well with OpenBSD? I have a Logitech C310 USB webcam that works well for my purposes. It's 720p. Note I haven't used the mic, as I have a separate USB mic. > Are they generally better > than the built-in laptop cameras? Probably. Depends of course on your laptop. You may want to look for some sample recordings online to get a sense if the image quality would suite your needs. > > I might be forced to lecture online this upcomming semester, > and tried the builtin mic and camera of a macbook. > Not horrible when close-capturing myself as a talking head in front > of a whiteboard, but both the audio and video could be improved. > I get good sound through a MobilePre uaudio(4), > but am at a loss wrt uvideo(4) cameras. > > Thanks, > > Jan >
Re: ThinkPad T14 AMD
On Mon, Aug 24, 2020 at 12:41:21AM +, s...@skolma.com wrote: [...] > I require Citrix and ms teams so unfortunately I’m running Linux on it . I don't know about MS Teams, but I also use Citrix for work and do that with Citrix Workspace chromium plugin: https://chrome.google.com/webstore/detail/citrix-workspace/haiffjcadagjlijoggckpgfnoeiflnem Maybe this can help some reduce their dependency on !OpenBSD...
Re: Mounting encrypted drive on boot
On Wed, Jun 03, 2020 at 12:27:00AM +0100, Chris Narkiewicz wrote:
[...]
> My setup consist of OpenBSD 6.7 with full drive encryption using
> softraid, configured as described in FAQ:
>
> /dev/sd0a - encrypted volume
> /dev/sd1 - decrypted
>
> I have additional need to mount an encrypted /var volume on boot.
> This volume is separate drive attached to be VPS "machine".
>
> I want to mount this drive automatically on boot by adding
> relevant entries to /etc/fstab, but before this can be done,
> softraid device must be configured using bioctl.
>
[...]
>
> Somebody on StackOverflow advised on modifying /etc/rc
> and run bioctl before disks are mounted, but I'm not sure
> if this is a right approach, especially that attaching
> more disks might change the /dev/sd* numberign.
Don't modify /etc/rc itself.
rc(8): "Normally, rc.local contains commands and daemons that are not
part of the stock installation."
I don't fully understand your question, but I used to have an rc.local
to allow using /home from an encrypted USB drive that got loaded from
rc.local. I'm not endorsing this as a great solution, but maybe this
will serve as inspiration for you to come up with your own method.
/etc/rc.local (REPLACE with your disk's DUID):
# CRYPTO_DEV assumes that home is on the k partition of a disk with the DUID
.
CRYPTO_DEV=`sysctl hw.disknames | sed -n -E "s/.*(sd[0-9]{1,2}):.*/\1/p"`
fsck -y /dev/r${CRYPTO_DEV}k
mount -o softdep,nodev,nosuid .k /home
signature.asc
Description: PGP signature
Re: Game controller / gamepad recommendation
On Wed, Jan 22, 2020, at 12:29 AM, Raf Czlonka wrote: > Hi all, > > I'm in a search for a game controller / gamepad for OpenBSD and > found an old article on OpenBSD Journal[0] regarding (support for) > an Xbox 360 one. SDL2 got some tweaks since [1] that allow using the Xbox 360 (wired) gamepad for all SDL2 games/applications. This is probably the most popular and best designed of all supported gamepads at this moment. > Good ol' Logitech has two gamepads - one wired[1] and one wireless[2] I have a Logitech F310 and it's probably the best option compatibility-wise you can switch between traditional joystick/DInput (D) mode and Xbox360 pad/XInput (X) mode with a switch on the back. > Has anyone tried Xbox One controller or Valve's, recently discontinued, > Steam Controller? I have those and they don't work. Unfortunately these gamepad manufacturers have abandoned any idea of portability and don't even provide USB HID descriptors. Instead it seems that everything is run through a custom driver for each device. The Linux kernel has special entries to detect the XBox One controller and send an initialization sequence that seems to be required. It may be possible to come up with an approach similar to our XBox360 implementation, but someone needs to come up with this. I also have a Steam controller. Interestingly, it attaches as mouse + keyboard by default if I recall it correctly. However, getting it to fully work as a gamepad also seems to require coming up with a way to provide a uhid descriptor. > I'd prefer a wireless one but a wired one will be just fine if it > "just works" and/or is superior to a wireless one. Yes, I'm well > aware that there's no Bluetooth support on OpenBSD but am thinking > of a wireless Logitech-style, i.e. with a wireless USB dongle. I'm not aware of any Bluetooth-less wireless gamepad option, but would like to hear of it if it exists. [...] > it here as, from what I understand, some emulators/games require > analogue control. SDL1 and those using joystick API otherwise would fall in this category. Again, the F310 has a switch to serve both modes. games/sdl-jstest has test binaries for D and X mode that can be used to see what works and what doesn't. [...] [1] https://marc.info/?l=openbsd-ports-cvs=154653811709620=2 -- tfrohw...@fastmail.com PGP Public Key: https://pgp.mit.edu/pks/lookup?op=get=0xE1A22D58D20C6D22
Re: OpenBSD and solid state disks
[...] > My question is whether OpenBSD addresses the special characteristics > of solid state drives, especially those having to do with longevity > and reliability. I can't find anything written on this. Linux has > certain means for addressing this issue, such as fstrim as well as > various kernel options. Is there anything I have missed with OpenBSD > on this subject? I'm certainly not one to reply to this question on the raw metal/filesystem level, but I can assure you that I have used OpenBSD on SSDs (in different computers) for several years by now without noticing any of the scares that circulate about SSDs (those seem to be mainly filesystem corruption and/or significant slowdown). Some of the concerns may simply go back to early generations of SSD drives. I recall that tedu@ discussed SSDs and these matters on his flak blog previously that may contain more details and possibly reassurance for you. Mounting with softdep seems to be advisable. I'm happy to be complemented or corrected by someone with more in-depth knowledge of the low-level aspects of SSDs.
Re: Good Quality Microphone for Podcasts compatible with OpenBSD
I've been doing screencasts to Twitch from OpenBSD that improved significantly with the Samson Meteor Mic, a USB Mic. No compatibility issues there, and I'm very pleased with the quality.
Re: Activating second crypted (or other raid) device
On Sun, May 05, 2019 at 08:57:55PM +0300, cho...@jtan.com wrote: [...] > Currently after every upgrade I patch /etc/rc to run /etc/rc.blockdev > (containing bioctl -cC -p /etc/sd0.key -l sd0a softraid0) before the > additional filesystems are checked or mounted. The order of sdX may change if e.g. a USB drive is plugged in during boot. You know you _can_ use the device UUID which AFAIK should be much more robust than using sdX. I used the following line at some point in an rc.local: bioctl -c C -l b3914b7ba0818788.a softraid0 > Before I resign myself to patching /etc/rc in perpetuity, is there a > better or more canonical way to activate a second encrypted disc using a > key file in /etc before filesystems defined in /etc/fstab are checked or > mounted (it becomes /srv)? That would be rc.local. From rc(8): Normally, rc.local contains commands and daemons that are not part of the stock installation. > The patch I use is below. Ignore the date; I've been using this since > around 6.2 at least. I feel rather silly saying that you're welcome to > use this tiny patch if it's useful, but there it is and you are. I empathize with your drive to get hands-on with the code to find a solution to a problem and the desire to share it, but the solution you are proposing should be discouraged. You are proposing a trivial 1-line patch to a file that isn't meant to be patched; ignoring the man page that contains a valid place for local customizations. For yourself, the closer you stay to the default install especially in regards to infrastructure like rc(8), the less likely you will run into bugs that are not reproducible by others.
Re: Malloc config became global sysctl in 6.5
On Sun, Apr 28, 2019 at 02:07:44AM +0700, Igor Podlesny wrote: [...] > Looks like decision made aren't subjects of discussing(?) Well, why > the hell you have those mail lists then(?) :) Igor: The actual purpose of misc@ is for us to learn that you are among the people to ignore. Everyone else: Move along, nothing to see here.
Re: [PATCH] Remove "Multibooting" in FAQ
On Sat, Apr 06, 2019 at 09:10:59PM +0300, Leonid Bobrov wrote: > On Sat, Apr 06, 2019 at 05:45:42PM +, tfrohw...@fastmail.com wrote: [...] > > Sure, what did you have to do in order to dualboot Windows and OpenBSD? > > I'm not experienced with dualbooting at all because I never need/must to > use it. I remember the following as the steps not mentioned in the FAQ that helped me get it to work. All with MBR and Windows 10. 1. Shrink the main partition in Windows disk manager and create a second partition. 2. In the OpenBSD installer, run fdisk and change the type of the second partition to OpenBSD (A6), otherwise keeping same size/offset. 3. For softraid crypto, follow the FAQ for installation. You should create the RAID partition as 'a' on the OpenBSD part of the disk, leaving (in my case 'i' and 'j' intact. If the above steps help you or your friend to set it up, we can see if an addition to the FAQ may be worth considering. Here my disklabel and fdisk from that setup: # /dev/rsd0c: type: SCSI disk: SCSI disk label: WDC WDS500G2B0B- duid: f2adf57b4715cd30 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 60801 total sectors: 976773168 # total bytes: 476940.0M boundstart: 455473152 boundend: 976769024 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:254539.0M455473152RAID c:476940.0M0 unused i: 500.0M 2048NTFS j:221898.0M 1026048NTFS Disk: sd0 geometry: 60801/255/63 [976773168 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 07 0 32 33 - 63 221 30 [2048: 1024000 ] NTFS 1: 07 63 221 31 - 28247 27 2 [ 1026048: 452763710 ] NTFS 2: 27 28247 58 36 - 28351 195 4 [ 453791744: 1679360 ] Win Recovery 3: A6 28351 227 37 - 60801 15 14 [ 455473152: 521295872 ] OpenBSD
Re: Determining if a package is installed (regardless of version)
On Wed, Mar 27, 2019 at 07:27:15AM +, Adam Steen wrote: [...] > I should have been more specific, my use case completes the check in two steps > > 1. find out whats installed, builds a list of packages > 2. install whats not installed. [...] If you want to build a list of installed packages from a current installation and install the same packages on different computer or at a later point, you could use pkg_add(1) with -z and -l to use a file created by pkg_info -m > file as the input. See man page for pkg_add(1). If you want to install every single available package, I'm not sure if there's a way and the use case for this escapes me. You could probably get the full list of all available packages with a (text) browser from the directory index of one mirrors, format it (e.g. removing '\.tgz.*' with regex) and feed that to pkg_add -z -l ... but I would question your use case and/or sanity...
Re: Shadow artifacts and color distortions when using compton(1). Perhaps after recent Xenocara update?
On Sun, Feb 10, 2019 at 11:16:03PM +0100, Erling Westenvik wrote: > Hi, > After upgrading to todays snapshot (February 10th) I experience some rather > ugly shadow artifacts and color distortions when using compton(1) under > cwm(1). > It may perhaps best be described by linking to an issue report from April 2018 > at github: > > https://github.com/chjj/compton/issues/487 > > and from that page - a link to a screendump showing exactly what I experience: > > https://framapic.org/dHfk2217huGs/NIiGKJsfnz52.jpg > > The problem can be reproduced by specifying "glx" as backend in compton(1). > It > appear to have been major glx-related imports in Xenocara on January 29th > 2019. > My previous snapshot was older than that, perhaps as old as from December > 2018, > but for certain newer than the previous bulk import which appears to have > been October 23rd 2018. > > My graphics card is a ATI Radeon HD 5770. Dmesg below. > > Not sure how to attack this. Help/ideas appreciated. [...] Yep, I noticed the same with compton after the update to Mesa 18 in snaps. I think the following GitHub issue is actually the more fitting one: https://github.com/chjj/compton/issues/477 For me, switching to xrender backend for compton is a satisfactory solution until the freedesktop bug referenced in the above link [1] has been addressed. [1] https://bugs.freedesktop.org/show_bug.cgi?id=104597
Re: ddb(4) and usb keyboards
On Sun, Oct 14, 2018 at 12:53:53AM -0500, Colton Lewis wrote: [...] > I wish to use the kernel debugger, but triggering it from the system > console causes the computer to stop responding to all keyboard input > and my only way out is a hard reset. I have tried every USB hub on my > system with the same result. I do not currently own another keyboard > to try. Adding the following line to /etc/sysctl.conf should allow you to use a USB keyboard in ddb(4): machdep.forceukbd=1
Re: New laptop recommendations
No AMD laptop recommendations in this day and age? Also buying used or refurbished laptops on eBay is a security risk from the outset - ask yourself how well you would be at spotting if someone had tampered e.g. with the webcam or the firmware? With new hardware, you have at least a reasonable expectation that the package hasn't been opened between manufacturer and you...
Re: Poor browser performance in OpenBSD
On Wed, Jun 20, 2018 at 11:36:37AM +0300, wrote: > cat /var/log/Xorg.0.log > > [17.555] (--) checkDevMem: using aperture driver /dev/xf86 > [17.603] (--) Using wscons driver on /dev/ttyC4 > [17.639] > X.Org X Server 1.19.6 When I tried different settings with Intel integrated graphics recently, I got the best performance with modesetting driver *and* with machdep.allowaperture=0. The latter should result in a warning (WW) at the beginning of Xorg.0.log like this: [36.333] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [36.333]linear framebuffer access unavailable which I don't see in your Xorg.0.log. I suspect you set allowaperture to something else manually. While I don't fully understand the technical reasons for it, anything greater than 0 led to a performance drop or other issues when I tested this a few weeks ago. Therefore, I would recommend you try the modesetting driver (just remove the intel driver from xorg.conf) with allowaperture set to 0. Please let me know if that helps - it may also be useful for others to know. Here's my Xorg.0.log: [36.333] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [36.333]linear framebuffer access unavailable [36.355] (--) Using wscons driver on /dev/ttyC4 [36.366] X.Org X Server 1.19.6 Release Date: 2017-12-20 [36.366] X Protocol Version 11, Revision 0 [36.366] Build Operating System: OpenBSD 6.3 amd64 [36.366] Current Operating System: OpenBSD e5570.domain 6.3 GENERIC.MP#36 amd64 [36.366] Build Date: 20 June 2018 12:26:31AM [36.366] [36.366] Current version of pixman: 0.34.0 [36.366]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [36.366] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [36.366] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 20 08:29:43 2018 [36.367] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [36.368] (==) No Layout section. Using the first Screen section. [36.369] (==) No screen section available. Using defaults. [36.369] (**) |-->Screen "Default Screen Section" (0) [36.369] (**) | |-->Monitor "" [36.369] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [36.369] (==) Automatically adding devices [36.369] (==) Automatically enabling devices [36.369] (==) Not automatically adding GPU devices [36.369] (==) Max clients allowed: 256, resource mask: 0x1f [36.370] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [36.370] (==) ModulePath set to "/usr/X11R6/lib/modules" [36.370] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [36.370] (II) Loader magic: 0x17a4fa86e000 [36.370] (II) Module ABI versions: [36.370]X.Org ANSI C Emulation: 0.4 [36.370]X.Org Video Driver: 23.0 [36.370]X.Org XInput driver : 24.1 [36.370]X.Org Server Extension : 10.0 [36.370] (--) PCI:*(0:0:2:0) 8086:5912:1462:7a74 rev 4, Mem @ 0xde00/16777216, 0xb000/268435456, I/O @ 0xf000/64 [36.371] (--) PCI: (0:1:0:0) 1002:67b1:148c:2358 rev 128, Mem @ 0xc000/268435456, 0xd000/8388608, 0xdf10/262144, I/O @ 0xe000/256 [36.371] (II) LoadModule: "glx" [36.372] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [36.382] (II) Module glx: vendor="X.Org Foundation" [36.382]compiled for 1.19.6, module version = 1.0.0 [36.382]ABI class: X.Org Server Extension, version 10.0 [36.383] (==) Matched modesetting as autoconfigured driver 0 [36.383] (==) Assigned the driver to the xf86ConfigLayout [36.383] (II) LoadModule: "modesetting" [36.383] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so [36.384] (II) Module modesetting: vendor="X.Org Foundation" [36.384]compiled for 1.19.6, module version = 1.19.6 [36.384]Module class: X.Org Video Driver [36.384]ABI class: X.Org Video Driver, version 23.0 [36.384] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [36.384]
Re: firefox crashes when password field is focused
> Whenever I click on a password field on a website firefox crashes. > This is on current w/ newest firefox and is reproducible on every > password field on every site I tried (although usernames work fine) > and is reproducible with all combinations of settings including > default. It has persisted for the last few days. > firefox[35106]: pledge "proc", syscall 2 It's because of the new plegde of firefox. Happens when messagebus isn't running. Make sure you got dbus installed and activated in /etc/rc.conf.local, like this: pkg_scripts=messagebus
Re: Different sound sources interfere with each other
> > The first problem is: when I listen to music (cmus) and browse in the > > internet (Firefox) cmus sometimes stops playing for a second. > > This happens when I click a link on a page or receive some notification > > from the web page (which may play some short sound) > > I am having the same problem when using USB audio device: > > uaudio0 at uhub10 port 7 configuration 1 interface 0 "Burr-Brown from TI USB > Audio DAC" rev 1.10/1.00 addr 3 > uaudio0: audio rev 1.00, 2 mixer controls > audio1 at uaudio0 > > There is a short interruption in sound when browsing. I think, the > exact time this happens is when Firefox launches new content process > on opening a new tab. There's 4 such processes by default, and it > looks like the issue mostly goes away when there's more then 4 tabs > already open. > > Issue can be reproduced without involvement of sndiod or a media > player by just running cat > /dev/audio1 < /dev/random. I was unable > to pinpoint any reliable triggers, other than Firefox. Nothing happens > in Chrome. Playback on built-in audio device is not affected. While I'm no expert in the matter and have never tried cmus, I know that other ports like mpg123 and moc exhibit the same behavior that you are describing. On the other hand, mpv doesn't seem affected, even when playing audiostream + full HD video. I suspect it may be related to how the ports handle threading, and if your heart isn't set on cmus specifically, you can probably find a different port that will suit your needs. Best advice I got on this... :/
Re: node: Cannot allocate memory
I can't reproduce this on -current amd64, neither with a snapshot from last
week, nor after updating today.
thfr@e5570:~$ node -v
v8.11.1
thfr@e5570:~$ node
> console.log('test log');
test log
undefined
> .exit
thfr@e5570:~$
> node -v
> bash: /usr/local/bin/node: Cannot allocate memory
I run ksh. Doubt that bash is the cause though...
Might wanna check if you have the same problem with ksh.
> I am on current, last grabbed the snapshot last Friday I think.
... still, you provided rather little information to understand what might be
particular about your system. In most cases, including a dmesg is MVP to
understand this better.
> Plenty of swap and memory available
Yes? what about your ulimit?
Re: Buying new laptop, looking for feedback
Hi, The specs on my Dell Latitude E5570 should similar to what you're looking at with the T470s. I'm very happy with running OpenBSD on it. The only limitations that I've noticed are: - I can't adjust screen brightness in OpenBSD. - The dedicated AMD R7 M370 doesn't work, but things run fine with the integrated Intel HD 530 - BIOS/firmware settings for HDD/SSD need to be switched from RAID to AHCI. - Very rarely, no input is registered from the keyboard or touchpad. Seems to be a BIOS bug because I've also observed it once after booting into Windows 10. Otherwise this one may be worth considering esp. if you could get it for a better price than the T470s. OpenBSD 6.3-current (GENERIC.MP) #36: Wed May 9 09:34:27 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17008320512 (16220MB) avail mem = 16484810752 (15721MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xea900 (105 entries) bios0: vendor Dell Inc. version "1.18.6" date 12/08/2017 bios0: Dell Inc. Latitude E5570 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT WSMT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT UEFI SSDT SSDT MSDM SLIC SSDT DMAR TPM2 SSDT ASF! WPBT acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(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) i7-6820HQ CPU @ 2.70GHz, 2295.40 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,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 24MHz 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) i7-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN 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-6820HQ CPU @ 2.70GHz, 2294.66 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz, 2294.66 MHz cpu5:
