Errors installing 3.19-2 with Nvidia driver
Posted: Mar 29, 15, 13:47 Runaway1956
 Status: Interested
Joined: 29 Mar 2015
Posts: 10
Reply Quote
The kernel installs alright, but DKMS cannot rebuild my nvidia driver for the kernel. Here is the Synaptic log:

:: Code ::

(synaptic:16855): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 0' failed
/usr/share/apt-listchanges/AptListChangesGtk.py:34: GtkWarning: Theme directory scalable/stock of theme NoirCrystal has no size field

  self.glade = gtk.glade.XML("/usr/share/apt-listchanges/apt-listchanges.glade")
Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field
Preconfiguring packages ...
Selecting previously unselected package linux-image-3.19-2.dmz.2-liquorix-amd64.
(Reading database ... 215326 files and directories currently installed.)
Preparing to unpack .../linux-image-3.19-2.dmz.2-liquorix-amd64_3.19-2_amd64.deb ...
Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field
Unpacking linux-image-3.19-2.dmz.2-liquorix-amd64 (3.19-2) ...
Selecting previously unselected package linux-headers-3.19-2.dmz.2-liquorix-amd64.
Preparing to unpack .../linux-headers-3.19-2.dmz.2-liquorix-amd64_3.19-2_amd64.deb ...
Unpacking linux-headers-3.19-2.dmz.2-liquorix-amd64 (3.19-2) ...
Selecting previously unselected package linux-headers-liquorix-amd64.
Preparing to unpack .../linux-headers-liquorix-amd64_3.19-2_amd64.deb ...
Unpacking linux-headers-liquorix-amd64 (3.19-2) ...
Selecting previously unselected package linux-image-liquorix-amd64.
Preparing to unpack .../linux-image-liquorix-amd64_3.19-2_amd64.deb ...
Unpacking linux-image-liquorix-amd64 (3.19-2) ...
Setting up linux-image-3.19-2.dmz.2-liquorix-amd64 (3.19-2) ...
Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 3.19-2.dmz.2-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/340.65/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.19-2.dmz.2-liquorix-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.19-2.dmz.2-liquorix-amd64
Found initrd image: /boot/initrd.img-3.19-2.dmz.2-liquorix-amd64
Found linux image: /boot/vmlinuz-3.18-9.dmz.1-liquorix-amd64
Found initrd image: /boot/initrd.img-3.18-9.dmz.1-liquorix-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done
Setting up linux-headers-3.19-2.dmz.2-liquorix-amd64 (3.19-2) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19-2.dmz.2-liquorix-amd64
Error! Bad return status for module build on kernel: 3.19-2.dmz.2-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/340.65/build/make.log for more information.
Setting up linux-headers-liquorix-amd64 (3.19-2) ...
Setting up linux-image-liquorix-amd64 (3.19-2) ...





This is the log from DKMS' attempt to build the module.

:: Code ::



