Dear , i use the modules from epc701 i915.ko .drm.ko
i find the intel graphics driver is same source . so i never build modules again . Thanks , Sam 2009/2/12 Jackie Wu <wwh.andr...@gmail.com> > > Where did you get the i915 driver? I don't find the android.git.kernel > common.git include the i915 driver code. The code can be got from > git://anongit.freedesktop.org/git/mesa/drm. See > http://intellinuxgraphics.org/download.html. > it has the modeset parameter. see i915_drv.c > > It works on both 2.6.25 and 2.6.27 on Eeepc1000h. I don't have 900sd > so can not have a try. > > Thanks > Jackie > > On Wed, Feb 11, 2009 at 8:59 PM, brian pang <brianpan...@gmail.com> wrote: > > > > But my i915 driver doesn't have modeset param. Besides, all the drivers > in vendor/asus/eee_701 are inconsistent with my kernel. Is your kernel > version 2.6.25? > > I checked android.git.kernel common.git, i915 driver doesn't declare any > PARAMs. > > Best Regards, > > Brian > > > > 2009/2/11 Jackie Wu <wwh.andr...@gmail.com> > >> > >> The kernel and i915 driver should be ok. I used EeePC1000H which is also > 945 but they use same driver source. > >> > >> I think your kernel config should still have problem. The black screen > is because your graphics modules (drm.ko and i915.ko) are not loaded > correctly. You must missed sth in kernel config. You can "alt+F1" to switch > to console to check dmesg what's the missed module. A better way is to > enable adbd and login to check the error. But you need to rebuild the atl > ethernet driver to get network work. > >> > >> Best Rgd > >> Jackie (Weihua) Wu > >> > >> On Wed, Feb 11, 2009 at 6:12 PM, brian pang <brianpan...@gmail.com> > wrote: > >>> > >>> sam > >>> I build the img for EPC904HD and got blackscreen too. but chen said > build the kernel with additional configuration can help. But looks my kernel > source from google is not match with prebuild driver from eeepc_701 source > tree. > >>> Best Regards, > >>> Brian > >>> > >>> 2009/2/11 bo wang <wangbo...@gmail.com> > >>>> > >>>> hi , > >>>> > >>>> you build the img to EPC701?you install img to EPC701 or other > platfrom ? > >>>> i build the img to 701 and i install to EPC900SD , will blackscreen > .... > >>>> the EPC900SD motherborad is mobile 945 and you build kernel modules > use i915.ko . > >>>> > >>>> i can't find the right driver source code too.... > >>>> > >>>> Best Regards, > >>>> Sam > >>>> > >>>> 2009/2/11 brianpan...@gmail.com <brianpan...@gmail.com> > >>>>> > >>>>> Hi, > >>>>> > >>>>> I use this way to compile 2.6.25 kernel from git. I put bzImage into > >>>>> vendor/asus/eee_701/kernel. > >>>>> then I rebuild the whole system. > >>>>> TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make > -j2 > >>>>> installer_img > >>>>> > >>>>> When i boot the system with my compiled kernel. > >>>>> I found following error. > >>>>> atl2: disagrees about version of symbol > >>>>> ... > >>>>> i915: disagrees about version of symbol > >>>>> > >>>>> > >>>>> I tried to build those driver from kernel tree. but I found i915 > >>>>> doesn't have modeset param at all. > >>>>> > >>>>> something wrong with my kernel source code? If so, where can I get > the > >>>>> right source code? > >>>>> > >>>>> Thanks in advance > >>>>> > >>>>> On Jan 9, 4:28 pm, "Chen Yang" <sunsety...@gmail.com> wrote: > >>>>> > Some additions to build the kernel for VMWare/VirtualBox: > >>>>> > > >>>>> > Hope it helps: > >>>>> > $cd mydroid > >>>>> > $cp vendor/asus/eee_701/kernel.config kernel/.config > >>>>> > $cd kernel > >>>>> > $make menuconfig > >>>>> > > >>>>> > Select the device drivers: > >>>>> > > >>>>> > For network card: > >>>>> > network device support -> > >>>>> > Ethernet (10 or 100Mbit) ---> > >>>>> > [*] EISA, VLB, PCI and on board controllers > >>>>> > <*> AMD PCnet32 PCI support > >>>>> > > >>>>> > For VESAFB: > >>>>> > Graphics support ---> > >>>>> > <*> Support for frame buffer devices ---> > >>>>> > [*] VESA VGA graphics support > >>>>> > Console display driver support ---> > >>>>> > <*> Framebuffer Console support > >>>>> > [*] Select compiled-in fonts > >>>>> > [*] VGA 8x8 font > >>>>> > [*] VGA 8x16 font > >>>>> > > >>>>> > In order to build correctly with 2.6.27, you may apply the patch > from here:http://review.source.android.com/6751 > >>>>> > > >>>>> > For command line option of vga=788, several approaches: > >>>>> > 1. append the option when the system boots, when it shows the menu, > >>>>> > you can press 'e' to edit the default entry(2). then 'd' to delete > the > >>>>> > first option line: "cmdline ... ", then 'e' the 0 entry, which is > the > >>>>> > line of " kernel --use-cmd ...", > >>>>> > remove the "--use-cmd-line" and append the option > >>>>> > "androidboot.hardware=eee_701 vga=788" at end of that line > >>>>> > then choose boot. It will enter the vesafb mode correctly. But > you > >>>>> > may need to edit it every time when boot. > >>>>> > > >>>>> > 2. modify the cmdline in /dev/block/sda3, you can mount it after > you > >>>>> > have successfully boot. to append "vga=788" to cmdline file: > >>>>> > #mkdir /data/boot > >>>>> > #mount -t ext2 /dev/block/sda3 /data/boot > >>>>> > #echo " vga=788" >/data/boot/cmdline > >>>>> > #umount /data/boot > >>>>> > then reboot the vm > >>>>> > > >>>>> > 3. modify the cmdline creation step in the build, i think you can > get > >>>>> > the in bootable/diskinstaller/config.mk, then you may need to > rebuild > >>>>> > the instaler.img and reinstall it to your vm. > >>>>> > > >>>>> > Hope it helps! > >>>>> > -- > >>>>> > ChenOn Fri, Jan 9, 2009 at 9:23 AM, rukiman < > ruksh...@optushome.com.au> wrote: > >>>>> > > >>>>> > > I have got as far as booting Android in VMware thanks to Chen > Yang's > >>>>> > > post above. I replaced mydroid/vendor/asus/ > >>>>> > > eee_701/ kernel with that of Stargatto's posted above. However > booting > >>>>> > > up Android with VMware keeps giving me the below error over and > over. > >>>>> > > >>>>> > > SurfaceFlinger[XXXX]: segfault at 38 ip XXXXXXXX sp XXXXXXXX > error 4 > >>>>> > > in libc.so[80100000+49000] > >>>>> > > >>>>> > > Perphaps my kernel is not ok? How do I build a kernel with VESAFB > and > >>>>> > > network drivers and where do I specify vga=788? I do not know > much > >>>>> > > about building kernels so if someone could provide a guide that > would > >>>>> > > be great. > >>>>> > > >>>>> > >> 1. Be sure to compile the kernel with VESAFB and add the vga=788 > with in > >>>>> > >> cmdline. 800x600 seems to be a quite usable resolution, for > 1024x768 and > >>>>> > >> above resolutions, you may meet some performance or execution > issues. > >>>>> > >> 2. If you want to use network, you may need to compile the AMD > PCNET32 > >>>>> > >> driver. > >>>>> > >>>> > >>>> > >>>> > >>> > >>> > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
