Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello, @Guido I tried to rebuild the xorg-server but it stoped to recognize all input devices even on Xfce4, I think I'm missing something. Tried to rebuild the xf86-input-evdev too but didn't work either. Had to revert to the pkg version to be able to send this email @Ulf Rudolf Now knowing that the xorg-server is not recognizing any input devices after rebuild the latest version, I have a feeling that this problem is related, maybe the LightDM expects some specific device? My system is a Dell G3 2019 with: 12.1-RELEASE-p2 Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Pkgs: - Xorg 7.7_3 - xorg-server 1.18.4_13,1 (hal is off in the description) - xfce 4.14 Ports: - drm-kmod-g20190710 Thank you, Mario Em ter., 10 de mar. de 2020 às 12:02, Guido Falsi escreveu: > On 10/03/20 13:41, Mario Olofo wrote: > > Hello All, > > In the prccess of making the FreeBSD my main OS, I stumbled on an very > > uncommon problem: the LightDM don't accept any keys, and I can't even get > > out to the tty with ctrl+alt+F1... > > > > I build the drm-kmod from ports, installed Xorg, Xfce4 and LightDM and > > lightdm-gtk-greeter with pkg, and enabled it on rc.conf with > > lightdm_enable="YES". > > On boot, it don't work because the lightdm need to be on video group, so > I > > added it to video groups and then the LightDM screen showed up, but only > > the mouse work. If I press a lot of keys and then use the mouse to > restart > > the system, I can see some garbage input on the first terminal! > > I didn't create a custom X config, but tried to force a input conf to see > > if it was the problem but it appears that the config is not used at all > > when starting LightDM. I rebuild from source the LightDM, but the problem > > persists. When I use startx to go directly to Xfce4 works like a charm. > > > > I'm sorry I don't have much insight about this, but this one (and the > following problem too) looks like a graphics hardware related problem. > > You should share some information about your system, which graphics > adapter and chipset you are using and what driver setup. > > > Then comes the second but less important problem that I found, the topbar > > decorator of windows are not displaying correctly. The background img > > behind the title don't stretch to cover the full width. Anyone had this > > problem before? > > There is a known problem with xfce 4.14 and window decorations on > certain hardware chipsets: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240887 > > It has been recently reported that Xorg server 1.20.7 (available with > the latest package set) fixes the issue. > > This update will reach quarterly packages at the start of April. If > you're willing you could migrate your machine to latest packages and > confirm if this fixes the issue for you. > > -- > Guido Falsi > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
> I just updated my laptop from source, and somewhere along the way
> the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too. See
http://www.lemis.com/grog/diary-mar2020.php?topics=c&subtitle=Daily%20teevee%20update&article=D-20200306-002910#D-20200306-002910
, not the first entry on the subject.
> I have the right Alt key mapped to "Multi_key", which is now
> keycode 108 instead of 113, which is now arrow left instead.
Interesting. Mine wandered from 117 to 147, with PageDown ("Next") as
collateral damage. It seems that there are a lot of strange new key
bindings (partial output of xmodmap -pk):
117 0xff56 (Next) 0x (NoSymbol) 0xff56 (Next)
130 0xff31 (Hangul) 0x (NoSymbol) 0xff31 (Hangul)
131 0xff34 (Hangul_Hanja) 0x (NoSymbol) 0xff34
(Hangul_Hanja)
135 0xff67 (Menu) 0x (NoSymbol) 0xff67 (Menu)
147 0x1008ff65 (XF86MenuKB) 0x (NoSymbol) 0x1008ff65
(XF86MenuKB)
Some of these may reflect other remappings that I have done.
> I hope this email saves somebody else from the frustrating
> morning I had...
Sorry. I should have thought of reporting it. For me, with a number
of other issues, it was a frustrating week,some of which are still not
resolved.
Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
signature.asc
Description: PGP signature
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On 2020-03-11 02:19, Ed Maste wrote: So to confirm, your issue is with sc(4), not vt(4)? I don't actually have an issue with either. although: "After booting, all colors can be changed using the syscons.kattr sysctl." % sysctl -a | grep syscons hw.syscons.sc_no_suspend_vtswitch: 0 hw.syscons.kbd_debug: 1 hw.syscons.kbd_reboot: 1 hw.syscons.bell: 1 hw.syscons.saver.keybonly: 0 % Also, both sc and vt are compiled into GENERIC. Is it just a matter of putting "syscons=[sc|vt]" in loader.conf to select whatever driver? FreeBSD drunkfish.andyit.com.au 12.1-STABLE FreeBSD 12.1-STABLE #1 r358253: Sun Feb 23 15:02:00 AEST 2020 -andyf ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
Hi Rebecca, I checked when I had the problem but the machine was up to date. I already solved this problem with the fix in the bugzilla and a lot of help from the great people here to try to narrow down the problem, but the little detail is that the installer wasn't using the ZFS volumes as 4k. So before the setup for partitions I entered the command line, loaded the ZFS driver and added the ashift=12 sysctl to it, so it installed the volumes as 4k, and after that I rebuilt the kernel with the patch (quirks = 0x03) =) Thank you, Mario Em ter., 10 de mar. de 2020 às 17:06, Rebecca Cran escreveu: > > >> On Feb 26, 2020, at 9:20 PM, Warner Losh wrote: > >> > >> On Wed, Feb 26, 2020, 8:54 PM Mario Olofo > wrote: > >> > >> Hello Mark, > >> Yes, I think that it's related to the WD Green SSD. > >> Today I found this bug on FreeBSD's bugzilla: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666 > >> Tried to reinstall and recompile the kernel with the patch but it didn't > >> work, I continue to see corrupted data. > >> I think that the only way to be really sure about the corrupted data is > to > >> reinstall again but already boot with the quirks configured, but the > >> kern.cam.ada.X.quirks don't seems to exists on FreeBSD 12, > >> so I have a probability of corruption between installation and > compilation > >> of the patched kernel... > >> Don't know what more to do... > > > > What happens if you disable TRIM? > > Also, have you checked to see if there’s a firmware update available? > > Rebecca > > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Running FreeBSD on M.2 SSD
>> On Feb 26, 2020, at 9:20 PM, Warner Losh wrote: >> >> On Wed, Feb 26, 2020, 8:54 PM Mario Olofo wrote: >> >> Hello Mark, >> Yes, I think that it's related to the WD Green SSD. >> Today I found this bug on FreeBSD's bugzilla: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225666 >> Tried to reinstall and recompile the kernel with the patch but it didn't >> work, I continue to see corrupted data. >> I think that the only way to be really sure about the corrupted data is to >> reinstall again but already boot with the quirks configured, but the >> kern.cam.ada.X.quirks don't seems to exists on FreeBSD 12, >> so I have a probability of corruption between installation and compilation >> of the patched kernel... >> Don't know what more to do... > > What happens if you disable TRIM? Also, have you checked to see if there’s a firmware update available? Rebecca ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On Mon, 9 Mar 2020 at 15:15, Andy Farkas wrote: > > On 2020-03-10 01:04, Konstantin Belousov wrote: > > Take a look at r334530. > > "or the user really hates this feature and can't wait to turn it off" So to confirm, your issue is with sc(4), not vt(4)? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
On 10/03/20 13:41, Mario Olofo wrote: > Hello All, > In the prccess of making the FreeBSD my main OS, I stumbled on an very > uncommon problem: the LightDM don't accept any keys, and I can't even get > out to the tty with ctrl+alt+F1... > > I build the drm-kmod from ports, installed Xorg, Xfce4 and LightDM and > lightdm-gtk-greeter with pkg, and enabled it on rc.conf with > lightdm_enable="YES". > On boot, it don't work because the lightdm need to be on video group, so I > added it to video groups and then the LightDM screen showed up, but only > the mouse work. If I press a lot of keys and then use the mouse to restart > the system, I can see some garbage input on the first terminal! > I didn't create a custom X config, but tried to force a input conf to see > if it was the problem but it appears that the config is not used at all > when starting LightDM. I rebuild from source the LightDM, but the problem > persists. When I use startx to go directly to Xfce4 works like a charm. > I'm sorry I don't have much insight about this, but this one (and the following problem too) looks like a graphics hardware related problem. You should share some information about your system, which graphics adapter and chipset you are using and what driver setup. > Then comes the second but less important problem that I found, the topbar > decorator of windows are not displaying correctly. The background img > behind the title don't stretch to cover the full width. Anyone had this > problem before? There is a known problem with xfce 4.14 and window decorations on certain hardware chipsets: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240887 It has been recently reported that Xorg server 1.20.7 (available with the latest package set) fixes the issue. This update will reach quarterly packages at the start of April. If you're willing you could migrate your machine to latest packages and confirm if this fixes the issue for you. -- Guido Falsi ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem
Hello All, In the prccess of making the FreeBSD my main OS, I stumbled on an very uncommon problem: the LightDM don't accept any keys, and I can't even get out to the tty with ctrl+alt+F1... I build the drm-kmod from ports, installed Xorg, Xfce4 and LightDM and lightdm-gtk-greeter with pkg, and enabled it on rc.conf with lightdm_enable="YES". On boot, it don't work because the lightdm need to be on video group, so I added it to video groups and then the LightDM screen showed up, but only the mouse work. If I press a lot of keys and then use the mouse to restart the system, I can see some garbage input on the first terminal! I didn't create a custom X config, but tried to force a input conf to see if it was the problem but it appears that the config is not used at all when starting LightDM. I rebuild from source the LightDM, but the problem persists. When I use startx to go directly to Xfce4 works like a charm. Then comes the second but less important problem that I found, the topbar decorator of windows are not displaying correctly. The background img behind the title don't stretch to cover the full width. Anyone had this problem before? Thank you, Mario ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
