Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 34
[LINUX] Problems compiling crystalhd branch
#76
I used the guides on the atv-bootloader site put together by davilla.

I used a replacement drive and only wanted linux on it so I followed this.
http://code.google.com/p/atv-bootloader/...oningLinux

Then the netboot portion of this. http://code.google.com/p/atv-bootloader/...tingLiveCD

You can use the http://code.google.com/p/atvusb-creator/ to make the bootable flash (Make ATV-Bootloader, not the ATV-Patchstick) drive then put the ubuntu netboot stuff on the big partition on that. The guides may not be exact if you follow this since the partition numbers won't match, but they should give you the gist and save doing the process twice.

There is no straight up guide out there for doing this, and I don't want to try to mimick the process again Smile, but I found enough information on here and on different sections of that bootloader site to get the job done.

Also since you're throwing 8.04 on there, this might be useful to get everything else working. http://code.google.com/p/atv-bootloader/...buntuHardy
Reply
#77
I actually did all of that, and ran into the issues that I had...

Maybe a more basic question would be what have others installed during the netboot/install process?

Almost everything I've been reading suggests that I should basically setup a mythbuntu box, is that the idea?

(I think that because I'm a server admin (unix/linux), rather than a desktop linux guy, I'm "getting in my own way")
Reply
#78
Davilla,

I'm not sure how much input you're looking for on this stuff since it's under heavy development, but I figure I'll let you know what issues I'm having after using this for a few evenings.

Some videos (http://dan1son.net/1.info http://dan1son.net/2.info) playback with the video smashed on the top half of the screen and the bottom half is green. The playback is also oddly choppy.

Also every video I've tried (except raw mpeg2 dvd rips [those appear to have an interlace problem if left on "auto-select"]) seem to have a frame skip or double frame every so often (every several seconds, looks like a slight jerk). This happens more often on scene changes (when whole frame is new). I'm a picky bastard so it's not impossible others won't see this. This even happens on H.264 dvd rips. It's just not quite smooooooooth as butta.

The large blockiness and/or lines going down the screen (you already said you know about these) happens more often on some media, less often on others, but consistently.

Sometimes it appears to get wonky (blocky and/or jumpy) after seeking, pausing, etc. Another seek or pause usually clears it up.

Other than that, it's remarkably stable and amazing to see that little box doing 1080p/24 over wi-fi. It'll play whatever I throw at it... just amazing.
Reply
#79
dan1son Wrote:Davilla,

I'm not sure how much input you're looking for on this stuff since it's under heavy development, but I figure I'll let you know what issues I'm having after using this for a few evenings.

1) Some videos (http://dan1son.net/1.info http://dan1son.net/2.info) playback with the video smashed on the top half of the screen and the bottom half is green. The playback is also oddly choppy.

2) Also every video I've tried (except raw mpeg2 dvd rips [those appear to have an interlace problem if left on "auto-select"]) seem to have a frame skip or double frame every so often (every several seconds, looks like a slight jerk). This happens more often on scene changes (when whole frame is new). I'm a picky bastard so it's not impossible others won't see this. This even happens on H.264 dvd rips. It's just not quite smooooooooth as butta.

3) The large blockiness and/or lines going down the screen (you already said you know about these) happens more often on some media, less often on others, but consistently.

4) Sometimes it appears to get wonky (blocky and/or jumpy) after seeking, pausing, etc. Another seek or pause usually clears it up.

1) deinterlacing is not being handled correctly.

2) related to 3)

3) related to the hack we are doing right now.

4) the crystalhd driver also decodes "metadata" and this gets dumped. sometimes there's a freeze up when this gets dumped and all hell breaks out, then it recovers. Not sure why. If you watch the console output you will see this happen.
Reply
#80
davilla Wrote:1) deinterlacing is not being handled correctly.

2) related to 3)

3) related to the hack we are doing right now.

4) the crystalhd driver also decodes "metadata" and this gets dumped. sometimes there's a freeze up when this gets dumped and all hell breaks out, then it recovers. Not sure why. If you watch the console output you will see this happen.

Sounds good, thanks... just making sure you know and, as usual, you already do.
Reply
#81
Just an FYI, to set the frequency of the cpu as davilla suggested, you must first install cpufrequtils:

Code:
sudo apt-get install cpufrequtils
then

