search for: pcnet32

The main modifications in the PCnet32 ethernet driver seems to be macro that test if COPYBREAK is define. I notice that for network driver which were written for Xen the main modifications was around the copybreak and also some adjustments with include files. Is it true if I say that the port of network device from Linux to Xen is quit...

...he client machine connects > > to host machine via vmnet1. I have dhcpd service on debian wheezy: > > root 8433 1 0 21:19 ? 00:00:00 /usr/sbin/dhcpd -q -cf > > /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid eth1 vmnet1 > > Thanks. > > vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware VMXNet3? Feel free to directly email me your .vmx file if you don't know. So that should be vlance or flexible (which can be PCNet32 or e1000). Could you verify with a real OS? I see it has two cores per socket. Is it one socket? What exact make/mode...

...der Windows XP SP2 1) Preparing boot floppy ======= syslinux.cfg content ====================== PROMPT 0 DISPLAY warning.txt DEFAULT kernel APPEND root=/dev/ram0 rw initrd=ukmrd.gz ramdisk_size=5000 bdev=/dev/fd0 ip=192.168.422.25 ipm=255.255.255.0 ipreq=n ipg=192.168.42.1 ipdns=192.168.42.2 mnet=pcnet32 durl=http://KP/ukminstall ============================================= After boot command line is truncated mnet=pcnet32 durl=http://KP/ukminstall variables are not passed to init 2) Preparing boot floppy with the win32 syslinux 3.52 and syslinux-3.52\com32\samples\linux.c32 module ======= s...

...39;, or ''c'' could include pxe as an option, but it''s unclear to me which order the NICs would try to boot in. Maybe all of the NICs with PXE ROMs in configuration order. It looks like Etherboot 5.4.2 has at least the beginnings of full PXE support for some drivers. AMD pcnet32 looked okay, but I don''t have a really demanding PXE environment for testing. Many thanks for your help! Andrew ===== Andrew D. Ball <aball@us dot ibm dot com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensou...

On 03/08/2014 10:06 PM, Gene Cumm wrote: >> Hi Gene, >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got >> > the same issue. My client machine >> > still only shows: >> > ==================== >> > Getting cached packets >> > My IP is 192.168.120.1 >> > ==================== >> > The syslog log

...Mar 9, 2014 at 8:09 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >>> >>> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >>> VMXNet3? Feel free to directly email me your .vmx file if you don't know. >> >> So that should be vlance or flexible (which can be PCNet32 or e1000). Could >> you verify with a real OS? > > I finally got the opport...

...IS900 client boots, it hang in -------------------------------- Trying to load : pxelinux.cfg/01-00-0c-76-e2-62-2f Trying to load : pxelinux.cfg/C0A8A803 .... .... Trying to load : pxelinux.cfg/default . <- stop here ------------- As for the same pxelinux.cfg/default, it works for e100, rtl8139, pcnet32. I tried to use simple.c32, and it works. Is that possible I can use pxelinux simple menu in the sis900 client in this coming version ? What info shall I provide so that you can make this magic happen ? Thanks. > > This test release includes the Multiboot support from Tim Deegan, and &...

Hello everybody, After going through multiple posts on Internet and trying different things I can't seems get zaptel wcfxo loaded on the server correctly. I run dual P3 500 Mhz box. After reading README.udev I put a file 60-zaptel.rules /etc/udev/rules.d # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer",

On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >> >> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >> VMXNet3? Feel free to directly email me your .vmx file if you don't know. > > So that should be vlance or flexible (which can be PCNet32 or e1000). Could > you verify with a real OS? I finally got the opportunity to test your VMX an...

... do not work anymore. Anybody with a hint? I''ve got a fully functional HTB setup and just wanted to replace the kernel from 2.4.17 to 2.4.19. In the end the modified tc binary doesn''t recognize "tc filter add" (yet it does accept qdisc show and recognizes htb...) I''ve downloaded the 2.4.19 from kernel.org, iproute2 (2.4.7), installed the patches

...dapter1 mptscsi alias scsi_hostadapter2 mptfc alias scsi_hostadapter3 mptspi alias scsi_hostadapter4 mptsas alias scsi_hostadapter5 mptscsih alias usb-controller uhci-hcd # Disable IPV6 alias net-pf-10 off alias ipv6 off # Added by VMware Tools install vmnics /sbin/modprobe vmxnet; /sbin/modprobe pcnet32; /bin/true alias char-major-14 sb options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 --------------------------------------------------------------------------------------- and like this on another --------------------------------------------------------------------------------------- alias eth0...

