•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the *nix Hardware Configuration section within the Tech Talk category of DaniWeb, a massive community of 396,972 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,914 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our *nix Hardware Configuration advertiser: Lunarpages Linux Web Hosting
Views: 695 | Replies: 8
![]() |
Not really. Hardware support is usually provided by kernel modules, which means that if they exist on your system, they get autoloaded when the computer starts or sometimes even when new hardware is plugged into a running system. If you don't have the appropriate kernel modules to detect a particular piece of hardware, the system won't be able to figure out what driver is needed anyway, so it's assumed you're going to handle it on your own.
Last edited by John A : Apr 12th, 2008 at 8:12 pm.
tuxation.com - Linux articles, tutorials, and discussions
lspci
lsusb
Toshiba M115 ● 1.49 GB DDR-2 RAM ● 1.6 GHz Centrino Duo ● 80GB HDD ● Windows XP Media Center Edition
>.....How will I know what modules I have/havn't got ?......
More importantly, how do you know which modules you need?
Basically, you can find out if a particular piece of hardware is detected by running the commands linux gave (or check the output of the
If it isn't detected, you need to do research to find out how support is provided for that piece of hardware (generally it requires you having to either recompile the kernel or compile and install a software package which will result in a module).
Finally, you can manually load a module with the modprobe command (as root). In a terminal, you would type
More importantly, how do you know which modules you need?
Basically, you can find out if a particular piece of hardware is detected by running the commands linux gave (or check the output of the dmesg command). If its name is listed there, it's been detected. If it isn't detected, you need to do research to find out how support is provided for that piece of hardware (generally it requires you having to either recompile the kernel or compile and install a software package which will result in a module).
Finally, you can manually load a module with the modprobe command (as root). In a terminal, you would type
modprobe module_name. If it doesn't give any errors, it's been loaded successfully. If it says that it doesn't exist, you most likely don't have the module installed. tuxation.com - Linux articles, tutorials, and discussions
another few things to go for:
fdisk -l to detect unmounted drives
look in the /proc directory - it contains a lot of online hardware information
dmesg will show the hardware detected during boot
kudzu (not sure ubuntu has it, RHEL sure does)
fdisk -l to detect unmounted drives
look in the /proc directory - it contains a lot of online hardware information
dmesg will show the hardware detected during boot
kudzu (not sure ubuntu has it, RHEL sure does)
Real stupidity always beats Artificial Intelligence. (Terry Pratchett)
BA BizMg, MCSE, DCSE, Linux+, Network+
BA BizMg, MCSE, DCSE, Linux+, Network+
![]() |
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
•
•
•
•
DaniWeb *nix Hardware Configuration Marketplace
- Previous Thread: Nothing shows up in lsusb
- Next Thread: Ubuntu 7.10 doesn't mount my second HDD



Linear Mode