LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-01-2012, 03:00 PM   #16
hyperhead
Member
 
Registered: Mar 2011
Location: UK
Distribution: Slackware-current
Posts: 95

Rep: Reputation: 7

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.
 
Old 09-01-2012, 05:51 PM   #17
Infinity8
LQ Newbie
 
Registered: Aug 2012
Distribution: Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by hyperhead View Post
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.
Had too many issues with Salix, said my MBR gap was in the negatives and I need at least 64 sectors whatever the hell that means. I just mounted my USB and cp-ed all the logs with interesting names over.

Xorg.0.log: http://pastebin.com/9P4F1Dw0
syslog: http://pastebin.com/Si5GrPjP
messages: http://pastebin.com/MA9G43BL

Last edited by Infinity8; 09-01-2012 at 05:56 PM.
 
Old 09-02-2012, 01:14 AM   #18
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,377

Rep: Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088
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.

Last edited by Didier Spaier; 09-02-2012 at 01:22 AM.
 
Old 09-02-2012, 06:00 AM   #19
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.1
Posts: 135

Rep: Reputation: Disabled
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.
 
Old 09-02-2012, 03:35 PM   #20
yars
Member
 
Registered: Apr 2012
Location: Russia
Distribution: Slackware
Posts: 125

Rep: Reputation: 11
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:
Originally Posted by Infinity8 View Post
How would I go about posting logs on here if I have no internet connection on Slackware?
You can make this:
boot Slackware-13.37
Code:
mkdir /mnt/slack
mount /dev/sda1 /mnt/slack/
mount --bind /proc /mnt/slack/proc
chroot /mnt/slack
If you have a connection to the Internet via Ethernet interface, uncomment in /etc/rc.d/rc.inet1.conf:
Code:
USE_DHCP[0]="yes"
and run /etc/rc.d/rc.inet1 start.

Last edited by yars; 09-02-2012 at 04:14 PM.
 
Old 09-02-2012, 04:38 PM   #21
Infinity8
LQ Newbie
 
Registered: Aug 2012
Distribution: Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by turtleli View Post
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.
How would I go about making the list of packages in /var/log/packages more easily besides writing them all down on a piece of paper?
 
Old 09-02-2012, 04:41 PM   #22
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.1
Posts: 135

Rep: Reputation: Disabled
Quote:
Originally Posted by Infinity8 View Post
How would I go about making the list of packages in /var/log/packages more easily besides writing them all down on a piece of paper?
Use something like:
Code:
ls /var/log/packages > installed_packages.txt
 
Old 09-02-2012, 06:20 PM   #23
Infinity8
LQ Newbie
 
Registered: Aug 2012
Distribution: Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Here's the list of packages in /var/log/packages:
http://pastebin.com/tAtWCpt9
 
Old 09-03-2012, 04:32 AM   #24
lemmens
LQ Newbie
 
Registered: Jan 2005
Location: netherlands
Distribution: slackware64 13.37 + current
Posts: 22

Rep: Reputation: 1
Thumbs up

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
 
Old 09-03-2012, 07:14 AM   #25
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,377

Rep: Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088
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.
Attached Files
File Type: txt diff.txt (29.9 KB, 2 views)
 
Old 09-03-2012, 08:22 AM   #26
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.1
Posts: 135

Rep: Reputation: Disabled
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).
Attached Files
File Type: txt diffinst1337.txt (3.3 KB, 9 views)
 
Old 09-09-2012, 01:04 AM   #27
Infinity8
LQ Newbie
 
Registered: Aug 2012
Distribution: Slackware
Posts: 11

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by turtleli View Post
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).
This worked, thanks a lot!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Keyboard/Mouse not detected Nishant Desai Linux - Newbie 7 08-04-2006 02:11 AM
usb mouse NOT detected, but usb keyboard IS detected mr.anderson Slackware 16 04-26-2006 09:09 PM
starting XFree86 4.5.* with no mouse/keyboard BTNC Linux - General 2 01-28-2006 11:19 PM
Suse 10.0: X setting won't "stick"; mouse & keyboard not properly detected Livino Suse/Novell 1 10-30-2005 03:51 AM
no mouse and keyboard is detected.... aditya_fx Linux - Hardware 11 04-11-2004 02:13 AM


All times are GMT -5. The time now is 09:30 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration