Results 1 to 7 of 7

Thread: Using a waveshare 3.5 touch screen with the raspberry pi

  1. #1
    Junior Member
    Join Date
    Feb 2017
    Posts
    6

    Using a waveshare 3.5 touch screen with the raspberry pi

    so I follow this guide https://whitedome.com.au/re4son/sticky-fingers-kali-pi/ on installing the the touch screen but one problem the new kali image for the pi does not have these two file needed to finish the installation.
    "/usr/share/X11/xorg.conf.d/99-fbturbo.conf
    /usr/share/X11/xorg.conf.d/99-calibration.conf"

  2. #2
    Junior Member
    Join Date
    Feb 2017
    Posts
    6
    Quote Originally Posted by makeitjustin View Post
    so I follow this guide https://whitedome.com.au/re4son/sticky-fingers-kali-pi/ on installing the the touch screen but one problem the new kali image for the pi does not have these two file needed to finish the installation.
    "/usr/share/X11/xorg.conf.d/99-fbturbo.conf
    /usr/share/X11/xorg.conf.d/99-calibration.conf"

    I should of say this is the waveshare uses the gpio pin not hdmi port
    I'm using a pi 2 b+

  3. #3
    Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    62
    Hi makeitjustin,

    Those files are not required for the installation of your screen.
    What error message did you get?

    Have you tried this pre-installed image:

    https://whitedome.com.au/re4son/stic...stalled-image/

    That'll get you up and running in a minute without any hassles.

    Hope that helps,
    Re4son
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

  4. #4
    Junior Member
    Join Date
    Feb 2017
    Posts
    6
    Quote Originally Posted by re4son View Post
    Hi makeitjustin,

    Those files are not required for the installation of your screen.
    What error message did you get?

    Have you tried this pre-installed image:

    https://whitedome.com.au/re4son/stic...stalled-image/

    That'll get you up and running in a minute without any hassles.

    Hope that helps,
    Re4son
    Yes I've try it I keep getting "Entering kdb (current=0xdace8000,pid 1) due to keyboard entry kdb>"

  5. #5
    Member
    Join Date
    Nov 2015
    Location
    Australia
    Posts
    62
    Shouldn't happen with a new image.
    You can put the sdcard in a linux PC and run fsck over it, e.g.:

    Code:
    sudo fdisk -l
    sudo fsck /dev/mmcblk1p1 -y
    sudo fsck /dev/mmcblk1p2 -y
    That should do the trick.

    If that doesn't work pm me to sort it out.

    Hope that helps,
    Re4son
    ----------------------------------------
    Check out "Sticky Fingers Kali-Pi":
    https://whitedome.com.au/kali-pi

    Now with mana-toolkit and more goodies!

  6. #6
    Junior Member
    Join Date
    Feb 2017
    Posts
    6
    Quote Originally Posted by re4son View Post
    Shouldn't happen with a new image.
    You can put the sdcard in a linux PC and run fsck over it, e.g.:

    Code:
    sudo fdisk -l
    sudo fsck /dev/mmcblk1p1 -y
    sudo fsck /dev/mmcblk1p2 -y
    That should do the trick.

    If that doesn't work pm me to sort it out.

    Hope that helps,
    Re4son
    yes the stock kali image works, message before line is

    freeing unsed kernel memory:380k (c07cf000 -c082e000)

    kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

    cpu:0 PID:1 Comm:init Not Tainted 4.4.49re4son-kail-pi-tft+ #1

    Hardware name:BCM2708

    2.460444 [<c0016788>] (unwind_backtrace) from [<c00136ac>] (show_stack+0x20/0x24)

    2.474161 [<c00136ac>] (show_stack) from [<c02f0690>] (dump_stack+0x20/0x28)

    2.487393 [<c02f0690>] (dump_stack)from [<c00d659c>] (panic+0x90/0x1fc)
    2.500261 [<c00d659c>] (panic) from [<c00241e0>] (do_exit+0x924/0x95c)
    2.512949 [<c00241e0>] (do_exit) from [<c00242b0>] (do_group_exit+0x4c/0xc0)
    2.526137 [<c00242b0>] (do_group_exit) from [<c002e820>] (get_signal+0x188/0x618)
    2.539825 [<c0019364>] (get_signal) from [<c0019364>] (do_signal+0x94/0x5f0)
    2.553118 [<c0019364>] (do_sigal)from [<c0012f68>] (do_work_pending+0xd4/0xec)
    2.566856 [<c0012f68>] (do_work_pending) from [<c000f928>] (slow_work_pending+0xc/0x20)
    Panic: ATTEMPTED TO KILL INIT! EXITCODE=0x00000004

  7. #7
    Junior Member
    Join Date
    Feb 2017
    Posts
    6
    ok think I found the problem I have fake waveshare screen from here https://www.elecrow.com/wiki/index.p...Pi#Description

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •