Hi! > Then I was (finally!) able to run dmesg, and that tells me: > > [ 0.816040] mousedev: PS/2 mouse device common for all mice > [ 0.817657] input: TWL4030 Keypad as > /devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl@48:keypad/input/input0 > [ 0.820800] i2c /dev entries driver > [ 0.830261] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout > 60 sec > [ 0.836212] omap_hsmmc 480b4000.mmc: RX DMA channel request failed > [ 0.840026] ledtrig-cpu: registered to indicate activity on CPUs > [ 0.840789] omap-aes 480c5000.aes: OMAP AES hw accel rev: 2.6 > [ 0.840942] omap-aes 480c5000.aes: Unable to request in DMA channel > [ 0.841644] omap-aes 480c5000.aes: will run requests pump with > realtime priority > > Kernel 4.13-rc2. Aha. DMADEVICES=y, then DMA_OMAP can be selected. Then mmc works. Debugging is much easier with dmesg :-). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
