Re: /bsd: thread: table is full

2022-02-16 Thread Alexis de BRUYN
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/mess

/bsd: thread: table is full

2022-02-14 Thread Alexis de BRUYN
=0 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets sd1 at scsibus3 targ 1 lun 0: sd1: 424961MB, 512 bytes/sector, 870320783 sectors root on sd1a (3f0d06aece990c6b.a) swap on sd1b dump on sd1b radeondrm0: PITCAIRN radeondrm0: 1920x1080, 32bpp wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0 wskbd1: connecting to wsdisplay0 wskbd2: connecting to wsdisplay0 wskbd3: connecting to wsdisplay0 wsdisplay0: screen 1-5 added (std, vt100 emulation) thread: table is full thread: table is full thread: table is full thread: table is full -- Alexis de BRUYN

Re: iwn0: no link after 6.1 upgrade

2017-08-19 Thread Alexis de BRUYN
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" &q

Re: iwn0: no link after 6.1 upgrade

2017-08-19 Thread Alexis de BRUYN
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

Re: iwn0: no link after 6.1 upgrade

2017-08-19 Thread Alexis de BRUYN
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.

iwn0: no link after 6.1 upgrade

2017-08-19 Thread Alexis de BRUYN
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: error: [drm:pid10679:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle

2016-10-10 Thread Alexis de BRUYN
ver 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

2016-10-01 Thread Alexis de BRUYN
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?)

2015-12-12 Thread Alexis de BRUYN
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 (

Pictures are "blurred" in certain cases after snapshot upgrade (radeonrdrm related?)

2015-12-11 Thread Alexis de BRUYN
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 butto

Re: Octeon snapshots

2015-12-09 Thread Alexis de BRUYN
/octeon/usr/mips64-unknown-openbsd5.8/bin/objcopy Thank you Paul. bsd.rd is now booting. -- Alexis de BRUYN

Re: Octeon snapshots

2015-12-09 Thread Alexis de BRUYN
ay 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

Xenocara/radeonsi_dri.so build failed on -current

2015-06-13 Thread Alexis de BRUYN
*** 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)

2015-06-11 Thread Alexis de BRUYN
) 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 ?

2014-07-17 Thread Alexis de BRUYN
aults: > 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: radeondrm(4): only 1 screen displaying over 3

2013-09-01 Thread Alexis de BRUYN
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

radeondrm(4): only 1 screen displaying over 3

2013-08-28 Thread Alexis de BRUYN
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 DisplayPo

nwflag hidenwid : SIOCS80211FLAGS: Invalid argument

2013-07-01 Thread Alexis de BRUYN
media DS11 mediaopt hostap media DS11 mediaopt monitor -- Alexis de BRUYN

nxsshd dies when client connecting

2013-03-09 Thread Alexis de BRUYN
penSSH_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

2013-03-02 Thread Alexis de BRUYN
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

