Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just did a kernel rebuild to fit my systems specs.
Ive seen a great performance in speed and boot time, but there is one problem. When plugging in any external devices ( thumbdrivers, external HDD(s) etc ) dmesg doesnt give me the information on what name udev has given the device.
This is snippet from the output from ( dmesg | tail -n 10 ) when plugging in a external HDD:
[ 819.784045] usb 4-1: usb wakeup-resume
[ 819.784049] usb 4-1: finish resume
[ 819.787046] hub 4-1:1.0: hub_resume
[ 819.795048] hub 4-0:1.0: resume on port 1, status 0
[ 819.795051] hub 4-0:1.0: port 1, status 0103, change 0004, 12 Mb/s
[ 819.795053] hub 4-1:1.0: state 7 ports 4 chg 0000 evt 0000
[ 821.997020] hub 4-1:1.0: hub_suspend
[ 821.999049] usb 4-1: usb auto-suspend
[ 824.010017] hub 4-0:1.0: hub_suspend
[ 824.010024] usb usb4: bus auto-suspend
[ 824.010027] ohci_hcd 0000:00:13.2: suspend root hub
To be able to find what udev has called the device, i have to now run ( udevadm monitor ).
What have i left out of the kernel build to make it behave like this?
Also to make clear,
CONFIG_USB_ANNOUNCE_NEW_DEVICES *is* compiled into the build.
is this the same kernel version . and did you do a make modules_install. this is not needed for just building the same kernel version. but you did need to configure the the usb modules and build it to be loaded in the kernel. but if you did custom kernel and you did a make modules_install and none of your usb modules are loading is because you you did not configure them to be built. I see the basic usb modules loaded in dmesg that is the ones that are default in your kernel but none of the device modules for usb.
# SCSI support type (disk, tape, CD-ROM)
# see USB_STORAGE Help for more information
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_LIBUSUAL is not set
# MemoryStick drivers
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
all usb devices are considered scsi to linux kernel small computerized integrated systems. whether it is usb ide drive or a usb flash drive. the data transfer is under scsi.
so make sure you have scsi configured for your system.