Re: Questions and *little* bugs in new vt(9)
Hello, 2014-05-09 18:48 GMT+09:00 David Demelier demelier.da...@gmail.com: On 08/05/2014 17:09, Ed Maste wrote: On 8 May 2014 04:16, David Demelier demelier.da...@gmail.com wrote: Hi there, I'm currently trying vt(9) on a CURRENT kernel (only the kernel not the base). I have very small bugs, not really serious. I'm currently using the radeon KMS driver. * When I don't use the native resolution (i.e the radeon firmwares are not loaded) switching from a tty to another results sometimes in a black screen when only some colors are displayed. This does not seems to appear when the native resolution is set. Can you describe the corruption in some more detail, or share a picture of it? I haven't observed something like this with stock vt, and the vt_vga driver. I also have similar display corruption when I switch between ttys. The monitor sometime become black screen with only cursor displayed, or sometimes get messed like this picture: https://dl.dropboxusercontent.com/u/16075585/FreeBSD/vt_20140509.jpg Toggling between ttys a few times get things normal, so it is not really a problem. I see it on current r265145 and stable/10 r265146. the (head of) dmesg for the PC running stable/10 is: Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-STABLE #28 r265146: Thu May 8 00:46:23 JST 2014 root@:/usr/obj/usr/src/sys/OIKUMENE i386 FreeBSD clang version 3.4 (tags/RELEASE_34/final 197956) 20140216 CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1608.03-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106c2 Family = 0x6 Model = 0x1c Stepping = 2 Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40c39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE AMD Features=0x10NX AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147483648 (2048 MB) avail memory = 2081185792 (1984 MB) Event timer LAPIC quality 400 ACPI APIC Table: A_M_I_ OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 WARNING: VIMAGE (virtualized network stack) is a highly experimental feature. ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x0820/0x0 (20130823/tbfadt-630) ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0, using default 8 (20130823/tbfadt-682) ioapic0: Changing APIC ID to 2 ioapic0 Version 2.0 irqs 0-23 on motherboard random: Software, Yarrow initialized kbd0 at kbdmux0 acpi0: A_M_I_ OEMXSDT on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7f70 (3) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 450 Event timer HPET1 frequency 14318180 Hz quality 440 Event timer HPET2 frequency 14318180 Hz quality 440 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0xec80-0xec87 mem 0xfeb8-0xfebf,0xd000-0xdfff,0xfeb4-0xfeb7 irq 16 at device 2.0 on pci0 agp0: Intel 945GME SVGA controller on vgapci0 agp0: aperture size is 256M, detected 7932k stolen memory vgapci0: Boot video device vgapci1: VGA-compatible display mem 0xfea8-0xfeaf at device 2.1 on pci0 hdac0: Intel 82801G HDA Controller mem 0xfeb38000-0xfeb3bfff irq 16 at device 27.0 on pci0 pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci4: ACPI PCI bus on pcib1 re0: RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet port 0xdc00-0xdcff mem 0xfe8ff000-0xfe8f,0xbfef-0xbfef irq 16 at device 0.0 on pci4 re0: Using 1 MSI-X message re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:23:54:c6:c1:12 pcib2: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci3:
Re: Questions and *little* bugs in new vt(9)
On 08/05/2014 17:09, Ed Maste wrote: On 8 May 2014 04:16, David Demelier demelier.da...@gmail.com wrote: Hi there, I'm currently trying vt(9) on a CURRENT kernel (only the kernel not the base). I have very small bugs, not really serious. I'm currently using the radeon KMS driver. * When I switch from a tty to X I can see the mouse appearing but the tty is still displayed until I move the mouse. Or until I wait something like 3 seconds. It sounds like a small refresh trouble. Interesting. On my stable/9 desktop with i915kms I can't reproduce this; after switching back to X the previous display is restored, and then a redraw happens, within a few hundred mS. I do see it on my laptop, which also has i915kms but newer software (recent CURRENT, and newer xorg packages). I'll see if I can gather more information at BSDCan next week. Funny, I can't reproduce the bug neither. I've removed some parts from my xorg.conf, maybe the problem came from here. * When I don't use the native resolution (i.e the radeon firmwares are not loaded) switching from a tty to another results sometimes in a black screen when only some colors are displayed. This does not seems to appear when the native resolution is set. Can you describe the corruption in some more detail, or share a picture of it? I haven't observed something like this with stock vt, and the vt_vga driver. Yes, I've recorded a video [1]. Please note again that I can reproduce this bug only when I don't have any firmware loaded / KMS enabled. I just boot with stock vt and vt_vga enabled. In the video I've successfully reproduced the bug two times by switching ttys at around 0:25 when you can see just the cursor shown and also at 0:40 where you can see some garbage colors which came from vim. You can also notice that sometimes switching from one to other displays some artifacts until it is refreshed. And some questions: * Will you add support for dead keys? I have a UK keyboard and when I want to write french characters like à ô ê I usually press the ` character then a. This isn't currently planned, but I'll keep it in mind if I look into future work on the keyboard input path. I hope for :-). [1] http://www.demelierdavid.fr/files/vt.mp4 Regards, David. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Questions and *little* bugs in new vt(9)
Hi there, I'm currently trying vt(9) on a CURRENT kernel (only the kernel not the base). I have very small bugs, not really serious. I'm currently using the radeon KMS driver. * When I switch from a tty to X I can see the mouse appearing but the tty is still displayed until I move the mouse. Or until I wait something like 3 seconds. It sounds like a small refresh trouble. * When I don't use the native resolution (i.e the radeon firmwares are not loaded) switching from a tty to another results sometimes in a black screen when only some colors are displayed. This does not seems to appear when the native resolution is set. And some questions: * Will you add support for dead keys? I have a UK keyboard and when I want to write french characters like à ô ê I usually press the ` character then a. Same for ^ then o and e. To accomplish this, I use the extd variant in Xorg. This let me to press the dead ` character before a. It would be great to add this support to the vt (or maybe it is already done but I was not able to modify .kdb files to support that). Thanks for your great work on vt(9) and I'm very happy to have full unicode support and a quick tty switch :-). PS: this is more a personal opinion, but I really prefer the syscons font rather than the vt(9)'s one. Regards, David. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Questions and *little* bugs in new vt(9)
On 8 May 2014 04:16, David Demelier demelier.da...@gmail.com wrote: Hi there, I'm currently trying vt(9) on a CURRENT kernel (only the kernel not the base). I have very small bugs, not really serious. I'm currently using the radeon KMS driver. * When I switch from a tty to X I can see the mouse appearing but the tty is still displayed until I move the mouse. Or until I wait something like 3 seconds. It sounds like a small refresh trouble. Interesting. On my stable/9 desktop with i915kms I can't reproduce this; after switching back to X the previous display is restored, and then a redraw happens, within a few hundred mS. I do see it on my laptop, which also has i915kms but newer software (recent CURRENT, and newer xorg packages). I'll see if I can gather more information at BSDCan next week. * When I don't use the native resolution (i.e the radeon firmwares are not loaded) switching from a tty to another results sometimes in a black screen when only some colors are displayed. This does not seems to appear when the native resolution is set. Can you describe the corruption in some more detail, or share a picture of it? I haven't observed something like this with stock vt, and the vt_vga driver. And some questions: * Will you add support for dead keys? I have a UK keyboard and when I want to write french characters like à ô ê I usually press the ` character then a. This isn't currently planned, but I'll keep it in mind if I look into future work on the keyboard input path. PS: this is more a personal opinion, but I really prefer the syscons font rather than the vt(9)'s one. I've been using vt for about six months and am now used to the default vt font -- the VGA ROM font looks odd to me now. However, I believe the primary motivation behind the font choice was the glyph coverage. I now have a vt-compatible version of the VGA ROM font, but it only has about half of the characters. vt default font: Count % RangeDescription - - --- 95 74% 007F Basic Latin 96 75% 0080 00FF Latin-1 Supplement 126 98% 0100 017F Latin Extended-A 15 7% 0180 024F Latin Extended-B 6 6% 0250 02AF IPA Extensions 10 12% 02B0 02FF Spacing Modifier Letters 7 6% 0300 036F Combining Diacritical Marks 74 51% 0370 03FF Greek 168 66% 0400 04FF Cyrillic 14 5% 1E00 1EFF Latin Extended Additional 38 34% 2000 206F General Punctuation 1 2% 2070 209F Superscripts and Subscripts 3 6% 20A0 20CF Currency Symbols 5 6% 2100 214F Letterlike Symbols 14 12% 2190 21FF Arrows 19 7% 2200 22FF Mathematical Operators 8 3% 2300 23FF Miscellaneous Technical 6 9% 2400 243F Control Pictures 101 79% 2500 257F Box Drawing 24 75% 2580 259F Block Elements 12 12% 25A0 25FF Geometric Shapes 11 4% 2600 26FF Miscellaneous Symbols 1 6% FFF0 Specials Converted cp437-8x16 font: Count % RangeDescription - - --- 98 77% 007F Basic Latin 55 43% 0080 00FF Latin-1 Supplement 1 0% 0180 024F Latin Extended-B 12 8% 0370 03FF Greek 2 2% 2000 206F General Punctuation 1 2% 2070 209F Superscripts and Subscripts 1 2% 20A0 20CF Currency Symbols 7 6% 2190 21FF Arrows 9 4% 2200 22FF Mathematical Operators 4 2% 2300 23FF Miscellaneous Technical 40 31% 2500 257F Box Drawing 8 25% 2580 259F Block Elements 9 9% 25A0 25FF Geometric Shapes 11 4% 2600 26FF Miscellaneous Symbols I expect to commit the converted font soon, and it'll be loadable at runtime. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
