Re: Unable to mount root on 1.2.0 CD

[Patrick McNamee <patm@xxxxxxxx>]

On Mon, Apr 11, 2005 at 10:53:13PM -0700, Matthew Dillon wrote:
> 
>     Try doing a boot -v (drop into the boot prompt using menu option 6 and
>     type 'boot -v'), and see if you can pick the ATA device lines.  See
>     what it identifies the ATA device as and try to find a PCI ID in the
>     identification line or earlier on that has the same PCI bus identifier.

Here are the ata-related lines I was able to glean:

ad0: <WDC AC26400R/15.01J55> ATA-4 disk at ata0-master
ata1-slave: piomode=4 dmamode=2 udmamode=2 dmaflag=1
ata1-slave: sucess setting PIO4 on generic chip
acd0: <LITE-ON LTR-24102B/5S0F> CD-RW drive at ata1 as slave
(probe3:ata1:0:1:0): INQUIRY. CDB: 12 1 80 0 FF 0
(probe3:ata1:0:1:0): ILLEGAL REQUEST ASC:24,0
(probe3:ata1:0:1:0): Invalid field in CDB
(probe3:ata1:0:1:0): INQUIRY. CDB: 12 1 80 0 FF 0
(probe3:ata1:0:1:0): ILLEGAL REQUEST ASC:24,0
(probe3:ata1:0:1:0): Invalid field in CDB
pass0 at ata1 bus 0 target 1 lun 0
cd0 at ata1 bus 0 target 1 lun 0

There were also a couple of root mount attempts:
Mounting root from cd9660:/dev/acd0a

That didn't explicitly fail (at least there was not message
saying it failed). Then, a few lines later we have:

iso_mountroot(): using sessions at block 119548
Root mount failed: 22


>     If you have a second computer and can attach a serial port to the
>     one that isn't booting right, you can boot it over the serial port and
>     record the sequence on the second computer.  It's a 9600 8N1 connection.
>     The boot loader will output to both the console and the serial port but
>     to make the kernel output to the serial port you have to give it the -h
>     option, e.g. drop into the boot prompt via the serial link and type
>     'boot -h -v'.

Haven't figured out how to do this yet. Are you referring to
connecting the two machines using a null modem cable? If so,
I tried that but couldn't establish a tip connection. I
assume the command would be something like 'tip -9600/8N1 foo',
but I don't know what host name to use for foo. But maybe
you're referring to something else entirely and I don't get
it yet. (I've been watching DragonFly's progress since you
got started, but this is the first time I've tried to do
anything with it.)


>     There may not be anything we can do.  If the machine has a USB port
>     it might be capable of booting from a USB disk key, but without a
>     working ATA device there isn't much you could do with it beyond that.

It's an older machine and doesn't have a USB port.

For what it's worth, here's the dmesg from a normal boot of
the machine:

Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD 4.10-RELEASE #4: Fri Jun 25 14:50:58 CDT 2004
    xxxxxxx@xxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (233.86-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x634  Stepping = 4
  Features=0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX>
real memory  = 167772160 (163840K bytes)
avail memory = 157634560 (153940K bytes)
Preloaded elf kernel "kernel" at 0xc0551000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 5 entries at 0xc00fde60
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
agp0: <Intel 82443LX (440 LX) host to PCI bridge> mem 0xe0000000-0xe7ffffff at device 0.0 on pci0
pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f
at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port
0x6400-0x641f irq 11 at device 7.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
chip0: <Intel 82371AB Power management controller> port
0x5000-0x500f at device 7.3 on pci0
fxp0: <Intel 82557 Pro/100 Ethernet> port 0x6800-0x681f mem
0xec000000-0xec0fffff,0xec100000-0xec100fff irq 10 
at device 16.0 on pci0
fxp0: Ethernet address 00:20:35:22:ac:a0
nsphy0: <DP83840 10/100 media interface> on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: <S3 ViRGE DX/GX graphics accelerator> at 18.0 irq 12
orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
pmtimer0 on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6
drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 6149MB <WDC AC26400R> [13328/15/63] at ata0-master UDMA33
acd0: CD-RW <LITE-ON LTR-24102B> at ata1-slave PIO4
Mounting root from ufs:/dev/ad0s1a