Re: Kernel question
On Friday 01 July 2005 11:02 pm, Nikolas Britton wrote: On 7/1/05, Bryan Maynard [EMAIL PROTECTED] wrote: I read through your kernel - very nice comments, thanks a lot! I compiled the kernel and boot-up is noticably faster, thanks again! I would like to investigate transfering all the device info from boot -v to LATITUDE_C600.hints. I don't really know what most of the info from boot -v means, I'd like to work on figuring it out. Maybe you could help me learn and we could figure it out together? Any help you could give you be greatly appreciated! One thing of note: I don't have any sound. I've never had sound, but after booting with the new kernel I went into KDE's control panel and tested the sound system, but nothing came out. I didn't get any errors when it restarted the sound system so I'm not sure what's up. Your using the wrong driver. the one you want is snd_maestro3. Add this to your loader.conf file: #sound_load=YES#PCM Sound Support #snd_driver_load=YES # Loads every sound drivers it can find snd_maestro3=YES # Your driver hw.snd.maxautovchans=4 #sets up up to 4 virtual audio channels on demand #hw.snd.targetirqrate=36# read the sound man page #hint.pcm.0.buffersize=16384 #read the sound man page After you do that reboot and retest it. first thing is to check dmesg. dmesg|grep -i pcm and do the same for ess and maestro, you should see that it was detected. also you should try 'cat /dev/sndstat'. fire up X and well, anyways if everything is working put the driver in the kernel config file and comment it out in loader.conf. I'll see what I can do about your other questions later, right now I need a smoke and have work to do. My sound is working now, thanks :-) My battery doesn't seem to be charging though. . . Everytime I boot dmesg tells me that my battery has a critically low charge. I do not know how to correct this. I just need my battery to work and I'll have a fully functional laptop! I've incuded the dmesg output from the new kernel boot in case you need to look at it along with my current CUSTOM.hints file (maybe it'll help. . . :-?) Anyway, thanks a lot for the new kernel, it works like a charm! Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for all your help! Bryan -- Open Source: by the people, for the people. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question
On 6/30/05, Bryan Maynard [EMAIL PROTECTED] wrote: I checked out the man pages you listed, thanks for the help! I didn't understand everything in all of them, but they did help me firgure out some more questions to ask. Is it possible to identify all hardware component in my system in the device.hints file and if so, what would that accomplish? I am running a Dell Latitude C600. Do this with the kernel .hints file. it will be statically compile into the kernel then. kernel.hints = statically compiled = faster boot. device.hints = dynamic-ish = slower, but still faster then random probing. Also, I have a custom kernel I am trying to tweak. However, when I boot from it I get the following messages: ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata1-master: FAILURE - ATAPI_IDENTIFY timed out ata1-master: timeout sending command=a1 ata1-master: error issueing ATAPI_IDENTIFY command ata1-master: FAILURE - ATAPI_IDENTIFY timed out Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 It then asks me to manually enter a root filesystem. I've attached my CUSTOM kernel config. Along with my CUSTOM.hints file. I don't use CUSTOM.hints, but it has hints about the nexus device. this device shows up when I use boot-v. I'm not sure If I have it's info entered properly, maybe you could help me with that. I've attached a kernel for you to use. Compare it to yours (and GENERIC) and read the comments I made in it. It should address most of your questions. Could I use the info from a boot -v in the device.hints file? If so, how do I translate the syntax. I've looked at the boot -v output before and it seems like there's enough info for the device.hints file, I just don't know what it all means or how to extract it. You can put the boot -v info into the kernel .hints file, I think. I never tried to do anything like that and I'm not sure how to go about doing it. Or maybe thats what kenv is for... hmmm LATITUDE_C600 Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question
I read through your kernel - very nice comments, thanks a lot! I compiled the kernel and boot-up is noticably faster, thanks again! I would like to investigate transfering all the device info from boot -v to LATITUDE_C600.hints. I don't really know what most of the info from boot -v means, I'd like to work on figuring it out. Maybe you could help me learn and we could figure it out together? Any help you could give you be greatly appreciated! One thing of note: I don't have any sound. I've never had sound, but after booting with the new kernel I went into KDE's control panel and tested the sound system, but nothing came out. I didn't get any errors when it restarted the sound system so I'm not sure what's up. I've incuded the dmesg output from the new kernel boot in case you need to look at it along with my current CUSTOM.hints file (maybe it'll help. . . :-?) Anyway, thanks a lot for the new kernel, it works like a charm! Bryan On Friday 01 July 2005 05:58 pm, Nikolas Britton wrote: On 6/30/05, Bryan Maynard [EMAIL PROTECTED] wrote: I checked out the man pages you listed, thanks for the help! I didn't understand everything in all of them, but they did help me firgure out some more questions to ask. Is it possible to identify all hardware component in my system in the device.hints file and if so, what would that accomplish? I am running a Dell Latitude C600. Do this with the kernel .hints file. it will be statically compile into the kernel then. kernel.hints = statically compiled = faster boot. device.hints = dynamic-ish = slower, but still faster then random probing. Also, I have a custom kernel I am trying to tweak. However, when I boot from it I get the following messages: ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata1-master: FAILURE - ATAPI_IDENTIFY timed out ata1-master: timeout sending command=a1 ata1-master: error issueing ATAPI_IDENTIFY command ata1-master: FAILURE - ATAPI_IDENTIFY timed out Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 It then asks me to manually enter a root filesystem. I've attached my CUSTOM kernel config. Along with my CUSTOM.hints file. I don't use CUSTOM.hints, but it has hints about the nexus device. this device shows up when I use boot-v. I'm not sure If I have it's info entered properly, maybe you could help me with that. I've attached a kernel for you to use. Compare it to yours (and GENERIC) and read the comments I made in it. It should address most of your questions. Could I use the info from a boot -v in the device.hints file? If so, how do I translate the syntax. I've looked at the boot -v output before and it seems like there's enough info for the device.hints file, I just don't know what it all means or how to extract it. You can put the boot -v info into the kernel .hints file, I think. I never tried to do anything like that and I'm not sure how to go about doing it. Or maybe thats what kenv is for... hmmm -- Open Source: by the people, for the people. # $FreeBSD: src/sys/i386/conf/CUSTOM.hints,v 1.13 2005/04/14 14:50:31 maynard Exp $ hint.npx.0.at=nexus hint.npx.0.port=0x0F0 hint.npx.0.flags=0x0 hint.npx.0.irq=13 hint.acpi_timer.0.port=0x808-0x80b hint.acpi_timer.0.at=acpi hint.ata.0.at=isa hint.ata.0.port=0x1F0 hint.ata.0.irq=14 hint.ata.1.at=isa hint.ata.1.port=0x170 hint.ata.1.irq=15 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.vga.0.at=isa hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.apm.0.disabled=0 hint.apm.0.flags=0x20 hint.pcic.0.at=isa #hint.pcic.0.irq=10 hint.pcic.0.port=0x3e0 hint.pcic.0.maddr=0xd hint.pcic.1.at=isa hint.pcic.1.irq=11 hint.pcic.1.port=0x3e2 hint.pcic.1.maddr=0xd4000 hint.pcic.1.disabled=0 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.ed.0.at=isa hint.ed.0.port=0x280 hint.ed.0.irq=5 hint.ed.0.maddr=0xd8000 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question
On 7/1/05, Bryan Maynard [EMAIL PROTECTED] wrote: I read through your kernel - very nice comments, thanks a lot! I compiled the kernel and boot-up is noticably faster, thanks again! I would like to investigate transfering all the device info from boot -v to LATITUDE_C600.hints. I don't really know what most of the info from boot -v means, I'd like to work on figuring it out. Maybe you could help me learn and we could figure it out together? Any help you could give you be greatly appreciated! One thing of note: I don't have any sound. I've never had sound, but after booting with the new kernel I went into KDE's control panel and tested the sound system, but nothing came out. I didn't get any errors when it restarted the sound system so I'm not sure what's up. Your using the wrong driver. the one you want is snd_maestro3. Add this to your loader.conf file: #sound_load=YES#PCM Sound Support #snd_driver_load=YES # Loads every sound drivers it can find snd_maestro3=YES # Your driver hw.snd.maxautovchans=4 #sets up up to 4 virtual audio channels on demand #hw.snd.targetirqrate=36# read the sound man page #hint.pcm.0.buffersize=16384 #read the sound man page After you do that reboot and retest it. first thing is to check dmesg. dmesg|grep -i pcm and do the same for ess and maestro, you should see that it was detected. also you should try 'cat /dev/sndstat'. fire up X and well, anyways if everything is working put the driver in the kernel config file and comment it out in loader.conf. I'll see what I can do about your other questions later, right now I need a smoke and have work to do. I've incuded the dmesg output from the new kernel boot in case you need to look at it along with my current CUSTOM.hints file (maybe it'll help. . . :-?) Anyway, thanks a lot for the new kernel, it works like a charm! Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question
On 6/29/05, Bryan Maynard [EMAIL PROTECTED] wrote: Hey helpful friends! :-D I would like to conduct an experiment: down the road (a couple years maybe) I'd like to start building and selling PCs. I'd like these PCs to run FreeBSD - because it's the best ;-). These machines will be a slightly different from the current crop in that they will be laptops that will not have PCMCIA slots or CD/DVD drives (these items will be held in a separate breakout box). The machines wil lbe completely sealed with the exception of the various memory card (SD, CompactFlash, Memory stick, etc.) embeded in the monitor casing. There's much more to these machines, but I'll save those details for the appropriate place - my question for here is this: I'd like to minimize boot time as much as possible. Since these machines will not ever have hardware added or changed I would like to statically build as much device information as early in the boot process as possible. I understand that FreeBSD has a three stage boot process. I'm a bit fuzzy as to what happens when, but was wondering how, or if, I could cut out any of these stages - and shorten the remaining stages as much as possible. I've looked around loader.conf, device.hints, KERNEL.hints, and such and this is what got me wondering. If you all need anymore info please let me know. Thanks a lot! Bryan -- http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/boot.html Man pages: loader.conf loader loader.4th boot btxld boot0cfg device.hints kenv The majority of the boot process time is the BIOS testing and initializing hardware and there is no simple way around this. The best place to start is to rip everything out of the kernel config file. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question
I checked out the man pages you listed, thanks for the help! I didn't understand everything in all of them, but they did help me firgure out some more questions to ask. Is it possible to identify all hardware component in my system in the device.hints file and if so, what would that accomplish? I am running a Dell Latitude C600. Also, I have a custom kernel I am trying to tweak. However, when I boot from it I get the following messages: ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata0-master: FAILURE - ATA_IDENTIFY timed out ata1-master: FAILURE - ATAPI_IDENTIFY timed out ata1-master: timeout sending command=a1 ata1-master: error issueing ATAPI_IDENTIFY command ata1-master: FAILURE - ATAPI_IDENTIFY timed out Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 It then asks me to manually enter a root filesystem. I've attached my CUSTOM kernel config. Along with my CUSTOM.hints file. I don't use CUSTOM.hints, but it has hints about the nexus device. this device shows up when I use boot-v. I'm not sure If I have it's info entered properly, maybe you could help me with that. Could I use the info from a boot -v in the device.hints file? If so, how do I translate the syntax. I've looked at the boot -v output before and it seems like there's enough info for the device.hints file, I just don't know what it all means or how to extract it. I've also included the output from kenv and dmesg if that will help. It says the kernel is kernel.old, but that's because I had to boot from that after writing down the messages I got when booting from my CUSTOM kernel. kernel.old is my GENERIC kernel though. Anyway, thanks for your help! Bryan On Thursday 30 June 2005 06:47 am, Nikolas Britton wrote: On 6/29/05, Bryan Maynard [EMAIL PROTECTED] wrote: Hey helpful friends! :-D I would like to conduct an experiment: down the road (a couple years maybe) I'd like to start building and selling PCs. I'd like these PCs to run FreeBSD - because it's the best ;-). These machines will be a slightly different from the current crop in that they will be laptops that will not have PCMCIA slots or CD/DVD drives (these items will be held in a separate breakout box). The machines wil lbe completely sealed with the exception of the various memory card (SD, CompactFlash, Memory stick, etc.) embeded in the monitor casing. There's much more to these machines, but I'll save those details for the appropriate place - my question for here is this: I'd like to minimize boot time as much as possible. Since these machines will not ever have hardware added or changed I would like to statically build as much device information as early in the boot process as possible. I understand that FreeBSD has a three stage boot process. I'm a bit fuzzy as to what happens when, but was wondering how, or if, I could cut out any of these stages - and shorten the remaining stages as much as possible. I've looked around loader.conf, device.hints, KERNEL.hints, and such and this is what got me wondering. If you all need anymore info please let me know. Thanks a lot! Bryan -- http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/boot.html Man pages: loader.conf loader loader.4th boot btxld boot0cfg device.hints kenv The majority of the boot process time is the BIOS testing and initializing hardware and there is no simple way around this. The best place to start is to rip everything out of the kernel config file. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Open Source: by the people, for the people. # # CUSTOM -- Custom kernel configuration file for FreeBSD/i386 created by Bryan Maynard # Last updated: 2005-06-29 # $FreeBSD: src/sys/i386/conf/CUSTOM,v 1.413.2.9 2005/06/29 12:00:10 maynard Exp $ machine i386 cpu I686_CPU ident CUSTOM options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options CD9660 # ISO 9660 Filesystem options PSEUDOFS# Pseudo-filesystem framework options PROCFS
Re: Kernel Question
Sean Murphy wrote: The FreeBSD kernel is monolithic correct? Hmm, how 'bout modern monolithic module-loading kernel? Does it support or does it use kernel loadable modules and if so why? The general reason would be to support extension of the kernel's capabilities at runtime, while keeping the amount of code running in kernelspace as low as possible Kevin Kinsey, No kernel expert, but eats corn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Question
On 2005-01-31 09:17, Sean Murphy [EMAIL PROTECTED] wrote: The FreeBSD kernel is monolithic correct? Yes. At least, sort of. Does it support or does it use kernel loadable modules and if so why? Yes. Because by not having everything loaded at the same time, a lot of memory can be saved. Memory which can be used to do more useful stuff. PS: You could have found hundreds of thousands of references for FreeBSD kernel modules on Google (almost 800,000 hits), without posting here. Use the network, please :P ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel question about sk(4)
On Fri, 2004-04-16 at 23:02, Mark wrote: I have a question about the sk(4) driver. I want to use the 3Com 3C940, onboard an ASUS K8V Deluxe motherboard, using FreeBSD 4.9R. I asked this before; but this is not really a 3com question, but more a kernel question, I think. At the SYNOPSIS of sk(4), I read: device miibus device sk Does that mean I need to recompile the kernel? Because device sk is not part of my kernel config, it seems. If sk is not in your current kernel config (GENERIC if you haven't changed it) then you either need to re-compile the kernel with the device listed, or use the module. Likely a module exists for sk on your system at /boot/modules, and you could just load it with kldload. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