...th the virt-preview qemu on F11 host kernel +# https://bugzilla.redhat.com/show_bug.cgi?id=512358 +RPMS="$RPMS gpxe-roms-qemu" +ln -snf ../etherboot/e1000-82542.zrom /usr/share/qemu/pxe-e1000.bin +ln -snf ../etherboot/ne.zrom /usr/share/qemu/pxe-ne2k_pci.bin +ln -snf ../etherboot/pcnet32.zrom /usr/share/qemu/pxe-pcnet.bin +ln -snf ../etherboot/rtl8139.zrom /usr/share/qemu/pxe-rtl8139.bin +ln -snf ../etherboot/virtio-net.zrom /usr/share/qemu/pxe-virtio.bin + # Things we could probably remove if libvirt didn't link against them #RPMS="$RPMS avahi PolicyKit xen-lib...

I downloaded nilo and oskit from www.nilo.org. Added pcnet32.c linux-2.0.39 driver to oskit. Compiled nilo with pcnet32 and produced boot floppy image. Use it inside vmware vm. My aim is to be able to test pxelinux using vmware+nilo and not a real machine. Floppy starts, detects nic, receives ip from dhcp server, requests boot image to tftpd-hpa, then crash...

>>> ... Bottom line; There are timing issues with TFTP transfers on VM machines emulating BIOS hardware. Probably the interrupt based timer is not the culprit; now I'm working on /core/fs/pxe/core.c trying to see if there's something wrong there. Best, Patrick <<< I've been working on this issue, I have tested the timers, and as you guys mentioned before they

...i parport_pc parport snd_seq_midi_event snd_seq evdev container snd_timer snd_seq_device serio_raw snd ac power_supply soundcore snd_page_alloc psmouse button i2c_piix4 i2c_core pcspkr shpchp pci_hotplug intel_agp agpgart ext3 jbd mbcache sg sr_mod cdrom sd_mod ata_generic floppy ata_piix pata_acpi pcnet32 mii libata BusLogic scsi_mod thermal processor fan fuse <4>[45260.760017] <4>[45260.761431] Pid: 4510, comm: cp Not tainted (2.6.24-4-generic #1) <4>[45260.762595] EIP: 0060:[<c0164ce1>] EFLAGS: 00010206 CPU: 0 <4>[45260.765053] EIP is at should_remove_suid+0x1/0x50 &...

...domain.local nameserver 10.180.0.2 nameserver 10.180.0.4 network.erb ------------------ NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=<%= hostname %>.<%= environ %>.mydomain.local GATEWAY=<%= gateway %> ifcfg-eth0.erb ---------------- # Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] DEVICE=eth0 BOOTPROTO=static IPADDR=<%= ipaddress %> NETMASK=255.255.255.0 ONBOOT=yes HWADDR=<%= macaddress %> Gets kicked off using: basehost {''basehostsetup'': ipaddress => ''10.148.0.32'', gateway => ''10.148.0.1''...

So far v2v did not read the model of network interfaces, resulting in "virtio" as the model for such interfaces. Start reading the model, if available, mapping only E1000 for now. There are also other models, e.g. PCNet32 or VmxNet3, but they are ignored for now: reading them as Source_other_nic would result in v2v rejecting OVAs previously converted. --- v2v/parse_ovf_from_ova.ml | 7 ++++++- v2v/test-v2v-i-ova-formats.expected | 2 +- v2v/test-v2v-i-ova-gz.expected | 2 +- v2v/test-v2v-...

Hi, I''ve a working xen 3.0.2 booting a gentoo linux on Dom0. I have setup a Windows XP in a DomU OK with no problems except the network!! My problem is that I wanted to give a working network interface on the DomU and the best I could. making the windows detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu,

Hello, A preview of the qemu 0.8.1 based ioemu is now available at: http://xenbits.xensource.com/chris/add-ioemu-new and http://xenbits.xensource.com/chris/enable-ioemu-new In addition to these two patches, you need a copy of qemu-0.8.1 and place it into tools/ioemu-new -- one option is the tarball available at http://xenbits.xensource.com/chris/ioemu-cvs-qemu-0.8.1.tar.bz2 which extracts to

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene