Geez, I'm batting 0 . . . /etc/modprobe.d/modprobe.conf
Anyway, I'm not a wiz with systemd, but it seems this should lead to a potential fix. On Fri, Sep 18, 2015 at 11:48 PM, William Hermans <[email protected]> wrote: > errr, culprit modules . . . > > On Fri, Sep 18, 2015 at 11:48 PM, William Hermans <[email protected]> > wrote: > >> So just a little google searching . . . >> >> https://bbs.archlinux.org/viewtopic.php?id=187314 >> >> The OPs problem is slightly different than yours. Since his problem is >> related to catalyst( AMD ) video drivers. But seems mostly relevant. Check >> /etc/modprobe.d, if such a file exists on Debian Jessie. To see if there >> are any culprit services. >> >> On Fri, Sep 18, 2015 at 11:39 PM, William Hermans <[email protected]> >> wrote: >> >>> Ok, next show us the output from lsmod >>> >>> On Fri, Sep 18, 2015 at 11:29 PM, Rick Mann <[email protected]> >>> wrote: >>> >>>> Hmm, there's this: >>>> >>>> [ 10.554071] systemd[1]: Cannot add dependency job for unit >>>> display-manager.service, ignoring: Unit display-manager.service failed to >>>> load: No such file or directory. >>>> [ 10.770822] systemd[1]: systemd-modules-load.service: main process >>>> exited, code=exited, status=1/FAILURE >>>> [ 10.838716] systemd[1]: Failed to start Load Kernel Modules. >>>> [ 10.844524] systemd[1]: Unit systemd-modules-load.service entered >>>> failed state. >>>> >>>> >>>> >>>> > On Sep 18, 2015, at 22:57 , William Hermans <[email protected]> >>>> wrote: >>>> > >>>> > Rick, try using grep on the output of dmesg to find out what's not >>>> loading. Something like . . . >>>> > >>>> > dmesg | grep module >>>> > >>>> > Where "module" could be any search keyword. >>>> > >>>> > On Fri, Sep 18, 2015 at 10:49 PM, Rick Mann <[email protected]> >>>> wrote: >>>> > Sorry, didn't remember that power-cycle was required. Where is that >>>> documented? Also, why (curious why a regular reset isn't enough)? >>>> > >>>> > I asked systemd, and got the (rather generic, from my googling) >>>> answer: >>>> > >>>> > root@beaglebone:/home/debian# systemctl status >>>> systemd-modules-load.service >>>> > ● systemd-modules-load.service - Load Kernel Modules >>>> > Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; >>>> static) >>>> > Active: failed (Result: exit-code) since Sat 2000-01-01 00:00:08 >>>> UTC; 15 years 8 months ago >>>> > Docs: man:systemd-modules-load.service(8) >>>> > man:modules-load.d(5) >>>> > Process: 162 ExecStart=/lib/systemd/systemd-modules-load >>>> (code=exited, status=1/FAILURE) >>>> > Main PID: 162 (code=exited, status=1/FAILURE) >>>> > >>>> > Warning: Journal has been rotated since unit was started. Log output >>>> is incomplete or unavailable. >>>> > >>>> > I looked through the modules-load.d directories, and found only one >>>> that had anything in it: >>>> > >>>> > root@beaglebone:/home/debian# ls /etc/modules-load.d >>>> > modules.conf mt7601.conf >>>> > root@beaglebone:/home/debian# cat /etc/modules-load.d/modules.conf >>>> > # /etc/modules: kernel modules to load at boot time. >>>> > # >>>> > # This file contains the names of kernel modules that should be loaded >>>> > # at boot time, one per line. Lines beginning with "#" are ignored. >>>> > >>>> > root@beaglebone:/home/debian# cat /etc/modules-load.d/mt7601.conf >>>> > mt7601Usta >>>> > >>>> > I do have a little MediaTek dongle plugged in, although I'm not sure >>>> how Linux magically installed a module conf file for it (this is the stock >>>> console, but I did do apt-get install wireless-tools, did that see the >>>> dongle and install it?). >>>> > >>>> > Anyway, I'm still not sure what's actually failing, or if it's >>>> important. The board seems to be working, Ethernet certainly works, and >>>> iwlist scan returns APs in the area, so I think the wifi dongle came up >>>> okay. >>>> > >>>> > Anyway, not too worried about it for now, just curious. >>>> > >>>> > Thanks, >>>> > Rick >>>> > >>>> > > On Sep 18, 2015, at 22:08 , Robert Nelson <[email protected]> >>>> wrote: >>>> > > >>>> > > So ask systemd... >>>> > > >>>> > > systemctl status systemd-modules-load.service >>>> > > >>>> > > On Sep 18, 2015 11:35 PM, "Rick Mann" <[email protected]> >>>> wrote: >>>> > > And I may have spoken too soon. Actually power-cycling the board >>>> allowed it to come up. But I still don't know what >>>> > > >>>> > > [FAILED] Failed to start Load Kernel Modules. >>>> > > >>>> > > means. >>>> > > >>>> > > Thanks! >>>> > > >>>> > > > On Sep 18, 2015, at 21:32 , Rick Mann <[email protected]> >>>> wrote: >>>> > > > >>>> > > > This is the transcript of the boot and flash and halt. If I >>>> remove the SD card at this point and press the reset button, I just get >>>> CCCCCC... >>>> > > > >>>> > > > http://pastebin.com/GXufknPT >>>> > > > >>>> > > > I see "bad magic", but it seems to proceed on to running the >>>> flasher. It formats the eMMC and reboots, then I see this: >>>> > > > >>>> > > > [ 132.166661] systemd[1]: systemd-modules-load.service: main >>>> process exited, code=exited, status=1/FAILURE >>>> > > > [FAILED] Failed to start Load Kernel Modules. >>>> > > > >>>> > > > Then it continues for a couple more minutes, and eventually shuts >>>> down. Not sure what's causing the problem (don't know enough about Linux to >>>> interpret what I see). >>>> > > > >>>> > > > Help would be much appreciated, thank you. >>>> > > > >>>> > > > -- >>>> > > > Rick Mann >>>> > > > [email protected] >>>> > > > >>>> > > > >>>> > > > -- >>>> > > > 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. >>>> > > >>>> > > >>>> > > -- >>>> > > Rick Mann >>>> > > [email protected] >>>> > > >>>> > > >>>> > > -- >>>> > > 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. >>>> > > >>>> > > -- >>>> > > 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. >>>> > >>>> > >>>> > -- >>>> > Rick Mann >>>> > [email protected] >>>> > >>>> > >>>> > -- >>>> > 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. >>>> > >>>> > >>>> > -- >>>> > 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. >>>> >>>> >>>> -- >>>> Rick Mann >>>> [email protected] >>>> >>>> >>>> -- >>>> 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. >>>> >>> >>> >> > -- 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.
