Discussion:
how to inject/transfer a working Broadcom 4331 Wifi Driver on Android x86 4.4 r1 build by cwhuang into another build wich doesn't have the driver, in the easiest way without rebuilding all from source?
(too old to reply)
Saipudin Haris
2015-06-04 06:18:03 UTC
Permalink
Currently only Android x86 4.4 r1 by cwhuang
<http://www.google.com/url?q=http%3A%2F%2Fsourceforge.net%2Fu%2Fcwhuang%2F&sa=D&sntz=1&usg=AFQjCNGWWsjKjFAXoM2MgGzYEGMgQNFv6w>
(
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download)
has a working Wifi driver (Broadcom 4331) for my Macbook Pro 8,1

here are the proof -----> http://valid.canardpc.com/a/5a8idy


I have tried these, and some of these build are working just fine on my
macbook pro 8,1 except that none of these have a working broadcom 4331
driver and of course bluetooth drivers (i'm not surprise though):

LATEST-GIT-TEST-BUILDS, link provided by rb g
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing)


and

Android-x86 lollipop, link provided by Mario Holzinger
(
https://drive.google.com/folderview?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
)


====================================================
below is working my usb boot parameter with persistent mode enabled
====================================================

#start androidx86-kk-4.4.2_r1
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
SDCARD=/multiboot/linux/androidx86/sdcard.img
#end androidx86-kk-4.4.2_r1


#start androidx86-kk-4.4.2_r2
LABEL androidx86-kk-4.4.2_r2
MENU LABEL Android x86 v4.4.2-r2-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r2/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r2/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r2/
#end androidx86-kk-4.4.2_r2


#start androidx86-4.4.4_3.18.8
LABEL androidx86-4.4.4_3.18.8
MENU LABEL Android x86 v4.4.4_3.18.8-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/
#end androidx86-4.4.4_3.18.8

#start androidx86-4.4.4_4.0
LABEL androidx86-4.4.4_4.0
MENU LABEL Android x86 v4.4.4_4.0-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_4.0/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_4.0/
#end androidx86-4.4.4_4.0


#start androidx86-lp-5.1.1
LABEL androidx86-lp-5.1.1
MENU LABEL Android x86 v5.1.1-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1/
#end androidx86-lp-5.1.1


#start androidx86-lp-5.1.1_3.18.8
LABEL androidx86-lp-5.1.1_3.18.8
MENU LABEL Android x86 v5.1.1_3.18.8-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/
#end androidx86-lp-5.1.1_3.18.8


#start androidx86-lp-5.1.1_4.0
LABEL androidx86-lp-5.1.1_4.0
MENU LABEL Android x86 v5.1.1_4.0-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_4.0/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_4.0/
#end androidx86-lp-5.1.1_4.0


==============
common file layout:
==============

filesystem: fat32

