DamnSmallLinuxThis forum is for the discussion of DamnSmallLinux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Every single time I tried to start x, I got this exact same message on all 3 machines:
Code:
xauth: creating new authority file /home/dsl/.Xauthority
xauth: creating new authority file /home/dsl/.Xauthority
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: init module: no such device
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: insmod char-major-10-134 failed
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining
Are you talking about running the "wizard" that sets up X86? If so, I've run it like all possible ways, but something still isn't right and X still wont start...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.