Raspberry Pi ROM 2nd Jan 14 not booting

Hi,

I have tried to upgrade my Pi ROm image from the one dated 8th Dec 13 to todays along wih the updated HardDisc image, both 2nd Jan 14, and my Pi will not now boot. All I got was a blank screen with no output of anything like the modules initialisation listing.

Returning to 8th Dec ROM allows the Pi to load back up.

Do I need to update any of the other files with this update or is it a faulty ROM image?

The latest ROM boots OK for me. Perhaps have another go at writing it to the card?

Hi Jeffrey

Tried it again and still the same and also tried a re-download from the website with the same issue.

The actual set up is a CJE LaPi and I have a CJE RTC and backup cell fitted.

Bootcode/Start and Fixup are all dated as 9th July 13 and I think were installed with RC11 and I have not updated those on any previous ROM updates I have done.

Doug, I had the exact same issue as you with the Attrix Lapdock,
I had to edit the config/txt file, and add the following at the top;

disable_overscan=0
overscan_left=1
overscan_right=1
overscan_top=1
overscan_bottom=1

Hi Rob

Changed disable_overscan from 1 to 0 and added in the other lines in my CONFIG/TXT file and I can confirm that the LaPi now boots with the 2nd Jan ROM.

Thanks for the tip though not critical it would be good to know why doesn’t the disable_overscan=1 option work now?

I have hdmi_driver and hdmi_group set to 2 and hdmi_mode =86 with hdmi_force_edid_audio=1.

So Normal HDMI mode and DMT set with all audio formats supported even when not reported as such.

Once again the RISC OS community comes up with the goods.

Glad it worked!

It was after the GraphicsV changes made on the 15-Dec-2013 that I had this issue.
It may be limited to the Attrix Lapdock, as I know someone else has had the same issue on their Lapdock.

I’m not sure why my GraphicsV changes will be having that effect. I’ll double-check my changes and see if I can spot anything that I’ve broken.

Thanks Jeffrey!
If you need anything testing on a Lapdock, feel free to give me a shout.

Out of interest, is it time to revisit the default config.txt file that comes with RISC OS Pi (and NOOBS)? What’s the feeling here?

Edit: moved to this topic.

I think I’ve fixed this now, so if anyone who’s having problems could try again tomorrow once the ROMs have been rebuilt then that would be great. Basically I messed up when removing some obsolete code, resulting in the first mode change request which gets sent to the GPU being utter garbage. If this doesn’t fix it then I’ll have to upload some builds for people to test with, because I can’t seem to reproduce it here.

It’s fixed the issue for me

It fixes the issue for me on my LaPi now running 20th Jan ROM and HardDisc image and disable_overscan=1 again.

Thanks Jeffrey

Tried ROM of January 23th. Commenting the overscan settings give no hangups any more. You wrote that the first mode change request send to the GPU lead to the hangup. Why did the overscan borders settings didn’t cause it then? Or are the overscan settings causing that the a mode change request is not issued as the screen is setup during start-up?

Anyway, many thanks for fixing this issue.

You wrote that the first mode change request send to the GPU lead to the hangup. Why did the overscan borders settings didn’t cause it then? Or are the overscan settings causing that the a mode change request is not issued as the screen is setup during start-up?

I have no idea. I can only assume that the bad mode change request was corrupting some of the GPU’s memory, and enabling overscan was doing something to fix or hide the corruption.