Troubleshooting New Kernel Image
01-15-2020, 07:06 PM
I'm having great fun dorking around with the Pinebook Pro, I haven't recompiled the Linux kernel since about 2005 or so, so it's been a while. It's great fun to try and get everything up to speed, I appreciate all the work that went into this project.
So far, I have gotten the
- firmware updates (trackpad)
- default image updates from MrFixit
- package updates from the Debian repo
- all the other password changes, directory renames, etc
Then, of course, more dorking around. I recompiled the kernel on my x86 laptop, to enable DM_CRYPT kernel so I could encrypt my home directly with LUKS, encrypted the SD card I had installed and was finally able to create the filesystem then mount under LUKS.
After several reboots fiddling with the /etc/crypttab and /etc/fstab the Pinebook does not boot. I dont get to the splash screen, I have read in the wiki that I should reset the motherboard so I have ordered a very small screwdriver set from Amazon to reset it.
It has booted one time after I let it be for about 5 minutes awaiting the splash screen, which makes me believe I have some type of connector issue. After all, a faulty kernel wouldn't boot after any length of time. I guess without some type of on-screen message I am really looking for some more advanced troubleshooting techniques?
T
So far, I have gotten the
- firmware updates (trackpad)
- default image updates from MrFixit
- package updates from the Debian repo
- all the other password changes, directory renames, etc
Then, of course, more dorking around. I recompiled the kernel on my x86 laptop, to enable DM_CRYPT kernel so I could encrypt my home directly with LUKS, encrypted the SD card I had installed and was finally able to create the filesystem then mount under LUKS.
After several reboots fiddling with the /etc/crypttab and /etc/fstab the Pinebook does not boot. I dont get to the splash screen, I have read in the wiki that I should reset the motherboard so I have ordered a very small screwdriver set from Amazon to reset it.
It has booted one time after I let it be for about 5 minutes awaiting the splash screen, which makes me believe I have some type of connector issue. After all, a faulty kernel wouldn't boot after any length of time. I guess without some type of on-screen message I am really looking for some more advanced troubleshooting techniques?
T
