Hot answers tagged devices
Formatting a device directly is extremely common in environments where the underlying block device represents something other than a physical disks, and where it is easy to create new devices or resize existing devices. You'll generally see this for iSCSI or Fibre disks, and of course for LVM logical volumes. There is often a substantial disadvantage to ...
lspci will do the trick as said by several others. Some additional clarification: Every modern bus-interface (Vesa Local Bus, PCMCIA, CardBus, PCI, PCI-X, PCI-e, Thurderbolt, IDE, ATAPI, SATA, USB, Firewire, just to name a few that come to mind) defines a set of low-level probe commands so the OS can detect which devices (if any) are present on that bus. ...
lspci -v will show the connected devices, even if there's no corresponding driver.
I also like the lshw on those distributions to offer it. Lots of good information about your CPUs, memory slots, USB slots, disks, and more.
mdev is a light-weight alternative to udev for usage in embedded devices. Both handle the creation of device files in /dev and starting of actions when certain events happen.
Why use gpsd? Just use the NMEA driver and enable PPS with flag1: server 127.127.20.0 minpoll 4 mode 18 prefer # NMEA serial port, 16 = 9600 baud, 2 = $GPGGA fudge 127.127.20.0 time2 0.435 flag1 1 flag3 0 You should change your fudge time to whatever is appropriate. You can get the position data from the clockstats file.
If you want extended information of all hardware, you can use dmidecode command. It dumps the DMI table contents.
How about lspci -v or lspci -k? 06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) Subsystem: Intel Corporation Device 1050 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at da000000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: ...
Looks like there is something a little odd going on with your system. The dladm output is only showing e1000g0. It should show all four interfaces even if they're not plumbed. More worrying is that it isn't showing your e1000g3 interface which is plumbed. Here's equivalent output from a T5120 (uses e1000g also), with interfaces e1000g0 and e1000g1 plumbed ...
Here is a link to the mdev primer.
You can boot from ubuntu CD into recovery mode. Then, you can execute a root shell. Look for your drives using: # ls -l /dev/disk/by-uuid/ You should get symlinks to your actual drives such as /dev/sda1 and /dev/sda2. Look at /etc/fstab and compare the UUID you found there with UUID you got from ls. You can edit the fstab accordingly. You can try to ...
Only top voted, non community-wiki answers of a minimum length are eligible