nVidia problems after update (FC3)

Place to discuss Fedora and/or Red Hat
User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Mon Dec 06, 2004 7:52 pm

My bad, the module is "snd_emu10k1". See what that one does. What worries me more than the IRQ is that your lspci output said it's an unknown device. Here's what mine shows (run as root):

Code: Select all

00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
        Subsystem: Compaq Computer Corporation Armada M700/E500
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (500ns min, 6000ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 3000 [size=256]
        Capabilities: [c0] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
I wouldn't worry too much about the IRQ and my soundcard and Wireless network card (ath0) also are both on IRQ 11:

cat /proc/interrupts:

Code: Select all

           CPU0
  0:    6418485          XT-PIC  timer
  1:      13110          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
  9:          2          XT-PIC  acpi
 11:    2083225          XT-PIC  ESS Maestro, uhci_hcd, yenta, yenta, ath0
 12:    1007714          XT-PIC  i8042
 14:      22848          XT-PIC  ide0
NMI:          0
ERR:          0

dishawjp
administrator
administrator
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY
Contact:

Post by dishawjp » Mon Dec 06, 2004 8:30 pm

Voidmain,

Wow, that did something! Now when I do a lsmod | grep snd, I get lots of good stuff!

Code: Select all

[root@vixen etc]# lsmod | grep snd
snd_emu10k1_synth       7873  0
snd_emux_synth         38977  1 snd_emu10k1_synth
snd_seq_virmidi         6593  1 snd_emux_synth
snd_seq_midi_event      8385  1 snd_seq_virmidi
snd_seq_midi_emul       6593  1 snd_emux_synth
snd_seq                56785  4 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul
snd_emu10k1            93769  1 snd_emu10k1_synth
snd_rawmidi            26725  2 snd_seq_virmidi,snd_emu10k1
snd_pcm_oss            47609  0
snd_mixer_oss          17217  1 snd_pcm_oss
snd_pcm                97993  2 snd_emu10k1,snd_pcm_oss
snd_timer              29765  2 snd_seq,snd_pcm
snd_seq_device          8137  5 snd_emu10k1_synth,snd_emux_synth,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec         64401  1 snd_emu10k1
snd_page_alloc          9673  2 snd_emu10k1,snd_pcm
snd_util_mem            4801  2 snd_emux_synth,snd_emu10k1
snd_hwdep               9413  2 snd_emux_synth,snd_emu10k1
snd                    54053  12 snd_emux_synth,snd_seq_virmidi,snd_seq,snd_emu10k1,snd_rawmidi,snd_pcm_oss, snd_mixer_oss,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_hwdep
soundcore               9889  1 snd
[root@vixen etc]#
However system-config-soundcard and kudzu still don't find the card :-(

I'm going to call it a night, but I still have tomorrow evening to see if I can get this going for her. If you have any further thoughts, please pass them along and give this another shot tomorrow. Do you think that it's likely that this soundcard was just plain bad out of the box?

Once again thanks for everything you do to help us!

Jim

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Mon Dec 06, 2004 8:35 pm

I wouldn't worry too much about system-config-soundcard or kudzu (in my uneducated opinion). I believe those may not be detecting it because it doesn't appear to be in your pci database (remember the "unknown device" from lspci?). What I would be more interested in is if gnome-alsamixer will run and if you can make sure all the volumes are up and unmuted and try to play something via mplayer, xmms, etc.

The "unknown device" would also be the reason that the modules aren't getting loaded. When I do a "cat /proc/pci" I see my sound card device is "125d:1978" (vendor id = 125d, device id = 1978):

Code: Select all

  Bus  0, device   8, function  0:
    Class 0401: PCI device 125d:1978 (rev 16).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=2.Max Lat=24.
      I/O at 0x3000 [0x30ff].
In the /usr/share/hwdata/pci.ids file I find the "125d" section (my vendor ID) looks like this:

Code: Select all

125d  ESS Technology
        0000  ES336H Fax Modem (Early Model)
        1948  Solo?
        1968  ES1968 Maestro 2
                1028 0085  ES1968 Maestro-2 PCI
                1033 8051  ES1968 Maestro-2 Audiodrive
        1969  ES1969 Solo-1 Audiodrive
                1014 0166  ES1969 SOLO-1 AudioDrive on IBM Aptiva Mainboard
                125d 8888  Solo-1 Audio Adapter
        1978  ES1978 Maestro 2E
                0e11 b112  Armada M700/E500
                1033 803c  ES1978 Maestro-2E Audiodrive
                1033 8058  ES1978 Maestro-2E Audiodrive
                1092 4000  Monster Sound MX400
                1179 0001  ES1978 Maestro-2E Audiodrive
        1988  ES1988 Allegro-1
                1092 4100  Sonic Impact S100
                125d 1988  ESS Allegro-1 Audiodrive
        1989  ESS Modem
                125d 1989  ESS Modem
        1998  ES1983S Maestro-3i PCI Audio Accelerator
                1028 00b1  Latitude C600
                1028 00e6  ES1983S Maestro-3i (Dell Inspiron 8100)
        1999  ES1983S Maestro-3i PCI Modem Accelerator
        199a  ES1983S Maestro-3i PCI Audio Accelerator
        199b  ES1983S Maestro-3i PCI Modem Accelerator
        2808  ES336H Fax Modem (Later Model)
        2838  ES2838/2839 SuperLink Modem
        2898  ES2898 Modem
                125d 0424  ES56-PI Data Fax Modem
                125d 0425  ES56T-PI Data Fax Modem
                125d 0426  ES56V-PI Data Fax Modem
                125d 0427  VW-PI Data Fax Modem
                125d 0428  ES56ST-PI Data Fax Modem
                125d 0429  ES56SV-PI Data Fax Modem
                147a c001  ES56-PI Data Fax Modem
                14fe 0428  ES56-PI Data Fax Modem
                14fe 0429  ES56-PI Data Fax Modem
and the 1978 lists my soundcard model (device ID). This is where lspci gets it's info. Now, a similar lookup is used to determine what modules to load based on detected hardware (I believe). In my running kernel modules directory (/lib/modules/2.6.9-1.681_FC3) there are several module related files, one of which is named "modules.pcimap" where if you look at it you will see the first line describes the format:

Code: Select all

# pci module         vendor     device     subvendor  subdevice  class      class_mask driver_data
When I do a "grep 125d modules.pcimap | grep 1978" I get this:

Code: Select all

snd-es1968           0x0000125d 0x00001978 0xffffffff 0xffffffff 0x00040100 0x00ffff00 0x0
Notice the first column is the name of the module to load for that device. If manually loading the device works for you then I think these files might be able to be modified to add your device. I'm not sure if the modules file is autogenerated or if it can be edited but I am pretty sure that the hwdata file can me modified. I will have to do a little more research on the proper course of action, but if you feel froggy, make backup copies of these files and edit away. I'm off to Google to see what I can find.

EDIT: This is a VERY interesting thread:
http://www.linuxquestions.org/questions/history/254265
The guy appears to have the same card you have. It would also lead me to believe that the proper driver might actually be "snd_audigyls" rather than the "snd_emu10k1". I don't find the audigyls driver included with my FC3 kernel. It might also suggest that the card may not work unless you have the very latest ALSA drivers. It looks like you might have a piece of hardware hot off the presses that has had some hardware modifications which require new drivers. If you can't get it working by loading either of the two ALSA drivers we've mentioned so far you might try just upgrading to the latest kernel (2.6.9-1.681_FC3) and trying again before delving into latest development ALSA drivers, if you don't just decide to take that one back and try again. :)

