Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I use in different Linux distribution running on Windows 10-hosted VirtualBox the following command:
lspci -xxxx
It prints dump of config spaces up to 64 bytes
When I try
sudo lspci -xxxx
It prints dump of config spaces up to 256 bytes
Can I get whole PCIe 4096 config space using lspci?
#prl made a good point to check if there is PCI Express capability (capability id 10h).
Turned out that most of devices seen under VirtualBox have all zeros in PCI capabilities space (0x40 thru 0xFF), they also have zero capabilities pointer. Even a device which has some capabilities does not have PCI Express capability.
I think it is VirtualBox emulation limitation.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Are there any way to detect if my server (on debian 6) is using RAID by Hardware or Software?. I have used some command but my server do not recognize them.
/proc/mdstat
omreport storage vdisk
cat /proc/mdstat
The commands upside is the only one that I have tried.
For hardware, try
lspci -vv | grep -i raid.
For software, try the mdadm utility. It is used to manage MD devices (or Linux Software RAID). In particular, try its query command. The mdadm manpage says
This will find out if a given device is a RAID array, or is part of one, and will provide brief information about the device.
You can get a list of devices in /dev with ls -a /dev and then use
mdadm --query /dev/DEVICENAME
Sources:
hardware: https://unix.stackexchange.com/questions/139271/how-to-get-details-of-raid-devices-both-soft-and-hard
software: https://linux.die.net/man/8/mdadm
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have run bitbake core-image-minimal-dev properly configured for a genericx86 machine. BitBake generates a bootia32.efi, a bzImage--<stuff>.bin, an .hddimg, an .iso, a .rootfs.ext3, a .rootfs.ext4, a .rootfs.tar.bz2, and a core-image-initramfs-<stuff>.rootfs.cpio.gz. I'm interested in a method of how to dd one or more of these onto the hard disk of my target machine and boot from that hard disk.
dd if=path/to/imagefile/imagename.hddimg of=/dev/usbdevicename
You'll find the correct usb device name e.g. by plugging in the usb disk and looking at dmesg|tail output -- do not guess as mistakes will be fatal to your hard disk. A practical example from my build machine:
sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-sato-intel-corei7-64.hddimg \
of=/dev/sdb \
bs=4096
Note that you probably want to use intel-corei7-64 as the machine unless you know that genericx86 is correct for your hardware: despite the name former is the common Intel BSP for anything that's not ancient (that includes big Cores, Xeons, Atoms ...).
How to boot the image depends on your target device: you may need to go to BIOS settings to select "boot from USB".
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
From the Red Hat website,
I found the following link ( Red Hat website ) shows the expression to ignoredisk.
ignoredisk_option
From my understanding,
if i set this option to
ignoredisk --only-use=sda
The image will be deployed and installed on to the sda drive on the client host.
1.If I expect to have this image to be installed on the sdb, then I just changed sda to sdb, is this correct ?
2.
bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sdb
For the bootload boot-drive, I should also change it to sdb if I expect the system to be installed onto sdb, is this correct?
Thanks
This kickstart_doc gave me a pretty nice hint.
I finally figured out the usage of my question by going through this document.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to find the command to show the installed memory (RAM) in Red Hat Enterprise Linux Server 6.5.
I have found the following command:
cat /proc/meminfo | grep MemTotal
But it looks like the MemTotal value is not the actual RAM value.
I want to know the real RAM of the system (similar to Installed memory(RAM) in Windows).
Thanks for your help.
Try the free command, which will tell you the total/used/free amounts of RAM you have, the -m flag will display it in MB:
free -m
Though I think it just uses the same source as /proc/meminfo behind the scenes so you may get the same answer.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I'm on a RedHat 5 server, with lm-sensors 3.3.4 installed,
and I executed sensors-detect and then run "sensors", then it just output:
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
How could I get cpu core voltage values from this tool? Do I have to install some drivers or something?
If yes, how do I know what drivers I need to download?
dmidecode shows that: Product Name: ProLiant SL390s G7
Thanks!
sudo dmidecode --type processor | grep Voltage