Re: video capture / streaming
Hello, Mihai Popescu writes: > For camera access as an user see: /etc/fbtab (fBtab not fStab) Is fbtab usable also in the case of login via xenodm? Into fbtab one should enter the login device name (like /dev/ttyp1), but is there such a thing when xlogin logs you in? Thanks Ruda
Re: amdgpu: AMD 5700XT (NAVI10) misreported and non-working
On Sun, Jul 19, 2020 at 04:36:37PM +1000, Jonathan Gray wrote: > On Sun, Jul 19, 2020 at 01:13:51AM -0400, jcm...@gmail.com wrote: > > I saw that much of the amdgpu related drm code had been updated against > > linux 5.7 and decided to try it out using a recent snapshot. While the > > amdgpu module loads and is able to mirror to both of my displays when in > > a tty, attempting to use startx or starting xenodm results in both > > displays showing a blank black screen. When this occurs I am unable to > > switch to another tty though I am able to SSH into the system and poke > > around. > > Userland support for navi10/gfx1010 requires at least llvm 9. > Currently llvm 8 is in the tree. We stopped updating when the license > changed for the worse. With llvm versions being tied to amd hardware > support and newer c++ standards, not updating is becoming increasingly > painful as time goes by so this may have to change in the near future. Snapshots now have llvm 10 so navi10 acceleration should work with the version of Mesa already in xenocara.
Re: sysctl and panic
On 2020-08-05, Stuart Henderson wrote: > On 2020-08-04, Sven F. wrote: >> Dear readers, >> >> About to upgrade devices, >> the device did not reboot on panic (6.4 stable) >> and i ' d like to see kernel crash in new version >> >> # sysctl -w ddb.panic=1 >> sysctl: ddb.panic: Operation not permitted >> >> wait what ?? >> >> # id >> uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), >> 5(operator), 20(staff), 31(guest) >> >> mkay .. >> >> Is this expected and can be set only early in boot ? >> >> is ddb.panic=0 still supported ? >> >> Thank you for reading . >> >> > > $ man -k any=ddb.console similar for ddb.panic of course. :) > sysctl(2) - get or set system information > ddb(4) - kernel debugger > pgs(4/macppc) - programmer's switch > sysbutton(4/macppc) - Xserve G4 and G5 front system identifier button > securelevel(7) - securelevel and its effects > boot, boot.conf(8/amd64) - amd64-specific second-stage bootstrap > boot, boot.conf(8/hppa) - hppa-specific bootstrap > boot, boot.conf(8/i386) - i386-specific second-stage bootstrap > boot, boot.conf(8/landisk) - landisk-specific second-stage bootstrap > boot_sparc64(8/sparc64) - sparc64 system bootstrapping procedures > > $ man securelevel > SECURELEVEL(7)Miscellaneous Information Manual SECURELEVEL(7) > > NAME > securelevel – securelevel and its effects > [...] > > >
Re: sysctl and panic
On 2020-08-04, Sven F. wrote: > Dear readers, > > About to upgrade devices, > the device did not reboot on panic (6.4 stable) > and i ' d like to see kernel crash in new version > > # sysctl -w ddb.panic=1 > sysctl: ddb.panic: Operation not permitted > > wait what ?? > > # id > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), > 5(operator), 20(staff), 31(guest) > > mkay .. > > Is this expected and can be set only early in boot ? > > is ddb.panic=0 still supported ? > > Thank you for reading . > > $ man -k any=ddb.console sysctl(2) - get or set system information ddb(4) - kernel debugger pgs(4/macppc) - programmer's switch sysbutton(4/macppc) - Xserve G4 and G5 front system identifier button securelevel(7) - securelevel and its effects boot, boot.conf(8/amd64) - amd64-specific second-stage bootstrap boot, boot.conf(8/hppa) - hppa-specific bootstrap boot, boot.conf(8/i386) - i386-specific second-stage bootstrap boot, boot.conf(8/landisk) - landisk-specific second-stage bootstrap boot_sparc64(8/sparc64) - sparc64 system bootstrapping procedures $ man securelevel SECURELEVEL(7)Miscellaneous Information Manual SECURELEVEL(7) NAME securelevel – securelevel and its effects [...]
Re: can't install some packages on -current
On 2020-08-04, Sonic wrote: > Is there a workaround? Is it a matter of timing - waiting for the > packages to be built around the newer libraries? Or were the older > library versions left off mistakenly? scp the old libraries, or wait for new packages that don't need them. This usually happens at least every few months with -current as libraries change.
