sety wrote:I just don't know where this media change error is coming from.
sety wrote:Hi. Sorry to bother you with this. I've tried to figure it out but I can't work out what's going on. Ever since I MiNT 1.16 I've been finding that my init process is being interrupted by error -13, which I believe means a media change. I've been able to live with it because I can just start init from the shell and it continues to boot, but it's starting to drive me nuts because I can't do an unattended boot.
sety wrote:I've attached my mint.cnf and /etc/ttytab as requested (with comments stripped) I've also put in some more info; the absolute path to my MiNT kernel loader and a list of running processes.
sety wrote:The processes are interesting. init is supposed to be PID 1. I understand why "shell" is PID 1, because I started init from the shell, so I'd expect init to be PID 2, but PID 2 is something called "update". What on Earth is that??
Faucon2001 wrote:Add the full path in your ttytab : u:/c/mint .... instead of /c/mint and check that you have tabs and not spaces before and after vt52
If it doesn't fix it, it would be interesting to see the full mint.cnf and your xaaes.cnf
joska wrote:No, it's not working. You're just crashing something else. It may appear to be working, but it will get you into trouble.
Users browsing this forum: No registered users and 0 guests