intel-linux-graphics-installer for xps13

Here you can post about your various experiences with PC hardware. You can also post about hardware that is not compatible with the linux kernel or not recommended for use with Porteus.
Post Reply
User avatar
francois
Contributor
Contributor
Posts: 5142
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

intel-linux-graphics-installer for xps13

Post#1 by francois » 29 Jul 2016, 01:41

This a thread to try to provide intel-linux-graphics-installer for xps13 under porteus 3.2rc4:
viewtopic.php?f=61&t=5876
1.0 You need porteus 3.2rc4
2.0 downloading the .deb package
3.0As deb2xzm is not there, lets try it from porteux 3.1:
Download:
https://www.mediafire.com/?hidgqu6hib345
4.0 From here we have to add the necessary libraries:

Code: Select all

root@porteus:~/Downloads# intel-linux-graphics-installer
intel-linux-graphics-installer: error while loading shared libraries: libpackagekit-glib2.so.16: cannot open shared object file: No such file or directory
root@porteus:~/Downloads# 
***troubleshooting in progress***
https://www.mediafire.com/?hidgqu6hib345
Carpe diem.

User avatar
francois
Contributor
Contributor
Posts: 5142
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Re: intel-linux-graphics-installer for xp13

Post#2 by francois » 29 Jul 2016, 03:48

Quit. :(

Explanation (it seems that brokenman knew what was involved):
libpackagekit-glib2 and libpackagekit seem to be needed. libpackagekit is not be available for linux from my search on the net.
https://www.freedesktop.org/software/Pa ... nload.html
Adding backends to PackageKit
PackageKit itself is an abstract daemon, the only bits that are distro specific are the backends.
To make PackageKit work on a new distribution,
you have to write a "backend" which is basically a shim layer from the distro tool to packagekitd. A backend can have one or more threads and also spawn other processes.
See the developer information here for more information.
Backends do not have to be complete; often they just contain basic functionality to install and remove but do not provide dependency or file lists for example. See the FAQ here for backends status.


I am not qualified to write that backend.

The solution is to work with ubuntu. Personnaly, I like kubuntu and the xubuntu editions.
Carpe diem.

Post Reply