On Mon, Oct 12, 2015 at 8:55 PM, <[email protected]> wrote: > I have just installed the new Debian 8.2 via the flasher image on a > BeagleboneBlack Rev C with 4DCape. I have changed the uEnv.txt file to > disable HDMI. I get the following errors on install: (Even when I dont > change the uEnv.txt file from default) > > [ 1113.740804] systemd[1]: Job > console-setup.service/start deleted to break ordering cycle starting with > basic.target/start > > [ SKIP ] Ordering cycle found, skipping LSB: Set console font and keymap > > . > > [ 1114.681515] systemd[1]: systemd-modules-load.service: main process > exited, code=exited, status=1/FAILURE > > [FAILED] Failed to start Load Kernel Modules. > > See 'systemctl status systemd-modules-load.service' for details.
Did you ask systemd, it give you a hint above ^^? systemctl status systemd-modules-load.service it would then tell you, that it couldn't find mt7601usb, which is an old remnant of the v3.14.x kernel > > [FAILED] Failed to start Store Sound Card State. > > See 'systemctl status alsa-store.service' for details. Well... you did disable hdmi... along with hdmi-audio, thus alsa noticed something changed... > > > Then when I boot the new image I get the error: > > > [FAILED] Failed to start Load Kernel Modules. > > See 'systemctl status systemd-modules-load.service' > for details. see above... > > > Then I do apt-get update. > > > Then when I do apt-get upgrade I get the following errors: > > WARNING: missing /lib/modules/4.2.2-armv7-x2 > > Ensure all necessary drivers are built into the linux image! > > depmod: ERROR: could not open directory /lib/modules/4.2.2-armv7-x2: No > such file or directory > > depmod: FATAL: could not search modules: No such file or directory > > depmod: WARNING: could not open > /var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.order: No > such file or directory > > depmod: WARNING: could not open > /var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.builtin: No > such file or directory > > ..... > Warning: Unit file of cloud9.socket changed on disk, 'systemctl > daemon-reload' recommended. > .... > c9-core-installer:Installing nak > npm WARN excluding symbolic link > tests/filelist_fixtures/symlink-to-1.txt -> 1.txt > npm WARN excluding symbolic link > tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt > npm WARN excluding symbolic link > tests/search_fixtures/symlink-to-file1.txt -> file1.txt > npm WARN excluding symbolic link > tests/filelist_fixtures/symlink-to-1.txt -> 1.txt > npm WARN excluding symbolic link > tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt > npm WARN excluding symbolic link > tests/search_fixtures/symlink-to-file1.txt -> file1.txt so you ran "apt-get upgrade" and it updated cloud9... so? > Any ideas why this is occuring and how the problem can be fixed ? > Lachlan No "problems" need fixing.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
