Keyboard and mouse not detected after starting X
My keyboard and mouse will no longer work after starting X. My system isn't freezing as conky still functions. My wired and wireless internet don't work anymore either.
Everything broke after I followed this tutorial to update Slackware packages: http://webgnuru.com/linux/slackpkg_howto.php I upgraded to Slackware 14.0 RC3 |
Are you sure you selected a mirror in /etc/slackpkg/mirrors for the correct version of Slackware that you're running?
Sorry if you did, I just wanted to get that out of the way first. Oh, and another possibility is an issue with the way you merged the config files over, especially if you're new to Slackware and/or slackpkg. |
Quote:
I probably overwrote the config files but I can't seem to find the original files. All I see are a bunch of errors and not founds at start up. |
You have a upgraded Slackware to 14.0 RC3? You should be to remove packages hal-0.5.14-i486-3 and hal-info-20091130-noarch-1 and upgrade udev, according to the ChangeLog.txt. Also you should install package kmod-9-i486-3.
|
Quote:
My mouse and keyboard still aren't functioning. My mouse powers up but my keyboard turns off after starting X. My system time also seems to be different from the hardware time. A lot of the errors say GLIBC_2.1.4 not found. |
Quote:
Code:
# slackpkg search firefox Quote:
My system time also seems to be different from the hardware time. A lot of the errors say GLIBC_2.1.4 not found.[/QUOTE] Packages match in glib* are upgraded? Code:
# slackpkg search glibc |
My wireless and wired internet doesn't work after updating so I won't be able to download any updates. My FireFox was upgraded from 4 to 14. I currently have glibc-2.1.5-x86_64-5 installed.
When I typed "iwconfig" or "ifconfig" all I see is "lo". Any way to "roll-back" or "downgrade"? 14 RC3 is unstable. |
You have overwritten some of your config files with new ones, you don't need to downgrade, just start out with the
"netconfig" this will get you back on the web. Then just work through the problems one by one, there are plenty of great help on this forum. |
Quote:
Anyways, I downloaded all the Slackware 13.37 files including patches from a Slackware mirror and placed it on a USB. |
Quote:
|
"lo" is the loopback device.
What is the output of Code:
lspci -k |
I had this problem on upgrading to current (which shows as 14 in /etc/slackware-version some time back.
I can't remember how I fixed it, but I think it was either a) Booting into Salix and mounting / and installing missing packages from slackware-current repo b) running Wicd-cli or plug in ethernet and run slackpkg upgrade, before startx but remember this time to do the install-new this time. Anyway it was solveable without a complete re-install. Good luck |
You need /run directory. Just make the directory and then reboot.
|
Quote:
slackpkg file-search run shows a long list of matches. Not surprising that udev doesn't work normally. I think it is necessary to add information about this issue in CHANGES_AND_HINTS.TXT. |
How would I go about posting logs on here if I have no internet connection on Slackware?
|
There is always Salix booted off SDCard / Keystick, has saved my bacon a couple of times.
You can mount / and take the logs and post them with that. Salix always picked up my wireless card, or when all else fails plug a network cable in. |
Quote:
Xorg.0.log: http://pastebin.com/9P4F1Dw0 syslog: http://pastebin.com/Si5GrPjP messages: http://pastebin.com/MA9G43BL |
It's easy to see from X.0.log that you still have xorg-server 1.9.5, shipped with Slackware 13.37.
So your system was not properly upgraded, else you would have xorg-server 1.12.3 instead. Upgrade this package with upgradepkg and see what you come up with. Possibly there are others upgrade problems, but better try one thing at a time. To check that you have the good version of a package there are many ways. For instance you could "grep" the Changelog for Slackware current or the file PACKAGES.TXT at the root of the Slackware current tree against the package name, or use the "find" command in the /slackware directory of the Slackware current tree. And of course you can check the installed package's version in /var/log/packages. |
From your logs I can see that the kernel modules are not being loaded for some reason, which is why you have no wired or wireless. You are using the 13.37 kernel so you most likely are in the middle of two different Slackware versions.
Didier brings up some valid points, if you can provide a list of the files in /var/log/packages we could probably see what state your system is in and provide you with better advice. |
If you you use the proprietary Linux graphics driver, you need upgrade it. Older video drivers like 173.14.31 (NVIDIA) is incompatible with a new Xorg.
ADD: In any case, you need to update your graphics card driver, because when you install a new kernel old driver will be placed in /lib/modules/{uname -r}, for the old stock smp-kernel it is, for examle, /lib/modules/2.6.37.6-smp, and for the new smp-kernel it is /lib/modules/3.2.28-smp. Quote:
boot Slackware-13.37 Code:
mkdir /mnt/slack Code:
USE_DHCP[0]="yes" |
Quote:
|
Quote:
Code:
ls /var/log/packages > installed_packages.txt |
Here's the list of packages in /var/log/packages:
http://pastebin.com/tAtWCpt9 |
Hi,
Had the same problems as you mention : no mouse/kb when X started and no ethernet. It turned out that udev wasn't installed properly and failed to start at bootup, which is why I only had a limited set of devices in /dev and also why the autoprobing of hardware failed. I simply did a reinstall of udev and after that everything worked fine. To get into your system : - boot into runlevel 3 to avoid X freezing up - manually load the driver for the ethernet card : modprobe tg3, modprobe e1000e or whatever - initialize the netcard manually : /etc/rc.d/rc.inet1 eth0_start - check if you have a network (ifconfig eth0, route) - slackpkg reinstall udev |
1 Attachment(s)
I compared your /var/log/packages list to mine on Slackare 14 RC4.
It appears that you have no less than 655 packages either missing, or that should be removed, or that should be upgraded, see the appended file where you will see your packages on the left side, mine on the right side. I had some formatting problems but "|" means "versions differ", "<" means "missing" and ">" means "should be removed". I had to strip -$ARCH from the filenames, as I do not have the same as yours. So, I suggest you just make a clean install of Slackware -current in its current state, or wait for Slackware 14 to be released and install it. |
1 Attachment(s)
I've compared your packages with both the 13.37 branch and the current branch and it seems your system is much closer to 13.37 than to 14.0RC3, the only packages from 13.37 which aren't there are the hal packages (which I believe you recently removed) and the kdei packages (which I believe you didn't install in the first place). You do have a lot of 14.0 packages installed in addition to that.
The most noticeable thing I see is that you have both module-init-tools and kmod packages installed which could be the reason why the kernel modules are not loading properly. Are you planning on getting your system working without doing a full reinstall? If that is the case I would suggest, since all your critical files are from 13.37, that you: - uninstall kmod and module-init-tools - reinstall module-init-tools, hal and hal-info. If that gets your internet connection working, great. If the rest of your system works, even better. It will be much easier to choose how to proceed with your system afterwards. If not, perhaps some of the other 14.0RC packages are interfering (I've attached the list of packages present in the installation which are not present in 13.37 for anyone who has better insight on how they affect the system). |
Quote:
|
All times are GMT -5. The time now is 03:40 PM. |