Date: Fri, 1 Jul 2005 12:58:59 -0500 From: Nikolas Britton <nikolas.britton@gmail.com> To: Bryan Maynard <bryan.maynard@reallm.com> Cc: freebsd-questions@freebsd.org Subject: Re: Kernel question Message-ID: <ef10de9a050701105849558f2a@mail.gmail.com> In-Reply-To: <200506301717.33857.bryan.maynard@reallm.com> References: <200506292116.00205.bryan.maynard@reallm.com> <ef10de9a050629234750b79f36@mail.gmail.com> <200506301717.33857.bryan.maynard@reallm.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 6/30/05, Bryan Maynard <bryan.maynard@reallm.com> 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 [-- Attachment #2 --] machine i386 cpu I686_CPU ident LATITUDE_C600 # To statically compile in device wiring instead of /boot/device.hints #hints "LATITUDE_C600.hints" # Default places to look for devices. 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 MSDOSFS # MSDOS Filesystem #options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC options CLK_USE_I8254_CALIBRATION # Use specialized CPU clock calibration. # You can't use any of these options: #CPU_FASTER_5X86_FPU is for old cyrix 5x86 chips, this may be why your # system won't boot with the kernel you made. #CPU_UPGRADE_HW_CACHE has absolutely no effect on non-PC98 systems. #NO_F00F_HACK this is only for Pentiums I's, it does absolutely # nothing for PPro, PII, PIII, PIV CPUs. # They need to comment the NOTES file better. # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # You don't have a i8259A so you can't use AUTO_EOI_1 and AUTO_EOI_2 options. plus # it breaks power management on notebooks. You don't need eisa, it's been dead # for years and it would have never been in a notebook anyways, it's for 32-bit # ISA cards. This was mainly used in servers, and some workstations. # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse # Video Support device vga # VGA video card driver device agp # AGP GART support (supports several AGP chipsets) device "r128drm" # ATI Rage 128 Direct Rendering Module options VESA # Full VESA BIOS support options SC_PIXEL_MODE # Rastered text mode (VESA graphic modes) # I have a patch to get 1024x768 at the console, email me if you want it. device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. # This is your nexus device, the FPU is basicly a # super fast calculator inside your CPU. don't # change any of the nexus stuff in the .hints file device npx # Power management support (see NOTES for more options) # You cannot use apm and acpi at the same time, pick only one. # If your having major power management problems etc. install # SuSE 9.3 Pro on your system. I have a similer notebook, # HP Omnibook 6000 / PIII 700Mhz / 440BX / ATI Video / ESS maestro3, # and it works like a dream with SuSE on it. #device apm device pmtimer device acpi device acpi_video # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Wireless NIC cards, It would be a good idea to keep these for a notebook. device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) # I disabled INET6 up at the top so you don't need gif or faith. ppp # and slip are for modems. # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support. I deleted ohci, your notebook only has uhci. device uhci # UHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # Sound Support device sound # Sound support device snd_sbc # Creative Sound Blaster? #"The snd_sbc bridge driver allows the generic audio drivers including # sound(4) to attach to Creative Sound Blaster ISA compatible audio cards." device snd_ess # ESS maestro3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a050701105849558f2a>