no sound on Fujitsu P2120 laptop / wireless

[ShivaSmith]

I installed Mandrak 9.2 on my P2120 Fujitsu laptop and everything worked fine except that there is no sound. During installation Mandrake appeared to recognize my sound card. Well it said it was an Acer while windows says its SigmaTel, but the default sound driver snd-ali5451 appeared to be selected and installed successfully. I also tried trident in HardDrake, but neither driver works. I also made sure the sound was un-muted and turned up in KMix, but that also was not it.

 

I also tried various other things like using aumix, sndconfig, and other things, but no luck.

 

Sound works fine in my Windows XP partition.

 

=========

 

On another installation note ;0, I was wondering how in 9.2 I can activate my wireless networking card (built in on the Fujitsu 2120). It's just that in Hard Drake it says the status of the wireless ethernet adapter is "down." How to make it "up"? It recognized it as an Orinoco adapter (really it is a Prism one -- the same maybe?). From my Windows partition the adapter works fine -- I'm using 128 WEP (found what field to enter that in on the Network Wizard in MDK 9.2), set mode to "auto", etc. but no luck.

 

Thanks for any help. :^)

[chris-tux]

Hi,

No a lot of experience with Linux but I solved my sound pb first by probing the sound card

lspci

then I checked in the ALSA web page if my card was supported then installed ALSA package, popped up the volume :D

Hope it will help

Alsa-project

[ShivaSmith]

Thanks, I'll try that. If anyone else has any other ideas, I'd like to hear 'em.

 

Actually the main thing would be to set up the wireless ethernet first, so help with that would be cool. :) ;)

[liquidzoo]

Not sure if this will help you or not seeing as the card is built in, but I wrote an FAQ about PCMCIA wireless here: http://www.mandrakeusers.org/index.php?showtopic=5494

 

If you could post the chipset of the internal card for us, we would be able to assist you in a bit more detail.

[ShivaSmith]

Thanks LiquidZoo, yes I did see your PCMCIA post -- nice and thorough :). Yes my 802.11b adapter is built-in on the Fujitsu P2120 (laptop).

 

Ok, from WindowsXP I got the following info on my wireless adapter:

 

Intersil Prism Wireless LAN -- Network Driver 1.07.41, date 6/5/02

NIC Firmware version 1.04.01.00

 

[And for my soundcard it said SigmaTel C-Major Audio, incidentally, although I'm gonna try to get wireless ethernet working first ;).]

 

One thing I noticed.. on my last reboot of MDK 9.2 on my P2120 the network configuration tool came up and I went through everything I thought I should do and at the end it said "Bringing up interface eth0 .... failed." and

"Bringing up interface eth1: ..... failed."

 

(also said during boot: re: sound... "starting alsa version 0.9.6 ali5451")

 

anyway.. ok... KDE 3.1 comes up, and then in a konsole, from lspci I got:

 

00:12.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev 01), for which I believe the driver that MDK picked was "orinoco_pci"

 

(for audio: 00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01))

 

using DrakConnect via the MCC I see various settings and such, but what I don't see is how to to turn the wireless adpater *on*... so that I might see it listed in the MCC as state "up" instead of how it is currently listed as "down." And note that this 802.11b adapter works fine in Windows XP so I know the hardware works.

 

Ok, thanks for all the network noobie help :D

[liquidzoo]

Ok, If XP is recognizing it as a prism card, that may help us (Imagine that...an m$ product actually providing useful information )

 

Try this for me. As root, type lsmod and see if the module orinoco_cs (or orinoco_pci) is running.

 

If so, do a modprobe -r orinoco_cs (or _pci) followed by modprobe prism_cs (or _pci, depending on which one was running) and see if there are any errors.

 

You saying that MCC is recognizing the card as eth1 makes me skeptical, though. It would seem that it is running. Have you gone through the network config and set all of the options correctly?

 

Try configuring it one more time, and making sure to restart the network at the end of the wizard (I always use expert mode in the wizard, might save you some time). If it doesn't work, try it again with the prism_* driver and see if that makes a difference.

[ShivaSmith]

Ok, I did the lsmod as root and all the orinoco related stuff I got was:

 

orinoco_pci 4228 0 (autoclean) (unused)

orinoco 36824 0 (autoclean) [orinoco_pci]

hermes 7784 0 (autoclean) [orinoco_pci orinoco]

 

I did a modprobe -r on all 3 of those listed above and got no errors.

 

When I tried to modprobe the prism_*'s, modprobe could not locate the modules, which could be part of my problem ;).

 

So then I did urpmi prism, and from my Linux Format DVD which has MDK 9.2 on it, I got the following installation message:

 

installing /var/cache/urpmi/rpms/prism2-utils-0.2.1-0.pre11.2mdk.i586.rpm

 

Then I tried to modprobe prism / prism2 / prism2-utils but modprobe could not find the modules... maybe just doing the urpmi was not enough?

 

Anyway, hmmm... I'm not sure what is going on... 'cause then in MCC under "Network and Internet" it still says "eth0 No Ip dhcp 8139too down". I'm not sure where the "driver 8139too" came from.

 

Actually back when I had first installed MDK, I recall it detecting both an eth0 and an eth1, but just the states were both shown as "down."

 

