Restoring device drivers on V1.0.2x

Using applications, configuring, problems
Post Reply
Message
Author
Waldo2
Posts: 19
Joined: Sun 08 May 2005, 20:47

Restoring device drivers on V1.0.2x

#1 Post by Waldo2 »

I lost the sound on two computers when I switched from V1.0.1 to 1.0.2RC. I followed the help steps, but have gotten stuck at the # insmod step as described below.

I first ran the Hardware probe script from the Control Panel menu and found that the on-board sound chip was "detected" but not "running". I followed the script Help file, and sure enough that particular driver had disappeared from V1.0.2RC. From 1.0.1 I used Rox to copy the driver to /root as suggested, switched to 1.0.2RC and ran the the following command as suggested, receiving the following error message:

# insmod /root/viaudiocombo.o.gz
insmod: error inserting '/root/viaudiocombo.o.gz': -1 Invalid module format

Any suggestions on what I should do next? .. and thanks. As a second step,assuming that the driver will run, how do I make it permanent? The Help file was a little vague on that step.

The V1.0.2RC Hardware probe also showed that two USB chips were "detected" instead of "running" as in 1.0.1. (One computer has a second add-in USB card.) I think that these are all fairly common chips, and the 2 motherboards are fairly new, so I hope that size constraints aren't eliminating too many drivers.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#2 Post by BarryK »

Try this:

# modprobe via82cxxx_audio

wscarl
Posts: 99
Joined: Mon 16 May 2005, 15:22
Location: NY

put 1.0.2RC on AST Laptop

#3 Post by wscarl »

AST Ascenia M Series 233mhz 64meg ram 3.2 hd cdrom ext floopy
Netgear FA511 (using tulip driver) the Sound is not working Crystal CS4237
and nothing list under sound? Are there Linux drivers for the Crystal CS4237
chipset and How do I load then?
This is the fist time loading to this Laptop, have been using Desktop - But Lobster easy HD install direction's Thank's Lobster :D :D :D I have been installing 1.0.1 on All my old Hardware with <128 ram! Make those old dogs run like pupies agian!!!!!! :shock: :D

Waldo2
Posts: 19
Joined: Sun 08 May 2005, 20:47

#4 Post by Waldo2 »

Well, Puppy responds to his master's voice. The audio began working after the following steps:

TEST SEQUENCE
Boot
Test MP3 CD in MPlayer - no sound
run # lsmod - no audio drivers shown loaded
run # modprobe via82cxxx_audio
Test MP3 CD in MPlayer - sound now working
run # lsmod again - now shows via82cxxx loaded

Reboot and repeat. Same results.
Now I only need a way get audio loaded at boot time.

The second machine is at another location, so I'll test it as well and try USB also.

One other anomaly is that the Puppy Hardware Probe continues to show everything but Ethernet as "detected" even after running modprobe, whereas under v1.0.1 everything was shown as "running".

Here is the terminal log (lsmod, modprobe, lsmod)

From v1.0.2RC
# lsmod
Module Size Used by
soundcore 9536 0
psmouse 27064 0
sr_mod 18240 0
scsi_mod 133864 1 sr_mod
ide_cd 39904 0
cdrom 38560 2 sr_mod,ide_cd
unionfs 192660 1
nls_iso8859_1 3952 1
nls_cp437 5616 1
ntfs 179832 0
ohci_hcd 21392 0
r8169 24340 0
crc32 4112 1 r8169
uhci_hcd 31832 0
ehci_hcd 31984 0
usbcore 115752 4 ohci_hcd,uhci_hcd,ehci_hcd
# modprobe via82cxxx_audio
# lsmod
Module Size Used by
via82cxxx_audio 28472 0
uart401 11524 1 via82cxxx_audio
sound 80140 2 via82cxxx_audio,uart401
ac97_codec 18576 1 via82cxxx_audio
soundcore 9536 2 via82cxxx_audio,sound
[etc.]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#5 Post by BarryK »

You can get any commands to run at bootup by putting them into /etc/rc.d/rc.local
-- this will not get changed when Puppy is upgraded to next version.

Anyway, I can make sure your sound chip gets properly detected in v1.0.3, but you have to tell me the chip numbers:
Start -> Control panel -> hardware probe
then press the "Modules" button, which should show the chip numbers, like "(1234:5678)". Otherwise, the "Query_pci" button should get that info.

wscarl
Posts: 99
Joined: Mon 16 May 2005, 15:22
Location: NY

sound driver 1.0.2

#6 Post by wscarl »

Do I need to post as new or can you Help me here about the sound in 1.0.2
I install on a larger 8.5 HD in LT with 1.0.2 Full still no sound

Waldo2
Posts: 19
Joined: Sun 08 May 2005, 20:47

#7 Post by Waldo2 »

Thanks for the V1.0.3 driver activation offer. I don't mean to pile another request on your plate, but hope that the info does contribute to the Puppy knowlege base. I have now had a chance to try V1.0.2 on three recent Via-based motherboards, each with a slightly different chip configuration. All three require the modprobe step with the via82cxxx_audio driver to get things running.

Board information: Asus A7V8x-x (Via KT400 ViaVT8235 ADI-AD1980), EPoX (Via KT400A ViaVT8237 Realtek ALC655) - SATA, MSI MS6702 V1.1 (Via K8T800 ViaVT8237 Realtek ALC655) - SATA

Puppy's audio detection on all three boards shows the following entry in the Control Panel / Hardware probe / Modules window:

AUDIO viaudiocombo: Via Technologies AC97 Compatible Controller (1106:3059) detected.

Image

These Via boards are actually an exception - Puppy has been very good setting up the audio on other machines I have tested, even compared to Windows XP. The screenshot, for instance, is from a new Athlon64 which I just configured. Even a new XP install did not handle the audio and I had to get the driver off the motherboard vendor's CD. The screenshot still shows audio and USB as "detected" rather than "running". I had already started the audio with modprobe, and the USB (including an add-in card) is actually running though not fully tested at this point. This board also has a SATA controller. I'll post some comments on this in another thread.

Cheers

Post Reply