DKMS make.log for nvidia-current-340.65 for kernel 3.19-2.dmz.2-liquorix-amd64 (x86_64)
Sun Mar 29 16:32:59 CDT 2015
make: Entering directory '/var/lib/dkms/nvidia-current/340.65/build'
make KBUILD_VERBOSE=1 -C /lib/modules/3.19-2.dmz.2-liquorix-amd64/build M=/var/lib/dkms/nvidia-current/340.65/build modules
make[1]: Entering directory '/usr/src/linux-headers-3.19-2.dmz.2-liquorix-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (      \
echo >&2;                     \
echo >&2 "  ERROR: Kernel configuration is invalid.";      \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";   \
echo >&2 ;                     \
/bin/false)
mkdir -p /var/lib/dkms/nvidia-current/340.65/build/.tmp_versions ; rm -f /var/lib/dkms/nvidia-current/340.65/build/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-current/340.65/build
/bin/sh /var/lib/dkms/nvidia-current/340.65/build/conftest.sh " gcc-4.9" " gcc-4.9" x86 /lib/modules/3.19-2.dmz.2-liquorix-amd64/build /lib/modules/3.19-2.dmz.2-liquorix-amd64/build compile_tests remap_pfn_range vmap set_pages_uc set_memory_uc set_memory_array_uc change_page_attr i2c_adapter pci_get_class pm_message_t irq_handler_t pci_choose_state vm_insert_page acpi_device_ops acpi_op_remove acpi_device_id acquire_console_sem console_lock kmem_cache_create outer_flush_all on_each_cpu smp_call_function nvmap_support acpi_evaluate_integer ioremap_cache ioremap_wc proc_dir_entry INIT_WORK acpi_walk_namespace scatterlist pci_domain_nr pci_dma_mapping_error file_operations sg_alloc_table sg_init_table pci_get_domain_bus_and_slot get_num_physpages efi_enabled dom0_kernel_present drm_available proc_create_data pde_data proc_remove sg_table pm_vt_switch_required pci_save_state
echo \#define NV_COMPILER \"` gcc-4.9 -v 2>&1 | tail -n 1`\" > /var/lib/dkms/nvidia-current/340.65/build/nv_compiler.h
   gcc-4.9 -Wp,-MD,/var/lib/dkms/nvidia-current/340.65/build/.nv.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.9/include -I./arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -m64 -mno-80387 -mno-fp-ret-in-387 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -DNV_MODULE_INSTANCE=0 -DNV_BUILD_MODULE_INSTANCES=0 -UDEBUG -U_DEBUG -DNDEBUG -I/var/lib/dkms/nvidia-current/340.65/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"340.65\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -D__linux__ -DNV_DEV_NAME=\"nvidia\"  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)"  -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /var/lib/dkms/nvidia-current/340.65/build/.tmp_nv.o /var/lib/dkms/nvidia-current/340.65/build/nv.c
In file included from /var/lib/dkms/nvidia-current/340.65/build/nv-linux.h:15:0,
                 from /var/lib/dkms/nvidia-current/340.65/build/nv.c:13:
/var/lib/dkms/nvidia-current/340.65/build/conftest.h:18:2: warning: #warning "The nvidia module is incompatible with nvidiafb!" [-Wcpp]
 #warning "The nvidia module is incompatible with nvidiafb!"
  ^
In file included from include/uapi/linux/stddef.h:1:0,
                 from include/linux/stddef.h:4,
                 from ./include/uapi/linux/posix_types.h:4,
                 from include/uapi/linux/types.h:13,
                 from include/linux/types.h:5,
                 from include/uapi/linux/capability.h:16,
                 from include/linux/capability.h:15,
                 from include/linux/sched.h:15,
                 from include/linux/utsname.h:5,
                 from /var/lib/dkms/nvidia-current/340.65/build/nv-linux.h:46,
                 from /var/lib/dkms/nvidia-current/340.65/build/nv.c:13:
include/asm-generic/qrwlock.h: In function ‘queue_write_trylock’:
include/asm-generic/qrwlock.h:93:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
          cnts, cnts | _QW_LOCKED) == cnts);
                                   ^
include/linux/compiler.h:159:40: note: in definition of macro ‘likely’
 # define likely(x) __builtin_expect(!!(x), 1)
                                        ^
In file included from include/uapi/linux/stddef.h:1:0,
                 from include/linux/stddef.h:4,
                 from ./include/uapi/linux/posix_types.h:4,
                 from include/uapi/linux/types.h:13,
                 from include/linux/types.h:5,
                 from include/uapi/linux/capability.h:16,
                 from include/linux/capability.h:15,
                 from include/linux/sched.h:15,
                 from include/linux/utsname.h:5,
                 from /var/lib/dkms/nvidia-current/340.65/build/nv-linux.h:46,
                 from /var/lib/dkms/nvidia-current/340.65/build/nv.c:13:
./arch/x86/include/asm/uaccess.h: In function ‘copy_from_user’:
./arch/x86/include/asm/uaccess.h:712:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if (likely(sz < 0 || sz >= n))
                          ^
