[solved ]no sound in FullMonty

[Just17]

I went to the site you suggested (http://www.pclinuxos.com/forum/index.php/topic,83740.0.html) and did everything but no results, pulse audio is enabled but still no sounds.
Then I tried the trouble shooters but;
no sound profile symlink in /etc/alternatives/
and no /etc/sysconfig.
Any more suggestion?

The link is soundprofile... one word, and /etc/sysconfig is an integrated and essential part of your system. If you don't have the latter, you don't have a working system. Look again, for both.

I don't recall a response to this ......  did you confirm the presence of the needed files/links?

[rejean]

Here is what's in /etc/alternatives/soundprofile/;



and in alsa-default.conf;

Code: [Select]

# pulseaudio plugin configuration

pcm.!default {
    type pulse
    hint {
        show on
        description "Default ALSA Output (currently PulseAudio Sound Server)"
    }
}

ctl.!default {
    type pulse
}

in canberra.conf;

Code: [Select]

CANBERRA_DRIVER=pulse
and finally in profile.conf;

Code: [Select]

SOUNDPROFILE=pulse

What I see in /etc/sound/profiles/pulse/ are 3 files;alsa-default.conf,canberra.conf and profile.conf.
alsa-default.conf has;

Code: [Select]

# pulseaudio plugin configuration

pcm.!default {
    type pulse
    hint {
        show on
        description "Default ALSA Output (currently PulseAudio Sound Server)"
    }
}

ctl.!default {
    type pulse
}

in canberra.conf;

Code: [Select]


CANBERRA_DRIVER=pulse
and in profile.conf;

Code: [Select]

SOUNDPROFILE=pulse

Finally what I see in /etc/sysconfig/pulseaudio is;

Code: [Select]

# Set the below variable to suit your needs.
# Possible values are:
#   personal  Start a personal pulseaudio server per-user (recommended)
#   system    Start a system wide daemon (not yet implemented)
#   none      Don't start pulse
#
# NB For the system wide daemon, users need to be in the group pulse-access.
#
PULSE_SERVER_TYPE=personal

# Set the various arguments to the daemon here
#  This defaults to:
#  --log-target=syslog for "personal"
#PULSE_ARGS=
I hope it is not too confusing. Thanks for your patience!!!

[Just17]

Those seem to be correct .....  just confirm that

/etc/alternatives/soundprofile

is a link .......  right click on it and select 'Properties' .....  it should have an entry that reads

Points to:  /etc/sound/profiles/pulse

If that is there then it is correct.

**********

It would be best if you could use speakers or headset directly rather than the wireless headset .....  but I don't really suspect the wireless unit if it works normally with another OS.

*******

I am back to wondering about the sound card and whether it needs a later kernel for support.

There is a 3.4.11 kernel in the testing section of the repository, and it might be worthwhile installing that kernel to see if it makes any difference.

To do so you would need to add  testing  to the sections of the repository you use in Synaptic

main updates nonfree kde games testing

Then Reload and search for    kernel-3.4.11-pclos1.bfs   and install it.

It will bring in one other kernel package.

After install reboot and check that you are using the new kernel with   uname -r 

Test the audio with the new kernel.

If you do not wish to keep that kernel you can boot using the older one and then uninstall the newer one.
Do not attempt to uninstall a kernel that is presently in use 

It would also be advisable to use more than one application to test the audio .....  play an audio file with a player app as well as what you have been testing with.

[rejean]

Those seem to be correct .....  just confirm that

/etc/alternatives/soundprofile

is a link .......  right click on it and select 'Properties' .....  it should have an entry that reads

Points to:  /etc/sound/profiles/pulse

If that is there then it is correct.It doesn't want to work.

It is there.

So next;

I open Synaptic, click on Settings ->Repositories then I try entering the new section;



I click OK then I reload and look again for the new kernel but I don't see it;




I went back into the repositories and added 2 new mirrors;
http://pclosusers.com/pclosfiles/
and http://ftp.nluug.nl/ibiblio/distributions/pclinuxos/pclinuxos/apt/

but I still don't see the kernel. I tried with more mirrors and I still don't see it.

Now I am told that some of the repositories were not available;



but I can see a few mirrors that could (should?) have the kernel like;

[Just17]

 

My apologies .......  I did not realise that the 3.4.11 testing kernel is not in the repositories now  .......  it is still showing here in Synaptic because I have it installed 

Can you post your full hardware details in case something obvious has been missed?

[Old-Polack]

My apologies .......  I did not realise that the 3.4.11 testing kernel is not in the repositories now  .......  it is still showing here in Synaptic because I have it installed  

Can you post your full hardware details in case something obvious has been missed?

It shows in the testing section on heanet. I just checked in a VM that doesn't have that kernel installed.

EDIT: I marked it for installation, the devel package was brought in, and the two packages were successfully installed.

[rejean]

Just opened Synaptic this morning and I am getting the following message;

The following problems were found on your system:
E: The package cache file is corrupted
E: Unable to lock the list directory

I added the url for heanet and the testing in the source and after reload I got this;

Could not download all repository indexes

The repository might be no longer available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and the correct writing of the repository address in the preferences.

 Then I closed Synaptic and after I reopened it I can see the kernel # so I marked the 2 entries and chose apply.

Before I reboot I want to register the message that came after installing the new kernel;

Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
mkinitrd failed:
(mkinitrd -f /boot/initrd-3.4.11-pclos1.bfs.img 3.4.11-pclos1.bfs) at /usr/lib/libDrakX/bootloader.pm line 124.

[rejean]

I don't think it worked. After rebooting;

Code: [Select]

[rejean@localhost ~]$ uname -r
3.2.18-pclos2.bfs

and here is the first part of /boot/grub/menu.lst;

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd2,11)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd2,11)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=5498d2cf-9d68-4f8d-9ca2-8240974d5b37 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a8f96c38-a441-4872-821e-fcb081110f36 splash=silent vga=788
initrd (hd2,11)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd2,11)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=5498d2cf-9d68-4f8d-9ca2-8240974d5b37 quiet nokmsboot vmalloc=256M acpi=on resume=UUID=a8f96c38-a441-4872-821e-fcb081110f36
initrd (hd2,11)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd2,11)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=5498d2cf-9d68-4f8d-9ca2-8240974d5b37 quiet nokmsboot failsafe vmalloc=256M acpi=on
initrd (hd2,11)/boot/initrd.img

