jgauthier Posted April 26, 2020 Posted April 26, 2020 Greetings, I haven't built a new image for awhile. But, I wanted to refresh the process. In the meanwhile, the only change I've made is upgrading my host. My build platform is a VM. I have no idea if that matters, but it was a change. I now have some weird errors/warning and I want to troubleshoot them. How can I enter into the environment to run just the customize script and commands? I'd like to dig into them, but not sure how. Thanks!
Igor Posted April 26, 2020 Posted April 26, 2020 2 minutes ago, jgauthier said: have some weird errors/warning Show them.
jgauthier Posted April 26, 2020 Author Posted April 26, 2020 3 minutes ago, Igor said: Show them. I understand, but they are not specific to Armbian so I did not want to engage with the team with troubleshooting. But, since I use BananaPi, I want t upgrade the firmware, So I use /usr/local/bin/bpi-update -c bpi-pkg-bpi-wiringpi.conf To install some software for GPIO. I get this: Unsupported setsockopt level=270 optname=3 sudo: Account or password is expired, reset your password and try again sudo: no tty present and no askpass program specified sudo: unable to change expired password: Authentication token manipulation error Which is something inside the script. But I can't troubleshoot what specifically until I can get into that environment. Then when I try to run a configure script for some software I see a whole lot of this: config.status: creating Makefile qemu: Unsupported syscall: 382 config.status: creating include/Makefile qemu: Unsupported syscall: 382 config.status: creating lib/Makefile qemu: Unsupported syscall: 382 config.status: creating tools/Makefile qemu: Unsupported syscall: 382 config.status: creating tests/Makefile qemu: Unsupported syscall: 382
Igor Posted April 26, 2020 Posted April 26, 2020 16 minutes ago, jgauthier said: Which is something inside the script. But I can't troubleshoot what specifically until I can get into that environment. Why don't you build an image and debug on board?
jgauthier Posted April 26, 2020 Author Posted April 26, 2020 33 minutes ago, Igor said: Why don't you build an image and debug on board? It never happened on the board. I built this using that method and after I upgraded my VM host these popped up. It would be a whole lot faster to be able to "get into" the environment during the build and see what programs are causing these warnings/errors.
Igor Posted April 26, 2020 Posted April 26, 2020 1 hour ago, jgauthier said: qemu: Unsupported syscall: 382 This is usually safe to ignore 1 hour ago, jgauthier said: bpi-update -c bpi-pkg-bpi-wiringpi.conf While this you need to debug. It probably checks some hardware functions.
jgauthier Posted April 26, 2020 Author Posted April 26, 2020 28 minutes ago, Igor said: This is usually safe to ignore While this you need to debug. It probably checks some hardware functions. Agreed! I previously debugged this and have written an image with it successfully. It used to work fine. Now it doesn't. So if I can drop into the environment to debug it on the build platform, that would be great. Is it possible to get into the build environment?
jgauthier Posted April 26, 2020 Author Posted April 26, 2020 Well, I stuck a 'bash' in the customize script and I can get into the build env. Turns out 'sudo' is a problem. #sudo ls Unknown host QEMU_IFLA type: 47 Unknown host QEMU_IFLA type: 48 Unknown host QEMU_IFLA type: 43 Unknown host QEMU_IFLA type: 47 Unknown host QEMU_IFLA type: 48 Unknown host QEMU_IFLA type: 43 Unsupported setsockopt level=270 optname=3 sudo: Account or password is expired, reset your password and try again Changing password for root. sudo: no tty present and no askpass program specified sudo: unable to change expired password: Authentication token manipulation error
Recommended Posts