Re: Typo in nfs_boot.c
2013/9/12 Eivind Evensen eivi...@terraplane.org: Hello. Trying to figure out what I've done wrong to have a diskless setup boot the kernel and then try to talk to a broadcast address rather than the nfsserver, I saw this typo. Eivind Hi, I think I have the same problem as, when booting a client, I get RPC timeout for server 192.168.100.255 how did you solve the problem of talking to a broadcast address? or, what am I doing wrong? Thanks -- Matteo Filippetto http://www.op83.eu
Re: Typo in nfs_boot.c
2013/12/30 matteo filippetto matteo.filippe...@gmail.com: 2013/9/12 Eivind Evensen eivi...@terraplane.org: Hello. Trying to figure out what I've done wrong to have a diskless setup boot the kernel and then try to talk to a broadcast address rather than the nfsserver, I saw this typo. Eivind Hi, I think I have the same problem as, when booting a client, I get RPC timeout for server 192.168.100.255 how did you solve the problem of talking to a broadcast address? or, what am I doing wrong? Thanks Ok, just solved the problem: start mountd at boot. Regards -- Matteo Filippetto http://www.op83.eu
Re: alc(4) support for Atheros AR815x
Hi, I have a eeepc 1001pxd with Attansic Technology L2C working and this patch didn't break the nic. One problem: very slow connectioncan I help? try to make some tests? Just an update: slow connection was a problem with my AP wifi. So my device is working well. Thank you, best regards -- Matteo Filippetto http://op83.blogspot.com
Re: alc(4) support for Atheros AR815x
2011/5/16 Stuart Henderson s...@spacehopper.org: So far, only had reports from L1C and the new devices (which is not the point of sending out this sort of diff). This is a fairly large diff and changes behaviour for existing devices. Has anyone with a currently-working L2C tested this to make sure it doesn't break their nic? Hi, I have a eeepc 1001pxd with Attansic Technology L2C working and this patch didn't break the nic. One problem: very slow connectioncan I help? try to make some tests? Latest snapshot of i386. Attached dmesg and pcidump. Best regards. Matteo Filippetto Domain /dev/pci0: 0:0:0: Intel Pineview DMI 0x: Vendor ID: 8086 Product ID: a010 0x0004: Command: 0006 Status ID: 2090 0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 00 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00 0x0010: BAR empty () 0x0014: BAR empty () 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1043 Product ID: 83ac 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 0x00e0: Capability 0x09: Vendor Specific 0:2:0: Intel Pineview Video 0x: Vendor ID: 8086 Product ID: a011 0x0004: Command: 0007 Status ID: 0090 0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 00 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00 0x0010: BAR mem 32bit addr: 0xf7e0/0x0008 0x0014: BAR io addr: 0xdc00/0x0008 0x0018: BAR mem prefetchable 32bit addr: 0xd000/0x1000 0x001c: BAR mem 32bit addr: 0xf7d0/0x0010 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1043 Product ID: 83ac 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 0f Min Gnt: 00 Max Lat: 00 0x0090: Capability 0x05: Message Signaled Interrupts (MSI) 0x00d0: Capability 0x01: Power Management 0:2:1: Intel Pineview Video 0x: Vendor ID: 8086 Product ID: a012 0x0004: Command: 0007 Status ID: 0090 0x0008: Class: 03 Subclass: 80 Interface: 00 Revision: 00 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size: 00 0x0010: BAR mem 32bit addr: 0xf7e8/0x0008 0x0014: BAR empty () 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1043 Product ID: 83ac 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 0x00d0: Capability 0x01: Power Management 0:27:0: Intel 82801GB HD Audio 0x: Vendor ID: 8086 Product ID: 27d8 0x0004: Command: 0006 Status ID: 0010 0x0008: Class: 04 Subclass: 03 Interface: 00 Revision: 02 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 08 0x0010: BAR mem 64bit addr: 0xf7cf8000/0x4000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1043 Product ID: 8442 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 04 Min Gnt: 00 Max Lat: 00 0x0050: Capability 0x01: Power Management 0x0060: Capability 0x05: Message Signaled Interrupts (MSI) 0x0070: Capability 0x10: PCI Express 0:28:0: Intel 82801GB PCIE 0x: Vendor ID: 8086 Product ID: 27d0 0x0004: Command: 0104 Status ID: 0010 0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 02 0x000c: BIST: 00 Header Type: 81 Latency Timer: 00 Cache Line Size: 08 0x0010: 0x0014: 0x0018: Primary Bus: 0 Secondary Bus: 4 Subordinate Bus: 4 Secondary Latency Timer: 00 0x001c: I/O Base: f0 I/O Limit: 00 Secondary Status: 2000 0x0020: Memory Base: fff0 Memory Limit: 0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001 0x0028: Prefetch Memory Base Upper 32 Bits: 0x002c: Prefetch Memory Limit Upper 32 Bits: 0x0030: I/O Base Upper 16 Bits: I/O Limit Upper 16 Bits: 0x0038: Expansion ROM Base Address: 0x003c: Interrupt Pin: 01 Line: 0f Bridge Control: 0002 0x0040: Capability 0x10
Re: which ISO for a VM?
2010/4/5 Richard Stride f...@nexxus.net: Sean Kennedy wrote: I concur, B it was a Valid question on running OpenBSD in a VM. Unless someone has answered directly, I'll short-run it here. Just to add my 2 cents, I run OpenBSD-current (i386) under VirtualBox 3.0.4 r50677 64-bit. The host operating system is Slackware 13 64 bit. I got to -current by installing OpenBSD 4.3 from the ISO image, and followed the upgrade guide from the OpenBSD website. Be warned, all I use that VM for is to compile the OpenBSD sources, it does nothing else. I have tried running OpenBSD under other versions of VirtualBox using different host operating systems, however there were always issues which would generally lead to various issues including kernel panics. My advice is to not run it virtualized. Rich I run 3 openbsd 4.6 virtualized with VBox (3.1.6 ) on a MacBook and I have no problem running services as DHCP, HTTP, DNS and others. Best regards -- Matteo Filippetto
