Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
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.
In support of a fast boot (Intel ATOM Z530 CPU, 2.6.31) we removed udev.
In the meantime we had to get the X server running to support graphics, as a result of that, udev was added back in.
Later we realized that udev was or some reason managing, and thus removing serial USB peripherals; however those peripherals are needed to be there all the time. These are standard FT232 serial USB devices, they do work, and I have no idea why udev detects them and then removes them as part of the boot sequence.
End results are:
- Udev not running, we can see and talk to all serial USB devices, and likely to the USB WIFI adapter (we merely haven't done much with that as yet) BUT we can't load Xserver.
- Udev running, we can load Xserver, but it causes the USB serial devices to be detected and then removed.
We'd like to figure out how to get Xserver running without udev running. The system boots faster and we do not have to worry about weird device behaviors.
hald is running and (not knowing too much about it) my guess is that when I don't run udev at all, hald is providing information for the Xserver.
The problem there is the following:
With udev, the Xorg log file shows:
LoadingModule: extmod, dbe, glx, freetype, dri, iegd, lvds, sdvo, fb, and ramdac
When udev is not running, it goes as far as iegd and then does not run the remaining modules.
This does have two displays, the Intel ATOM chip has a controller (Intel US15W) that has both LVDS and SDVO outputs and we have an xorg.conf that provides the proper settings for these displays.
What I don't know is the information that udev provides to allow the Xserver to load those final 4 modules and get fully operational. Since they are .so files, I can't load them as modules, I instead have a chance at finding the right modules to run at startup, or need to find the correct options to indicate to Xserver that these need to be included.