2013-03-02 Thread Alexis de BRUYN
85] (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

Xorg + wsudl(4) DL-165 consumes a lot of cpu

2013-03-02 Thread Alexis de BRUYN
0 Hub" rev 2.00/2.88 addr 5 uhidev2 at uhub7 port 3 configuration 1 interface 0 "Microsoft Microsoft 3-Button Mouse with IntelliEye?" rev 2.00/0.00 addr 6 uhidev2: iclass 3/1 ums0 at uhidev2: 3 buttons, Z dir wsmouse0 at ums0 mux 0 uhidev3 at uhub7 port 4 configuration 1 interface 0 "Logitech USB Keyboard" rev 1.10/66.00 addr 7 uhidev3: iclass 3/1 ukbd1 at uhidev3: 8 variable keys, 6 key codes wskbd1 at ukbd1 mux 1 wskbd1: connecting to wsdisplay0 uhidev4 at uhub7 port 4 configuration 1 interface 1 "Logitech USB Keyboard" rev 1.10/66.00 addr 7 uhidev4: iclass 3/0, 3 report ids uhid3 at uhidev4 reportid 1: input=1, output=0, feature=0 uhid4 at uhidev4 reportid 2: input=1, output=0, feature=0 uhid5 at uhidev4 reportid 3: input=3, output=0, feature=0 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets sd0 at scsibus1 targ 1 lun 0: SCSI2 0/direct fixed sd0: 476937MB, 512 bytes/sector, 976767473 sectors root on sd0a (e37ebc54ca3260d7.a) swap on sd0b dump on sd0b clock: unknown CMOS layout softraid0: sd1 was not shutdown properly softraid0: sd1 was not shutdown properly sd1 at scsibus1 targ 2 lun 0: SCSI2 0/direct fixed sd1: 475901MB, 512 bytes/sector, 974646960 sectors -- Alexis de BRUYN

Re: softraid to encrypt _AND_ raid?

2012-11-30 Thread Alexis de BRUYN
-c C -r 8192 -l /dev/sd0d softraid0 sd1 is your raid+crypto device. -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-20 Thread Alexis de BRUYN
On 14.08.2012 23:57, Matthieu Herrb wrote: > On Tue, Aug 14, 2012 at 10:35:40PM +0200, Alexis de BRUYN wrote: >> On 14.08.2012 17:58, Matthieu Herrb wrote: >>> On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote: >>>> On Tue, Aug 14, 2012 at 10:31:24A

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Alexis de BRUYN
On 14.08.2012 17:58, Matthieu Herrb wrote: > On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote: >> On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote: >>> On 13.08.2012 23:34, Matthieu Herrb wrote: >>>> On Sun, Aug 12, 2012 at 10:04:17P

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Alexis de BRUYN
On 13.08.2012 23:34, Matthieu Herrb wrote: > On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote: >> On 11.08.2012 23:33, Alexis de BRUYN wrote: >> I still have my previous issue, but I have another one : while the >> in-board display device is actived through

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-12 Thread Alexis de BRUYN
On 11.08.2012 23:33, Alexis de BRUYN wrote: > # wsconsctl -f /dev/ttyC0 display.type > display.type=vga-pci > # wsconsctl -f /dev/ttyD0 display.type > display.type=displaylink > # wsconsctl -f /dev/ttyE0 display.type > display.type=displaylink I still have my previous issue,

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-11 Thread Alexis de BRUYN
rev 2.00/0.03 addr 4 no data for est. mode 832x768x74 no data for est. mode 640x480x67 no data for est. mode 720x400x70 max_dotclock according to supported modes: 162000 wsdisplay1 at udl0 mux 1 wsdisplay1: screen 0 added (std, vt100 emulation) udl1 at uhub6 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 5 no data for est. mode 832x768x74 no data for est. mode 640x480x67 no data for est. mode 720x400x70 max_dotclock according to supported modes: 162000 wsdisplay2 at udl1 mux 1 wsdisplay2: screen 0 added (std, vt100 emulation) vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (388f307771acfa52.a) swap on wd0b dump on wd0b clock: unknown CMOS layout -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-11 Thread Alexis de BRUYN
Thanks for your help. -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-11 Thread Alexis de BRUYN
On 02.08.2012 22:31, Alexis de BRUYN wrote: > On 02.08.2012 21:48, Matthieu Herrb wrote: >> >> This is the xorg.conf I use to test wsudl: >> >> Section "Devicë >> Identifier "Card0" >> Driver "wsudl" >>

OpenBSD & USB display experience

2012-08-07 Thread Alexis de BRUYN
://www.mail-archive.com/misc@openbsd.org/msg114982.html. Does anybody have a working configuration with an "USB Display" ? Thanks for sharing your experience, -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-04 Thread Alexis de BRUYN
*_edid_modes[] = { "1920x1080px60", "1920x1080x60", "1280x1024x60", And rebuilt the kernel. But again same error. Thanks again for your help Mats. -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-03 Thread Alexis de BRUYN
and rebuilt as you mentionned, but unfortunately, I have the same error message. Regards, -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-02 Thread Alexis de BRUYN [Mailinglists]
my problem. UDL(4) mentions that : DESCRIPTION The udl driver supports USB display devices based on the DisplayLink DL-120 / DL-160 graphic chip. Regards, -- Alexis de BRUYN

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-02 Thread Alexis de BRUYN [Mailinglists]
> Could this be related to the space preceding in the device declaration? > Option "device" "/ dev/wsdisplay1" --> Option "device" "/dev/wsdisplay1" Thanks for your reply, Вовочка, but this is a typo mistake I have made while I write my mail. -- Alexis de BRUYN

DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-02 Thread Alexis de BRUYN [Mailinglists]
66.380] (II) UnloadModule: "wsudl" [66.380] (EE) Screen(s) found, but none have a usable configuration. - I have found another post, http://permalink.gmane.org/gmane.os.openbsd.misc/174164, but it is not resolved. Does anyone have this device (or other usb2dvi) working ? Thanks for your help. Alex. -- Alexis de BRUYN

Re: Raid + OpenBSD Problem

2009-04-21 Thread Alexis de BRUYN
I had some help > from a few people, specifically Alexis de BRUYN who frequents this list > often, but I never managed to get it working. Basically what happened was it > would seam to work all the way up to copying the data and parity using these > two commands; > > > >

Re: FW: raidctl -vF component0 raid0

2009-04-14 Thread Alexis de BRUYN
back; > Raid0: Autoconfigure: Yes > Raid0: Root: Yes > > So that's seams present and correct. I am guessing I make it autoconfig then > do newfs on the parts? But then I guess it doesn't matter which way round it > happens does it? Well I did it after newfs and it displayed s

Re: FW: raidctl -vF component0 raid0

2009-04-02 Thread Alexis de BRUYN
can not read metadata version 8, expected 3 > softraid0: raid0i can not read metadata version 8, expected 3 > root on raid0a > filesystem type 19 not known.. assuming ffs > WARNING: / was not properly unmounted > swapmount: no device > raid0: Error re-writing parity! > > Chris

Re: raidctl -vF component0 raid0

2009-04-02 Thread Alexis de BRUYN
then changing device letters so I left it on. But I get the same results > weather I use AHCI or not just using sd0 sd1 or wd0 wd1. > > So, sorry, just a typo there! > > Chris > > -Original Message- > From: Alexis de BRUYN [mailto:ale...@de-bruyn.fr] > Sent

Re: FW: raidctl -vF component0 raid0

2009-04-02 Thread Alexis de BRUYN
uot; instead of "4.2BSD". Chris Harries a icrit : > All typoes checked. Now correct...finally, > > Apologies > > Chris > > -Original Message- > From: Chris Harries [mailto:ch...@sharescope.co.uk] > Sent: 02 April 2009 14:07 > To: 'Alex

Re: raidctl -vF component0 raid0

2009-04-02 Thread Alexis de BRUYN
0 > > Which seams fine with me. Did you following a guide to teach your self this? > I have tried reading over man raidctl but it's now showing me anything more > then I know already and what I am not doing correct to cause this > reconstruction to just hang...? Any ideas > >

Re: raidctl -vF component0 raid0

2009-04-02 Thread Alexis de BRUYN
> /dev/raid0e /var/vmail ffs rw 1 2 > /dev/raid0f /var ffs rw 1 2 > /dev/raid0g /tmp ffs rw 1 2 > /dev/raid0h /usr ffs rw 1 2 > /dev/raid0i /home ffs rw 1 2 > EOF > > Umount partitions and reboot: > umount /mnt/*; umount /mnt > halt (reboot) > > boot> boot sd1a

Re: raidctl -vF component0 raid0

2009-03-31 Thread Alexis de BRUYN
> To: Chris Harries > Cc: misc@openbsd.org > Subject: Re: raidctl -vF component0 raid0 > > On Mon, 30 Mar 2009 09:43:31 +0100 "Chris Harries" > wrote: > >> START disks >> /dev/wd2b # the fake device >> /dev/wd1b >> > > The abo

Re: Issues with ntpd on openbsd 3.7-stable (not running ?)

2005-08-10 Thread Alexis de BRUYN
l local time is correct. I'll see later. -- Alexis de BRUYN email : [EMAIL PROTECTED] web : http://www.de-bruyn.fr >-Message d'origine- >De : Simon Farnsworth [mailto:[EMAIL PROTECTED] >Envoyi : jeudi 11 ao{t 2005 00:14 >@ : Alexis de BRUYN; misc@openbsd.org >Obj

Issues with ntpd on openbsd 3.7-stable (not running ?)

2005-08-10 Thread Alexis de BRUYN
279]: no server suitable for synchronization found I guess 2036 seems no response from the ntpd. Does anyone can help me please? Best regards, -- Alexis de BRUYN email : [EMAIL PROTECTED] web : http://www.de-bruyn.fr

Re: openbsd 3.7 in-kernel pppoe issues

2005-08-03 Thread Alexis de BRUYN
Try to remove your /etc/mygate if exists. >Hi, > >I have the same problem here in Hungary, running 3.7- >(almost)stable. My ISP is Axelero (T-Online Hungary now) and the >userland ppp worked like a charm. I switched to kernel pppoe but >it only works if I specify the remote peer (gateway) IP addre

Re: openbsd 3.7 in-kernel pppoe issues

2005-08-03 Thread Alexis de BRUYN
't use >it. >but if you have a permanent (static) gateway address, you could >plug >that value into /etc/hostname.pppoe0. i don't think it's your >problem >though. > >jmc -- Alexis de BRUYN email : [EMAIL PROTECTED] web : http://www.de-bruyn.fr >-Messag

openbsd 3.7 in-kernel pppoe issues

2005-08-02 Thread Alexis de BRUYN
uot; mode) is by default, but i try to explicit it on my hostname.pppoe, the connection fails. Does anyone try to do the same setup ? Can you help me please ? Thanks. -- Alexis de BRUYN email : <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] web : <http://www.de-bruyn.fr> http://www.de-bruyn.fr