Re: [arch-general] Cannot use monitor in 1920x1080 anymore
>> >> Hmmm... Martin, if you still have a Xorg.log it means you have a >> >> really old installation, >> >> That was true for versions under 1.16.0-3 as evidenced by the version >> comparison, but it is not true anymore, Xserver 1.17 dumps its logs to >> syslog. And syslog is trapped by journalctl. >> > > Err No it does not this system is fully up to date . > > I use startx to start the graphical display nothing in journalctlit is > in /var/log/Xorg.0.log > > Sorry to disapoint and all that .. >From what I've read, it's *only* GDM that "hacks" the X server to run so that it redirects the logs to the journal. Otherwise, it'll go to the /var/log/Xorg.0.log file as ever. ps. on my two - always up-to-date - Arch installations, using lightdm and sddm X logs to /var/log/Xorg.0.log -- damjan
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On Sun, 05 Apr 2015 12:10:13 -0500
"Pedro A. López-Valencia" wrote:
> On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
> > On Sat, 04 Apr 2015 11:29:26 -0500 "Pedro A. López-Valencia"
> > wrote:
> >
> >> Hmmm... Martin, if you still have a Xorg.log it means you have a
> >> really old installation, or you installed syslog-ng and integrated it
> >> with journalctl, something that is not standard anymore. Heck,
> >> OpenSUSE just removed it of Tumbleweed, it's a sign of the times.
> > That would only be true if systemd launched Xorg directly. Xorg writes
> > its log file on its own, not through syslog and not to the journal; I
> > can tell you that on my fully up-to-date system, at least, Xorg writes
> > to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for
> > non-root Xorg).
> >
>
> You mean the contents of the xorg-server.install file?
>
> post_upgrade() {
>if (( $(vercmp $2 1.16.0-3) < 0 )); then
> post_install
>fi
> }
>
> post_install() {
>cat < >>> xorg-server has now the ability to run without root rights with
> the help of systemd-logind. xserver will fail to run if not
> launched
> from the same virtual terminal as was used to log in.
> Without root rights, log files will be in ~/.local/share/xorg/
> directory.
>
> Old behavior can be restored through Xorg.wrap config file.
> See Xorg.wrap man page (man xorg.wrap).
> MSG
> }
>
> xorg-server.install (END)
>
>
>
> That was true for versions under 1.16.0-3 as evidenced by the version
> comparison, but it is not true anymore, Xserver 1.17 dumps its logs to
> syslog. And syslog is trapped by journalctl.
>
Err No it does not this system is fully up to date .
I use startx to start the graphical display nothing in journalctlit is
in /var/log/Xorg.0.log
Sorry to disapoint and all that ..
Pete .
--
Illegitimi non carborundum . ro for the purists out there
Noli nothis permittere te terere.
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote: That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg). I did some testing, and found we both are right, although what I said isn't. If you launch the xserver manually or with a display manager that is not well integrated with systemd, you'll get your text logs. If it is well integrated, namely GDM, everything will go into journalctl. -- Pedro A. López-Valencia http://about.me/palopezv
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
On Sat, 04 Apr 2015 11:29:26 -0500 "Pedro A. López-Valencia"
wrote:
Hmmm... Martin, if you still have a Xorg.log it means you have a
really old installation, or you installed syslog-ng and integrated it
with journalctl, something that is not standard anymore. Heck,
OpenSUSE just removed it of Tumbleweed, it's a sign of the times.
That would only be true if systemd launched Xorg directly. Xorg writes
its log file on its own, not through syslog and not to the journal; I
can tell you that on my fully up-to-date system, at least, Xorg writes
to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for
non-root Xorg).
You mean the contents of the xorg-server.install file?
post_upgrade() {
if (( $(vercmp $2 1.16.0-3) < 0 )); then
post_install
fi
}
post_install() {
cat <>> xorg-server has now the ability to run without root rights with
the help of systemd-logind. xserver will fail to run if not
launched
from the same virtual terminal as was used to log in.
Without root rights, log files will be in ~/.local/share/xorg/
directory.
Old behavior can be restored through Xorg.wrap config file.
See Xorg.wrap man page (man xorg.wrap).
MSG
}
xorg-server.install (END)
That was true for versions under 1.16.0-3 as evidenced by the version
comparison, but it is not true anymore, Xserver 1.17 dumps its logs to
syslog. And syslog is trapped by journalctl.
--
Pedro A. López-Valencia
http://about.me/palopezv
Re: [arch-general] Lenovo carbon X1 and kernel 3.19 issues
On 04/05/2015 01:33 AM, andrea crotti wrote: I have a Lenovo Carbon X1 third generation, just bought a few months ago. Everything worked perfectly but a week ago I upgraded to the new kernel version: "Linux carbon 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64 GNU/Linux" After that two problems started: 1. Audio doesn't work anymore, even speaker-test fails, I already tried everything and, the audio card still comes up, but nothing happens even using speaker-test, which makes me thing it might be a hardware issue, what do you think? I don't have an audio issue with kernel 3.19.2-1 but I do have an ALSA MIDI issue -- module snd_seq_midi is no longer loaded automatically on my machine. I've been waiting for the next kernel update to see if the problem gets fixed. Also note that the ALSA packages were updated to 1.0.29-1 around March 9.
Re: [arch-general] Little automation to install
On 04/04/15 at 06:47pm, Roman Neuhauser wrote: # brauli...@gmail.com / 2015-04-01 13:53:57 -0300: Hello all, After some many years, I'm back to ArchLinux. One thing that took me time was to read the manuals and run all the commands for installation. That made me wonder on how automation might help things get easier and faster on install. Could you please tell the current works on that? The result of my work was this script: https://github.com/brauliobo/gitconfig/blob/master/histories/archinstall.sh https://wiki.archlinux.org/index.php/FAQ , Judd Vinet "Arch is what you make it"
Re: [arch-general] Cannot use monitor in 1920x1080 anymore
On 2015-04-04 11:29:26, "Pedro A. López-Valencia" wrote:
> On 30/03/15 06:24, Martin S. Weber wrote:
> >On 2015-03-30 13:08:11, Alfredo Palhares wrote:
> >>Any ideas how can I debug this problem further ?
> >Have a look at X's logfile, /var/log/Xorg.log. There should be messages that
> >say the modes
> >are being removed, and why (not enough Vram, some parameter out of range,
> >etc.). It's likely
> >warning or errors, so it should be among the output of egrep '\([WE]{2}\)'
> >Xorg.0.log.
> >
> >Good luck,
> >-Martin
>
> Hmmm... Martin, if you still have a Xorg.log it means you have a really old
> installation, or you installed syslog-ng and integrated it with journalctl,
> something that is not standard anymore. Heck, OpenSUSE just removed it of
> Tumbleweed, it's a sign of the times.
>
> Alfredo, as Arch uses systemd/journalctl, you need to use the command:
>
> journalctl -b0 _EXE=/usr/lib/xorg-server/Xorg
>
As evidenced by your reply, if you can see the file, it's so much easier to look
at and massage with base system utilities, thanks for the showcase; if it's not
there, one might wish it was.
Anyways, Alfredo, right, as Arch says you cannot configure your system,
you NEED, you absolutely MUST use journalctl to access your logs.
Happy Easter,
-Martin
[arch-general] Lenovo carbon X1 and kernel 3.19 issues
Hi guys, I have a Lenovo Carbon X1 third generation, just bought a few months ago. Everything worked perfectly but a week ago I upgraded to the new kernel version: "Linux carbon 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64 GNU/Linux" After that two problems started: 1. Audio doesn't work anymore, even speaker-test fails, I already tried everything and, the audio card still comes up, but nothing happens even using speaker-test, which makes me thing it might be a hardware issue, what do you think? $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice # card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 2. Sometimes after resuming from suspension Xorg becomes crazy. I use Awesome as VM and basically it still shows something but I can't click or do anything, and the weird thing is that if I kill "Awesome" and start it again, same problem. It only starts to work normally again when I reboot the machine. The problem is not Awesome either because I tried also Fluxbox and Xfce4 but still the same problem. I can't see any clue from the logs either, any idea what I could look at? Thanks a lot PS. About 1. sometimes while listening to music the computer would give a tiny shock that made the external monitor skip and a small shock in my headset, which was very annoying, and makes me thing is a hardware issue.
