Re: TCL in a chroot
> have you run ldconfig? ... > that should create /var/www/var/run/ld.so.hints which aids the linker in > locating the shared libs. Thanks Dan, I hadn't.
Re: TCL in a chroot
On Mon, 28 Dec 2015 19:53:47 -0500 Paul Pereira wrote:
> Has anyone had luck running tcl within a chroot? I have the required
> libraries reported by ldd in place, but the interpreter cannot find
> them.
>
> # chroot /var/www /usr/local/bin/tclsh8.5
> /usr/local/bin/tclsh8.5: can't load library 'libtcl85.so.1.7'
>
> # ldd `which tclsh8.5`
> /usr/local/bin/tclsh8.5:
> StartEnd Type Open Ref GrpRef Name
> 1a646000 3a64a000 exe 10 0 /usr/local/bin/tclsh8.5
> 0c0e6000 2c105000 rlib 01 0 /usr/local/lib/libtcl85.so.1.7
> 0a26d000 2a276000 rlib 02 0 /usr/lib/libm.so.9.0
> 0ce86000 2cea4000 rlib 01 0 /usr/lib/libc.so.80.1
> 02688000 02688000 rtld 01 0 /usr/libexec/ld.so
>
> # ls /var/www/usr/local/lib/libtcl85.so.1.7
> /var/www/usr/local/lib/libtcl85.so.1.7
>
> Regards,
> Paul
>
have you run ldconfig?
i do the following to set up my chroots (_jailroot=/var/www in your case)
sudo mkdir $_jailroot/{sbin,usr/libexec}
sudo cp -p /sbin/ldconfig $_jailroot/sbin
sudo cp -p /usr/libexec/ld.so $_jailroot/usr/libexec
sudo chroot $_jailroot ldconfig /usr/{,X11R6,local}/lib
that should create /var/www/var/run/ld.so.hints which aids the linker in
locating the shared libs.
Re: Panic when copying files
For the archive: I changed the cabling. RW disk on SATA3_A1 RO disk on SATA3_A2 (Instead of the other way around.) Now no more kernel panic.
TCL in a chroot
Has anyone had luck running tcl within a chroot? I have the required libraries reported by ldd in place, but the interpreter cannot find them. # chroot /var/www /usr/local/bin/tclsh8.5 /usr/local/bin/tclsh8.5: can't load library 'libtcl85.so.1.7' # ldd `which tclsh8.5` /usr/local/bin/tclsh8.5: StartEnd Type Open Ref GrpRef Name 1a646000 3a64a000 exe 10 0 /usr/local/bin/tclsh8.5 0c0e6000 2c105000 rlib 01 0 /usr/local/lib/libtcl85.so.1.7 0a26d000 2a276000 rlib 02 0 /usr/lib/libm.so.9.0 0ce86000 2cea4000 rlib 01 0 /usr/lib/libc.so.80.1 02688000 02688000 rtld 01 0 /usr/libexec/ld.so # ls /var/www/usr/local/lib/libtcl85.so.1.7 /var/www/usr/local/lib/libtcl85.so.1.7 Regards, Paul
Re: kernel compile error
On 28.12.2015. 23:44, Hrvoje Popovski wrote:
> Hi,
>
> after fetching source from cvs at 23:40 CET i'm getting this error
> whilte comliling kernel.
>
>
>
> cc -Werror -Wall -Wimplicit-function-declaration -Wno-main
> -Wno-uninitialized -Wframe-larger-than=2047 -mcmode
> l=kernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dnow -mno-mmx
> -msoft-float -fno-omit-frame-pointer -fno-builtin-
> printf -fno-builtin-snprintf -fno-builtin-vsnprintf -fno-builtin-log
> -fno-builtin-log2 -fno-builtin-malloc -fno
> -pie -O2 -pipe -nostdinc -I../../../.. -I. -I../../../../arch -DDDB
> -DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTAT
> S -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
> -DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES
> -DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660
> -DUDF -DMSDOSFS -DFIFO -DTMPFS -DFUSE -DSOC
> KET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC
> -DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -D
> MPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
> -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMP
> AT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
> -DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE
> -DMULTIPROCESSOR -DMAXUSERS=80 -D_KERNEL -MD -MP -c
> ../../../../dev/pci/vga_pci_common.c
> {standard input}: Assembler messages:
> {standard input}:254: Error: no such instruction: `rdseed %rbx'
> *** Error 1 in target 'cpu.o'
> *** Error 1 in /usr/src/sys/arch/amd64/compile/GENERIC.MP (Makefile:938
> 'cpu.o')
>
>
>
>
please ignore .. everything what i need to know is here
http://www.openbsd.org/faq/current.html
under
2015/12/27 - amd64 and i386 support for rdseed instruction
Re: wle200nx WiFi card on apu2b4 - athn0: device timeout
Hello Dániel, thank you for your reply. I changed from PCIe slot 1 to PCie slot 2 - same result. got athn0: device timeout. (Sorry forgot the "n" in error msg in first post) I tried also to set media with - media autoselect - media autoselect mode 11g - media DS1 mode 11g but won't work. I will give -current a try, but that's not the right way for a production system. Friendly regards, Stefan -Ursprüngliche Nachricht- Von: LÉVAI Dániel [mailto:l...@ecentrum.hu] Gesendet: Montag, 28. Dezember 2015 15:10 An: Kapfhammer, Stefan Cc: misc@openbsd.org Betreff: Re: wle200nx WiFi card on apu2b4 - no link Kapfhammer, Stefan @ 2015-12-27T22:44:09 +0100: > Good evening, > > I cannot access hotspot with apu2b4's wle200nx wifi card. > > got ath0: device timeout [...] How come it's not athn? Is this the full and only error message? >From athn(4): athn0: device timeout A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware. This should not happen. Can you try the minipcie card in an other board, or switch minipcie slots? [...] > -> athn0 at pci4 dev 0 function 0 "Atheros AR9281" rev 0x01: apic > -> 4 int 16 > -> athn0: AR9280 rev 2 (2T2R), ROM rev 22, address [...] > # ifconfig > > athn0: flags=8843 mtu 1500 > lladdr > priority: 4 > groups: wlan > media: IEEE802.11 autoselect (OFDM6 mode 11a) > status: no network > ieee80211: nwid chan 9 wpakey 0x > wpaprotos > wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher tkip > > # cat /etc/hostname.athn0 > > nwid TESTNET > wpakey 'Do!Not-deal+w1th-IT' > dhcp I'm using exactly the same minipcie card, in almost the same board (apu1d), only with -current, and in hostap mode. Just off the top of my head, you could try to set media to autoselect, and make sure that you use the right mode: # ifconfig athn0 media [...] supported media: media autoselect media autoselect mediaopt hostap media autoselect mediaopt monitor media autoselect mode 11a media autoselect mode 11a mediaopt hostap media autoselect mode 11a mediaopt monitor media autoselect mode 11b media autoselect mode 11b mediaopt hostap media autoselect mode 11b mediaopt monitor media autoselect mode 11g media autoselect mode 11g mediaopt hostap media autoselect mode 11g mediaopt monitor The one and only problem with my WLE card was that I set the mode to 11g before setting it to a 5GHz channel, and that combo does not exist, and I could not set it back without a reboot. But other than that, it is performing really well, set to 11a and 5GHz. Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
kernel compile error
Hi,
after fetching source from cvs at 23:40 CET i'm getting this error
whilte comliling kernel.
cc -Werror -Wall -Wimplicit-function-declaration -Wno-main
-Wno-uninitialized -Wframe-larger-than=2047 -mcmode
l=kernel -mno-red-zone -mno-sse2 -mno-sse -mno-3dnow -mno-mmx
-msoft-float -fno-omit-frame-pointer -fno-builtin-
printf -fno-builtin-snprintf -fno-builtin-vsnprintf -fno-builtin-log
-fno-builtin-log2 -fno-builtin-malloc -fno
-pie -O2 -pipe -nostdinc -I../../../.. -I. -I../../../../arch -DDDB
-DDIAGNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTAT
S -DPTRACE -DPOOL_DEBUG -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
-DUVM_SWAP_ENCRYPT -DFFS -DFFS2 -DFFS_SOFTUPDATES
-DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DNFSCLIENT -DNFSSERVER -DCD9660
-DUDF -DMSDOSFS -DFIFO -DTMPFS -DFUSE -DSOC
KET_SPLICE -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DINET6 -DIPSEC
-DPPP_BSDCOMP -DPPP_DEFLATE -DPIPEX -DMROUTING -D
MPLS -DBOOT_CONFIG -DUSER_PCICONF -DAPERTURE -DMTRR -DNTFS -DHIBERNATE
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMP
AT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
-DWSDISPLAY_COMPAT_PCVT -DX86EMU -DONEWIREVERBOSE
-DMULTIPROCESSOR -DMAXUSERS=80 -D_KERNEL -MD -MP -c
../../../../dev/pci/vga_pci_common.c
{standard input}: Assembler messages:
{standard input}:254: Error: no such instruction: `rdseed %rbx'
*** Error 1 in target 'cpu.o'
*** Error 1 in /usr/src/sys/arch/amd64/compile/GENERIC.MP (Makefile:938
'cpu.o')
Re: audio capturing
On Dec 28 17:45:40, nightl...@nightbbs.ru wrote: > On 12/28/15 17:21, Jan Stary wrote: > > On Dec 28 16:46:24, nightl...@nightbbs.ru wrote: > >> I want to capture audio from another app to file or simply stdout. How > >> can I do this? > > It woould be easier to help you you just said what "app" it is > > and how it produces "audio". > > i want to capture with ffmpeg from dosbox If you are running sndiod, then dosbox is a client to sndiod. With an appropriate sndiod command line, you should be able to capture all of dosbox's output (or any sound output, for that matter) to a file. You might benefit from reading Alex Ratchov's posts to this list in particular.
System hangs at setting tty flags
Hello, I just did a fresh install with OpenBSD 5.8 and an ASUS motherboard Z97-P The installation went fine but then from the first boot it hangs at "setting tty flags" this is just after the partitions are fsck'edI searched on search engines and found that people running Openbsd as a VM disable the mpbios I did that but no luck, I'm not using Openbsd as a VM, it's running on a physical hardware. Do you have any idea on how to debug this situation ? Thanks
Re: VESA mode
Am Mon, 28 Dec 2015 17:53:45 + schrieb Sébastien Morand : > I'm using the snapshots version in my computer and for about 2 weeks > now I'm stuck in VESA mode. > > I was working pretty well since 26th september for "Intel HD Graphics > 5500" but not anymore, any information about this? http://marc.info/?l=openbsd-cvs&m=145068713628147 |CVSROOT: /cvs |Module name: xenocara |Changes by:kette...@cvs.openbsd.org2015/12/21 01:37:11 | |Modified files: | xserver/hw/xfree86/common: xf86pciBus.c | |Log message: |On Broadwell, default to using the modesetting driver. Our KMS support |on Broadwell is still a bit weak and the modesetting driver seems to |work better than the intel driver, while still providing 3D |acceleration and video playback support. | |ok phessler@, matthieu@, jsg@ You can of course override this in you xorg.conf I prefer the Intel driver too (even if it isn't always stable) so I created a small /etc/X11/xorg.conf: Section "Device" Identifier "Intel" Driver "intel" EndSection
VESA mode
Hi I'm using the snapshots version in my computer and for about 2 weeks now I'm stuck in VESA mode. I was working pretty well since 26th september for "Intel HD Graphics 5500" but not anymore, any information about this? Regards, Sebastien dmesg : OpenBSD 5.9-beta (GENERIC.MP) #1778: Wed Dec 23 18:23:06 MST 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 16884772864 (16102MB) avail mem = 16368922624 (15610MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xacdfd000 (61 entries) bios0: vendor LENOVO version "J5ET43WW (1.14 )" date 02/10/2015 bios0: LENOVO 20DF004UFR acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI acpi0: wakeup devices LID_(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 4 (EXP3) acpiprt4 at acpi0: bus 6 (EXP6) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: AMD3, resource for PEG_ acpipwrres2 at acpi0: AMD2, resource for PEG_ acpitz0 at acpi0: critical temperature is 127 degC acpibtn0 at acpi0: LID_ acpibat0 at acpi0: BAT0 model "LNV-45N1" serial 2079 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 798 MHz: speeds: 2401, 2400, 2300, 2100, 2000, 1900, 1700, 1600, 1400, 1300, 1200, 1000, 900, 800, 600, 500 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 5G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 5500" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1920x1080 wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) azalia0 at pci0 dev 3 function 0 "Intel Core
Re: libGL error: failed to open drm device: Permission denied
Mon, 28 Dec 2015 19:50:42 +0200 Mihai Popescu > But, that file is filled in for ttyC0 only, the tty that most users > are using it for login. But, giving the fact that I got some annoying > kernel messages from my connecting/disconnecting USB mouse with > aggresive power management routines, I was using ttyC1 for login. Similar here, not using anywhere ttyC0, rather tty00 and ttyC1 to ttyC5. Confirmed the /etc/fbtab lines for these ttys worked as expected in these cases. > So the error was not really an error, going back to ttyC0 login I got > the right permission and the messages are no more. Of course I can > edit the /etc/fbtab, too. Interesting if you ssh log in to startx, e.g. ttyp0, does this work in /etc/fbtab and is it expected to in this case? > One question please: is it right that not getting access to /dev/drm0 > is like losing hardware acceleration for applications using it? Yes, on a drm(4) supported device. You could confirm this with the demo glxgears(1).
Binding ^T to status
The installation ramdisk kernel, binds ^T to status by default, which is quite useful. We don't set this up by default on a standard install, though. Admittedly it's easy to add, but is there a reason for it's inclusion in the ramdisk kernel, and not elsewhere? I can understand removing features to reduce kernel site on the installation media, but that clearly doesn't apply in this case. Presumably consistency between terminal behaviour during install and the defaults for a newly installed system is a good thing? -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Re: libGL error: failed to open drm device: Permission denied
Well, things were sorted out. Looking at that /etc/fbtab file Jonathan Gray pointed out (and yes, this is not a typo of /etc/fstab like I thought before) I can spot the /dev/drm0 in that long list of devices prepared for chown at login. But, that file is filled in for ttyC0 only, the tty that most users are using it for login. But, giving the fact that I got some annoying kernel messages from my connecting/disconnecting USB mouse with aggresive power management routines, I was using ttyC1 for login. From that things got another way. I think this clarifies the other issue of changing tty / ownership change mentioned in this thread by somebody else. So the error was not really an error, going back to ttyC0 login I got the right permission and the messages are no more. Of course I can edit the /etc/fbtab, too. One question please: is it right that not getting access to /dev/drm0 is like losing hardware acceleration for applications using it? Thanks.
Re: Mg scroll-up issue in xterm
We are seeing too much of your emails Your rudeness is crass and inappropriate. You are not obliged to read any of my posts to this or any other mailing list. Other people have read them, and that is why, besides other things, certain ports now build correctly with systrace enabled that didn't build before, and the terminfo file actually contains correctly working entries for the framebuffer console. -- Tati Chevron Perl and FORTRAN specialist. SWABSIT development and migration department. http://www.swabsit.com
Adding a new Polish BUG to groups list
Hi misc@, Here is a filled template for a new user group submission. We are based in Poland, and targeting the Podkarpackie Voivodeship. 0 C Poland P Podkarpackie T Rzeszow F Irregular O SBUG I Frederic Cambus M U http://www.sbug.org/ N OpenBSD, *BSD Thanks in advance! Cheers, Frederic
Re: libGL error: failed to open drm device: Permission denied
Mon, 28 Dec 2015 00:25:25 +0200 Mihai Popescu > libGL error: failed to open drm device: Permission denied > libGL error: failed to load driver: r600 > > Is it normal, can it be fixed on my side? Quick and dirty hack around this (if your user is in group wheel): $ grep chmod .xinitrc sudo chmod g+rw /dev/drm0 $ ls -l /dev/drm* Any other suggestions, and moreover proper way to address this?
Re: libGL error: failed to open drm device: Permission denied
> Can you include the output of ls -l /dev/drm0 and > the contents of /var/log/Xorg.0.log ? $ ls -l /dev/drm0 crw--- 1 root wheel 87, 0 Dec 11 20:39 /dev/drm0 $ more /var/log/Xorg.0.log [46.215] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [46.215]linear framebuffer access unavailable [46.221] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [47.345] X.Org X Server 1.17.4 Release Date: 2015-10-28 [47.345] X Protocol Version 11, Revision 0 [47.345] Build Operating System: OpenBSD 5.8 amd64 [47.345] Current Operating System: OpenBSD thinkc.my.domain 5.8 GENERIC.MP#1739 amd64 [47.346] Build Date: 11 December 2015 07:02:02AM [47.346] [47.346] Current version of pixman: 0.32.8 [47.346]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [47.346] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [47.346] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 28 17:22:45 2015 [47.376] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [47.383] (==) No Layout section. Using the first Screen section. [47.383] (==) No screen section available. Using defaults. [47.383] (**) |-->Screen "Default Screen Section" (0) [47.383] (**) | |-->Monitor "" [47.384] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [47.384] (==) Disabling SIGIO handlers for input devices [47.384] (==) Automatically adding devices [47.384] (==) Automatically enabling devices [47.384] (==) Not automatically adding GPU devices [47.488] (==) 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/ [47.488] (==) ModulePath set to "/usr/X11R6/lib/modules" [47.488] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [47.488] (II) Loader magic: 0x10a6b3131ce0 [47.488] (II) Module ABI versions: [47.488]X.Org ANSI C Emulation: 0.4 [47.488]X.Org Video Driver: 19.0 [47.488]X.Org XInput driver : 21.0 [47.488]X.Org Server Extension : 9.0 [47.489] (--) PCI:*(0:1:5:0) 1002:9715:17aa:3082 rev 0, Mem @ 0xd000/268435456, 0xfe90/65536, 0xfe80/1048576, I/O @ 0xe000/256 [47.489] (II) LoadModule: "glx" [47.503] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [47.581] (II) Module glx: vendor="X.Org Foundation" [47.581]compiled for 1.17.4, module version = 1.0.0 [47.581]ABI class: X.Org Server Extension, version 9.0 [47.581] (==) AIGLX enabled [47.582] (==) Matched ati as autoconfigured driver 0 [47.582] (==) Matched vesa as autoconfigured driver 1 [47.582] (==) Assigned the driver to the xf86ConfigLayout [47.582] (II) LoadModule: "ati" [47.582] (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so [47.607] (II) Module ati: vendor="X.Org Foundation" [47.607]compiled for 1.17.4, module version = 7.5.0 [47.607]Module class: X.Org Video Driver [47.607]ABI class: X.Org Video Driver, version 19.0 [47.607] (II) LoadModule: "radeon" [47.608] (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.so [47.626] (II) Module radeon: vendor="X.Org Foundation" [47.626]compiled for 1.17.4, module version = 7.5.0 [47.626]Module class: X.Org Video Driver [47.626]ABI class: X.Org Video Driver, version 19.0 [47.627] (II) LoadModule: "vesa" [47.627] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so [47.636] (II) Module vesa: vendor="X.Org Foundation" [47.636]compiled for 1.17.4, module version = 2.3.3 [47.636]Module class: X.Org Video Driver [47.636]ABI class: X.Org Video Driver, version 19.0 [47.636] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), ATI Radeon Mobility X300 (M24) 3152 (PCIE), ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI), ATI Radeon X600 (RV380) 3E50 (PCIE), ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
Re: Mg scroll-up issue in xterm
> On Sun, Dec 27, 2015 at 06:21:41PM +0200, Timo Myyrä wrote: > I noticed issue with mg scroll-up keybinding when "xterm*locale: > true" is set in ~/.Xresources. > When the above option is set, mg requires that you type C-v C-v to > scroll-up I have this in .Xdefaults and don't have to press any of the scroll keys twice: XTerm*locale: utf8 I also have the locale(1) for character set to this: LC_CTYPE=en_US.UTF-8 > On Sun, Dec 27, 2015 at 06:21:41PM +0200, Timo Myyrä wrote: > instead of single C-v. I'm not sure if this is bug or feature. What date is the snapshot you're running? Here C-v goes down in mg and M-v goes up (as intended), are you using default key bindings for mg? Any window manager / terminal emulator key bindings that might interfere? ---8<--- skip below ---8<--- Accompanying info about scrolling direction. According to the mg(1) man page [1] they should be: C-v scroll-up M-v scroll-down scroll-up Scroll forward one page. A two-line overlap between pages is assumed. If given a repeat argument, scrolls back lines, not pages. scroll-down Scroll backwards n pages. A two-line overlap between pages is assumed. If given a repeat argument, scrolls back lines, not pages. [1]http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/mg.1 If your intuition told you scroll-up would go up, it's the other way in reality, and it goes down. The mg(1) tutorial [2] says this: >> Try using M-v and C-v to move up and down, one page at a time. [2]http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr.bin/mg/tutoria l Again more intuitive would be to have it phrased (as the order you would need them, and the order in which they come on the man page): >> Try using C-v and M-v to move down and up, one page at a time. The man page got them in the right order definition, but the meaning scroll-up going forward (is down) and scroll-down going backward (is up) similar to the Emacs manual [3] quote: You can also scroll explicitly with these commands: C-v next PageDown Scroll forward by nearly a full window (scroll-up-command). M-v prior PageUp Scroll backward (scroll-down-command). C-v (scroll-up-command) scrolls forward by nearly the whole window height. The effect is to take the two lines at the bottom of the window and put them at the top, followed by lines that were not previously visible. If point was in the text that scrolled off the top, it ends up on the window’s new topmost line. The next (or PageDown) key is equivalent to C-v. M-v (scroll-down-command) scrolls backward in a similar way. The prior (or PageUp) key is equivalent to M-v. [3]http://www.gnu.org/software/emacs/manual/html_node/emacs/Scrolling.html Think about rolling a long paper sheet between two drum rolls, so that the scroll-up-command means activate the upper drum of the paper scroll, text goes up, you move forward down the file. One can find this in the CVS tree for mg and probably fix the tutorial page to be more common sense like the man page, and optionally make clearer the man page wording for the directions of movement, though it's not "that" necessary. Sun, 27 Dec 2015 17:37:21 + Tati Chevron > ^V is traditionally used on UNIX like systems to 'insert the next > character literally', for example if you type Control-V, Enter at the > shell, you will produce ^M, or Control-V, Backspace will produce ^? > which is a backspace character. General knowledge, probably not relevant in this case though increases chance you make a mistake suggesting something. Concentrate on the man pages, included docs, FAQs, sources, mailing list threads etc before giving quick common suggestions just to say something, even if this is correct. Sun, 27 Dec 2015 17:37:21 + Tati Chevron > This is what you are seeing, the first Control-v is swallowed before > reaching mg. How are you sure this is what's happening, have you debugged this in reality, can you point code sections responsible for this? Please try it first before advising. Try to replicate it. We are seeing too much of your emails in every other thread, Mr. Tati Chevron, looks more like an advertisement for your employment company in the email signature all over the place, on the OpenBSD mailing lists like a know it all but did not participate in it person. Please don't respond to this challenge, act accordingly.
Re: Panic when copying files
I tried EFI for a change. Same panic there:
# time cp -R /mnt/BackupDisk/Tag.0/a/b/c/* /home/c
panic: kernel diagnostic assertin "(cmd & AHCI_PREG_CMD_CR) == 0"
failed: files "../../../../dev/ic/ahci.c", line 2513
wsdisplay_switch2: not switching
Stopped at Debugger+0x9: leave
TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ahci_port_read_ncp_error() at ahci_port_read_ncp_error+0x251
ahci_port_intr() at ahci_port_intr+0x73c
ahci_intr() at ahci_intr+0x5b
intr_handler() at intr_handler+0x67
Xintr_ioapic_edge23() at Xintr_ioapic_ewdsgdei2s3p+10axyc_9s
h-i-n-g tc
h-i-n-g interrupt ---tc
tacchp2i:c pnuo_ti dslwei(t)c haitn ga
dw 2
:c pnuo_ti dslwei_tccyhcilneg(
cle+0x10 y
end trace frame: 0x0, count: 5
ddb{0}> trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ahci_port_read_ncp_error() at ahci_port_read_ncp_error+0x251
ahci_port_intr() at ahci_port_intr+0x73c
ahci_intr() at ahci_intr+0x5b
intr_handler() at intr_handler+0x67
Xintr_ioapic_edge23() at Xintr_ioapic_edge23+0xc9
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: -10
ddb{0}> mach ddbcpu 1
Stopped at Debugger+0x9: leave
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi()at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: 10
ddb{1}> trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: -5
ddb{1}> mach ddbcpu 2
Stopped at Debugger+0x9: leave
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi()at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: 10
ddb{2}> trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: -5
ddb{2}> mach ddbcpu 3
Stopped at Debugger+0x9: leave
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi()at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: 10
ddb{3}> trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1c
--- interrupt ---
acpicpu_idle() at acpicpu_idle+0x22d
cpu_idle_cycle() at cpu_idle_cycle+0x10
end trace frame: 0x0, count: -5
ddb{3}> ps
TID PPID PGRPUID S FLAGS WAIT COMMAND
8960 15339 8960 0 3 0x3 bioait cp
16465 18320 16465 0 30x83 poll systat
26860 0 0 0 3 0x14200 bored srdis
22457 1 22457 0 30x100083 ttyin getty
10940 1 10940 0 30x100083 ttyin getty
30641 1 30641 0 30x100083 ttyin getty
18320 1 18320 0 30x10008b pause ksh
15339 1 15339 0 30x10008b pause ksh
2381 1 2381 0 30x100098 pool cron
14885 1 14885 99 30x100090 pool sndiod
25921 1 25921110 30x100090 pool sndiod
19894 26249 26249 95 30x100090 kqread smtpd
19281 26249 26249 95 30x100090 kqread smtpd
10089 26249 26249 95 30x100090 kqread smtpd
25084 26249 26249 95 30x100090 kqread smtpd
24862 26249 26249 95 30x100090 kqread smtpd
15496 26249 26249103 30x100090 kqread smtpd
26249 1 26249 0 30x100090 kqread smtpd
16966 1 16966 0 30x80 select sshd
22068 28619 22385 83 30x100090 poll ntpd
28619 22385 22385 83 30x100090 poll ntpd
22385 1 22385 0 30x100080 poll ntpd
9328 28932 28932 74 30x100090 bpfpflogd
28932 1 28932 0 30x80 netio pflogd
5510 9277 9277 73 30x100090 kqread syslogd
9277 1 9277 0 30x100080 netio syslogd
12989 1 12989 77 30x100090 poll dhclient
28690 1 28690 0 30x80 poll dhclient
23316 0 0 0 3 0x14200 pgzero zerothread
2296 0 0 0 3 0x14200 a
Re: audio capturing
On 12/28/15 17:21, Jan Stary wrote: > On Dec 28 16:46:24, nightl...@nightbbs.ru wrote: >> I want to capture audio from another app to file or simply stdout. How >> can I do this? > It woould be easier to help you you just said what "app" it is > and how it produces "audio". i want to capture with ffmpeg from dosbox (no, internal dosbox capture don't need)
Re: audio capturing
On Dec 28 16:46:24, nightl...@nightbbs.ru wrote: > I want to capture audio from another app to file or simply stdout. How > can I do this? It woould be easier to help you you just said what "app" it is and how it produces "audio".
Re: wle200nx WiFi card on apu2b4 - no link
Kapfhammer, Stefan @ 2015-12-27T22:44:09 +0100: > Good evening, > > I cannot access hotspot with apu2b4's wle200nx wifi card. > > got ath0: device timeout [...] How come it's not athn? Is this the full and only error message? >From athn(4): athn0: device timeout A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware. This should not happen. Can you try the minipcie card in an other board, or switch minipcie slots? [...] > -> athn0 at pci4 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 4 int 16 > -> athn0: AR9280 rev 2 (2T2R), ROM rev 22, address [...] > # ifconfig > > athn0: flags=8843 mtu 1500 > lladdr > priority: 4 > groups: wlan > media: IEEE802.11 autoselect (OFDM6 mode 11a) > status: no network > ieee80211: nwid chan 9 wpakey 0x wpaprotos > wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher tkip > > # cat /etc/hostname.athn0 > > nwid TESTNET > wpakey 'Do!Not-deal+w1th-IT' > dhcp I'm using exactly the same minipcie card, in almost the same board (apu1d), only with -current, and in hostap mode. Just off the top of my head, you could try to set media to autoselect, and make sure that you use the right mode: # ifconfig athn0 media [...] supported media: media autoselect media autoselect mediaopt hostap media autoselect mediaopt monitor media autoselect mode 11a media autoselect mode 11a mediaopt hostap media autoselect mode 11a mediaopt monitor media autoselect mode 11b media autoselect mode 11b mediaopt hostap media autoselect mode 11b mediaopt monitor media autoselect mode 11g media autoselect mode 11g mediaopt hostap media autoselect mode 11g mediaopt monitor The one and only problem with my WLE card was that I set the mode to 11g before setting it to a 5GHz channel, and that combo does not exist, and I could not set it back without a reboot. But other than that, it is performing really well, set to 11a and 5GHz. Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
audio capturing
Hello! I want to capture audio from another app to file or simply stdout. How can I do this? Thanks.
ospfd 224.0.0.5: Can't assign requested address on rdomain 2
Hello!
I created a simple ospf test lab, but i ran into the following error:
The setup:
ospfd.conf
rdomain 2
area 0.0.0.0 {
interface vio2
}
route -T2 -n show
Routing tables
Internet:
DestinationGatewayFlags Refs Use Mtu Prio
Iface
default127.0.0.1 UGBS 00 32768 8 lo2
127/8 127.0.0.1 UGRS 00 32768 8 lo2
127.0.0.1 127.0.0.1 UHl09 32768 1 lo2
172.16.2/24172.16.2.1 UC 00 - 4 vio2
172.16.2.1 08:00:27:1b:ce:55 UHLl 05 - 1 vio2
172.16.2.255 172.16.2.1 UHb00 - 1 vio2
224/4 127.0.0.1 URS00 32768 8 lo2
ifconfig
lo0: flags=8049 mtu 32768
priority: 0
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet 127.0.0.1 netmask 0xff00
vio0: flags=8843 mtu 1500
lladdr 08:00:27:48:6a:16
priority: 0
groups: egress
media: Ethernet autoselect
status: active
inet 10.0.2.15 netmask 0xff00 broadcast 10.0.2.255
vio1: flags=8843 mtu 1500
lladdr 08:00:27:e8:94:dc
priority: 0
media: Ethernet autoselect
status: active
inet 192.168.56.11 netmask 0xff00 broadcast 192.168.56.255
vio2: flags=8843 rdomain 2 mtu 1500
lladdr 08:00:27:1b:ce:55
priority: 0
media: Ethernet autoselect
status: active
inet 172.16.2.1 netmask 0xff00 broadcast 172.16.2.255
enc0: flags=0<>
priority: 0
groups: enc
status: active
pflog0: flags=141 mtu 33144
priority: 0
groups: pflog
lo2: flags=8049 rdomain 2 mtu 32768
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff00
ospfd -dvv -f /etc/ospfd2.conf
WARNING: IP forwarding NOT enabled, running as stub router
password = "secret"
warning: macro 'password' not used
startup
if_join_group: error IP_ADD_MEMBERSHIP, interface vio2 address 224.0.0.5:
Can't assign requested address
if_fsm: error changing state for interface vio2, event UP, state DOWN
error starting interface vio2
ospfctl show interfaces
Interface AddressState HelloTimer Linkstate Uptimenc ac
vio2172.16.2.1/24 DOWN - active 00:00:00 0 0
ospfctl show fib
flags: * = valid, O = OSPF, C = Connected, S = Static
Flags Prio Destination Nexthop
*S8 0.0.0.0/0127.0.0.1
*C0 127.0.0.0/8 link#0
*S8 127.0.0.0/8 127.0.0.1
* 1 127.0.0.1/32 127.0.0.1
*C4 172.16.2.0/24link#3
*S8 224.0.0.0/4 127.0.0.1
ospfctl show summary
Router ID: 10.0.2.15
Uptime: 00:01:33
RFC1583 compatibility flag is disabled
SPF delay is 1000 msec(s), hold time between two SPFs is 5000 msec(s)
Number of external LSA(s) 0 (Checksum sum 0x0)
Number of areas attached to this router: 1
Area ID: 0.0.0.0
Number of interfaces in this area: 1
Number of fully adjacent neighbors in this area: 0
SPF algorithm executed 0 time(s)
Number LSA(s) 0 (Checksum sum 0x0)
I miss something, or this is a bug?
Thx
Godot
OpenBSD 5.9-beta (GENERIC) #1658: Sun Dec 27 17:03:23 MST 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 520028160 (495MB)
avail mem = 500244480 (477MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries)
bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006
bios0: innotek GmbH VirtualBox
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz, 2594.82 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,RDRAND,HV,NXE,LONG,LAHF,ABM,ITSC
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: CPU supports MTRRs but not enabled by BIOS
cpu0: apic clock running at 1000MHz
cpu0: mwait min=64, max=64
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpibat0 at acpi0: BAT0 model "1" serial 0 type VBOX oem "innotek"
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: GFX0
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 d
Re: Mg scroll-up issue in xterm
Christian Weisgerber writes: > On 2015-12-27, Timo Myyrä wrote: > >> I noticed issue with mg scroll-up keybinding when "xterm*locale: true" is set in >> ~/.Xresources. >> When the above option is set, mg requires that you type C-v C-v to scroll-up >> instead of single C-v. I'm not sure if this is bug or feature. > > That would be a bug, but I can't reproduce this. Just did a bit more testing. After stripping my ~/.Xresources to following: xterm*loginShell: true xterm*locale: utf-8 And using 'xrdb ~/.Xresources', opening new xterm I get the expected behaviour. If I change the config 's/utf-8/true/', use xrdb to update settings and open new Xterm I get the odd behaviour. It doesn't seem to be mg specific. The Xterm itself shows this. With first config the key combination "^v^m" inserts literal ^M to shell. With latter config shell does new line as though ^v never happened. By looking at Xterm man page seems that locale:true assumes all input is utf-8 encoded already, with locale:utf-8 xterm uses luit to convert input to utf-8 with it. So input given to xterm isn't utf-8 on OpenBSD and needs luit to convert it? Timo
