Archive:Building restricted drivers for XBMCbuntu - Revision history

Karellen: Karellen moved page Building restricted drivers for XBMCbuntu to Archive:Building restricted drivers for XBMCbuntu without leaving a redirect: Outdated

2020-07-20T04:37:00Z

Karellen moved page Building restricted drivers for XBMCbuntu to Archive:Building restricted drivers for XBMCbuntu without leaving a redirect: Outdated

← Older revision	Revision as of 04:37, 20 July 2020
(No difference)

Karellen at 22:01, 17 June 2020

2020-06-17T22:01:17Z

← Older revision		Revision as of 22:01, 17 June 2020
Line 138:		Line 138:
	Its a more reliable, faster to install and works well.		Its a more reliable, faster to install and works well.

	:see also: [[XBMCbuntu#Upgrading NVidia drivers in Ubuntu and variants]]		:see also: XBMCbuntu#Upgrading NVidia drivers in Ubuntu and variants

	== Building ATI/AMD video drivers ==		== Building ATI/AMD video drivers ==

Ned Scott at 04:54, 28 June 2013

2013-06-28T04:54:22Z

← Older revision		Revision as of 04:54, 28 June 2013
Line 1:		Line 1:
	{{~~cleanup~~}}		{{outdated}}
	The simpler approach to build and install the restricted drivers is to run the driver installer on XBMCbuntu. The installer will take care of all installations and modify the config files accordingly.		The simpler approach to build and install the restricted drivers is to run the driver installer on XBMCbuntu. The installer will take care of all installations and modify the config files accordingly.

Line 210:		Line 210:

	Ubuntu Hardy Installation Guide on the [http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide Unofficial ATI Linux Drivers Wiki]		Ubuntu Hardy Installation Guide on the [http://wiki.cchtml.com/index.php/Ubuntu_Hardy_Installation_Guide Unofficial ATI Linux Drivers Wiki]

	~~[[Category:Development]]~~
	~~[[Category:Linux]]~~
	~~[[Category:XBMCbuntu]]~~
	~~[[Category:To-Do]]~~

>NedBot: Robot: Cosmetic changes

2013-04-27T14:44:46Z

Robot: Cosmetic changes

← Older revision		Revision as of 14:44, 27 April 2013
Line 133:		Line 133:
	There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.nvidia.img. My way of doing it is to boot XBMCbuntu with NVIDIA drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.27-11-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.		There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.nvidia.img. My way of doing it is to boot XBMCbuntu with NVIDIA drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.27-11-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.

	===Installing driver from repositories===		=== Installing driver from repositories ===

	Certainly less involved and is up-to-date with all Ubuntu variants that are still supported, If you have a EOL Ubuntu or variant repositories may not have the driver your looking for.		Certainly less involved and is up-to-date with all Ubuntu variants that are still supported, If you have a EOL Ubuntu or variant repositories may not have the driver your looking for.
	Its a more reliable, faster to install and works well.		Its a more reliable, faster to install and works well.

	:see also: [[XBMCbuntu#~~Upgrading_NVidia_drivers_in_Ubuntu_and_variants~~]]		:see also: [[XBMCbuntu#Upgrading NVidia drivers in Ubuntu and variants]]

	== Building ATI/AMD video drivers ==		== Building ATI/AMD video drivers ==

>UNiversal: Honestly this is madness and unnecessary page, however for documentation purposes and more new ways to screw your system Its best left then.

2013-04-17T13:16:34Z

Honestly this is madness and unnecessary page, however for documentation purposes and more new ways to screw your system Its best left then.

← Older revision		Revision as of 13:16, 17 April 2013
Line 7:		Line 7:

	The following procedures are intended to tackle this issue; it has side effects and limitations but once you have a fully working build environment it does not have major disadvantages (IMHO).		The following procedures are intended to tackle this issue; it has side effects and limitations but once you have a fully working build environment it does not have major disadvantages (IMHO).

			{{greenv\|'''NOTICE'''\|The simplest and recommended installation method for restricted drivers is using repositories (ppa's) like X-swat, since on Kernel upgrades you wont need to worry about going through the procedures below.}}

>UNiversal: XBMCbuntu not XBMC Live

2013-04-17T13:09:38Z

XBMCbuntu not XBMC Live

← Older revision		Revision as of 13:09, 17 April 2013
Line 164:		Line 164:
	* Method 2: build drivers in MIC		* Method 2: build drivers in MIC

	Assuming you have created a target in MIC for the creation of the ~~XBMC Live~~ image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the XBMCbuntu target.		Assuming you have created a target in MIC for the creation of the XBMCbuntu image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the XBMCbuntu target.

	Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target:		Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target:
Line 203:		Line 203:
	$ umount Image		$ umount Image

	There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.amd.img. My way of doing it is to boot ~~XBMC Live~~ with AMD drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.2X-yy-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.		There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.amd.img. My way of doing it is to boot XBMCbuntu with AMD drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.2X-yy-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.

	== References ==		== References ==

>UNiversal: /* Building ATI/AMD video drivers */

2013-04-17T13:08:38Z

Building ATI/AMD video drivers

← Older revision		Revision as of 13:08, 17 April 2013
Line 164:		Line 164:
	* Method 2: build drivers in MIC		* Method 2: build drivers in MIC

	Assuming you have created a target in MIC for the creation of the XBMC Live image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the ~~XBMC Live~~ target.		Assuming you have created a target in MIC for the creation of the XBMC Live image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the XBMCbuntu target.

	Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target:		Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target:

>UNiversal: moved Building restricted drivers for XBMC Live to Building restricted drivers for XBMCbuntu: XBMCbuntu is the release identifier.

2013-04-17T13:07:17Z

moved Building restricted drivers for XBMC Live to Building restricted drivers for XBMCbuntu: XBMCbuntu is the release identifier.

← Older revision	Revision as of 13:07, 17 April 2013
(No difference)

>NedBot: Robot: Changing Category:XBMC Live to Category:XBMCbuntu

2013-04-08T07:35:23Z

Robot: Changing Category:XBMC Live to Category:XBMCbuntu

← Older revision		Revision as of 07:35, 8 April 2013
Line 211:		Line 211:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:~~XBMC Live~~]]		[[Category:XBMCbuntu]]
	[[Category:To-Do]]		[[Category:To-Do]]

>UNiversal at 09:43, 19 November 2012

2012-11-19T09:43:11Z

← Older revision		Revision as of 09:43, 19 November 2012
Line 2:		Line 2:
	The simpler approach to build and install the restricted drivers is to run the driver installer on XBMCbuntu. The installer will take care of all installations and modify the config files accordingly.		The simpler approach to build and install the restricted drivers is to run the driver installer on XBMCbuntu. The installer will take care of all installations and modify the config files accordingly.

	However, this requires that a full build environment has to be available on the system, while the default ~~XBMC Live~~ build does not have the required packages for sake of being as much compact as possible.		However, this requires that a full build environment has to be available on the system, while the default XBMCbuntu build does not have the required packages for sake of being as much compact as possible.

	As several users have experienced, a full build environment requires around 1 GB of space, and the ~~XBMC Live~~ permanent storage file can be filled up quite easily.		As several users have experienced, a full build environment requires around 1 GB of space, and the XBMCbuntu permanent storage file can be filled up quite easily.

	The following procedures are intended to tackle this issue; it has side effects and limitations but once you have a fully working build environment it does not have major disadvantages (IMHO).		The following procedures are intended to tackle this issue; it has side effects and limitations but once you have a fully working build environment it does not have major disadvantages (IMHO).
Line 11:		Line 11:
	== Building NVIDIA video drivers ==		== Building NVIDIA video drivers ==

	* Method 1: build drivers on ~~XBMC Live~~		* Method 1: build drivers on XBMCbuntu

	NB. You have to have a LARGE persistent storage file for this, around 1 GB, or the process will not complete due to insufficient disk space.		NB. You have to have a LARGE persistent storage file for this, around 1 GB, or the process will not complete due to insufficient disk space.
Line 40:		Line 40:
	* Method 2: build drivers in MIC		* Method 2: build drivers in MIC

	Assuming you have created a target in MIC for the creation of the ~~XBMC Live~~ image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the XBMCbuntu target.		Assuming you have created a target in MIC for the creation of the XBMCbuntu image, you need to create a new target having all the necessary development tools ON THE SAME PLATFORM, so that the build target has the same system components as the XBMCbuntu target.

	Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target (ignore the error from mv):		Once done, copy the driver installer script onto the target and perform the following steps in a chrooted terminal on the build target (ignore the error from mv):
Line 129:		Line 129:


	There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.nvidia.img. My way of doing it is to boot ~~XBMC Live~~ with NVIDIA drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.27-11-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.		There is however a final step, ie. having the new module automatically loaded. For this we need to have an updated modules.dep inside the restrictedDrivers.nvidia.img. My way of doing it is to boot XBMCbuntu with NVIDIA drivers in safe mode, run a "sudo depmod -a" and copy the resulting /lib/modules/2.6.27-11-generic/modules.dep (and /lib/modules/2.6.27-11-generic/modules.dep.bin if there) over to the same location in build environment again, and reiterate the population of the .img file.

	===Installing driver from repositories===		===Installing driver from repositories===
Line 140:		Line 140:
	== Building ATI/AMD video drivers ==		== Building ATI/AMD video drivers ==

	* Method 1: build drivers on ~~XBMC Live~~		* Method 1: build drivers on XBMCbuntu

	NB. You have to have a LARGE persistent storage file for this, around 1 GB, or the process will not complete due to insufficient disk space.		NB. You have to have a LARGE persistent storage file for this, around 1 GB, or the process will not complete due to insufficient disk space.