|
inxi 2.0.0
New feature: shows with -Ix or -Ixx (Eye): :: Code ::
# ARCH current Info: Processes 282 Uptime 3 days Memory 6390.2/11868.6MB Init systemd v 208 default graphical.target Gcc sys 4.8.2 Client Quassel v0.10-pre (0.10-pre+36 git-5b1428b*) inxi 2.0.0 # Debian Info: Processes 156 Uptime 47 min Memory 723.8/3841.7MB Init SysVinit v 2.88 runlevel 2 default 2 Gcc sys 4.7.2 alt 4.4/4.5/4.6 Client Konversation 1.4 inxi 2.0.0 # Siduction Info: Processes 124 Uptime 2:07 Memory 145.1/831.5MB Init systemd v 204 runlevel 5 default 5 Gcc sys 4.8.2 alt 4.4 Client Irssi 0.8.15 inxi 2.0.0 # xubuntu Info: Processes 81 Uptime 1:52 Memory 82.7/908.9MB Init Upstart v 1.11 runlevel 2 default 2 Gcc sys N/A Client Irssi 0.8.15 inxi 2.0.0 # vsido Info: Processes 147 Uptime 1 day Memory 342.8/8002.7MB Init systemd v 204 runlevel 5 default 2 Gcc sys 4.8.2 alt 4.7 Client X-Chat 2.8.8 inxi 2.0.0 -x turns on Init/Runlevel, -xx init version, default runlevel. OpenRC presence will show as RC: OpenRC v: x.xx but because rc data is too mushy on the other systems I'm not showing rc unless it's open rc. To get sysvinit version number requires a hack, using: :: Code :: strings /sbin/init | grep versionI do not have the package owner for strings in arch, fedora, or the other covered distros in inxi so --recommends won't show that info for them, just debian/ubuntu apt. Solidly supported output from: systemd, upstart. Those are unlikely to be wrong in terms of truly being the init system. Epoch and Runit are missing data in terms of checking to make sure they truly are the init system, and not just installed. sysvinit is a default because it's the only one that you really can't test for, so I do a test of: if file exists: /etc/inittab after the other cases have been handled, then assume it's sysvinit corner cases would be where you installed various init systems but don't actually use them, that will be handled in further releases as I gather more data. Back to top |
|||||
|
Please note: I am still collecting data on alternate init systems, to get them really accurate, I need the following:
a check on the system to see if it is running, ideally via ps aux or a pid in /run or something like that. A way to get its version number once detected, for example: epoch version runit uses /sbin/sv but I do not have any way to find if I can get version data from that. Both epoch and runit tests would give false results currently if soeone installed the packages but didn't actually use it, since it checks files exist, not that it actually runs the init. systemd and upstart are accurate I believe, systemd is the most accurate since I can query pid 1 directly to see who owns it. Back to top |
|||||
|
inxi 2.1.0
A long standing issue report which I thought I'd never fix, is now working! help/version now prints to dynamically sized width, based on the width of the temrinal, with a max column width of 120. The max width is a configuration option, so you can change it in your inxi config file, like so: :: Code :: COLS_MAX_CONSOLE=110or whatever you want it to be. 110-120 is about right for decent display, and it will go down to whatever your temrinal/console width is. I'll be rolling this feature out to smxi/sgfxi too since the method is pretty solid. The downside is that it's slower, takes new systems 0.5 to 1.0 seconds to show the menu, but that is way better than my first attempts, which took a lot longer. It's unusual for inxi to get two major version bumps this quickly, but I didn't think I'd actually get to the dynamic resizing so quickly, but it all sort of fell into place. <updated: 2014-103-14> fine tuned sizing, started work on lines, now -C and -f should size dynamically down pretty small, or big. Back to top |
|||||
|
with the latest update of inxi, 2.1.5, i see my single laptop graphic card listed twice.
:: Code :: inxi -Gxxx
Graphics: Card-1: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0 chip-ID: 8086:2a02 Card-2: Intel Mobile GM965/GL960 Integrated Graphics Controller (secondary) bus-ID: 00:02.1 chip-ID: 8086:2a03 Display Server: X.Org 1.15.0 driver: intel Resolution: 1280x800@60.0hz GLX Renderer: Mesa DRI Intel 965GM x86/MMX/SSE2 GLX Version: 2.1 Mesa 10.1.0-rc2 Direct Rendering: Yes Back to top |
|||||
|
damn, unexpected consequences, grrr.
show me lspci please I added support for 3D controller and Display controller if the same device is named twice it's almost certainly because it's using those in different senses. Annoying. Wait: no, I take it back, I was wrong, those are two devices, see the different bus id and chip id? But do show lspci please. Back to top |
|||||
|
2.1.6 should now be correcteed, but do please post the lspci output so I can confirm that what I think happened happened.
The same card in some cases appears to show as both a VGA or a 3D controller, I want to make sure that was the cause of the doubled thing. The bus id and the chip id is different however, but that's too confusing, and for sgfxi, it would cause serious breaks. I believe this may be an EFI issue, is your system uefi? Back to top |
|||||
|
here you go
:: Code :: lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02) 15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) 15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11) no, it is not. here is the entire inxi: :: Code :: inxi -Fzxxx
System: Host: hell Kernel: 3.13-6.dmz.1-liquorix-686 i686 (32 bit gcc: 4.8.2) Desktop: Fluxbox 1.3.5 dm: nodm Distro: antix Machine: System: LENOVO product: 89329WU v: ThinkPad R61/R61i Chassis: type: 10 Mobo: LENOVO model: 89329WU Bios: LENOVO v: 7OETC3WW (2.23 ) date: 05/12/2009 CPU: Dual core Intel Core2 Duo CPU T5250 (-MCP-) cache: 2048 KB flags: (lm nx pae sse sse2 sse3 ssse3) bmips: 5985 Clock Speeds: 1: 1000 MHz 2: 1000 MHz Graphics: Card-1: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0 chip-ID: 8086:2a02 Card-2: Intel Mobile GM965/GL960 Integrated Graphics Controller (secondary) bus-ID: 00:02.1 chip-ID: 8086:2a03 Display Server: X.Org 1.15.0 driver: intel Resolution: 1280x800@60.0hz GLX Renderer: Mesa DRI Intel 965GM x86/MMX/SSE2 GLX Version: 2.1 Mesa 10.1.0-rc2 Direct Rendering: Yes Audio: Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:284b Sound: Advanced Linux Sound Architecture v:: k3.13-6.dmz.1-liquorix-686 Network: Card-1: Broadcom NetLink BCM5787M Gigabit Ethernet PCI Express driver: tg3 v: 3.134 bus-ID: 04:00.0 chip-ID: 14e4:1693 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945 v: in-tree:s bus-ID: 03:00.0 chip-ID: 8086:4227 IF: wlan0 state: down mac: <filter> Drives: HDD Total Size: 120.0GB (48.3% used) 1: id: /dev/sda model: HITACHI_HTS54161 size: 120.0GB serial: SB3D04EWGRD70E Partition: ID: / size: 2.0G used: 1.3G (67%) fs: ext4 Sensors: System Temperatures: cpu: 42.0C mobo: 32.0C Fan Speeds (in rpm): cpu: 3018 105 Info: Processes: 86 Uptime: 4:21 Memory: 389.8/998.0MB Init: systemd v: 204 runlevel: 5 default: 5 Gcc sys: N/A Client: Shell (bash 4.3.01 running in rxvt) inxi: 2.1.6 Back to top |
|||||
|
I guessed wrong, inxi -U and it will be right again.
I hit this particular issue on another thread: :: Code :: lspci
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:02.0 Display controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) 00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02) 00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) 01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02) and assumed that Display controller was an alternate syntax, but clearly there is more going on than I thought. On another, older, test system, I got two results too, for VGA compatible.. and Display controller, for the same card. So that puts me back at square one, failure to id one card on some systems, but if I fix that, the same card gets id'ed twice on other systems. What's worse is that the actual lspci output for each line if it's the same card is different, the chip id is different, the bus id is different, so I can't do a double check to make sure that it's not the same card by comparing bus is or chip id or card name. This one is tricky, any ideas? I believe though I'm not certain that if the first part of the bus id string is the same, it is the same device, like yours: 00:02.0 00:02.1 where only the last digit is different. Whereas the different one is: 00:02.0 01:00.0 that's a built in and an aftermarket, or something. I'll obviously need to collect more data. I believe stripping off the last digit of the bus id and using that to identify the real card will work, from what I can see, the 00 part is the actual pci slot, so 01 and 02 are pcie slots 1 and 2. 00 is motherboard attached, 05 is regular pci slots, I think. Yes, that appears to be right: :: Code :: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2)
02:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1) there you see it, the device itself is: 02:00 and .0 is the video part, and .1 is the audio part of the card. So I think that's adequate as a test to avoid dual detection of single card. Thanks for spotting this so quickly. Back to top |
|||||
|
i see it, looks like a valid answer for the problem. thank you for fixing it.
also, i noticed that inxi outputs a number above the Info line. Back to top |
|||||
|
ah, forgot to remove the debugger from something else, thanks. that's removed now.
The logic to handle this will be much harder than it was however, and I'm not sure how to grant one card over another priority, maybe pick the .0 as the main card, and the .1 as the alternate? that could work. So build an array of cards, then only print out the ones that are .0 versions, that might do it, using the busid. Very tricky stuff heh. I'd never seen a non vga compatible controller output with lspci until a few days ago, and there they are, all over. This issue is all over the forums but nobody has pulled the pieces together I think. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||