LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices



Reply
 
Search this Thread
Old 03-08-2011, 08:19 PM   #1
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Rep: Reputation: 0
Issues installing/upgrading to Slackware Current


So for about a week now, any time I update to Slackware-Current(x86 or x64 or multi-lib) it appears to run just fine. However, once it is powered off, it will not boot again. It doesn't give an error of any kind, or at least it doesn't stay up on the screen long enough to let me see it. It boots as normal for a few seconds, and then stops sending a signal to the monitor. Additionally, it never gets to a point where it can take input from a keyboard(double checked by doing a few commands that cause a system beep when they run).

I thought at first it was just a bad upgrade due to me getting lazy with my update script(can attach if needed, but it's been working fine for the last year), but then I tried installing with a newly created Slackware64-current disc(mirrored with alien bob's script on 3/1/11) and got the same issue on a fresh install(rules out a bad upgrade). So I thought it was just an x64 issue until it happened to my sister's boyfriend(fresh install, x86, mirrored 3/2/11, he's been using Slackware for at least the 4 years I've known him). His machine is an AMD proc + ATI card, mine is AMD + NVidia.

So I know it's not just me(as it happens to someone else I know), not an issue with x64(as it happens with x86 as well), not my update script(happens on fresh installs), and beyond that I'm stumped. No one else seems to have reported this from what I've found via Google, and I didn't see any threads on it here either(though I'm new to this particular site, and may have overlooked it somewhere). Anyone have any thoughts? I've been beating my head on the desk trying to figure it out for about a week now.

(edit)It should be noted that I first had the issue(when I thought it was a bad upgrade script) about two weeks ago, and have installed about four times since then each time mirroring what was current. Sister's boyfriend has only tried the one, and decided to tinker in other distros for a week or two while waiting for a fix.(/edit)

Last edited by rougegoat; 03-08-2011 at 09:47 PM. Reason: marked new paragraph with (edit)(/edit) tags
 
Old 03-08-2011, 11:29 PM   #2
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Hardware specs?

If you are using Intel graphics, turn off DVMT, and try setting the amount of RAM dedicated to the IGP to something like 32MiB.

To rule out hardware problems - does another Distro work? How about Slackware 13.1 stable?
 
Old 03-09-2011, 02:09 AM   #3
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by disturbed1 View Post
Hardware specs?

If you are using Intel graphics, turn off DVMT, and try setting the amount of RAM dedicated to the IGP to something like 32MiB.

To rule out hardware problems - does another Distro work? How about Slackware 13.1 stable?
Hardware between the two machines I know to be affected aren't very similar, so I don't think it's that. I don't know my sister's boyfriend's specs, but my computer(x64) has the following:

Video Card: NVidia GeForce 9500 GT
Onboard(disabled in bios): NVidia GeForce 8200
Sound Card: None/integrated
CPU: AMD Athlon 64 X2 Dual Core 6000+
MoBo: MSI K9N2G Neo
RAM: Corsair, 2GBx2

As for other distros, I've used plenty of different ones in the past. Slackware 13.1(same disc I installed from at it's release) works fine(stated above I try to update to it and it's only after the update or new install that the issue pops up). As for recent attempts at other distros, I had mixed issues. I tried OpenSuSE 11.2, and it installed fine and basic setup went fine, but GRUB had 5 entries(instead of 3) that didn't link to any OS successfully. I haven't tried another one, but the next attempt to install Slackware and update to current put Lilo back on and that's all working correctly.

(generally a dual boot system between Windows 7 and Slackware64/multilib)
 
Old 03-09-2011, 02:15 AM   #4
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
I wonder -- since you have 2 video cards, if somehow it's attempting to use the other. Or, it's the new Nouveau driver that is included by default now.
Code:
x/xf86-video-nouveau-8bb82312-x86_64-1.txz:  Upgraded.
  This is the actual nouveau driver, added to the main tree for the first time.
  If you do not want to use this, use upgradepkg to switch to the blacklist
  package in /extra.
At boot, you can try passing the following to the kernel
Code:
nouveau.modeset=0


The PC does POST, you select a kernel option in Lilo --- then blank?
 
Old 03-09-2011, 01:47 PM   #5
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by disturbed1 View Post
I wonder -- since you have 2 video cards, if somehow it's attempting to use the other. Or, it's the new Nouveau driver that is included by default now.
Code:
x/xf86-video-nouveau-8bb82312-x86_64-1.txz:  Upgraded.
  This is the actual nouveau driver, added to the main tree for the first time.
  If you do not want to use this, use upgradepkg to switch to the blacklist
  package in /extra.
onboard is disabled in Bios(Slackware doesn't generally detect it), and the issue affects another computer not using an NVidia card(sister's boyfriend uses an ATI card). I generally(for the problem installs at least) wait to install the graphic driver(fresh from NVidia's site) until I reboot. Oddly, I seem to remember it having issues with installing due to some library(can't remember off the top of my head) conflict if I tried installing it before rebooting on an upgraded install. Never got a chance to try installing it before reboot on a fresh install though. I'll try it when I get off work, though it'll take a while to remirror and be able to do the whole upgrade to current.

Quote:

The PC does POST, you select a kernel option in Lilo --- then blank?
Pretty much. I get about five seconds of normal boot, then the screen turns blank, I get the usual "No signal" message on the monitor, and it goes to standby. If I wait a good long while(between a minute and an hour from past attempts) to see if it's still booting but not displaying, I find that I cannot login and run commands blind(starting in init 3, so logging in without seeing it is easy enough to do). No beeps or any sort of acknowledgment. Can't remember if I've checked mouse/keyboard lights, though I can't remember them actually turning on.

(edit)Got busy between work and class and important side projects, had to put doing the above off until the weekend. Hopefully 13.37RC1 fixes my issue.(/edit)

Last edited by rougegoat; 03-10-2011 at 11:52 PM.
 
Old 03-12-2011, 09:12 PM   #6
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
downloaded current(x64), same issue. Sister's boyfriend reports no issues with current(x86).

Additionally, I tried installing OpenSuse 11.4(x64) and found it had the exact same issue. Their forums suggested it has to do with udev, and starting Suse with "nomodeset" works. Doing this, I get no network connectivity and sometimes no graphical interfaces.

So problem still stands.
 
Old 03-14-2011, 04:21 AM   #7
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,222

Rep: Reputation: 578Reputation: 578Reputation: 578Reputation: 578Reputation: 578Reputation: 578
If addon graphics card is not working, wouldn't it be easier to get OS installed, using onboard graphics that way you have a stable system then adding the graphics card and getting drivers
 
Old 03-14-2011, 05:06 PM   #8
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by EDDY1 View Post
If addon graphics card is not working, wouldn't it be easier to get OS installed, using onboard graphics that way you have a stable system then adding the graphics card and getting drivers
I'll attempt that tonight. I still have the previous RC1 install(from my last post) on there, so I'll go into my BIOS, re-enable onboard video(also NVidia, I believe GeForce 8200), and see if it boots.
 
Old 03-14-2011, 07:54 PM   #9
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
installed with confirmed onboard video both enabled and disabled(separate installs), issue persists. also tried changing enabled/disabled status after initial install but before successful boot. No dice.

RC1 from the one posted 3/8/11.
 
Old 03-20-2011, 06:47 PM   #10
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
Installed 13.37 RC2 today, default settings(+kdei, cups, samba), same issue still exists.

Does anyone have any suggestions of anything to try? It's been over a month since this started happening and I just assumed that someone out there would have sent a patch in over it. Apparently that assumption was a bad one to make.

(edit) further investigation shows this is a slight improvement. Keyboard now responds. Just blind. Other threads suggested running lilo or lilo.conf and rebooting. did that, no change. (/edit)

(edit2) decided to retry some old advise that did not work the first time and booted with nouveau.modeset=0. got graphical no issues. went in and installed the alternate package found in /extra and from what I understand that should solve my issue.(/edit2)

Last edited by rougegoat; 03-20-2011 at 08:02 PM.
 
Old 03-20-2011, 10:17 PM   #11
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Figured it was nouveau related to begin with, as posted a couple of weeks ago.

Last edited by disturbed1; 03-20-2011 at 10:18 PM.
 
Old 03-21-2011, 01:40 AM   #12
rougegoat
LQ Newbie
 
Registered: Mar 2011
Location: with Carmen Sandiego
Distribution: Slackware64
Posts: 8

Original Poster
Rep: Reputation: 0
True, but at the time that you had posted it there, it did not help. It had no effect up until RC2 for inexplicable reasons.
 
  


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
[SOLVED] Upgrading to current; potential issues? 2handband Slackware 14 11-02-2010 08:44 AM
Upgrading from Slackware 13.1 to Current njb Slackware 6 08-08-2010 01:42 PM
[SOLVED] Bluetooth mouse issues after upgrading to BlueZ 4 in -current cgorac Slackware 2 05-08-2010 01:56 AM
Issues with Hylafax 10.1 after upgrading Avantfax to current. Carlo1973 Suse/Novell 1 04-16-2009 03:58 PM


All times are GMT -5. The time now is 08:42 PM.

Main Menu
Advertisement
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