From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15226] New: lsblk: not found
Date: Fri, 06 Jan 2023 03:25:24 +0000 [thread overview]
Message-ID: <bug-15226-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15226
Bug ID: 15226
Host: qemu_x86
Build: Ubuntu 22 X86_64
Summary: lsblk: not found
Product: buildroot
Version: 2022.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: glscene2010@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Why I can't use lsblk?
_________
Steps to Reproduce. I build Buildroot from git
git clone git://git.buildroot.net/buildroot
make clean -C buildroot
make -C buildroot qemu_x86_defconfig
make -C buildroot
I run
buildroot/output/images/start-qemu.sh
0) Actual Results. I try to use lsblk command via console
# lsblk
-sh: lsblk: not found
Expected Results. lsblk should be found in my system!
1)
lsusb works (return nothing)
2)
# fdisk -l
Disk /dev/vda: 60 MB, 62914560 bytes, 122880 sectors
121 cylinders, 16 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Disk /dev/vda doesn't contain a valid partition table
3)
file
buildroot/output/build/linux-5.15.18/.config
contains
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_SYSFS_SYSCALL=y
CONFIG_SYSFS=y
4)
# uname -a
Linux buildroot 5.15.18 #1 SMP Fri Jan 6 19:29:11 KST 2023 i686 GNU/Linux
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-01-06 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 3:25 bugzilla [this message]
2023-01-06 15:04 ` [Buildroot] [Bug 15226] lsblk: not found bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15226-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox