SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi. I have little problem. When I have xmms running and playing if I do something wich requires the hdd to work a little bit more (mostly when I copy large files and directories or I download something with Linux DC++ at a high speed) my music suddenly stops and I have to push the play button again. This may look like a little thing but I think something is wrong, with my hdd with my installation, I don't know what but would really like to find out. Please ask any info you need to check for my hardware or software and I'll post as fast as I can. Thanks alot.
Ok so I did a little bit of testing and used amarok now as a player and copied the whole slackware-current dir from /root to /home/nykey wich would be enough for xmms to stop playing, but amarok didn't stop. That means the issue is in xmms... but still I would like to keep xmms as my player, so what should I do ?
It has to be a priority setting under xmms. Look under the mp3 driver, or somewhere under the xmms preference settings, and see if you can change the priority playback, from realtime to a lower one, that might help under xmms. Amarok should have the same settings, but probably handles realtime playback better than xmms, since xmms is dated.
I've searched xmms settings and the only thing I could find was Use real time priority wich was's checked so it wasn't using realtime.
And for second question:
Code:
root@nykey:~# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 1676 MB in 2.00 seconds = 838.00 MB/sec
Timing buffered disk reads: 170 MB in 3.03 seconds = 56.11 MB/sec
root@nykey:~# hdparm -tT /dev/hdd
/dev/hdd:
Timing cached reads: 1696 MB in 2.00 seconds = 848.00 MB/sec
Timing buffered disk reads: 164 MB in 3.02 seconds = 54.30 MB/sec
root@nykey:~#
and even more info:
Code:
root@nykey:~# hdparm -iI /dev/hda
/dev/hda:
Model=WDC WD800JB-00JJC0, FwRev=05.01C05, SerialNo=WD-WCAM95146812
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=66
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version:
* signifies the current active mode
ATA device, with non-removable media
Model Number: WDC WD800JB-00JJC0
Serial Number: WD-WCAM95146812
Firmware Revision: 05.01C05
Standards:
Supported: 6 5 4 3
Likely used: 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 66 Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* Automatic Acoustic Management feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
root@nykey:~# hdparm -iI /dev/hdd
/dev/hdd:
Model=ST380011A, FwRev=3.06, SerialNo=3JV3V3J7
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
* signifies the current active mode
ATA device, with non-removable media
Model Number: ST380011A
Serial Number: 3JV3V3J7
Firmware Revision: 3.06
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4 3
Configuration:
Logical max current
cylinders 16383 65535
heads 16 1
sectors/track 63 63
--
CHS current addressable sectors: 4128705
LBA user addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Standard
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 128, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* SMART self-test
* SMART error logging
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1 determined by CSEL
Checksum: correct
root@nykey:~#
I have the same XMMS problem, at least it sounds like it. In Fedora Core 6 though. Whenever some things are installed (not all) it'll stop, it won't pause.. it still displays the play icon. So I have to pause and then play to continue from the same place, Maybe trying out real-time could be an option, I'm trying it, but it isn't recommended. In real-time the songs keep stopping but starting again automatically.. jumping but I'm not really doing anything with the processor or hard drive and so I don't think it is helping. You could try out real player which comes with things like MP3 playback with it or Amarok.. even Kaffeine player.. it's just a shame because xmms has some great features.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.