include/linux/compiler.h:159:40: note: in definition of macro ‘likely’
 # define likely(x) __builtin_expect(!!(x), 1)
                                        ^
./arch/x86/include/asm/uaccess.h: In function ‘copy_to_user’:
./arch/x86/include/asm/uaccess.h:730:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
  if (likely(sz < 0 || sz >= n))
                          ^
include/linux/compiler.h:159:40: note: in definition of macro ‘likely’
 # define likely(x) __builtin_expect(!!(x), 1)
                                        ^
/var/lib/dkms/nvidia-current/340.65/build/nv.c: In function ‘nvidia_unlocked_ioctl’:
/var/lib/dkms/nvidia-current/340.65/build/nv.c:1842:29: error: ‘struct file’ has no member named ‘f_dentry’
     return nvidia_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
                             ^
scripts/Makefile.build:257: recipe for target '/var/lib/dkms/nvidia-current/340.65/build/nv.o' failed
make[2]: *** [/var/lib/dkms/nvidia-current/340.65/build/nv.o] Error 1
Makefile:1380: recipe for target '_module_/var/lib/dkms/nvidia-current/340.65/build' failed
make[1]: *** [_module_/var/lib/dkms/nvidia-current/340.65/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-3.19-2.dmz.2-liquorix-amd64'
Makefile:35: recipe for target 'modules' failed
make: *** [modules] Error 2
make: Leaving directory '/var/lib/dkms/nvidia-current/340.65/build'
make: Entering directory '/var/lib/dkms/nvidia-current/340.65/build/uvm'
make KBUILD_VERBOSE=1 -C /lib/modules/3.19-2.dmz.2-liquorix-amd64/build M=/var/lib/dkms/nvidia-current/340.65/build/uvm modules
make[1]: Entering directory '/usr/src/linux-headers-3.19-2.dmz.2-liquorix-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (      \
echo >&2;                     \
echo >&2 "  ERROR: Kernel configuration is invalid.";      \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";   \
echo >&2 ;                     \
/bin/false)
mkdir -p /var/lib/dkms/nvidia-current/340.65/build/uvm/.tmp_versions ; rm -f /var/lib/dkms/nvidia-current/340.65/build/uvm/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-current/340.65/build/uvm
/bin/sh /var/lib/dkms/nvidia-current/340.65/build/uvm/conftest.sh " gcc-4.9" " gcc-4.9" x86 /lib/modules/3.19-2.dmz.2-liquorix-amd64/build /lib/modules/3.19-2.dmz.2-liquorix-amd64/build compile_tests remap_page_range remap_pfn_range irq_handler_t vm_insert_page kmem_cache_create outer_flush_all vm_operations_struct file_operations task_struct address_space address_space_init_once kbasename fatal_signal_pending kuid_t
/bin/sh /var/lib/dkms/nvidia-current/340.65/build/uvm/conftest.sh " gcc-4.9" " gcc-4.9" x86 /lib/modules/3.19-2.dmz.2-liquorix-amd64/build /lib/modules/3.19-2.dmz.2-liquorix-amd64/build patch_check
*** Please build the nvidia.ko module first ***
exit 1
/var/lib/dkms/nvidia-current/340.65/build/uvm/Kbuild:220: recipe for target '/var/lib/dkms/nvidia-current/340.65/build/uvm/../Module.symvers' failed
make[2]: *** [/var/lib/dkms/nvidia-current/340.65/build/uvm/../Module.symvers] Error 1
Makefile:1380: recipe for target '_module_/var/lib/dkms/nvidia-current/340.65/build/uvm' failed
make[1]: *** [_module_/var/lib/dkms/nvidia-current/340.65/build/uvm] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-3.19-2.dmz.2-liquorix-amd64'
Makefile:35: recipe for target 'modules' failed
make: *** [modules] Error 2
make: Leaving directory '/var/lib/dkms/nvidia-current/340.65/build/uvm'




Long story short - DKMS believes the kernel to be improperly configured? I don't understand that.

< Edited by Runaway1956 :: Mar 30, 15, 1:02 >
Back to top
Posted: Mar 29, 15, 15:02 damentz
 Status: Assistant
Joined: 09 Sep 2008
Posts: 1135
Reply Quote
You'll want to install the latest nvidia driver - older drivers are incompatible with the latest upstream kernels.

In respect to the output you gave me, you're trying to install 340.65. The latest for this LTM branch is 340.74. If possible, try running the latest stable drivers, which are 346.47 as of this post.

You also didn't mention which distro you're using, but it's most likely some version of Ubuntu since you're installing the nvidia-current package. Make sure you add the xorg-edgers ppa and you install the latest possible nvidia driver compatible with your graphics card.
Back to top
Posted: Mar 29, 15, 20:38 Runaway1956
 Status: Interested
Joined: 29 Mar 2015
Posts: 10
Reply Quote
Sorry about not mentioning the distro. I'm running Sparky Linux right now - based on Debian testing. sparkylinux.org/#

I'm checking on the driver upgrade right now. I guess I'm losing my distro hopper status - when I installed the driver, it was then the most current version of the driver.

Thanks for the reply - I'll post back after upgrading the driver!


Hmmm - can't upgrade from any of my repositories, there simply seems to be no 340.74. I visited this site and found a 340.76 - https://devtalk.nvidia.com/default/topic/533434/linux/current-graphics-driver-releases/

Downloading now, to see if it will work. It claims to be a "long lived branch release". This may take some time . . . .
Back to top
Posted: Mar 29, 15, 21:10 Runaway1956
 Status: Interested
Joined: 29 Mar 2015
Posts: 10
Reply Quote
Oh, fun, fun, fun. I wandered around that site for a little bit, and apparently the 340 series of drivers are "legacy". The 346 and 349 are "current".

Double checked my card with nvidia-detect, and matched it to the 346 driver. Where the fun comes from, is that I tried to install the 346 on another distro, and couldn't get X to run after installation.

Maybe I'll be even longer than I though. Downloading both the 346 and 349 drivers, in addition to the the 340 driver. I plan to install the newest, 349 first, and if X won't run, "downgrade" to the 346 driver. If that also fails, then I'll go with the 340.76.

For info, my card is:

$ nvidia-detect
Detected NVIDIA GPUs:
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1)
Your card is supported by the default drivers and legacy driver series 304.
It is recommended to install the
nvidia-driver
package.


