The most important thing you should know is that the RaspberryPi is a strange beast where the ARM CPU is the not main CPU - it's only a co-processor to the VideoCore GPU. When the RaspberryPi starts, a GPU blob is read from the SD card to the L2 cache and executed. This code then brings up all the important peripherals (RAM, clocks etc) and ...
Starting with the default configuration, or one you know works already, is a good idea. Beware that for the Pi 2, you should use:
Instead of bcmrpi_defconfig.
Note that if you want to avoid clobbering an existing kernel install of the same version, set the General setup -> Local version - append to kernel release string to a unique ...
After hours of reading threads and following guides here and there, the definitive guide that got the driver working was here. Following the steps listed in that post:
$ # install necessary software
$ sudo apt-get update
$ sudo apt-get install bc git
$ # download raspbian kernel sources, takes some minutes
$ sudo wget "https://raw.githubusercontent.com/...
Turns out the steps to recompile and load the rtlwifi module are correct. The problem is iwconfig not working to enable/determine monitoring mode in this situation.
Instead, I used iw as outlined by Steven Gordon and it worked.
STEP 6b: List the physical network interfaces available
$ iw dev
STEP 7: Determine if the physical interface ...
"In normal circumstances there is NEVER a need to run rpi-update as it always gets you to the leading edge firmware and kernel and because that may be a testing version it could leave your RPi unbootable". https://www.raspberrypi.org/forums/viewtopic.php?p=916911#p916911
Even the rpi-update documentation now warns "Even on Raspbian you should only use this ...
Indeed, it was a problem with the drivers. I switched to use Raspbian and then I installed the drivers, like explained here.
Dowloaded the driver
Extracted the files (tar xvf LCD-show.tar.gz)
sudo ./LCD35-show (this depends on the display size, mine is 3.5")
In my case it didn't reboot automatically, but it displayed some messages regarding ...
One of the things that I have read a hundred times in dealing with anything attached to the USB on any model of RPi is to make sure that you have a decent Power Supply (2 or more Amps) or use a quality powered USB hub. Could it be possible that your WiFi dongle isn't getting enough power now because the HDMI screen is too greedy?
For an SD Card image file (similar to the .sdimg ones) to be generated your local.conf file must include the rpi-sdimg filesystem type in the IMAGE_FSTYPE variable. This will typicaly give you a value such as:
IMAGE_FSTYPES = "tar.xz ext3 rpi-sdimg"
With the above parameter included a .rpi-sdimg file will be created during a the build. After a bitbake ...
To update Krzysztof's great answer, Broadcom finally publicly released some code, licensed as 3-Clause BSD, to aid the making of an open source GPU driver. The "rpi-open-firmware" effort to replace the Raspberry Pi VPU firmware blob started in 2016: https://github.com/christinaa/rpi-open-firmware. See more at https://news.ycombinator.com/item?id=11703842
Edit: It's here!
Check the release notes for NOOBS v1.3.3:
Check out the release notes for each distribution for more details.
Highlights for Raspbian include:
New firmware and 3.10 kernel, with numerous functionality improvements.
New hardware-accelerated X driver included and enabled by default.
Mathematica and the Wolfram Language ...
If your idea is to make an exact carbon copy of the Pi 2, you won't succeed.
While @joan stated that the OTP contents are not shared to the public, the actual SoC is also not available. The BCM2836 is a custom design for the Raspberry Pi Foundation and I doubt it is available through the common channels.
That being said there is a wide variety of Raspberry-...
What is the difference between kernel "3.18.11" and "3.18.11-v7+"?
The -v7+ is tacked on to indicate this isn't from a vanilla source tree, and that it was compiled specifically for the Pi 2.
I'm planning to get this kernel source: wget https://github.com/raspberrypi/linux/archive/rpi-3.18.y.tar.gz Is this the correct source for my kernel?
No. If you ...
Important: Follow these instructions meticulously
Note: The OP is using Wheezy and the latest kernel version from raspberrypi-bootloader then is 4.1.7-v7+, while on jessie that version is 4.1.13-v7+ and that's a critical difference!
If you're going to apply these steps to your own situation, adjust the values accordingly.
Step 1: Get the git_hash from ...
Finally I had a breakthrough!
Instead of using modprobe and dkms it was enough to follow these steps:
sudo git clone https://github.com/EntropicEffect/rtl8822bu.git
sudo nano Makefile
Update lines 100 and 101 to this and save the file:
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ARM_RPI = y
sudo make install
The Model B uses a SMSC LAN9512 USB 2.0 Hub and 10/100 Ethernet Controller IC to provide multiple physical USB host ports from the single USB OTG port available on the Broadcom SoC.
The presence of this hub IC prevents the USB ports from being used in slave mode. However, as the Model A does not have this IC present and instead just has a single USB port ...
A comment to goldilock's great post:
Just wanted to add one thing I observe with rpi-4.1.y branch (05376fce25aaab4f47182a5af04928bfa06f30d6): In order to have USB working (this includes the USB-connected ethernet), one has to also enable BCM2708_MBOX (Device Drivers->Mailbox Hardware Support->Broadcom BCM2708 Mailbox (vcio)).
Without this option USB starts ...
I spent a number of hours recently with my C920 and a Raspberry Pi 3 recently to make a babyCam that I could stream within my home network. I may be able to shed some light but also provide documentation and experience to other users.
OK, to use the Video4Linux2 driver to find the camera's video device do this:
There should not be a driver problem with the 2.8" display and RPi 2 newer kernels, as support is built in (ie you don't need the adafruit kernel) 4.0.7 works. The main problem is with the touch screen support. I have the same set up (but kernel 4.0.9-v7+).
To get the display to work, you need either the adafruit dts overlay file pitft28c-overlay.dts (which ...
I have a Pi 4 Model B/4GB serving a small office as a router/firewall/gateway with dnsmasq (DHCP+DNS), dnscrypt-proxy, chrony (NTP), and a few other odds and ends. It's fairly busy: up to 20 users at a time, lots of file uploads, three main VLANs (plus a management VLAN). There's minimal internal routing for the time being.
I haven't really stress-tested ...
I have tested with the as seen on http://www.brianhensley.net/2012/07/getting-spi-working-on-raspberry-pi.html and changed the speed.
The maximum speed when the test passed is 15MHz = 15000KHz:
spi mode: 0
bits per word: 8
max speed: 15000000 Hz (15000 KHz)
FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF ...
It can be hard to learn writing drivers when interfacing with complicated devices and/or complicated buses. Because of that I would recommend either using some simple and well known devices (ignoring existing implementation of their drivers in the kernel) like I²C/SPI devices that are usually used with microcontrollers. For example you could find any device ...
well google will provide your answer
generate custom linux image
it is a lil about which distro you want to use.. if you can give more informations i can update my answer maybe..
furthermore.. why you do not install and configure your pi and make an image from the final state?
It is not possible, Unix like system relies on standards that are not implemented in FAT or NTFS. Your system need permissions, groups, symbolic links to work properly. Neither FAT nor NTFS can provide it.
by supergordon » Tue Sep 09, 2014 3:20 pm Hello,
there are no drivers for 3.12.28+, so I compiled them. Works well.
http://gordon.d4rc.net/8188eu_3.12.28.zip readme.txt contains quick
This from supergordon worked for me:
sudo cp rtl8188eufw.bin /lib/...
Could it be something as simple as the camera being recognized as something other than /dev/video0? Does ls /dev/video* yield anything else?
It's been many months since I used a C920 on my Raspberry Pi, but at the time, everything "just worked" so long as I used the right device.
The biggest obstacle I can think of is programming the OTP (One-time programmable) memory of the Broadcom SoC so that it will boot.
I am not sure what infomation is publically available for that purpose.