Re: freebsd broken after kernel re-compile.
well yesterday I recompiled the kernel again turning on and off some of the options I had previously changed just to see if that what would change. I was able to get both NIC cards up and the routing services on. The problem is that now the card that used to be rl0 is now rl1 and the one that used to be rl1 is now rl0. It doesn't really matter that much since I just had to change the variables in some settings. And everything started working fine. Is there a reason why this happened? why did the system re-asisgn the names of the NICs? On 5/22/07, Reid Linnemann <[EMAIL PROTECTED]> wrote: Comments inline: Written by Yanko Sanchez on 05/21/07 19:44>> > @youshi10: > yeah, I'm aware that MacOSX supports for unix, but at the time that we > transfered the data to the hdd we didn't know which server was gonna > be running the hdd... Fat32 was the only FS that we know would be > compatible with any OS (but we didn't know of the size limit) so if > the server had been a Windows 2003 server, I don't think I would have > had any chance of opening that FS (unless 3rd party software if there > is any) > > > Anyways, here is the info that Reid asked for. > > 1: I updated the ports tree following the instructions of freebsd wiki > The FreeBSD wiki is a collection of pages, I need to know which specific pages contained your instructions. > 2: I recompiled the kernel following the instructions of freebsd wiki: > cp /usr/src/sys/i386/conf/BASTION /usr/src/sys/i386/conf/BASTION2 > vim /usr/src/sys/i386/conf/BASTION2 > added option MSDOSFS_LARGE > > cd /usr/src > make buildkernel KERNCONF=BASTION2 > > make installkernel KERNCONF=BASTION2 > reboot > This is a standard way to install a new kernel. > 3: uname -a: > FreeBSD bastion 6.2-STABLE FreeBSD 6.2-STABLE #2L Mon May 21 00:30:39 > PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BASTION2 i386 > > 4: iffconfig -a: > bastion# ifconfig -a > > rl0: flags=8843 mtu 1500 > options=8 > atalk 65280.205 range 0-65534 phase 2 broadcast 0.255 > ether 00:e0:18:8d:10:8f > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=108802 mtu 1500 > options=8 > ether 0a:00:46:29:6f:02 > ch 1 dma -1 > plip0: flags=108810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff00 > atalk 0.0 range 0-0 phase 2 > > Also, I think my network card that shows up took the place of the > otherone, in other words, rl1 is now rl0 and rl1 is gone... I don't > know if that just changed cos it can't find the other network card. > > I think the output of pciconf -lv might help as well. You should be able to boot back up in your old kernel so you can at least get back to your previous working conditions. When you boot the machine, and you see the boot menu, select the option to escape to the loader prompt. Here, 'unload kernel' and 'load /boot/kernel.old/kernel', then 'boot' to start the system. Whenever you make installkernel from the source tree, it will back up your old kernel and modules in /boot/kernel.old. Alternatively, you can move /boot/kernel to /boot/kernel.bak and move /boot/kernel.old to /boot/kernel to restore your original kernal and modules, and reboot the machine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd broken after kernel re-compile.
Comments inline: Written by Yanko Sanchez on 05/21/07 19:44>> @youshi10: yeah, I'm aware that MacOSX supports for unix, but at the time that we transfered the data to the hdd we didn't know which server was gonna be running the hdd... Fat32 was the only FS that we know would be compatible with any OS (but we didn't know of the size limit) so if the server had been a Windows 2003 server, I don't think I would have had any chance of opening that FS (unless 3rd party software if there is any) Anyways, here is the info that Reid asked for. 1: I updated the ports tree following the instructions of freebsd wiki The FreeBSD wiki is a collection of pages, I need to know which specific pages contained your instructions. 2: I recompiled the kernel following the instructions of freebsd wiki: cp /usr/src/sys/i386/conf/BASTION /usr/src/sys/i386/conf/BASTION2 vim /usr/src/sys/i386/conf/BASTION2 added option MSDOSFS_LARGE cd /usr/src make buildkernel KERNCONF=BASTION2 make installkernel KERNCONF=BASTION2 reboot This is a standard way to install a new kernel. 3: uname -a: FreeBSD bastion 6.2-STABLE FreeBSD 6.2-STABLE #2L Mon May 21 00:30:39 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BASTION2 i386 4: iffconfig -a: bastion# ifconfig -a rl0: flags=8843 mtu 1500 options=8 atalk 65280.205 range 0-65534 phase 2 broadcast 0.255 ether 00:e0:18:8d:10:8f media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=108802 mtu 1500 options=8 ether 0a:00:46:29:6f:02 ch 1 dma -1 plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 atalk 0.0 range 0-0 phase 2 Also, I think my network card that shows up took the place of the otherone, in other words, rl1 is now rl0 and rl1 is gone... I don't know if that just changed cos it can't find the other network card. I think the output of pciconf -lv might help as well. You should be able to boot back up in your old kernel so you can at least get back to your previous working conditions. When you boot the machine, and you see the boot menu, select the option to escape to the loader prompt. Here, 'unload kernel' and 'load /boot/kernel.old/kernel', then 'boot' to start the system. Whenever you make installkernel from the source tree, it will back up your old kernel and modules in /boot/kernel.old. Alternatively, you can move /boot/kernel to /boot/kernel.bak and move /boot/kernel.old to /boot/kernel to restore your original kernal and modules, and reboot the machine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd broken after kernel re-compile.
@youshi10: yeah, I'm aware that MacOSX supports for unix, but at the time that we transfered the data to the hdd we didn't know which server was gonna be running the hdd... Fat32 was the only FS that we know would be compatible with any OS (but we didn't know of the size limit) so if the server had been a Windows 2003 server, I don't think I would have had any chance of opening that FS (unless 3rd party software if there is any) Anyways, here is the info that Reid asked for. 1: I updated the ports tree following the instructions of freebsd wiki 2: I recompiled the kernel following the instructions of freebsd wiki: cp /usr/src/sys/i386/conf/BASTION /usr/src/sys/i386/conf/BASTION2 vim /usr/src/sys/i386/conf/BASTION2 added option MSDOSFS_LARGE cd /usr/src make buildkernel KERNCONF=BASTION2 make installkernel KERNCONF=BASTION2 reboot 3: uname -a: FreeBSD bastion 6.2-STABLE FreeBSD 6.2-STABLE #2L Mon May 21 00:30:39 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BASTION2 i386 4: iffconfig -a: bastion# ifconfig -a rl0: flags=8843 mtu 1500 options=8 atalk 65280.205 range 0-65534 phase 2 broadcast 0.255 ether 00:e0:18:8d:10:8f media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=108802 mtu 1500 options=8 ether 0a:00:46:29:6f:02 ch 1 dma -1 plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 atalk 0.0 range 0-0 phase 2 Also, I think my network card that shows up took the place of the otherone, in other words, rl1 is now rl0 and rl1 is gone... I don't know if that just changed cos it can't find the other network card. On 5/21/07, Reid Linnemann < [EMAIL PROTECTED]> wrote: Written by Yanko Sanchez on 05/21/07 14:03>> > Thanks for anyone that has helped so far, I'm a freebsd newbie coming > from linux. > > > So I basically re-compiled my kernel with the LARGE option on and it > seems to mount the drive fine. I encountered another problem tho. > > Before I recompiled the kernel I updated the ports tree, basically cos > I just wanted to see how it was done and it seemed to be successful. > The problem is that after I recompiled the kernel a bunch of stuff > stoped working. I have the server setup as a router and my to Network > cards isn't showing up anymore (both being the same type of cards, I > use to have rl0 and rl1) so It isn't routing anymore, and now im > getting a bunch of DHCPREQUEST messages on startup which I wasn't > getting before. And other errors saying that my network card isn't > configured. I checked /etc/rc.conf and the lines for ifconfig are > still in there... > > Did I upgrade the kernel sources by doing an upgrade to the ports? > That would make sense, but what bugs me is that I copied the same > kernel config and just added the MSDOSFS_LARGE option once I booted up > I got the errors mentioned above. Shouldn't it have stayed pretty much > the same? I'm just trying to get a better understand if what happened > to that I don't make the same mistake. > > > 1. How did you upgrade your ports tree? 2. How did you recompile the kernel? 3. What does uname -a report? 4. what is the output of ifconfig -a? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