Code:
sudo cpufreq-set -d 1000MHz -u 1000MHz
That was probably self explanatory for 90% of the people in this thread. This post is for the other 10% Smile
Reply
#82
Another mini-guide for the newbies like myself, this one gets your ATV's front led back to it's good ole white self:
Code:
sudo apt-get install libusb-dev libusb-0.1-4

If no errors appear then download, extract and compile atvtool:
Code:
sudo wget http://peter.korsgaard.com/atv/atvtool-0.2.tar.gz
sudo tar xvf atvtool-0.2.tar.gz
sudo cd atvtool-0.2/
sudo ./configure
sudo make install

Then create a shell script in /etc/init.d/ named atvled:
Code:
#!/bin/sh -e

/usr/local/sbin/atvtool -l 3

esac

exit 0

chmod 755 and +x it, then register it for executing upon bootup with the following code:

Code:
sudo update-rc.d atvled defaults
Reboot, now your led should turn solid white automatically when ubuntu is loaded.

Enjoy!
Reply
#83
It also breaks lircd Smile
Reply
#84
I followed the guides in this thread and got Ubuntu and my own compile of XBMC running on my ATV. However, I am not getting any sound -- neither in Ubuntu or XBMC. Do I have to follow (this guide) to make it work, or is that not required for 8.04?

Also, is the Nvidia driver update described here necessary/recommended?

The reason I am asking is that Cake mentions neither of these in his guide.

/ Thanks in advance, Poul
Reply
#85
pouldam Wrote:I followed the guides in this thread and got Ubuntu and my own compile of XBMC running on my ATV. However, I am not getting any sound -- neither in Ubuntu or XBMC. Do I have to follow (this guide) to make it work, or is that not required for 8.04?

Also, is the Nvidia driver update described here necessary/recommended?

The reason I am asking is that Cake mentions neither of these in his guide.

/ Thanks in advance, Poul

Forgot to mention that I did add "options snd-hda-intel model=imac24" to "/etc/modprobe.d/options" as described here.

However, I now realize that I have not run the alsamixer as mentioned on that link (is that just the default audio device mixer in Ubuntu?), so that may be the reason for the missing audio...
Reply
#86
pouldam Wrote:Forgot to mention that I did add "options snd-hda-intel model=imac24" to "/etc/modprobe.d/options" as described here.

I did that as well to get sound and unmuted the IEC958 port in alsamixer or any GUI mixer. The IEC958 is the optical out (not sure on HDMI, but I'd imagine it's the same one). With those settings and telling XBMC to use digital out and IEC958 I get full DTS/DD 5.1 and stereo for music as expected.

The PostMythbuntuHardy post up there has the information that should work for ubuntu 8.04 as well since it's basically the same install.
Reply
#87
How does one get the Apple Remote to "attach" the XBMC App?

I've got the remote working with irw/lirc, but there are no options under settings|system|input devices other than:

Remote control sends keyboard presses
Enable Mouse

A little help...

Thanks
Reply
#88
Philmatic Wrote:Another mini-guide for the newbies like myself, this one gets your ATV's front led back to it's good ole white self:
Code:
sudo apt-get install libusb-dev libusb-0.1-4

If no errors appear then download, extract and compile atvtool:
Code:
sudo wget http://peter.korsgaard.com/atv/atvtool-0.2.tar.gz
sudo tar xvf atvtool-0.2.tar.gz
sudo cd atvtool-0.2/
sudo ./configure
sudo make install

Then create a shell script in /etc/init.d/ named atvled:
Code:
#!/bin/sh -e

/usr/local/sbin/atvtool -l 3

esac

exit 0

chmod 755 and +x it, then register it for executing upon bootup with the following code:

Code:
sudo update-rc.d atvled defaults
Reboot, now your led should turn solid white automatically when ubuntu is loaded.

Enjoy!

Use the --reattach argument on atvtool to give back the IR receiver to
hiddev.
Reply
#89
davilla Wrote:Use the --reattach argument on atvtool to give back the IR receiver to
hiddev.

You'll need to restart lirc after doing that, if it was already started. I'm not familiar with Debian init scripts, but if you could make the lirc init script depend on atvled, atvled would run first and all should be well.
Reply
#90
next version of atv-bootloader (don't ask when Smile will have atvtool inside and preset the LED to white before running kexec.
Reply
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 34

Logout Mark Read Team Forum Stats Members Help
[LINUX] Problems compiling crystalhd branch2