Re: [gentoo-user] startx Cannot open virtual console 7
el Fri, 30 Oct 2020 17:35:30 + antlists escribió: > I've got memories that you should launch getty on 1 to 6, and I don't > know whether you declare how many exist, but you tell X to grab the > next available. > > I'm pretty certain if I do a and I haven't launched a > second user, it just comes up with a blank screen, not a login prompt. This is exactly what happens here. The thing is that I can only run X on the console I logged in, and I don't see a way to override that. Only root can launch X on vt7 and up. I cannot believe there is no way to overrule that, but so far I haven't been able to find information on how to do it. In my /etc/inittab I have this: # TERMINALS #x1:12345:respawn:/sbin/agetty 38400 console linux c1:12345:respawn:/sbin/agetty 38400 tty1 linux c2:2345:respawn:/sbin/agetty 38400 tty2 linux c3:2345:respawn:/sbin/agetty 38400 tty3 linux c4:2345:respawn:/sbin/agetty 38400 tty4 linux c5:2345:respawn:/sbin/agetty 38400 tty5 linux c6:2345:respawn:/sbin/agetty 38400 tty6 linux -- edes
Re: [gentoo-user] startx Cannot open virtual console 7
el Tue, 27 Oct 2020 12:53:44 + Michael escribió: > The systemd-logind and elogind by default only allow you to run X on > the console you have logged in as a user. So I guess my question is basically if this default can be modified, and how. > As I understand it systemd-logind and its elogind derivative both use > the variable $XDG_VTNR to set the VT number. I suppose this variable > could be set to a different VT than the console you login, > via .xinitrc, or .xserverrc, or .bashrc - but I haven't tried it out. Setting XDG_VTNR to a different value didn't change anything. As far as I can see, it's not different from running startx -- vtN, and I get the same error. -- edes
Re: [gentoo-user] startx Cannot open virtual console 7
el Tue, 27 Oct 2020 09:35:25 -0300 edes escribió: > Just to be sure: I should enable the -suid USE flag in > x11-base/xorg-server? Just for the record, I rebuilt x11-base/xorg-server with +suid, and the problem persists: $ startx -- vt7 Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied) -- edes
Re: [gentoo-user] startx Cannot open virtual console 7
el Tue, 27 Oct 2020 13:15:32 +0100 Arve Barsnes escribió: > If you've migrated to elogind, you have probably moved away from a > setuid xorg-server. I'd start loooking here: > https://wiki.gentoo.org/wiki/Non_root_Xorg Hi, thanks for the response. I had read that document (and others), but I thought it addressed the problem of not being able to start Xorg as regular user, which is not my case. Just to be sure: I should enable the -suid USE flag in x11-base/xorg-server? -- edes
[gentoo-user] startx Cannot open virtual console 7
Hi, I'm using xfce without a graphical login. The system boots into a terminal and after logging in in tty1, I start the GUI with startx. This used to start X in vt7, but after the migration to elogind, X starts in the same tty where I type the command, which I don't want. I can't replicate the old behaviour. I tried "startx -- vt7", but I get this error message: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied) I don't know if this is relevant, but under /dev I see: crw--w 1 root tty 4, 0 oct 27 07:54 /dev/tty0 crw--- 1 edes tty 4, 1 oct 27 07:57 /dev/tty1 crw--w 1 root tty 4, 2 oct 27 07:54 /dev/tty2 crw--w 1 root tty 4, 3 oct 27 07:54 /dev/tty3 crw--w 1 root tty 4, 4 oct 27 07:54 /dev/tty4 crw--w 1 root tty 4, 5 oct 27 07:54 /dev/tty5 crw--w 1 root tty 4, 6 oct 27 07:54 /dev/tty6 crw--w 1 root tty 4, 7 oct 27 07:54 /dev/tty7 crw--w 1 root tty 4, 8 oct 27 07:54 /dev/tty8 crw--w 1 root tty 4, 9 oct 27 07:54 /dev/tty9 I would appreciate any help, since I'm completely ignorant of all things related to authentication, pam, and the rest, which I suspect might have something to do with this (or perhaps not?). -- edes
Re: [gentoo-user] Python:2.7 and removing it early
el 2020-05-04 a las 21:56 antlists escribió: > Another app that's 2.7 only is the current version of lilypond. The new > dev version I think can run without python2, but certainly building the > stable version demands it. I *think* if you get the pre-compiled binary > the current version can run (crippled) without python2. re lilypond, please see bug 720422: https://bugs.gentoo.org/720422 there's an ebuild for lilypond-2.21.1, that builds with python 3.7 (and with guile 2.2). --
Re: [gentoo-user] USB sound card not recognized as capture device
el 2020-01-23 a las 13:59 Mick escribió: > The way I went about it was to comment out the offending lines in these > files and recompile the kernel. It is a bit of pain, since I have to > perform this manual editing with each kernel so far. > > You could try to comment out the lines which break your card for now and > see if this fixes the problem. This option might be a bit over my head, since I don't know C/C++, and the changes between 5.4.10 and 5.4.11 in drivers/usb/core/config.c have been important: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/usb/core/config.c?id=v5.4.11=v5.4.10 Not to mention further changes in the following kernels. I might try to keep the old version of the file and see what happens, but I'm not sure of the consequences. > I would start with BGO in the first instance: > > https://bugs.gentoo.org/ > > providing info on the affected hardware, the errors you've identified > and the files you suspect containing the changes in the code. Will do, although this is a problem in the linux kernel and not specific to gentoo. Thanks for your help. --
Re: [gentoo-user] USB sound card not recognized as capture device
el 2020-01-19 a las 16:49 Mick escribió: > You could compare the dmesg output of working and non-working kernels > and see what differences are present, then google for bugs/solutions on > that basis. [...] > You could also diff the two different kernel tree versions and see what > drivers have changed. Hello, thanks for your suggestions. I'm not a programmer and I know nothing about C or kernel development, but I found that, beginning with 5.4.11, several changes were introduced in drivers/usb/core/config.c, that seem to be consistent with the message that appears now when I connect my card: [ 129.153850] usb 3-10.3: config 1 interface 2 altsetting 1 has a duplicate endpoint with address 0x85, skipping [ 129.153854] usb 3-10.3: config 1 interface 2 altsetting 2 has a duplicate endpoint with address 0x85, skipping Where can I post this problem? I've been using Linux for 20 years, but this is my first problem with the kernel. I found these forums: https://forum.linuxfoundation.org/categories/drivers https://www.linuxquestions.org/questions/linux-kernel-70/ And of course the kernel mailing list, but seems to be for developers. -
Re: [gentoo-user] USB sound card not recognized as capture device
el 2020-01-18 a las 12:58 edes escribió: > But now for some reason it works as playback device, but is not > recognized as capture device. I kept investigating, and all the evidence points to a kernel problem (gentoo-sources). I tried several versions, everything works fine with kernels up to 5.4.10, problems appear with 5.4.11, 12 and 13. Same results on two different machines with two different cards (same model). It seems that some changes were introduced in 5.4.11 that affect USB audio. This only affects my Sound Devices USPre2 cards, I tried with a cheap card, and it continues to work normally with all kernels. Where should I report this problem and who could help? Thanks. --
[gentoo-user] USB sound card not recognized as capture device
Hello list, I have a Sound Devices that always worked perfectly fine out of the box as a generic USB device, without need of asoundrc or anything. But now for some reason it works as playback device, but is not recognized as capture device. Below I pasted the output of the alsa_info script, where you can see that arecord -l returns nothing and there is no capture device under /dev/snd. The card itself works fine on other machines, including one with a very similar gentoo system installed by myself, also without asoundrc or any special configuration. Any help would be greatly appreciated, because I have no idea where to start looking. upload=true=true= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Sat Jan 18 03:33:25 UTC 2020 !!Linux Distribution !!-- Gentoo Base System release 2.6 NAME=Gentoo ID=gentoo PRETTY_NAME="Gentoo/Linux" HOME_URL="https://www.gentoo.org/; SUPPORT_URL="https://www.gentoo.org/support/; BUG_REPORT_URL="https://bugs.gentoo.org/; !!DMI Information !!--- Manufacturer: Product Name: Product Version: Firmware Version: Board Vendor: Board Name: !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0004:00/status 15 /sys/bus/acpi/devices/LNXCPU:00/status 15 /sys/bus/acpi/devices/LNXCPU:01/status 15 /sys/bus/acpi/devices/LNXCPU:02/status 15 /sys/bus/acpi/devices/LNXCPU:03/status 15 /sys/bus/acpi/devices/LNXCPU:04/status 15 /sys/bus/acpi/devices/LNXCPU:05/status 15 /sys/bus/acpi/devices/LNXCPU:06/status 15 /sys/bus/acpi/devices/LNXCPU:07/status 15 /sys/bus/acpi/devices/LNXCPU:08/status 15 /sys/bus/acpi/devices/LNXCPU:09/status 15 /sys/bus/acpi/devices/LNXCPU:0a/status 15 /sys/bus/acpi/devices/LNXCPU:0b/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0501:00/status 15 /sys/bus/acpi/devices/PNP0A03:03/status 15 /sys/bus/acpi/devices/PNP0C0C:00/status 11 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:10/status 15 /sys/bus/acpi/devices/device:11/status 15 /sys/bus/acpi/devices/device:12/status 15 /sys/bus/acpi/devices/device:13/status 15 /sys/bus/acpi/devices/device:14/status 15 /sys/bus/acpi/devices/device:15/status 15 /sys/bus/acpi/devices/device:16/status 15 /sys/bus/acpi/devices/device:17/status 15 /sys/bus/acpi/devices/device:18/status 15 /sys/bus/acpi/devices/device:19/status 15 /sys/bus/acpi/devices/device:1e/status 15 /sys/bus/acpi/devices/device:1f/status 15 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 /sys/bus/acpi/devices/device:22/status 15 /sys/bus/acpi/devices/device:23/status 15 /sys/bus/acpi/devices/device:24/status 15 /sys/bus/acpi/devices/device:25/status 15 /sys/bus/acpi/devices/device:26/status 15 /sys/bus/acpi/devices/device:27/status 15 !!Kernel Information !!-- Kernel release:5.4.12-gentoo Operating System: GNU/Linux Architecture: x86_64 Processor: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.12-gentoo Library version:1.2.1.2 Utilities version: 1.2.1 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Jack: Installed - Yes (/usr/bin/jackd) Running - No !!Soundcards recognised by ALSA !!- 0 [USBPre2]: USB-Audio - USBPre2 Sound Devices USBPre2 at usb-:00:14.0-10.3, high speed !!PCI Soundcards installed in the system !!-- 00:1b.0 Audio device [0403]: Intel Corporation C610/X99 series chipset HD Audio Controller [8086:8d20] (rev 05) Subsystem: ASUSTeK Computer Inc. C610/X99 series chipset HD Audio Controller [1043:8637] 01:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1) Subsystem: eVga.com. Corp. High Definition Audio Controller [3842:1303] !!Loaded sound module options !!--- !!USB Mixer information !!- --startcollapse-- USB Mixer: usb_id=0x09260202, ctrlif=0, ctlerr=0 Card: Sound Devices USBPre2 at usb-:00:14.0-10.3, high speed --endcollapse-- !!ALSA Device nodes !!- crw-rw+ 1 root audio 116, 0 Jan 18 00:25 /dev/snd/controlC0 crw-rw+ 1 root audio 116, 16 Jan 18 00:25 /dev/snd/pcmC0D0p crw-rw+ 1 root audio 116, 1 Jan 18 00:25 /dev/snd/seq crw-rw+
