LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-14-2013, 12:06 AM   #1
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Rep: Reputation: Disabled
Unhappy Can't get my slackware system boot


Hi friends my pc's inbuilt sound card failed so I decided to go for a pci sound card so I bought a creative ca0103 4ch pci card an installed it on my slot its said that its compatible with linux.usually I use a triple boot or a dual boot system so when I tried to use is windows xp or 7 bot worked. But in my linux systems i was not able to complete the boot sequence.I tried while booting the messages stay at

/sbin/udevd trigger event -- action=add
and some of initializing devices

snd_emu10k1x 0000:01:03.0: PCI INT A ->GSI 20(level,low) -> IRQ 20

Model 1001 Rev 00000000 Serial 10011102



or some time s my monitor switches off but cpufan keeps running.I have tried removing it from blacklist in /etc/modprobe.d as suggested on net but invain.Please guys its urgent I really need it the problem is from 2 months "HELP ME".

Last edited by Greence; 07-14-2013 at 12:53 AM.
 
Old 07-14-2013, 05:50 PM   #2
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware
Posts: 6,371
Blog Entries: 6

Rep: Reputation: Disabled
Hi:

Sorry you are having trouble with your Slackware distro.

I can't help you but I did look up the error messages.

Until another member with more experience with SLACKWARE in this area can help you, these links may provide you
with some information to think on.

You could try booting with a Live Linux CD and see if you can access your system that way or at least look at the HDD-
You could also try holding down Ctrl + Alt + F2 and see if that will let you log in--

To be certain of which sound card you have if and when you can boot your system can run:
Code:
lspci | grep -i audio
Sorry I don't know more-

http://www.linuxquestions.org/questi...dm-4175455842/
http://connie.slackware.com/~rworkma....d/rc.udev.new
http://drivers.softpedia.com/get/SOU...or-Linux.shtml
 
1 members found this post helpful.
Old 07-15-2013, 08:21 AM   #3
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Original Poster
Rep: Reputation: Disabled
Hi:
Thank you I will try as you suggested.
Actually both neither my ubuntu nor slackware were able to boot, in ubuntu it was jast a pink screen so was not able to know any messages,I found these in slackware.When I did
lspci

it showed as "media controller creative SB live emu10k1X" but when I tried "modinfo soundcore" I got as no sound cards detected.Another thing I noticed was that some times when I tried to boot , Linux boots but windows does not boot and many a times its windows that is able to boot but not linux.

Last edited by Greence; 07-15-2013 at 08:29 AM.
 
Old 07-15-2013, 10:09 AM   #4
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,429

Rep: Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348Reputation: 1348
Quote:
Another thing I noticed was that some times when I tried to boot , Linux boots but windows does not boot and many a times its windows that is able to boot but not linux.
The boot message
Quote:
/sbin/udevd trigger event -- action=add
arises from /etc/rc.d/rc.udev which is called from /etc/rc.d/rc.S at boot. This occurs before the root file system is mounted.
I suspect that your hard disk is failing.
 
1 members found this post helpful.
Old 07-15-2013, 10:15 AM   #5
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Original Poster
Rep: Reputation: Disabled
Smile

Quote:
Originally Posted by allend View Post
The boot message

arises from /etc/rc.d/rc.udev which is called from /etc/rc.d/rc.S at boot. This occurs before the root file system is mounted.
I suspect that your hard disk is failing.
oh thanks allend for telling me this, I didn't knew it.
 
Old 07-16-2013, 09:54 AM   #6
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Hi Greence,

are you using the generic kernel? did you build an initrd?

Markus
 
Old 07-16-2013, 01:02 PM   #7
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37
Posts: 290

Rep: Reputation: 55
The first thing I suspect is that the built-in sound device is still there.
You did not say how it failed, but I suspect that sound still has the io-ports in use.
I have not had this happen, so it is hard to presuppose how it works out.
On my systems the built-in sound devices shows up as an internal ISA bus device repeated onto the internal PCI bus.

