[9fans] Installation CD Problems

[9fans] Installation CD Problems

[Akshat Kumar]

I've been trying to install Plan 9 on my most
used computer here, but the install CD I've
made has been giving me problems
(I've used Nero on Windows to create it):
when I try to boot into the Live CD, at
a very early stage (actually, just after asking
"root is from"), it reports "I/O read error"
messages, and continually does so, unable
to boot into the Live CD.
However, booting into just the Install goes OK
(other than that I cannot move my USB mouse...),
so I immediately go into rc with `!rc' at the install
rio window, and upon trying `mount /dev/sdC0/data',
I again get the same "I/O read error" message, so
it is unable to mount the data.

And yet, the CD data is readable from a mount
within Linux.

Any suggestions?
ak

Re: [9fans] Installation CD Problems

[erik quanstrom]

> I've been trying to install Plan 9 on my most
> used computer here, but the install CD I've
> made has been giving me problems
> (I've used Nero on Windows to create it):
> when I try to boot into the Live CD, at
> a very early stage (actually, just after asking
> "root is from"), it reports "I/O read error"
> messages, and continually does so, unable
> to boot into the Live CD.
[...]
> And yet, the CD data is readable from a mount
> within Linux.

assuming that your linux test was on the same
machine, that certianly sounds like a bug.  could
you send me pci or lspci -nvv output.  i'm
wondering if you have an ahci chipset.  older
versions of the ahci driver / 9load driver have
some trouble with some newer ahci wrinkles, like
staggered spinup and advanced power management.  i
believe that i've gotten to the bottom of anothy's
problems reported in
http://9fans.net/archive/2009/01/370  i can work
with you offline.  the code's not ready let loose.

- erik

Re: [9fans] Installation CD Problems

[blstuart]

> so I immediately go into rc with `!rc' at the install
> rio window, and upon trying `mount /dev/sdC0/data',
> I again get the same "I/O read error" message, so
> it is unable to mount the data.
>
> And yet, the CD data is readable from a mount
> within Linux.

How is the CD drive installed?  /dev/sdC0 seems
definitely wrong for the CD.  If it's the master on
a second IDE controller (the most common case),
you want /dev/sdD0.  If it's the slave on the first
controller, you want /dev/sdC1.

BLS

Re: [9fans] Installation CD Problems

[Akshat Kumar]

> How is the CD drive installed?  /dev/sdC0 seems

I might have forgotten what it was. I'll check soon
and get back to you on that.

> BLS

Thanks,
ak

Re: [9fans] Installation CD Problems

[Akshat Kumar]

[-- Attachment #1: Type: text/plain, Size: 49 bytes --]

lspci -nvv > lspci.out
attached

Thanks,
ak

[-- Attachment #2: lspci.out --]
[-- Type: application/octet-stream, Size: 8603 bytes --]

00:00.0 0600: 8086:2570 (rev 02)
	Subsystem: 103c:12bc
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Capabilities: [e4] Vendor Specific Information <?>
	Capabilities: [a0] AGP version 3.0
		Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP+ GART64- 64bit- FW- Rate=x8

00:01.0 0604: 8086:2571 (rev 02) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	Memory behind bridge: f1000000-f21fffff
	Prefetchable memory behind bridge: e0000000-f01fffff
	Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:1d.0 0c03: 8086:24d2 (rev 02) (prog-if 00 [UHCI])
	Subsystem: 103c:12bc
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 10
	Region 4: I/O ports at 1440 [size=32]
	Kernel driver in use: uhci_hcd

00:1d.1 0c03: 8086:24d4 (rev 02) (prog-if 00 [UHCI])
	Subsystem: 103c:12bc
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 5
	Region 4: I/O ports at 1460 [size=32]
	Kernel driver in use: uhci_hcd

00:1d.2 0c03: 8086:24d7 (rev 02) (prog-if 00 [UHCI])
	Subsystem: 103c:12bc
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 10
	Region 4: I/O ports at 1480 [size=32]
	Kernel driver in use: uhci_hcd

00:1d.7 0c03: 8086:24dd (rev 02) (prog-if 20 [EHCI])
	Subsystem: 103c:12bc
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin D routed to IRQ 10
	Region 0: Memory at f0500000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Kernel driver in use: ehci_hcd

00:1e.0 0604: 8086:244e (rev c2) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=64
	Memory behind bridge: f0200000-f04fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:1f.0 0601: 8086:24d0 (rev 02)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.1 0101: 8086:24db (rev 02) (prog-if 8a [Master SecP PriP])
	Subsystem: 103c:12bc
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at 01f0 [size=8]
	Region 1: I/O ports at 03f4 [size=1]
	Region 2: I/O ports at 0170 [size=8]
	Region 3: I/O ports at 0374 [size=1]
	Region 4: I/O ports at 14c0 [size=16]
	Region 5: Memory at 30000000 (32-bit, non-prefetchable) [size=1K]
	Kernel driver in use: PIIX_IDE

00:1f.2 0101: 8086:24d1 (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: 103c:12bc
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at 14f0 [size=8]
	Region 1: I/O ports at 1808 [size=4]
	Region 2: I/O ports at 14f8 [size=8]
	Region 3: I/O ports at 180c [size=4]
	Region 4: I/O ports at 14d0 [size=16]

00:1f.3 0c05: 8086:24d3 (rev 02)
	Subsystem: 103c:12bc
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin B routed to IRQ 11
	Region 4: I/O ports at fc00 [size=32]

00:1f.5 0401: 8086:24d5 (rev 02)
	Subsystem: 103c:12bc
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 5
	Region 0: I/O ports at 1000 [size=256]
	Region 1: I/O ports at 1400 [size=64]
	Region 2: Memory at f0500400 (32-bit, non-prefetchable) [size=512]
	Region 3: Memory at f0500600 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: Intel ICH

01:00.0 0300: 10de:0326 (rev a1) (prog-if 00 [VGA controller])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 248 (1250ns min, 250ns max)
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at f1000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e0000000 (32-bit, prefetchable) [size=256M]
	[virtual] Expansion ROM at f0000000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [44] AGP version 3.0
		Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
	Kernel driver in use: nvidia
	Kernel modules: nvidia

05:02.0 0200: 14e4:1696 (rev 03)
	Subsystem: 103c:12bc
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (16000ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at f0400000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data <?>
	Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
		Address: f7ffdfff7fff9efc  Data: bfbf
	Kernel driver in use: tg3
	Kernel modules: tg3

05:0a.0 0200: 168c:0013 (rev 01)
	Subsystem: 1948:3ab9
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at f0410000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-
	Kernel driver in use: ath_pci
	Kernel modules: ath_pci

Re: [9fans] Installation CD Problems

[erik quanstrom]

> How is the CD drive installed?  /dev/sdC0 seems
> definitely wrong for the CD.  If it's the master on
> a second IDE controller (the most common case),
> you want /dev/sdD0.  If it's the slave on the first
> controller, you want /dev/sdC1.

great point.

i don't think there's any problem with running a cdrom
as ide0 device 0.  but iirc, the plan 9 installer is particular
about where the cdrom is installed.  the last time i tried
sdE0 (ide interface) was not an acceptable location.

if someone's itching for a project, the installer could use
a little touch up.

- erik

Re: [9fans] Installation CD Problems

[Pietro Gagliardi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jan 31, 2009, at 5:33 PM, erik quanstrom wrote:

> if someone's itching for a project, the installer could use
> a little touch up.

The program to detect where to install from, /sys/lib/dist/pc/inst/
mountdist, is good. The only problem seems to be with the plan9.ini
file, /sys/lib/dist/pc/plan9.ini.cd, which specifically asks to boot
from /dev/sdD0. Unless there is a better way to specify "the device
where plan9.ini was found," say $inidev? That would require some
modifications to the plan9.ini parser, am I right?

However, Akshat also said

On Jan 31, 2009, at 1:52 PM, Akshat Kumar wrote:

> However, booting into just the Install goes OK

but the plan9.ini.cd behaves the same way in Install as in Boot Live.
Unless there's something I'm missing...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkmE1bAACgkQuv7AVNQDs+wS5gCfXAiX0cvYh66avVFuCQ1kwdhx
BTEAnA7acRmK+X/F5kw435BQVUeSbC/f
=zOym
-----END PGP SIGNATURE-----

Re: [9fans] Installation CD Problems

[erik quanstrom]

> > if someone's itching for a project, the installer could use
> > a little touch up.
>
> The program to detect where to install from, /sys/lib/dist/pc/inst/
> mountdist, is good. The only problem seems to be with the plan9.ini
> file, /sys/lib/dist/pc/plan9.ini.cd, which specifically asks to boot
> from /dev/sdD0. Unless there is a better way to specify "the device
> where plan9.ini was found," say $inidev? That would require some
> modifications to the plan9.ini parser, am I right?

i have made this modification.  /n/sources/contrib/quanstro/src/9loadaoe.
look for "bootdev" in load.c

unfortunately, this technique will not work when booting from a cd
because an el torito cd uses a fakey-fakey floppy image to boot from.
as far as the installer is concerned, it's booting from a floppy disk.

i also think there's a few other places where assumptions are made.
maybe i'm wrong.  it's been a long time since i fought with the installer.

and that time i lost. :-)

- erik

Re: [9fans] Installation CD Problems

[Akshat Kumar]

OK, so I'm just getting caught up on the
replies here so far.

As far as /dev/sdC0 goes -- BLS is right,
it was really /dev/sdD0, and I remembered
incorrectly. That is, the CD ROM Drive is,
indeed, second IDE master.

Re: [9fans] Installation CD Problems

[erik quanstrom]

> OK, so I'm just getting caught up on the
> replies here so far.
>
> As far as /dev/sdC0 goes -- BLS is right,
> it was really /dev/sdD0, and I remembered
> incorrectly. That is, the CD ROM Drive is,
> indeed, second IDE master.

i think it's really likely that this change needs
to be move from the kernel into 9load's sdata.c.
but it's pretty hard for me to test.  regardless,
if this change is good enough for the kernel,
it should be good enough for 9load:

diff -c /sys/src/boot/pc-e820/sdata.c /n/sources/plan9/sys/src/boot/pc/
(other stuff)
/sys/src/boot/pc-e820/sdata.c:875,882 - /n/sources/plan9/sys/src/boot/pc//sdata.c:875,881
  	qlock(ctlr);

  	as = ataready(cmdport, ctlport, drive->dev, Bsy|Drq, Drdy, 107*1000);
- 	/* used to test as&Chk as failure too, but some CD readers use that for media change */
- 	if(as < 0){
+ 	if(as < 0 || (as&Chk)){
  		qunlock(ctlr);
  		return -1;
  	}

- erik

Re: [9fans] Installation CD Problems

[lucio]

> The only problem seems to be with the plan9.ini
> file, /sys/lib/dist/pc/plan9.ini.cd, which specifically asks to boot
> from /dev/sdD0

If I understand the handling of the bootfile and bootargs, multiple
entries for most variables cause a menu prompt.  But that does not
apply here, you're referring to the second option, the first,
[install], boots off the floppy.  Where is the plan9.ini that the
floppy consults?

++L