On Sat, Nov 19, 2016 at 08:31:22 +0900, Ken OKABE via arch-general wrote:
> > The kernel is a different, as it can cause an unbootable situation.
>
> [...]
>
> On what reason or scenario, some LTS(maybe incompatible to the kernel)
> will break kernel or make the system unbootable?
Ideally never. T
On 11/18/2016 11:02 PM, David C. Rankin wrote:
> I've got to get something figured out. This laptop will absolutely blind you
> when you open a browser, or anything with a white background. I have the
> backlight set at 40% in win10 and that works well. Here it looks like it is on
> MAX continually
On 11/18/2016 03:56 AM, Warp wrote:
> Do you use any special kernel boot parameters?
>
> Using "acpi_backlight=vendor" helped me in a similar situation, though it
> was about another option interfering with backlight control.
>
> Sylvain
Thanks Sylvain,
I've tried with both "acpi_backlight=ve
>>The kernel is a different, as it can cause an unbootable situation.
I can only imagine as follows:
1-a linux boot succesfully
1-b linux-lte boot succesfully
2 TYY or some DM load successfully
3-a Plasma might fail to launch
3-b Plasma-LTS might fail to launch
On what reason or scenario, some
> Ralf, exactly, and that is to what I'm attracted.
That they maintain it doesn't necessarily mean that they will also make
sure that it works with new library versions. It sounded more like bug-
and security fixes to me.
Arch is not like Debian or even Ubuntu. Most libraries get updated as
soon
Bruno,
>Yes, but what if plasma-lts doesn’t build with the new libwhatever? Will
plasma-lts have updates that take care of this? Will they be available
ahead of libwhatever release?
>Then, consider the number of package plasma-lts represents. Multiply by
their number of dependencies. Especially, k
On 11/18/2016 12:46 PM, Doug Newgard wrote:
> On Sat, 19 Nov 2016 02:34:08 +0900
> Ken OKABE via arch-general wrote:
>
>> What kind of scenario in the real world to be problematic to maintain
>> KDE Plasma LTS line as separated packages from non-LTS?
>
> A whole lot more work for litte/no gain.
>What's completely missing by the kernel related explanation is, that
upstrem provides, IOW maintains longterm linux,
https://www.kernel.org/ . Does KDE upstream maintain KDE Plasma LTS?
Ralf, exactly, and that is to what I'm attracted.
https://community.kde.org/Schedules/Plasma_5
According to the
On Sat, 19 Nov 2016 02:34:08 +0900
Ken OKABE via arch-general wrote:
> What kind of scenario in the real world to be problematic to maintain
> KDE Plasma LTS line as separated packages from non-LTS?
A whole lot more work for litte/no gain. The kernel is a different, as it can
cause an unbootable
On Sat, 19 Nov 2016 02:34:08 +0900, Ken OKABE via arch-general wrote:
>What kind of scenario in the real world to be problematic to maintain
>KDE Plasma LTS line as separated packages from non-LTS?
Apart from the policy, the problem are maintainers willing it to do and
to provide it by a third par
Le 18/11/2016 à 18:34, Ken OKABE via arch-general a écrit :
> Arch-wiki suggests:
> https://wiki.archlinux.org/index.php/System_maintenance#Install_the_linux-lts_package
>> Tips and tricks
> The following tips are generally not required, but certain users may
> find them useful.
>> Install the lin
Arch-wiki suggests:
https://wiki.archlinux.org/index.php/System_maintenance#Install_the_linux-lts_package
>Tips and tricks
The following tips are generally not required, but certain users may
find them useful.
>Install the linux-lts package
The linux-lts package is an alternative Arch kernel packag
On November 18, 2016 6:42:40 AM GMT+01:00, "David C. Rankin"
wrote:
>On 11/17/2016 04:31 PM, David C. Rankin wrote:
>> All,
>>
>> Laptop: HP 8760w, Quadro 3000M, nvidia-340xx packages.
>>
>> The driver works perfectly (no errors in Xorg.0.log), but I have no
>way to
>> control the screen
13 matches
Mail list logo
