Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
 Linux voyage 3.14.12-voyage-rt-rt9 #1 SMP PREEMPT RT Fri Apr 17 15:10:46 HKT 2015 i686 GNU/Linux

USB DAC turned on and connected

dmesg
[  283.995809] usb 5-8: USB disconnect, device number 4
[  294.335129] usb 5-8: new high-speed USB device number 5 using ehci-pci
[  294.450184] usb 5-8: New USB device found, idVendor=20b1, idProduct=000a
[  294.450871] usb 5-8: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[  294.451628] usb 5-8: Product: xCORE USB Audio 2.0
[  294.452135] usb 5-8: Manufacturer: XMOS
[  294.453256] cannot find the slot for index 0 (range 0-0), error: -16
[  294.453918] cannot create card instance 0
[  294.454456] snd-usb-audio: probe of 5-8:1.0 failed with error -5

Only my internal audio device is recognized

aplay -l
root@voyage:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC9228 Analog [STAC9228 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

I thought this thread might help

http://voyage-linux.34677.n3.nabble.com/voyage-mpd-0-10-0-does-not-recognize-Combo384-td4026314.html#a4026316

I removed the line options snd-usb-audio index=0 from /etc/modprobe.d/alsa-base.conf. Now I get

aplay -l
root@voyage:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC9228 Analog [STAC9228 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: x20 [xCORE USB Audio 2.0], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

So the device is recognized, BUT there's still no audio playing through it. I've tried to use alsamixer and F6 to set the sound card device to xCore USB, but still no audio is playing through it.

I've also tried to change the line in /etc/modprobe.d/alsa-base.conf to options snd-usb-audio index=1, but the result is exactly the same.

Any help is appreciated.

Cheers



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

chris hermansen

Good day,

On Dec 23, 2015 16:06, "z0rk" <[hidden email]> wrote:
>
>  Linux voyage 3.14.12-voyage-rt-rt9 #1 SMP PREEMPT RT Fri Apr 17 15:10:46 HKT
> 2015 i686 GNU/Linux
>
> USB DAC turned on and connected
>
> dmesg
> [  283.995809] usb 5-8: USB disconnect, device number 4
> [  294.335129] usb 5-8: new high-speed USB device number 5 using ehci-pci
> [  294.450184] usb 5-8: New USB device found, idVendor=20b1, idProduct=000a
> [  294.450871] usb 5-8: New USB device strings: Mfr=1, Product=3,
> SerialNumber=0
> [  294.451628] usb 5-8: Product: xCORE USB Audio 2.0
> [  294.452135] usb 5-8: Manufacturer: XMOS
> [  294.453256] cannot find the slot for index 0 (range 0-0), error: -16
> [  294.453918] cannot create card instance 0
> [  294.454456] snd-usb-audio: probe of 5-8:1.0 failed with error -5
>
> Only my internal audio device is recognized
>
> aplay -l
> root@voyage:~# aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC9228 Analog [STAC9228 Analog]
>   Subdevices: 0/1
>   Subdevice #0: subdevice #0
>
> I thought this thread might help
>
> http://voyage-linux.34677.n3.nabble.com/voyage-mpd-0-10-0-does-not-recognize-Combo384-td4026314.html#a4026316
>
> I removed the line options snd-usb-audio index=0 from
> /etc/modprobe.d/alsa-base.conf. Now I get
>
> aplay -l
> root@voyage:~# aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC9228 Analog [STAC9228 Analog]
>   Subdevices: 0/1
>   Subdevice #0: subdevice #0
> card 1: x20 [xCORE USB Audio 2.0], device 0: USB Audio [USB Audio]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> So the device is recognized, BUT there's still no audio playing through it.
> I've tried to use alsamixer and F6 to set the sound card device to xCore
> USB, but still no audio is playing through it.
>
> I've also tried to change the line in /etc/modprobe.d/alsa-base.conf to
> options snd-usb-audio index=1, but the result is exactly the same.
>
> Any help is appreciated.

Two suggestions.

The 3.14 kernel is pretty old. Can you try this on a newer kernel, for example on a desktop or laptop running a 4.x kernel? Maybe the latest Ubuntu or Fedora live CD?

Then, if that doesn't work, try the ALSA user mailing list [hidden email] (you have to subscribe)


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
Hey, thanks for your suggestions. The device works on OpenELEC, but I want to use it on Voyage-MPD; and I am running the latest version. So, if the kernel is too old to support my device than Voyage-MPD is no good to me.
I guess I'll have to post to the ALSA mailing list.

Cheers
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

Kim-man 'Punky' TSE-2
In reply to this post by z0rk
On 12/24/2015 8:00 AM, z0rk wrote:

> aplay -l
> root@voyage:~# aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC9228 Analog [STAC9228 Analog]
>    Subdevices: 0/1
>    Subdevice #0: subdevice #0
> card 1: x20 [xCORE USB Audio 2.0], device 0: USB Audio [USB Audio]
>    Subdevices: 1/1
>    Subdevice #0: subdevice #0
>
> I've also tried to change the line in /etc/modprobe.d/alsa-base.conf to
> options snd-usb-audio index=1, but the result is exactly the same.
This is known.  Try set "options snd-usb-audio index=-1" in /etc/modprobe.d/alsa-base.conf and reboot.

Check with amixer (not alsamixer) to see if it is mute:

root@voyage:~# amixer
Simple mixer control 'XMOS Clock Selector',0
   Capabilities: pvolume pswitch
   Playback channels: Front Left - Front Right
   Limits: Playback 0 - 127
   Mono:
   Front Left: Playback 64 [50%] [-63.00dB] [on]
   Front Right: Playback 64 [50%] [-63.00dB] [on]
Simple mixer control 'XMOS Clock Selector',1
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined
   Playback channels: Mono
   Limits: Playback 0 - 127
   Mono: Playback 127 [100%] [0.00dB] [on]

Some settings is set to [off], then probably muted.

--
Regards,
Kim-man "Punky" Tse

* Open Source Embedded Solutions and Systems
   - Voyage Linux (http://linux.voyage.hk)
   - Voyage MPD   (http://linux.voyage.hk/voyage-mpd)
   - Voyage MuBox (http://mubox.voyage.hk)
* Voyage Store   (http://store.voyage.hk)


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
/etc/modprobe.d/alsa-base.conf is set to options snd-usb-audio index=1

There's no entry for XMOS

amixer
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 127
  Mono: Playback 102 [80%] [-18.75dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 127
  Mono:
  Front Left: Playback 89 [70%] [-28.50dB] [on]
  Front Right: Playback 89 [70%] [-28.50dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 127
  Mono:
  Front Left: Playback 102 [80%] [-18.75dB] [on]
  Front Right: Playback 102 [80%] [-18.75dB] [on]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 4
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 14
  Front Left: Capture 8 [57%] [12.00dB] [on]
  Front Right: Capture 8 [57%] [12.00dB] [on]
Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Speaker Only' 'Line Out+Speaker'
  Item0: 'Line Out+Speaker'

Thanks Punky
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

Kim-man 'Punky' TSE-2
I mean index=-1 , not index=1

Or use aplay to specify the card# to play some sample .wav file.

On 12/24/2015 10:27 AM, z0rk wrote:

> /etc/modprobe.d/alsa-base.conf is set to options snd-usb-audio index=1
>
> There's no entry for XMOS
>
> amixer
> Simple mixer control 'Master',0
>    Capabilities: pvolume pvolume-joined pswitch pswitch-joined
>    Playback channels: Mono
>    Limits: Playback 0 - 127
>    Mono: Playback 102 [80%] [-18.75dB] [on]
> Simple mixer control 'Headphone',0
>    Capabilities: pvolume pswitch
>    Playback channels: Front Left - Front Right
>    Limits: Playback 0 - 127
>    Mono:
>    Front Left: Playback 89 [70%] [-28.50dB] [on]
>    Front Right: Playback 89 [70%] [-28.50dB] [on]
> Simple mixer control 'PCM',0
>    Capabilities: pvolume pswitch
>    Playback channels: Front Left - Front Right
>    Limits: Playback 0 - 127
>    Mono:
>    Front Left: Playback 102 [80%] [-18.75dB] [on]
>    Front Right: Playback 102 [80%] [-18.75dB] [on]
> Simple mixer control 'Mic Boost',0
>    Capabilities: volume
>    Playback channels: Front Left - Front Right
>    Capture channels: Front Left - Front Right
>    Limits: 0 - 4
>    Front Left: 0 [0%] [0.00dB]
>    Front Right: 0 [0%] [0.00dB]
> Simple mixer control 'Capture',0
>    Capabilities: cvolume cswitch
>    Capture channels: Front Left - Front Right
>    Limits: Capture 0 - 14
>    Front Left: Capture 8 [57%] [12.00dB] [on]
>    Front Right: Capture 8 [57%] [12.00dB] [on]
> Simple mixer control 'Auto-Mute Mode',0
>    Capabilities: enum
>    Items: 'Disabled' 'Speaker Only' 'Line Out+Speaker'
>    Item0: 'Line Out+Speaker'
>
> Thanks Punky
>
>
>
>
> --
> View this message in context: http://voyage-linux.34677.n3.nabble.com/Voyage-MPD-snd-usb-audio-probe-of-5-8-1-0-failed-with-error-5-tp4026433p4026437.html
> Sent from the Voyage Linux mailing list archive at Nabble.com.
>
> _______________________________________________
> Voyage-linux mailing list
> [hidden email]
> http://list.voyage.hk/mailman/listinfo/voyage-linux


--
Regards,
Kim-man "Punky" Tse

* Open Source Embedded Solutions and Systems
   - Voyage Linux (http://linux.voyage.hk)
   - Voyage MPD   (http://linux.voyage.hk/voyage-mpd)
   - Voyage MuBox (http://mubox.voyage.hk)
* Voyage Store   (http://store.voyage.hk)


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
This post has NOT been accepted by the mailing list yet.
Ok, gotcha. I changed 1 to -1 and rebooted and I am getting exactly the same results. But I did

aplay -vv -Ddefault:1 .flac

to play back a FLAC file and now the card plays back audio, but it's all white noise.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
In reply to this post by Kim-man 'Punky' TSE-2
I used a WAV instead and it worked!

aplay -vv -Ddefault:1 .wav

Where do I take it from here?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
In reply to this post by Kim-man 'Punky' TSE-2
The following fix worked for me

options snd cards_limit=1
options snd-usb-audio id=x20 index=-1
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Hangs voyage 0.10.0

Volodymyr
Hello list!

voyage-0.10.0
Thin Client  - Wyse V90
CPU: VIA C3 (C5XL - VIA Nehemiah)
RAM: 256
http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml

Such problem: The client periodically (once a week) hangs.
Logs are maintained. However, information about the problems of hang-up in the log is not saved.

Why is there no information in the logs, on the causes of hangs?
How is it possible to determine the cause of the hang-up?

Best regards
Volodymyr

_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hangs voyage 0.10.0

chris hermansen

Volodymyr and list,

On Dec 24, 2015 09:07, "Volodymyr" <[hidden email]> wrote:
>
> Hello list!
>
> voyage-0.10.0
> Thin Client  - Wyse V90
> CPU: VIA C3 (C5XL - VIA Nehemiah)
> RAM: 256
> http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml
>
> Such problem: The client periodically (once a week) hangs.
> Logs are maintained. However, information about the problems of hang-up in the log is not saved.
>
> Why is there no information in the logs, on the causes of hangs?
> How is it possible to determine the cause of the hang-up?
>
> Best regards
> Volodymyr

Is there a crontab entry whose timing corresponds to the hang-up? If so you should check to see if it might be the cause.


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hangs voyage 0.10.0

Volodymyr
От кого: "chris hermansen" <[hidden email]>
Дата: 24 декабря 2015, 19:11:18

Volodymyr and list,

On Dec 24, 2015 09:07, "Volodymyr" <[hidden email]> wrote:
>
> Hello list!
>
> voyage-0.10.0
> Thin Client  - Wyse V90
> CPU: VIA C3 (C5XL - VIA Nehemiah)
> RAM: 256
> http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml
>
> Such problem: The client periodically (once a week) hangs.
> Logs are maintained. However, information about the problems of hang-up in the log is not saved.
>
> Why is there no information in the logs, on the causes of hangs?
> How is it possible to determine the cause of the hang-up?
>
> Best regards
> Volodymyr

Is there a crontab entry whose timing corresponds to the hang-up? If so you should check to see if it might be the cause.


Hello Chris,


The client, every day, is switched on via Bios at 7 am.
Is switched off via Cron at 12 pm.
All this time the logs are written wonderful.
The logs are not written information from the launch to hang-up.




_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hangs voyage 0.10.0

chris hermansen

Volodymyr and list,

On Dec 24, 2015 10:00, "Volodymyr" <[hidden email]> wrote:
>
> От кого: "chris hermansen" <[hidden email]>
> Дата: 24 декабря 2015, 19:11:18
>
>> Volodymyr and list,
>>
>> On Dec 24, 2015 09:07, "Volodymyr" <[hidden email]> wrote:
>> >
>> > Hello list!
>> >
>> > voyage-0.10.0
>> > Thin Client  - Wyse V90
>> > CPU: VIA C3 (C5XL - VIA Nehemiah)
>> > RAM: 256
>> > http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml
>> >
>> > Such problem: The client periodically (once a week) hangs.
>> > Logs are maintained. However, information about the problems of hang-up in the log is not saved.
>> >
>> > Why is there no information in the logs, on the causes of hangs?
>> > How is it possible to determine the cause of the hang-up?
>> >
>> > Best regards
>> > Volodymyr
>>
>> Is there a crontab entry whose timing corresponds to the hang-up? If so you should check to see if it might be the cause.
>
>
> Hello Chris,
>
>
> The client, every day, is switched on via Bios at 7 am.
> Is switched off via Cron at 12 pm.
> All this time the logs are written wonderful.
> The logs are not written information from the launch to hang-up.

OK so to confirm that I understand correctly:

6 days per week the computer starts up, writes its log files, and shuts down correctly.

1 day per week the computer starts up, does not appear to write its log files, and hangs up.

Is that correct?

If so, have you examined the log files on "the bad day" while the computer is running?

Are you running the computer with a read-only root and using /tmp for storing /var while running? And expecting the shutdown process to copy the files in /tmp back to /var? If so, that may be why your files appear not to be written - because they are not copied back on shutdown.


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hangs voyage 0.10.0

Volodymyr
 

--- Исходное сообщение ---
От кого: "chris hermansen" <[hidden email]>
Дата: 24 декабря 2015, 21:22:20

Volodymyr and list,

On Dec 24, 2015 10:00, "Volodymyr" <[hidden email]> wrote:
>
> От кого: "chris hermansen" <[hidden email]>
> Дата: 24 декабря 2015, 19:11:18
>
>> Volodymyr and list,
>>
>> On Dec 24, 2015 09:07, "Volodymyr" <[hidden email]> wrote:
>> >
>> > Hello list!
>> >
>> > voyage-0.10.0
>> > Thin Client  - Wyse V90
>> > CPU: VIA C3 (C5XL - VIA Nehemiah)
>> > RAM: 256
>> > http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml
>> >
>> > Such problem: The client periodically (once a week) hangs.
>> > Logs are maintained. However, information about the problems of hang-up in the log is not saved.
>> >
>> > Why is there no information in the logs, on the causes of hangs?
>> > How is it possible to determine the cause of the hang-up?
>> >
>> > Best regards
>> > Volodymyr
>>
>> Is there a crontab entry whose timing corresponds to the hang-up? If so you should check to see if it might be the cause.
>
>
> Hello Chris,
>
>
> The client, every day, is switched on via Bios at 7 am.
> Is switched off via Cron at 12 pm.
> All this time the logs are written wonderful.
> The logs are not written information from the launch to hang-up.

OK so to confirm that I understand correctly:

6 days per week the computer starts up, writes its log files, and shuts down correctly.

1 day per week the computer starts up, does not appear to write its log files, and hangs up.

Is that correct?


Yes. Approximately once a week. With various periodicities.


If so, have you examined the log files on "the bad day" while the computer is running?

He is not saved them in /var/log, at the time of crash.



Are you running the computer with a read-only root and using /tmp for storing /var while running?

Yes. :)


And expecting the shutdown process to copy the files in /tmp back to /var? If so, that may be why your files appear not to be written - because they are not copied back on shutdown.

Thank you Chris! It seems so. :))
Now, I'll wait for the new crash, see the information in /tmp/var/log.

/tmp/var/log/kern.log - No information: from the "Dec 19 7:00:00" at "Dec 19 17:46:46". :

Dec 18 23:59:09 localhost vmunix: [64732.092133] Ebtables v2.0 unregistered
Dec 19 17:46:47 localhost vmunix: [    0.114706] ACPI: bus type PNP unregistered


Unfortunately, I still know very little about the difference between Debian and Voyage.  smile-3



!
_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Voyage-MPD; snd-usb-audio: probe of 5-8:1.0 failed with error -5

z0rk
In reply to this post by z0rk
The problem is back again. I switched the external USB DAC to a different model and everything worked. Then I switched back again to the original setup and it broke again.
It appears there are some setting in Voyage-MPD that persist between reboot / shutdowns.

Any advice?

Thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hangs voyage 0.10.0

Volodymyr
In reply to this post by chris hermansen
Hello,


Today,
system hangs again.
smile-3

What must be done to voyage-0.10.0, permanently saves all the logs here - "/var/log" ?
Not waiting shutdown.
Thanks.

Volodymyr



--- Исходное сообщение ---
От кого: "chris hermansen" <[hidden email]>
Дата: 24 декабря 2015, 21:22:20

Volodymyr and list,

On Dec 24, 2015 10:00, "Volodymyr" <[hidden email]> wrote:
>
> От кого: "chris hermansen" <[hidden email]>
> Дата: 24 декабря 2015, 19:11:18
>
>> Volodymyr and list,
>>
>> On Dec 24, 2015 09:07, "Volodymyr" <[hidden email]> wrote:
>> >
>> > Hello list!
>> >
>> > voyage-0.10.0
>> > Thin Client  - Wyse V90
>> > CPU: VIA C3 (C5XL - VIA Nehemiah)
>> > RAM: 256
>> > http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90.shtml
>> >
>> > Such problem: The client periodically (once a week) hangs.
>> > Logs are maintained. However, information about the problems of hang-up in the log is not saved.
>> >
>> > Why is there no information in the logs, on the causes of hangs?
>> > How is it possible to determine the cause of the hang-up?
>> >
>> > Best regards
>> > Volodymyr
>>
>> Is there a crontab entry whose timing corresponds to the hang-up? If so you should check to see if it might be the cause.
>
>
> Hello Chris,
>
>
> The client, every day, is switched on via Bios at 7 am.
> Is switched off via Cron at 12 pm.
> All this time the logs are written wonderful.
> The logs are not written information from the launch to hang-up.

OK so to confirm that I understand correctly:

6 days per week the computer starts up, writes its log files, and shuts down correctly.

1 day per week the computer starts up, does not appear to write its log files, and hangs up.

Is that correct?

If so, have you examined the log files on "the bad day" while the computer is running?

Are you running the computer with a read-only root and using /tmp for storing /var while running? And expecting the shutdown process to copy the files in /tmp back to /var? If so, that may be why your files appear not to be written - because they are not copied back on shutdown.


_______________________________________________
Voyage-linux mailing list
[hidden email]
http://list.voyage.hk/mailman/listinfo/voyage-linux
Loading...