LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 04-28-2007, 08:27 AM   #1
rangalo
Member
 
Registered: Jan 2005
Posts: 189

Rep: Reputation: 30
starting of x fails because of alsactl restore


Hi all,

I just upgraded gcc and installed expat using slackpkg. Now, when I reboot, i cannot start x-windows. The error I get says that could not load the snd_seq_oss module.

When I run alsaconf from the command line and again try to start x with startx it starts without any problem.

What should I do to get the x back ?

thanks and regards,
Hardik
 
Old 04-28-2007, 08:43 AM   #2
rob.rice
Member
 
Registered: Apr 2004
Distribution: slack what ever
Posts: 784

Rep: Reputation: 99
from the command line or an xterm run alsamixer get the sound working then rum "alsactl save"
now edit /etc/rc.d/rc.local put the command "alsactl restore" somewhere in there
 
Old 04-28-2007, 09:31 AM   #3
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
I find it *very* hard to believe that X would refuse to start due to alsa, but since it seems to be "solved," I won't even go there.

I am concerned about your upgrade to gcc and expat. What version of Slackware are you running? I certainly hope that you did not upgrade to the gcc and expat packages that are part of Slackware -current while you're running a Slackware 11.0 system. If so, be sure to mention this in your future problem reports (or upgrade the entire system to -current), because you will have some very strange problems lying ahead, and it's not fair for people to spend time trying to debug them due to your carelessness and failure to follow instructions.

Of course, if I misinterpreted what you did, ignore this message. :-)
 
Old 04-29-2007, 06:10 AM   #4
rangalo
Member
 
Registered: Jan 2005
Posts: 189

Original Poster
Rep: Reputation: 30
Hi,

@rob.rice

My slackware system is at work, so I will only be able to try this on monday


@rworkman
I was already running slackware-current. Did not upgrade the system though for a long time. Now, I needed fluxbox (the latest package) installed it using slackpkg and it failed due to libexpat, so I installed expat package and also gcc. I don't know if this is carelessness or stupidity or just a normal upgrade procedure.

Why should I upgrade everything when I only need one or two packages upgraded ? I think in this case slackpkg is to blame for not fetching the required dependencies. This would have never happened on my debian system at home.

I don't know howmany things are now broken on my system, but anyway thanks for your help.


regards,
Hardik
 
Old 04-29-2007, 06:37 AM   #5
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 50
Quote:
This would have never happened on my debian system at home.
But are you running the development branch of debian? because that's what you are doing if you are running current in Slackware.

There was current, and then there is current since 17th March 2007. A prerequisite to using current branch is to read the changelog!

tobyl
 
Old 04-29-2007, 06:42 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,194

Rep: Reputation: Disabled
Quote:
Originally Posted by rangalo
I think in this case slackpkg is to blame for not fetching the required dependencies. This would have never happened on my debian system at home.
It is unfair to blame slackpkg. Slackpkg does not try to resolve and handle dependencies. You will have to realize that Slackware packages do not contain dependency information. Some 3rd party package managers try to add dependency checking but since they have to try and extract this information from the package content themselves the process is not reliable.
Running slackware-current would imply that you know what you're doing since -current is a development snapshot and not a stable release.

Slackware basically requires you to do your own homework.
Maybe it is better to stick with Debian if you require a distro with package dependency checking.

Eric
 
Old 04-29-2007, 12:12 PM   #7
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Quote:
Originally Posted by rangalo
@rworkman
I was already running slackware-current. Did not upgrade the system though for a long time. Now, I needed fluxbox (the latest package) installed it using slackpkg and it failed due to libexpat, so I installed expat package and also gcc. I don't know if this is carelessness or stupidity or just a normal upgrade procedure.

Why should I upgrade everything when I only need one or two packages upgraded ? I think in this case slackpkg is to blame for not fetching the required dependencies. This would have never happened on my debian system at home.

I don't know howmany things are now broken on my system, but anyway thanks for your help.
I think you are confused about some terminology. Slackware -current does not refer to the current stable release of Slackware - it refers to the ongoing *development* packages of Slackware (as alienBOB has already advised).

Since Slackware -current (the development that has taken place *after* 11.0 released) has a newer glibc (the C library), gcc, and others (basically the entire toolchain is new), many new/updated packages, and basically all underlying libraries recompiled against the other new/updated packages, you can't just selectively replace a package here and there in 11.0 with something from -current, because the package from -current needs the other packages from -current.

As alienBOB has stated, it is definitely not fair to blame slackpkg for the problems that you are having. You failed to understand the process you were undertaking, and as result, your system has problems.
 
Old 04-29-2007, 01:52 PM   #8
rangalo
Member
 
Registered: Jan 2005
Posts: 189

Original Poster
Rep: Reputation: 30
OK, I was not trying to create any flame-war neither wanted I to bash slack. I use slakware at my work because I like it. The problem though was I just replaced fluxbox and gcc and I broke something which one may thing would not be related e.g. alsactl ...

Now, I will just need to come out of this. Is there anyway to downgrade to slackware-11 ?

@rworkman
Thanks for your input, I was really thinking that slacware-current is the current stable release. I run debian-testing at home, so to get the latest packages in slackware, I was running slackware-current all the time.

regards,
Hardik
 
Old 04-29-2007, 02:00 PM   #9
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Quote:
Originally Posted by rangalo
Now, I will just need to come out of this. Is there anyway to downgrade to slackware-11 ?
Sure. Simply use upgradepkg to replace each package that you had previously replaced with the ones from -current, except go the other direction. Of course, I make no promises that this will work, but it's your best bet aside from a reinstall.
 
Old 04-30-2007, 04:21 AM   #10
rangalo
Member
 
Registered: Jan 2005
Posts: 189

Original Poster
Rep: Reputation: 30
Hi,

Now, I have managed to get into X and also downgrade the packages to slackware-11 by chaning the mirrors in slackpkg.

I am not sure but after these changes, I had to change inittab and set the default runlevel as 4. It was 3 and was not starting X.

I don't remember, if runlevel 3 was for graphical system or 4 ?

Thanks all for your help.


regards,
Hardik
 
  


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
Alsactl restore fails on boot up marsh58 Debian 1 09-12-2006 08:23 AM
Alsactl restore problem on debian ferlopes Linux - Hardware 5 05-07-2005 02:43 PM
alsactl restore not working at boot rgiggs Slackware 4 07-14-2004 03:57 PM
alsactl restore problem Guste Debian 1 02-08-2004 01:53 AM
Doing alsactl to restore mixer setings Maurice Arthur Linux - Software 0 11-11-2003 12:56 AM


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