Of course, windows will scan the pci bus differently than Linux and probably give different card addressing.
Linux may be giving it the same io-ports as the existing built-in sound which will not work well.
PCI is supposed to insure that each device gets unique addressing but it is complicated by the existence of legacy devices, and is at the mercy of on card configuration data.
You would have to compare boot logs with and without the new card to tell if the same addresses are being used for both, or if two sound devices are detected.

When a built-in device fails you have to go into bios and totally disable that hardware.
You may have to install a replacement sound card at an alternative bus address (which would require PCI configuration workarounds).

If Linux finds both the old sound and new sound card, it may default to the old sound device.

First disable the old device, and without the new card boot Linux and make sure that no sound cards are detected, and that there are no other errors.
Something else could be failing instead.

It is possible that the new card has a bus issue and is simply bad.
When it does boot, is the system stable, or are strange bus errors being logged?

Monitors will turn off when left alone for too long. There are several timers that will do this, but none of them are called a blacklist, and it has nothing to do with modprobe.
It is normal behavior, just touch ctrl key and it turns monitor back on.
If you want to stop it look under settings for display power saving.

The cpu fan keeps running as long a cpu is hot, and that is as it should be.

Try shorter sentences. Much of the original post is not understood.

Last edited by selfprogrammed; 07-16-2013 at 01:45 PM.
 
1 members found this post helpful.
Old 07-22-2013, 11:08 AM   #8
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by markush View Post
Hi Greence,

are you using the generic kernel? did you build an initrd?

Markus
Hi, I am using a generic kernel
 
Old 07-22-2013, 11:24 AM   #9
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by selfprogrammed View Post
"The first thing I suspect is that the built-in sound device is still there.
You did not say how it failed, but I suspect that sound still has the io-ports in use.
I have not had this happen, so it is hard to presuppose how it works out.
On my systems the built-in sound devices shows up as an internal ISA bus device repeated onto the internal PCI bus......."
Hi,selfprogrammed,sorry for late reply
I will try to improve using shorter sentences.
I don't know how the internal sound card failed,I use my system for recording casettes and convert to mp3's,I think that may have damaged it while handling. I have disabled the internal sound card in bios and when it boots , no errors are found , system is stable except no sound.

Last edited by Greence; 07-22-2013 at 11:26 AM.
 
Old 07-22-2013, 11:34 AM   #10
Greence
LQ Newbie
 
Registered: Jan 2013
Location: Karnataka,India
Distribution: Ubuntu,slackware
Posts: 13

Original Poster
Rep: Reputation: Disabled
and here is a snapshot where my system stops when bootingClick image for larger version

Name:	DD-MM-YY1062.jpg
Views:	24
Size:	259.9 KB
ID:	13035 and I tried

Code:
lspci | grep -i audio
the response was

Code:
01:03.0 Multimedia audio controller: CreativeLabs[SB live! value] EMU10k1X
 
Old 07-23-2013, 06:18 PM   #11
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37
Posts: 290

Rep: Reputation: 55
As soon as the SB card is touched the system hangs.
This is often the hardware, the card ties up the bus by failing to complete a bus transaction.

If windows is also failing with this card present, then I suspect you have gotten a bad card.
Some cards are sold because they were giving the previous owners problems too.

There have been updates and fixes to the emu10k driver over the recent years, but also some evidence that it generally works.
I have searched for "Linux hang emu10k" and there are many old reports, but nothing new that I can tell you about.

Your built-in sound might not of failed. There is more than one way to mess up settings so that you do not get sound.
But, if it does not work for Linux, nor Windows, then maybe it did fail.
 
Old 07-24-2013, 12:42 PM   #12
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware
Posts: 6,371
Blog Entries: 6

Rep: Reputation: Disabled
Greence:

