too many debug messages on dmesg
anyone have a clue about this problem in dmesg log? at_matroute: v=(16)10ff007100 at_matroute: head=0xc4392800 at_matroute: returnr rn=0xc459a6c8 at_matroute: v=(16)10ff007100 i know it is something related to netatalk, but i would like to be less verbose ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
ok, sorry... 2009/11/12 Jerry McAllister jerr...@msu.edu On Thu, Nov 12, 2009 at 09:38:27AM -0600, Jesús Abidan wrote: First, please send all messages to the freebsd-questions list and not just to me. That is proper list etiquette, plus you will be able to get responses from more than just me. Others may know more. In other words, always do a 'reply all' on list email. read this: First, be aware that all the information necessary to boot FreeBSD must be located within the first 1,024 cylinders of the hard disk. This is necessary for the FreeBSD boot manager to work; it means that when you partition the disk for FreeBSD using FIPS, either the root partition must be completely located within the first 1,024 cylinders or you can use a separate boot partition that is completely located in the first 1,024 cylinders. Use the Start and End cylinder readouts in FIPS to determine where your partitions start and end. If you choose the latter option, the root partition does not have to be completely located in the first 1,024 cylinders. Note that completely located means that the partition has to both start and end below the 1,024th cylinder. Simply starting below the 1,024th cylinder is not good enough. This is obsolete information for most computers with BIOS and disks created later than about 1998. That really means all computers functioning today. It is also obsolete for FreeBSD systems which do not use BIOS to talk to the disk. There are numerous web sites that explain this including some documentation on the FreeBSD web site:http://www.freebsd.org/ jerry http://www.informit.com/articles/article.aspx?p=32084seqNum=4; as i see, do i need to create a partition(located in the first 1024cylinders) to BOOT from? (sorry) 2009/11/12 Jesús Abidan jabi...@gmail.com no, it's not vista, is XP 2009/11/12 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: i did it like you say, but something is happening with my installation, it boots always the first OS, i don't have any ideas for having a dual system... argh!! Perchance, is your other system MS-Vista? As I mentioned in a previous response, I have heard of people having problems with dual booting with Vista and having to follow some other procedure for that. But, I haven't used Vista (and do not intend to) so you will have to do some archive searching to find those pieces of information. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: so, then i need to create 2 slices with gparted, install windows on the first one, and install freebsd on the second one and label this partition automatically by the installer (ad0s1, ad0s2, etc) and install the bootmgr? Yes, essentially except for those partition names. Create the two slices/primary partitions. Install the MS-Win in the first one. I think then MS will call it 'c:' Anyway, FreeBSD will think it is ad0s1. Then install FreeBSD in the second slice/primary partition. MS will not even know it is there. FreeBSD will call it ad0s2. During the install, that ad0s2 slice will be subdivided according to how you tell it into FreeBSD partitions with names like ad0s2a (for root) and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e for something else, such as /usr, etc. For my general purpose machines I usually subdivide in to the following partitions: amounts as / eg: mount /dev/ad0s2a / b swap cdescribes the slice and is not a real partition dmounts as /tmp eg: mount /dev/ad0s2d /tmp emounts as /usr etc fmounts as /var gmounts as /home or something similar For my systems that are single purpose central servers I tend to do this: amounts as / everything but swap and afscache goes in root. b swap cslice description d/afscache If I have a second drive for scratch or work space I tend to do: amounts as /work and uses up all the space except extra swap bused for additional swap cdescribes the slice The sizes of the various partition-subdivisions depends on the size of the disk and the use being made of the machine and what I want to install on it and how I want to handle backups. jerry 2009/11/11 Jerry McAllister jerr...@msu.edu On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: ok. the slices in freebsd are little tricky, i will check my installation and send
Re: cannot boot freebsd
no idea... the machine had only one hard drive(PATA), then i plugged a new sata HD(freebsd style), with information on it. The PATA drive is cofigured as the primary disk, and the sata in bios it says is in PORT 0. I'll try removing the SATA disk and install freebsd, maybe is the jumper configuration. 2009/11/12 Jerry McAllister jerr...@msu.edu On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: i think i have the problem... i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is F: instead of C: maybe it is something related to jumpers or something like that? That is a little surprise to me, but I am not up on the ins and outs of IDE/SATA labeling.Most of my machines - all of the servers - have SCSI or SAS disk which does it differently (and more easily). My only SATA machines have only a single disk. One thing to ask is: what does it have as c:, d: and e: ?? Maybe something is plugged in the wrong - or inconvenient - order on the controller. Or, I suppose there might be a jumper issue. jerry 2009/11/12 Jesús Abidan jabi...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot boot freebsd
no, it is not the disk, i removed it and the same problem... 2009/11/12 Jesús Abidan jabi...@gmail.com no idea... the machine had only one hard drive(PATA), then i plugged a new sata HD(freebsd style), with information on it. The PATA drive is cofigured as the primary disk, and the sata in bios it says is in PORT 0. I'll try removing the SATA disk and install freebsd, maybe is the jumper configuration. 2009/11/12 Jerry McAllister jerr...@msu.edu On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: i think i have the problem... i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is F: instead of C: maybe it is something related to jumpers or something like that? That is a little surprise to me, but I am not up on the ins and outs of IDE/SATA labeling.Most of my machines - all of the servers - have SCSI or SAS disk which does it differently (and more easily). My only SATA machines have only a single disk. One thing to ask is: what does it have as c:, d: and e: ?? Maybe something is plugged in the wrong - or inconvenient - order on the controller. Or, I suppose there might be a jumper issue. jerry 2009/11/12 Jesús Abidan jabi...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
cannot boot freebsd
Hi there, i have a problem here, i installed windows in mi box and i left a partition for freebsd, i finished install of freebsd and installed the boot mgr of freebsd but when i reboot only windows boots with f1 pressed? how can I make the system boots both? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FATAL TRAP 12
Someone has had problems with this type of issues? what it is related to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kernel trap
sorry for bothering guys, but i have a big problem here, i recently installed freebsd on a box and i was very happy updating ports, when i realized the system suddenly reboot, when i saw the dmesg it says: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x828dee24 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0a27b0b stack pointer = 0x28:0xe4f2fb80 frame pointer = 0x28:0xe4f2fb94 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 48 (vnlru) trap number = 12 panic: page fault cpuid = 1 Uptime: 18m45s Physical memory: 1522 MB Dumping 203 MB: 188 172 156 140 124 108 92 76 60 44 28 12 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... I searched in google for something but it seems i need to dump the kernel, i guess if it could be an HD issue. By the way, the current process line has little variations (g_down, fsck_ufs, vnlru Any clue? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hi! a question about log in dmesg
Hi, there, i am a pretty good user in linux and i don't know i am getting some strange info in my dmesg file: at_matroute: v=(16)10ff007f00 at_matroute: head=0xc42c1700 at_matroute: returnr rn=0xc45b126c at_matroute: v=(16)10ff007f00 at_matroute: head=0xc42c1700 at_matroute: returnr rn=0xc45b126c at_matroute: v=(16)10ff007f00 at_matroute: head=0xc42c1700 at_matroute: returnr rn=0xc45b126c at_matroute: v=(16)10ff007f00 at_matroute: head=0xc42c1700 at_matroute: returnr rn=0xc45b126c at_addroute: v=(16)10fffe at_addroute: n=(16)10 at_addroute: head=0xc42c1700 treenodes=0xc45b12e8 at_addroute: returns rn=0xc45b12e8 at_addroute: v=(16)10ff007f00 at_addroute: n=null at_addroute: head=0xc42c1700 treenodes=0xc45b126c at_addroute: returns rn=0xc45b126c at_delroute: v=(16)10ff00 at_delroute: n=(16)10ff80 at_delroute: head=0xc42c1700 at_delroute: returns rn=0xc45b2e88 at_delroute: v=(16)10ff80 at_delroute: n=(16)10ffc0 at_delroute: head=0xc42c1700 at_delroute: returns rn=0xc45b2e0c and calcru: runtime went backwards from 229 usec to 114 usec for pid 690 (devd) calcru: runtime went backwards from 551 usec to 468 usec for pid 376 (dhclient) calcru: runtime went backwards from 1999 usec to 999 usec for pid 360 (dhclient) calcru: runtime went backwards from 39486 usec to 19742 usec for pid 360 (dhclient) calcru: runtime went backwards from 668 usec to 334 usec for pid 146 (adjkerntz) calcru: runtime went backwards from 57078 usec to 47420 usec for pid 51 (sh) calcru: runtime went backwards from 1964549 usec to 1411651 usec for pid 51 (sh) i know there is an issue about acpi and intel chipset or something like that but i have no results about changing things in bios. I have desactivate udma and no results. the firs message about at_matroute and delroute issues i have no idea. Anyone has a clue??? greetings to everyone out there! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
