SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Right... so here's the story. A friend got pissed off at WinXP and asked me to setup linux on his Thinkpad T21.
I'd like to think I know my way around Slack decently, but this is the first laptop I've worked on with linux.
I've got the following problems:
--when logging out of any desktop and *trying* to get back to kdm, the screen goes black and the system goes unresponsive (only taking out the battery at this point does anything).
--ethernet card(e100) isn't working. I've heard that it might be because of ACPI.
I've been to Thinkwiki and Linux-laptop as well as a healthy ammout of googlin'. Nothing seems to be any specific help [not written 'for dummies']
First - instead of pulling out the battery try to push the main power button for appr. 5..7 seconds.
This should switch off your T21 as it happens to my T23 when there is a serious lack of response.
Assuming that you have one of the latest Slack installed please check the content of /etc/modprobe.d/blacklist for this entry:
blacklist eepro100
For my T23 it is a must so set yours the same way. It should be uncommented (without # at the beginning of the line).
After rebooting your T21 invoke this at the terminal:
lsmod | grep 100
And you should get something like this in return:
e100 35724 0
which means that proper module for ethernet card is loaded.
According to problem with leaving graphical managers like KDE/Xorg please post here your /etc/X11/xorg.conf content. I had a similar problem some time ago and a newer Savage video driver fixed it.
Also disabling 3D rendering in xorg.conf may temporarily fix the problem. Commenting (#) these entries:
Location: Danville, VA Approx. N 36°36.434' W 79°24.342' Accur. 100' or so.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,209
Rep:
The e100 module is loaded, have you tried running
Code:
netconfig
or bringing up the interface manually? If you need to use the eepro100 module, then you'll need to edit /etc/modprobe.d/blacklist change eepro100 to e100.
Good luck. ;-)
I'm using the default huge.smp kernel, you know, cause it's the default I assume it's safe.
This seems to be the standard thought process for everyone new to Slackware, despite it being mentioned in the official documentation included with your install CD/DVD which you are EXPECTED to read BEFORE installing (and it's been the same since Slackware 12.0, but if you're a newbie you wouldn't be expected to know that). All of the text files in the root directory of CD1 (or the DVD) contain useful information that you should read, especially CHANGES_AND_HINTS.TXT and UPGRADE.TXT (even if you are not upgrading).
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.
If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.
If you decide to use one of the huge kernels anyway, you will encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels.
It almost certainly isn't the cause of this specific problem (since both e100 and eepro100 are compiled as modules in both the huge-smp and generic-smp kernels). As others said, the fact that `lsmod` outputs the e100 module means that it is loaded, and the fact that `ifconfig -a` outputs an eth0 stanza means that your specific card is recognized. It is all just a matter of configuration now, and as others have stated, `netconfig` should do the trick. However, I would still recommend switching to the generic-smp kernel (which requires an initial ramdisk [initrd] -- for instructions on how to create one, read /boot/README.initrd. Alien Bob's script can usually output a correct mkinitrd command as well, available here: http://www.slackware.com/~alien/tool...d_generator.sh)
As for your KDM troubles, did disabling DRI "fix" the issue? If not (or if you want to try to get DRI working), you should run `xorgconfig` and select one of the few Savage drivers listed there. There are a few Savage drivers you can try -- one listed near the beginning of the list (if I recall correctly) and some Savage S3 drivers way down the list (in the "S" section, oddly enough). Using a different driver may fix the problem. I've heard the DRI and Savage cards don't mix very well, so I can't predict how successful an attempt at enabling DRI would be.
I've been using slackware as a desktop for about 4 years now (mandrake for 2 years before that), this is my first time getting into linux on a laptop. The huge kernels have never been an issue before; I figure if it works, why mess with things. What is the advantage to using the generic-smp?
My netconfing couldn't be simpler. Just put in the same thing I did post-installation, host/domain name, everything else is automatic from DHCP. I've read that the ethernet problem may be because of using acpi and that using apm would fix that. I sure don't know how to switch the two up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.