On Tue, Mar 1, 2011 at 10:39 AM, Tapas Mishra <mightydreams@xxxxxxxxx> wrote:
> On Tue, Mar 1, 2011 at 10:01 AM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
>> On Tue, Mar 1, 2011 at 11:22 AM, Tapas Mishra <mightydreams@xxxxxxxxx> wrote:
>>>> Is there a way to undo things specially for the make commands?
>>> Ok I read the Makefile
>>> /mnt/1/fajar/xen-4.0.1/Makefile
>>> and found make clean and make uninstall have done the job.(Correct me
>>> if I am mistaken here)
>>> I think I need to rebuild the kernel 2.6.32.27 and xen etc from here on.
>>
>> Since you're able to run "xm", you should only need to recompile the
>> kernel. Start with setting the options I sent to "y" (if it's
>> available, just ignore the ones that doesn't exist on your kernel).
>>
> Ok I was thinking of copying your .config options from this thread to
> the .config of mine if I do that would it be wrong?
> Since you mentioned to ignore the ones that don't exist on my kernel.
>
> Also I found when doing make install-tools
> the git pull was happening from
> buildconfigs/src.git-clone
> so I have commented these lines
>
>
> # rm -rf $(LINUX_SRCDIR) $(LINUX_SRCDIR).tmp; \
> # mkdir $(LINUX_SRCDIR).tmp; rmdir $(LINUX_SRCDIR).tmp; \
> # $(GIT) clone -o $(XEN_GIT_ORIGIN) -n
> $(XEN_LINUX_GIT_URL) $(LINUX_SRCDIR).tmp; \
> # (cd $(LINUX_SRCDIR).tmp; git checkout -b
> $(XEN_LINUX_GIT_LOCALBRANCH) $(XEN_LINUX_GITREV) ); \
> # mv $(LINUX_SRCDIR).tmp $(LINUX_SRCDIR); \
>
>
> and from buildconfigs/mk.linux-2.6-common
>
>
> # rm -rf $(LINUX_DIR)
> # mkdir -p $(LINUX_DIR)
> # rm -rf tmp-linux-$(LINUX_VER) $(LINUX_DIR) $(LINUX_SRCDIR)
> # rm -rf $(LINUX_SRCDIR)
>
> and what I did is I have a copy of linux-2.6-pvops.git so I manually
> copied it to
> /mnt/1/fajar/xen-4.0.1
> and now restarting process of make install-tools
>
> so my question is above way of commenting out git pull lines and then
> putting them in xen source dir is wrong or can lead to wrong results?
> The only problem being I can not each time do a git pull and wait for
> 4 hours for 850 Mb to download.
> If this is not then I am proceeding this way and going to compile the
> new kernel.
>
Ok finally I am answering my question I have done the way I mentioned
above as git pull was costly.
Things have worked finally without any error and almost perfectly.
for tools I had to use
make install-tools PYTHON_PREFIX_ARG=
and after that I rebooted
xm info shows
host : tapas
release : 2.6.32.27
version : #1 SMP Tue Mar 1 12:52:19 IST 2011
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2100
hw_caps :
bfebfbff:20100800:00000000:00000940:0408e39d:00000000:00000001:00000000
virt_caps :
total_memory : 3036
free_memory : 128
node_to_cpu : node0:0-1
node_to_memory : node0:128
node_to_dma32_mem : node0:128
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dummy=dummy
cc_compiler : gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Tue Mar 1 10:51:33 IST 2011
xend_config_format : 4
and
xm list shows
Name ID Mem VCPUs State Time(s)
Domain-0 0 2870 2 r----- 36.9
Let me know if any one sees any error here.I think upto here things
are absolutely perfect.
I have used the .config file you mentioned in this thread and was able
to get all options as you mentioned.
For just sake of information I am mentioning what I got in xen.log
http://pastebin.com/ZJ9BCMLq
and xend-debug.log
http://pastebin.com/C6DQ5DP3
I was able to get Dom0 booting.
I wish if after this I can use my wireless also in Dom0.
The device on Dom0 I has PCI Id 14e4:4315
when booted with this new kernel pv-ops Dom0 kernel 2.6.32.27 checked
lspci -vnn
it shows
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11b/g [14e4:4315] (rev 01)
Subsystem: Dell Device [1028:000c]
Flags: bus master, fast devsel, latency 0, IRQ 4
Memory at f69fc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [13c] Virtual Channel <?>
Capabilities: [16c] Power Budgeting <?>
Kernel modules: ssb
where as in the old kernel (which still is there with working wifi
this is without Xen)
lspci -vnn shows
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11b/g [14e4:4315] (rev 01)
Subsystem: Dell Device [1028:000c]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f69fc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [13c] Virtual Channel <?>
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: wl
Kernel modules: wl, ssb
In the above kernel the wifi works and you can see a wl driver in
use.How ever in the newly compiled pv-ops kernel I mentioned wl
driver is missing.Is there a way to load it from system some how or
what more can I do to get my wifi back.When I had installed Ubuntu
then while being connected from my LAN from Ubuntu 10.04 (64 bit) gui
I had installed driver
in (default 2.6.32.24 kernel)
System->Administration-->Hard Ware Drivers-->Broad Com STA driver I
but if I do the same in new 2.6.32.27 kernel which I compiled)
System->Administration-->Hard Ware Drivers-->Broad Com STA driver
get a failure message which says me to check
/var/log/jockey.log
and here is the jockey.log
http://pastebin.com/VBTLGw42
how ever I feel the problem is rather simple and some thing is missing.
/etc/modprobe.d/blacklist.conf I have
# replaced by b43 and ssb.
blacklist bcm43xx
also checked wl.ko driver in the old working kernel is at following location
/var/lib/dkms/bcmwl/5.60.48.36+bdcom/2.6.32-24-generic/x86_64/module/wl.ko
If you notice in above output it has path to 2.6.32-24-generic kernel.
I do not have any problem in using my wifi when I boot with
2.6.32.24 (which is what was installed during installation from Ubuntu CD)
but when I boot
2.6.32.27 (which I had compiled) I do not get my wireless back and
lspci shows above output as I mentioned where wl driver is missing.So
how can I get this back?
Is it possible to have some thing like
/var/lib/dkms/bcmwl/5.60.48.36+bdcom/2.6.32.27/x86_64/module/wl.ko
for new kernel that I compiled.Let me know how can I get beyond this
point.I feel this can give me the wifi back but how to go for this one
I am not clear.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home