Shouldn't there be 2 entries, one for each kernel? This is what I normally get from other distros.

[Old-Polack]

Just opened Synaptic this morning and I am getting the following message;

The following problems were found on your system:
E: The package cache file is corrupted
E: Unable to lock the list directory

I added the url for heanet and the testing in the source and after reload I got this;

Could not download all repository indexes

The repository might be no longer available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and the correct writing of the repository address in the preferences.

 Then I closed Synaptic and after I reopened it I can see the kernel # so I marked the 2 entries and chose apply.

Before I reboot I want to register the message that came after installing the new kernel;

Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
Error: Can't have overlapping partitions.
mkinitrd failed:
(mkinitrd -f /boot/initrd-3.4.11-pclos1.bfs.img 3.4.11-pclos1.bfs) at /usr/lib/libDrakX/bootloader.pm line 124.

Exactly how many mirrors do you have checked? There should only be one, not counting the megagames mirror, which is optional. After selecting only one mirror, you need to click Reload again. If you get errors about not being able to download all repository indexes, the mirror is most likely syncing, so wait an hour or so to let it finish.

The overlapping partitions errors are a bit worrisome, so open a terminal, su to root, then enter the command;

[root@localhost ~]# fdisk -l                                 <Enter>

Post your results.

[Just17]

Duh!  I checked the heanet repo and yes the kernel is there! 

+1 to O-P's post above .......  and also please post your hardware details, thanks.

[rejean]

I reopened Synaptic and this time unselected every mirror except 'heanet' and marked the 2 kernels for reinstallation. We'll see what happens.
Edit:
Sorry I think our posts are overlapping not just my partitions. Anyway;
@O-P;

Code: [Select]

[root@localhost rejean]# fdisk -l

