Crash Volumio Os

[qpens]

After installing I'm getting kernel panic

[lavolp3]

You need to go into the /boot/cmdline.txt and find the rootfs entry. Change the last number from 2 to 3. Volumio creates three partitions, standard raspbian has only two.

qpens notifications@github.com schrieb am So., 6. Mai 2018, 07:05:

After installing I'm getting kernel panic

[image: img_20180506_051302] https://user-images.githubusercontent.com/30188485/39670033-5f20b09c-50f3-11e8-8841-39bf80296645.jpg

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/goodtft/LCD-show/issues/78, or mute the thread https://github.com/notifications/unsubscribe-auth/ATJ17RHSOr9hIZlLTAiYy8QnctvauFetks5tvoSHgaJpZM4Tz5a6 .

[qpens]

I made new Install. My cmdline.txt: dwc_otg.lpm_enable=0 console=tty1 console=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo

After installing driver:

[lavolp3]

Try changing root=/dev/mmcblk0p2 into root=/dev/mmcblk0p3

And then boot... There's a lot on this issue if you google volumio and kernel panic

qpens notifications@github.com schrieb am So., 6. Mai 2018, 12:49:

I made new Install. My cmdline.txt: dwc_otg.lpm_enable=0 console=tty1 console=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo

After installing driver:

[image: img_20180506_113716] https://user-images.githubusercontent.com/30188485/39672498-f93422ac-5122-11e8-9f77-a3eff3b85f97.jpg

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/goodtft/LCD-show/issues/78#issuecomment-386870440, or mute the thread https://github.com/notifications/unsubscribe-auth/ATJ17ao_5cw2x-KuMt2vR_Zr4wMM-S_cks5tvtVSgaJpZM4Tz5a6 .

[qpens]

[qpens]

I have noticed that that script is replacing cmdline.txt and I made some changes instead raspberry I put volumio and put original cmdline. And now Its dead without HDMI and still no screen on 3.5lcd ;(

this is orginal from volumio splash quiet plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 console=serial0,115200 kgdboc=serial0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh elevator=noop rootwait bootdelay=5 logo.nologo vt.global_cursor_default=0 loglevel=0

[lavolp3]

Why aren't you trying out what I suggested?

The Volumio installation also replaces cmdline.txt and you just used the installation-cmdline.txt and not the final one for the running system. The final volumio cmd-line.txt is here It reads force_turbo=1 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 elevator=noop rootfstype=ext4 rootwait smsc95xx.turbo_mode=N ...

[qpens]

I try with that line and change in script raspberry to volumio and same kernel panic. Some guy from volumio forum gave this info:

"Well, I still doubt cmdline.txt, because your screenshot shows that the kernel can’t find init, this means Volumio is not booting with its specific parameters in cmdline.txt"

[lavolp3]

I will try to test that out for myself soon... also would like to try out volumio again.

[qpens]

cool

[brian777777]

@lavolp3 I just tired your final cmd-line.txt

force_turbo=1 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 elevator=noop rootfstype=ext4 rootwait smsc95xx.turbo_mode=N

and it goes just like what that pic shows....... attempted to kill init! see....

[lavolp3]

@brian777777 I presume you mean cmdline.txt and not cmd-line.txt It is IMO really very much advisable to only change the rootfs entry as shown above instead of the whole cmdline.txt. The file is very sensitive towards formatting. Can you paste your new cmdline.txt here?

[brian777777]

@lavolp3 cmdline.txt,sorry for wrong typing.I re-install the system again.

"Try changing root=/dev/mmcblk0p2 into root=/dev/mmcblk0p3

And then boot..."
you mean this? hope it works this time....