EDIT2: I have to assume that the "audigyls" modules are part of the latest ALSA package v1.0.7 where FC3 comes with v1.0.6. Assuming that the emu10k1 module doesn't work for you and assuming you don't want to mess around with downloading/compiling/installing ALSA and potentially a new kernel and if you don't want to wait for the support to be added in the main distro (which could be anywhere from tomorrow to infinity) then I am thinking "otchie1" might have the best advice in this thread:

http://www.linuxquestions.org/questions/history/254265

A few month old look into the development of the driver in this thread:

http://www.mail-archive.com/alsa-devel@ ... 12815.html

It sounds like eventually the audigyls driver should be rolled into the emu10k1 driver, if it hasn't already been rolled in. Loading the emu10k1 module with modprobe as mentioned earlier and fiddling with gnome-alsamixer should tell you that. If it works then it's just a case of it not being in the proper config files so as to be detected by a kudzu/system-config-soundcard probe. Worst case scenerio, I think you said you could return it if it doesn't work right? The key is being able to match up what is printed on the box with what is really in the box.

dishawjp
administrator
administrator
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY
Contact:

Post by dishawjp » Tue Dec 07, 2004 3:03 pm

Thanks for all the time you've put in looking for all this. I'm still at work, but I blew out for a bit this afternoon and went to a local computer recycler and picked up an older second hand SB 16 bit PCI soundcard for $6.00. When I get home, I'll try plugging that in to see if it is detected. As you suggested last night, I did try raising the sound settings and enabling sound events and all that, but it was a no-go. Even if I tried to increase the volume control slider, it just dropped right down when I took the mouse cursor off it. I guess it won't let you increase volume when it doesn't see a sound card.

If I can't get it working tonight, I'll have to give up for now. My daughter needs her computer back and I'm out of time. The reason I wanted to get it going is that she uses her computer for everything from watching DVD's to listening to CD's. She has a great Altec Lansing speaker system and she uses it a lot. And if I hadn't talked her into upgrading to FC3, everything would still have been good.:oops:

Thanks again for everything and I'll let you know how I make out. Worst case, I know what her Christmas present will be... she and I will be building a nice new Linux box for her from the ground up.

Jim

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Tue Dec 07, 2004 3:52 pm

