Re: nfs v2/v3 and diskless boot problem
Danny Braniss wrote: Danny Braniss wrote: Danny Braniss wrote: Danny Braniss wrote: there is an undocumented option: boot-nfsroot-options that the diskeless boot can use. I tried boot-nfsroot-options = "nfsv3" since the pxeboot does the initial mount via nfsv2, and this has at least one problem: removing a file from the readonly / will hang the system. so, the remount to v3 works in the case that the root is served by a Freebsd nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle is 32 bytes, and when switching to V3 it becomes 28bytes - sizeof(fhandle_t). This is not liked by the NetApp, which correctly gives error 1001: BADHANDLE :-) While I'm trying to come up with a solution, I am wondering if someone can shed some light: - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to 32 bytes will start WW3? NFSv3 file handles (by spec) can be up to 64bytes. true, but in freebsd, look at sys/nfs/nfsproto.h #define NFSX_V2FH 32 #define NFSX_V3FH (sizeof (fhandle_t)) #define NFSX_V4FH 128 so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) I'm not 100% sure what is happening, but it sounds like the file handle for the mount point or maybe one of the directories is not getting reset on remount. When do you get the BADHANDLE error? Can you capture a tshark/wireshark/tcpdump of the remount and error? I did, and if you look in sys/nfsclient/nfs_vfsops.c, nfs_convert_diskless is responsible for chopping off the 4 extra bytes. BTW, I tried to change the bcopy count to NFSX_V2FH/32, and it panics the kernel :-( danny oh - looks like this says it all: http://fxr.googlebit.com/source/sys/nfsclient/nfsdiskless.h?v=8-CURRENT#L51 that's where the boot-nfsroot-options comes from:-) if you notice, the filehandle for v3 is 64 bytes, but only 28 are used. but as I mentioned initially, this ONLY works when the server is FreeBSD, and breaks for other servers, ie NetAPP. AND the initial question stands: what's in a filehandle, or can it be > 28bytes. Yea, FreeBSD is making the assumption that all NFS servers will use the same size FH for NFSv3. That is just wrong. carful, I think this is the case only if fsb is the server, it will 'probably' accept filehandles of other sizes from other servers. I'm talking about the diskless root mounting code only at this point.. The FH is a server created opaque handle that it can create however it wishes. Most servers use information like inode, generation, fsid, etc to create it, but it's something that you can't necessarily decode. yes, but the FH has information that the server can/must use to figure out which local filesystem it refers to - remember that v2/v3 are stateless. Right, see my list right above your comment: inode, generation, fsid. Those three can uniquely identify a file on a filesystem on a server. There can be anything the server wants to stuff in the FH, or the FH can be a random number assigned to that file, etc. I've created a patch that might fix this, but I'm still testing and QEMU (which I use for my testing) keeps making my system either panic or lock up, so hopefully I should have something for you to try tonight. Also - can you tell me the exact 'mount' command you tried to do the remount/update? it's only in the diskless boot, where setting boot-nfsroot-options = "nfsv3" in /boot/loader.conf will do the remount. Ok - I'll do a little more testing on my patch tonight and let you know. Eric ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
> Danny Braniss wrote: > >> Danny Braniss wrote: > Danny Braniss wrote: > > there is an undocumented option: > > boot-nfsroot-options > > that the diskeless boot can use. I tried > > boot-nfsroot-options = "nfsv3" > > since the pxeboot does the initial mount via nfsv2, and this has at > > least > > one problem: removing a file from the readonly / will hang the system. > > > > so, the remount to v3 works in the case that the root is served by a > > Freebsd > > nfs server, but fails if it's NetAPP. The reason is that the v2 > > filehandle > > is 32 bytes, and when switching to V3 it becomes 28bytes - > > sizeof(fhandle_t). > > This is not liked by the NetApp, which correctly gives error 1001: > > BADHANDLE > > :-) > > > > While I'm trying to come up with a solution, I am wondering if someone > > can shed some light: > > - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to > >32 bytes will start WW3? > NFSv3 file handles (by spec) can be up to 64bytes. > >>> true, but in freebsd, look at sys/nfs/nfsproto.h > >>> #define NFSX_V2FH 32 > >>> #define NFSX_V3FH (sizeof (fhandle_t)) > >>> #define NFSX_V4FH 128 > >>> > >>> so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) > >>> > >>> > I'm not 100% sure what is happening, but it sounds like the file handle > for the mount point or maybe one of the directories is not getting reset > on remount. > > When do you get the BADHANDLE error? Can you capture a > tshark/wireshark/tcpdump of the remount and error? > >>> I did, and if you look in sys/nfsclient/nfs_vfsops.c, > >>> nfs_convert_diskless is responsible > >>> for chopping off the 4 extra bytes. BTW, I tried to change the bcopy > >>> count to NFSX_V2FH/32, and > >>> it panics the kernel :-( > >>> > >>> danny > >> > >> oh - looks like this says it all: > >> http://fxr.googlebit.com/source/sys/nfsclient/nfsdiskless.h?v=8-CURRENT#L51 > >> > > that's where the boot-nfsroot-options comes from:-) > > if you notice, the filehandle for v3 is 64 bytes, but > > only 28 are used. > > > > but as I mentioned initially, this ONLY works when the server is FreeBSD, > > and > > breaks for other servers, ie NetAPP. AND the initial question stands: > > what's in a filehandle, or can it be > 28bytes. > > > Yea, FreeBSD is making the assumption that all NFS servers will use the > same size FH for NFSv3. That is just wrong. > carful, I think this is the case only if fsb is the server, it will 'probably' accept filehandles of other sizes from other servers. > The FH is a server created opaque handle that it can create however it > wishes. Most servers use information like inode, generation, fsid, etc > to create it, but it's something that you can't necessarily decode. > yes, but the FH has information that the server can/must use to figure out which local filesystem it refers to - remember that v2/v3 are stateless. > I've created a patch that might fix this, but I'm still testing and QEMU > (which I use for my testing) keeps making my system either panic or lock > up, so hopefully I should have something for you to try tonight. > > Also - can you tell me the exact 'mount' command you tried to do the > remount/update? > it's only in the diskless boot, where setting boot-nfsroot-options = "nfsv3" in /boot/loader.conf will do the remount. cheers, danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
Danny Braniss wrote: Danny Braniss wrote: Danny Braniss wrote: there is an undocumented option: boot-nfsroot-options that the diskeless boot can use. I tried boot-nfsroot-options = "nfsv3" since the pxeboot does the initial mount via nfsv2, and this has at least one problem: removing a file from the readonly / will hang the system. so, the remount to v3 works in the case that the root is served by a Freebsd nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle is 32 bytes, and when switching to V3 it becomes 28bytes - sizeof(fhandle_t). This is not liked by the NetApp, which correctly gives error 1001: BADHANDLE :-) While I'm trying to come up with a solution, I am wondering if someone can shed some light: - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to 32 bytes will start WW3? NFSv3 file handles (by spec) can be up to 64bytes. true, but in freebsd, look at sys/nfs/nfsproto.h #define NFSX_V2FH 32 #define NFSX_V3FH (sizeof (fhandle_t)) #define NFSX_V4FH 128 so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) I'm not 100% sure what is happening, but it sounds like the file handle for the mount point or maybe one of the directories is not getting reset on remount. When do you get the BADHANDLE error? Can you capture a tshark/wireshark/tcpdump of the remount and error? I did, and if you look in sys/nfsclient/nfs_vfsops.c, nfs_convert_diskless is responsible for chopping off the 4 extra bytes. BTW, I tried to change the bcopy count to NFSX_V2FH/32, and it panics the kernel :-( danny oh - looks like this says it all: http://fxr.googlebit.com/source/sys/nfsclient/nfsdiskless.h?v=8-CURRENT#L51 that's where the boot-nfsroot-options comes from:-) if you notice, the filehandle for v3 is 64 bytes, but only 28 are used. but as I mentioned initially, this ONLY works when the server is FreeBSD, and breaks for other servers, ie NetAPP. AND the initial question stands: what's in a filehandle, or can it be > 28bytes. Yea, FreeBSD is making the assumption that all NFS servers will use the same size FH for NFSv3. That is just wrong. The FH is a server created opaque handle that it can create however it wishes. Most servers use information like inode, generation, fsid, etc to create it, but it's something that you can't necessarily decode. I've created a patch that might fix this, but I'm still testing and QEMU (which I use for my testing) keeps making my system either panic or lock up, so hopefully I should have something for you to try tonight. Also - can you tell me the exact 'mount' command you tried to do the remount/update? Eric ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
> Danny Braniss wrote: > >> Danny Braniss wrote: > >>> there is an undocumented option: > >>> boot-nfsroot-options > >>> that the diskeless boot can use. I tried > >>> boot-nfsroot-options = "nfsv3" > >>> since the pxeboot does the initial mount via nfsv2, and this has at least > >>> one problem: removing a file from the readonly / will hang the system. > >>> > >>> so, the remount to v3 works in the case that the root is served by a > >>> Freebsd > >>> nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle > >>> is 32 bytes, and when switching to V3 it becomes 28bytes - > >>> sizeof(fhandle_t). > >>> This is not liked by the NetApp, which correctly gives error 1001: > >>> BADHANDLE > >>> :-) > >>> > >>> While I'm trying to come up with a solution, I am wondering if someone > >>> can shed some light: > >>> - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to > >>>32 bytes will start WW3? > >> > >> NFSv3 file handles (by spec) can be up to 64bytes. > > > > true, but in freebsd, look at sys/nfs/nfsproto.h > > #define NFSX_V2FH 32 > > #define NFSX_V3FH (sizeof (fhandle_t)) > > #define NFSX_V4FH 128 > > > > so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) > > > > > >> I'm not 100% sure what is happening, but it sounds like the file handle > >> for the mount point or maybe one of the directories is not getting reset > >> on remount. > >> > >> When do you get the BADHANDLE error? Can you capture a > >> tshark/wireshark/tcpdump of the remount and error? > > > > I did, and if you look in sys/nfsclient/nfs_vfsops.c, nfs_convert_diskless > > is responsible > > for chopping off the 4 extra bytes. BTW, I tried to change the bcopy count > > to NFSX_V2FH/32, and > > it panics the kernel :-( > > > > danny > > > oh - looks like this says it all: > http://fxr.googlebit.com/source/sys/nfsclient/nfsdiskless.h?v=8-CURRENT#L51 > that's where the boot-nfsroot-options comes from:-) if you notice, the filehandle for v3 is 64 bytes, but only 28 are used. but as I mentioned initially, this ONLY works when the server is FreeBSD, and breaks for other servers, ie NetAPP. AND the initial question stands: what's in a filehandle, or can it be > 28bytes. danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
Danny Braniss wrote: Danny Braniss wrote: there is an undocumented option: boot-nfsroot-options that the diskeless boot can use. I tried boot-nfsroot-options = "nfsv3" since the pxeboot does the initial mount via nfsv2, and this has at least one problem: removing a file from the readonly / will hang the system. so, the remount to v3 works in the case that the root is served by a Freebsd nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle is 32 bytes, and when switching to V3 it becomes 28bytes - sizeof(fhandle_t). This is not liked by the NetApp, which correctly gives error 1001: BADHANDLE :-) While I'm trying to come up with a solution, I am wondering if someone can shed some light: - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to 32 bytes will start WW3? NFSv3 file handles (by spec) can be up to 64bytes. true, but in freebsd, look at sys/nfs/nfsproto.h #define NFSX_V2FH 32 #define NFSX_V3FH (sizeof (fhandle_t)) #define NFSX_V4FH 128 so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) I'm not 100% sure what is happening, but it sounds like the file handle for the mount point or maybe one of the directories is not getting reset on remount. When do you get the BADHANDLE error? Can you capture a tshark/wireshark/tcpdump of the remount and error? I did, and if you look in sys/nfsclient/nfs_vfsops.c, nfs_convert_diskless is responsible for chopping off the 4 extra bytes. BTW, I tried to change the bcopy count to NFSX_V2FH/32, and it panics the kernel :-( danny oh - looks like this says it all: http://fxr.googlebit.com/source/sys/nfsclient/nfsdiskless.h?v=8-CURRENT#L51 Snippet: 51 /* 52 * I have defined a new structure that can handle an NFS Version 3 file handle 53 * but the kernel still expects the old Version 2 one to be provided. The 54 * changes required in nfs_vfsops.c for using the new are documented there in 55 * comments. (I felt that breaking network booting code by changing this 56 * structure would not be prudent at this time, since almost all servers are 57 * still Version 2 anyhow.) 58 */ Eric ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
> Danny Braniss wrote: > > there is an undocumented option: > > boot-nfsroot-options > > that the diskeless boot can use. I tried > > boot-nfsroot-options = "nfsv3" > > since the pxeboot does the initial mount via nfsv2, and this has at least > > one problem: removing a file from the readonly / will hang the system. > > > > so, the remount to v3 works in the case that the root is served by a Freebsd > > nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle > > is 32 bytes, and when switching to V3 it becomes 28bytes - > > sizeof(fhandle_t). > > This is not liked by the NetApp, which correctly gives error 1001: > > BADHANDLE > > :-) > > > > While I'm trying to come up with a solution, I am wondering if someone > > can shed some light: > > - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to > >32 bytes will start WW3? > > > NFSv3 file handles (by spec) can be up to 64bytes. true, but in freebsd, look at sys/nfs/nfsproto.h #define NFSX_V2FH 32 #define NFSX_V3FH (sizeof (fhandle_t)) #define NFSX_V4FH 128 so for v3 it's 28 bytes. (fhandle_t is defined in sys/mount.h) > > I'm not 100% sure what is happening, but it sounds like the file handle > for the mount point or maybe one of the directories is not getting reset > on remount. > > When do you get the BADHANDLE error? Can you capture a > tshark/wireshark/tcpdump of the remount and error? I did, and if you look in sys/nfsclient/nfs_vfsops.c, nfs_convert_diskless is responsible for chopping off the 4 extra bytes. BTW, I tried to change the bcopy count to NFSX_V2FH/32, and it panics the kernel :-( danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs v2/v3 and diskless boot problem
Danny Braniss wrote: there is an undocumented option: boot-nfsroot-options that the diskeless boot can use. I tried boot-nfsroot-options = "nfsv3" since the pxeboot does the initial mount via nfsv2, and this has at least one problem: removing a file from the readonly / will hang the system. so, the remount to v3 works in the case that the root is served by a Freebsd nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle is 32 bytes, and when switching to V3 it becomes 28bytes - sizeof(fhandle_t). This is not liked by the NetApp, which correctly gives error 1001: BADHANDLE :-) While I'm trying to come up with a solution, I am wondering if someone can shed some light: - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to 32 bytes will start WW3? NFSv3 file handles (by spec) can be up to 64bytes. I'm not 100% sure what is happening, but it sounds like the file handle for the mount point or maybe one of the directories is not getting reset on remount. When do you get the BADHANDLE error? Can you capture a tshark/wireshark/tcpdump of the remount and error? Eric ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nfs v2/v3 and diskless boot problem
there is an undocumented option: boot-nfsroot-options that the diskeless boot can use. I tried boot-nfsroot-options = "nfsv3" since the pxeboot does the initial mount via nfsv2, and this has at least one problem: removing a file from the readonly / will hang the system. so, the remount to v3 works in the case that the root is served by a Freebsd nfs server, but fails if it's NetAPP. The reason is that the v2 filehandle is 32 bytes, and when switching to V3 it becomes 28bytes - sizeof(fhandle_t). This is not liked by the NetApp, which correctly gives error 1001: BADHANDLE :-) While I'm trying to come up with a solution, I am wondering if someone can shed some light: - is sizeof(fhandle_t) == 28 bytes is mystical, or changing it to 32 bytes will start WW3? cheers danny ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Diskless boot problem
Hi, I have a problem with booting Dell 2850 over network. The machine reads kernel over net, boots upto mounting / from NFS and then crashes. Tcpdump output: 12:15:58.919683 arp who-has 10.158.190.73 tell 10.158.190.74 12:15:58.919702 arp reply 10.158.190.73 is-at 00:11:43:d3:6e:e1 12:15:58.920058 IP 10.158.190.74.475209176 > 10.158.190.73.2049: 92 getattr [|nfs] 12:15:58.920134 IP 10.158.190.73.2049 > 10.158.190.74.475209176: reply ok 28 getattr ERROR: Stale NFS file handle 12:15:58.920432 arp who-has 10.158.190.73 tell 10.158.190.74 12:15:58.920442 arp reply 10.158.190.73 is-at 00:11:43:d3:6e:e1 12:15:58.920681 IP 10.158.190.74.475209177 > 10.158.190.73.2049: 100 lookup [|nfs] 12:15:58.920707 IP 10.158.190.73.2049 > 10.158.190.74.475209177: reply ok 28 lookup ERROR: Stale NFS file handle 12:15:58.920932 IP 10.158.190.74.475209178 > 10.158.190.73.2049: 100 lookup [|nfs] 12:15:58.920963 IP 10.158.190.73.2049 > 10.158.190.74.475209178: reply ok 28 lookup ERROR: Stale NFS file handle 12:15:58.952180 IP 10.158.190.74.475209179 > 10.158.190.73.2049: 100 lookup [|nfs] 12:15:58.952277 IP 10.158.190.73.2049 > 10.158.190.74.475209179: reply ok 28 lookup ERROR: Stale NFS file handle 12:15:58.984785 IP 10.158.190.74.475209180 > 10.158.190.73.2049: 100 lookup [|nfs] 12:15:58.984866 IP 10.158.190.73.2049 > 10.158.190.74.475209180: reply ok 28 lookup ERROR: Stale NFS file handle 12:15:59.020500 IP 10.158.190.74.475209181 > 10.158.190.73.2049: 104 lookup [|nfs] 12:15:59.020573 IP 10.158.190.73.2049 > 10.158.190.74.475209181: reply ok 28 lookup ERROR: Stale NFS file handle 12:15:59.054130 IP 10.158.190.74.475209182 > 10.158.190.73.2049: 104 lookup [|nfs] 12:15:59.054224 IP 10.158.190.73.2049 > 10.158.190.74.475209182: reply ok 28 lookup ERROR: Stale NFS file handle I wonder where the `Stale NFS handle' error comes from, as the client doesn't seem to have mounted the filesystem over NFS from what I can see. On the console of the diskless I have this: NFS ROOT: 10.158.190.73:/var/www/FreeBSD-5.4-x86-PXE em0: Link is up 100 Mbps Half Duplex exec /sbin/init: error 70 exec /sbin/oinit: error 70 exec /sbin/init.bak: error 70 exec /rescue/init: error 70 exec /stand/sysinstall: error 70 init: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall panic: no init Uptime: 55s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort The speed for em0 is obviously wrong. Setting on the switch is 100 full-duplex. Our network wizards can f***kup autonegotiation on Cisco Catalyst, so it must stay that way. Intel em-s tend to hang for a couple of seconds before getting on the net so it might be the problem. On the other hand kernel loads just fine over TFTP. Any thoughts? Thanks, /S -- Sławek Żak / UNIX Systems Administrator ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/boot/boot problem
Hi John, thanks for commiting my previous boot2.c patch. I would appreciate any hint about the following problem. I am using 5.3, sources from 1 Dec 2004. The environment I am using is this: ATA disk has one partition with one file, /kernel. /kernel has MFS root filesystem. there is no /boot/loader, /kernel is boot by the first stage loader (/boot/boot). So, the problem is: 1. when /kernel is kgzipped, It says 'Invalid format'. that means, inflate() could not correctly unzip the kernel. 2. when /kernel is not kgzipped, boot crashes: int=06 err=0 efl=10002 eip=c0432540 eax=c0432540 ebx=c2152600 ecx=18 edx=a050001e esi=947a4 edi=c0432540 ebp=7 esp=9e6f0 cs:eip= ff ff ff ff ff (all ff) ss:eip=69 95 00 00 00 00 00 80 1c 00 50 00 00 00 00 00 objdump -d kernel shows, that eip c0432540 is exactly where kernel's .text segment starts: c0432540 <.text>: c0432540: 66 c7 05 72 04 00 00movw $0x1234,0x472 c0432547: 34 12 c0432549: 55 push %ebp So it looks like that kernel was mapped wrong ? 3. The craziest thing is that *sometimes* it works! I do build kernels again and again, without cvsup-ing the sources, and sometimes it works, sometimes not. Any comment, hint etc would be very appreciated. sergey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4.9 boot problem on em0 platform.
From: Deepak Jain [mailto:[EMAIL PROTECTED] > > Just a guess, but i think you've bumped nmbclusters or nmbufs up > > too much (or perhaps maxsockets, maxfds, ...) and have run out of > > KVA. > > > > You can tune clusters & mbufs in loader.conf without recompiling > > kernel. You will want to see what vm.zone_kmem_pages, > vm.zone_kmem_kvaspace > > are showing you, vmstat -z, vmstat -m, etc. > > > > You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are > > trying to put more into the kernel mem space. > > > > The kernel that works from another machine has the same settings > (NMBCLUSTERS=65536, maxusers=512). The machine has 2GB of RAM. > > How do you undo the loader.conf settings when the machine won't boot > because of the settings you made? :| Use 'space' to get to the 'ok' loader prompt. now 'set' the values to a lower #... ok set path.path.path=value man loader will tell you about this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 boot problem on em0 platform.
Just a guess, but i think you've bumped nmbclusters or nmbufs up too much (or perhaps maxsockets, maxfds, ...) and have run out of KVA. You can tune clusters & mbufs in loader.conf without recompiling kernel. You will want to see what vm.zone_kmem_pages, vm.zone_kmem_kvaspace are showing you, vmstat -z, vmstat -m, etc. You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are trying to put more into the kernel mem space. The kernel that works from another machine has the same settings (NMBCLUSTERS=65536, maxusers=512). The machine has 2GB of RAM. How do you undo the loader.conf settings when the machine won't boot because of the settings you made? :| thanks, Deepak ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4.9 boot problem on em0 platform.
> From: Deepak Jain [mailto:[EMAIL PROTECTED] > As a part of tracking down a performance issue, I tried building a > custom kernel (with just IPFW, DUMMYNET added, NMBCLUSTERS, > commenting > out MATH_EMULATE, INET6, I386, I486). The system is currently > running a > kernel from a similar machine with the same settings. The > machine does > run on this kernel: 4.9-RELEASE FreeBSD 4.9-RELEASE #8, with > the above > options, but I have not been able to compile a 4.9-RELEASE #2 > (which is > the source tree on the machine) kernel that has an identical > config file. > > So, when it builds itself from -RELEASE sources, it hangs at: > > "pmap_mapdev: Couldn't alloc kernel virtual memory" I couldn't find a > reference to anything recent. Nothing non-default (from a GENERIC > kernel) with respect to ACPI has been touched. I see a reference to > -CURRENT from 9/03, but that's it. Just a guess, but i think you've bumped nmbclusters or nmbufs up too much (or perhaps maxsockets, maxfds, ...) and have run out of KVA. You can tune clusters & mbufs in loader.conf without recompiling kernel. You will want to see what vm.zone_kmem_pages, vm.zone_kmem_kvaspace are showing you, vmstat -z, vmstat -m, etc. You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are trying to put more into the kernel mem space. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.9 boot problem on em0 platform.
As a part of tracking down a performance issue, I tried building a custom kernel (with just IPFW, DUMMYNET added, NMBCLUSTERS, commenting out MATH_EMULATE, INET6, I386, I486). The system is currently running a kernel from a similar machine with the same settings. The machine does run on this kernel: 4.9-RELEASE FreeBSD 4.9-RELEASE #8, with the above options, but I have not been able to compile a 4.9-RELEASE #2 (which is the source tree on the machine) kernel that has an identical config file. So, when it builds itself from -RELEASE sources, it hangs at: "pmap_mapdev: Couldn't alloc kernel virtual memory" I couldn't find a reference to anything recent. Nothing non-default (from a GENERIC kernel) with respect to ACPI has been touched. I see a reference to -CURRENT from 9/03, but that's it. Should I turn off power management? Is there a way to prevent ACPI support from being loaded at the kernel level? Should I just cvsup to 4.9-RELENG and try it again? It would be very nice if this were some how related to my network performance problem, but that might be too much to hope for. :) Thanks in advance, DJ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Okay I've checked my BIOS. I'm using Phoenix BIOS Setup version 4.0 with the bwlo versions BIOS Version: R216B1 EC BIOS Version: R216B1 Video BIOS Version: BOAM7_12 I can't seem to find the option specified below or something similar. Hidetoshi Shimokawa wrote: It seems that fwohci registers are not mapped correctly. If your BIOS has a option for `PnP OS', try to set it to 'no'. /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 16:32:30 +0100, Kris Davidson wrote: I'm trying to install 5.1 release and am in the process of downloading version 4.8 Hidetoshi Shimokawa wrote: Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: This may be a complete newbie question, or it may have been answered before but I would appreciate any help or input that can be provided. I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install FreeBSD on. I boot from the CD and then try selecting each one of the 7 boot options however each option I pick returns the below and then the system reboots, as such I can not start the installation. -- fwohci0: Link S100, max_rec 2 bytes fwohci0: max_rec2 -> 512 fwohci0: bus_OPT 0x0 -> 0xf8008000 fwohci0: fwohci_set_intr: 1 firewire : on fwohci0 fatal trap 12: page fault while in Kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8 :0xc02e5a50 Stack pointer = 0x10 :0xc0b2e8c4 frame pointer = 0x10 :0xc0b2e8c8 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupte enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Panic: Page fault -- I would appreciate it if anyone could help me with this or provide advice. Cheers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
It seems that fwohci registers are not mapped correctly. If your BIOS has a option for `PnP OS', try to set it to 'no'. /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 16:32:30 +0100, Kris Davidson wrote: > > I'm trying to install 5.1 release and am in the process of downloading > version 4.8 > > Hidetoshi Shimokawa wrote: > > Which version of FreeBSD are you trying to install? > > > > /\ Hidetoshi Shimokawa > > \/ [EMAIL PROTECTED] > > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > > > > At Sat, 25 Oct 2003 15:19:56 +0100, > > Kris Davidson wrote: > > > >>This may be a complete newbie question, or it may have been answered > >>before but I would appreciate any help or input that can be provided. > >> > >>I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install > >>FreeBSD on. I boot from the CD and then try selecting each one of the 7 > >>boot options however each option I pick returns the below and then the > >>system reboots, as such I can not start the installation. > >> > >>-- > >>fwohci0: Link S100, max_rec 2 bytes > >>fwohci0: max_rec2 -> 512 > >>fwohci0: bus_OPT 0x0 -> 0xf8008000 > >>fwohci0: fwohci_set_intr: 1 > >> > >>firewire : on fwohci0 > >>fatal trap 12: page fault while in Kernel mode > >> > >>fault virtual address = 0x2c > >>fault code = supervisor read, page not present > >>instruction pointer = 0x8 :0xc02e5a50 > >>Stack pointer = 0x10 :0xc0b2e8c4 > >>frame pointer = 0x10 :0xc0b2e8c8 > >>code segment = base 0x0, limit 0xf, type 0x1b > >> = DPL0, pres 1, def32 1, gran 1 > >>processor eflags = interrupte enabled, resume, IOPL=0 > >>current process = 0 (swapper) > >>trap number = 12 > >> > >>Panic: Page fault > >>-- > >> > >>I would appreciate it if anyone could help me with this or provide advice. > >> > >>Cheers. > >> > >>___ > >>[EMAIL PROTECTED] mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > >>To unsubscribe, send any mail to "[EMAIL PROTECTED]" > >> > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
I'm trying to install 5.1 release and am in the process of downloading version 4.8 Hidetoshi Shimokawa wrote: Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: This may be a complete newbie question, or it may have been answered before but I would appreciate any help or input that can be provided. I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install FreeBSD on. I boot from the CD and then try selecting each one of the 7 boot options however each option I pick returns the below and then the system reboots, as such I can not start the installation. -- fwohci0: Link S100, max_rec 2 bytes fwohci0: max_rec2 -> 512 fwohci0: bus_OPT 0x0 -> 0xf8008000 fwohci0: fwohci_set_intr: 1 firewire : on fwohci0 fatal trap 12: page fault while in Kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8 :0xc02e5a50 Stack pointer = 0x10 :0xc0b2e8c4 frame pointer = 0x10 :0xc0b2e8c8 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupte enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Panic: Page fault -- I would appreciate it if anyone could help me with this or provide advice. Cheers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-firewire To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot Problem
Which version of FreeBSD are you trying to install? /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html At Sat, 25 Oct 2003 15:19:56 +0100, Kris Davidson wrote: > > This may be a complete newbie question, or it may have been answered > before but I would appreciate any help or input that can be provided. > > I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install > FreeBSD on. I boot from the CD and then try selecting each one of the 7 > boot options however each option I pick returns the below and then the > system reboots, as such I can not start the installation. > > -- > fwohci0: Link S100, max_rec 2 bytes > fwohci0: max_rec2 -> 512 > fwohci0: bus_OPT 0x0 -> 0xf8008000 > fwohci0: fwohci_set_intr: 1 > > firewire : on fwohci0 > fatal trap 12: page fault while in Kernel mode > > fault virtual address = 0x2c > fault code = supervisor read, page not present > instruction pointer = 0x8 :0xc02e5a50 > Stack pointer = 0x10 :0xc0b2e8c4 > frame pointer = 0x10 :0xc0b2e8c8 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > processor eflags = interrupte enabled, resume, IOPL=0 > current process = 0 (swapper) > trap number = 12 > > Panic: Page fault > -- > > I would appreciate it if anyone could help me with this or provide advice. > > Cheers. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot Problem
This may be a complete newbie question, or it may have been answered before but I would appreciate any help or input that can be provided. I have a Sony VAIO PCG-GRZ615M laptop which I'm trying to install FreeBSD on. I boot from the CD and then try selecting each one of the 7 boot options however each option I pick returns the below and then the system reboots, as such I can not start the installation. -- fwohci0: Link S100, max_rec 2 bytes fwohci0: max_rec2 -> 512 fwohci0: bus_OPT 0x0 -> 0xf8008000 fwohci0: fwohci_set_intr: 1 firewire : on fwohci0 fatal trap 12: page fault while in Kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8 :0xc02e5a50 Stack pointer = 0x10 :0xc0b2e8c4 frame pointer = 0x10 :0xc0b2e8c8 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupte enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Panic: Page fault -- I would appreciate it if anyone could help me with this or provide advice. Cheers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Installation and the 1024 cylinder boot problem
Recently I had to install 5.1-RELEASE at 60GB, and had a lot of troubles to start booting correctly. I hope that /stand/sysinstall have to handle >1024 cylinder booting. Otherwise I have to run 'boot0cfg' manually to fix this issue. MuTk0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vmware boot problem (xp host, freebsd guest)
Glenn Gombert wrote:
>
> Here is a patch that was posted to the list a couple weeks ago, that
> needs to be applied to make FreeBSD uner vmware work reliably..
>
> In message <[EMAIL PROTECTED]>, Robert Watsonwrit
> es:
> >I've had -STABLE run fine, but of late have had a lot of trouble with
> >-current. Userland processes during the boot sequence seem to spenda
> lot
> >of time just spinning -- it's not clear to me what the cause is, andI
> >haven't had time to debug.
>
> Someone mentioned on a list somewhere that vmware takes forever to
> emulate the cmpxchg instruction, and that using the I386_CPU version
> of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown
> with -current sometime in September, so I tried avoiding the
> cmpxchg's and things got much faster. Below is the patch I use
> (using this outside vmware on SMP hardware is a bad idea :-).
Is there any reason why don't you just define I386_CPU instead
of modifying the header file ? This is done by the line
cpu I386_CPU
in the config file. Or has the full i386 support been already dropped
from the kernel by now (I remember such a discussion on
-developers) ? Hm, maybe we should add "VMWARE_CPU" then for
inclusion of any Vmware-related optimisations.
-SB
>
> Ian
>
> Index: atomic.h
> ===
> RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v
> retrieving revision 1.21
> diff -u -r1.21 atomic.h
> --- atomic.h2001/10/08 20:58:24 1.21
> +++ atomic.h2001/10/09 18:35:25
> @@ -111,7 +111,7 @@
> * Returns 0 on failure, non-zero on success
> */
>
> -#if defined(I386_CPU)
> +#if defined(I386_CPU) || 1
> static __inline int
> atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src)
> {
>
> "Bill G." <[EMAIL PROTECTED]> wrote:
> >
> > I am having trouble getting FreeBSD 4.4-RELEASE to run in
> > vmware. I am using Windows XP Pro as the host os, vmware
> > version 3, and FreeBSD as the guest os. I tried searching
> > the mailing lists, but was unsuccessful in finding the
> > answer to this problem.
> >
> > FreeBSD installs, but will not boot - it just hangs, with
> > no errors.
> >
> > All suggestions / solutions appreciated. Thanks,
> >
> > Bill
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
> __
> FREE voicemail, email, and fax...all in one place.
> Sign Up Now! http://www.onebox.com
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: vmware boot problem (xp host, freebsd guest)
Here is a patch that was posted to the list a couple weeks ago, that
needs to be applied to make FreeBSD uner vmware work reliably..
In message <[EMAIL PROTECTED]>, Robert Watsonwrit
es:
>I've had -STABLE run fine, but of late have had a lot of trouble with
>-current. Userland processes during the boot sequence seem to spenda
lot
>of time just spinning -- it's not clear to me what the cause is, andI
>haven't had time to debug.
Someone mentioned on a list somewhere that vmware takes forever to
emulate the cmpxchg instruction, and that using the I386_CPU version
of atomic_cmpset_int() helps a lot. I noticed a major vmware slowdown
with -current sometime in September, so I tried avoiding the
cmpxchg's and things got much faster. Below is the patch I use
(using this outside vmware on SMP hardware is a bad idea :-).
Ian
Index: atomic.h
===
RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v
retrieving revision 1.21
diff -u -r1.21 atomic.h
--- atomic.h2001/10/08 20:58:24 1.21
+++ atomic.h2001/10/09 18:35:25
@@ -111,7 +111,7 @@
* Returns 0 on failure, non-zero on success
*/
-#if defined(I386_CPU)
+#if defined(I386_CPU) || 1
static __inline int
atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src)
{
"Bill G." <[EMAIL PROTECTED]> wrote:
>
> I am having trouble getting FreeBSD 4.4-RELEASE to run in
> vmware. I am using Windows XP Pro as the host os, vmware
> version 3, and FreeBSD as the guest os. I tried searching
> the mailing lists, but was unsuccessful in finding the
> answer to this problem.
>
> FreeBSD installs, but will not boot - it just hangs, with
> no errors.
>
> All suggestions / solutions appreciated. Thanks,
>
> Bill
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
vmware boot problem (xp host, freebsd guest)
I am having trouble getting FreeBSD 4.4-RELEASE to run in vmware. I am using Windows XP Pro as the host os, vmware version 3, and FreeBSD as the guest os. I tried searching the mailing lists, but was unsuccessful in finding the answer to this problem. FreeBSD installs, but will not boot - it just hangs, with no errors. All suggestions / solutions appreciated. Thanks, Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Iomega ZIP boot problem
No answer from the -questions list, so I figured I'd try here. I'm encountering difficulties booting from a 250MB Iomega ZIP drive. The ZIP drive is installed as the primary master IDE. There's a UFS filesystem on /dev/afd0a. At the boot prompt, I enter boot: 0:ad(0,a)kernel afd0? is of course not an option here. Since the ZIP is configured in the BIOS to emulate an IDE HD, I take a stab. The kernel loads properly, devices are detected as per usual. At the stage where the root filesystem is remounted r/w, I get the following: afd0: 239MB [239/64/32] at ata0-master using PIO3 Mounting root from ufs:ad0s1a Root mount failed: 6 Mounting root from ufs:ad0sa Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input mountroot> /dev/afd0a Mounting root from /dev/afd0a Root mount failed: 22 mountroot> ufs:/dev/afd0a Mounting root from ufs:/dev/afd0a spec_getpages:(#afd/0) IO read failure: (error=0) bp 0xc1c78438 vp 0xc5ae1d40 size: 53248, resid: 32768, a_count: 53248, valid: 0x0 nread: 20480, reqpage: 7, pindex: 51, pcount: 13 vm_fault: pager read error, pid 1 (init) Nov 28 10:31:15 init: setlogin() failed: Bad address spec_getpages:(#afd/0) IO read failure: (error=0) bp 0xc1c78438 vp 0xc5ae1d40 size: 57344, resid: 32768, a_count: 57344, valid: 0x0 nread: 24576, reqpage: 7, pindex: 73, pcount: 14 vm_fault: pager read error, pid 6 (sh) pid 6 (sh), uid 0: exited on signal 11 Nov 28 10:31:16 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /sbin/sh: As you can see, manually selecting "/dev/afd0a" seems to be a valid option. However, once / is mounted, I get a series of read errors. There's more, though. If I hit "enter" a few times, it manages to execute /bin/sh and give me a prompt. At this point, most any command I type that isn't a shell builtin results in a few inital read failures followed by any number of successful operations. For example, if I tried to 'newfs' a partition, the first two attempts fail, and then I can 'newfs' as many partitions as I need. Seems like a caching issue, as if the latency of the drive exceeds the driver's expectation. This should not be an issue if it's using the "afd" driver. I'm wondering if this kind of operation is even supported? There don't seem to be any problems with the drive or the media, I can read and write files w/o errors with the drive mounted on a running system. Has anyone done this sort of thing successfully? If so, what am I missing? Thanks in advance... -Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: PXE boot problem. - SOLVED
That was it. Updating the flash on the Intel NIC and she booted right up. Thanks, Matt > -Original Message- > From: Mathew KANNER [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 01, 2000 8:54 AM > To: Matt Simerson > Cc: '[EMAIL PROTECTED]' > Subject: Re: PXE boot problem. > > > On Nov 30, Matt Simerson wrote: > > [...] > > > >Intel UNDI, PXE-2.0 (build 067) > >Copyright (c) 1997, 1998 Intel Corporation > > [...] > > > Get the flash upgrade from intel. > > Mine reads: > Intel(R) Boot Agent Version 4.0.14 > > and it works well. > > --Mat > > > -- > Mathew Kanner <[EMAIL PROTECTED]> SOCS McGill University >Obtuse quote: He [not me] understands: "This field of perception >is void of perception of man." -- The Quintessence of Buddhism > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PXE boot problem.
On Nov 30, Matt Simerson wrote: > [...] > >Intel UNDI, PXE-2.0 (build 067) >Copyright (c) 1997, 1998 Intel Corporation > [...] Get the flash upgrade from intel. Mine reads: Intel(R) Boot Agent Version 4.0.14 and it works well. --Mat -- Mathew Kanner <[EMAIL PROTECTED]> SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PXE boot problem.
From: Doug White <[EMAIL PROTECTED]> Subject: Re: PXE boot problem. Date: Thu, 30 Nov 2000 20:18:26 -0800 (PST) > On Thu, 30 Nov 2000, Matt Simerson wrote: > > > Hi Folks, > > > > I've been trying hard to get a FreeBSD system booted via PXE with only > > limited success. Maybe someone can have a look at my configs and shed a > > little light on this for me. > > > > Here's what happens at boot time: > > > >Intel UNDI, PXE-2.0 (build 067) > > Problem #1: broken build. Flash your motherboard/card to the latest, > build 082. I have two Intel PRO/100+ Management Adapters with differnet versions of ROM. One is build 67, the other is build 78. Both work fine for me. > NFS is configured as follows: > >matt# more /etc/exports >/-alldirs -ro >/usr -alldirs -ro >/cdrom -alldirs -maproot=root -ro Perhaps, you can add /tftpboot in /etc/exports. Manabu Yokawa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PXE boot problem.
On Thu, 30 Nov 2000, Matt Simerson wrote: > Hi Folks, > > I've been trying hard to get a FreeBSD system booted via PXE with only > limited success. Maybe someone can have a look at my configs and shed a > little light on this for me. > > Here's what happens at boot time: > >Intel UNDI, PXE-2.0 (build 067) Problem #1: broken build. Flash your motherboard/card to the latest, build 082. >option broadcast-address 192.168.254.255; >option domain-name-servers 192.168.254.3; >option domain-name "domain.com"; >option routers 192.168.254.1; >option subnet-mask 255.255.255.0; >option space PXE; >option PXE.mtftp-ip code 1 = ip-address; >option PXE.mtftp-cport code 2 = unsigned integer 16; >option PXE.mtftp-sport code 3 = unsigned integer 16; >option PXE.mtftp-tmout code 4 = unsigned integer 8; >option PXE.mtftp-delay code 5 = unsigned integer 8; Problem #2: This is not required, and is in fact wrong. tftp != mtftp. Unless you have an MTFTP server around ... I highly suggest doing it the old fashioned way with boot-file. PXE will fault over to RPL/'normal' mode very quickly and works perfectly. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
PXE boot problem.
Hi Folks,
I've been trying hard to get a FreeBSD system booted via PXE with only
limited success. Maybe someone can have a look at my configs and shed a
little light on this for me.
Here's what happens at boot time:
Intel UNDI, PXE-2.0 (build 067)
Copyright (c) 1997, 1998 Intel Corporation
DHCP MAC ADDR
CLIENT ID: 192.168.254.133 MASK: 255.255.255.0 DHCP IP: 192.168.254.3
GATEWAY IP: 192.168.254.1
PXE Loader 1.00
Building the boot loader arguments
Relocating the loader and the BTX
Starting the BTX loader
BTX loader 1.00 BTX Version 1.01
Console: internal video/keyboard
BIOS drive A: is disk0
PXE Version 2.1, real mode entry point @9db3:0106
BIOS 639kB/392180kB available memory
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Thu Nov 30 11:45:41 PST 2000)
pxe_open: server addr: 192.168.254.3
pxe_open: server path: /tftpboot
pxe_open: gateway ip: 192.168.254.1
\
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
\ (if using pxeboot)
can't load 'kernel' (if using pxeboot.tftp)
Because it'll be fetching the pxeboot file via tftp, it's set up as follows:
# grep tftp /etc/inetd.conf
tftpdgram udp waitnobody /usr/libexec/tftpd tftpd -l
/tftpboot
Since I've also tried to get it to work using TFTP for the kernel (as
opposed to NFS) I run inetd with the -R0 flag so that connections to inetd
services aren't rate limited.
# ps ax | grep inetd
1088 ?? Ss 0:00.01 inetd -wW -R0
My /tftpboot is set up as follows:
# ll /tftpboot/*
-rw-r--r-- 1 root wheel 2034 Nov 12 09:12 /tftpboot/install.cfg
-r-xr-xr-x 1 root wheel 2441176 Nov 30 11:54 /tftpboot/kernel
-rw-r--r-- 1 root wheel 2949120 Nov 30 11:57 /tftpboot/mfsroot
-rw-r--r-- 1 root wheel 165888 Nov 30 11:46 /tftpboot/pxeboot
-rw-r--r-- 1 root wheel 165888 Nov 30 11:47 /tftpboot/pxeboot.tftp
/tftpboot/boot:
-r--r--r-- 1 root wheel 512 Nov 11 16:57 boot1
-r--r--r-- 1 root wheel7680 Nov 11 16:57 boot2
-r-xr-xr-x 1 root wheel 163840 Nov 11 16:57 loader
-rw-r--r-- 1 root wheel 190 Nov 30 12:51 loader.rc
-rw-r--r-- 1 root wheel 190 Nov 11 18:42 loader.rc.custom
-rw-r--r-- 1 root wheel 136 Nov 30 12:21 loader.rc.flp
All the files in the boot directory are off the 4.1-stable boot floppy. The
loader.rc.custom is the same as the example given on Alfred's page and the
.flp one is off the floppy.
The pxeboot and pxeboot.tftp are exactly what you'd expect. The pxeboot file
is the default pxeboot with NFS support and the pxeboot.tftp was generated
by editing the /etc/make.conf file, setting the TFTP flag and recompiling
pxeboot. The files definately are different because I can change the DHCP
file to point to the other file and get different results at boot time.
NFS is configured as follows:
matt# more /etc/exports
/-alldirs -ro
/usr -alldirs -ro
/cdrom -alldirs -maproot=root -ro
matt# mount
/dev/ad0s2a on / (ufs, NFS exported, local)
/dev/ad0s2e on /usr (ufs, NFS exported, local)
/dev/acd0c on /cdrom (cd9660, NFS exported, local, read-only)
The DHCP server is a FreeBSD 4.2-stable system (make buildworld on
11/29/00). The DHCP server is isc-dhcp 3.0b2pl9 and is configured as shown:
option broadcast-address 192.168.254.255;
option domain-name-servers 192.168.254.3;
option domain-name "domain.com";
option routers 192.168.254.1;
option subnet-mask 255.255.255.0;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
server-name "DHCPserver";
server-identifier 192.168.254.3;
subnet 192.168.254.0 netmask 255.255.255.0 {
option routers 192.168.254.1;
option root-path "/tftpboot";
filename "pxeboot";
#filename "pxeboot.tftp";(compiled for TFTP boot support vs
standard NFS)
range 192.168.254.32 192.168.254.99;
}
host c3.domain.com {
hardware ethernet 00:02:b3:1c:c6:02;
next-server 192.168.254.3;
fixed-address 192.168.254.133;
default-lease-time -1;
class "pxeclients"
{ match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
option vendor-class-identifier "PXEClient";
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
}
}
So, what am I missing?
Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Boot problem!
Excuse that I again trouble you, but after I read snth on Freebsd.org I have such questions. I installed FreeBSD 3.5 on Compaq Proliant 1500 with SCSI disks and after booting I receive such message: changing root device to wd0s1a changing root device to wd0a error 6: panic: cannot mount root (2) My / filesystem is on idad0s1a so I tried when booting wrote so boot: 0:da(0,a)/boot/loader but it doesn't help, please answer me what I must write in the beggining of booting(or somewhere else) to boot from my SCSI disks Thank you very much To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