A new sound card should be fairly easy to install on the motherboard if this computer is a desktop.
Installing a new sound card for a laptop could get intresting to say the least:-
A few weeks back I dis-esembled a laptop to replace the fan and clean the heat sink; it took me a few days to complete the task.

http://www.amazon.com/ASUS-XONAR-Hea...4683885&sr=1-1
http://www.amazon.com/Creative-Sound...ard+for+laptop

selfprogrammed:

Is there a way to test this sound card?
Or will that be hard to establish as there are 2 cards involed here?
I think that by default Ubuntu uses Alsa. The Alsa mixer can be adjusted using the terminal;not sure if that helps-

Last edited by Ztcoracat; 07-24-2013 at 12:54 PM.
 
Old 07-25-2013, 10:44 PM   #13
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37
Posts: 290

Rep: Reputation: 55
I have fought with sound cards for so many years and do not have any fixed system for testing them. Almost all the problems are in the operating system interface and getting the driver to work.

I once thought I had destroyed the built-in sound on my motherboard. After fighting with it for a few days it was working again. Never did figure out what had shut it down.

* Sometimes the cord gets yanked and the speaker plug comes out one notch. It will not work that way.
* It will not work with the speakers plugged into anything but the speaker jack.
* The speakers can fail, or get unplugged, or have a button on them get pushed.
Check that your speakers are actually working using a AAA battery, or some other stereo source.
* Check the built-in sound device microphone input. Does that work.
You might blow out an output amp, but that would not affect the microphone input.
* If all access to the built-in device has failed, then suspect a driver problem.
The internal built-in device bus is not fragile, nor is it exposed to user error.
Driver problems can be fixed.


The new sound card is PCI.
That can be tested on a windows system.
Try two different slots, you may have plugged it into a bad slot, or an incompatible PCI slot. There are at least 4 kinds of PCI slots (PCI 5V, PCI 3.3V, PCI-express, PCI-mini).

With a card that hangs at first touch, it often is the wrong driver, or card mis-configuration. There may be nothing to configure on a PCI card, but read the manual.

If it hangs with both windows, and linux, then probably a bad input on the bus connector (bad card). This is not repairable.
These can be blown by cards fighting on the bus.
It is hard to get PCI cards to do that, but it is possible (no, I don't have an example).
It can also be damaged by handling the card while walking around (static), or by shipping it packed with styrene pellets (static).
 
1 members found this post helpful.
Old 07-25-2013, 11:19 PM   #14
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware
Posts: 6,371
Blog Entries: 6

Rep: Reputation: Disabled
Quote:
If it hangs with both windows, and linux, then probably a bad input on the bus connector (bad card). This is not repairable.
Didn't know that; selfprogrammed; Thank You!

Quote:
I once thought I had destroyed the built-in sound on my motherboard. After fighting with it for a few days it was working again. Never did figure out what had shut it down.
Maybe a switch enabled or disabled? (guessing)

Last edited by Ztcoracat; 07-25-2013 at 11:24 PM.
 
Old 07-26-2013, 04:56 AM   #15
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,599

Rep: Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241Reputation: 1241
One thing you might double check.

I have had cards that "fit" into a PCI slot, but be a bit improperly centered causing a pin to not make a good connection. If the card is tight with respect to the mounting frame, you might try bending the leading edge of the mounting frame a little to make it "less tight", which might allow better centering during insertion.
 
  


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] System boot without USB or Slackware DVD Dman58 Linux - Desktop 4 04-12-2012 03:09 AM
brand new to Slackware....... and already lost...... cannot boot system Perquisitor Slackware 19 01-31-2008 07:22 PM
Help! I am unable to boot into my Slackware 10.1 system adityavpratap Slackware 15 04-24-2006 06:39 AM
system alarm on boot in slackware 10.0 but not win2000(dual boot) Arch Stanton Slackware 3 01-24-2005 11:33 AM


All times are GMT -5. The time now is 06:24 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration