Re: [arch-general] Linux still at 4.2, but nvidia and virtualbox compiled for 4.3?

2015-11-24 Thread João Miguel
> Even better: read the pacman messages while updating (or afterwards in the
> logs). ;)
Turns out I read messages that weren't there... Thought I had missed
them when I saw this thread. Which makes my problem as complicated as I
thought it was before I found this (i.e. an actual driver problem
instead of a packaging mistake).

Thanks for the attention,
João Miguel


Re: [arch-general] Linux still at 4.2, but nvidia and virtualbox compiled for 4.3?

2015-11-24 Thread João Miguel
> Did you update today? Laurent fixed the nvidia package the same day (22
> Nov.), which is in [extra] now. There shouldn't be any problems with the
> current package.
Yes. Rereading this thread, it seems not only hadn't I read the email
before I had the problem, I didn't even read it properly afterwards... I
thought I might have had those errors and hadn't read them, but upon
inspection of /var/log/pacman.log, it turns out there were actually no
errors.

Given the case, and since I'm in no emergency (have downgraded the
packages, can use the X, although graphical acceleration does not work),
I'll make a new thread asking why do I get the problem I described with
the most recently packaged kernel and nvidia drivers, searching for it
more adequately first.

Sorry if I wasted your time, false alarm, I was simply distracted.
Twice.

João Miguel


Re: [arch-general] Linux still at 4.2, but nvidia and virtualbox compiled for 4.3?

2015-11-24 Thread Guus Snijders
Op 24 nov. 2015 18:42 schreef "João Miguel" :
>
> > I'm afraid if I'll reboot, there will be problems with the graphics
driver.
> > Why wasn't the linux package updated alongside these others?
> >
> > Or am I wrong, and is this harmless?
> Boy, I wish I was as cautious as you before updating... I was about to
> post that after updating nvidia drivers, trying to start the X will get
> you a black screen. I had assumed it was related to the custom kernel
> and/or DKMS, but the problem appears with the regular nvidia package and
> kernel. Well, I guess I can always downgrade.
>
> Thanks for the post, I must remember to check my email more often.

Even better: read the pacman messages while updating (or afterwards in the
logs). ;)

Mvg, Guus


Re: [arch-general] Linux still at 4.2, but nvidia and virtualbox compiled for 4.3?

2015-11-24 Thread Sebastiaan Lokhorst
2015-11-24 18:42 GMT+01:00 João Miguel :
>
> Boy, I wish I was as cautious as you before updating... I was about to
> post that after updating nvidia drivers, trying to start the X will get
> you a black screen. I had assumed it was related to the custom kernel
> and/or DKMS, but the problem appears with the regular nvidia package and
> kernel. Well, I guess I can always downgrade.
>
> Thanks for the post, I must remember to check my email more often
>

Did you update today? Laurent fixed the nvidia package the same day (22
Nov.), which is in [extra] now. There shouldn't be any problems with the
current package.


Re: [arch-general] Linux still at 4.2, but nvidia and virtualbox compiled for 4.3?

2015-11-24 Thread João Miguel
> I'm afraid if I'll reboot, there will be problems with the graphics driver.
> Why wasn't the linux package updated alongside these others?
> 
> Or am I wrong, and is this harmless?
Boy, I wish I was as cautious as you before updating... I was about to
post that after updating nvidia drivers, trying to start the X will get
you a black screen. I had assumed it was related to the custom kernel
and/or DKMS, but the problem appears with the regular nvidia package and
kernel. Well, I guess I can always downgrade.

Thanks for the post, I must remember to check my email more often.

--
>From mutt in /dev/tty4...
João Miguel


Re: [arch-general] Problems with movie playback (HTML5)

2015-11-24 Thread João Miguel
> > Would be really nice to know what's the root cause.
> 
> 
> systemctl --user restart pulseaudio
>
I also had this problem, even though I don't have pulseaudio installed.
For me simply restarting the browser was enough, though. So
pulseaudio must not be the root cause, even if it's involved.

João Miguel,