[okl4-developer] Fwd: Ubuntu VMware VM with 2.1 loaded
Kalamkar, Dhiraj D
dhiraj.d.kalamkar at intel.com
Fri May 23 14:49:03 EST 2008
Yes, I had used L4 on VMWare and used both pcnet32 and e1000 driver in
OKLinux.
For e1000 you need to add following line to
linux/kernel-2.6.23-v2/include/asm-l4/i386/io.h
#define mmiowb()
With this it should work fine.
Regards,
Dhiraj
________________________________
From: Geoff White [mailto:netengadmin at gmail.com]
Sent: Friday, May 23, 2008 9:53 AM
To: Kalamkar, Dhiraj D
Subject: Re: [okl4-developer] Fwd: Ubuntu VMware VM with 2.1 loaded
Hi Dhiraj!
Did you ever get your driver working ?Were you trying to get e1000
working?
Thanks I'll try what you suggest.
On Thu, May 22, 2008 at 9:18 PM, Kalamkar, Dhiraj D
<dhiraj.d.kalamkar at intel.com> wrote:
Hi Geoff,
You don't need to comment out line 114 in arch/l4/Makefile. Just do
following:
#cp l4linux_config_ia32 .config
#make menuconfig ARCH=l4 SYSTEM=i368
#mv .config l4linux_config_ia32
#make mrproper
And rebuild OKL4. At least it worked for me fine.
Regards,
Dhiraj
________________________________
From: developer-bounces at okl4.org [mailto:developer-bounces at okl4.org] On
Behalf Of Geoff White
Sent: Friday, May 23, 2008 9:32 AM
To: developer
Subject: [okl4-developer] Fwd: Ubuntu VMware VM with 2.1 loaded
OK, so I have a VMware VM that talks to the Network!!!
I enabled the PCnet32 drivers in the OLLinux kernel (more on the
problems with this later) and rebuilt everything,and I was able to ping
mit.edu ;)
I did have issues building the new image however! I followed a modified
set of instructions that worked for 1.5.2, comment out line 114 in
.../arch/l4/Makefile
and run
make menuconfig
this worked fine but when I moved the .config file over to
l4linux_config_ia32, I had major problems building the resultant kernel.
Finally what I did is to take the original l4linux_config_ia32 and hand
edit it to include the PCnet32 driver, this didn't quite work, it
dropped into interactive mode during the build and I had to answer a
bunch of questions by hand. But in the end , the kernel built and I was
able to load it into a VMware VM and start it up and ping through the
interface! So my only question for now is what is wrong with make
menuconfig or what step do I need to do to get a working config?
Here is what it looks like when I build...
sound/isa/Kconfig:68:warning: 'select' used by config symbol
'SND_ALS100' refers to undefined symbol 'ISAPNP'
sound/isa/Kconfig:82:warning: 'select' used by config symbol
'SND_AZT2320' refers to undefined symbol 'ISAPNP'
sound/isa/Kconfig:146:warning: 'select' used by config symbol
'SND_DT019X' refers to undefined symbol 'ISAPNP'
sound/isa/Kconfig:160:warning: 'select' used by config symbol
'SND_ES968' refers to undefined symbol 'ISAPNP'
sound/pci/Kconfig:489:warning: 'select' used by config symbol
'SND_FM801_TEA575X' refers to undefined symbol 'VIDEO_V4L1'
sound/pci/Kconfig:490:warning: 'select' used by config symbol
'SND_FM801_TEA575X' refers to undefined symbol 'VIDEO_DEV'
*
* Restart config...
*
*
* Ethernet (10 or 100Mbit)
*
Ethernet (10 or 100Mbit) (NET_ETHERNET) [Y/n/?] y
Generic Media Independent Interface device support (MII) [Y/?] y
Sun Happy Meal 10/100baseT support (HAPPYMEAL) [N/m/y/?] n
Sun GEM support (SUNGEM) [N/m/y/?] n
Sun Cassini support (CASSINI) [N/m/y/?] n
3COM cards (NET_VENDOR_3COM) [N/y/?] n
HP 10/100VG PCLAN (ISA, EISA, PCI) support (HP100) [N/m/y/?] n
EISA, VLB, PCI and on board controllers (NET_PCI) [Y/n/?] y
AMD PCnet32 PCI support (PCNET32) [Y/n/m/?] y
Use RX polling (NAPI) (PCNET32_NAPI) [N/y/?] (NEW) y
AMD 8111 (new PCI lance) support (AMD8111_ETH) [Y/n/m/?] y
Enable NAPI support (AMD8111E_NAPI) [N/y/?] n
Adaptec Starfire/DuraLAN support (ADAPTEC_STARFIRE) [N/m/y/?] (NEW)
n
Broadcom 4400 ethernet support (B44) [N/m/y/?] (NEW) n
nForce Ethernet support (FORCEDETH) [N/m/y/?] (NEW) n
Digi Intl. RightSwitch SE-X support (DGRS) [N/m/y/?] (NEW) n
EtherExpressPro/100 support (eepro100, original Becker driver)
(EEPRO100) [N/m/y/?] (NEW) n
Intel(R) PRO/100+ support (E100) [N/m/y/?] (NEW) n
Myson MTD-8xx PCI Ethernet support (FEALNX) [N/m/y/?] (NEW) n
National Semiconductor DP8381x series PCI Ethernet support (NATSEMI)
[N/m/y/?] (NEW) n
(there were a few more but I didn't type them in.)
So my question is how do I get a .config (l4linux_config_ia32_vmw ) that
doesn't require interactive intervention?
so when it's built, I start it up and...
This architecture does not implement dump_stack()
Iguana virtual serial driver v1.0
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (ext2 filesystem) readonly.
vserial: init done (handle: 0, owner: 18001, mask: 2)
Linux user startup!
Mounted proc on /proc
Mounted sysfs on /sys
Mounted devpts on /dev/pts
no IDE disk image available
Configured net lo device
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=40.0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.0 ms
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.0/20.0/40.0 ms
eth0 Link encap:Ethernet HWaddr 00:0C:29:FC:77:6E
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0x1400
eth0: link up
configuring network for Linux wombat 2.6.23-i386l4_pc99 #2 Mon May 19
00:34:56 PDT 2008 i386 unknown
info, udhcpc (v0.9.9-pre) started
debug, Sending discover...
debug, Sending select for 192.168.127.130...
info, Lease of 192.168.127.130 obtained, lease time 1800
deleting routers
route: SIOC[ADD|DEL]RT: No such process
adding dns 192.168.127.2
net eth0 device configuration failed
*And We're Done!*
Please press Enter to activate this console.
BusyBox v1.00 (2008.05.19-04:45+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ # ping mit.edu
PING mit.edu (18.7.22.69): 56 data bytes
64 bytes from 18.7.22.69: icmp_seq=0 ttl=128 time=90.0 ms
64 bytes from 18.7.22.69: icmp_seq=1 ttl=128 time=90.0 ms
64 bytes from 18.7.22.69: icmp_seq=2 ttl=128 time=90.0 ms
64 bytes from 18.7.22.69: icmp_seq=3 ttl=128 time=90.0 ms
64 bytes from 18.7.22.69: icmp_seq=4 ttl=128 time=80.0 ms
64 bytes from 18.7.22.69: icmp_seq=5 ttl=128 time=90.0 ms
64 bytes from 18.7.22.69: icmp_seq=6 ttl=128 time=90.0 ms
--- mit.edu ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 80.0/88.5/90.0 ms
I'd like to get this build fully automated and then get it up on the
Wiki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080523/5e32f16a/attachment-0001.htm
More information about the Developer
mailing list