[SOLVED] Sound stutters on new KDE install

[Grisen]

On a new dual boot install of 2010.10 with XP the welcome and goodbye sound stutters.  Youtube video sound stutters.  Amarok tunes stutter.

This happens randomly on some boots.  On shutdown, when the sound is in "stutter mode" it will play the broken goodbye sound, then will not complete the shutdown-- just sits at the wallpaper.  I have to do a hard shutdown.

9 boots out of 10, the laptop works fine with no stuttering.

Is there a way in Linux to check for file corruption now like with Windows SFC or a Win "repair install" (not file system corruption - fsck from live CD, which I've done)?  Just a wild guess that it's a corrupt file.

I md5sum my iso files and CD's.

Machine seems to run fine with exception of sound and, when sound is bad, doesn't shutdown.  Situation is not major, but a nuisance and for the newb user I'm helping migrate from Windows on his machine-- would like it to work right and not go through a reinstall.

Ideas, anyone?

[Grisen]

Starting to wonder if this sound problem only occurs if I do something to interact with the laptop before the "welcome" music has played.  It's the last thing the machine does before it's ready for action (systray loads, wireless link established, update-notifier checks for updates, then music.)

E.g. If I hit the Firefox shortcut or respond to a prompt from update-notifier to configure my wireless (no connection) before the music, then I get sound problems (I think...)

Is the OS so sensitive for others?  

I don't recall ever having this be an issue on other installs-- my own laptop or desktop.  I'm just as quick on the trigger there...

Thoughts?

EDITED NEXT DAY:

Well, stuttering started after 30 min of internet browsing when I opened a youtube video.  Then exit sound stuttered and machine wouldn't follow shut down command.

[muungwana]

you can force a file system check on next system reboot and then reboot by opening the terminal, log in as root and then executing this command

touch /forcefsck


Lack of consistency on your sound problem may be problematic on trying to troubleshoot it. Have you tried to configure sound in pcc and select a different sound driver?

you can do that by going to pcc->hardware->sound configuration

Log in and log sounds are produced by phonon, try to set phonon to use a different sound device at systemsettings->hardware->multimedia->phonon

[Grisen]

Thanks for the command line tip, that's much easier than booting a live CD to fsck the hard drive.  Right now I have the machine set to do a file system check every 5 mounts on /home and every 7 mounts on /  using tune2fsck command in terminal.

Okay-- so looking at phonon in Configure Your Desktop theres only one device shown there: "HDA ATI SB (STAC 92xx Analog)" and doesn't appear to be any list of options available anywhere.  Should there be some more options?  Also the problem is broader than just login and logout music-- the last time this happened the login music was fine but then sound for a youtube video started stuttering badly, then logout music stuttered, and the machine wouldn't respond to gui shutdown commands, only keyboard shortcuts.

PCC>hardware>sound configuration I already looked at, but the list of sound drivers is maybe a couple of hundred long.  I'm at a loss as to where to start.  I saw the make of this card from looking at it in XP, but don't see anything related in the list.  PCLOS install chose (snd_hda_intel[ALSA]).  Does a person just start at the top of the list and try different drivers?

There's no one else on the forum that I can find with a sound-stutter issue, so that leads me to think about file corruption.

Any thoughts about my hunch that a file (like the sound driver) is corrupted for some reason?  Is there a way to deal with data/file corruption in Linux (not talking about file system corruption and fsck)?  Windows tools here are chkdsk and SFC /scannow (System File Checker).  Must be tools with a similar function in Linux (?).  Last resort before a full install in Win is a repair install, so there are several alternatives to deal with file corruption before doing a full reinstall.  Let's say the lens on the CD drive is dirty and it threw a one instead of a zero when loading PCLOS sound drivers during the install.  Or the hard drive has a bad sector and the sound driver or some other sound-related system file got copied there.

In Windows diagnostics (not that I'm a MS fan, just happen to know it) causes of computer failure are generally three: bad hardware, file corruption (or file system corruption), and malware.  So how, in the case of this sound problem, can a person address the possibility of a corrupted sound driver, for example?

That may not even be the problem.  Just saying... in Windows I would look at file corruption and try to replace the driver with a fresh copy from the manufacturer's website.  That's after doing a Google search on keywords like "sound stutters XP" to get some other leads.

[muungwana]

as root, open "/var/log/syslog" text file and go through it and there could be a clue on why sound doesnt work as expected

You can have a corrupted file on a clean file system but this, as far as i can tell,will be caused by installing the corrupted file. Its possible but i dont see file corruption as an issue, if it is, the system log will have a record of it

does the system run slow when sound stutters? It could be you have a run away process that eat most of the cpu circle all by itself and the stuttering is due to sound system not getting its share of cpu time

what does this command give you?

lspci | grep audio

How many options you see on both areas depends on what driver you have loaded and what functionality it see from your hardware, its hard to tell how many options you should expect to see.I have three options on both so its not hard to test them. Always go with a driver that uses ALSA

[Grisen]

Not sure what you're looking for here, but lspci | grep audio doesn't return anything.  grep audio alone doesn't return any information, lspci shows me what's on the PCI bus, which includes  Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)

[root@localhost bert]# lspci | grep audio
[root@localhost bert]# lspci
00:00.0 Host bridge: ATI Technologies Inc Device 5a31 (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
08:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
[root@localhost bert]#
[root@localhost bert]#
[root@localhost bert]# grep audio

Regarding the syslog, it is tens of thousands of lines long, so I'll wait for another misfire and look at just that portion of the log.  Thx for the tip.

I don't get the impression there is a runaway process eating up CPU cycles, but can check with  ctrl esc  next time.

[muungwana]

The command should have been "lspci | grep -i audio"

The "-i" option to "grep" command tell the command to ignore differences in upper and lower cases letters. The command looked for "audio" while your system returned "Audio" and hence it missed it because it saw them as being different.

The command was supposed to filter out the rest and only show the audio part since this is the problematic part. I googled the card you have a lot of people seem to have issues with it. I havent seen anything yet with a solution to your problem.

What kernel are you using? try to update to the latest one and see if it will help.

[ff103]

If this machine is a laptop, go to PCLinux Control Center>Boot>Set up boot system, click on "advanced" button, and uncheck acpi and apci and see if that fixes the sound. if it does, you may notice that the laptop will not power off at shutdown, if this is the case,go back and turn on ACPI and see if that fixes it, if not, uncheck ACPI and check APCI. this worked on my HP laptop with stuttering sound. hope this helps.

[Grisen]

Muungwana - Currently using kernel 2.6.33.5-pclos1.bfs.  Will upgrade to 2.6.33.7-pclos6.bfs through Synaptic.

FF103, the acpi / apci fix looks easy enough (if I can keep my p's and c's straight  ).  Thanks for posting since there was no previous post I could find with a "sound stutters" issue.  (No need to reinvent the wheel, eh?)  Will try it.

As we say here in Alabama, "Thank y'all"

**EDIT**   1/2 hour later

Okay, installed new kernel.  Rebooted, uninstalled old kernel, rebooted.

I was quick to respond to update-notifier that, yes, I did want to configure my internet connection, since it didn't come up automatically.  Welcome sound hadn't played yet.  When it did, it stuttered.

Okay!  Looked at /var/log/syslog, posting a piece of it here.  Note in the log that the machine was dealing with laptop issues an then says
##Program is starting ##.  Then it goes into starting the wireless.  That may be me interrupting the welcome music.  Just before ##Program is starting## it was dealing with laptop issues, which may have had to do with acpi or apci.  There are three lines that say Module /usr/local/share/laptop-mode-tools/modules/* is not executable.  So, maybe it is an acpi / apci issue.

Dec  4 16:46:41 localhost laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: /proc/fs/nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: Checking nfsd against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/lcd-brightness.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-mc-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-smt-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/start-stop-programs.
Dec  4 16:46:41 localhost laptop-mode: START_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: STOP_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/syslog-conf.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/terminal-blanking.
Dec  4 16:46:41 localhost laptop-mode: CONTROL_TERMINAL is disabled, skipping...
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/usb-autosuspend.
Dec  4 16:46:41 localhost laptop-mode: USB autosuspend is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/video-out.
Dec  4 16:46:41 localhost laptop-mode: video-out module is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-ipw-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IPW Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-iwl-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IWL Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/lib/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/share/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /etc/laptop-mode/modules/* is not executable.
Dec  4 16:46:41 localhost klogd: usbcore: registered new interface driver snd-usb-audio
Dec  4 16:47:02 localhost net_applet[3786]: ### Program is starting ###
Dec  4 16:47:13 localhost draknetcenter[3873]: ### Program is starting ###
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: changed mode of /etc/sysconfig/network-scripts/ifcfg-wlan0 to 700
Dec  4 16:47:33 localhost draknetcenter[3873]: written wlan0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: running: /sbin/ifdown wlan0 daemon
Dec  4 16:47:34 localhost ifplugd(wlan0)[2864]: Exiting.
Dec  4 16:47:34 localhost draknetcenter[3873]: running: /sbin/ifup wlan0 daemon
Dec  4 16:47:36 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:36 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:36 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: deauthenticating from 00:12:88:4c:aa:a1 by local choice (reason=3)
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:37 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:37 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: authenticated
Dec  4 16:47:37 localhost klogd: wlan0: associate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: RX AssocResp from 00:12:88:4c:aa:a1 (capab=0x431 status=0 aid=1)
Dec  4 16:47:37 localhost klogd: wlan0: associated
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec  4 16:47:37 localhost klogd: cfg80211: Calling CRDA for country: US
Dec  4 16:47:37 localhost klogd: cfg80211: Current regulatory domain updated by AP to: US
Dec  4 16:47:37 localhost klogd:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:47:37 localhost klogd:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: ifplugd 0.28 initializing.
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using interface wlan0/00:C0:A8:C1:28:70 with driver <rtl8180> (version: 2.6.33.7-pclos6.bfs)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using detection mode: SIOCETHTOOL
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Initialization complete, link beat detected.

Dec  4 16:46:41 localhost laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: /proc/fs/nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: Checking nfsd against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/lcd-brightness.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-mc-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-smt-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/start-stop-programs.
Dec  4 16:46:41 localhost laptop-mode: START_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: STOP_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/syslog-conf.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/terminal-blanking.
Dec  4 16:46:41 localhost laptop-mode: CONTROL_TERMINAL is disabled, skipping...
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/usb-autosuspend.
Dec  4 16:46:41 localhost laptop-mode: USB autosuspend is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/video-out.
Dec  4 16:46:41 localhost laptop-mode: video-out module is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-ipw-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IPW Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-iwl-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IWL Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/lib/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/share/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /etc/laptop-mode/modules/* is not executable.
Dec  4 16:46:41 localhost klogd: usbcore: registered new interface driver snd-usb-audio
Dec  4 16:47:02 localhost net_applet[3786]: ### Program is starting ###
Dec  4 16:47:13 localhost draknetcenter[3873]: ### Program is starting ###
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: changed mode of /etc/sysconfig/network-scripts/ifcfg-wlan0 to 700
Dec  4 16:47:33 localhost draknetcenter[3873]: written wlan0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: running: /sbin/ifdown wlan0 daemon
Dec  4 16:47:34 localhost ifplugd(wlan0)[2864]: Exiting.
Dec  4 16:47:34 localhost draknetcenter[3873]: running: /sbin/ifup wlan0 daemon
Dec  4 16:47:36 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:36 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:36 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: deauthenticating from 00:12:88:4c:aa:a1 by local choice (reason=3)
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:37 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:37 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: authenticated
Dec  4 16:47:37 localhost klogd: wlan0: associate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: RX AssocResp from 00:12:88:4c:aa:a1 (capab=0x431 status=0 aid=1)
Dec  4 16:47:37 localhost klogd: wlan0: associated
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec  4 16:47:37 localhost klogd: cfg80211: Calling CRDA for country: US
Dec  4 16:47:37 localhost klogd: cfg80211: Current regulatory domain updated by AP to: US
Dec  4 16:47:37 localhost klogd:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:47:37 localhost klogd:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: ifplugd 0.28 initializing.
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using interface wlan0/00:C0:A8:C1:28:70 with driver <rtl8180> (version: 2.6.33.7-pclos6.bfs)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using detection mode: SIOCETHTOOL
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Initialization complete, link beat detected. and starts configuring wireless.  That may be me launching

Dec  4 16:46:41 localhost laptop-mode: Checking none against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: /proc/fs/nfsd not found in PARTITIONS.
Dec  4 16:46:41 localhost laptop-mode: Checking nfsd against HD because PARTITIONS contains "auto".
Dec  4 16:46:41 localhost laptop-mode:    Considering /dev/sda.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/lcd-brightness.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-mc-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/sched-smt-power-savings.
Dec  4 16:46:41 localhost laptop-mode: Scheduler power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/start-stop-programs.
Dec  4 16:46:41 localhost laptop-mode: START_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: STOP_SERVICES =
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/syslog-conf.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/terminal-blanking.
Dec  4 16:46:41 localhost laptop-mode: CONTROL_TERMINAL is disabled, skipping...
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/usb-autosuspend.
Dec  4 16:46:41 localhost laptop-mode: USB autosuspend is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/video-out.
Dec  4 16:46:41 localhost laptop-mode: video-out module is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-ipw-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IPW Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Invoking module /usr/share/laptop-mode-tools/modules/wireless-iwl-power.
Dec  4 16:46:41 localhost laptop-mode: Intel IWL Wireless power setting is disabled.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/lib/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /usr/local/share/laptop-mode-tools/modules/* is not executable.
Dec  4 16:46:41 localhost laptop-mode: Module /etc/laptop-mode/modules/* is not executable.
Dec  4 16:46:41 localhost klogd: usbcore: registered new interface driver snd-usb-audio
Dec  4 16:47:02 localhost net_applet[3786]: ### Program is starting ###
Dec  4 16:47:13 localhost draknetcenter[3873]: ### Program is starting ###
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: modified file /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: changed mode of /etc/sysconfig/network-scripts/ifcfg-wlan0 to 700
Dec  4 16:47:33 localhost draknetcenter[3873]: written wlan0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-wlan0
Dec  4 16:47:33 localhost draknetcenter[3873]: running: /sbin/ifdown wlan0 daemon
Dec  4 16:47:34 localhost ifplugd(wlan0)[2864]: Exiting.
Dec  4 16:47:34 localhost draknetcenter[3873]: running: /sbin/ifup wlan0 daemon
Dec  4 16:47:36 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:36 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:36 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:36 localhost klogd: wlan0: deauthenticating from 00:12:88:4c:aa:a1 by local choice (reason=3)
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec  4 16:47:37 localhost klogd: wlan0: direct probe to AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: direct probe responded
Dec  4 16:47:37 localhost klogd: wlan0: authenticate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: authenticated
Dec  4 16:47:37 localhost klogd: wlan0: associate with AP 00:12:88:4c:aa:a1 (try 1)
Dec  4 16:47:37 localhost klogd: wlan0: RX AssocResp from 00:12:88:4c:aa:a1 (capab=0x431 status=0 aid=1)
Dec  4 16:47:37 localhost klogd: wlan0: associated
Dec  4 16:47:37 localhost klogd: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec  4 16:47:37 localhost klogd: cfg80211: Calling CRDA for country: US
Dec  4 16:47:37 localhost klogd: cfg80211: Current regulatory domain updated by AP to: US
Dec  4 16:47:37 localhost klogd:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:47:37 localhost klogd:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: ifplugd 0.28 initializing.
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using interface wlan0/00:C0:A8:C1:28:70 with driver <rtl8180> (version: 2.6.33.7-pclos6.bfs)
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Using detection mode: SIOCETHTOOL
Dec  4 16:47:37 localhost ifplugd(wlan0)[4103]: Initialization complete, link beat detected.

[Grisen]

Okay, I have a partial resolution, at least that much.

In PCC > boot > advanced, unchecking both apic/lapic and acpi caused the machine to not want to boot into the desktop.  I had lots of struggles at this point in the grub menu to get a configuration where it would boot into X at all.  Eventually, I found this:

Unchecking acpi and leaving apic/lapic made my system tray battery monitor stop working.

Unchecking apic/lapic and leaving acpi solved some other issues that had been a problem.  Hypothetically let's say apic/lapic and acpi loading together took up so much CPU time, that the wifi connection wouldn't start in time most of the time.  (Theorizing from the proximity of laptop lines and wifi lines in the syslog posted before)  Then update-notifier would check for updates, fail to connect, and prompt me to configure wifi, and if I did this before the login music started, it would stutter.  If I waited it would not stutter.  Or if I were connected automatically (occasionally) and started Firefox before the music played, it would stutter.  Then the machine would stutter on all sounds for the session (Amarok, youtube audio, system sounds, etc), and it would refuse gui shutdown commands, forcing me to use keyboard shortcuts.

Now I've rebooted about seven times and wifi doesn't fail to connect on its own.  Update notifier goes and checks for updates without telling me to configure wifi.  System welcome sound is not interrupted by my trying to configure wifi before music has played.  And, I've tried starting Firefox before music has played, and it does not stutter.

It will be a while before I see whether this lappy starts stuttering in the middle of a session, as it did randomly a couple of times over the course of the last couple of days on it.  Maybe that's fixed, too.

*******  I THINK THIS MIGHT BE A BUG FOR THE DEVS TO LOOK AT ********  because my other dual core recent model laptop also has a problem many times with update-notifier checking for updates before the WIFI connection is made, and then there is no automatic wifi and it prompts me to set it up and check for updates. (though no sound issues on that one)

Not knowing much about these packages, why are acpi and apic/lapic both loaded by default at the same time?  There's probably a good reason.  But either that has caused problems on e these laptops-- more severe on one than the other-- or maybe update-notifier is just checking for updates too soon, and not waiting for the WIFI connection.

This is all so   c o m p l i c a t e d     but that's what lack of knowledge will do.  E.g. my hypothesis earlier that there was file corruption.

Anyways muugwana and ff103, things are looking up.  Thank you.  In a couple of days, I'll mark this SOLVED if there are no more sound issues in the middle of a session on the computer.

I do believe the developers need to look at this issue, since it has cropped up in one form or another on two laptops for me.  Do you know how to escalate it to their attention if that is warranted? (I don't).

[muungwana]

The dev team follows most of discussions on most threads, sometimes a thread or two go past them but they catch most of them. The problem with the update-notifier trying to connect before the network is up and running maybe solved by increasing the time it waits before it tries to connect.

Waiting a little bit while giving room for other programs to load up at start up is probably a good thing too it doesnt need to check for updates right after a user log in and a user probably wants to do something else right after log in.

Hope the stuttering problem is gone, the forum is always here if the issue or any other issue show up.

ps:
Long outputs are better be places in "code" tags for easy readability

[Grisen]

Thank you.

Yes, the problem may be update-notifier loading too soon, but why would that be fixed by turning off apic/lapic?  Seems more complex than just update-notifier.  When apic/lapic are on, wireless does not connect automatically most of the time.  Sound was another layer in the cake that's also related, apparently to apic/lapic vs acpi.

Regarding your PS: since the PCLOS forums don't have a pastebin capability (do they??) I didn't know any other way to get the relevant part of the syslog file into the thread.  Would be glad to know about a better way.  Not sure I understand what you mean by "code tags".

[muungwana]

when you are on the edit mode ie when you are writing your post, you see emoticons above the edit area, "code" tag is the third icon from the right just above the emoticons line. The "code" button has a "#" symbol on it

You can just mouse over those icons and a pop up will tell you what they are

The problem may be caused by something tripping when the system is under stress and maybe the log in time causes a lot of system stress and the problem is triggered there. This is just a speculation though, do you need those log in/log out sounds? turning them off could also help

I dont have a laptop so i cant comment on the acpi/lacpi stuff

[Grisen]

Thanks, so the # code button will do what, put the pasted syslog stuff in a file that is separate from the post, and insert a hyperlink to it?  That would be good, if that's how it works.

Actually turning the welcome sound off might not solve the problem.  Once that sound stutters, no sound works (Amarok, youtube videos, etc-- they all stutter) and the machine will not follow gui commands to shut down.  Plus sometimes the stuttering starts in the middle of a session.

I'm working on this laptop for a man who wants to transition from Windows.  It would be great to have a high-functioning PCLOS install to give him.  One more convert to Linux, if things work right.

Thanks for your patience and persistence.  I appreciate it.

I suspect the problem is fixed.  I'll know in a couple of days.