1.0.2 to 1.0.3 upgrade problems: no sound modules

Using applications, configuring, problems
Post Reply
Message
Author
c10237
Posts: 7
Joined: Mon 06 Jun 2005, 14:09

1.0.2 to 1.0.3 upgrade problems: no sound modules

#1 Post by c10237 »

Good day to you guys and keep up the good work on Puppy.

1.0.2 is a good distribution. But im am having problems upgrading it to 1.0.3. Here's the shinny...
Upgrading from 1.2.0 to .3 was easy but when i tried to load the drivers for my sound card using modprobe, I noticed that the module.conf file is stil using the 2.6 kernel. It always says that the module.conf is much newer that the 2.4.27 modules.dep file on the /lib. I tried different steps in order to resolve it but it seems that the module.conf file was not updated from 2.6 to 2.4. I could not load my sound card anymore during that time that is why I reverted back to the .2 distro.

I hope that somebody would help me in shedding some light on the subject... I would love to go to .3.

Also how would I enable the swap space on the .2 distro? :lol: :D

User avatar
Ian
Official Dog Handler
Posts: 1234
Joined: Wed 04 May 2005, 12:00
Location: Queensland

#2 Post by Ian »

You might do better to just do a 1.0.3 clean install.

If you have a swap partition 1.0.2 will automatically switch swap on.

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

Re: 1.0.2 to 1.0.3 upgrade problems: no sound modules

#3 Post by BarryK »

c10237 wrote: Upgrading from 1.2.0 to .3 was easy but when i tried to load the drivers for my sound card using modprobe, I noticed that the module.conf file is stil using the 2.6 kernel. It always says that the module.conf is much newer that the 2.4.27 modules.dep file on the /lib. I tried different steps in order to resolve it but it seems that the module.conf file was not updated from 2.6 to 2.4. I could not load my sound card anymore during that time that is why I reverted back to the .2 distro.
This is not a problem.
The 2.6 kernel does not use module.conf at all.
If modules.conf is newer than modules.dep that is not a problem.

We need the details on your sound card, and what module previously worked.
Also, type "lsmod" command to see if a sound module is indeed loaded.
Also try "Start -> Control panel -> Hardware probe -> Modules".
Let us know the details.

Post Reply