Tag Info

Hot answers tagged

4

If you're using a standard kernel, it should run on pretty much every hardware, so moving disks from one box to another shouldn't be a problem. That's the theory anyway. However, it may be a different story if it's using some kind of hardware RAID that may not be compatible with another hardware RAID controller. Same for brand-new or exotic hardware that ...


3

USB 2.0 or 3.0 is a hardware specification and has little to do with the OS. There's no way to downgrade (or upgrade) an specific USB version. What you can do is plugging your device in a 2.0 hub. USB 3.0 is totally backwards compatible with 2.0 and 1.1 devices, but some glichs can appear in the kernel implementation of the specification, in such cases is ...


2

make only reports the errors but they are in fact errors from your compiler (probably gcc): error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’ Basically, your code is buggy or inappropriate for your platform but make functions correctly.


1

Apparently there were missing pieces that the driver depended on, that were not auto-selected by the menuconfig. In my case I was missing: pps_core and ptp I found these by booting a working install with the modules folder renamed. This caused the kernel to not find any loadable modules. Then I tried to insmod the e1000e.ko. This indicated that there ...


1

Martin- Very similar setup on my end, except with a pair of nvidia GT9800's - circa 2008!. Also an onboard Intel HD4000 (disabled in bios). xrandr only showed 1 gpu, though all other sys related tools properly reported both. ubuntu 14.04 lts beta 2, nvidia 331.28 proprietary The holy grail fix for me last night was: Base Mosaic! Empty xorg.conf, nvidia x ...


1

Having the windows drivers won't do you any good in Ubuntu, because linux can't use them. A quick search turned up one vivobook model which uses an Atheros AR9485 wifi chip. This is supported by the ath9k kernel driver, which should be included with any stock linux kernel. the wireless card drivers appear to have been corrupted or deleted You have ...


1

As per HP doc (See Moving hard drives and arrays) on SmartArray it seems possible depending on the RAID controller.


1

As explained in the Makefile comments, there is two parts to this Makefile. That's because it will be read twice. First when you call make on the command line, then by kbuild. # if KERNELRELEASE is not defined, we've been called directly from the command line. # Invoke the kernel build system. ifeq (${KERNELRELEASE},) KERNEL_SOURCE := /usr/src/linux ...


1

Did you try downloading the drivers from here? http://www.edimax.com/en/support_download.php?pl1_id=1. Also I found this thread titled: "Thread: Driver installation Probrema 7612UAn Edimax EW-v2" which covers the compiling and setting up of what looks to be the same card as yours.


1

Mikserv's suggestion that the issue here is the driver makes sense. As he points out, you have hybrid graphics and that doesn't work too well under Linux. So, try the following: Install the kernel headers and the nvidia DKMS module sudo aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') nvidia-kernel-dkms nvidia-xconfig ...


1

There is a bug in the drivers. You have the correct driver info loaded. You need to go to /etc/modprobe.d/radeon-kms.conf and set it to this: radeon.modeset=0 Shut down and add the PCI card then go to BIOS and select the correct video adapter and save and reboot. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=58981


1

The best way is to find what programs/services use the old libraries and restart them. And you can achieve it by listing all used files using 'lsof' and find those that have 'DEL' type. DEL means filename was removed from the filesystem but it is still stuck in memory because someone uses it. Here is the full command line: sudo lsof +c 0 | grep 'DEL.*lib' ...


1

This is no good: PATH: /usr/local/rvm/gems/ruby-1.9.3-p194/bin:\ /usr/local/rvm/gems/ruby-1.9.3-p194@global/bin:\ /usr/local/rvm/rubies/ruby-1.9.3-p194/bin:\ /usr/local/rvm/bin:\ /usr/local/sbin:\ /usr/local/bin:\ /usr/sbin:\ /usr/bin:\ /sbin:\ /bin I am willing to bet that in at least a few of those directories you had ...



Only top voted, non community-wiki answers of a minimum length are eligible