I do realize that this is not a liquorix issue - but I'll post back about any success that I may have.
Back to top
Made it work!
Posted: Mar 30, 15, 0:40 Runaway1956
 Status: Interested
Joined: 29 Mar 2015
Posts: 10
Reply Quote
I ran down several dead-ends before I finally made Nvidia work with the newest Liquorix kernel.

In the interest of helping others who might have this problem, I'll document what I did to make my system work again.

DISCLAIMER: This worked for me, on my hardware, on my distro. It may or may not work for you - but I suspect that anyone running the liquorix kernel can probably work out details for themselves.


Assuming Liquorix is already updated to latest version, boot into that kernel, in maintenance mode. You're going to need the internet, so enable networking now.

:: Code ::

dhclient eth0


:: Code ::

Linux sparky 3.19-2.dmz.2-liquorix-amd64 #1 ZEN SMP PREEMPT Debian 3.19-2 (2015-03-24) x86_64 GNU/Linux


Next, uninstall/purge all nvidia packages.

:: Code ::

apt-get purge nvidia-* 


Let me emphasize that THIS package will most definitely block any attempt to install the downloaded package:

:: Code ::

apt-get remove nvidia-installer-cleanup



CD into some working directory that you are comfortable with - I chose to mkdir /home/guy/nvidia

:: Code ::

wget http://us.download.nvidia.com/XFree86/Linux-x86_64/346.47/NVIDIA-Linux-x86_64-346.47.run