dishawjp wrote:Thanks for all the time you've put in looking for all this. I'm still at work, but I blew out for a bit this afternoon and went to a local computer recycler and picked up an older second hand SB 16 bit PCI soundcard for $6.00. When I get home, I'll try plugging that in to see if it is detected. As you suggested last night, I did try raising the sound settings and enabling sound events and all that, but it was a no-go. Even if I tried to increase the volume control slider, it just dropped right down when I took the mouse cursor off it. I guess it won't let you increase volume when it doesn't see a sound card.
Make sure you do this in "gnome-alsamixer" and not the default volume slider on your taskbar when making sure everything is unmuted and the sliders are up. It's possible that the one on your taskbar might not work when the gnome-alsamixer does work. Another thing that will cause the slider to bounce back is if the permissions are not sufficient on /dev/mix*.

caveman
programmer
programmer
Posts: 130
Joined: Sun Feb 09, 2003 1:08 pm
Location: Midrand Gauteng, South Africa

Post by caveman » Tue Dec 07, 2004 4:38 pm

Just my 2 cents worth.

I had a problem with my sound on FC3 as well.

On some of the programs the volume stayed full-out and on others.....
nothing... had to change the volume physically on the speakers.
Then found "aumix" and "xaumix" - a sound mixer with all the volumes
on zero. Set the volume on 100% - and now the software volume
controls seem to do the right thing.

My main problem was getting the four speaker system going by plugging
an xtra set of speakers into the line-in plug. Now everything seems fine.
Four speakers and software volume controls.

Hope this helps a lost soul or some such;)

dishawjp
administrator
administrator
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY
Contact:

Post by dishawjp » Tue Dec 07, 2004 6:42 pm

Success!!! Or, maybe I just took the coward's way out of a bind. The card I bought today was detected, installed automagically, and everything works.

I really want to thank you for all your help. If I had continued to follow through with your help, I'm certain that I would have gotten it eventually, but my little girl is now sitting next to me, waiting to take her computer home and she's happy.

BTW, she thanks you too :-)

Jim

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Tue Dec 07, 2004 7:29 pm

I figured the new card was the best solution. I really didn't expect you to get the other one working. Even with new ALSA drivers I think it would have had problems. Glad to hear you got it working and hopefully you can get your money back for the other card. Who says you can't get anything for 6 bucks these days? :)

dishawjp
administrator
administrator
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY
Contact:

Post by dishawjp » Tue Dec 07, 2004 9:22 pm

Glad to hear you got it working and hopefully you can get your money back for the other card. Who says you can't get anything for 6 bucks these days? :)
I will be returning the other card. I dropped $30 on it and expect a full refund. They will also hear that the reason it the card is no good is that it isn't Linux compatible. Maybe if retailers and vendors hear enough of that they will do more to either label their products better or provide Linux drivers on the CD's they include for Windows users.

Most hardware, even if fully supported by Linux, makes no mention of that fact on the package. They will list 10 versions of Windows, possibly Mac, but almost never Linux. So, if I mistakenly purchase a product that won't work with Linux, I will get a full refund. If not in the store, then after a hearing in the Small Claims part of the local court. Hell, that could almost be fun :-)

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Tue Dec 07, 2004 9:32 pm

I don't know why these vendors, especially ones like Creative, don't hire a good Linux driver writer, or at least fund an existing ALSA driver developer and ARM him with technical details of hardware before it is released. nVidia does a decent job but they have problems keeping up as well, mainly because they choose to be secretive and to keep the source closed. They are selling hardware not software for crying out loud.

worker201
guru
guru
Posts: 668
Joined: Sun Jun 13, 2004 6:38 pm
Location: Hawaii

Post by worker201 » Tue Dec 07, 2004 9:49 pm

Hopefully, hardware will start to open up soon. It was closed for a long time as part of Microsoft's trusted computing scheme. The original Xbox actually had its boot code hidden in the nvidia graphics chip, to prevent BIOS bypass. A couple of MIT kids solved that mystery within months. So now, with any luck, Microsoft will realize that security through obscurity just won't cut it. SELinux is a good multi-tiered example of how trusted computing ought to work.

Man, I wish i had that ES1879 back, because now that I know a few things, I want to see if I can get that thing working...

dishawjp
administrator
administrator
Posts: 334
Joined: Thu Jan 23, 2003 9:05 am
Location: Central NY
Contact:

Post by dishawjp » Sun Dec 12, 2004 7:23 am

Just in case anybody's interested, I had no problem returning the soundcard to CompUSA. I listed the reason for return as "not Linux compatible" and the clerk at Customer Service began immediately to fill out the refund form. I did have someone (a manager?) come over to ask what was wrong with the soundcard and when I told him that it didn't work with Linux he made a somewhat derogatory comment. I just replied that he should reconsider his opinion of Linux and Linux users, that we were growing and if he's in the computer hardware/software business he may not want to alienate us. HE didn't respond and just walked away.

But there was never a question of a full cash refund and I would highly recommend doing business with them. They also happen to be one of the few retailers in my area who carry software such as Red Hat Desktop, SUSE and Mandrake Linux boxed and occasionally a few other distros as well as OpenOffice.

Post Reply