arandr/xrandr only dectecting 1 of 2 amdgpu(4) video cards
Hello Everybody, On a system running -current with 2 video cards, I want to use arandr to configure grafically at least 10 monitors and because the "Option Rotate" settings in xorg.conf is not working. [25.614] (--) PCI:*(3@0:0:0) 1002:7312:1002:031e rev 0, Mem @ 0xa000/268435456, 0xb000/2097152, 0xb580/524288, I/O @ 0x7000/256 [25.614] (--) PCI: (12@0:0:0) 1002:7312:1002:031e rev 0, Mem @ 0x8000/268435456, 0x9000/2097152, 0xb550/524288, I/O @ 0x4000/256 $ cat /etc/X11/xorg.conf.d/20-amdgpu.conf Section "Device" Identifier "Card3" Driver "amdgpu" BusID "PCI:3:0:0" EndSection Section "Device" Identifier "Card12" Driver "amdgpu" BusID "PCI:12:0:0" EndSection In menu "Outputs" menu of arandr, only 6 DisplayPort are shown. $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x5a cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 6 associated providers: 0 name:AMD Radeon Pro W5700 @ pci::03:00.0 I have tested the same setup with an Ubuntu live CD, and 12 DP were recognized. Thanks for your help. $ cat /var/log/Xorg.0.log [21.301] (--) checkDevMem: using aperture driver /dev/xf86 [21.306] (--) Using wscons driver on /dev/ttyC4 [21.332] X.Org X Server 1.21.1.13 X Protocol Version 11, Revision 0 [21.332] Current Operating System: OpenBSD alexis.test.local 7.6 GENERIC.MP#394 amd64 [21.332] [21.332] Current version of pixman: 0.42.2 [21.332]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [21.332] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [21.332] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 28 16:37:56 2024 [21.334] (==) Using config directory: "/etc/X11/xorg.conf.d" [21.334] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [21.335] (==) No Layout section. Using the first Screen section. [21.335] (==) No screen section available. Using defaults. [21.335] (**) |-->Screen "Default Screen Section" (0) [21.335] (**) | |-->Monitor "" [21.336] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [21.336] (**) | |-->Device "Card0" [21.336] (**) | |-->GPUDevice "Card1" [21.336] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [21.336] (**) Allowing byte-swapped clients [21.336] (==) Automatically adding devices [21.336] (==) Automatically enabling devices [21.336] (==) Not automatically adding GPU devices [21.336] (==) Automatically binding GPU devices [21.336] (==) Max clients allowed: 256, resource mask: 0x1f [21.338] (==) 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/ [21.338] (==) ModulePath set to "/usr/X11R6/lib/modules" [21.338] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [21.338] (II) Loader magic: 0x34fe7ca0500 [21.338] (II) Module ABI versions: [21.338]X.Org ANSI C Emulation: 0.4 [21.338]X.Org Video Driver: 25.2 [21.338]X.Org XInput driver : 24.4 [21.338]X.Org Server Extension : 10.0 [21.339] (--) PCI:*(3@0:0:0) 1002:7312:1002:031e rev 0, Mem @ 0xa000/268435456, 0xb000/2097152, 0xb580/524288, I/O @ 0x7000/256, BIOS @ 0x/131072 [21.339] (--) PCI: (12@0:0:0) 1002:7312:1002:031e rev 0, Mem @ 0x8000/268435456, 0x9000/2097152, 0xb550/524288, I/O @ 0x4000/256, BIOS @ 0x/131072 [21.339] (II) LoadModule: "glx" [21.340] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [21.350] (II) Module glx: vendor="X.Org Foundation" [21.350]compiled for 1.21.1.13, module version = 1.0.0 [21.350]ABI class: X.Org Server Extension, version 10.0 [21.351] (II) LoadModule: "amdgpu" [21.351] (II) Loading /usr/X11R6/lib/modules/drivers/amdgpu_drv.so [21.353] (II) Module amdgpu: vendor="X.Org Foundation" [21.353]compiled for 1.21.1.13, module version = 23.0.0 [21.353]Module class: X.Org Video Driver [21.353]ABI class: X.Org Video Driver, version 25.2 [21.353] (II) AMDGPU: Driver for AMD Radeon: All GPUs supported by the amdgpu kernel driver [21.354] (II) AMDGPU(0): [KMS] Kernel modesetting enabled. [21.476] (II) AMDGPU(1): [KMS] Kernel modesetting enabled. [21.543] (EE) Screen 1 deleted because of
Re: iwx(4) / Intel Wi-Fi 6 AX210 not configured
Hello Stefan, Thanks for your answer. From a weekly live build of debian-live-testing-amd64-gnome.iso : root@debian:~# cat /etc/issue Debian GNU/Linux trixie/sid \n \l root@debian:~# lshw -C network *-network description: Wireless interface product: Meteor Lake PCH CNVi WiFi vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: d0:65:78:75:e2:84 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=6.11.2-amd64 firmware=89.202a2f7b.0 ma-b0-gf-a0-89.uc ip=192.168.0.32 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:400-3ff irq:18 memory:405b714000-405b717fff root@debian:~# dpkg -l |grep iwlwifi ii firmware-iwlwifi 20240709-2 all Binary firmware for Intel Wireless cards On 21/10/2024 16:25, Stefan Sperling wrote: On Mon, Oct 21, 2024 at 03:57:19PM +0200, Alexis de BRUYN [Mailing Lists] wrote: Hello everyone, With a Lenovo ThinkPad X1 Carbon Gen 12 (21KC-CTO1WW, BIOS and firmware up to date) and a -current fresh install (with a dock), I can't get the Intel AX200 wireless network device working. No iwx interface is listed with ifconfig(8). And in dmesg(8): "Intel Wi-Fi 6 AX210" rev 0x20 at pci0 dev 20 function 3 not configured There are some more recent hardware variants which are not yet supported by iwx driver. If your card does not attach then it is likely one of them. Is there a solution? Wait for supported to appear. Meanwhile, you could boot Linux and try to figure out which firmware image the iwlwifi driver is loading. Knowing this will make it easier to add support for your particular device once newer hardware is supported. -- Alexis de BRUYN
iwx(4) / Intel Wi-Fi 6 AX210 not configured
USB Audio" rev 2.01/0.95 addr 5 uaudio1: only one clock domain supported uhidev0 at uhub6 port 2 configuration 1 interface 3 "Lenovo ThinkPad Thunderbolt 3 Dock USB Audio" rev 2.01/0.95 addr 5 uhidev0: iclass 3/0, 16 report ids uhid0 at uhidev0 reportid 4: input=0, output=38, feature=0 uhid1 at uhidev0 reportid 5: input=34, output=0, feature=0 uhid2 at uhidev0 reportid 6: input=0, output=36, feature=0 uhid3 at uhidev0 reportid 7: input=32, output=0, feature=0 uhid4 at uhidev0 reportid 16: input=2, output=0, feature=0 ugen0 at uhub6 port 2 configuration 1 "Lenovo ThinkPad Thunderbolt 3 Dock USB Audio" rev 2.01/0.95 addr 5 ugen1 at uhub4 port 5 "LENOVO 40AN" rev 2.01/31.81 addr 6 ugen2 at uhub1 port 7 "Synaptics product 0x0123" rev 2.00/0.00 addr 7 ugen3 at uhub1 port 9 "SLS Lattice AI USB 2.0" rev 2.10/41.64 addr 8 ugen4 at uhub1 port 10 "Intel Bluetooth" rev 2.01/0.00 addr 9 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (496af608b649cff7.a) swap on sd0b dump on sd0b drm:pid0:init_engine_mask *NOTICE* [drm] No GSC FW selected, disabling GSC CS and media C6 drm:pid0:ct_send *ERROR* [drm] *ERROR* GT1: GUC: CT: No response for request 0x4000 (fence 1) drm:pid0:intel_guc_ct_send *ERROR* [drm] *ERROR* GT1: GUC: CT: Sending action 0x4000 failed (0xffc4e) status=0 drm:pid0:intel_huc_auth *ERROR* [drm] *ERROR* GT1: HuC: clear media authentication failed 0xffc4e drm:pid86854:ct_handle_response *ERROR* [drm] *ERROR* GT1: GUC: CT: Unsolicited response message: len 1, data 0xf000 (fence 1, last 1) drm:pid86854:ct_handle_hxg *ERROR* [drm] *ERROR* GT1: GUC: CT: Failed to handle HXG message (0xfffee) 0x8135e378h drm:pid86854:ct_handle_msg *ERROR* [drm] *ERROR* GT1: GUC: CT: Failed to process CT message (0xfffee) 0x8135e374h inteldrm0: 1920x1200, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (std, vt100 emulation) Is there a solution? Thanks for your help. -- Alexis de BRUYN
Re: Favorite configuration and system replication tools?
Andreas Kähäri writes:
i'm not sure why you're addressing this to me, as i'm not the
OP.
It's addressed to the thread in general.
Your response quoted me, then made use of the word 'you'. Which
you - and yes, i mean you, Andreas, specifically - have again done
below:
That said, yes, minimising the extent to which certain
non-'word'
characters
(i.e. roughly the POSIX 'alnum' class as described in
re_format(7))
_can_
make it easier to programatically do certain tasks which are
restricted by
the long and messy history of C and Unix development. Given
that
i've been
using computers for a few decades, i still instinctively don't
use
spaces in
filenames, even though they're very much allowed. But of
course,
that's not
what most of the world does, and this is an example of trying
to
work out
what the best tradeoffs might be when dealing with the
messiness of
the real
world.
Alexis.
With rsync(1):
rsync -n -aim --delete-excluded \
--include-from=list \
--include='*/' \
--exclude='*' \
source/ target
This would read your inclusion patterns from the file "list" (it
is
assumed that directories are entered as "dirname/***", which
matches the
name "directory" and all its content), include any directory,
and then
finaly exclude anything not already included. The matched names
would
be synchonised from beneath "source" to "target", and excluded
names
would be deleted from the target. With "-m", we don't keep
directories
at the target that ends up being empty.
You - by which i mean, you, Andreas, specifically - have quoted me
_at length_, in an email with _my email address_ in the To header,
before immediately making remarks not related to the text of mine
you quoted (which was instead related to the `-r` option to `read`
in the context of processing filenames, and which Страхиња has
addressed to my satisfaction).
If you - by which i mean, you, Andreas, specifically - want to use
'you' in the general sense of 'one' ("This would read one's
inclusions patterns ..."), which is certainly fair enough, then
please don't quote unrelated text _from me_ when doing so. If, for
some bizarre reason, your mail client prevents the removal of
unrelated quotes from others, use a better mail client.
In any case, from this point forward, please do not include my
email address in the delivery-related headers of any further
replies to this thread.
Alexis.
Re: Favorite configuration and system replication tools?
Andreas Kähäri writes: The external env(1) utility will only ever list environment variables. The IFS variable does not need to be exported as an environment variable as it's only ever used by the current shell (and any new shell would reset it). To list all variables in a shell, use the built-in set utility without any arguments. $ (unset -v IFS; ksh -c 'set' | grep -A 1 IFS) IFS=' ' $ (unset -v IFS; ksh -c 'printf "%s" "$IFS" | hexdump -C') 20 09 0a | ..| 0003 i stand corrected. Alexis.
Re: Favorite configuration and system replication tools?
Страхиња Радић writes: Дана 24/05/12 07:31PM, Alexis написа: Omitting -r as a parameter to read would make it interpret backscape sequences, which would make the directory name in the filesystem different than the one command/script operates on, which is most likely undesired (unless the intention is to exploit some bug). Yes, i understood that omitting `-r` would make it interpret escape sequences, hence me asking: about the possibility of someone having consciously put e.g. a \t in a directory name because they were assuming that it _would_ get interpreted when required? So i take your answer as, in reference a comment in the other subthread: yes, there are in fact 'inappropriate' characters, in the sense that certain representations of certain characters aren't allowed. Which seems very reasonable to me. Thanks for explaining. Alexis.
Re: Favorite configuration and system replication tools?
Andreas Kähäri writes: Well, that's one way to control this trainwreck of a script; just say that any name containing "inappropriate" characters aren't allowed! May I ask why you don't simply use rsync(1) (or even openrsync(1) from the OpenBSD base system)? i'm not sure why you're addressing this to me, as i'm not the OP. That said, yes, minimising the extent to which certain non-'word' characters (i.e. roughly the POSIX 'alnum' class as described in re_format(7)) _can_ make it easier to programatically do certain tasks which are restricted by the long and messy history of C and Unix development. Given that i've been using computers for a few decades, i still instinctively don't use spaces in filenames, even though they're very much allowed. But of course, that's not what most of the world does, and this is an example of trying to work out what the best tradeoffs might be when dealing with the messiness of the real world. Alexis.
Re: Favorite configuration and system replication tools?
Andreas Kähäri writes: The ksh(1) shell sets IFS by default to a space, tab and a newline character. Those are the defaults used when IFS is not set _as a variable_. If you log in, and run env(1), in the absence of any manual setting of IFS in .kshrc or whatever, you'll see that IFS is not listed, because it's not 'set' in the shell variable sense. When it's not set, the shell assumes that IFS has the value you listed. (Additionally, a shell variable not being set is _not_ the same as that variable being set to the empty string.) Alexis.
Re: Favorite configuration and system replication tools?
Страхиња Радић writes:
When `while ... read ...` idiom is used, it is advisable to
clear IFS
to turn off field splitting
*nod* Fair point; it's not set by default, so i didn't think to
note that any manual setting of it should be overridden for this.
and use -r to avoid interpretation of backslash sequences in the
input:
i wondered about that in this context. If people putting odd /
inappropriate things in directory names are a concern ("weird
characters", as you wrote upthread), what do we do about the
possibility of someone having consciously put e.g. a \t in a
directory name because they were assuming that it _would_ get
interpreted when required?
Alexis.
Re: Favorite configuration and system replication tools?
Страхиња Радић writes: Lapsus: the variable dirs should not be quoted here if it contains more than one directory to be passed to find. It is vulnerable to directory names containing spaces and weird characters, however. So: cd "$target" && find $dirs | sort | uniq > "$target_list" To deal with spaces etc., one could possibly use something along the lines of the following kludge; it assumes that \n is relatively unlikely to be found in a directory name, and that the directories in $dirs can be separated by \n. cd "$target" && echo "$(echo $dirs | while read dir do find $dir done)\n" | sort | uniq > "$target_list" Alexis.
Re: Kernel debugging
Daniel Hejduk writes: Is there any way to build the kernel on Linux preferably Arch Linux? In a VM, sure. Otherwise, no. Here's a comment from a thread about this topic, from a couple of years ago: https://www.reddit.com/r/openbsd/comments/r6wj3c/comment/hmwhk4a/ Alexis.
Re: Fwd: bad first impression of OpenBSD at install time
Katherine Mcmillan writes: Hi Harald, I am compiling a qualitative list of experiences of those who have requested help from various user groups who/which have been rejected or ignored, to try to find similarities between the approaches used by the poster; a grounded theory methodology. Would it be okay if I included yours? Thank you for considering, Katie Hi Katherine, As someone who's been participating in multiple online tech fora for well over two decades, i'd like to make some comments, based on my own experiences. Some common problematic approaches taken by posters include: * Not demonstrating any awareness of group rules or culture. In the case of OpenBSD, the 'netiquette' for the mailing lists is laid out at https://www.openbsd.org/mail.html; each point is explained with a rationale. One thing not mentioned there is top-posting, which is common outside tech communities, but often frowned upon within tech communities. 'Top-posting' involves adding one's reply _before_ the message one is replying to, rather than _after_. There are a few reasons this is discouraged in tech contexts; one is that top-posting not only removes potentially important context, but often results in important questions not being answered. Many of those seeking help don't answer questions that they've been asked - questions that have been asked in order to diagnose what the problem might be. Top-posting seems to exacerbate this phenomenon, and it can be exhausting to try to help someone, only to find it's like pulling teeth. * Treating volunteer communities as though they consist of paid staff. OpenBSD is primarily a volunteer effort - the developers/maintainers, the documenters, the people trying to help out on the mailing lists. Yet people regularly interact with the OpenBSD community (and other volunteer-based tech communities) as though we're a business offering a product seeking 'market share' - and in a number of cases, act as though they're entitled to the sort of support one would might associate with a _paid_ support contract. But OpenBSD is developed/maintained _for the developers/maintainers themselves_, even if it's nonetheless made available for others who might also find it useful. * Assuming that "lack of response" must mean "being ignored" (often in a way that implies that the user feels entitled to others' volunteer time). There's a general phenomenon called "Warnock's dilemma": "Warnock's dilemma, named for its originator Bryan Warnock, is the problem of interpreting a lack of response to a posting in a virtual community. The term originally referred to mailing list discussions, but has been applied to Usenet posts, blogs, web forums, and online content in general. The dilemma arises because a lack of response does not necessarily imply that no one is interested in the topic, but could also mean for example that readers find the content to be exceptionally good (leaving nothing for commenters to add.)" -- https://en.wikipedia.org/wiki/Warnock's_dilemma In the specific case of people asking for help, people will usually not answer with "Hmm, I don't know", just for the sake of answering - that would flood the group with useless messages. Additionally, however, there are common behaviours that can result in volunteers not feeling inclined to put in the effort to help someone, which are described on the "I downvoted because ..." site: https://idownvotedbecau.se/ Hope that helps - please feel free to contact me off-list with any followup questions. Alexis.
Re: syntax error in httpd.conf file
"Peter N. M. Hansteen" writes: Here's the story of my asking it to write a PF.conf - https://nxdomain.no/~peter/chatgpt_writes_pf.conf.html or with nicer formatting and trackers https://bsdly.blogspot.com/2023/06/i-asked-chatgpt-to-write-pfconf-to-spec.html so in this context, near totally useless, likely due to insufficient volume of actually useful configurations in the data it was trained on. Yes, i was thinking that might be one reason ChatGPT is, mm, 'not great', in terms of OpenBSD content. Another reason might be that, since only the two most recent OpenBSD releases are supported, there can be changes in the base system which result in e.g. tutorials becoming out-of-date more quickly. Which is, of course, why the first port of call should always be the man pages and the FAQ. :-) Still, even on topics where there's ample information available, 'AI' can get it very wrong, as in the case of an AI-generated article on CNET about compound interest: https://gizmodo.com/cnet-ai-chatgpt-news-robot-1849996151 But hey, it doesn't really matter whether factual information is or isn't available: just make up data! "ChatGPT Created a Fake Dataset With Skewed Results - Findings raise concerns about the ease of generating false medical evidence", https://www.medpagetoday.com/special-reports/features/107247 Finally, there's a paper relevant to many OpenBSD user's interests: "Do Users Write More Insecure Code with AI Assistants?", https://arxiv.org/abs/2211.03622. Overall, we find that participants who had access to an AI assistant based on OpenAI's codex-davinci-002 model wrote significantly less secure code than those without access. Additionally, participants with access to an AI assistant were more likely to believe they wrote secure code than those without access to the AI assistant. Furthermore, we find that participants who trusted the AI less and engaged more with the language and format of their prompts (e.g. re-phrasing, adjusting temperature) provided code with fewer security vulnerabilities. Alexis.
Re: syntax error in httpd.conf file
"Luca Leone" writes: thanks Alexis for pointing me to the right resources! Actually I did a search in the man pages, but I searched for "httpd" which gave me the page for httpd, and rightly so, page that was not useful for my problem. I *didn't *search for "httpd.conf", which would have been much more useful. Ah, well, what you can do is use apropos(1): $ apropos httpd httpd.conf(5) - HTTP daemon configuration file httpd(8) - HTTP daemon And because the man pages of OpenBSD are written in mdoc(7), which uses semantic markup (unlike man(7), used for Linux man pages, which is mostly presentational markup), you can do things like search for man pages which reference the `httpd` man page: $ apropos -k 'Xr=httpd' acme-client(1) - ACME client httpd.conf(5) - HTTP daemon configuration file hier(7) - layout of filesystems patterns(7) - Lua's pattern matching rules bgplg(8) - looking glass for the OpenBSD Border Gateway Protocol daemon bgplgd(8) - a bgpctl FastCGI server httpd(8) - HTTP daemon intro(8) - introduction to system maintenance and operation commands ocspcheck(8) - check a certificate for validity against its OCSP responder slowcgi(8) - a FastCGI to CGI wrapper server ssl(8) - details for libssl and libcrypto tcpdrop(8) - drop a TCP connection where `Xr` is the mdoc(7) 'cross-reference' macro. Alexis.
Re: syntax error in httpd.conf file
"Luca Leone" writes: I could not find much online on how to write these two guys: httpd.conf and relayd.conf On OpenBSD, the first places to check for documentation are: * the man(ual) pages, which can be accessed from the command line, e.g. $ man httpd.conf $ man relayd.conf but which can also be accessed online: https://man.openbsd.org/httpd.conf.5 https://man.openbsd.org/relayd.conf.5 * and the FAQ: https://www.openbsd.org/faq/ and a bit surprinsigly - at least to me - chatgpt didn't get the syntax right either, no matter how detailed my prompt was. Not at all surprising to me, given that ChatGPT and other LLM-based 'AI' systems - essentially Markov chains / glorified autocorrect - are increasingly known for 'hallucinations' and confidently making false claims. i have a boatload of links about this stuff, but here are a couple of examples: * ChatGPT claims that the _whistleblower_ of a bribery scandal was a guilty party: https://www.abc.net.au/news/2023-04-06/hepburn-mayor-flags-legal-action-over-false-chatgpt-claims/102195610 * Meta Chatbot claims to have a child in school: https://www.abc.net.au/news/2024-04-19/meta-releases-llama-3-ai-model/103744538 Alexis.
Re: Ping blocked by firewall
Karel Lucas writes: Ping only works partially. For example, this works: ping -c 10 195.121.1.34. But this doesn't work: ping -c 10 www.apple.com. I suspect this has to do with DNS servers, but I don't know where to start troubleshooting. Indeed, you appear to have no rules allowing outgoing requests to DNS servers for name resolution. Alexis.
Re: 7.5 /var/log/messages - vfprintf %s NULL in "%.*s"
"Why 42? The lists account." writes: Tumbler is something to do with D-Bus and is also a required package by/for XFCE. Yeah, Tumbler / tumblerd is a service, accessible via D-Bus, that generates thumbnails for files, e.g. in ~/.cache/thumbnails or equivalent. (But i'm not an XFCE user myself.) Alexis.
Re: lcamtuf on the recent xz debacle
Katherine Mcmillan writes: I have seen the following comment, or similar, in several articles now: "On Friday, a lone Microsoft developer rocked the world when he revealed a backdoor<https://arstechnica.com/security/2024/03/backdoor-found-in-widely-used-linux-utility-breaks-encrypted-ssh-connections/> had been intentionally planted in xz Utils, an open source data compression utility available on almost all installations of Linux and other Unix-like operating systems." https://arstechnica.com/security/2024/04/what-we-know-about-the-xz-utils-backdoor-that-almost-infected-the-world/ There are a couple of problems with this statement, but I just want to focus in on the "almost all installations of Linux and other Unix-like operating systems" part. From my understanding, it is certainly almost all installations of Linux, but the "and other Unix-like operating systems" doesn't seem founded. From what I understand, this backdoor would not affect any flavour of *BSD, or of illumos for that matter (ex. smartOS), or QNX, or Solaris. Just for clarity, does anyone know what "Unix-like operating systems" would be affected by this? The quoted passage states the platforms on which xz-utils is available; it doesn't explicitly say that all of those platforms are affected by this specific backdoor (though i acknowledge the passage can be read in a way that implies that). Indeed, not even all Linux platforms are affected: the backdoor specifically targets RPM- and DEB-based systems. In addition to the detailed writeup in Christian's message, there's also one by Russ Cox: https://research.swtch.com/xz-script (Who has also put together a timeline: https://research.swtch.com/xz-timeline) However, even though _this _particular backdoor_ only affects (a subset of) Linux platforms, there's the broader concern that the _project_ was 'socially' backdoored - a project involving a piece of software that's available for a wide variety of platforms, and relatively deep in a number of stacks. (Although, on the technical side, the versions of xz-utils since the malfeasant got involved, but prior to the confirmed-backdoored versions, are being looked at carefully.) Alexis.
Re: securelevel=2 and mount hardening
Dan writes: I'm curious John Doe.. you said cloud but not firewall, and cattle but not pets, right? As with a number of your posts, i'm not clear on what you're saying or asking, but for those wondering, here's an explanation of "cattle vs pets" in the context of computing infrastructure: https://www.copado.com/resources/blog/pets-vs-cattle-more-than-an-analogy-for-modern-infrastructures Alexis.
Re: Unable to get ip6 address
Hari writes: I have uses mtw wifi firmware. Stuart asked you to provide dmesg output. dmesg output provides more information than simply the name of the firmware: it often provides information like version and revision numbers, as well as warnings and errors regarding the hardware. Some years ago, setting up Linux on a laptop, the dmesg showed why wifi wasn't working: rtw_8821ce :01:00.0: enabling device ( -> 0003) rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 rtw_8821ce :01:00.0: rfe 4 isn't supported rtw_8821ce :01:00.0: failed to setup chip efuse info rtw_8821ce :01:00.0: failed to setup chip information In general, when people ask for specific information as part of trying to help someone solve a problem, we're typically doing so for specific reasons, based on knowledge and experience, which might not be immediately apparent to the person asking for help. Personally, if someone i'm trying to help keeps not providing the specific information i'm asking for, i'll stop wasting my time, and just walk away from the discussion. Alexis.
Re: [TUHS] Re: SunOS 4 in 2024
Sorry for accidentally sending this here, rather than to the TUHS list. :-/ Alexis writes: [snip]
Re: [TUHS] Re: SunOS 4 in 2024
Henry Bent writes: Now, I find that there is a fragmentation happening. There are those of us who still cling to mailing lists - like this one! - and those who are willing to navigate the realms of increasingly compartmentalized other forms of community, Discord included. The fact that there is not a recognized central repository of unpaid support for a product, like sun-managers, I find to be frustrating. i basically agree. i won't dwell on this too much further because i recognise that i'm going off-topic, list-wise, but: i think part of the problem is related to different people having different preferences around the interfaces they want/need for discussions. What's happened is that - for reasons i feel are typically due to a lock-in-oriented business model - many discussion systems don't provide different interfaces/'views' to the same underlying discussions. Which results in one community on platform X, another community on platform Y, another community on platform Z Whereas, for example, the 'Rocksolid Light' BBS/forum software provides a Web-based interface to an underlying NNTP-based system, such that people can use their NNTP clients to engage in forum discussions. i wish this sort of approach was more common. Alexis.
Re: files are going missing
Michael Hekeler writes:
Am 11.03.24 19:04 schrieb beecdadd...@danwin1210.de:
I'm not stupid, of course I know about -o
Am 11.03.24 18:37 schrieb beecdadd...@danwin1210.de:
...why still ask redundant question?
isn't this a rather strange way of communicating for someone who
is
looking for help ;-) ??
Indeed. :-) Having spent a lot of time over the years trying to
help people with tech stuff, i'm going to soapbox for a bit:
Part of the issue can be that, at the point someone is asking for
help on a public forum, they might well have spent quite some time
working on the problem, and so are quite frustrated. However, they
might not be aware that it's very common for people to spend
little time trying to solve the problem on their own (e.g. by
*gasp* reading the man pages or other documentation) before
resorting to public forums, which many of us can find frustrating
ourselves (particularly those of us who spend quite a bit of time
working on documentation).
On top of all this, many people asking for help don't understand
that those who are trying to help are often trying to methodically
rule out certain possible causes of the problem, and to reduce the
number of 'moving parts' that need to be taken into consideration.
OP (and others), please note the above, and also take time to read
e.g. https://idownvotedbecau.se/, which lists a number of common
issues with how people ask for tech help. Help us help you. And be
sure to check your configs for typos (e.g. via the `-n` flag on
programs like smtpd(8)):
< nutbar> [root@linux!/usr/src/bind] grep "{" named.conf.newer |
wc -l
< nutbar> 19314
< nutbar> [root@linux!/usr/src/bind] grep "}" named.conf.newer |
wc -l
< nutbar> 19313
-- http://bash.org/?7748
:-)
Alexis.
Re: httpd location question
Michael Hekeler writes: Is there any directive or regex for the 'location' directive, httpd doesn't support regular expressions. httpd includes lua pattern support. see patterns(7) (Though to use patterns(7) syntax, one needs to use the 'match' keyword, e.g. "location match" rather than just "location". In the latter case, shell globbing rules are used.) Alexis.
Re: No packages found for 7.5 snapshot on arm64
Dmitry Matveyev writes: 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 Refer to "OpenBSD -current drops -beta tag, goes to 7.5", https://www.undeadly.org/cgi?action=article;sid=20240301064504: For upgrades to work correctly, you will need to run sysupgrade(8) with the -s flag and upgrade your installed packages by running pkg_add(1) with -D snap in addition to your usual options Alexis.
Re: browser titlebar doesn't support emoji
Dan writes: Just adding a little feedback more about dealing with emoji flags coding on my station: Claws Mail*: doesn't help a lot, blank with auto encoding or a difficult hex representation with unicode; anyway it depends on a general font set in its preferences. gedit*: depend on the general font of the editor. NetBeans: depends on the fonts for the single portions of text set its preferences. nano: display an easy bold "IT" at the place of the flag. [my] RADXIDE (tcl/tk): display an easy bold "IT" like nano behavior. vi: display a difficult hex representation of the emoji. * depending on one general font for text, often a monospaced one, they will have no luck to display emoji anyway. [A comment i posted in another forum recently, links extracted:] In Unicode, what is visually a single 'character' / 'grapheme' is not necessarily a single Unicode code point. For example, different skin tones of face emoji can be created by combining a specific face emoji with an emoji modifier sequence: https://emojipedia.org/emoji-modifier-sequence Similarly, what appears as a single flag emoji is actually the result of combining two 'regional indicator symbols', which together a two-letter country code, the official flag for which can then be rendered as a single character - as long as the software does so. If you go to the Emojipedia page for flags: https://emojipedia.org/flags you'll see that the alt / hover / mouseover text for various flags says things like "The flag for Australia, which may show as the letters AU on some platforms". This was the outcome of the Unicode Consortium trying to get involved in various political debates about which flags "should" and/or "shouldn't" be included. More details on Wikipedia: https://en.wikipedia.org/wiki/Regional_indicator_symbol Thus, the issue is that some of the software you're using doesn't 'know' that certain Unicode sequences need to be represented on-screen as a 'flag'. Alexis.
Re: as cannot do endbr64 instructions (too old)
"Lorenz (xha)" writes: On Mon, Jan 01, 2024 at 08:47:07PM +1100, Alexis wrote: "Lorenz (xha)" writes: > just out of couriosity, why is "as" in the base system if it > is > outdated and is updating it an option? i presume it's due to subsequent versions being licensed under later versions of the GPL, but i'd be happy to be corrected on this point. i couldn't find any discussions on why the later versions are not acceptable in the base system. are there any? There's a discussion about GPL software in base at https://www.openbsd.org/policy.html, although it doesn't mention GPL versions: The GNU Public License and licenses modeled on it impose the restriction that source code must be distributed or made available for all works that are derivatives of the GNU copyrighted code. While this may superficially look like a noble strategy, it is a condition that is typically unacceptable for commercial use of software. So in practice, it usually ends up hindering free sharing and reuse of code and ideas rather than encouraging it. As a consequence, no additional software bound by the GPL terms will be considered for inclusion into the OpenBSD base system. For historical reasons, the OpenBSD base system still includes the following GPL-licensed components: the GNU compiler collection (GCC) with supporting binutils and libraries, GNU CVS, GNU texinfo, the mkhybrid file system creation tool, and the readline library. Replacement by equivalent, more freely licensed tools is a long-term desideratum. But, again, someone else will have to describe what's happening with 'as' specifically; i'm not an OpenBSD dev myself. My speculation about the GPL version potentially being involved comes from Apple not including versions of software whose license had been changed from GPL2 to GPL3 (such that e.g. versions of macOS prior to Catalina only included GNU Emacs 22). Alexis.
Re: as cannot do endbr64 instructions (too old)
"Lorenz (xha)" writes: just out of couriosity, why is "as" in the base system if it is outdated and is updating it an option? i presume it's due to subsequent versions being licensed under later versions of the GPL, but i'd be happy to be corrected on this point. Alexis.
Re: self-hosted man.openbsd.org script?
Mihai Popescu writes: [ removed elaborate instruction about going html from almost txt with man pages ] All this to jump in html boat? Or I got it wrong? Are old man pages deprecated? It can be convenient to have Web-based access to the man pages for systems or software that one isn't currently using (or that isn't already installed). Gentoo is my daily driver, and as it turns out, the OpenBSD man pages are available as a package in the GURU repo, so i have that package installed to allow me to read those man pages on my Gentoo box: $ man cat will get me the man page for GNU coreutils 'cat', but: $ man 1bsd cat will get me the man page for OpenBSD's 'cat'. In the absence of such packaging, a Web-based UI for reading the man pages of other systems can be really helpful (e.g. for checking what functionality is and isn't implemented in a given system's implementation of a particular program, for portability reasons). Alexis.
Re: self-hosted man.openbsd.org script?
Paul Pace writes: I have this vague memory of reading someone who posted a script, IIRC, to convert the system's man pages to HTML, or similar, into somewhere under /var/www and the pages worked just like the highly useful man.openbsd.org, and not like the plain text pages that everyone always posts to their websites. Does someone happen to know where that is? Not sure if this is what you were specifically thinking of, but there's man.cgi(8): https://mandoc.bsd.lv/man/man.cgi.8.html Alexis.
Re: Firefox and DPMS
Ricky Cintron writes: I was hoping to see if others have experienced the same behavior, if anyone can confirm my assumption about WMs/DEs, and if there's a better way to deal with it. https://bugzilla.mozilla.org/show_bug.cgi?id=1766064
Re: Reference/Citation Manager -- Zotero or JabRef? (+ compilation of Zotero?)
"Stephan, Corey J" writes: What are academics and others who require citation management using in OpenBSD nowadays? i'm not an academic myself - merely engaged with academia - but i'd be interested to know the extent to which people are making use of refer(1). i've only started working in the roff ecosystem in recent years, having spent more time in the LaTeX world, and i've been increasingly appreciating it. Alexis.
Re: Wayland
"Daniele B." writes: I see you are talking about X server in other threads and apart its bugs and security, absolutly in terms of num of clients.. I came in my mind with a curiousity that is passing by from a while and sorry if it is disregarding the "archive": What is the porting / development status of Wayland in OpenBSD? This Reddit thread has a discussion of Wayland and OpenBSD's privsep'd Xenocara: https://www.reddit.com/r/openbsd/comments/ys6bbx/linux_user_here_bsd_caught_my_attention_and_i/ Alexis.
Re: syslogd program logging
Steven Shockley writes: My isc_dhcpd logs are kind of chatty, and I'd like to send them to their own log. I tried appending the following to syslogd.conf: !dhcpd *.* /var/log/dhcpd This works, but the dhcpd messages still appear in /var/log/daemon as well. Shouldn't this actually be: !!dhcpd *.*/var/log/dhcpd !* at the start of the file? At least, that's my reading of syslog.conf(5): the two exclamation marks will cause a match on 'dhcpd' to _only_ result in the listed action (with no further evaluation of the file, and thus no further opportunities for logging to be done), and the '!*' means that further evaluation will happen if there _isn't_ such a match. Alexis.
Re: Weirdness with du/df/my brain (latter more likely)
Steve Fairhead writes: - Old machine: 49 GB - New machine: 188 GB Figures as measured with du -sk, which I realise is sector-oriented, but still... And yes, my boss does a *lot* of email. i might well be barking up the wrong tree, but the first thing that comes to mind is inode usage. OpenBSD du(1) doesn't appear to have an inode-related option, but df(1) does; what numbers does `df -i` report in each case? Alexis.
Re: iridium/chromium webcam access
Robert Alessi writes: I am beginning to think that this issue may not be related to iridium or chromium because other browsers on my system fail to access the webcam, such as qutebrowser or otter-browser, while firefox always succeeds. There must be a common link between those browsers. Blink/QtWebEngine? Alexis.
Re: Documentation of wsconsctl keyboard.map format?
Vlad Meșco writes: Good idea! I may try that. It would be too much to hope for a setting that logs keycodes to some log file or to the console I expect? I mean you could add some printfs or log(9) in `wskbd.c', probably in `wskbd_translate', assuming control flows through there on your setup. I don't know of any utility on OpenBSD that can help here. xev(1)? https://man.openbsd.org/xev.1 Alexis.
Re: Questions about OpenBSD and IRC
Michael G Workman writes: I remember some years there was an IRC channel for openbsd, I think it was on freenode. I just installed hexchat and there is no freenode option anymore, is there still an openbsd irc channel somewhere? Due to events last year: "On 19 May 2021, Freenode underwent what some staff described as a 'hostile takeover' and at least 14 volunteer staff members resigned. Following the events, various organisations using Freenode – including Arch Linux, CentOS, FreeBSD, Free Software Foundation Europe, Gentoo Linux, KDE, LineageOS, Slackware, Ubuntu, and Wikimedia Foundation–moved their channels to Libera Chat, a network created by former Freenode staff." -- https://en.wikipedia.org/wiki/Freenode many FOSS communities have moved from Freenode to libera.chat. There's an #openbsd channel there. Alexis.
Re: doas and args matching
Maksim Rodin writes: $ /sbin/wsconsctl display.brightness=50 wsconsctl: /dev/ttyC0: Permission denied Did you forget to type "doas" before your command? Gah, apparently so. :-/ i try to be thorough when i check these things, but then i do something like this. Thank you. Chris: There you go - as Alexander said, just don't specify any argument to wsconsctl in /etc/doas.conf. Alexis.
Re: doas and args matching
Alexander Hall writes: There's a good chance i'm misunderstanding, but doesn't this run into the same issue? Namely, that (as far as i'm aware) it's not possible to specify that a doas-permitted command be allowed to run with arbitrary arguments (or range of arguments), rather than only the arguments specified in doas.conf? Just leaving out the "args ..." from the config should accomplish that. Not on 7.1, unless i'm doing something wrong? /etc/doas.conf: permit nopass alexis as root cmd /sbin/wsconsctl $ /sbin/wsconsctl display.brightness=50 wsconsctl: /dev/ttyC0: Permission denied Hence the OP's question, and my suggested kludge. Alexis.
Re: doas and args matching
Alexander Hall writes:
Better yet, the wrapper could be allowed with no argument
restrictions
and just do
wsconsctl "display.brightness=$1"
or even (maybe; untested)
wsconsctl "display.brightness${1%%[!+-]*}=${1#[+-]}"
for moar fanziness.
There's a good chance i'm misunderstanding, but doesn't this run
into the same issue? Namely, that (as far as i'm aware) it's not
possible to specify that a doas-permitted command be allowed to
run with arbitrary arguments (or range of arguments), rather than
only the arguments specified in doas.conf?
Alexis.
Re: doas and args matching
Chris Narkiewicz writes:
Is it possible to match command arguments against an expression
in
doas.conf?
I'd like to allow user to run wsconsctl
display.brightness=<0-100> and
the only solution i found so far is to explicitly put all values
in
doas.conf.
Since no-one has yet offered any better suggestions: perhaps you
could write a wrapper script that can be called without arguments,
and instead takes the brightness value from stdin? E.g. something
like:
$ echo 50 | doas /usr/local/bin/my-wrapper
where my-wrapper is something like:
#!/bin/ksh
IFS=
read -u VAL
wsconsctl display.brightness=${VAL}
(Obviously the script should check that VAL is an appropriate
value.)
Alexis.
Re: Atom code environment
jeanfrancois writes: Specifically the multiline work is very helpful that ought to be enough. Have I missed other editors with this ? There are extensions for both Vim and Emacs for this, e.g.: https://github.com/mg979/vim-visual-multi https://github.com/magnars/multiple-cursors.el Alexis.
Re: Another kernel fault incident on a Vultr OpenBSD VM
Mihai Popescu writes: It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. Not sure exactly what you mean by that, but i can say i'm very happy with my OpenBSD VM provided by openbsd.amsterdam. Alexis.
Re: /bsd: thread: table is full
On 14/02/2022 17:19, Stuart Henderson wrote: On 2022-02-14, Alexis de BRUYN wrote: Hello Everybody, Since I have updated my -current deskop this morning (sysupgrade & pkg_add), the whole box seems slower, I have a lot of application crashes and I see this message a lot in /var/log/messages : "/bsd: thread: table is full". Nothing changes in my habits, I still use the same applications (terms, thunderbird, firefox, chrome, iridium, ...), heavily. I have tried to increase progressively some values in sysctl.conf and login.conf but even with theses high attempts, I still have the same issues. kern.maxproc=8192 kern.maxfiles=10240 $ sysctl kern.nfiles kern.nfiles=1960 How about kern.maxthread ? (You can see how many are currently used in kern.nthreads). Indeed it was my problem. Thanks a lot Stuart for your help! -- Alexis de BRUYN
/bsd: thread: table is full
Hello Everybody, Since I have updated my -current deskop this morning (sysupgrade & pkg_add), the whole box seems slower, I have a lot of application crashes and I see this message a lot in /var/log/messages : "/bsd: thread: table is full". Nothing changes in my habits, I still use the same applications (terms, thunderbird, firefox, chrome, iridium, ...), heavily. I have tried to increase progressively some values in sysctl.conf and login.conf but even with theses high attempts, I still have the same issues. kern.maxproc=8192 kern.maxfiles=10240 $ sysctl kern.nfiles kern.nfiles=1960 $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) 8388608 file size (blocks, -f) unlimited max locked memory (kbytes, -l) 10820926 max memory size (kbytes, -m) 32457356 open files (-n) 10240 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 8192 virtual memory (kbytes, -v) 8396800 What can I change ? Thanks for your help, Alexis. OpenBSD 7.0-current (GENERIC.MP) #335: Sun Feb 13 16:41:43 MST 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34298658816 (32709MB) avail mem = 33241968640 (31702MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb510 (78 entries) bios0: vendor American Megatrends Inc. version "1.12" date 05/14/2013 bios0: Shuttle Inc. SZ77 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! MCFG SLIC HPET SSDT SSDT SSDT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(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-3770K CPU @ 3.50GHz, 3492.58 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 MHz, 06-3a-09 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,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 MHz, 06-3a-09 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0
Re: Install latest package without prompts on OpenBSD 7.0
Jeffrey Walton writes: How do I tell pkg_add to install the latest version without prompting me? Proof-of-concept wrapper script, written in Perl: https://gist.github.com/flexibeast/816610233ebbb3745ec43852a96b9248 Alexis.
Re: Doku Wiki femail?
latin...@vcn.bc.ca writes: i did an installation of dokuwiki over OBSD 7.0, but i am not bring able to configure femail! i am following this: | Running femail-chroot on OpenBSD +--- Setup with httpd from OpenBSD base system = By default, femail will use `localhost' for smtphost. httpd(8) inside the chroot(2) will NOT be able to use the system /etc/hosts or /etc/resolv.conf. One will need to populate /var/www/etc/hosts and/or /var/www/etc/resolv.conf in the chroot(2) environment. Additionally, one may create a custom femail.conf; see femail(8). If you're using femail with PHP inside a chroot jail, be aware that PHP's built-in "mail" function uses popen(), which requires /bin/sh. I have tried different ways without success. Can somebody help please? dokuwiki works correctly in general, exept femail. Do you actually have a properly-configured SMTP server running and listening as part of your setup? Your email doesn't say. Alexis.
Re: How to use macros in acme-client.conf?
Stuart Henderson writes:
In gmane.os.openbsd.misc, you wrote:
I'm trying to use macros in my acme-client.conf, but it seems I
cannot
get the syntax right. In addition to that, even when I try the
example
from the acme-client.conf(5):
api_url="https://acme-v02.api.letsencrypt.org/directory";
authority letsencrypt {
api url $api_url
account key "/etc/acme/letsencrypt-privkey.pem"
}
It fails with a syntax error:
$ ./acme-client -vvv -f ../test.conf
api_url = "https://acme-v02.api.letsencrypt.org/directory";
../test.conf:3: syntax error
Are spaces around the '=' permitted? i thought they weren't. The
example in acme-client.conf(5) man page certainly doesn't have
them.
Alexis.
Re: How can I contribute code to openbad
cc writes: I recently started to study openbsd. I am a computer major student. How can I contribute to openbsd? See the FAQ: https://www.openbsd.org/faq/faq1.html#Support Alexis.
Re: How to clear the screen correctly in ksh
Joseph Mayer writes: As far as I am aware, since about 6 months ksh clears the screen on ctrl+L by default, no bind is needed anymore? You're right; it's specifically stated in the Changelog for 6.5: https://www.openbsd.org/plus65.html which apparently i didn't read closely enough. :-/ Alexis.
Re: How to clear the screen correctly in ksh
Максим writes: In bash I can press Ctrl-l to clear the screen. In ksh this key combination does not work. I can clear the screen only using the command "clear". How can I do this using hotkeys in ksh? i have this in my .kshrc: bind -m '^L=^Uclear^J^Y' Alexis.
Re: phonetic alphabet on OpenBSD
Chris Bennett writes: Is there any information out there to help actually learn the sounds? I couldn't find anything and I don't want to take classes. https://en.wikipedia.org/wiki/Help:IPA
Re: Selling things through the mailing list allowed? I have compatible THIN CLIENTS for Firewall / Router appliance use Available
Jon Tabor writes: Yep, right there with ya. So, ah...what's everyone using for mail filtering these days? Spamassassin? ClamAV? Something else entirely? i use maildrop: http://www.courier-mta.org/maildrop/ Alexis.
Re: risc-v
flipchan writes: I love risc-v ! But has risc-v started producing on real hardware and not kvm/qemu ? Yes; cf. e.g. https://riscv.org/risc-v-cores/#fe310-g000 which is used for the HiFive1 Arduino board. Alexis.
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Dear all, I tried to run OpenBSD 6.2 on Debian GNU/Linux 9.2 and qemu-kvm 2.8 no issue so far too. Proxmox is using Debian GNU/Linux as the core OS. Next step will be to use the same version of qemu-kvm that Proxmox 5.0 ship by default. Regards, On 12/10/2017 13:38, Scott Reese wrote: On 8 Oct 2017, at 23:59, Oliver Marugg wrote: Thanks Mike, will do so. The proxmox guys have also the idea that it could be a bug in kvm hypervisor (which is the hypervisor part for proxmox) and will affect OpenBSD since 4.9, they wrote me in their public forum. As far as I understood they do not know what OpenBSD needs in kvm or what/where should be fixed in kvm run OpenBSD without that freezes. -oliver I have to correct my previous post "...will affect OpenBSD since 4.9" was nonsense and sorry for this noise. Proxmox guys said it will affect OpenBSD guests under KVM with Linux kernels starting from 4.9 on, I only saw wrong version numbers. Currently running tests with OpenBSD 6.2-release and 6.2-stable guests in proxmox/kvm, but it seems there is no change with freezes to OpenBSD 6.1. Greetings: Just a data point for you: I run about a dozen OpenBSD VMs, versions 6.0, 6.1, and 6.2 under KVM on Linux kernel 4.11 without any of the issues that you are describing. The host system is running Fedora 25, the kernel version is 4.11.3, and the qemu-kvm package version is 2.7.1-7. If there's any information I can provide, please let me know. -Scott
Re: iwn0: no link after 6.1 upgrade
On 08/19/17 16:16, Stefan Sperling wrote: On Sat, Aug 19, 2017 at 03:51:32PM +0200, Alexis de BRUYN wrote: Yes, I have double-checked, this is what is shown in the Web GUI. "Authentication PassPhrase Settings" : "WPA-Personal" "WPA Mode" : "WPA2 Only" "Cipher Type" : "TKIP" Please set Cipher Type to 'AUTO' or 'AES'. Then it should work. Force AES works. I will test on other AP. Thanks Stefan. TKIP is used with WPA1 only. -- Alexis de BRUYN
Re: iwn0: no link after 6.1 upgrade
On 08/19/17 15:02, Stefan Sperling wrote: On Sat, Aug 19, 2017 at 02:54:05PM +0200, Alexis de BRUYN wrote: On 08/19/17 11:35, Stefan Sperling wrote: On Sat, Aug 19, 2017 at 11:12:04AM +0200, Alexis de BRUYN wrote: After an 6.1 upgrade (from 6.0-release to 6.1-release) on my Lenovo X230 laptop, I can't get my wireless connection working anywore on different kind of access points or ISP boxes. Same problem on 6.1-current My guess is that your AP is using WPA1. Is this correct? On my DLINK DAP-2310 with the last firmware, the WPA mode is WPA2 Only. I cannot check with other AP today. Are you really sure about that? Yes, I have double-checked, this is what is shown in the Web GUI. "Authentication PassPhrase Settings" : "WPA-Personal" "WPA Mode" : "WPA2 Only" "Cipher Type" : "TKIP" WPA1 has been disabled by default because it is not secure. Make sure your AP is using WPA2 (sometimes called "AES" by vendors). Only if you cannot change the AP, try: ifconfig iwn0 wpaprotos wpa1,wpa2 $ sudo ifconfig iwn0 wpaprotos wpa1,wpa2 $ sh /etc/netstart iwn0 DHCPREQUEST on iwn0 to 255.255.255.255 DHCPREQUEST on iwn0 to 255.255.255.255 DHCPACK from 192.168.0.51 (ec:a8:6b:ff:15:4e) bound to 192.168.0.9 -- renewal in 900 seconds. But not working with $ sudo ifconfig iwn0 wpaprotos wpa2 $ sudo sh /etc/netstart iwn0 iwn0: no link ... sleeping This implies that the AP is using WPA1, no? Yes it seems so. Please also show the output of 'ifconfig iwn0 scan' and show any additional messages produced in /var/log/messages after running 'ifconfig iwn0 debug'. $ sudo ifconfig iwn0 scan iwn0: flags=8843 mtu 1500 lladdr 60:67:20:43:86:aa index 2 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (autoselect mode 11a) status: no network ieee80211: nwid my_ssid wpakey [...] wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp And there were no lines here showing access points? These lines would probably tell us which WPA version is used by your AP, if you had shown them. Yes sorry, there is just mine listed: nwid my_ssid chan 1 bssid 54:b8:0a:39:df:48 -20dBm 54M privacy,short_preamble,short_slottime,wpa2 $ sudo ifconfig iwn0 debug $ tail -f /var/log/messages Aug 19 14:48:29 lt4-alexis /bsd: iwn0: end passive scan Aug 19 14:48:29 lt4-alexis /bsd: - 54:b8:0a:39:df:481! +233 54M ess privacy rsn! "my_ssid" This shows the AP is not being selected because it has the wrong channel (channel 1 when we expected something else, probably cause the scan was currently scanning 11a mode which only supports channels >= 36, nothing to worry about) and the wrong encryption settings (rsn!) (so again, this indicates AP is using WPA1). -- Alexis de BRUYN
Re: iwn0: no link after 6.1 upgrade
On 08/19/17 11:35, Stefan Sperling wrote: On Sat, Aug 19, 2017 at 11:12:04AM +0200, Alexis de BRUYN wrote: After an 6.1 upgrade (from 6.0-release to 6.1-release) on my Lenovo X230 laptop, I can't get my wireless connection working anywore on different kind of access points or ISP boxes. Same problem on 6.1-current My guess is that your AP is using WPA1. Is this correct? On my DLINK DAP-2310 with the last firmware, the WPA mode is WPA2 Only. I cannot check with other AP today. WPA1 has been disabled by default because it is not secure. Make sure your AP is using WPA2 (sometimes called "AES" by vendors). Only if you cannot change the AP, try: ifconfig iwn0 wpaprotos wpa1,wpa2 $ sudo ifconfig iwn0 wpaprotos wpa1,wpa2 $ sh /etc/netstart iwn0 DHCPREQUEST on iwn0 to 255.255.255.255 DHCPREQUEST on iwn0 to 255.255.255.255 DHCPACK from 192.168.0.51 (ec:a8:6b:ff:15:4e) bound to 192.168.0.9 -- renewal in 900 seconds. But not working with $ sudo ifconfig iwn0 wpaprotos wpa2 $ sudo sh /etc/netstart iwn0 iwn0: no link ... sleeping Please also show the output of 'ifconfig iwn0 scan' and show any additional messages produced in /var/log/messages after running 'ifconfig iwn0 debug'. $ sudo ifconfig iwn0 scan iwn0: flags=8843 mtu 1500 lladdr 60:67:20:43:86:aa index 2 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (autoselect mode 11a) status: no network ieee80211: nwid my_ssid wpakey [...] wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp $ sudo ifconfig iwn0 debug $ tail -f /var/log/messages Aug 19 14:48:29 lt4-alexis /bsd: iwn0: end passive scan Aug 19 14:48:29 lt4-alexis /bsd: - 54:b8:0a:39:df:481! +233 54M ess privacy rsn! "my_ssid" -- Alexis de BRUYN
iwn0: no link after 6.1 upgrade
cpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2601, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x768, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) 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 puc0 at pci0 dev 22 function 3 "Intel 7 Series KT" rev 0x04: ports: 1 com com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo com4: probed fifo depth: 0 bytes em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address 3c:97:0e:3c:00:5d ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 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 azalia0 at pci0 dev 27 function 0 "Intel 7 Series HD Audio" rev 0x04: msi azalia0: codecs: Realtek ALC269, Intel/0x2806, using Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 2 sdhc0 at pci1 dev 0 function 0 "Ricoh 5U823 SD/MMC" rev 0x04: apic 2 int 16 sdhc0: SDHC 3.0, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, MIMO 2T2R, MoW, address 60:67:20:43:86:aa ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 4 ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 usb2 at ehci1: USB revision 2.0 uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 pcib0 at pci0 dev 31 function 0 "Intel QM77 LPC" rev 0x04 ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 ahci0: port 0: 6.0Gb/s scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed naa.55cd2e414d26bd18 sd0: 114473MB, 512 bytes/sector, 234441648 sectors, thin ichiic0 at pci0 dev 31 function 3 "Intel 7 Series SMBus" rev 0x04: apic 2 int 18 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-12800 SO-DIMM isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbdprobe: reset response 0x0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 wsmouse1 at pms0 mux 0 pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x940300 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 error: [drm:pid0:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A error: [drm:pid0:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder A FIFO underrun uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2 ugen0 at uhub3 port 4 "Broadcom Corp BCM20702A0" rev 2.00/1.12 addr 3 uhub4 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets sd1 at scsibus3 targ 1 lun 0: SCSI2 0/direct fixed sd1: 114470MB, 512 bytes/sector, 234435953 sectors root on sd1a (d70c277ea78ccc07.a) swap on sd1b dump on sd1b -- Alexis de BRUYN
Re: isakmpd dies quietly with over 100 tunnels
I didn't think it was isakmpd related back then. Maybe a configuration issue on my end or the partner's. But sure we need to post traces. Nonetheless OpenBSD is an amazing piece of software, so thank you ! Regards, Alexis. On 29/05/2017 11:14, Theo de Raadt wrote: Great thing is you all have source code, and can run the same debuggers live in your key-happy situations, and then generate traces to expose the problem so that someone can help you. But, yet, that doesn't happen. Strange isn't it?
Re: isakmpd dies quietly with over 100 tunnels
Hi Michał, I'm having same issue without 100 ipsec tunnels and dedicated hardware. Unfortunately it's a production environment so I can't really troubleshooting this issue to track down the culprit. Anyway maybe it's not related to your issue. Regards, Alexis. On 28/05/2017 14:31, Michał Koc wrote: Hi all, I'm running 6.0/amd64 inside KVM/Quemu with over 100 ipsec tunnels. Everything was running just fine when the number of tunnels was lower. But as we have been setting up more and more tunnels we suddenly run on problems. The isakmpd deaemon keeps dying quietly. Probably I'm running out of something, but I need some help to find out what it is and how to monitor it and tweak. Thank You in advance. Best Regards M.K. root@vgate0:/root# netstat -m 215 mbufs in use: 163 mbufs allocated to data 46 mbufs allocated to packet headers 6 mbufs allocated to socket names and addresses 160/920/6144 mbuf 2048 byte clusters in use (current/peak/max) 0/8/6144 mbuf 4096 byte clusters in use (current/peak/max) 0/8/6144 mbuf 8192 byte clusters in use (current/peak/max) 0/14/6146 mbuf 9216 byte clusters in use (current/peak/max) 0/10/6150 mbuf 12288 byte clusters in use (current/peak/max) 0/8/6144 mbuf 16384 byte clusters in use (current/peak/max) 0/8/6144 mbuf 65536 byte clusters in use (current/peak/max) 2760 Kbytes allocated to network (13% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Sample tail of the log: When I run "isakmpd -K -d -DA=10": 142043.246192 Sdep 10 pf_key_v2_set_spi: satype 2 dst xxx.xxx.xxx.xxx SPI 0x42f03e5d 142043.246209 Timr 10 timer_add_event: event sa_soft_expire(0x1fb9d0bdf400) added before sa_soft_expire(0x1fb9c8f05400), expiration in 25056s 142043.246223 Timr 10 timer_add_event: event sa_hard_expire(0x1fb9d0bdf400) added before sa_soft_expire(0x1fb9dd458200), expiration in 28800s 142043.246326 Sdep 10 pf_key_v2_set_spi: satype 2 dst xxx.xxx.xxx.xxx SPI 0x3ffa5955 142043.268229 Default responder_recv_HASH_SA_NONCE: KEY_EXCH payload without a group desc. attribute 142043.268250 Default dropped message from xxx.xxx.xxx.xxx port 500 due to notification type NO_PROPOSAL_CHOSEN 142043.268281 Timr 10 timer_add_event: event exchange_free_aux(0x1fb9a5336400) added before sa_soft_expire(0x1fba0d6a2a00), expiration in 120s 142043.268289 Exch 10 exchange_establish_p2: 0x1fb9a5336400 policy initiator phase 2 doi 1 exchange 5 step 0 142043.268295 Exch 10 exchange_establish_p2: icookie 8c58f4e7f8269ed3 rcookie 0fe2d7657125a339 142043.268301 Exch 10 exchange_establish_p2: msgid de2c5cc3 sa_list 142043.269079 Timr 10 timer_add_event: event message_send_expire(0x1fb994136900) added before connection_checker(0x1fb9b2646280), expiration in 7s 142043.269614 Exch 10 exchange_finalize: 0x1fb9a5336400 policy> policy initiator phase 2 doi 1 exchange 5 step 1 142043.269630 Exch 10 exchange_finalize: icookie 8c58f4e7f8269ed3 rcookie 0fe2d7657125a339 142043.269637 Exch 10 exchange_finalize: msgid de2c5cc3 sa_list 142043.269653 Timr 10 timer_remove_event: removing event exchange_free_aux(0x1fb9a5336400) 142043.289465 Timr 10 timer_remove_event: removing event message_send_expire(0x1fb994136900) 142043.289513 Exch 10 exchange_finalize: 0x1fb972b59400 from-xxx.xxx.xxx.xxx/24-to-xxx.xxx.xxx.xxx/24 policy responder phase 2 doi 1 exchange 32 step 2 142043.289521 Exch 10 exchange_finalize: icookie 8c58f4e7f8269ed3 rcookie 0fe2d7657125a339 142043.289528 Exch 10 exchange_finalize: msgid de079ef6 sa_list 0x1fb9dd458800 0x1fb985d09e00 142043.289578 Sdep 10 pf_key_v2_set_spi: satype 2 dst xxx.xxx.xxx.xxx SPI 0xe5d04953 142043.289594 Timr 10 timer_add_event: event sa_soft_expire(0x1fb9dd458800) added before sa_soft_expire(0x1fba1d81de00), expiration in 3279s 142043.289608 Timr 10 timer_add_event: event sa_hard_expire(0x1fb9dd458800) added before sa_soft_expire(0x1fba2c980800), expiration in 3600s 142043.289710 Sdep 10 pf_key_v2_set_spi: satype 2 dst xxx.xxx.xxx.xxx SPI 0x4d895568 root@vgate0:/root# OpenBSD 6.0-stable (GENERIC.MP) #0: Sat Feb 4 21:55:17 CET 2017 root@amd64.vcomp:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1056956416 (1007MB) avail mem = 1020506112 (973MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1dc0 (11 entries) bios0: vendor Bochs version "Bochs" date 01/01/2011 bios0: Bochs Bochs acpi0 at bios0: rev 0 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC HPET acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: QEMU Virtual CPU version 2.1.2, 3492.32 MHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT,HV,NXE,LONG,LAHF,ABM cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way
Re: error: [drm:pid10679:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle
On 10/03/16 13:43, Mark Kettenis wrote: This is expected. You should use the "modesetting" driver instead of the "intel" driver. And if you don't have an /etc/X11/xorg.conf file, that would be the default. If you really need an /etc/X11/xorg.conf file, change the driver Thanks Mark, this is now working fine. there. Otherwise, just delete the file. Cheers, Mark -- Alexis de BRUYN
error: [drm:pid10679:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle
use disabled
[22.181] (II) intel(0): HW Cursor enabled
[22.181] (II) intel(0): RandR 1.2 enabled, ignore the following
RandR disabled message.
[22.183] (==) intel(0): DPMS enabled
[22.183] (II) intel(0): [DRI2] Setup complete
[22.183] (II) intel(0): [DRI2] DRI driver: i965
[22.183] (II) intel(0): [DRI2] VDPAU driver: i965
[22.183] (II) intel(0): direct rendering: DRI2 enabled
[22.183] (II) intel(0): hardware support for Present enabled
[22.183] (--) RandR disabled
[22.241] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[22.241] (II) AIGLX: enabled GLX_ARB_create_context
[22.241] (II) AIGLX: enabled GLX_ARB_create_context_profile
[22.241] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[22.241] (II) AIGLX: enabled GLX_INTEL_swap_event
[22.241] (II) AIGLX: enabled GLX_SGI_swap_control and
GLX_MESA_swap_control
[22.241] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[22.241] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[22.241] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[22.241] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
objects
[22.241] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[22.242] (II) AIGLX: Loaded and initialized i965
[22.242] (II) GLX: Initialized DRI2 GL provider for screen 0
[22.248] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using
pipe 0, position (1920, 0), rotation normal, reflection none
[22.273] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using
pipe 1, position (0, 0), rotation normal, reflection none
[22.277] (II) intel(0): Setting screen physical size to 1016 x 285
[22.402] (II) config/wscons: checking input device /dev/wskbd
[22.402] (II) wskbd: using layout fr
[22.402] (II) LoadModule: "kbd"
[22.403] (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.so
[22.404] (II) Module kbd: vendor="X.Org Foundation"
[22.404] compiled for 1.18.4, module version = 1.8.1
[22.404] Module class: X.Org XInput Driver
[22.404] ABI class: X.Org XInput driver, version 22.1
[22.404] (II) Using input driver 'kbd' for '/dev/wskbd'
[22.404] (**) /dev/wskbd: always reports core events
[22.404] (**) /dev/wskbd: always reports core events
[22.404] (**) Option "Protocol" "standard"
[22.404] (**) Option "XkbRules" "base"
[22.404] (**) Option "XkbModel" "pc105"
[22.404] (**) Option "XkbLayout" "fr"
[22.404] (II) XINPUT: Adding extended input device "/dev/wskbd"
(type: KEYBOARD, id 6)
[22.631] (II) config/wscons: checking input device /dev/wsmouse
[22.632] (**) /dev/wsmouse: Applying InputClass "Mouse"
[22.632] (II) LoadModule: "ws"
[22.632] (II) Loading /usr/X11R6/lib/modules/input/ws_drv.so
[22.633] (II) Module ws: vendor="X.Org Foundation"
[22.633] compiled for 1.18.4, module version = 1.3.0
[22.633] Module class: X.Org XInput Driver
[22.633] ABI class: X.Org XInput driver, version 22.1
[22.633] (II) Using input driver 'ws' for '/dev/wsmouse'
[22.633] (**) /dev/wsmouse: always reports core events
[22.633] (II) ws: /dev/wsmouse: debuglevel 0
[22.633] (**) Option "Device" "/dev/wsmouse"
[22.633] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5
[22.633] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7
[22.633] (**) ws: /dev/wsmouse: associated screen: 0
[22.634] (II) ws: /dev/wsmouse: minimum x position: 0
[22.634] (II) ws: /dev/wsmouse: maximum x position: 3839
[22.634] (II) ws: /dev/wsmouse: minimum y position: 0
[22.634] (II) ws: /dev/wsmouse: maximum y position: 1079
[22.634] (==) ws: /dev/wsmouse: Buttons: 7
[22.634] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5
[22.634] (II) XINPUT: Adding extended input device "/dev/wsmouse"
(type: MOUSE, id 7)
[22.634] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1
[22.634] (**) /dev/wsmouse: (accel) acceleration profile 0
[22.634] (**) Option "AccelerationNumerator" "5"
[22.634] (**) Option "AccelerationDenominator" "2"
[22.634] (**) Option "AccelerationThreshold" "0"
[22.634] (**) /dev/wsmouse: (accel) acceleration factor: 2.500
[22.634] (**) /dev/wsmouse: (accel) acceleration threshold: 0
--
Alexis de BRUYN
Re: Pictures are "blurred" in certain cases after snapshot upgrade (radeonrdrm related?)
Problem solved [1]. Thanks jsd@ [1]: https://www.marc.info/?l=openbsd-tech&m=144984739021388&w=2 On 12/11/15 16:19, Alexis de BRUYN wrote: Hi Everybody, After upgraded from snapshots/amd64 12/09/2015 (previous was 12/04/2015), Puffy is blurred on xdm login screen (like [1]). Puffy (/etc/X11/xdm/pixmaps/OpenBSD_15bpp.xpm) displayed in feh is fine [2], while in eog is blurred [1]. Pictures/thumbnails displayed and all icon buttons in/of Thunderbird, Firefox [3], Libreoffice, Evince (some texts too if zoomed)... In Chromium [4], Gajim and Minitube, all is displayed fine. After this upgraded I also have another issue [5]: radeon_ring_test_lockup / radeon_sa_bo_manager_fini *ERROR* Today's snapshot sets and packages upgrade doesn't correct the problem. (fresh dmesg and Xorg.0.log below) -- Alexis de BRUYN
Pictures are "blurred" in certain cases after snapshot upgrade (radeonrdrm related?)
Hi Everybody, After upgraded from snapshots/amd64 12/09/2015 (previous was 12/04/2015), Puffy is blurred on xdm login screen (like [1]). Puffy (/etc/X11/xdm/pixmaps/OpenBSD_15bpp.xpm) displayed in feh is fine [2], while in eog is blurred [1]. Pictures/thumbnails displayed and all icon buttons in/of Thunderbird, Firefox [3], Libreoffice, Evince (some texts too if zoomed)... In Chromium [4], Gajim and Minitube, all is displayed fine. After this upgraded I also have another issue [5]: radeon_ring_test_lockup / radeon_sa_bo_manager_fini *ERROR* Today's snapshot sets and packages upgrade doesn't correct the problem. (fresh dmesg and Xorg.0.log below) Thanks for your help, [1]: http://www.de-bruyn.fr/puffy_bad.png [2]: http://www.de-bruyn.fr/puffy_good.png [3]: http://www.de-bruyn.fr/firefox_bad.png [4]: http://www.de-bruyn.fr/chromium_good.png [5]: http://marc.info/?l=openbsd-tech&m=144984166819347&w=2 $ dmesg OpenBSD 5.8-current (GENERIC.MP) #1737: Thu Dec 10 23:29:07 MST 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34306285568 (32717MB) avail mem = 33262448640 (31721MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb510 (78 entries) bios0: vendor American Megatrends Inc. version "1.12" date 05/14/2013 bios0: Shuttle Inc. SZ77 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ASF! MCFG SLIC HPET SSDT SSDT SSDT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(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-3770K CPU @ 3.50GHz, 3492.52 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,PCID,SSE4.1,SSE4.2,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, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 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,PCID,SSE4.1,SSE4.2,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-3770K CPU @ 3.50GHz, 3492.07 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,PCID,SSE4.1,SSE4.2,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-3770K CPU @ 3.50GHz, 3492.07 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,PCID,SSE4.1,SSE4.2,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-3770K CPU @ 3.50GHz, 3492.07 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT 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-3770K CPU @ 3.50GHz, 3492.07 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 1, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.07 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,AC
Re: Octeon snapshots
On 12/09/15 12:58, Paul Irofti wrote: [1]: https://www.mail-archive.com/tech%40openbsd.org/msg26048.html You have to use the octeon native objcopy by building the cross compiler: # cd /usr/src # make -f Makefile.cross TARGET=octeon cross-gcc And then use the objcopy from /usr/cross/octeon/usr/mips64-unknown-openbsd5.8/bin/objcopy Thank you Paul. bsd.rd is now booting. -- Alexis de BRUYN
Re: Octeon snapshots
trieving pub/OpenBSD/snapshots/octeon/bsd*.* local: bsd.mp remote: bsd.mp 150 Opening BINARY mode data connection for 'bsd.mp' (4057768 bytes). 100% |**| 3962 KB00:06 226 Transfer complete. 4057768 bytes received in 6.87 seconds (576.76 KB/s) local: bsd.rd remote: bsd.rd 150 Opening BINARY mode data connection for 'bsd.rd' (7568951 bytes). 100% |**| 7391 KB00:12 226 Transfer complete. 7568951 bytes received in 12.04 seconds (613.83 KB/s) 221 Goodbye. # ls -al total 30604 drwxr-xr-x 1 root wheel16384 Dec 31 1979 . drwxr-xr-x 13 root wheel 512 Dec 5 00:11 .. -rwxr-xr-x 1 root wheel 4020931 Nov 14 17:29 bsd -rwxr-xr-x 1 root wheel 4057768 Nov 27 03:42 bsd.mp -rwxr-xr-x 1 root wheel 7568951 Nov 27 03:42 bsd.rd # cd / # umount /mnt # reboot In my U-Boot I have for testing reason setup the variable bootdelay=10 so that I have time to press enter to stop the boot process and make changes if I need to, you can set it up to 5, or 3 if you like. You will see the count down anyway on the console. You can change it like this: Octeon ubnt_e100# setenv bootdelay '5' Octeon ubnt_e100# saveenv so in the future you are good to go and see the count down when to press enter to stop the boot process. Anyway, here when it start to boot you need to tell it to load the bsd.rd and this is how I do it. I just don't save it in the env variables, just preset what I need to get it going one time, so at the next reset it is what ot was before I did this install. Octeon ubnt_e100# setenv bootcmd 'fatload usb 0 $loadaddr bsd.rd; bootoctlinux rootdev=/dev/sd0' Octeon ubnt_e100# run bootcmd And then install as usual keeping my previous working partition name and all, just wiping out everything and do it fresh as I have notes for my install and did copy the configurations files I needed to keep. I like fresh clean install all the time. But upgrade works to and is faster too. And normal install: At your question that you are not sure, I just press enter, or that would be the default to be OpenBSD the A6 id partition. I didn't copy the full stuff here as it is boring and the same seen multiple times already. Formatting the partitions is kind of slow, on the USB I have anyway. Then I install the files from a decent mirrors and reboot. and here is the end results: # dmesg Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2015 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.8-current (GENERIC) #1: Thu Nov 26 15:01:01 CET 2015 jas...@erl-2.jasper.la:/usr/src/sys/arch/octeon/compile/GENERIC real mem = 247463936 (236MB) avail mem = 245170176 (233MB) warning: no entropy supplied by boot loader mainbus0 at root cpu0 at mainbus0: Cavium OCTEON CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 iobus0 at mainbus0 dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 cn30xxgmx0 at iobus0 base 0x118000800 irq 48 cnmac0 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f8 atphy0 at cnmac0 phy 7: F1 10/100/1000 PHY, rev. 2 cnmac1 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:f9 atphy1 at cnmac1 phy 6: F1 10/100/1000 PHY, rev. 2 cnmac2 at cn30xxgmx0: RGMII, address 44:d9:e7:40:ac:fa atphy2 at cnmac2 phy 5: F1 10/100/1000 PHY, rev. 2 uartbus0 at mainbus0 com0 at uartbus0 base 0x118000800 irq 34: ns16550, no working fifo com0: console com1 at uartbus0 base 0x118000c00 irq 35: ns16550, no working fifo /dev/ksyms: Symbol table not valid. umass0 at uhub0 port 1 configuration 1 interface 0 "SanDisk Cruzer Fit" rev 2.00/1.27 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct removable serial.07815571360927117103 sd0: 15267MB, 512 bytes/sector, 31266816 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets boot device: sd0 root on sd0a (55072c2137c3a4e7.a) swap on sd0b dump on sd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE! So, I see no problem and just did it again to s=be 100% sure even if that was good before too and try to give you way more details then needed to help you. May be somehow you didn't boot the bsd.rd file you think the system did? That's why I put these details steps in here. I hope it help you some anyway. Daniel -- Alexis de BRUYN
Re: em(4) watchdog timeouts
Hi Gregor, I use the same revision than yours : - "Intel 82583V" rev 0x00: msi Regards, Alexis VACHETTE.* * On 16/11/2015 10:12, Alexis VACHETTE wrote: > Hi Gregor, > > Thank you for your feedback. > > Did you have some timeout on 5.6 ? > > On amd64 version, I experienced some on heavy network load. Is it > related ? > > Regards, > Alexis VACHETTE. > On 11/11/2015 21:19, Gregor Best wrote: >> Hi Alexis, >> >> On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote: >>> [...] >>> Even with heavy network load ? >>> [...] >> So far, yes. I've saturated the device for about 45 Minutes with >> something like this (the other end is my laptop): >> >> ## on the router >> $ dd if=/dev/zero bs=8k | nc 172.31.64.174 55000 >> ## on my laptop >> $ nc -l 55000 | dd of=/dev/null bs=8k >> >> (with two or three streams in parallel). There were about 6k >> interrupts per second and bandwidth was about 250Mbps, which seems >> to be the maximum the tiny CPU in this router can do. No watchdog >> timeouts appeared, where previously something relatively low bandwidth >> (the SSDs in router and laptop suck) like this caused one every 20 >> or 30 seconds: >> >> ## on the router >> $ pax -w /home | nc 172.31.64.174 55000 >> >> I'll keep an eye on things, but so far it looks good. Regular usage >> works out so far as well. If you need me to run some special workload >> for you, I'd be more than happy to do that.
Re: em(4) watchdog timeouts
Hi Gregor, Thank you for your feedback. Did you have some timeout on 5.6 ? On amd64 version, I experienced some on heavy network load. Is it related ? Regards, Alexis VACHETTE. On 11/11/2015 21:19, Gregor Best wrote: Hi Alexis, On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote: [...] Even with heavy network load ? [...] So far, yes. I've saturated the device for about 45 Minutes with something like this (the other end is my laptop): ## on the router $ dd if=/dev/zero bs=8k | nc 172.31.64.174 55000 ## on my laptop $ nc -l 55000 | dd of=/dev/null bs=8k (with two or three streams in parallel). There were about 6k interrupts per second and bandwidth was about 250Mbps, which seems to be the maximum the tiny CPU in this router can do. No watchdog timeouts appeared, where previously something relatively low bandwidth (the SSDs in router and laptop suck) like this caused one every 20 or 30 seconds: ## on the router $ pax -w /home | nc 172.31.64.174 55000 I'll keep an eye on things, but so far it looks good. Regular usage works out so far as well. If you need me to run some special workload for you, I'd be more than happy to do that.
Re: em(4) watchdog timeouts
Hi Gregor, Even with heavy network load ? Regards, Alexis. De : owner-t...@openbsd.org de la part de Gregor Best Envoyé : mercredi 11 novembre 2015 15:20 À : Mark Kettenis Cc : t...@openbsd.org; misc@openbsd.org Objet : Re: em(4) watchdog timeouts I've done some further testing and I think I've narrowed it down to the "Unlocking em(4) a bit further"-patch [0]. With the patch reverted, I haven't seen any watchdog timeouts yet. I'm currently running the router with the patch reverted to make sure the timeouts don't happen again. [0]: https://www.marc.info/?l=openbsd-tech&m=144347723907388&w=4 -- Gregor
Re: Libreoffice i386 crash on 5.8 snapshot
On Sun, Jul 12, 2015 at 5:23 PM, Edgar Pettijohn wrote: Attempting to run libreoffice (be it writer, calc or the 'soffice' chooser component) fails with the error listed below. terminate called after throwing an instance of 'com::sun::star::uno::DeploymentException' >>> >>> (more snipping : double-checking sysmerge and pkg_add -u) > I would recommend removing it an reinstalling. My mirror shows 4.4.3.2 to > be the latest. You're showing to have 4.3.5.2 installed which is probably > what the problem is. If you installed from ports did you update your tree > first if not is PKG_PATH set correctly. I set installpath in pkg.conf, and I try to stick to packages whenever possible (99% of the time :) ). The old installed version was indeed the problem, 'pkg_delete libreoffice' followed by 'pkg_add libreoffice' bumped me to 4.4.3.2 which works as expected. First time I see a package failing to upgrade this way, though. Maybe I missed something with the jump to snapshots itself ? Anyway, case solved. Thank you.
Libreoffice i386 crash on 5.8 snapshot
Hi all, I'm relatively new to OpenBSD, hope this is proper. Attempting to run libreoffice (be it writer, calc or the 'soffice' chooser component) fails with the error listed below. The problem has been observed over the last few snapshots (since 21 june). Haven't seen anything here or on bugs@ about this. Hardware is a stock Thinkpad T60 originally installed with i386 5.7, since upgraded to snapshots and following updates every few days. Installed package libreoffice-4.3.5.2v0-no_java. Is there anything I'm missing or should I report a bug ? Output from 'lowriter' at the prompt: /usr/local/lib/libreoffice/program/soffice.bin:/usr/X11R6/lib/libfreetype.so.24.0: /usr/X11R6/lib/libfreetype.so.23.0 : WARNING: symbol(af_blue_strings) size mismatch, relink your program /usr/local/lib/libreoffice/program/soffice.bin:/usr/X11R6/lib/libfreetype.so.24.0: /usr/X11R6/lib/libfreetype.so.23.0 : WARNING: symbol(af_script_classes) size mismatch, relink your program /usr/local/lib/libreoffice/program/soffice.bin:/usr/X11R6/lib/libfreetype.so.24.0: /usr/X11R6/lib/libfreetype.so.23.0 : WARNING: symbol(af_blue_stringsets) size mismatch, relink your program /usr/local/lib/libreoffice/program/soffice.bin:/usr/X11R6/lib/libfreetype.so.24.0: /usr/X11R6/lib/libfreetype.so.23.0 : WARNING: symbol(af_style_classes) size mismatch, relink your program /usr/local/lib/libreoffice/program/soffice.bin:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.16.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/libi18nutil.so: undefined symbol '_ZTVN6icu_5413UnicodeStringE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/libvcllo.so: undefined symbol '_ZTIN6icu_547UObjectE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZTIN6icu_5422RuleBasedBreakIteratorE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIterator17getDynamicClassIDEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIteratoreqERKNS_13BreakIteratorE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIterator5cloneEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIterator7getTextEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIterator8getUTextEP5UTextR10UErrorCode' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator7setTextERKNS_13UnicodeStringE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator7setTextEP5UTextR10UErrorCode' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator9adoptTextEPNS_17CharacterIteratorE' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator5firstEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator4lastEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator8previousEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator4nextEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZNK6icu_5422RuleBasedBreakIterator7currentEv' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator9followingEi' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator9precedingEi' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/../program/libi18npoollo.so: undefined symbol '_ZN6icu_5422RuleBasedBreakIterator10isBoundaryEi' /usr/local/lib/libreoffice/program/soffice.bin:/usr/local/lib/libreoffice/program/..
Xenocara/radeonsi_dri.so build failed on -current
Hi misc@, For a couple of weeks, I am not able to build Xenocara on -current (even after a fresh cvs update or checkout, and manually install the sets) anymore. OpenBSD 5.7 GENERIC.MP#44 amd64 I have got the following errors: cc -shared -fpic -o radeonsi_dri.so `lorder dri_context.so dri_drawable.so dri_query_renderer.so dri_screen.so dri2.so utils.so dri_util.so xmlconfig.so drm_target.so dri_context.so dri_drawable.so dri_query_renderer.so dri_screen.so dri2.so utils.so dri_util.so xmlconfig.so drm_target.so|tsort -q` ../../mesa/libmesagallium/libmesagallium_pic.a ../../glsl/libglsl/libglsl_pic.a ../../gallium/drivers/trace/libtrace_pic.a ../../gallium/drivers/rbug/librbug_pic.a ../../gallium/drivers/radeonsi/libradeonsi_pic.a ../../gallium/drivers/radeon/libradeon_pic.a ../../gallium/winsys/radeon/drm/libradeonwinsys_pic.a ../../gallium/libgallium/libgallium_pic.a -L/usr/X11R6/lib -lexpat -lm -lstdc++ -lc -ldrm_radeon -lxcb-dri2 -L/usr/local/lib -lLLVMAsmParser -lLLVMipo -lLLVMVectorize -lLLVMR600CodeGen -lLLVMR600Desc -lLLVMR600Info -lLLVMR600AsmPrinter -lLLVMMCJIT -lLLVMRuntimeDyld -lLLVMBitWriter -lLLVMX86Disassembler -lLLVMX86AsmParser -lLLVMX86CodeGen -lLLVMSelectionDAG -lLLVMAsmPrinter -lLLVMMCParser -lLLVMX86Desc -lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMJIT -lLLVMExecutionEngine -lLLVMCodeGen -lLLVMScalarOpts -lLLVMInstCombine -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMMC -lLLVMObject -lLLVMBitReader -lLLVMCore -lLLVMSupport /usr/local/lib/libelf.a /usr/bin/ld: /usr/local/lib/libelf.a(end.o): relocation R_X86_64_PC32 against `elf_end' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status *** Error 1 in lib/libGL/dri/radeonsi (../Makefile.inc:86 'radeonsi_dri.so') *** Error 2 in lib/libGL/dri (:48 'all') *** Error 2 in lib/libGL (:48 'all') *** Error 2 in lib/libGL (/usr/X11R6/share/mk/bsd.xorg.mk:211 'build') *** Error 2 in lib (:48 'build') *** Error 2 in . (:48 'realbuild') *** Error 2 in /usr/xenocara (Makefile:36 'build') Thanks for your help, -- Alexis de BRUYN
Re: usbhidctl(1) and usbhidaction(1)
On 05/07/15 14:40, ludovic coues wrote: hello, Hi Ludovic, I wanted to know if anyone get either usbhidctl(1) or usbhidaction(1) working and if so for which usage. I have some issues with Logitech wireless keyboards (Wave 2.4 and K400r) on -current. Consumer:Mute and Consumer:Volume_Decrement have no effect and Consumer:Volume_Increment actually decrements. $ cat ~/.usbhid.conf Consumer:Volume_Increment 1 mixerctl outputs.master=+15 Consumer:Volume_Decrement 1 mixerctl outputs.master=-15 Consumer:Mute 1 mixerctl outputs.master.mute=toggle With a Logitech K200 (with cable) and a Cherry KW 3000 (wireless), everything is working fine. Let me know if you need more information. Regards, -- Alexis de BRUYN
Re: [Cannot allocate memory][Qemu][x86 & i386] limits ? login.conf ?
On 16.07.2014 10:48, Francois Pussault wrote: > Hi all. Hi François, > I experiment qemu problems while playing with emulators/virtual machines ... > > When I try to create any virtual machines with x86_64 or i 386 hardware and > more than 256Mo ram that fail. > Qemu returns "Cannot allocate memory". I had the same issue on -current couple weeks ago. > default:\ > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin > /usr/local/sbin:\ > :umask=022:\ > :datasize-max=2048M:\ > :datasize-cur=2024M:\ > :maxproc-max=512:\ > :maxproc-cur=256:\ > :vmemoryuse=1024:\ > :openfiles-cur=1024:\ > :stacksize-cur=8M:\ > :localcipher=blowfish,6:\ > :ypcipher=old:\ > :tc=auth-defaults:\ > :tc=auth-ftp-defaults: > I added in my user class: :datasize=infinity:\ No more problem for me, I can start VM with +256M RAM. Be sure that the user which launches qemu has your class (vipw(8)). Regards, -- Alexis de BRUYN
Re: APU firmware
Thank you for the tips Brett. I ordered my two boards from gooze.eu's website. The two APU have an old bios. One of them is up-to-date since my debugging session last evening. I will update the last one today ;) Best regards, Alexis VACHETTE. _ From: Brett Mahar [mailto:br...@coiloptic.org] To: misc@openbsd.org Sent: Sun, 06 Apr 2014 12:36:25 +0100 Subject: Re: APU firmware Hi misc@, I just emailed PC-Engines sales about the updated bios, they said: "We will update to the new BIOS for new production batches. In the meantime, you can request upgraded BIOS in the order comments." So, think I'll get one soon. Brett. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
Glad to see it's working for you too ;) Thanks to Stuart for the debugging session and Theo ! Best regards, Alexis VACHETTE. _ From: Zé Loff [mailto:zel...@zeloff.org] To: misc@openbsd.org Sent: Sun, 06 Apr 2014 00:31:53 +0100 Subject: Re: APU firmware On Sat, Apr 05, 2014 at 08:14:22AM +, Stuart Henderson wrote: > On 2014-04-04, Zé Loff wrote: > > On Thu, Apr 03, 2014 at 07:22:52AM -0600, dera...@cvs.openbsd.org wrote: > >> For those of you with PC-Engines APU systems, a BIOS which works a lot > >> better can be found about halfway down http://pcengines.ch/apu1c.htm > >> > >> Good luck. I hope they have it on newly shipped boards.. > >> > > > > After an unbelievable ordeal to flash the new BIOS, OpenBSD's installer > > (5.4-release and -current, amd64) still fails at the same spot: hangs > > right after the 'entry point' line (unable to detect storage devices?). > > > > > > That sounds like you forgot to 'set tty com0' in the boot loader. > *facepalm* Well, this is embarrassing... I did an install onto a USB stick on my laptop and then used the stick to boot the APU, so I _think_ the installer didn't ask me about changing the default console to com0 and it slipped my mind. It's been a long time since I did a clean install on a headless machine, I've been happily upgrading them for a while now... Sorry for the noise and thanks for the cluebat * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
It's much better with : - stty com0 115200 - set tty com0 Still get error messages on OpenBSD 5.4 flashrd image : ohci3 at pci0 dev 22 function 0 "ATI SB700 USB" rev 0x00: couldn't map interrupt ohci2 at pci0 dev 22 function 2 "ATI SB700 USB2" rev 0x00: couldn't map interrupt The system hang after. Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: misc@openbsd.org Sent: Sat, 05 Apr 2014 10:14:22 +0100 Subject: Re: APU firmware On 2014-04-04, Zé Loff wrote: > On Thu, Apr 03, 2014 at 07:22:52AM -0600, dera...@cvs.openbsd.org wrote: >> For those of you with PC-Engines APU systems, a BIOS which works a lot >> better can be found about halfway down http://pcengines.ch/apu1c.htm >> >> Good luck. I hope they have it on newly shipped boards.. >> > > After an unbelievable ordeal to flash the new BIOS, OpenBSD's installer > (5.4-release and -current, amd64) still fails at the same spot: hangs > right after the 'entry point' line (unable to detect storage devices?). > > That sounds like you forgot to 'set tty com0' in the boot loader. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
Good evening, The board boot successfully with OpenBSD 5.5. I'm unable to get the login prompt with serial port. I enabled the serial port with /etc/ttys file : - tty00 "/usr/libexec/getty std.9600" vt220 on secure I am missing something here ? Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: misc@openbsd.org Sent: Sat, 05 Apr 2014 10:14:22 +0100 Subject: Re: APU firmware On 2014-04-04, Zé Loff wrote: > On Thu, Apr 03, 2014 at 07:22:52AM -0600, dera...@cvs.openbsd.org wrote: >> For those of you with PC-Engines APU systems, a BIOS which works a lot >> better can be found about halfway down http://pcengines.ch/apu1c.htm >> >> Good luck. I hope they have it on newly shipped boards.. >> > > After an unbelievable ordeal to flash the new BIOS, OpenBSD's installer > (5.4-release and -current, amd64) still fails at the same spot: hangs > right after the 'entry point' line (unable to detect storage devices?). > > That sounds like you forgot to 'set tty com0' in the boot loader. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
After booting a recent snapshot of OpenBSD 5.5, it's working without big issues. I don't have any mSSD card right know (firmware issues), I will only test network card (wired and wireless) ;) Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: Alexis Vachette [mailto:avache...@sisteer.com] Cc: misc@openbsd.org Sent: Sat, 05 Apr 2014 22:12:46 +0100 Subject: Re: APU firmware On 2014/04/05 22:04, Alexis Vachette wrote: > Thank you for the tips Stuart. > > It's mandatory to use the same speed ? Well, not mandatory, but it's a lot easier, otherwise you will have to change the speed of your serial terminal, e.g. if you're in cu(1) you can type ~S and choose the new speed. If the speed doesn't match, you will either get junk on the screen, or see nothing at all. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
Thank you for the tips Stuart. It's mandatory to use the same speed ? Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: Alexis Vachette [mailto:avache...@sisteer.com] Cc: misc@openbsd.org Sent: Sat, 05 Apr 2014 21:43:15 +0100 Subject: Re: APU firmware On 2014/04/05 21:14, Alexis Vachette wrote: > Good evening, > > The board boot successfully with OpenBSD 5.5. > > I'm unable to get the login prompt with serial port. > > I enabled the serial port with /etc/ttys file : > > - tty00 "/usr/libexec/getty std.9600" vt220 on secure > > I am missing something here ? Is the port speed in your /etc/ttys entry correct? I don't have one of these boards, but it looks like it should be 115200 baud unless you have changed the BIOS setting. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
Hum, maybe too quick. I can't type anything in the shell, it's always blank ;( Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: Alexis Vachette [mailto:avache...@sisteer.com] Cc: misc@openbsd.org Sent: Sat, 05 Apr 2014 22:12:46 +0100 Subject: Re: APU firmware On 2014/04/05 22:04, Alexis Vachette wrote: > Thank you for the tips Stuart. > > It's mandatory to use the same speed ? Well, not mandatory, but it's a lot easier, otherwise you will have to change the speed of your serial terminal, e.g. if you're in cu(1) you can type ~S and choose the new speed. If the speed doesn't match, you will either get junk on the screen, or see nothing at all. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
I don't know what to say. It's working now, thank you very much Stuart ;) Best regards, Alexis VACHETTE. _ From: Stuart Henderson [mailto:s...@spacehopper.org] To: Alexis Vachette [mailto:avache...@sisteer.com] Cc: misc@openbsd.org Sent: Sat, 05 Apr 2014 22:12:46 +0100 Subject: Re: APU firmware On 2014/04/05 22:04, Alexis Vachette wrote: > Thank you for the tips Stuart. > > It's mandatory to use the same speed ? Well, not mandatory, but it's a lot easier, otherwise you will have to change the speed of your serial terminal, e.g. if you're in cu(1) you can type ~S and choose the new speed. If the speed doesn't match, you will either get junk on the screen, or see nothing at all. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: APU firmware
Thanks Theo, I will test that ASAP ;) When my two boards will be at home ! Regards, *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> On 04/03/14 15:22, dera...@cvs.openbsd.org wrote: > For those of you with PC-Engines APU systems, a BIOS which works a lot > better can be found about halfway down http://pcengines.ch/apu1c.htm > > Good luck. I hope they have it on newly shipped boards.. > * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: OpenBSD and NetFlow
Hi Peter, What you mean by the local one, it's the one with which I have trouble ? *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 04/12/2013 15:50, Peter N. M. Hansteen a écrit : > Alexis VACHETTE writes: > >> Here is the network interfaces configuration : > After a too-quick look there's nothing that immediately screams out at > me as very wrong here, but another point - can you verify that any and > all firewalls in the signal path (starting with the local one) > actually passes UDP on the relevant ports and in the relevant > directions? > > It's easy to forget that the 'default to block' rule sets we commonly > advocate will in fact block anything we don't explicitly allow. > > One anecdote I probably should write up properly some time involves a > netflow setup I had where something we did not manage was an > intermediate hop between one sensor and the collector, so we resorted > to a pflow export to udp port 22 on the collector site's > internet-visible interface and little rdr-to trickery to get it all > there (22/udp is reserved for ssh, but none of the widely used > implementations actually rely on it). > > - Peter * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: OpenBSD and NetFlow
Hi Giancarlo, This can be an option but we have one more router which export is netflow data. We need to have a single point of data collection. *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 04/12/2013 14:38, Giancarlo Razzolini a écrit : > Em 04-12-2013 11:15, Alexis VACHETTE escreveu: >> Hi Patrick, >> >> Yes you're are right. >> >> > Hi Alexis, > > I am currently using a pflow interface with the nfsen package. I am > running it on the same machine that generate the flows, hence, I do not > send them over the wire. I know that it do not solve your current > problem, but if you can run them both on the same machine, I strongly > advise you to do so. The setup is very simple, I've even managed to run > it using the chrooted apache. > > Cheers, > * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: OpenBSD and NetFlow
Hi Patrick, Yes you're are right. *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 04/12/2013 14:10, Patrick Lamaiziere a écrit : > Le Tue, 03 Dec 2013 17:05:59 +0100, > Alexis VACHETTE a écrit : > >> Hi everyone, > Hello, > >> I would like to share an issue with one of my OpenBSD Firewall which >> is present in my company. >> >> Everything was working fine until a server crash this last week-end. >> >> We have setup the netflow protocol with the pseudo device pflow0. > If I understand well, you see the outgoing netflow packets on pflow0 but > not on the physical interface with tcpdump ? > > I've tried on OpenBSD 5.1, tcpdump shows the netflow packets on both > interfaces. > > Regards. * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: OpenBSD and NetFlow
Hi Peter, Thanks for your help ! Here is the network interfaces configuration : # ifconfig -a lo0: flags=8049 mtu 33160 priority: 0 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 em2: flags=8b43 mtu 1300 lladdr 00:10:f3:1a:49:3a priority: 0 media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 192.168.1.251 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::210:f3ff:fe1a:493a%em2 prefixlen 64 scopeid 0x1 em3: flags=8b43 mtu 1500 lladdr 00:10:f3:1a:49:3b priority: 0 media: Ethernet autoselect (1000baseT full-duplex,master) status: active inet 192.168.16.251 netmask 0xff00 broadcast 192.168.16.255 inet6 fe80::210:f3ff:fe1a:493b%em3 prefixlen 64 scopeid 0x2 em4: flags=8843 mtu 1500 lladdr 00:10:f3:1a:49:3c description: PFSYNC priority: 0 media: Ethernet autoselect (none) status: no carrier inet 172.16.0.1 netmask 0xff00 broadcast 172.16.0.255 inet6 fe80::210:f3ff:fe1a:493c%em4 prefixlen 64 scopeid 0x3 enc0: flags=0<> priority: 0 groups: enc status: active pflog0: flags=141 mtu 33160 priority: 0 groups: pflog pflow0: flags=41 mtu 1492 priority: 0 pflow: sender: 192.168.1.251 receiver: 192.168.1.19:9995 groups: pflow carp2: flags=8843 mtu 1500 lladdr 00:00:5e:00:01:0a priority: 0 carp: MASTER carpdev em2 vhid 10 advbase 1 advskew 0 groups: carp status: master inet6 fe80::200:5eff:fe00:10a%carp2 prefixlen 64 scopeid 0xa inet 192.168.1.253 netmask 0xff00 broadcast 192.168.1.255 carp3: flags=8843 mtu 1500 lladdr 00:00:5e:00:01:01 priority: 0 carp: MASTER carpdev em3 vhid 1 advbase 1 advskew 0 groups: carp status: master inet6 fe80::200:5eff:fe00:101%carp3 prefixlen 64 scopeid 0xb inet 192.168.16.253 netmask 0xff00 broadcast 192.168.16.255 All networks use a /24 netmask. And my routing table looks like that : # route -n show Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface 127/8 127.0.0.1 UGRS 00 33160 8 lo0 127.0.0.1 127.0.0.1 UH 2 151 33160 4 lo0 172.16.0/24link#3 C 00 - 4 em4 192.168.1/24 link#1 UC150 - 4 em2 192.168.1.1link#1 UHLc 1 2969 - 4 em2 192.168.1.12 link#1 UHLc 02 - 4 em2 192.168.1.40 link#1 UHLc 02 - 4 em2 192.168.1.253 192.168.1.253 UH 00 - 4 carp2 192.168.16/24 link#2 UC 10 - 4 em3 192.168.16.253 192.168.16.253 UH 00 - 4 carp3 194.204.201.130/32 link#5 UC 00 - 4 em6 224/4 127.0.0.1 URS00 33160 8 lo0 As josh stated he is right. We use carp(4), but right know the configuration is broken. I don't see any traffic passing through the carp2 interface. *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 03/12/2013 18:27, Peter N. M. Hansteen a écrit : > Alexis VACHETTE writes: > >> - uname -a >> >> OpenBSD casa-vpn01.my.domain 4.8 GENERIC.MP#335 amd6 > It's been a while since 4.8. It's not guaranteed that running outdated > software is your problem, but it's easier for everyone trying to help > if you're reasonably up to date (which these days means 5.3 or better). > > >> - dmesg output >> >> wskbd0 at pckbd0: console keyboard, using wsdisplay0 >> pcppi0 at isa0 port 0x61 >> spkr0 at pcppi0 >> lpt0 at isa0 port 0x378/4 irq 7 >> wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 >> lm2 at wbsio0 port 0xa00/8: W83627HF >> mtrr: Pentium Pro MTRR support >> softraid0 at root >> root on wd0a swap on wd0b dump on wd0b >> WARNING: / was not properly unmounted > That is *not* complete dmesg output, but then again I suspect the > problem is not really hardware related. > >>>> # ifconfig pflow0 >>>> pflow0: flags=41 mtu 1492 >>>> priority: 0 >>>> pflow: sender: 192.168.1.251 receiver: 192.168.1.19:9995 >>>> groups: pflow > Looks reasonable, but what's the netmask? What does your routing table > look like? An
Re: OpenBSD and NetFlow
Bonjour Sven, Je suis d'accord que le plus simple c'est de suivre le paquet avec tcpdump. Par contre ce que je constate c'est qu'il n'y a aucun paquet qui part de l'interface em2. La règle packet filter en sortie est toute simple car c'est un pass out all, comme indiqué dans mon message suivant. *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff â France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 03/12/2013 18:28, sven falempin a écrit : > # nc -zvu 192.168.1.19 9995 > Connection to 192.168.1.19 9995 port [udp/*] succeeded! > > va pas t aider en UDP il peu pas savoir si cela ecoute. > > > > tu dois faire des (tcp)dump sur le chemin reseau et suivre tes data udp > > > > echo "vivelafrance" | nc 192.168.1.19 9995 > > > > On Tue, Dec 3, 2013 at 12:13 PM, Alexis VACHETTE > mailto:avache...@sisteer.com>> wrote: > > Hi Josh, > > First of all thanks for the welcome to the misc list ! > > I don't get a failure when I tried to destroy and re-create the pflow > interface indeed. > > You will find the information requested below : > > - uname -a > > OpenBSD casa-vpn01.my.domain 4.8 GENERIC.MP#335 > <http://GENERIC.MP#335> amd6 > > - dmesg output > > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > lpt0 at isa0 port 0x378/4 irq 7 > wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 > lm2 at wbsio0 port 0xa00/8: W83627HF > mtrr: Pentium Pro MTRR support > softraid0 at root > root on wd0a swap on wd0b dump on wd0b > WARNING: / was not properly unmounted > > I just posted one line because the packet filter configuration is very > permissive : > > pass out log (all) all keep state (pflow) > > The tcpdump output of pflog interface don't report any block lines > with > the src and dst ip of the netflow configuration. > > Using "nc" command always give me a correct answer : > > # nc -zvu 192.168.1.19 9995 > Connection to 192.168.1.19 9995 port [udp/*] succeeded! > > If you need anything else don't hesitate. > > Right now, I'm stuck because I don't see anything wrong. > > *Alexis VACHETTE | Network and System Engineer > * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff â France > Direct line: +33 1 70 95 51 19 > | Fax: +33 1 70 95 50 90 > www.sisteer.com <http://www.sisteer.com> <http://www.sisteer.com> > Le 03/12/2013 17:51, josh Grosse a écrit : > > On 2013-12-03 11:05, Alexis VACHETTE wrote: > >> Hi everyone, > > > > Hey there! Welcome to misc@ (if you haven't posted to the list > > before). I use NfSen to monitor a pair of small OpeNBSD firewalls, > > and pflow(4) between them. > > > >> set state-defaults pflow > > > > I use this, too. > > > >> # ifconfig pflow0 > >> pflow0: flags=41 mtu 1492 > >> priority: 0 > >> pflow: sender: 192.168.1.251 receiver: > 192.168.1.19:9995 <http://192.168.1.19:9995> > >> groups: pflow > > > > My output looks similar, except the protocol I use (5, the default), > > is shown on my ifconfig(8) output. I am > > running -current, so I suspect you are running an earlier > -release or > > -stable, or -release+errata. You didn't post your dmesg, nor > mention > > flavor of the OpenBSD. There has been recent work in pflow(4), and > > there is a patch for 5.3-release and 5.4-release for a bug when a > > pflow interface is destroyed. You didn't mention a failure on > > destroy/recreate so I assume you must have applied it. > > > >> I don't see anything going out of the em2 interface. > > > > I would suspect your PF configuration, since you only posted a > single > > line from it. I use a crossover cable between the firewalls, > and one > > reports to the other for data collection, so my rule is simple: > > > > pass log quick on $private_nic proto udp from any to any port 9995 > > > > I hope that helps. If my Email was valueless, I'm sorry. > > > > -Josh- > > > > *
Re: OpenBSD and NetFlow
Hi Josh, First of all thanks for the welcome to the misc list ! I don't get a failure when I tried to destroy and re-create the pflow interface indeed. You will find the information requested below : - uname -a OpenBSD casa-vpn01.my.domain 4.8 GENERIC.MP#335 amd6 - dmesg output wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 wbsio0 at isa0 port 0x2e/2: W83627HF rev 0x41 lm2 at wbsio0 port 0xa00/8: W83627HF mtrr: Pentium Pro MTRR support softraid0 at root root on wd0a swap on wd0b dump on wd0b WARNING: / was not properly unmounted I just posted one line because the packet filter configuration is very permissive : pass out log (all) all keep state (pflow) The tcpdump output of pflog interface don't report any block lines with the src and dst ip of the netflow configuration. Using "nc" command always give me a correct answer : # nc -zvu 192.168.1.19 9995 Connection to 192.168.1.19 9995 port [udp/*] succeeded! If you need anything else don't hesitate. Right now, I'm stuck because I don't see anything wrong. *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff â France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> Le 03/12/2013 17:51, josh Grosse a écrit : > On 2013-12-03 11:05, Alexis VACHETTE wrote: >> Hi everyone, > > Hey there! Welcome to misc@ (if you haven't posted to the list > before). I use NfSen to monitor a pair of small OpeNBSD firewalls, > and pflow(4) between them. > >> set state-defaults pflow > > I use this, too. > >> # ifconfig pflow0 >> pflow0: flags=41 mtu 1492 >> priority: 0 >> pflow: sender: 192.168.1.251 receiver: 192.168.1.19:9995 >> groups: pflow > > My output looks similar, except the protocol I use (5, the default), > is shown on my ifconfig(8) output. I am > running -current, so I suspect you are running an earlier -release or > -stable, or -release+errata. You didn't post your dmesg, nor mention > flavor of the OpenBSD. There has been recent work in pflow(4), and > there is a patch for 5.3-release and 5.4-release for a bug when a > pflow interface is destroyed. You didn't mention a failure on > destroy/recreate so I assume you must have applied it. > >> I don't see anything going out of the em2 interface. > > I would suspect your PF configuration, since you only posted a single > line from it. I use a crossover cable between the firewalls, and one > reports to the other for data collection, so my rule is simple: > > pass log quick on $private_nic proto udp from any to any port 9995 > > I hope that helps. If my Email was valueless, I'm sorry. > > -Josh- * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
OpenBSD and NetFlow
Hi everyone, I would like to share an issue with one of my OpenBSD Firewall which is present in my company. Everything was working fine until a server crash this last week-end. We have setup the netflow protocol with the pseudo device pflow0. You can find the relevant files for the netflow configuration below. /etc/pf.conf : set state-defaults pflow /etc/hostname.pflow : flowsrc 192.168.1.251 flowdst 192.168.1.19:9995 The output of ifconfig for the pflow0 interface : # ifconfig pflow0 pflow0: flags=41 mtu 1492 priority: 0 pflow: sender: 192.168.1.251 receiver: 192.168.1.19:9995 groups: pflow Three tcpdump sample : - From the netflow interface : # tcpdump -nettti pflow0 tcpdump: listening on pflow0, link-type RAW Dec 03 15:53:31.817647 ip: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] Dec 03 15:53:40.247888 ip: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] Dec 03 15:53:50.623061 ip: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] Dec 03 15:53:57.428342 ip: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] - From the pflog inteface : # tcpdump -nettti pflog0 host 192.168.1.19 and port 9995 tcpdump: listening on pflog0, link-type PFLOG Dec 03 15:55:37.643985 rule def/(match) pass out on em2: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] Dec 03 15:55:42.644029 rule def/(match) pass out on em2: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] Dec 03 15:55:48.644243 rule def/(match) pass out on em2: 192.168.1.251.49904 > 192.168.1.19.9995: udp 1464 (DF) [tos 0x10] - From the sender interface : # tcpdump -nettti em2 host 192.168.1.19 and port 9995 tcpdump: listening on em2, link-type EN10MB I don't see anything going out of the em2 interface. On a lab environment with GNS3, I clearly see the UDP packets going out of the sender interface. Is there a best way to troubleshoot this issue ? I don't know how to fix this behaviour, I tried to destroy and recreate the pflow0 interface but still no luck. -- *Alexis VACHETTE | Network and System Engineer * Sisteer France: 43 rue Pierre Valette, 92240 Malakoff -- France Direct line: +33 1 70 95 51 19 | Fax: +33 1 70 95 50 90 www.sisteer.com <http://www.sisteer.com> * * Ce message et toutes les pieces jointes sont confidentiels et etablis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. SISTEER decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas le destinataire de ce message, merci de le detruire et d'informer l'expediteur. * * This message and any attachments are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. SISTEER shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. * *
Re: radeondrm(4): only 1 screen displaying over 3
Thanks to jsg@, problem solved: CVSROOT:/cvs Module name:src Changes by: j...@cvs.openbsd.org2013/09/01 04:39:39 Modified files: sys/dev/pci/drm/radeon: si.c sid.h Log message: drm/radeon: update line buffer allocation for dce6 [...] On 28.08.2013 09:51, Alexis de BRUYN wrote: > Hi misc@, > > On an ATI Radeon HD 7870 display card with 6 mini-display-ports, only 1 > screen over 3 connected is displaying correctly : > > [ 4026.582] (II) RADEON(0): Output DisplayPort-0 connected > [ 4026.582] (II) RADEON(0): Output DisplayPort-1 connected > [ 4026.582] (II) RADEON(0): Output DisplayPort-2 connected > > * Output DisplayPort-0 connected : displaying the default backgroud > with the login box ; > * Output DisplayPort-1 connected : black screen ; > * Output DisplayPort-2 connected : displaying only multiple > white/green/blue/red/... vertical lines (without the mouse cursor > interacting). > > I have tested with and without a xorg.conf file, xrandr too but the > result is the same. > > All hardware devices are working fine separetely. A 3-head xinerama mode > was testing under Linux with the Ati proprietary driver, all looks fine. > > # cat /var/log/Xorg.0.log > [ 4025.282] (--) checkDevMem: using aperture driver /dev/xf86 > [ 4025.290] (--) Using wscons driver on /dev/ttyC4 in pcvt > compatibility mode (version 3.32) > [ 4026.353] > X.Org X Server 1.14.2 > Release Date: 2013-06-25 > [ 4026.353] X Protocol Version 11, Revision 0 > [ 4026.353] Build Operating System: OpenBSD 5.4 amd64 > [ 4026.353] Current Operating System: OpenBSD test.test.org 5.4 > GENERIC.MP#0 amd64 > [ 4026.353] Build Date: 25 August 2013 10:11:53AM > [ 4026.353] > [ 4026.353] Current version of pixman: 0.30.2 > [ 4026.353]Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 4026.353] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 4026.353] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 25 > 22:11:57 2013 > [ 4026.353] (==) Using system config directory > "/usr/X11R6/share/X11/xorg.conf.d" > [ 4026.353] (==) No Layout section. Using the first Screen section. > [ 4026.353] (==) No screen section available. Using defaults. > [ 4026.353] (**) |-->Screen "Default Screen Section" (0) > [ 4026.353] (**) | |-->Monitor "" > [ 4026.354] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 4026.354] (==) Disabling SIGIO handlers for input devices > [ 4026.354] (==) Automatically adding devices > [ 4026.354] (==) Automatically enabling devices > [ 4026.354] (==) Not automatically adding GPU devices > [ 4026.354] (==) 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/ > [ 4026.354] (==) ModulePath set to "/usr/X11R6/lib/modules" > [ 4026.354] (II) The server relies on wscons to provide the list of > input devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [ 4026.354] (II) Loader magic: 0x1a91968ea040 > [ 4026.354] (II) Module ABI versions: > [ 4026.354]X.Org ANSI C Emulation: 0.4 > [ 4026.354]X.Org Video Driver: 14.1 > [ 4026.354]X.Org XInput driver : 19.1 > [ 4026.354]X.Org Server Extension : 7.0 > [ 4026.354] (--) PCI:*(0:5:0:0) 1002:6818:1787:2321 rev 0, Mem @ > 0xd000/268435456, 0xeff8/262144, I/O @ 0xe800/256, BIOS @ > 0x/131072 > [ 4026.354] Initializing built-in extension Generic Event Extension > [ 4026.354] Initializing built-in extension SHAPE > [ 4026.354] Initializing built-in extension MIT-SHM > [ 4026.354] Initializing built-in extension XInputExtension > [ 4026.354] Initializing built-in extension XTEST > [ 4026.354] Initializing built-in extension BIG-REQUESTS > [ 4026.354] Initializing built-in extension SYNC > [ 4026.354] Initializing built-in extension XKEYBOARD > [ 4026.354] Initializing built-in extension XC-MISC > [ 4026.354] Initializing built-in extension SECURITY > [ 4026.354] Initializing built-in extension XINERAMA > [ 4026.354] Initializing built-in extension XFIXES > [ 4026.354] Initializing built-in extension RENDER > [ 4026.354] Initializing built-in extension RANDR > [ 4026.354] Initializing built-in
radeondrm(4): only 1 screen displaying over 3
Hi misc@, On an ATI Radeon HD 7870 display card with 6 mini-display-ports, only 1 screen over 3 connected is displaying correctly : [ 4026.582] (II) RADEON(0): Output DisplayPort-0 connected [ 4026.582] (II) RADEON(0): Output DisplayPort-1 connected [ 4026.582] (II) RADEON(0): Output DisplayPort-2 connected * Output DisplayPort-0 connected : displaying the default backgroud with the login box ; * Output DisplayPort-1 connected : black screen ; * Output DisplayPort-2 connected : displaying only multiple white/green/blue/red/... vertical lines (without the mouse cursor interacting). I have tested with and without a xorg.conf file, xrandr too but the result is the same. All hardware devices are working fine separetely. A 3-head xinerama mode was testing under Linux with the Ati proprietary driver, all looks fine. # cat /var/log/Xorg.0.log [ 4025.282] (--) checkDevMem: using aperture driver /dev/xf86 [ 4025.290] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [ 4026.353] X.Org X Server 1.14.2 Release Date: 2013-06-25 [ 4026.353] X Protocol Version 11, Revision 0 [ 4026.353] Build Operating System: OpenBSD 5.4 amd64 [ 4026.353] Current Operating System: OpenBSD test.test.org 5.4 GENERIC.MP#0 amd64 [ 4026.353] Build Date: 25 August 2013 10:11:53AM [ 4026.353] [ 4026.353] Current version of pixman: 0.30.2 [ 4026.353]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4026.353] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4026.353] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 25 22:11:57 2013 [ 4026.353] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 4026.353] (==) No Layout section. Using the first Screen section. [ 4026.353] (==) No screen section available. Using defaults. [ 4026.353] (**) |-->Screen "Default Screen Section" (0) [ 4026.353] (**) | |-->Monitor "" [ 4026.354] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 4026.354] (==) Disabling SIGIO handlers for input devices [ 4026.354] (==) Automatically adding devices [ 4026.354] (==) Automatically enabling devices [ 4026.354] (==) Not automatically adding GPU devices [ 4026.354] (==) 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/ [ 4026.354] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 4026.354] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 4026.354] (II) Loader magic: 0x1a91968ea040 [ 4026.354] (II) Module ABI versions: [ 4026.354]X.Org ANSI C Emulation: 0.4 [ 4026.354]X.Org Video Driver: 14.1 [ 4026.354]X.Org XInput driver : 19.1 [ 4026.354]X.Org Server Extension : 7.0 [ 4026.354] (--) PCI:*(0:5:0:0) 1002:6818:1787:2321 rev 0, Mem @ 0xd000/268435456, 0xeff8/262144, I/O @ 0xe800/256, BIOS @ 0x/131072 [ 4026.354] Initializing built-in extension Generic Event Extension [ 4026.354] Initializing built-in extension SHAPE [ 4026.354] Initializing built-in extension MIT-SHM [ 4026.354] Initializing built-in extension XInputExtension [ 4026.354] Initializing built-in extension XTEST [ 4026.354] Initializing built-in extension BIG-REQUESTS [ 4026.354] Initializing built-in extension SYNC [ 4026.354] Initializing built-in extension XKEYBOARD [ 4026.354] Initializing built-in extension XC-MISC [ 4026.354] Initializing built-in extension SECURITY [ 4026.354] Initializing built-in extension XINERAMA [ 4026.354] Initializing built-in extension XFIXES [ 4026.354] Initializing built-in extension RENDER [ 4026.354] Initializing built-in extension RANDR [ 4026.354] Initializing built-in extension COMPOSITE [ 4026.354] Initializing built-in extension DAMAGE [ 4026.354] Initializing built-in extension MIT-SCREEN-SAVER [ 4026.354] Initializing built-in extension DOUBLE-BUFFER [ 4026.354] Initializing built-in extension RECORD [ 4026.354] Initializing built-in extension DPMS [ 4026.354] Initializing built-in extension X-Resource [ 4026.354] Initializing built-in extension XVideo [ 4026.354] Initializing built-in extension XVideo-MotionCompensation [ 4026.354] Initializing built-in extension XFree86-VidModeExtension [ 4026.354] Initializing built-in extension XFree86-DGA [ 4026.354] Initializing built-in extension XFree86-DRI [ 4026.354] Initializing built-in extension DRI2 [ 4026.354] (II) LoadModule: "glx" [ 4026.355] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 4026.355] (II) Modu
nwflag hidenwid : SIOCS80211FLAGS: Invalid argument
FDM48 mode 11g media OFDM48 mode 11g mediaopt hostap media OFDM48 mode 11g mediaopt monitor media OFDM54 mode 11g media OFDM54 mode 11g mediaopt hostap media OFDM54 mode 11g mediaopt monitor media OFDM6 media OFDM6 mediaopt hostap media OFDM6 mediaopt monitor media OFDM9 media OFDM9 mediaopt hostap media OFDM9 mediaopt monitor media OFDM12 media OFDM12 mediaopt hostap media OFDM12 mediaopt monitor media OFDM18 media OFDM18 mediaopt hostap media OFDM18 mediaopt monitor media OFDM24 media OFDM24 mediaopt hostap media OFDM24 mediaopt monitor media OFDM36 media OFDM36 mediaopt hostap media OFDM36 mediaopt monitor media OFDM48 media OFDM48 mediaopt hostap media OFDM48 mediaopt monitor media OFDM54 media OFDM54 mediaopt hostap media OFDM54 mediaopt monitor media DS1 media DS1 mediaopt hostap media DS1 mediaopt monitor media DS2 media DS2 mediaopt hostap media DS2 mediaopt monitor media DS5 media DS5 mediaopt hostap media DS5 mediaopt monitor media DS11 media DS11 mediaopt hostap media DS11 mediaopt monitor -- Alexis de BRUYN
Re: OpenBSD freeze after DRM changes
Hi all, Following up on this: On Thu, Apr 25, 2013 at 08:50:33AM -0300, Daniel Bolgheroni wrote: > Hi misc@, > > after one of the screenshots that include the DRM changes, my laptop > began to freeze after the first boot. Sometimes it freezes at Pentium > Pro MTRR support, but most of the times it freezes no more than 1 minute > after login. > > After reboot, the system runs rock solid. > > dmesg and pcidump included below. > > Anyone experiencing the same? > Thank you. This newer snapshot: OpenBSD 5.3-current (GENERIC.MP) #103: Wed Apr 24 09:33:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP has the same behaviour on my laptop. Maybe three more points maybe worth mentionning (they are not new to this snapshot, but I forgot to mention them in my first email): 1. Booting about one hour and a half after last shutdown leads to the freeze described. 2. When booting for the first time in a while, if I reboot before the machine freezes, the system does not subsequently freeze. 3. The system freezes after a couple of minutes when resuming from suspend. I hope this helps. Alexis
Re: OpenBSD freeze after DRM changes
Hi! > after one of the screenshots that include the DRM changes, my laptop > began to freeze after the first boot. Sometimes it freezes at Pentium > Pro MTRR support, but most of the times it freezes no more than 1 minute > after login. > > After reboot, the system runs rock solid. > > dmesg and pcidump included below. > > Anyone experiencing the same? I experience the same thing since I updated to the snapshot: OpenBSD 5.3-current (GENERIC.MP) #63: Thu Apr 4 09:48:21 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I have been collecting details about each crash for a couple of weeks. The only pattern I can see is the same as what you report: my laptop freezes every first time I start it. After halting it using the power button, starting it again and going through fsck(8), the system works flawlessly. I have tried once to shut it down, pull the power cord and remove the battery, wait some time (< 10 minutes) and start it again: it did not freeze. The laptop freezes when I log in with an X session and when I log in a virtual terminal (ttyC0) and X is not running. Battery or AC or both does not make any difference. When the laptop freezes, it does so within 5 minutes after boot. The dmesg(8) and pcidump(8) of my laptop is appended to this email. I have just updated to a newer snapshot (see below): I can't report on it causing the laptop to freeze yet. If anyone has some insight on possible causes of this, or pointers to start investigating, I would be grateful. I can test patches if helpful. Cheers, Alexis OpenBSD 5.3-current (GENERIC.MP) #103: Wed Apr 24 09:33:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1987788800 (1895MB) avail mem = 1927221248 (1837MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe0010 (44 entries) bios0: vendor LENOVO version "6YET29WW (1.12 )" date 03/05/2010 bios0: LENOVO 01965NG acpi0 at bios0: rev 4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET MCFG APIC BOOT SLIC SSDT SSDT SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) USB0(S3) USB1(S3) USB2(S3) USBR(S3) EHC1(S3) USB3(S3) USB4(S3) EHC2(S3) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) RP06(S4) BLAN(S4) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Genuine Intel(R) CPU U7300 @ 1.30GHz, 1296.95 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,XSAVE,NXE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Genuine Intel(R) CPU U7300 @ 1.30GHz, 1296.75 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,XSAVE,NXE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus 5 (P0P1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus 3 (RP02) acpiprt5 at acpi0: bus -1 (RP03) acpiprt6 at acpi0: bus -1 (RP04) acpiprt7 at acpi0: bus -1 (RP05) acpiprt8 at acpi0: bus 4 (RP06) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 100 degC acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PWRB cpu0: Enhanced SpeedStep 1296 MHz: speeds: 1300, 1200, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1366x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 16 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int 19 ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int 19 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 82801I HD Audio" rev 0x03: msi azalia0: codecs: Conexant/0x5066, Intel/0x2802, us
nxsshd dies when client connecting
Hi Everybody, I am trying to use nxsshd port on my -current machine (in addition to /usr/sbin/sshd): OpenBSD 5.3-current (GENERIC.MP) #0: Fri Mar 8 18:45:36 CET 2013 r...@test.me:/usr/src/sys/arch/i386/compile/GENERIC.MP But when the client is connecting, the daemon dies : # /usr/ports/pobj/nxssh-3.5.0.2/nxssh/nxsshd -4 -p 2 -f /etc/ssh/ssh_config -h /etc/ssh/ssh_host_dsa_key -d debug1: sshd version OpenSSH_4.7p1 debug1: read PEM private key done: type DSA debug1: private host key: #0 type 2 DSA Disabling protocol version 1. Could not load host key debug1: rexec_argv[0]='/usr/ports/pobj/nxssh-3.5.0.2/nxssh/nxsshd' debug1: rexec_argv[1]='-4' debug1: rexec_argv[2]='-p' debug1: rexec_argv[3]='2' debug1: rexec_argv[4]='-f' debug1: rexec_argv[5]='/etc/ssh/ssh_config' debug1: rexec_argv[6]='-h' debug1: rexec_argv[7]='/etc/ssh/ssh_host_dsa_key' debug1: rexec_argv[8]='-d' debug1: Bind to port 2 on 0.0.0.0. Server listening on 0.0.0.0 port 2. debug1: fd 4 clearing O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 debug1: inetd sockets after dupping: 3, 3 Connection from 192.168.0.2 port 44076 debug1: Client protocol version 2.0; client software version OpenSSH_4.7 debug1: match: OpenSSH_4.7 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7 debug1: do_cleanup Does anyone use nxsshd successfully ? Thanks for your help. Regards, -- Alexis de BRUYN
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
On 02.03.2013 19:24, Tobias Ulmer wrote: > Your resolution is 1600*1200*3 bytes (lets ignore whatever protocol the > driver uses, probably not 3 byte words), so 1 full frame update, without > the large USB overhead, means pushing out 5.5MB/s. At just 25fps that is > 138MB/s or around 1.2Gbit/s. > > Now, USB2 has a theoretical bandwidth of 480Mbit/s, DVI has 4Gbit/s > (dedicated, with no protocol that also supports mice and stuff). And > DVI gets replaced by DP (8Gbit/s and more) because it can't keep up. > > Even if OpenBSD was super-awesome at graphics, video and usb (which it > clearly is not), it could not overcome the hardware limitations. Unless > the chip itself could do video decoding in hardware, but that is clearly > not something supported by a framebuffer driver. > > So... no way is this ever going to work. Thanks for the technical clarification. > Your graphics card does nothing here, afaict. It's all purely done on > the CPU. Actually I find it kind of amazing that it works at all... Yes it is ! It is sufficient for me in many cases. -- Alexis de BRUYN
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
HAPE [ 155.778] (II) Initializing built-in extension MIT-SHM [ 155.778] (II) Initializing built-in extension XInputExtension [ 155.778] (II) Initializing built-in extension XTEST [ 155.778] (II) Initializing built-in extension BIG-REQUESTS [ 155.778] (II) Initializing built-in extension SYNC [ 155.778] (II) Initializing built-in extension XKEYBOARD [ 155.778] (II) Initializing built-in extension XC-MISC [ 155.778] (II) Initializing built-in extension SECURITY [ 155.778] (II) Initializing built-in extension XINERAMA [ 155.778] (II) Initializing built-in extension XFIXES [ 155.778] (II) Initializing built-in extension RENDER [ 155.778] (II) Initializing built-in extension RANDR [ 155.778] (II) Initializing built-in extension COMPOSITE [ 155.778] (II) Initializing built-in extension DAMAGE [ 155.813] (II) AIGLX: Screen 0 is not DRI2 capable [ 155.813] (II) AIGLX: Screen 0 is not DRI capable [ 155.813] (EE) AIGLX error: dlopen of /usr/X11R6/lib/modules/dri/swrastg_dri.so failed (File not found) [ 156.115] (II) AIGLX: Loaded and initialized swrast [ 156.115] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 156.115] (II) AIGLX: Screen 1 is not DRI2 capable [ 156.115] (II) AIGLX: Screen 1 is not DRI capable [ 156.115] (EE) AIGLX error: dlopen of /usr/X11R6/lib/modules/dri/swrastg_dri.so failed (File not found) [ 156.115] (II) AIGLX: Loaded and initialized swrast [ 156.115] (II) GLX: Initialized DRISWRAST GL provider for screen 1 [ 156.115] (II) AIGLX: Screen 2 is not DRI2 capable [ 156.115] (II) AIGLX: Screen 2 is not DRI capable [ 156.115] (EE) AIGLX error: dlopen of /usr/X11R6/lib/modules/dri/swrastg_dri.so failed (File not found) [ 156.115] (II) AIGLX: Loaded and initialized swrast [ 156.115] (II) GLX: Initialized DRISWRAST GL provider for screen 2 [ 156.143] [dix] Could not init font path element unix/:7100, removing from list! [ 156.778] (II) config/wscons: checking input device /dev/wskbd [ 156.778] (II) wskbd: using layout fr [ 156.779] (II) LoadModule: "kbd" [ 156.779] (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.so [ 156.792] (II) Module kbd: vendor="X.Org Foundation" [ 156.792]compiled for 1.12.3, module version = 1.6.2 [ 156.792]Module class: X.Org XInput Driver [ 156.792]ABI class: X.Org XInput driver, version 16.0 [ 156.792] (II) Using input driver 'kbd' for '/dev/wskbd' [ 156.792] (**) /dev/wskbd: always reports core events [ 156.792] (**) /dev/wskbd: always reports core events [ 156.792] (**) Option "Protocol" "standard" [ 156.792] (**) Option "XkbRules" "base" [ 156.792] (**) Option "XkbModel" "pc105" [ 156.792] (**) Option "XkbLayout" "fr" [ 156.792] (II) XINPUT: Adding extended input device "/dev/wskbd" (type: KEYBOARD, id 6) [ 156.860] (II) config/wscons: checking input device /dev/wsmouse [ 156.860] (II) LoadModule: "ws" [ 156.861] (II) Loading /usr/X11R6/lib/modules/input/ws_drv.so [ 156.885] (II) Module ws: vendor="X.Org Foundation" [ 156.885]compiled for 1.12.3, module version = 1.3.0 [ 156.885]Module class: X.Org XInput Driver [ 156.885]ABI class: X.Org XInput driver, version 16.0 [ 156.885] (II) Using input driver 'ws' for '/dev/wsmouse' [ 156.885] (**) /dev/wsmouse: always reports core events [ 156.885] (II) ws: /dev/wsmouse: debuglevel 0 [ 156.885] (**) Option "Device" "/dev/wsmouse" [ 156.885] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5 [ 156.885] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7 [ 156.885] (**) ws: /dev/wsmouse: associated screen: 0 [ 156.885] (II) ws: /dev/wsmouse: minimum x position: 0 [ 156.885] (II) ws: /dev/wsmouse: maximum x position: 1919 [ 156.885] (II) ws: /dev/wsmouse: minimum y position: 0 [ 156.885] (II) ws: /dev/wsmouse: maximum y position: 1079 [ 156.885] (==) ws: /dev/wsmouse: Buttons: 7 [ 156.885] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5 [ 156.885] (II) XINPUT: Adding extended input device "/dev/wsmouse" (type: MOUSE, id 7) [ 156.886] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1 [ 156.886] (**) /dev/wsmouse: (accel) acceleration profile 0 [ 156.886] (**) /dev/wsmouse: (accel) acceleration factor: 2.000 [ 156.886] (**) /dev/wsmouse: (accel) acceleration threshold: 4 [ 3767.061] damage command failed, giving up! -- Alexis de BRUYN
