Adding a network driver to kernel for custom build

[Peter Flannery]

Hi I wanted to add the marvell network driver to a custom os build but I can't seem to get it to appear in the compiled usb image.

When following the http://www.chromium.org/chromium-os/quick-start-guide

I can get an image on the usb and boot from it but there is no network detected on my motherboard.

So I've tried to add the marvell drivers to the kernel config but these drivers don't appear when I rebuild the image.

This is the workflow I'm using to try and add the marvell ethernet drivers

• cros_sdk
  
• cd /path/to/kernel
  
• cros_workon --board=x86-generic start sys-kernel/chromeos-kernel
  
• ./chromeos/scripts/prepareconfig chromiumos-x86_64
  
• ./chromeos/scripts/kernelconfig editconfig  # mark the marvell ethernet drivers with 'M'
  
• cd /path/to/scripts
  
• ./build_packages --board=x86-generic
  
• ./image_to_usb.sh --board=x86-generic
  

But the marvell drivers never appear in /lib/modules/3.4.0/kernel/drivers/net/ethernet

what am I missing?

do i need to copy the drivers manually in to the image?

thanks

[Sonny Rao]

x86-generic doesn't use the chromiumos-x86_64 config, but amd64-generic does

 

do i need to copy the drivers manually in to the image?

thanks

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
 

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Peter Flannery]

Thanks for your help, I've managed to get the drivers to appear in the image..

so what I did was

• cros_sdk
• ./build_packages --board=amd64-generic
  
• cros_workon --board=amd64-generic start sys-kernel/chromeos-kernel
  
• cd /path/to/kernel
  
• ./chromeos/scripts/prepareconfig chromiumos-x86_64
  
• ./chromeos/scripts/kernelconfig editconfig
  
• cd /path/to/scripts
• ./build_packages --board=amd64-generic # got an error saying I needed to run "make mrproper"
• cd /path/to/kernel
• make mrproper
• cd /path/to/scripts
• ./build_packages --board=amd64-generic
• ./build_image --board=amd64-generic

Now when I boot with the usb image I get a "dm-verify" failure message "integrity failure"

I'm going to try and write the image to the usb again..

[Peter Flannery]

I've rebuilt and got the same issue.

Here is the top part of the message I get on boot

 Kernel panic - not syncing: dm-verity failure: device:8:19 error:-5 block:18446744073709551615 message:integrity failure

 Pid: 5, comm: kworker/u:0 Not tainted 3.4.0 #1

[Sonny Rao]

you must be building and booting an image with verification enabled, and somehow the image is getting corrupted (which is a little disturbing). 

you could try adding  --noenable_rootfs_verification to the build_image step and see if that helps.  

[Simon Boch]

Hello, 

i want to add a wireless driver too, but im not fully into the cros_sdk so i don't know where the path/to/kernel actually is