folder structure: /multiboot/linux/androidx86/*code/*version

file structure:

/multiboot/linux/androidx86/*code/*version/kernel ---- [android x86 kernel]

/multiboot/linux/androidx86/*code/*version/initrd.img ---- [android x86
initrd image]

/multiboot/linux/androidx86/*code/*version/ramdisk.img ---- [android x86
ramdisk image]

/multiboot/linux/androidx86/*code/*version/system.img ---- [unsquashed
android x86 root file system, required for root file system modification]

/multiboot/linux/androidx86/*code/*version/data.img ---- [persistent
storage, ext2 file system, for application/internal persistent storage
purpose, created using PDL Casper-RW Creator is ©2009 Lance
http://www.pendrivelinux.com and renamed the output file from casper-rw to
data.img. For data.img partition resizing, I use TopoResize 0.7.1 by Chris
Semler.]



===============================
Syslinux parameter to make bootable drive:
===============================

#syslinux install parameter for dual boot Windows 7 & Android x86

syslinux32.exe -i -m -f -d /multiboot c:


#syslinux.cfg parameter for dual boot Windows 7 & Android x86

PROMPT 0
TIMEOUT 30

#Win7 [Partition 2, NTFS, Primary, Data]
LABEL Win7
MENU LABEL Windows 7
MENU INDENT 1
KERNEL chain.c32
APPEND hd0,1
COM32 /multiboot/chain.c32 fs ntldr=/bootmgr
#end Windows.7


#start androidx86-kk-4.4.2_r1 [Partition 1, Fat32, Primary, Boot]
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
#end androidx86-kk-4.4.2_r1
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-05 19:07:29 UTC
Permalink
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to stick
with open source
drivers if possible....

check with fuzzy7k as he's the one who provided all the work / patches for
android-x86 to be
able to integrate the WL driver....or you could port / debug it to kernel
4.0 / 4.1

REF: https://groups.google.com/forum/#!searchin/android-x86/broardcom$20wl|sort:date/android-x86/nhRi2q6I7Nc/vJQm7r75A7sJ
Post by Saipudin Haris
Currently only Android x86 4.4 r1 by cwhuang
<http://www.google.com/url?q=http%3A%2F%2Fsourceforge.net%2Fu%2Fcwhuang%2F&sa=D&sntz=1&usg=AFQjCNGWWsjKjFAXoM2MgGzYEGMgQNFv6w>
(
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download)
has a working Wifi driver (Broadcom 4331) for my Macbook Pro 8,1
here are the proof -----> http://valid.canardpc.com/a/5a8idy
I have tried these, and some of these build are working just fine on my
macbook pro 8,1 except that none of these have a working broadcom 4331
LATEST-GIT-TEST-BUILDS, link provided by rb g
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing)
and
Android-x86 lollipop, link provided by Mario Holzinger
(
https://drive.google.com/folderview?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
)
====================================================
below is working my usb boot parameter with persistent mode enabled
====================================================
#start androidx86-kk-4.4.2_r1
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
SDCARD=/multiboot/linux/androidx86/sdcard.img
#end androidx86-kk-4.4.2_r1
#start androidx86-kk-4.4.2_r2
LABEL androidx86-kk-4.4.2_r2
MENU LABEL Android x86 v4.4.2-r2-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r2/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r2/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r2/
#end androidx86-kk-4.4.2_r2
#start androidx86-4.4.4_3.18.8
LABEL androidx86-4.4.4_3.18.8
MENU LABEL Android x86 v4.4.4_3.18.8-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/
#end androidx86-4.4.4_3.18.8
#start androidx86-4.4.4_4.0
LABEL androidx86-4.4.4_4.0
MENU LABEL Android x86 v4.4.4_4.0-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_4.0/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_4.0/
#end androidx86-4.4.4_4.0
#start androidx86-lp-5.1.1
LABEL androidx86-lp-5.1.1
MENU LABEL Android x86 v5.1.1-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1/
#end androidx86-lp-5.1.1
#start androidx86-lp-5.1.1_3.18.8
LABEL androidx86-lp-5.1.1_3.18.8
MENU LABEL Android x86 v5.1.1_3.18.8-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/
#end androidx86-lp-5.1.1_3.18.8
#start androidx86-lp-5.1.1_4.0
LABEL androidx86-lp-5.1.1_4.0
MENU LABEL Android x86 v5.1.1_4.0-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_4.0/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_4.0/
#end androidx86-lp-5.1.1_4.0
==============
==============
filesystem: fat32
folder structure: /multiboot/linux/androidx86/*code/*version
/multiboot/linux/androidx86/*code/*version/kernel ---- [android x86 kernel]
/multiboot/linux/androidx86/*code/*version/initrd.img ---- [android x86
initrd image]
/multiboot/linux/androidx86/*code/*version/ramdisk.img ---- [android x86
ramdisk image]
/multiboot/linux/androidx86/*code/*version/system.img ---- [unsquashed
android x86 root file system, required for root file system modification]
/multiboot/linux/androidx86/*code/*version/data.img ---- [persistent
storage, ext2 file system, for application/internal persistent storage
purpose, created using PDL Casper-RW Creator is ©2009 Lance
http://www.pendrivelinux.com and renamed the output file from casper-rw
to data.img. For data.img partition resizing, I use TopoResize 0.7.1 by
Chris Semler.]
===============================
===============================
#syslinux install parameter for dual boot Windows 7 & Android x86
#syslinux.cfg parameter for dual boot Windows 7 & Android x86
PROMPT 0
TIMEOUT 30
#Win7 [Partition 2, NTFS, Primary, Data]
LABEL Win7
MENU LABEL Windows 7
MENU INDENT 1
KERNEL chain.c32
APPEND hd0,1
COM32 /multiboot/chain.c32 fs ntldr=/bootmgr
#end Windows.7
#start androidx86-kk-4.4.2_r1 [Partition 1, Fat32, Primary, Boot]
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
#end androidx86-kk-4.4.2_r1
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-05 20:06:43 UTC
Permalink
Ok. Thanks for the info.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-06 07:22:31 UTC
Permalink
I'll be glad to test it ASAP if you would kindly build it and provided me
the iso image link download.
I have so little knowlege to build android x86 from source, so i'm just
relying on your kindness for building it for people like me.

Thanks.
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-06 18:13:26 UTC
Permalink
the attached files are log files from Android x86 4.4.2 r1 ----->
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-06 18:16:55 UTC
Permalink
the attached files are log files from Android x86 4.4.4 with kernel 4.0 (
kitkat_4.4.4_4.0_x86_gapps_20150525.iso
<https://drive.google.com/open?id=0B43N_UcsJhpjNk1wWnpVbXBYUnM>) ----->
https://drive.google.com/uc?id=0B43N_UcsJhpjNk1wWnpVbXBYUnM&export=download
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-06 18:19:07 UTC
Permalink
the attached files are log files from Android x86 5.1.1 with kernel 4.0 (
<https://drive.google.com/open?id=0B43N_UcsJhpjNk1wWnpVbXBYUnM>
lollipop_5.1.1_4.0_x86_gapps.iso
<https://drive.google.com/open?id=0B43N_UcsJhpjM2hqSDRSMUJsWmM>) ----->
https://drive.google.com/uc?id=0B43N_UcsJhpjM2hqSDRSMUJsWmM&export=download
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-08 07:52:25 UTC
Permalink
the attached files are log files from android_x86-4.4-r2-20150606.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkZU02blF3ZFpuX1U> i capture
on my macbook pro 8,1
using the following command in a rooted terminal window:

# dmsg > dmsg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt

I hope, the attached logs can be a little help in further developing
Android x86 project.

Thanks.
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-08 07:54:51 UTC
Permalink
the attached files are log files from
android_x86-4.4-r2-64bitKRNL_32bitUSR-20150606.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkUF9rdjlEbGFEU2s> i capture
on my macbook pro 8,1
using the following command in a rooted terminal window:

# dmsg > dmsg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt

I hope, the attached logs can be a little help in further developing
Android x86 project.

Thanks.
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-08 07:56:51 UTC
Permalink
the attached files are log files from
<https://drive.google.com/open?id=0B2evBKvIpdYkUF9rdjlEbGFEU2s>
android_x86-5.1.1-20150607.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkelVJQmRKblcyNU0> i capture
on my macbook pro 8,1
using the following command in a rooted terminal window:

# dmsg > dmsg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt

I hope, the attached logs can be a little help in further developing
Android x86 project.

Thanks.
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-08 15:40:00 UTC
Permalink
Hi,

here are the attached files are log files from
android_x86-5.1.1-64bitKRNL_32bitUSR-20150607.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkdUFiQnVvVnJ1Tnc>
<https://drive.google.com/open?id=0B2evBKvIpdYkelVJQmRKblcyNU0> i capture
on my macbook pro 8,1
using the following command in a rooted terminal window:

# dmesg > dmesg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt

addition:

# lspci -k > lspci.txt

I hope, the attached logs can be a little help in further developing
Android x86 project.

Thanks.

NB: I'm still hoping that there would be a working Broadcom 4331 driver
support (just as said on --->
https://wireless.wiki.kernel.org/en/users/drivers/brcm80211)
for my macbook pro 8.1 on next Android x86 official release. In the
mean time, i will post all available android x86 newest build running
on my macbook pro 8.1 here such as the:

LATEST-GIT-TEST-BUILDS
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list)
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may not
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-08 15:51:49 UTC
Permalink
would it not make more sense for you to continue running Android x86 4.4 r1
which you said in OP
works fine for your wifi, instead of filling up this forum with log files
from builds which do not include
the wl driver and therefore will not work for you.????

Or you could "test and make sure the wl driver
work with the kernel 4.0" as the project lead stated and provide
the needed patches
Post by Saipudin Haris
Hi,
here are the attached files are log files from
android_x86-5.1.1-64bitKRNL_32bitUSR-20150607.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkdUFiQnVvVnJ1Tnc>
<https://drive.google.com/open?id=0B2evBKvIpdYkelVJQmRKblcyNU0> i capture
on my macbook pro 8,1
# dmesg > dmesg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt
# lspci -k > lspci.txt
I hope, the attached logs can be a little help in further developing
Android x86 project.
Thanks.
NB: I'm still hoping that there would be a working Broadcom 4331 driver
support (just as said on --->
https://wireless.wiki.kernel.org/en/users/drivers/brcm80211)
for my macbook pro 8.1 on next Android x86 official release. In the
mean time, i will post all available android x86 newest build running
LATEST-GIT-TEST-BUILDS
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list
)
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may
not
Post by rbg
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-08 16:00:03 UTC
Permalink
OK then, I'll just revert to the old ones that's still working.

Thanks, for the notice.
Post by rbg
would it not make more sense for you to continue running Android x86 4.4
r1 which you said in OP
works fine for your wifi, instead of filling up this forum with log files
from builds which do not include
the wl driver and therefore will not work for you.????
Or you could "test and make sure the wl driver
work with the kernel 4.0" as the project lead stated and provide
the needed patches
Post by Saipudin Haris
Hi,
here are the attached files are log files from
android_x86-5.1.1-64bitKRNL_32bitUSR-20150607.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkdUFiQnVvVnJ1Tnc>
<https://drive.google.com/open?id=0B2evBKvIpdYkelVJQmRKblcyNU0> i
capture on my macbook pro 8,1
# dmesg > dmesg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt
# lspci -k > lspci.txt
I hope, the attached logs can be a little help in further developing
Android x86 project.
Thanks.
NB: I'm still hoping that there would be a working Broadcom 4331 driver
support (just as said on --->
https://wireless.wiki.kernel.org/en/users/drivers/brcm80211)
for my macbook pro 8.1 on next Android x86 official release. In the
mean time, i will post all available android x86 newest build running
LATEST-GIT-TEST-BUILDS
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list
)
Post by Saipudin Haris
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may
not
Post by rbg
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work / patches
for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-08 17:25:32 UTC
Permalink
FWIW:

it can be patched / implemented, spend time reading all the available
documentation BUT....

I have b43 wifi implemented as I have an older wifi card I test with...if
you look at all the documentation
the broardcom driver support is all over the map......

bcrmsmac / bcrmfmac / b43 / b43 legacey / wl_sta, oh and if you use A then
blacklist B cause it'll cause issues
and so on and so forth....it's a nightmare.....

chips a/b/c are supported by this b43 group, chips d/e/f are supported by
bcrmsmac and so on...

now when someone who has a wifi driver that has ssb uses the build their
wifi doesn't work
cause the broadcom driver wasn't blacklisted and uses ssb....

Ubuntu and other distributions have gone through a lot of work over the
years to iron all that out
using blacklist/whitelist and who knows what...and they have done it
well....
The Wi-Fi For BC does work in 4.4 R2, I used it for years, One thing,
Make sure your “Alternate OS” has it turned on then reboot to R2 and it
works fine, turns on/off everything, But if you shut the Hardware switch
down, It can’t turn it back on, I’m Currently On 5.1.1 with the 4.0 kernel,
and same thing, been the same since I started playing with X86...
Other then that, I have the BC43 Drivers, And From what I understand you
can do A build with them (No, I have no clue how), But if you Search this
thread for B43, You’ll find it....
Good Luck
Mike
*From:* Saipudin Haris <javascript:>
*Sent:* Monday, June 08, 2015 11:00 AM
*Subject:* Re: how to inject/transfer a working Broadcom 4331 Wifi Driver
on Android x86 4.4 r1 build by cwhuang into another build wich doesn't have
the driver, in the easiest way without rebuilding all from source?
OK then, I'll just revert to the old ones that's still working.
Thanks, for the notice.
Post by rbg
would it not make more sense for you to continue running Android x86 4.4
r1 which you said in OP
works fine for your wifi, instead of filling up this forum with log
files from builds which do not include
the wl driver and therefore will not work for you.????
Or you could "test and make sure the wl driver
work with the kernel 4.0" as the project lead stated and provide
the needed patches
Post by Saipudin Haris
Hi,
here are the attached files are log files from
android_x86-5.1.1-64bitKRNL_32bitUSR-20150607.iso
<https://drive.google.com/open?id=0B2evBKvIpdYkdUFiQnVvVnJ1Tnc> i
capture on my macbook pro 8,1
# dmesg > dmesg.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b radio -d > radio.txt
# getprop > prop.txt
# uname -a > uname.txt
# ps > ps.txt
# cat > /proc/cpuinfo > cpuinfo.txt
# cat > /proc/modules > modules.txt
# lspci -k > lspci.txt
I hope, the attached logs can be a little help in further developing
Android x86 project.
Thanks.
NB: I'm still hoping that there would be a working Broadcom 4331 driver
support (just as said on --->
https://wireless.wiki.kernel.org/en/users/drivers/brcm80211)
for my macbook pro 8.1 on next Android x86 official release. In
the mean time, i will post all available android x86 newest build running
LATEST-GIT-TEST-BUILDS
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list
)
Post by rbg
Post by rbg
think you'll find the 4.4-r1 was using the broadcom proprietary WL
driver.....which
has been replaced by the open source drivers and it appears they may
not
Post by rbg
support
the 4331 chip yet....I believe the goal of android-x86 project was to
stick
Post by rbg
with open source
drivers if possible....
check with fuzzy7k as he's the one who provided all the work /
patches for
Post by rbg
android-x86 to be
able to integrate the WL driver....or you could port / debug it to
kernel
Post by rbg
4.0 / 4.1
If someone can test and make sure the wl driver
work with the kernel 4.0, I'll try to add it back.
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-08 20:40:54 UTC
Permalink
ya think it's called anaconda (cira 1995) and used in various linux
distributions....then again
they have probably moved on from that...LOL
How about a Build that Test for what Is Actually there and then installs
and white/black lists the appropriate drivers?!?!??!
9-)
Mike
Post by Saipudin Haris
Currently only Android x86 4.4 r1 by cwhuang
<http://www.google.com/url?q=http%3A%2F%2Fsourceforge.net%2Fu%2Fcwhuang%2F&sa=D&sntz=1&usg=AFQjCNGWWsjKjFAXoM2MgGzYEGMgQNFv6w>
(
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download)
has a working Wifi driver (Broadcom 4331) for my Macbook Pro 8,1
here are the proof -----> http://valid.canardpc.com/a/5a8idy
I have tried these, and some of these build are working just fine on my
macbook pro 8,1 except that none of these have a working broadcom 4331
LATEST-GIT-TEST-BUILDS, link provided by rb g
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing)
and
Android-x86 lollipop, link provided by Mario Holzinger
(
https://drive.google.com/folderview?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
)
====================================================
below is working my usb boot parameter with persistent mode enabled
====================================================
#start androidx86-kk-4.4.2_r1
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
SDCARD=/multiboot/linux/androidx86/sdcard.img
#end androidx86-kk-4.4.2_r1
#start androidx86-kk-4.4.2_r2
LABEL androidx86-kk-4.4.2_r2
MENU LABEL Android x86 v4.4.2-r2-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r2/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r2/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r2/
#end androidx86-kk-4.4.2_r2
#start androidx86-4.4.4_3.18.8
LABEL androidx86-4.4.4_3.18.8
MENU LABEL Android x86 v4.4.4_3.18.8-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/
#end androidx86-4.4.4_3.18.8
#start androidx86-4.4.4_4.0
LABEL androidx86-4.4.4_4.0
MENU LABEL Android x86 v4.4.4_4.0-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_4.0/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_4.0/
#end androidx86-4.4.4_4.0
#start androidx86-lp-5.1.1
LABEL androidx86-lp-5.1.1
MENU LABEL Android x86 v5.1.1-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1/
#end androidx86-lp-5.1.1
#start androidx86-lp-5.1.1_3.18.8
LABEL androidx86-lp-5.1.1_3.18.8
MENU LABEL Android x86 v5.1.1_3.18.8-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/
#end androidx86-lp-5.1.1_3.18.8
#start androidx86-lp-5.1.1_4.0
LABEL androidx86-lp-5.1.1_4.0
MENU LABEL Android x86 v5.1.1_4.0-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_4.0/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_4.0/
#end androidx86-lp-5.1.1_4.0
==============
==============
filesystem: fat32
folder structure: /multiboot/linux/androidx86/*code/*version
/multiboot/linux/androidx86/*code/*version/kernel ---- [android x86 kernel]
/multiboot/linux/androidx86/*code/*version/initrd.img ---- [android x86
initrd image]
/multiboot/linux/androidx86/*code/*version/ramdisk.img ---- [android x86
ramdisk image]
/multiboot/linux/androidx86/*code/*version/system.img ---- [unsquashed
android x86 root file system, required for root file system modification]
/multiboot/linux/androidx86/*code/*version/data.img ---- [persistent
storage, ext2 file system, for application/internal persistent storage
purpose, created using PDL Casper-RW Creator is ©2009 Lance
http://www.pendrivelinux.com and renamed the output file from casper-rw
to data.img. For data.img partition resizing, I use TopoResize 0.7.1 by
Chris Semler.]
===============================
===============================
#syslinux install parameter for dual boot Windows 7 & Android x86
#syslinux.cfg parameter for dual boot Windows 7 & Android x86
PROMPT 0
TIMEOUT 30
#Win7 [Partition 2, NTFS, Primary, Data]
LABEL Win7
MENU LABEL Windows 7
MENU INDENT 1
KERNEL chain.c32
APPEND hd0,1
COM32 /multiboot/chain.c32 fs ntldr=/bootmgr
#end Windows.7
#start androidx86-kk-4.4.2_r1 [Partition 1, Fat32, Primary, Boot]
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
#end androidx86-kk-4.4.2_r1
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-10 07:35:24 UTC
Permalink
BROADCOM TEST BUILDS AVAILABLE
(using latest git builds)

These builds include Broadcom b43 and sta drivers with kernel 4.0, only
have one test card,
Broadcom 802.11g Wifi PCI Card,linksys WMP54G,tested fine(limited
testing)..NEED MORE TESTING.


---- FOR TESTING PURPOSES ONLY----

********************************************************************
WARNING: be advised that:
- These changes may contain bugs that could DAMAGE your hardware and/or
cause DATA LOSS.

- The .iso was simply tested for boot and connectivity checked, browser
check using WiFi...
- The updated .img file is untested...

Use it AT YOUR OWN RISK. YOU WERE ADVISED
********************************************************************

Testing feedback is welcomed....no guaranties on any fixes...info can be
provided
as it's time for younger people to step up and work / fix issues........



https://drive.google.com/folderview?id=0B2evBKvIpdYkfmxDRl84ajl3eVphaEZvZEdkSzkzOEZFSnRFUU1UNjNYRmtkQnlfVW1Fdms&usp=sharing#list
Post by Saipudin Haris
Currently only Android x86 4.4 r1 by cwhuang
<http://www.google.com/url?q=http%3A%2F%2Fsourceforge.net%2Fu%2Fcwhuang%2F&sa=D&sntz=1&usg=AFQjCNGWWsjKjFAXoM2MgGzYEGMgQNFv6w>
(
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download)
has a working Wifi driver (Broadcom 4331) for my Macbook Pro 8,1
here are the proof -----> http://valid.canardpc.com/a/5a8idy
I have tried these, and some of these build are working just fine on my
macbook pro 8,1 except that none of these have a working broadcom 4331
LATEST-GIT-TEST-BUILDS, link provided by rb g
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing)
and
Android-x86 lollipop, link provided by Mario Holzinger
(
https://drive.google.com/folderview?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
)
====================================================
below is working my usb boot parameter with persistent mode enabled
====================================================
#start androidx86-kk-4.4.2_r1
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
SDCARD=/multiboot/linux/androidx86/sdcard.img
#end androidx86-kk-4.4.2_r1
#start androidx86-kk-4.4.2_r2
LABEL androidx86-kk-4.4.2_r2
MENU LABEL Android x86 v4.4.2-r2-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r2/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r2/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r2/
#end androidx86-kk-4.4.2_r2
#start androidx86-4.4.4_3.18.8
LABEL androidx86-4.4.4_3.18.8
MENU LABEL Android x86 v4.4.4_3.18.8-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/
#end androidx86-4.4.4_3.18.8
#start androidx86-4.4.4_4.0
LABEL androidx86-4.4.4_4.0
MENU LABEL Android x86 v4.4.4_4.0-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_4.0/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_4.0/
#end androidx86-4.4.4_4.0
#start androidx86-lp-5.1.1
LABEL androidx86-lp-5.1.1
MENU LABEL Android x86 v5.1.1-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1/
#end androidx86-lp-5.1.1
#start androidx86-lp-5.1.1_3.18.8
LABEL androidx86-lp-5.1.1_3.18.8
MENU LABEL Android x86 v5.1.1_3.18.8-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/
#end androidx86-lp-5.1.1_3.18.8
#start androidx86-lp-5.1.1_4.0
LABEL androidx86-lp-5.1.1_4.0
MENU LABEL Android x86 v5.1.1_4.0-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_4.0/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_4.0/
#end androidx86-lp-5.1.1_4.0
==============
==============
filesystem: fat32
folder structure: /multiboot/linux/androidx86/*code/*version
/multiboot/linux/androidx86/*code/*version/kernel ---- [android x86 kernel]
/multiboot/linux/androidx86/*code/*version/initrd.img ---- [android x86
initrd image]
/multiboot/linux/androidx86/*code/*version/ramdisk.img ---- [android x86
ramdisk image]
/multiboot/linux/androidx86/*code/*version/system.img ---- [unsquashed
android x86 root file system, required for root file system modification]
/multiboot/linux/androidx86/*code/*version/data.img ---- [persistent
storage, ext2 file system, for application/internal persistent storage
purpose, created using PDL Casper-RW Creator is ©2009 Lance
http://www.pendrivelinux.com and renamed the output file from casper-rw
to data.img. For data.img partition resizing, I use TopoResize 0.7.1 by
Chris Semler.]
===============================
===============================
#syslinux install parameter for dual boot Windows 7 & Android x86
#syslinux.cfg parameter for dual boot Windows 7 & Android x86
PROMPT 0
TIMEOUT 30
#Win7 [Partition 2, NTFS, Primary, Data]
LABEL Win7
MENU LABEL Windows 7
MENU INDENT 1
KERNEL chain.c32
APPEND hd0,1
COM32 /multiboot/chain.c32 fs ntldr=/bootmgr
#end Windows.7
#start androidx86-kk-4.4.2_r1 [Partition 1, Fat32, Primary, Boot]
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
#end androidx86-kk-4.4.2_r1
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-10 21:04:02 UTC
Permalink
Hi rbg,


Wifi works great!, thanks.


I've uploaded the test log to:

https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing

for:

1. android_x86-4.4-r2_BCOM-20150610.iso
(https://drive.google.com/uc?id=0B2evBKvIpdYkc0J6a1B0dFFybDg&export=download)

2. android_x86-4.4-r2_BCOM-64bitKRNL_32bitUSR-20150610.iso
(https://drive.google.com/uc?id=0B2evBKvIpdYkWjhqYkJrTUtaNVU&export=download)

3. android_x86-4.4-r2_BCOM-20150610.img
(https://drive.google.com/uc?id=0B2evBKvIpdYkaGhGMWtxc29qNDA&export=download)

which i capture on my macbook pro 8,1 using the following command in a rooted terminal window:

# alsa_aplay -l > alsa_aplay_l.txt
# bugreport > bugreport.txt
# cat > /proc/asound/cards > proc_asound_cards.txt
# cat > /proc/asound/modules > proc_asound_modules.txt
# cat > /proc/cpuinfo > proc_cpuinfo.txt
# cat > /proc/modules > proc_modules.txt
# cat > /proc/net/dev > proc_net_dev.txt
# cat > /proc/net/wireless > proc_net_wireless.txt
# dmesg > dmesg.txt
# getprop > prop.txt
# logcat -v time -d > logcat.txt
# logcat -v time -b events -d > logcat_events.txt
# logcat -v time -b main -d > logcat_main.txt
# logcat -v time -b radio -d > logcat_radio.txt
# logcat -v time -b system -d > logcat_system.txt
# logcat -d | grep -i wifi > logcat_wifi.txt
# lspci -k > lspci_k.txt
# lsusb -k > lsusb_k.txt
# lsmod | grep bcma > lsmod_grep_bcma.txt
# lsmod | grep b43 > lsmod_grep_b43.txt
# modinfo bcma > modinfo_bcma.txt
# modinfo b43 > modinfo_b43.txt
# netcfg > netcfg.txt
# ps > ps.txt
# service list > service_list.txt
# uname -a > uname.txt


I hope, the attached logs can be a little help in further developing Android x86 project.

Thanks.


NB:
- When first bootup into Android x86 running in full charged battery, the battery status shown a red lighting (looks like 0% percent battery) but after restart the issue disappear and work normally. This issue only happened once.
- Photo capture resulting 0 KB file. Video capture OK.
- When click network settings from notification bar, instantly crashed android settings.
- Is it possible to add a reset button next to shutdown button in notification bar?
Post by rbg
BROADCOM TEST BUILDS AVAILABLE
                   (using latest git builds)
These builds include Broadcom b43 and sta drivers with kernel 4.0, only have one test card,
Broadcom 802.11g Wifi PCI Card,linksys WMP54G,tested fine(limited testing)..NEED MORE TESTING.
         ---- FOR TESTING PURPOSES ONLY----
********************************************************************
 - These changes may contain bugs that could DAMAGE your hardware and/or cause DATA LOSS.
 - The .iso was simply tested for boot and connectivity checked, browser check using WiFi...
 - The updated .img file is untested...
Use it AT YOUR OWN RISK. YOU WERE ADVISED
********************************************************************
Testing feedback is welcomed....no guaranties on any fixes...info can be provided
as it's time for younger people to step up and work / fix issues........
  https://drive.google.com/folderview?id=0B2evBKvIpdYkfmxDRl84ajl3eVphaEZvZEdkSzkzOEZFSnRFUU1UNjNYRmtkQnlfVW1Fdms&usp=sharing#list
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-11 04:34:51 UTC
Permalink
He has only tested the wl driver, I have also enabled the b43 driver stuff
and feel maybe we should get more testing
by others because of possible conflicts......

Will provide patches if you disagree with waiting of more testing?
Post by Saipudin Haris
Post by Saipudin Haris
Hi rbg,
Wifi works great!, thanks.
https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing
Good work.
So the b43 driver works for you?
Hi rbg, please send me the patch. Thanks!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-11 05:22:38 UTC
Permalink
In checking his logs I see you are correct again...he is using the b43
driver....

all the info I found said that chip 4331 was only supported by the wl
driver...???

so maybe the wl driver stuff isn't needed after all????
Post by rbg
He has only tested the wl driver, I have also enabled the b43 driver stuff
and feel maybe we should get more testing
by others because of possible conflicts......
Will provide patches if you disagree with waiting of more testing?
Post by Saipudin Haris
Post by Saipudin Haris
Hi rbg,
Wifi works great!, thanks.
https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing
Good work.
So the b43 driver works for you?
Hi rbg, please send me the patch. Thanks!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-11 05:13:26 UTC
Permalink
Hi Chih-Wei & rbg,


It works like a charm.


[# dmesg > dmesg.txt]

<6>[ 41.642691] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
<6>[ 42.901819] wlan0: authenticate with a4:99:47:f8:47:3c
<6>[ 42.922967] wlan0: send auth to a4:99:47:f8:47:3c (try 1/3)
<6>[ 42.924683] wlan0: authenticated
<6>[ 42.925919] wlan0: associate with a4:99:47:f8:47:3c (try 1/3)
<6>[ 42.929058] wlan0: RX AssocResp from a4:99:47:f8:47:3c (capab=0x431 status=0 aid=3)
<6>[ 42.929515] wlan0: associated
<6>[ 42.929595] cfg80211: Calling CRDA to update world regulatory domain


[# getproc > getproc.txt]

[dhcp.wlan0.dns1]: [208.67.222.222]
[dhcp.wlan0.dns2]: [208.67.220.220]
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: []
[dhcp.wlan0.gateway]: [192.168.1.1]
[dhcp.wlan0.ipaddress]: [192.168.1.5]
[dhcp.wlan0.leasetime]: [-1]
[dhcp.wlan0.mask]: [255.255.255.0]
[dhcp.wlan0.mtu]: []
[dhcp.wlan0.pid]: [2640]
[dhcp.wlan0.reason]: [ROUTERADVERT]
[dhcp.wlan0.result]: [ok]
[dhcp.wlan0.server]: [192.168.1.1]
[dhcp.wlan0.vendorInfo]: []

[wlan.interface]: [wlan0]
[wlan.modname]: [b43]



[# lsmod | grep b43 > lsmod_grep_b43.txt]

b43 344632 0 - Live 0x00000000
mac80211 409102 1 b43, Live 0x00000000
cfg80211 377402 2 b43,mac80211, Live 0x00000000
ssb 34207 1 b43, Live 0x00000000
rng_core 4530 1 b43, Live 0x00000000
bcma 35969 1 b43, Live 0x00000000



[# modinfo b43 > modinfo_b43.txt]

filename: kernel/drivers/net/wireless/b43/b43.ko
license: GPL
author: Rafał Miłecki
author: Michael Buesch
author: Martin Langer
description: Broadcom B43 wireless driver
alias: ssb:v4243id0812rev10*
alias: ssb:v4243id0812rev0D*
alias: ssb:v4243id0812rev0B*
alias: ssb:v4243id0812rev09*
alias: ssb:v4243id0812rev06*
alias: bcma:m04BFid0812rev2Acl*
alias: bcma:m04BFid0812rev1Ecl*
alias: bcma:m04BFid0812rev1Ccl*
alias: bcma:m04BFid0812rev17cl*
srcversion: B9834295EAD16862836C844
depends: bcma,ssb,mac80211,cfg80211,rng-core
vermagic: 4.0.0-android-x86+ SMP preempt mod_unload modversions PENTIUMM
parm: allhwsupport:Enable support for all hardware (even it if overlaps with the brcmsmac driver)
parm: pio:Use PIO accesses by default: 0=DMA, 1=PIO
parm: verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug
parm: btcoex:Enable Bluetooth coexistence (default on)
parm: qos:Enable QOS support (default on)
parm: hwtkip:Enable hardware tkip.
parm: nohwcrypt:Disable hardware encryption.
parm: hwpctl:Enable hardware-side power control (default off)
parm: fwpostfix:Postfix for the .fw files to load.
parm: bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption
firmware: b43/ucode9.fw
firmware: b43/ucode16_mimo.fw
firmware: b43/ucode14.fw
firmware: b43/ucode11.fw



[# logcat - d | grep -i wifi > logcat_wifi.txt]

D/ConnectivityService( 1970): wifiOnly=false
I/WifiService( 1970): WifiService starting up with Wi-Fi disabled
D/SubSettings( 2275): Launching fragment com.android.settings.wifi.WifiSettings
D/WifiService( 1970): setWifiEnabled: true pid=2275, uid=1000
E/WifiStateMachine( 1970): Failed to reload STA firmware java.lang.IllegalArgumentException: command '7 softap fwreload wlan0 STA' failed with '501 7 SoftAP command has failed'
D/WifiMonitor( 1970): startMonitoring(wlan0) with mConnected = false
D/WifiConfigStore( 1970): Loading config and enabling all networks
E/WifiStateMachine( 1970): Unexpected BatchedScanResults :OK
D/WifiStateMachine( 1970): VerifyingLinkState enter
D/WifiStateMachine( 1970): VerifyingLinkState GOOD_LINK_DETECTED: transition to captive portal check
D/WifiStateMachine( 1970): CaptivePortalCheckState enter
D/WifiStateMachine( 1970): CaptivePortalCheckState CMD_CAPTIVE_CHECK_COMPLETE
D/ConnectivityService( 1970): Captive portal check NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1970): handleCaptivePortalTrackerCheck: call captivePortalCheckComplete ni=NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1970): Captive portal check NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1970): handleCaptivePortalTrackerCheck: call captivePortalCheckComplete ni=NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1970): ConnectivityE/ConnectivityService( 1970): Unexpected mtu value: ***@217f0a84
D/ConnectivityService( 1970): ConnectivityChange for WIFI: CONNECTED/CONNECTED
E/ConnectivityService( 1970): Unexpected mtu value: ***@217f0a84Change for WIFI: CONNECTED/CONNECTED
D/CaptivePortalTracker( 1970): NoActiveNetworkState{ when=0 what=1 obj=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
D/CaptivePortalTracker( 1970): DelayedCaptiveCheckState{ when=-1ms what=1 obj=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
D/CaptivePortalTracker( 1970): Not captive network NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/CaptivePortalTracker( 1970): notifyPortalCheckCompleted: captive=false ni=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1970): captivePortalCheckCompleted: ni=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false captive=false



[netcfg > netcfg.txt]

wlan0 UP 192.168.1.5/24 0x00001043 b8:8d:12:1c:ed:ba
eth0 UP 0.0.0.0/0 0x00001003 3c:07:54:2f:08:3f
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00


[#cat /proc/net/wireless > proc_net_wireless.txt]
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlan0: 0000 58. -52. -256 0 0 0 0 19 0



[# cat /proc/net/dev > proc_net_dev.txt]

Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
wlan0: 7820 92 0 0 0 0 0 0 5193 46 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ip6tnl0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



more detail, please see the logs i've uploaded to:
https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing


Thanks.
Post by Saipudin Haris
Post by Saipudin Haris
Hi rbg,
Wifi works great!, thanks.
https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing
Good work.
So the b43 driver works for you?
Hi rbg, please send me the patch. Thanks!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-11 18:56:45 UTC
Permalink
essentially after going to my backups for 4.4-r1, sept-oct 2014 time-frame..
I have just reconstructed the work that was done previously.....

the patches have been supplied.
Post by Saipudin Haris
Post by Saipudin Haris
Hi rbg,
Wifi works great!, thanks.
https://drive.google.com/folderview?id=0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU&usp=sharing
Good work.
So the b43 driver works for you?
Hi rbg, please send me the patch. Thanks!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-06-23 03:38:31 UTC
Permalink
BROADCOM WiFi is now integrated into the Latest-Git-Test-Builds for KitKat
here:


https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list
Post by rbg
BROADCOM TEST BUILDS AVAILABLE
(using latest git builds)
These builds include Broadcom b43 and sta drivers with kernel 4.0, only
have one test card,
Broadcom 802.11g Wifi PCI Card,linksys WMP54G,tested fine(limited
testing)..NEED MORE TESTING.
---- FOR TESTING PURPOSES ONLY----
********************************************************************
- These changes may contain bugs that could DAMAGE your hardware and/or
cause DATA LOSS.
- The .iso was simply tested for boot and connectivity checked, browser
check using WiFi...
- The updated .img file is untested...
Use it AT YOUR OWN RISK. YOU WERE ADVISED
********************************************************************
Testing feedback is welcomed....no guaranties on any fixes...info can be
provided
as it's time for younger people to step up and work / fix issues........
https://drive.google.com/folderview?id=0B2evBKvIpdYkfmxDRl84ajl3eVphaEZvZEdkSzkzOEZFSnRFUU1UNjNYRmtkQnlfVW1Fdms&usp=sharing#list
Post by Saipudin Haris
Currently only Android x86 4.4 r1 by cwhuang
<http://www.google.com/url?q=http%3A%2F%2Fsourceforge.net%2Fu%2Fcwhuang%2F&sa=D&sntz=1&usg=AFQjCNGWWsjKjFAXoM2MgGzYEGMgQNFv6w>
(
http://sourceforge.net/projects/android-x86/files/Release%204.4/android-x86-4.4-r1.iso/download)
has a working Wifi driver (Broadcom 4331) for my Macbook Pro 8,1
here are the proof -----> http://valid.canardpc.com/a/5a8idy
I have tried these, and some of these build are working just fine on my
macbook pro 8,1 except that none of these have a working broadcom 4331
LATEST-GIT-TEST-BUILDS, link provided by rb g
(
https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing)
and
Android-x86 lollipop, link provided by Mario Holzinger
(
https://drive.google.com/folderview?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM&usp=sharing
)
====================================================
below is working my usb boot parameter with persistent mode enabled
====================================================
#start androidx86-kk-4.4.2_r1
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
SDCARD=/multiboot/linux/androidx86/sdcard.img
#end androidx86-kk-4.4.2_r1
#start androidx86-kk-4.4.2_r2
LABEL androidx86-kk-4.4.2_r2
MENU LABEL Android x86 v4.4.2-r2-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r2/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r2/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r2/
#end androidx86-kk-4.4.2_r2
#start androidx86-4.4.4_3.18.8
LABEL androidx86-4.4.4_3.18.8
MENU LABEL Android x86 v4.4.4_3.18.8-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_3.18.8/
#end androidx86-4.4.4_3.18.8
#start androidx86-4.4.4_4.0
LABEL androidx86-4.4.4_4.0
MENU LABEL Android x86 v4.4.4_4.0-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.4_4.0/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.4_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.4_4.0/
#end androidx86-4.4.4_4.0
#start androidx86-lp-5.1.1
LABEL androidx86-lp-5.1.1
MENU LABEL Android x86 v5.1.1-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1/
#end androidx86-lp-5.1.1
#start androidx86-lp-5.1.1_3.18.8
LABEL androidx86-lp-5.1.1_3.18.8
MENU LABEL Android x86 v5.1.1_3.18.8-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_3.18.8/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_3.18.8/
#end androidx86-lp-5.1.1_3.18.8
#start androidx86-lp-5.1.1_4.0
LABEL androidx86-lp-5.1.1_4.0
MENU LABEL Android x86 v5.1.1_4.0-lp-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/lp/5.1.1_4.0/kernel
append initrd=/multiboot/linux/androidx86/lp/5.1.1_4.0/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/lp/5.1.1_4.0/
#end androidx86-lp-5.1.1_4.0
==============
==============
filesystem: fat32
folder structure: /multiboot/linux/androidx86/*code/*version
/multiboot/linux/androidx86/*code/*version/kernel ---- [android x86 kernel]
/multiboot/linux/androidx86/*code/*version/initrd.img ---- [android x86
initrd image]
/multiboot/linux/androidx86/*code/*version/ramdisk.img ---- [android x86
ramdisk image]
/multiboot/linux/androidx86/*code/*version/system.img ---- [unsquashed
android x86 root file system, required for root file system modification]
/multiboot/linux/androidx86/*code/*version/data.img ---- [persistent
storage, ext2 file system, for application/internal persistent storage
purpose, created using PDL Casper-RW Creator is ©2009 Lance
http://www.pendrivelinux.com and renamed the output file from casper-rw
to data.img. For data.img partition resizing, I use TopoResize 0.7.1 by
Chris Semler.]
===============================
===============================
#syslinux install parameter for dual boot Windows 7 & Android x86
#syslinux.cfg parameter for dual boot Windows 7 & Android x86
PROMPT 0
TIMEOUT 30
#Win7 [Partition 2, NTFS, Primary, Data]
LABEL Win7
MENU LABEL Windows 7
MENU INDENT 1
KERNEL chain.c32
APPEND hd0,1
COM32 /multiboot/chain.c32 fs ntldr=/bootmgr
#end Windows.7
#start androidx86-kk-4.4.2_r1 [Partition 1, Fat32, Primary, Boot]
LABEL androidx86-kk-4.4.2_r1
MENU LABEL Android x86 v4.4.2-r1-kk-generic
MENU INDENT 1
kernel /multiboot/linux/androidx86/kk/4.4.2_r1/kernel
append initrd=/multiboot/linux/androidx86/kk/4.4.2_r1/initrd.img
root=/dev/ram0 androidboot.hardware=android_x86 USE_SQUASHFS=0
SRC=/multiboot/linux/androidx86/kk/4.4.2_r1/
#end androidx86-kk-4.4.2_r1
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Saipudin Haris
2015-06-24 03:05:54 UTC
Permalink
Hi rbg,


i've tested the latest kitkat test build:

1. android_x86-4.4-r2-64bitKRNL_32bitUSR-20150623.iso
2. android_x86-4.4-r2-20150623.img
3. android_x86-4.4-r2-20150623.iso

the wifi works great. also i've uploaded the test log to:


https://drive.google.com/drive/folders/0B2WvSssMmRNwfkhNMkxncVhwY2lPZFBlUkU1eFFteERoaUJockhmU1dNNXdzNDdmYm1DWVU



below are the brief info:
========================

# dmesg > dmesg.txt [android_x86-4.4-r2-20150623.iso]
==========================================
<6>[ 7.766198] cfg80211: Calling CRDA to update world regulatory domain
<6>[ 7.800677] applesmc: key=380 fan=1 temp=24 index=23 acc=1 lux=2 kbd=1
<6>[ 7.862837] input: applesmc as /devices/platform/applesmc.768/input/input18
<6>[ 7.904933] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
<6>[ 7.905390] b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
<6>[ 7.905407] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2059, Revision 0, Version 1
<4>[ 7.905412] b43-phy0 warning: 5 GHz band is unsupported on this PHY
<6>[ 7.906088] Broadcom 43xx driver loaded [ Features: PNL ]
<7>[ 8.237733] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<4>[ 8.450199] wl: module license 'unspecified' taints kernel.
<4>[ 8.450209] Disabling lock debugging due to kernel taint

<6>[ 79.293615] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
<6>[ 94.390981] wlan0: authenticate with a4:99:47:f8:47:3c
<6>[ 94.402551] wlan0: send auth to a4:99:47:f8:47:3c (try 1/3)
<6>[ 94.406990] wlan0: authenticated
<6>[ 94.407378] wlan0: associate with a4:99:47:f8:47:3c (try 1/3)
<6>[ 94.410453] wlan0: RX AssocResp from a4:99:47:f8:47:3c (capab=0x431 status=0 aid=1)
<6>[ 94.410920] wlan0: associated
<6>[ 94.411070] cfg80211: Calling CRDA to update world regulatory domain




# logcat -d | grep -i wifi > logcat_wifi.txt [android_x86-4.4-r2-20150623.iso]
==========================================
D/ConnectivityService( 1963): wifiOnly=false
I/WifiService( 1963): WifiService starting up with Wi-Fi disabled
I/ActivityManager( 1963): START u0 {act=android.settings.WIFI_SETTINGS flg=0x14000000 cmp=com.android.settings/.Settings$WifiSettingsActivity} from pid 2023
I/ActivityManager( 1963): Displayed com.android.settings/.Settings$WifiSettingsActivity: +158ms
D/WifiService( 1963): setWifiEnabled: true pid=2068, uid=1000
E/WifiStateMachine( 1963): Failed to reload STA firmware java.lang.IllegalArgumentException: command '7 softap fwreload wlan0 STA' failed with '501 7 SoftAP command has failed'
D/WifiMonitor( 1963): startMonitoring(wlan0) with mConnected = false
D/WifiConfigStore( 1963): Loading config and enabling all networks
E/WifiConfigStore( 1963): Error parsing configurationjava.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
E/WifiStateMachine( 1963): Unexpected BatchedScanResults :OK
D/WifiStateMachine( 1963): VerifyingLinkState enter
D/WifiStateMachine( 1963): VerifyingLinkState GOOD_LINK_DETECTED: transition to captive portal check
D/WifiStateMachine( 1963): CaptivePortalCheckState enter
D/ConnectivityService( 1963): Captive portal check NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/WifiStateMachine( 1963): CaptivePortalCheckState CMD_CAPTIVE_CHECK_COMPLETE
D/ConnectivityService( 1963): handleCaptivePortalTrackerCheck: call captivePortalCheckComplete ni=NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1963): Captive portal check NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1963): handleCaptivePortalTrackerCheck: call captivePortalCheckComplete ni=NetworkInfo: type: WIFI[], state: CONNECTING/CAPTIVE_PORTAL_CHECK, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1963): ConnectivityChange for WIFI: CONNECTED/CONNECTED
E/ConnectivityService( 1963): Unexpected mtu value: ***@217a7b58
D/ConnectivityService( 1963): ConnectivityChange for WIFI: CONNECTED/CONNECTED
E/ConnectivityService( 1963): Unexpected mtu value: ***@217a7b58
D/CaptivePortalTracker( 1963): NoActiveNetworkState{ when=0 what=1 obj=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
D/CaptivePortalTracker( 1963): DelayedCaptiveCheckState{ when=0 what=1 obj=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false target=com.android.internal.util.StateMachine$SmHandler }
D/CaptivePortalTracker( 1963): Not captive network NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/CaptivePortalTracker( 1963): notifyPortalCheckCompleted: captive=false ni=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
D/ConnectivityService( 1963): captivePortalCheckCompleted: ni=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: "Rumah", roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false captive=false




# netcfg > netcfg.txt [android_x86-4.4-r2-20150623.iso]
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
eth0 UP 0.0.0.0/0 0x00001003 3c:07:54:2f:08:3f
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
wlan0 UP 192.168.1.7/24 0x00001043 b8:8d:12:1c:ed:ba



# cat /proc/modules > proc_modules.txt [android_x86-4.4-r2-20150623.iso]
binfmt_misc 7095 1 - Live 0x00000000
wl 6129558 0 - Live 0x00000000 (P)
b43 344548 0 - Live 0x00000000
joydev 6700 0 - Live 0x00000000
mac80211 408518 1 b43, Live 0x00000000
cfg80211 377218 3 wl,b43,mac80211, Live 0x00000000
kvm_intel 127284 0 - Live 0x00000000
kvm 330706 1 kvm_intel, Live 0x00000000
applesmc 9119 0 - Live 0x00000000
input_polldev 4171 1 applesmc, Live 0x00000000
ssb 34191 1 b43, Live 0x00000000
rng_core 4518 1 b43, Live 0x00000000
mac_hid 2731 0 - Live 0x00000000
pppoe 6650 0 - Live 0x00000000
uvcvideo 56347 0 - Live 0x00000000
videobuf2_vmalloc 3753 1 uvcvideo, Live 0x00000000
videobuf2_memops 2150 1 videobuf2_vmalloc, Live 0x00000000
videobuf2_core 30119 1 uvcvideo, Live 0x00000000
bcm5974 7491 0 - Live 0x00000000
pcspkr 1354 0 - Live 0x00000000
bcma 35921 1 b43, Live 0x00000000
tg3 118907 0 - Live 0x00000000
ptp 8621 1 tg3, Live 0x00000000
pps_core 7966 1 ptp, Live 0x00000000
libphy 26158 1 tg3, Live 0x00000000
hwmon 3329 2 applesmc,tg3, Live 0x00000000
i2c_i801 13573 0 - Live 0x00000000
lpc_ich 12133 0 - Live 0x00000000
snd_hda_codec_hdmi 33072 1 - Live 0x00000000
snd_hda_codec_cirrus 8048 1 - Live 0x00000000
snd_hda_codec_generic 42370 1 snd_hda_codec_cirrus, Live 0x00000000
snd_hda_intel 20180 0 - Live 0x00000000
snd_hda_controller 19108 1 snd_hda_intel, Live 0x00000000
snd_hda_codec 93342 5 snd_hda_codec_hdmi,snd_hda_codec_cirrus,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller, Live 0x00000000
snd_hwdep 4223 1 snd_hda_codec, Live 0x00000000
snd_pcm 68470 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_controller,snd_hda_codec, Live 0x00000000
snd_timer 14998 1 snd_pcm, Live 0x00000000
snd 48461 8 snd_hda_codec_hdmi,snd_hda_codec_cirrus,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer, Live 0x00000000
soundcore 4971 2 snd_hda_codec,snd, Live 0x00000000
i915 776046 14 - Live 0x00000000
drm_kms_helper 78627 1 i915, Live 0x00000000
drm 242119 16 i915,drm_kms_helper, Live 0x00000000
i2c_algo_bit 4301 1 i915, Live 0x00000000
shpchp 19423 0 - Live 0x00000000
hid_appleir 2095 0 - Live 0x00000000
hid_apple 4453 0 - Live 0x00000000
apple_gmux 4945 0 - Live 0x00000000
apple_bl 3563 1 apple_gmux, Live 0x00000000
sbs 6195 0 - Live 0x00000000
sbshc 4545 1 sbs, Live 0x00000000





NB:
1. for the test logs for BROADCOM kitkat & lolipop builds before merged to the latest git test build, i've uploaded to:


https://drive.google.com/drive/folders/0B2WvSssMmRNwfldHN0VrZGEwME1SOXB4VEZwbGhMeFBoeHdpYVMwS1B5bFFLd1lPMmhWRVE


2. the android_x86-5.1.1_BCOM-20150614.img build, always reboot my macbook after showing message "ANDROID rootx86#", so I can't provide you any test logs. I've tried to enter DEBUG mode, but it always hangs/stuck after showing "....found on /sda1".
     https://drive.google.com/folderview?id=0B2evBKvIpdYkfm1EdmFtUUc1QjA5dmlLMXlEaEJyQ29wc1VtbDRQa2YyOXlJdjZFUWRFckk&usp=sharing#list
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Loading...