After a hiatus I found my machine to be down, but upon turning it on I get significant errors and dropped into emergency mode (see below). This machine wasn't very up-to-date to begin with, so I'm having difficulty determining the order in which to proceed. A couple naive checks and updates on my part are not working. The file system appears to be intact enough to "cd" around and "ls" to see that my files are all (seemingly) there. But the kernel modules aren't loading which is, you know, a problem.
The state I find it in is that it will begin booting to Linux 3.2 (which I know is no longer supported in testing, see below where I tried to update to 3.16), but fails quickly and puts me into emergency mode
Loading, please wait... megasas: INIT adapter done systemd: Failed to insert module 'autofs4' systemd: Failed to open /dev/autofs: No such file or directory systemd: Failed to initialize automounter: No such file or directory systemd: Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
...Then several drives show up as clean....
Running "journalctl -xb" shows that it can't mount the module even though it's there on the disk: ... systemd-modules-load: could not open moddep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin' ... systemd-modules-load: Failed to lookup alias 'firewire-sbp2': Function not implemented ... systemd-modules-load: could not open modeep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin' ... systemd-modules-load: Failed to lookup alias 'loop': Function not implemented
And yet, if I 'ls' that modules.dep.bin file, it's right where it's supposed to be, for the appropriate architecture and everything.
After that (in the journalctl output), it shows several things start up, but systemd-modules-load.service fails: .. systemd: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE .. systemd: systemd-modules-load.service: Failed to start Load Kernel Modules
...and lots of things fail from systemd-udevd: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_ev_event': No such file directory.
I tried updating via apt to the Linux 3.16.0 kernel, but grub wasn't finding it in a way that effects the boot process, and no appropriate "vmlinuz-" file appears with the others on the boot partition. So, I tried switching to grub2 but the update-grub command produces many errors.... For now, grub2 still (attempts to) load the old kernel (3.2) with the same results as I was getting with the old grub-legacy.
Regarding the module-loading features, running "lsmod" shows about 30 lines:
Module ext3 mbcache jbd dm_mod usbhid hid
...I'm at the limit of what I know to check and/or try.
I was wondering how can I determine among the modules loaded at boot which of them are really necessary and which are not, in order to reduce the boot process time and have a more "elegant" system start.
I know this theme is a little bit of complicated because it depends of the user's point of view and demand a high knowledge of which things are happening in your system but I need somewhere to start improving the performance of my debian system.
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 am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/188.8.131.52-smp kernel modules tree found for kernel "184.108.40.206-smp"
I tried to look into the directory and there was only modules under 220.127.116.11. So I tried to change the command into: Quote: mkinitrd -c -k 18.104.22.168 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
I installed linux-image-4.1.0-trunk, when I boot into the kernel there's no wireless available. Dmesg indicates seems like the firmware is loaded, although firmware-iwlwifi is installed: ... [ 11.047031] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-7265D-13.ucode (-2) [ 11.047039] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
How do I get modules in the Kernel to load automatically at boottime? I''m specifically trying to get i810fb to load during the boot process. In Ubuntu, I just had to edit a file and update my initramfs. How do I do this in Fedora?
Tonight I installed ubuntu 10.10 (32 bit) on an external usb harddrive with a dvd I burned and I used my older desktop. I disconnected all internal and external drives first so everything had to be put on the usb drive I selected (only option available). I used the option to load extra software, use the entire hard drive, and let the software do it's thing. I basically had no options where to put things and it didn't have much choice.
When I boot the usb drive on my laptop (win 7 64 bit) by telling the bios to boot to it first... I get an error: modprobe: FATAL Could not load /lib/modules 2.6.35-22 generic modules No such file or directory. This message appears twice and then it does boot into ubuntu and seems to work fine. I'm new to this OS so that is an uneducated guess but the things I have done seem to be working. So exactly what is this error referring too? Is there a way to fix the problem or do I just ignore it.
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/22.214.171.124-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
I've been trying to load my pcmcia network card driver "xirc2ps_cs" at startup with no success. I have added "modprobe xirc2ps_cs" to the rc.modules file but it doesn't load at startup. Curiously, though, if I execute rc.modules AFTER the machine has booted it will load the modules just fine. Just not during the boot up process. Thinking that hotstart might have been causing problems I've disabled hotstart (chmod -x) temporarilly to remove it from the picture, but there was no change.
I've been playing with some intel server board and they provide a type of fakeraid which is called Embedded Server Raid Technology 2. Since Intel officially support RHEL and SLES on their servers, they provide drivers/modules for this fake raid (which supports raid 0, 1, 5 and 10). I have installed RHEL before on these severs and redhat's installer has the ability to load additional modules (via a boot command linux dd).
While intel doesn't provide the modules for other operating systems, they provide a library where people can build their own module for their kernel. I managed to build this module called 'megasr' (for now I've built it for kernel 2.6.32-24-generic which is my testbed at the moment but I would eventually build it for box i386 and amd64 for both server and desktop versions) and load it on a system which is installed on a single drive.
We are able to load it successfully and see the raid 5 as a single volume and access it (partition, format and copy data to it) and all its functions (work in degraded mode, rebuild, etc) work fine but my main goal is to actually install such volume as my main boot volume (similar to how its possible with RHEL or SLES). Is this possible? Load additional modules during the installation that will be present after the installation is finished?
I was using v 8.10. It came to its end of life and I felt compelled to upgrade. I upgraded to v 9.04. All seemed well, but then I discovered that I had no sound. As a test, I booted up with the v 9.04 CD, using it as a live CD. I had sound, so it seems as though it should be possible for me to have sound from my upgraded v 9.04 too, provided I can make the necessary changes to it.
When using the live CD and opening the volume control, I get as the listed device "HDA ATI SB (Alsa mixer)". That doesn't appear when I open the volume control using my upgraded v 9.04. Instead, it says "Playback: Null Output (PulseAudio mixer)". Also, when I check for loaded modules when using the live CD, I get many with snd in their name, but nary a one when using the upgraded 9.04.
Is there some simple way for me to load the same modules in the upgraded 9.04 as are loaded by the live CD? I tried to figure out the answer to this by reading other threads, but was simply overwhelmed by the volume of material and often wasn't sure to which version of Ubuntu it applied.
My nvidia graphics driver was updated last night, and since then I've been unable to get into Gnome without resorting to low graphics mode. I have extensive knowledge of Windoze systems. Upon boot up, I get the following error:
(EE) NVIDIA(0): Failed to load NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration
I've tried some troubleshooting, including attempting to uninstall all nvidia drivers and reinstall (via synaptic).
Administration->Hardware Drivers reports that version 173 is installed loaded and active. Nvidia X Server Settings (nvidia-settings) gives me the "You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server." error.
I've tried the nvidia-xconfig (both with gdm up and down) and it hasn't made any difference.
Oh, it's a GeForce 6200 wwith two Dell E193FPp monitors running on Ubuntu 10.04.
Here's my xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder75) Fri Mar 12 01:42:27 PST 2010 Section "ServerLayout"
My laptop broke beyond repair recently so I am stuck on a 6 year old hp pavilion zv5000 given to me by a friend and I thought I may as well give linux a go, I have been meaning to for years. I've installed xubuntu 10.04 as I heard it is less resource intensive than normal ubuntu but have been unable to configure the nvidia graphics card. I used the hardware drivers program which installed the nvidia accelerated graphics driver 96 (which was the recommended version) and then ran sudo nvidia-xconfig as instructed and got
Code: Warning: Unable to locate/open X configuration file. New X configuration file written to '/etc/X11/xorg.conf'
Which I presume means it worked correctly, but whenever I try to boot I get a message saying "failed to load nvidia kernel module", at which point I either have to restore the generic configuration or just start the session in low graphics mode. I have googled the problem and in a lot of peoples cases it seems to be linked to upgrading from a previous version whilst mine was a fresh install. I tried sudo modprode and it says the nvidia module isn't present. I tried installing the packages in synaptic which mentioned nvidia kernel modules but still no luck.
I am trying to fix my friends laptop and after the most recent upgrade she performed she got this error message when her laptop boots. Thing is that it stays frozen in that mode. I don't even see the grub boot loader. I know its the only operating system she has running on her laptop as well. The following error was encountered. You may need to update your configuration to solve this.
(EE) NVIDIA: failed to load the NVIDIA Kernel module. please check your (EE) NVIDIA: system's kernal log for additional error messages. (EE) failed to load module "nvidia" (module-specific error, 0) (EE) no drivers available She is running ubuntu 10.10
So I just recently got my proprietary driver working yesterday (and enjoyed too many hours of Starcraft 2 afterwards) but today after I downloaded an Update Package and rebooted, it's telling me that it "Filed to load NVIDIA kernel module".So now I'm back to square one, I had to restart in the lower graphics mode or whatever it's called prior to logging in.When I go to System - Admin - Hardware Drivers, nothing shows up and it says no proprietary drivers are in use on this system.
When I try to change the resolution under System - Preferences - Monitors (since everything is so big) I get "It appears that your graphics driver does not support the necessary extensions to use this tool. Do you want to use your graphics driver vendor's tool instead?" I select "Yes" and I get "You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server."I'm a total loss here, I'm assuming something from the update package has caused everything to go haywire and I'm hoping that if/when I get this fixed I don't have to keep doing this fix every time I use the Update Manager.I'm still fairly new to this whole Ubuntu thing, so any step-by-step instructions would be appreciated
i want to do is dual boot windows, Slackware, and Debian. I don't care if i use lilo or grub, they are both equally familiar to me, just above nort. i have made attempts at editing the lilo.conf file, which said it had warnings but i didn't know how to view the warnings. It made it so i could select it, but when i did it booted the slack kernel with debian with no modules. get slack, debian and windows all running on my machine the way they're intended?
I am using Ubuntu 10.04 LTS.With the last update, I have installed the kernel 2.6.32-33.And I have the message "module nvidia failed to load" in Xorg.log.0 My "current" nvidia module is 195. I have tried without success to reinstall nvidia. What I must do ? Wait for a new update of nvidia ?
I am running my PC on Lucid. It has been working fine, but suddenly the other day I got an error message when booting, saying that Nvidia kernel module failed to load. I had to boot in low graphics mode. The only thing i can think of that had changed is that I had recently upgraded to latest Linux kernel 2.6.36-25.I have tried carefully following tips on numerous threads on this forum and others, but still no go. I have purged nvidia drivers and reinstalled nvidia-current (also tried nvidia-glx-185). However, when I then do <sudo modprobe nvidia>, I get this message:
WARNING: All config files need .conf: /etc/modprobe.d/lrm-vide, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/bad_list, it will be ignored in a future release.
When I go to System>Administration>Hardware Divers, it shows Nvidia-current as present but not currently activated.I have blacklisted vga16fb and nouveau in blacklist.conf, done <sudo nvidia-xconfig> etc.I am at a loss as what to do next, and am still new enough to Linux to not be in a position to fiddle to try fix it myself.
0 down vote favorite share [fb] share [tw] This is the problem I run lspci -v which checks all drivers on my system and more. It says kernel driver in use is nouveau. Then under that it says kernel modules: nvidia recent, nvidia-96, nouveau, nvidiafb. So what it looks like I have 3-4 drivers for my video card loaded and one, nouveau, being used. I think they conflict with each other.
I'm trying to add drivers other then nouveau, because the mouse freezes with it. At this point I can't seem to get rid of nouveau, I go to terminal and type: sudo apt-get --purge remove xserver-xorg-video-nouveau And it says that it's not loaded so I can't dump it. lspci-v says nouveau is the driver being used and trying to dump it. It says it isn't installed. I'm confused. I want to dump nouveau, what should I do? I also go into Synaptic package manager and it isn't listed as being installed.
The new kernel upgrade on Fedora 14 will not boot. lib/modules do not exist is the message. Grub was adjusted to match the old kernel, and the new kernel when booting says lib/modules do not exist. The old kernel has twice as many modules as the new kernel in lib/modules. How do I get the new modules to install so I can boot with the new kernel then? Should I reinstall the new kernel?
I want to remotely install OpenSUSE on one of my servers. I followed the instructions given at SDB:Remote installation - openSUSE, but it didn't work. (My server reverted back to the already installed system.) I think this has to do with a special kernel module (megaraid_sas) that is necessary for the raid controller. Without this module, the kernel cannot find any disk. Of course, the module is not included in the initrd provided by OpenSUSE. I know how to add files to the initrd, but I have no idea where I have to put the required kernel module and which config file inside the initrd must be modified to make the kernel load the module.
Over the past few days I have been trying to install an older kernel (kernel 126.96.36.199) on ubuntu 9.10 64-bit WUBI installation. I compiled, installed, and updated my grub for the kernel. When I reboot, the grub menu correctly gives me the option of booting into the older kernel but when I do so I receive the following error message:
error: you need to load the linux kernel first.
I am at a complete loss on how to fix this. I even downgraded grub but I still get the same error.
I have noticed in the recent updates there is a Kernel update 2.6.32-22 but there is no restricted modules included. On my Desktop I have a Nvidia card which I installed the driver using the Hardware Drivers Application. As far as I know these Drivers are ether reinstalled or updated whenever there is a kernel update.
I also have a Laptop with a ATI Radeon card which I did run the updates and ended up (after the reboot) in low graphics mode, after a bit of work I was able to reinstall the drivers and get my desktop back so that's ok now.
I had this problem a few years ago with an old version of Ubuntu, kernel updates but no restricted drivers. The drivers turned up the next day and all was fine. I was just wandering if this is a known issue with Lucid or if anyone else has had this problem, It's been a couple of days since I noticed the Kernel update but still Restricted Modules. Oh I'm using Ubuntu Lucid 10.04