Disk /dev/sda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 cylinders, total 78125000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb25cb25c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     1060289      530113+  83  Linux
/dev/sda2         1060290     1590434      265072+  82  Linux swap / Solaris
/dev/sda3         1590435    32322779    15366172+  83  Linux
/dev/sda4        32322780    78124094    22900657+  83  Linux

Disk /dev/sdb: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders, total 490234752 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa34da34d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63    78140159    39070048+   7  HPFS/NTFS
/dev/sdb2        78140160   117210239    19535040   83  Linux
/dev/sdb3       117210301   490223474   186506587    5  Extended
/dev/sdb5       117210303   118190204      489951   82  Linux swap / Solaris
/dev/sdb6       118190268   159123824    20466778+  83  Linux
/dev/sdb7       159123888   200507264    20691688+  83  Linux
/dev/sdb8       200507266   220042304     9767519+  83  Linux
/dev/sdb9       220042368   239577344     9767488+  83  Linux
/dev/sdb10      239577408   280527029    20474811   83  Linux
/dev/sdb11      280527093   490223474   104848191    b  W95 FAT32

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00011388

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048    66074623    33036288   83  Linux
/dev/sdc2        66074624   170932223    52428800   83  Linux
/dev/sdc3       170947665  1686455504   757753920    5  Extended
/dev/sdc4      1256347648  1324382207    34017280   83  Linux
/dev/sdc5       170947728   215977859    22515066   83  Linux
/dev/sdc6       215977923   232348094     8185086   82  Linux swap / Solaris
/dev/sdc7       232348158  1256347259   511999551    7  HPFS/NTFS
/dev/sdc8      1324382598  1396482254    36049828+  83  Linux
/dev/sdc9      1396482318  1433319299    18418491   83  Linux
/dev/sdc10     1433319363  1490655284    28667961   83  Linux
/dev/sdc11     1490659328  1543669784    26505228+  83  Linux
/dev/sdc12     1543669848  1593455219    24892686   83  Linux
/dev/sdc13     1593455283  1686455504    46500111   83  Linux



@Just17; I am not quite sure what you want me to do, what kind of info you need.

[Just17]

@Just17; I am not quite sure what you want me to do, what kind of info you need.

The general hardware spec of the machine .......  processor, memory, graphics, audio etc etc .....  make & model number if applicable ...... it gives us a better idea what we are dealing with ...... 

[Old-Polack]

I reopened Synaptic and this time unselected every mirror except 'heanet' and marked the 2 kernels for reinstallation. We'll see what happens.

Only install one kernel at a time. Never two. There are processes involved that will surely screw up when multiple kernels are installed at one time.

After installing a kernel, (only one) reboot. It will be longer than a normal reboot, because all the dkms drivers have to be rebuilt to work with the new kernel. Only after successfully logging into your system, check which kernel is being used with the uname -r command. The newly installed kernel should be the default kernel, and the same boot menu selection you normally use should boot to the new kernel without any modifications to /boot/grub/menu.lst.

If you then install another kernel, the same process will repeat, as above, and it will then become the default kernel.

[Just17]

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048    66074623    33036288   83  Linux
/dev/sdc2        66074624   170932223    52428800   83  Linux
/dev/sdc3       170947665  1686455504   757753920    5  Extended
/dev/sdc4     1256347648  1324382207    34017280   83  Linux
/dev/sdc5       170947728   215977859    22515066   83  Linux

Am I losing it or is this rather odd?

Not only are the partitions not in order, but that 'primary' partition appears to be within the Extended partition.

.....  or I am misreading something .....

[Old-Polack]

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048    66074623    33036288   83  Linux
/dev/sdc2        66074624   170932223    52428800   83  Linux
/dev/sdc3       170947665  1686455504   757753920    5  Extended
/dev/sdc4     1256347648  1324382207    34017280   83  Linux
/dev/sdc5       170947728   215977859    22515066   83  Linux

Am I losing it or is this rather odd?

Not only are the partitions not in order, but that 'primary' partition appears to be within the Extended partition.

.....  or I am misreading something .....

No you are not losing it, it is exactly what you describe... a royally screwed up partition table.