SliTaz SliTaz Forum

You are not logged in.

#1 2018-11-29 20:25:06

pcoppock1
Member
Registered: 2018-11-29
Posts: 2

Kernel Panic SD Card Boot

I am trying to boot Slitaz from an SD card. I used dd to copy the Slitaz rolling .iso file to the card. While booting, I can select my keyboard layout, which Slitaz version to boot, and what boot parameters to use. After selecting "base" and no boot parameters, I get the following kernel panic error. (In the photo)

Is the problem that I am using an SD card? If so, how can I fix this? Will you be adding SD card support to the .iso's?

Thank you very much for your time.

[attachment=46979,2759]

Offline

#2 2018-11-30 17:32:38

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Kernel Panic SD Card Boot

Slitaz linux kernel configuration doesn't support booting from sd card reader.

Slitaz builds MMC drivers as modules and packages them (linux-mmc).

They're not included on any of the isos.

If the kernel has a driver that supports your reader it would have to be built into the kernel or might work in an initrd.

Offline

#3 2018-11-30 19:09:32

pcoppock1
Member
Registered: 2018-11-29
Posts: 2

Re: Kernel Panic SD Card Boot

Thank you for your reply, mojo.

I am new to modification of the Linux kernel or initrd, and I do not know what general steps I should take to enable support for the SD card. Could you give me some pointers on how to do this? I.e., how to load the correct module/driver during boot by recompiling the kernel or changing the initrd.

Also, I would like to enable support for my ALPS touchpad and my "Intel Dual Band Wireless-AC 8265" WiFi card. Are there specific modules/drivers/packages for these? It is possible that I need a later kernel version to support the above two pieces of hardware.

I would like to roll my own flavor that has all these features enabled as well.

Thanks again, in advance, for your help.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]