printing boot probe messages
Chuck Robey
chuckr at chuckr.org
Tue Dec 25 11:49:46 PST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bernd Walter wrote:
> On Sun, Dec 23, 2007 at 01:12:49PM -0500, Chuck Robey wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Dag-Erling Smørgrav wrote:
>>> Chuck Robey <chuckr at chuckr.org> writes:
>>>> I've lost the printing of all of th e messages you normally see, when you are
>>>> booting yoiur machine (you know, mostly probe messages. I used to see them on
>>>> this box. When I made my first kernel, I had begun (obviously, as we all do)
>>>> with GENERIC as a base, but changing the first loaders.hints and the kernel,
>>>> that's the last I saw of booting messages.
>>> You say something stopped working after you fiddled with some config
>>> files, but you don't show us those config files nor even tell us *which*
>>> config files you modified in terms that we can understand (there is no
>>> such thing as loader.hints).
>> Dag, I looked through all my older messages, I couldn't see where I'd given
>> you the misimpression about stuff stopping working when I made my first
>> kernel. Teh target then was to maintain booting, which it did, and I don't
>> remember anything specific that stopped working. The sound, for instance,
>> didn't work before, and also didn't immediately work thereafter. The only
>> striking change, beyond jumping to current, was the uname print, and the
>> sudden jarring cessation of all the boot messages (that, I could hardly
>> have missed, it worried me more than a little at first, I though the
>> machine had hung during boot!)
>
> We all know that you have fiddled with a config file, because that's the
> only possible reason for this to happen.
>
>> Anyhow, I don't have that first config file. I have the one I'm using now,
>> so in the assumption that you would like to see that, I'm going to paste it
>> at the end. The only thing that I can comment on, so far, is that my
>> motherboard hasn't got any serial devices, no uarts, so I don't have any
>> ttyd0 device, and that's (I think) why it doesn't show up on any
>> conscontrol listing. Is there a better device to have set up, as my
>> console output? Note that my kernel config file has the sc (syscons,
>> right?) device, in case either I have done that wrong, or maybe it might
>> mean I should spec some specific device to conscontrol.
>>
>>
>> # To statically compile in device wiring instead of /boot/device.hints
>> hints "APRIL.hints" # Default places to look for devices.
>
> We all need to see your APRIL.hints and as already asked for your
> /boot/device.hints
> Why do you need statically compiled in hints at all?
> This is normaly only done for exotic boot environments (e.g. on embedded
> systems) where the normal bootchain can't be used.
>
OK, I think I might finally be understanding you a bit better (I hope so,
at least, I'm surely not trying to make things hard). The config file I
was always referring to, it's the kernel config file (I named it APRIL in
the config file). I've lost that first APRIL, the one where the boot
messages stopped. I think the other confusion lies in what broke: not
hardware: the printing of the boot messages is what broke, that's all,
nothing else. My goal in recompiling was only (besides jumping to current)
was to get rid of all the devices I didn't use, in GENERIC. I'd intended
to attach my APRIL listing to the last mail, but I must have screwed that
up, so I'll list it here at the end (I'm going to paste it right now, for
insurance's sake, but in the interest of brevity, I deleted out all the
lines that I'd just commented out, so as to save the mail KBs).
As far as the hints files go, I'm embarrassed to admit that I don't
understand the difference between the hints file that I name (APRIL.hints)
in my config file, and the device.hints in the man page of that name. I
have experimented with naming the file as device.hints, as APRIL.hints as I
named it in the kernel config file, and without one completely (rebooting
with each). I have also tried using kenv to automatically generate a
config file, and making one by starting with the GENERIC.hints, and
subtracting those device lines that I knew I wasn't using. I have to admit
I was somewhat nonplussed by the fact that the kenv command came out with a
binary format when I piped the output to a file. I rebooted with each, so
I could see if maybe one combination might be right. The device.hints man
page didn't explain for me (at least, I couldn't figure this out) what the
difference in naming was, between naming it device.hints or APRIL.hints.
If I use the name in the kernel config file, does it still reside in /boot,
or then maybe /boot/kernel? If I skip naming the hints file in the kernel
config file, that means only that it defaults the name? No other effects?
Anyhow, non of these combos got my boot messages back for me.
To both you and DES, I really apologize if I misunderstood your questions
about what failed. It really confused me, because I couldn't see in my
messages where I'd referred to anything extra that failed, besides the boot
messages. I might also forestall the question, why did I jump to current:
I'd run current for years, from 1.0 up to about 5.something, and Iliked
following current, and fixing the occaisonal breakages, I liked the
troubleshooting. Looks like I've been away too long.
====begin, my APRIL config file===================================
TCSH-april:root:/usr/src:#135-13:43>cat /sys/i386/conf/APRIL
#cpu I486_CPU
#cpu I586_CPU
cpu I686_CPU
ident APRIL
# To statically compile in device wiring instead of /boot/device.hints
hints "APRIL.hints" # Default places to look for devices.
makeoptions DEBUG=-g # Build kernel with gdb(1) debug
symbols
options SCHED_ULE # ULE scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission Protocol
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 UFS_GJOURNAL # Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires
PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
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.
options STOP_NMI # Stop CPUS using NMI instead of IPI
options AUDIT # Security event auditing
# Debugging for use in -current
options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.
options KSE
#options INVARIANTS # Enable calls of extra sanity checking
#options INVARIANT_SUPPORT # Extra sanity checks of internal
structures, required by INVARIANTS
#options WITNESS # Enable checks to detect deadlocks
and cycles
#options WITNESS_SKIPSPIN # Don't run witness on spinlocks
for speed
# To make an SMP kernel, the next two lines are needed
options SMP # Symmetric MultiProcessor Kernel
device apic # I/O APIC
# CPU frequency control
device cpufreq
# Bus support.
device eisa
device pci
# Floppy drives
device fdc
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
device atapist # ATAPI tape drives
options ATA_STATIC_ID # Static device numbering
# SCSI Controllers
# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device da # Direct Access (disks)
#device sa # Sequential Access (tape etc)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)
# RAID controllers interfaced to the SCSI subsystem
device twa # 3ware 9000 series PATA/SATA RAID
# RAID controllers
device twe # 3ware ATA RAID
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device psm # PS/2 mouse
device kbdmux # keyboard multiplexer
device vga # VGA video card driver
#device splash # Splash screen and screen saver support
# syscons is the default console driver, resembling an SCO console
device sc
options MAXCONS=8
options SC_HISTORY_SIZE=256
device agp # support several AGP chipsets
# Power management support (see NOTES for more options)
#device apm
# Add suspend/resume support for the i8254.
device pmtimer
# 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
device uart # Generic UART driver
# Parallel port
device ppc
device ppbus # Parallel port bus (required)
device lpt # Printer
device plip # TCP/IP over parallel
device ppi # Parallel port interface device
#device vpo # Requires scbus and da
# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device puc
# PCI Ethernet NICs.
device le # AMD Am7900 LANCE and Am79C9xx PCnet
# 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 dc # DEC/Intel 21143 and various workalikes
device nfe # nVidia nForce MCP on-board Ethernet
device nve # nVidia nForce MCP on-board Ethernet
Networking
device pcn # AMD Am79C97x PCI 10/100 (precedence over
'le')
device sis # Silicon Integrated Systems SiS 900/SiS 7016
# ISA Ethernet NICs. pccard NICs included.
device cs # Crystal Semiconductor CS89x0 NIC
# Wireless NIC cards
device wlan # 802.11 support
device wlan_wep # 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
device wlan_amrr # AMRR transmit rate control algorithm
device wlan_scan_ap # 802.11 AP mode scanning
device wlan_scan_sta # 802.11 STA mode scanning
# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
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)
device firmware # firmware assist module
# 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
device uhci # UHCI PCI->USB interface
device ohci # OHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
#device udbp # USB Double Bulk Pipe devices
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 ural # Ralink Technology RT2500USB wireless NICs
device rum # Ralink Technology RT2501USB wireless NICs
device uscanner # Scanners
# USB Ethernet, requires miibus
device aue # ADMtek USB Ethernet
device axe # ASIX Electronics USB Ethernet
device cdce # Generic USB over Ethernet
#device cue # CATC USB Ethernet
#device kue # Kawasaki LSI USB Ethernet
device rue # RealTek RTL8150 USB Ethernet
# FireWire support
device firewire # FireWire bus code
device sbp # SCSI over FireWire (Requires scbus and da)
device fwe # Ethernet over FireWire (non-standard!)
device fwip # IP over FireWire (RFC 2734,3146)
device dcons # Dumb console driver
device dcons_crom # Configuration ROM for dcons
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHcV4fz62J6PPcoOkRAjmfAJ40nMxZS7kyxok/Xhj0hlPVeppGogCfeK8p
0C93TDM8B+8HDUgJ1u3eO+k=
=Ji0n
-----END PGP SIGNATURE-----
More information about the freebsd-hackers
mailing list