I'm using openSUSE 11.3 with an Intel Corporation Mobile 945GME Express Integrated Graphics Controller. The kernel driver in use is i915, however, in another distribution of Linux, two kernel modules are loaded: i915 and intelfb. I would like to know how to load module intelfb in openSUSE 11.3 as it seems to significantly improve my video card's responsiveness.
I have been trying to run my vmachines in virtualbox with no success so I decided to install upgraded packages for upgraded kernel, this means to install them from Virtualization-kernel-HEAD repo.The error is about that known issue where the kernel module can't start.
It is bad enough that the kernel gods have basically required that the whole kernel source tree be installed and configured to compile even a simple module but they have made it so a module compiled on one kernel will not work on any other.
To make the situation worse much of the configuration needed to successfully compile a module has been left out of open suse11.3. If you want to replicate the problems may I suggest you attempt to compile the usb-skeleton.c driver example code that is included with each kernel. If it is the intent of the linux community to limit driver development to the professionals then congratulations.
I have just reinstalled OS 11.2 but this time the 64bit system variant. I installed the real-time kernel and saw that the apparmor module reported an error and wasn't loaded. I have never looked into apparmor and only knows it has something to do with security, and thus I wonder if it is important to do something with this issue? I plan to use the kernel-rt and have more or less always used a variant of this kernel flavour, often self built. Though I can not recall having seen that error before and I have not used a 64bit system before
I have been having some problems with virtualbox starting. So here is the issue: When I start a VM I get the following: Code: Kernel driver not installed (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. reinstall the kernel module by executing
I am seeing quite a few entries about the usb. I am not sure if that is common or if its unrelated. I am running x86 11.3, and virtualbox 4.0.4 I have tried to uninstall, and even go back to 3.2
I just up-graded to the latest version of the stable 11.4 64bit kernel on my laptop and it appears that the repositories have not compiled the VirtualBox driver module for the current kernel ... When I make /vboxdrv setup the message is:
Recompiling VirtualBox vboxadd kernel module, NOT. It has been packaged
I think this means that the installed module will not recompile has it was packaged. My kernel version is the lattest :
And my VirtualBox was installed from the Virtualization repos (184.108.40.206-1) even made the Vendor change and all. The version Before the lattest (4.0.4-1.6) did not work either. With the same problem. It is very easy to install VirtualBox from the Sun site and every time there is a Kernel up-date one can always make /etc/vboxdrv setup.
I Just loaded 11.2 64 bit, initially the kernel was "default", however, after I installed my Nvidia drivers it changed to desktop, I'm not sure I understand? In GRUB my screen lists it as desktop. Is "default" somewhere? Was it replaced? Things seem to be working alright in most cases although I'm having inordinate problems with "virtual Box" and Vmware server. In Vbox the kernel module won't start.
I've upgraded kernel 220.127.116.11-0.2-default to 18.104.22.168-0.1.1 on openSUSE 11.1. Before I tried to upgrade to 22.214.171.124-0.3-default where I encountered the same issue. After reboot it can not find the modules for 126.96.36.199-0.2-default which puzzled me to no end. Now I have found that the /boot which is on separate partition of ext2 type is not mounted. The mount command does not recognize ext2 and xfs anymore.
Clearly the initrd does not have the right modules. Since this is standard zypper up process I would expect this to work without issues since it has worked until the 188.8.131.52-0.2-default kernel without issues. Has something changed with the last 2 kernel versions that requires some extra actions from me and if so what do I have to do.
I have installed Virtualbox PUEL in 64-bit 11.3. This is a fresh install. My computer has an onboard nvidia 8300GS graphics card. I do not think this is related to the issue. I added the virtualbox repository and installed the program via yast. when I type "VirtualBox" in the terminal I get the following output:
I'm trying to install the nVidia driver for a fresh Installation of OpenSUSE 11.4 (32-bit) but I'm running into some issues. I followed the instructions (SDB:NVIDIA the hard way - openSUSE) using the driver binary mentioned in the workaround link (NVIDIA DRIVERS 256.53 Certified) but the installer fails while building the kernel module with the following errors:
Code: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sun Mar 13 17:32:56 2011
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
I've installed openSuse 11.4 server-mode (text only) on my desktop, and I'm trying to configure IceWM so i'll eventually have it set up so it always boots into text only mode, but I could be able to quickly start icewm via the command line.using Yast, I installed the Xorg server, and icewm.when I type X, the screen goes black and it just doesn't seem to do anythingI found if I hit ctrl+alt+f1 it kinda puts me back into text only mode, but I can't put in commands anymore. The last thing it says on the screen is:
Failed to load module "fglrx" (module does not exist, 0)
I've goggled that error message and the discussions that popped up around it made no sense to me at all. I've never configured X from scratch before, can someone point me towards a tutorial or something?
I recently bought an AMD R7 360 videocard and I'd like to use the free Radeon driver.
Problem is, PCI-ID 0x665f is not present in Jessie's 3.16 kernel sources. The hardware however is supported, it's just not recognized. So I'll have to get the Debain sources and patch include/drm/drm_pciids.h
From the 4.1rc1 kernel I know what to patch and where.
Debian page that explains how to use the Debian build system for recompiling the current kernel from Debian packages?
I have a Samsung phone GT-B3210. For some time I was unable to find working Windows drivers for it. I eventually gave up looking. Then one time I was charging phone over its USB port and booted Ubuntu and was pleasantly surprised when I saw phone's μSD card reader on my desktop. I now need to switch to Gento and would like to be able to work with phone there too. Lsusb tells me it's detected as Bus 007 Device 006: ID 04e8:663f Samsung Electronics Co., Ltd SGH-E720/SGH-E840but lsmod wasn't very helpful. On the list of loaded modules, I wasn't able to find one which looks like it's related to the phone.
I have inserted a module with modprobe. However it seems to have problem. 1- How can I remove the module from modprobe? 2- If I reboot and the kernel can not boot up because of this faulty module, how can I remove it?
The problem I'm facing is that I can't use my headphone. Sound works, but not the headphone. See my ealier thread. It was suggested to edit the module options, but I don't quite know which buttons to push.
I'vd a problem with loading modules. Booting gives the this error:
Code: Select alllucas@debian8-1:~$ systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● systemd-modules-load.service loaded failed failed Load Kernel Modules
LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type.
Always the same error when booting. After a period of time, (Graphical User Interface) the mouse click no longer operates, also text input isn't possible.
I had no access to the system at all, even crt alt F1 stopped working, also text input was no't possible. so reinstall was the only option. Maybe there is a connection with this two errors.
I've reinstalled Debian 8 several times. Still, both errors stay.
The same happend again (in the GUI) is nothing possible, no txt input, no mouse click), but now I have access to the system, ctr/alt F1 is working.
I'm having problems to compile XIllybus kernel module. As this guide explains, [URL] ..... (on the top of page 8 of 25) I unpackaged the tar.gz file and compiled the kernel module by typing the make command in the proper path. When I compile the module with make command, I get the following error:
make -C /lib/modules/3.16.0-0.bpo.4-amd64/build SUBDIRS=/home/xillybus/module modules make: *** /lib/modules/3.16.0-0.bpo.4-amd64/build: No such file or directory. Stop. make: *** [default] Error 2
/lib/modules/3.16.0-0.bpo.4-amd64/build path does not exist. What does it mean? Should I have to install some kernel packet? www does not work for me.
I'm trying to build the kernel module for dvbhdhomerun. The problem is the linux kernel headers provided by Debian do not have the dvb header files. Trying to set up my own kernel source tree to use is not working out so well.
I'm following the instructions in the Debian section here: [URL] ....
My first try compiled, but the modules ender up under /lib/modules/3.2.51/extra instead of /lib/modules/3.2.0-4-amd64/extra. Why?
I tried to start over, but noticed this while running apt-get source linux-image-3.2.0-4-amd64:
Code: Select allReading package lists... Done Building dependency tree Reading state information... Done Picking 'linux' as source package instead of 'linux-image-3.2.0-4-amd64' NOTICE: 'linux' packaging is maintained in the 'Svn' version control system at: svn://svn.debian.org/svn/kernel/dists/trunk/linux/
The failure to verify the signature has me concerned, but beyond that, what do I do about the different version number when compiling and installing the kernel modules?