I wonder if I have somehow screwed things up a bit with all this messing around with network stuff, well I'm sure it is fixable, but I almost wonder if it might be easiest to reinstall MDK 9.2 from my DVD. I have no problem reinstalling since I haven't done anything critical with my current install.... just a thought if it would be easier to work with a clean slate.

 

thanks for all the help :)

[liquidzoo]

Strange that the prism drivers aren't there...do you have the kernel source installed?

 

If not, issue a uname -r in a console and use the kernel output and go to http://rpmfind.net and search for kernel-source-kernelversion

 

I *think* that the drivers are in there, but I'm not sure.

 

Also, your issue with MCC seeing eth0 as down and the other driver...Usually eth0 is your onboard ethernet, and eth1 will be your wireless. That would explain why eth0 is showing as down.

 

I need to research this more when I get access to my laptop. I would be willing to bet there's a command that we can use to help, but I need to see my wireless hardware and commands to work through it more.

[ShivaSmith]

Victory!!! :lol:

 

I'm now typing this to you inside Konqueror from MDK 9.2 on my Fujitsu P2120 through the built-in wireless 802.11b via my Netgear wireless router. :^D

 

The solution was to re-install MDK (to get both eth0 and eth1 to be detected properly) and, when configuring the network adapters, to very carefully make sure all options are set correctly... duh ;) :)

 

It's actually working using the orinoco_pci driver which was originally installed. I'm using zeroconf DHCP and I think maybe before I hadn't put the proper hostname in the proper field. I'm also using full 128 bit WEP and it works just fine. :)

 

Well then, now I can move on to konquering my sound-driver problem. Also I seem to have some slight screen interference that sometimes emerges when I drag a window or move the mouse.. some "streakiness" to the right of the moving object. Also it might be caused by some local electronic devices 'cause I'm also noticing it now when nothing is moving... perhaps some slight video card weirdness or something... tho' I don't see it in WinXP. Also I need to get my eraser-head mouse to work at the same time as my external usb mouse.

 

In any case, all problems are now *much* more easily solveable now that I have net access... so hurray :).

 

Thanks again to all who helped :).

[liquidzoo]

Too bad a reinstall is what cured your issue with the net drivers, but great job with that! Glad to see that it's working.

 

Your video issue might be cured by installing the correct video drivers. If it's an nvidia card, you will need the kernel source (at least, I always have).

 

Hope you get your sound working. I have a similar issue that I'm working through on my laptop.

[ShivaSmith]

Thanks, yeah it's nice to now be able to get on the net from Linux anywhere in the house ;).

 

Actually I have a Mobility Radeon in this Fujitsu laptop and the MDK installer seemed to locate it just fine as "Radeon", but there are 2 other Radeon drivers that are labeled as "Radeon[a few letters]" and maybe I'll try those other drivers. Also I tried changing colors from millions to thousands and also resolutions -- might be it's not at native resolution for the LCD, so we'll see. Other than that slight streaking to the right of the window when you move a window, the display is crystal clear.

 

For your own sound problems/explorations, you might want to look at the following. I haven't implemented these steps yet, but found 'em on the net and I think I'm gonna try 'em since they are pretty thorough:

 

Update: Setting up sound

November 6: I managed to get the sound to work,

following the instructions on

http://www.greenfly.org/fujitsu/. Here is what I did:

First, I downloaded the following files from

http://www.alsa-project.org/:

 

    * alsa-driver-0.9.8.tar.bz2

    * alsa-oss-0.9.8.tar.bz2

    * alsa-lib-0.9.8.tar.bz2

 

I stored these files in /usr/local/src. Then I

followed these steps:

 

cd /usr/local/src

# compile and install core sound drivers

tar jxf alsa-driver-0.9.8.tar.bz2

cd alsa-driver-0.9.8/

./configure

make

make install

modprobe snd-ali5451

# (/var/log/messages: kernel: PCI: Found IRQ 9 for

device 00:04.0)

cd ..

 

# compile and install sound libraries, needed to

compile alsa-aware programs

tar jxf alsa-lib-0.9.8.tar.bz2

cd alsa-lib-0.9.8/

./configure

make

make install

cd ..

 

# compile and install OSS compatibility stuff - many

programs need this

tar jxf alsa-oss-0.9.8.tar.bz2

cd alsa-oss-0.9.8/

./configure

make

make install

modprobe snd-pcm-oss

modprobe snd-mixer-oss

modprobe snd-seq-oss

 

At this point, all the correct modules are installed

and running, but you will not hear anything, because

the speaker volume is initially set to 0! To set the

volume, use aumix:

 

aumix -v 100 -w 100

 

At this point, your sound should be working. However,

you still need to edit /etc/modules.conf to make the

settings permanent. Here are the relevant lines in my

/etc/modules.conf:

 

alias sound-slot-0 snd-ali5451

post-install sound-slot-0 /bin/aumix-minimal -f

/etc/.aumixrc -L >/dev/null 2>&1 || :

pre-remove sound-slot-0 /bin/aumix-minimal -f

/etc/.aumixrc -S >/dev/null 2>&1 || :

above snd-ali5451 snd-mixer-oss snd-pcm-oss

snd-seq-oss

 

Note that there was an old "alias sound-slot-0

trident" line, which I deleted.