./NVIDIA-Linux-x86_64-346.47.run -f -a -Z --opengl-headers --install-vdpau-wrapper


You must remove existing Nvidia configuration files - the installer told me that this file would prevent the driver from working.

:: Code ::

rm /etc/X11/xorg.conf.d/20-nvidia.conf


The installation is only moderately lengthy. I chose to install Nvidia's vdpau rather than try to add vdpau support from Synaptic or apt-get.

I am now booted into latest Liquorix, with Nvidia's own proprietary binary, downloaded from Nvidia's site.


Linux sparky 3.19-2.dmz.2-liquorix-amd64 #1 ZEN SMP PREEMPT Debian 3.19-2 (2015-03-24) x86_64 GNU/Linux

And, here is my xorg.conf file:
:: Code ::

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 346.47  (buildmeister@swio-display-x86-rhel47-01)  Thu Feb 19 19:19:45 PST 2015

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Back to top
Posted: Apr 2, 15, 16:23 techAdmin
 Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
running sgfxi is a lot easier since it automates those steps, selects the right driver for your card series, downloads, etc.

I would think that by now those really long how to install the graphics driver run package things would have been left behind, just like we've left other ancient methods behind, but they keep reappearing.

I wouldn't try to do a manual how to install a video driver myself, knowing how much it takes to handle all the card types etc, it's almost certain parts will be out of date within a month.

So you can replace the above with:

download sgfxi to /usr/local/bin, chmod +x sgfxi, then:

sgfxi

It's really a lot easier, and you are pretty much sure to get the right driver. Also offers beta driver support.

By the way, damentz was asking about adding the dkms option to sgfxi for nvidia install, but I had to remind that generally the latest kernel and latest xorg have serious issues a few times a year with video drivers, for example, catalyst amd hasn't even released a driver since december I think now, and certainly don't support newest kernels at all, which would kill dkms dead. Best to have something that alerts you that there is no support and why. We happen due to debian new stable freeze of sid/testing now to have somewhat stable xorg/kernels, and in ubuntu, the releases are also frozen, so same applies, but when you leave that, it gets messier re non free video drivers and dkms.
Back to top
Posted: Apr 2, 15, 18:40 stevepusser
 Status: Interested
Joined: 04 Jul 2011
Posts: 15
Reply Quote
Good to see that the downloaded Nvidia driver will build on the 3.19 kernel. We ended up patching the MEPIS backports of the Jessie AMD fglrx packages so they'll work with our Wheezy backports of the 3.19 Liquourix Kernel--Arch is a great source of that cutting edge stuff stuff.
Back to top
Posted: Apr 2, 15, 23:04 techAdmin
 Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Oh, i forgot, there's also an ubuntu ppa that packages latest nvidia drivers, edge something I think. That way you can have latest drivers with dkms and liquorix, as long as nvidia supports latest kernel / xorg of course.
Back to top
Posted: Apr 3, 15, 9:21 stevepusser
 Status: Interested
Joined: 04 Jul 2011
Posts: 15
Reply Quote
:: techAdmin wrote ::
Oh, i forgot, there's also an ubuntu ppa that packages latest nvidia drivers, edge something I think. That way you can have latest drivers with dkms and liquorix, as long as nvidia supports latest kernel / xorg of course.


Do you know that PPA URL offhand? It sounds like a good idea to package it for our community repo, as long as we have a 3.19 kernel in there.
Back to top
Posted: Apr 3, 15, 11:32 techAdmin
 Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
launchpad.net/~xorg-edgers/+archive/ubuntu/ppa

note that I have no firsthand experience, or second hand feedback.

I did read that they say to NOT use only parts, but all of it.

In a sense, this is why I keep doing sgfxi, year after year it works, and just does its thing, while the alternatives continue being unreliable, though much better now than in the past.

I wouldn't personally recommend a ppa that pulls that much stuff in though.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours
Contact Us
Hosting: Pair Networks: 0.037
Forum Style © techpatterns.com
info

tech forums