I have similar problem. Error message is: “Started Update UTMP about System Runlevel Changes”
History: I used Apple TV 1 many years, and already updated to XBMC. Yesterday I just updated to OSMC. “OSMC installed successfully”, but on the first run hang on the above quoted error.
Unfortunately I can not access any Log file -unless someone tell me how- but I can upload a screenshot with the error message:
After I try to reinstall to original Apple TV OS 3.02 (later the 3.01 also!) but failed. Actually usb stick was not recognize by Apple TV box. Right away Linux booting, but hang on the above message.
USB stick is bootable → I check it on my MacBook Pro: It show up as bootable device!
Please help me fix the OSMC or reinstall the original Apple TV OS 3.02
Thanks in advance.
Steve
I am using USB stick install. Even two different one tested, so the USB port is working. Now I just take the hd out and try to reinstall ATV1 OS 3.02 to a brand new (empty ATA) drive. NO luck. Under Disk Utility I make two different partition and install OSboot from this omg: 2Z694-6013-013.img
When start it’ll show only the apple logo and yellow light still flashing for. awhile after shut down and start again. This is in the loop.
I still have the original hd, when I try to reinstall OS 3.02 from usb -> failed. Simple ignore the usb drive and goes directly to the linux.
I have a live linux system (Knoppix 8.1) so I can see what is on the smaller partition, but I do not know how to replace and what in order to get back Apple TV1 original rescue partition.
Please help.
Thanks.
Steve
Sticks: One is 8 GB another is 32GB. I think I need an original RESCUE partition image for my Apple TV1. If you have one pls. let me know. Even a working OSMC version would be fine for me.
Thanks.
Steve
Yes! I understand, I do not need IF, IF… cosmic is working, but after “cosmic installed successfully” first start hang on to “Started Update UTMP about System Runlevel Changes.”
Do you have a working osmc on your ATV1?? Could you make an image from the recovery partition?
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Thank you very much for your help. Now I made TWO hd with ATV1 OS 3.02 So, question is: Do I have to upgrade at first to the XMBC (ATV Flash) or can I go right away to OSMC.
BTW are you sure your osmc is working on ATV 1???
If someone wants to restore ATV 1 to original partition hd, here is the link:
Finally I restore my ATV 1 to the original OS 3.02. Now I can start from scratch install OSMC. I download latest osmc (2017/08/01 hdd) to my 8GB SD card. Installation was smooth “OSMC installed successfully” Reboot without usb stick ATV went back to OS 3.02. At least this osmc version does not destroy the original software.
Second reboot linux boot message went quite fast and after a blue screen with OSMC logo appeared for a while (maybe 20 sec) after disappeared and several reboot attempt (automatically) but nothing on the screen. Not even the sad face came up.
On the usb stick I found an install.log file. Here it is:
Tue Dec 26 20:19:49 2017 Starting OSMC installer
Tue Dec 26 20:19:54 2017 Detecting device we are running on
Tue Dec 26 20:19:54 2017 Mounting boot filesystem
Tue Dec 26 20:19:54 2017 Trying to mount to MNT_BOOT (/mnt/boot)
Tue Dec 26 20:19:54 2017 Using device->boot: /dev/sdb1 and FS: hfsplus
Tue Dec 26 20:19:54 2017 No preseed file was found
Tue Dec 26 20:19:54 2017 Creating root partition
Tue Dec 26 20:19:54 2017 From a root partition of /dev/sdb2, I have deduced a base device of /dev/sdb
Tue Dec 26 20:19:54 2017 Determined 256 MB as end of first partition
Tue Dec 26 20:19:54 2017 Calling mkpart for device: /dev/sdb and fs: ext4 with start 258M and end 100%
Tue Dec 26 20:19:57 2017 Calling fmtpart for partition /dev/sdb2 and fstype ext4
Tue Dec 26 20:20:05 2017 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
478608 inodes, 1911040 blocks
95552 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1958739968
59 block groups
32768 blocks per group, 32768 fragments per group
8112 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Thank you very much for your hint. Actually I went to my other TV and right away finished install KODI. So the display resolution was TOO high for this 15 years old 50" Sony Wega. Which is easily handle the Apple TV and another media player box with KODI on it.
Now I have only problem with the sound. Not when I connect ATV1 to a 2017 Samsung TV but when I get back to the Sony, I see nice picture, but no sound.
I went to KODI settings and try to change the audio decoder, but still no sound.
I try to figure out why the original ATV1 Os is working so flawless, and why the android based other media box with KODI has no audio problem at all on the same old SONY TV.
Any advice what and where should I change?
Thanks again:
Steve
You probably need to configure the audio settings accordingly. Disable passthrough if directly connected to a TV.
You can manually adjust the resolution to 720p, via Xorg.conf. Your TV probably only supports 1080i, not 1080p. Your EDID on your TV should report this however, but some older TVs had invalid (for their true capabilities) EDIDs.
I am really sorry about the log file. I would be very happy if I could reach my Apple TV (or even KODI) from my MacBook Pro with ssh. I do not know how.
Install.log was on the usb stick and I went to my live Knoppix linux to read/copy this files.
Do you think Kodi log files are on the same place?
BTW. Now I setup the audio HDMI default and it is working perfectly. So now I have no complains any more.
Thanks:
Steve
