LinuxQuestions.org
Register a domain and help support LQ
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-06-2012, 11:18 PM   #31
slacktroll
Member
 
Registered: May 2011
Distribution: Slackware 14.0 on Thinkpad X60
Posts: 56

Rep: Reputation: 3

Quote:
Originally Posted by slack_newbie View Post
should it matter if i boot from lilo or the install disc?

btw, thanks for all the help
No problems. If anyone else reads this, and want a quick fix for 13.37 you can follow the following procedure:

(put in installation cd, don't run setup)
mount /dev/sda2 /hello # note use whatever slackware is installed,

rm -f /hello/lib/modules/2.6.37.6/kernel/drivers/gpu/drm/nouveau/nouveau.ko
rm -f /hello/lib/modules/2.6.37.6-smp/kernel/drivers/gpu/drm/nouveau/nouveau.ko

depending if you use smp kernel or not.

Last edited by slacktroll; 09-06-2012 at 11:20 PM.
 
Old 09-06-2012, 11:20 PM   #32
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
After you remove the driver you'll have to boot from LILO to see if it works, but in order to get the machine booted and remove the driver or blacklist it, you'll have to boot with the install disk since you are unable to boot from the hard drive.
 
Old 09-06-2012, 11:54 PM   #33
slack_newbie
LQ Newbie
 
Registered: Sep 2012
Posts: 11

Original Poster
Rep: Reputation: Disabled
Long story short, I attempted to reinstall because I read somewhere that changing from KDE to xfce may help. Except this time, when trying to configure LILO I got the message:
"Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation
Fatal: open /dev/sdb1: No such device or address"

I can look up how to install it manually, but I figured this error message may offer new information/tell us something we already know.
 
Old 09-07-2012, 01:02 AM   #34
slack_newbie
LQ Newbie
 
Registered: Sep 2012
Posts: 11

Original Poster
Rep: Reputation: Disabled
This is quite exciting. After following slacktroll's instructions, I was able to log into root. What reading would you recommend I do so I can figure out how to get my GUI working.
 
Old 09-07-2012, 01:24 AM   #35
J1NKL3
Member
 
Registered: Mar 2012
Distribution: Slackware64-current
Posts: 77

Rep: Reputation: Disabled
Quote:
Originally Posted by slack_newbie View Post
Long story short, I attempted to reinstall because I read somewhere that changing from KDE to xfce may help. Except this time, when trying to configure LILO I got the message:
"Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation
Fatal: open /dev/sdb1: No such device or address"

I can look up how to install it manually, but I figured this error message may offer new information/tell us something we already know.
I got that a couple of times during various installs... just boot back into the rescue and rerun lilo
 
Old 09-07-2012, 05:46 AM   #36
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by slacktroll View Post
No problems. If anyone else reads this, and want a quick fix for 13.37 you can follow the following procedure:

(put in installation cd, don't run setup)
mount /dev/sda2 /hello # note use whatever slackware is installed,

rm -f /hello/lib/modules/2.6.37.6/kernel/drivers/gpu/drm/nouveau/nouveau.ko
rm -f /hello/lib/modules/2.6.37.6-smp/kernel/drivers/gpu/drm/nouveau/nouveau.ko

depending if you use smp kernel or not.
Nothing worong with the advice here, except ithe kernel version is constantly changing, and removing driver files without removing the package can affect troubleshooting down the road. Chrooting and just uninstalling the driver with removepkg is just a cleaner way to accomplish the same goal without potentially muddying the waters down the road. It would be nice if the nouveau driver would just go back to /extra.
 
Old 09-07-2012, 06:33 AM   #37
slacktroll
Member
 
Registered: May 2011
Distribution: Slackware 14.0 on Thinkpad X60
Posts: 56

Rep: Reputation: 3
Quote:
Originally Posted by slack_newbie View Post
This is quite exciting. After following slacktroll's instructions, I was able to log into root. What reading would you recommend I do so I can figure out how to get my GUI working.
use the command xwconfig to change Windowmanager.
use startx to start GUI.

:-)
 
Old 09-07-2012, 07:03 AM   #38
slacktroll
Member
 
Registered: May 2011
Distribution: Slackware 14.0 on Thinkpad X60
Posts: 56

Rep: Reputation: 3
Quote:
Originally Posted by damgar View Post
Nothing worong with the advice here, except ithe kernel version is constantly changing, and removing driver files without removing the package can affect troubleshooting down the road. Chrooting and just uninstalling the driver with removepkg is just a cleaner way to accomplish the same goal without potentially muddying the waters down the road. It would be nice if the nouveau driver would just go back to /extra.
well /var/log/packages/xf86-video-nouveau-* does'nt include the nouveau.ko driver. And AFAIK xorg in 13.37 does not load that driver while starting X at ALL if the kernel module is not loaded / builtin

Read the entire thread, see his info,. he mentions somewhere that machine hangs when initalising DRM. DRM is NOT the xf86-video-nouveau driver at all. The kernel driven graphic driver is the problem, not the xorg driver.

TS: you could have installed this package:
ftp://ftp.slackware.com/pub/slackwar...t-noarch-1.txt

basicly does the same thing as you did manual to blacklist it in i /etc/modprobe.d/blacklist.conf :P

but removing the module is maybe better practice :P your choice!

Last edited by slacktroll; 09-07-2012 at 07:09 AM.
 
Old 09-11-2012, 10:41 AM   #39
m.knives
LQ Newbie
 
Registered: Aug 2011
Posts: 20

Rep: Reputation: Disabled
Quote:
Originally Posted by slacktroll View Post
use the command xwconfig to change Windowmanager
Of course slacktroll meant to say "xwmconfig"

Slightly off-topic:
Quote:
Originally Posted by slack_newbie View Post
Live USB is a no go, because as far as I can tell my laptop doesn't allow you to boot to removable devices.
My old laptop also can't boot from pendrives, but I've found a great solution for this. Download and burn Plop Boot Manager to a CD and this might be the last time you'll have to waste money on CDs/DVDs.
 
Old 09-11-2012, 11:32 AM   #40
Alvin Chey
LQ Newbie
 
Registered: Jan 2006
Location: Singapore
Distribution: Slackware64 14.0 Stable (64-bit)
Posts: 9

Rep: Reputation: 8
Was the CPU temperature too high?

Quote:
Originally Posted by slack_newbie View Post
I was able to install Slackware successfully (after multiple attempts--it would often stop at random times during the installation with different error messages every time). However, it can't boot. I tried it with LILO installed to the MBR, to the main partition, and even just booting from the disk. Same error every time.
I remember re-installing Slackware on old hardware - the installation stopped at random times. I could never complete installing all packages at one go.

I later found out that it was due to overheating of CPU (due to accumulated dust between CPU fan and heatsink). As all the packages are installed, the CPU temperature was too high and it caused the installation process to stop abruptly.

Opening another terminal to query the CPU temperature confirmed for me that the CPU is working near the upper limit of temperature even before the setup process was started.

I hope you will check the CPU temp as one of the possible causes of failed installation.
 
Old 09-11-2012, 12:10 PM   #41
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
I have a similar laptop, and it is close to death.

The first thing I would do is boot the UBCD and run memtest86+, HDD diagnostics (SMART), Video Memory Stress Test.

The DVD Burner for it failed quickly, so don't trust it to burn good disks, make sure to check the burned disk using:

Code:
cmp slackware.iso /dev/sr0
or whatever other way you have to check that the disk is burned properly.
 
  


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
Best rolling distros geared towards noobs-novice? DTW Linux - General 17 03-24-2011 03:01 AM
Hardware compatible with one or more linux distros. Will it work on all other distros necromancer44 Linux - Hardware 2 06-07-2010 06:28 PM
No distros seem to work on my computer..please help. gejr Linux - Distributions 9 03-21-2007 09:38 AM
Two Linux distros on the same computer Gins Linux - General 3 11-02-2005 04:39 PM
An HP computer won't boot most linux distros dracolich Linux - General 3 10-23-2005 03:40 PM


All times are GMT -5. The time now is 09:33 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