Re: r338641 && /dev/cyapa0: moused does not show pointer on console
On Mon, Sep 24, 2018 at 21:57 Matthias Apitz wrote: > El día Monday, September 24, 2018 a las 09:01:34PM +0200, Michael Gmelin > escribió: > > > >> On 24/09/2018 13:21, Matthias Apitz wrote: > > >> Re/ i915kms, I have to load it with kldload by hand. If I load it via > > >> loader.conf, the cyapa devices (both) say 'Unable to bring the device > > >> out of bootstrap'. > > > > > > That's probably because you use device hints to configure cyapa, but > i2c bus > > > numbers are different depending on whether the kms driver is loaded or > not > > > (because it also creates i2c buses). > > > > > > Try to remove the hints and to use chromebook_platform(4) instead. > > Thanks, I will test > > chromebook_platform_load="YES" > > > Also, I think the preferred way to load i915kms is to use kld_list > (might be unrelated, but still). > > > > pkg install drm-next-kmod > > sysrc kld_list="/boot/modules/i915kms.ko" > > Thanks too. On my laptop in production I do use a handmade script > /usr/local/etc/rc.d/loadi915kms to load the module at late time. Hi Yes, the new drm drivers can’t be loaded from loader.conf. Use kld_list in rc.conf as suggested. > > matthias > > -- > Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ > +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 09:01:34PM +0200, Michael Gmelin escribió: > >> On 24/09/2018 13:21, Matthias Apitz wrote: > >> Re/ i915kms, I have to load it with kldload by hand. If I load it via > >> loader.conf, the cyapa devices (both) say 'Unable to bring the device > >> out of bootstrap'. > > > > That's probably because you use device hints to configure cyapa, but i2c bus > > numbers are different depending on whether the kms driver is loaded or not > > (because it also creates i2c buses). > > > > Try to remove the hints and to use chromebook_platform(4) instead. Thanks, I will test chromebook_platform_load="YES" > Also, I think the preferred way to load i915kms is to use kld_list (might be > unrelated, but still). > > pkg install drm-next-kmod > sysrc kld_list="/boot/modules/i915kms.ko" Thanks too. On my laptop in production I do use a handmade script /usr/local/etc/rc.d/loadi915kms to load the module at late time. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
> On 24. Sep 2018, at 15:08, Andriy Gapon wrote: > >> On 24/09/2018 13:21, Matthias Apitz wrote: >> Re/ i915kms, I have to load it with kldload by hand. If I load it via >> loader.conf, the cyapa devices (both) say 'Unable to bring the device >> out of bootstrap'. > > That's probably because you use device hints to configure cyapa, but i2c bus > numbers are different depending on whether the kms driver is loaded or not > (because it also creates i2c buses). > > Try to remove the hints and to use chromebook_platform(4) instead. Also, I think the preferred way to load i915kms is to use kld_list (might be unrelated, but still). pkg install drm-next-kmod sysrc kld_list="/boot/modules/i915kms.ko" Yours, Michael > > -- > Andriy Gapon > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
On 24/09/2018 13:21, Matthias Apitz wrote: > Re/ i915kms, I have to load it with kldload by hand. If I load it via > loader.conf, the cyapa devices (both) say 'Unable to bring the device > out of bootstrap'. That's probably because you use device hints to configure cyapa, but i2c bus numbers are different depending on whether the kms driver is loaded or not (because it also creates i2c buses). Try to remove the hints and to use chromebook_platform(4) instead. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 12:46:17PM +0300, Michael Gmelin escribió: > > What could be wrong? > > Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)? > > vt doesn’t support hardware mouse cursors, so no cursor in text mode (see > https://wiki.freebsd.org/Newcons) > Thanks. When I remove hw.vga.textmode=1 the mouse pointer comes up and works. Re/ i915kms, I have to load it with kldload by hand. If I load it via loader.conf, the cyapa devices (both) say 'Unable to bring the device out of bootstrap'. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
> On 24. Sep 2018, at 12:42, Matthias Apitz wrote: > >> El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz >> escribió: >> >> >> Hello, >> >> I've booted a fresh r338641 from an USB key on my Acer C720, and have >> the required modules loaded at boot (cyapa and ig4) and the values for cyapa >> in >> /boot/device.hints, as I do use them in r314251. The moused is running as >> >> /usr/sbin/moused -p /dev/cyapa0 -t ps/2 >> >> but no mouse pointer is written on the console. If I do >> >> # cat /dev/cyapa0 >> >> on TP movements, bytes can be read by cat(1). And trussing the PID of >> the moused shows too that it is reading bytes. >> >> What could be wrong? > > additional information: when I do load *after* boot > > # kldload i915kms > > the mouse pointer appears and can be moved. How do you load i915kms on boot? In loader.conf or in rc.conf? > >matthias > > -- > Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ > +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
> On 24. Sep 2018, at 11:31, Matthias Apitz wrote: > > > Hello, > > I've booted a fresh r338641 from an USB key on my Acer C720, and have > the required modules loaded at boot (cyapa and ig4) and the values for cyapa > in > /boot/device.hints, as I do use them in r314251. The moused is running as > > /usr/sbin/moused -p /dev/cyapa0 -t ps/2 > > but no mouse pointer is written on the console. If I do > > # cat /dev/cyapa0 > > on TP movements, bytes can be read by cat(1). And trussing the PID of > the moused shows too that it is reading bytes. > > What could be wrong? Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)? vt doesn’t support hardware mouse cursors, so no cursor in text mode (see https://wiki.freebsd.org/Newcons) Best, Michael > >matthias > -- > Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ > +49-176-38902045 > Public GnuPG key: http://www.unixarea.de/key.pub > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r338641 && /dev/cyapa0: moused does not show pointer on console
El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz escribió: > > Hello, > > I've booted a fresh r338641 from an USB key on my Acer C720, and have > the required modules loaded at boot (cyapa and ig4) and the values for cyapa > in > /boot/device.hints, as I do use them in r314251. The moused is running as > > /usr/sbin/moused -p /dev/cyapa0 -t ps/2 > > but no mouse pointer is written on the console. If I do > > # cat /dev/cyapa0 > > on TP movements, bytes can be read by cat(1). And trussing the PID of > the moused shows too that it is reading bytes. > > What could be wrong? additional information: when I do load *after* boot # kldload i915kms the mouse pointer appears and can be moved. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r338641 && /dev/cyapa0: moused does not show pointer on console
Hello, I've booted a fresh r338641 from an USB key on my Acer C720, and have the required modules loaded at boot (cyapa and ig4) and the values for cyapa in /boot/device.hints, as I do use them in r314251. The moused is running as /usr/sbin/moused -p /dev/cyapa0 -t ps/2 but no mouse pointer is written on the console. If I do # cat /dev/cyapa0 on TP movements, bytes can be read by cat(1). And trussing the PID of the moused shows too that it is reading bytes. What could be wrong? matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
