Doesn't work on Pi1 with 512 MB RAM

[seandepagnier]

I have copied the image to a micro sd card with:

dd if=20150821-1625-vc4-image.img of=/dev/sdb bs=4M

and the raspberry remains black screen without booting. I can mount the filesystems and see all the files. What can I do to get a working image? Did I miss an important step?

[the-unusual]

The 20150821-1625-vc4-image.img build doesn't work because Mesa is preventing X from working properly. The image 20150821-1625-vc4-image.img should work.

[ktb83dev]

HoboHacker meant to say "The image 20150808-1312-vc4-image.img should work."

The latest build failed (20150917-0953-vc4-failure.log.bz2) due to some code in Mesa, but the build can be successful if using GCC/G++ 4.9.2.

[seandepagnier]

My friend tried the 08-08 image and claimed it had the same result.

Basically, the green light flashes a little at power up then turns off and that's it, and there is always a black screen nothing to hdmi ever.

So don't understand how this has anything to do with mesa as I cannot even get into the bootloader.

On 9/17/15, ktb83dev notifications@github.com wrote:

Hobohacker meant to say "The image 20150808-1312-vc4-image.img should work."

---

Reply to this email directly or view it on GitHub: https://github.com/gohai/vc4-buildbot/issues/4#issuecomment-141066377

[ktb83dev]

Try adding (or uncommenting) hdmi_drive=2 in config.txt. I needed that for it to boot.

[seandepagnier]

I had success using hdmi_drive=2

Now I face a different problem. The ephiphany web browser will not run, it complains about missing libraries. Further, the keyboard mysteriously repeats the last character making typing nearly impossible. Finally programs crash in very strange ways.

glxgears does however work. Any hints here? Does the vc4 driver support etc1 compression?

[ktb83dev]

I had success using hdmi_drive=2

Good.

Now I face a different problem. The ephiphany web browser will not run, it complains about missing libraries.

Epiphany browser for the Pi is built to use the userland libs from the foundation which are located at /opt/vc/. However, that directory has been moved to /opt/vc.bak so that it doesn't get in the way. Certain applications which have been specifically compiled to use those files will likely not work. I haven't tried to see if I can leave a limited set of the userland libs in place in order to support Pi-specific applications like Epiphany, but you're welcome to try (you would probably want to make sure to get the libs which conflict with the Mesa libs out of the way, and run sudo ldconfig). Applications which haven't been customized to use the Pi libs should work. Try Iceweasel (Firefox) and Chromium (I use a recent version from Ubuntu armhf).

Further, the keyboard mysteriously repeats the last character making typing nearly impossible.

I was able to avoid this problem by adding dwc_otg.fiq_fsm_mask=0xF to cmdline.txt.

Finally programs crash in very strange ways.

My guess is that this is probably related to the moved libs (see above).

glxgears does however work. Any hints here? Does the vc4 driver support etc1 compression?

I'm not familiar with etc1 compression. S3TC might work. Try installing libtxc-dxtn-s2tc0, you might need to force-enable it with driconf in some cases. http://dri.freedesktop.org/wiki/S3TC/

FYI - you'll probably want to set cma=256 or cma=512 in cmdline.txt. I've been using cma=512.

[nighteagle1974]

Hi,

so i have found out, if gpu_mem was set in config.txt i have a black screen. Uncomment or not configure with raspi-config should work to prevent this. Use Vc4 CMA? So then i think gpu_mem is wrong to set?

Regards

[Schule04]

I'm having a somewhat similar problem: I copied the latest image 20151112 using dd to an sd card, but when I try to boot it in my raspi (model B with 512MB RAM) I only see the rainbow test image, but raspbian never launches. Is it because I tried it with screens that are not 1920x1080? I only have displays with native resolutions of 1280x1024 and 1920x1200, could that be the reason why it's not booting up?

[nighteagle1974]

Hi,

open your config.txt and deactivate all HDMI and all VIDEO Variables and also check if gpu_mem ist set.. this ends in an hang up if you have used the raspi-config to split memory.

Am 29.11.2015 17:58, schrieb Schule04:

I'm having a somewhat similar problem: I copied the latest image 20151112 using dd to an sd card, but when I try to boot it in my raspi (model B with 512MB RAM) I only see the rainbow test image, but raspbian never launches. Is it because I tried it with screens that are not 1920x1080? I only have displays with native resolutions of 1280x1024 and 1920x1200, could that be the reason why it's not booting up?

— Reply to this email directly or view it on GitHub https://github.com/gohai/vc4-buildbot/issues/4#issuecomment-160432019.

[Schule04]

config.txt

Here is my config.txt, it is unchanged from the one in the image since it will never boot up.

[nighteagle1974]

Hi,

i don't know if the VC4 is working on the RPI B. I have the RPI 2B. Have you use Win32DiskImager to make the SD and copied the Image with this tool? Then you can test to set hdmi_group and hdmi_mode to the values of your monitor. If they hangs on the rainbow it don't boot up.. so it can't find the image ont he SD Card?

Format SD Card and write it again with the Win32DiskImager Tool.

Am 29.11.2015 18:42, schrieb Schule04:

config.txt https://github.com/gohai/vc4-buildbot/files/46684/config.txt

Here is my config.txt, it is unchanged from the one in the image since it will never boot up.

— Reply to this email directly or view it on GitHub https://github.com/gohai/vc4-buildbot/issues/4#issuecomment-160435600.

[Schule04]

I now tried it with Win32DiskImager Tool and the result was the same as with dd.

[gohai]

If you didn't get this working (with the vanilla image) before: could you give the latest from http://sukzessiv.net/~gohai/vc4-buildbot/build/ a try? Thanks.

[nighteagle1974]

Hi,

@gohai...

do you think the problem is actually? So the Post is from last month! On my RPI2 VC4 works only in HDMI not in Video-Out Mode.

For Chromium on the RPI2 with VC4 sometimes ist unstable and System hang up. I use an RPI2 with Chromium in Kiosk-Mode on an Touch-Screen 21" Works fine with Software-Rasterizer but a little bit slow on scrolling the Websites like an iPad. With VC4 is better and react quick.. but is unstable.

Wish you good slide to the new Year :-)

[gohai]

@nighteagle1974 It's a known limitation that HDMI is the only output currently working. The other bug you mention is not related to "Cannot boot image".

[Schule04]

The system is behaving identical as with the old build.

[gohai]

@Schule04 You're using different monitors, connected via HDMI? (just checking to make sure)

[gohai]

@Schule04 And just to be sure: you were using http://sukzessiv.net/~gohai/vc4-buildbot/build/20151220-1053-vc4-image.zip, on a Pi1 with 512 MB RAM?

[Schule04]

I used 2 monitors with a HDMI to DVI adapter:

• 1280x1024 Ilyama screen
• 1920x1200 Lenovo screen

Both work with the regular drivers, Yes, I used the image from your link. After setting cma in cmdline.txt to certain values, the raspi seems to boot for a few seconds, but when this happens there is nothing displayed on the screen.

[gohai]

@Schule04 Raspbian just released a new version with experimental vc4 support, but they say they only support the Pi 2, so perhaps this is expected behavior?

[wuyuehang]

@gohai from the last story on thread https://github.com/raspberrypi/linux/issues/1210, it's expected behavior on Pi1