Tracker bug for the things that need: A) Fixing B) Improving C) Ideas D) Feedback E) Any and/or all of the above F) Anything else I missed
Is it possible to add some suggested command options for the cdrecord command to the README? I tend to use graphical frontends, and haven't been very successful with the cdrecord command to burn the install CD. I'm attempting a clean install onto an Indy r5000(IP22) with no Irix partition. Thanks for your time
cdrecord -vv -pad speed=24 dev=ATAPI:0,0,0 -tao <ISO/IMG File> Is the command I use. -vv gives additional, verbose output -pad pads the end of the disc speed= speed of the drive (24x is reasonable, no point to burn this with the fastest drive on the block) dev= points to the device. ATAPI:x,y,z tells cdrecord to use IDE-based drives at the specified target. Run cdrecord -scanbus dev=ATAPI to see a list of available/detected ATAPI devices. This is also dependent on the 2.6 kernel. -tao sets track-at-once; pretty much the default on all new versions of cdrecord whether you include it or not. I'll include similar info like this in whatever becomes the next release, as it's difficult to edit the README file once it's out on the mirrors.
I tried booting the live CD on my Indy IP22 R5000 box. I get this resonse: ARCLoader version 0.43(c)2004-5 Stanislaw Skowronek Loading configuration for '/unix'... Detecting system parameters... Loading scsi(0)cdrom(7)partition(8)/ip22r5k... Reading 5304390 bytes...OK. Entering kernel. then the box hangs and the power light flashes red and green. Any thoughts?
(In reply to comment #3) > I tried booting the live CD on my Indy IP22 R5000 box. I get this resonse: > ARCLoader version 0.43(c)2004-5 Stanislaw Skowronek > Loading configuration for '/unix'... > Detecting system parameters... > Loading scsi(0)cdrom(7)partition(8)/ip22r5k... > Reading 5304390 bytes...OK. > Entering kernel. > > then the box hangs and the power light flashes red and green. Any thoughts? Did you check the hardware compatibility list before trying to install linux? It sounds like you are trying to use the graphical console on an indy with GR3-XZ graphics. This board is not supported (yet) by linux, and therefore you would need to use serial console to boot the machine. What does typing "hinv" from the prom prompt say about the graphics?
Oh, yes it is the GR3-XZ which I see is unsupported, as you say. I will put together a cable to hook up my intel laptop to the indy (DB9 to MINI-DIN-8) and give it a try. Thanks for pointing out my problem so quickly!
(In reply to comment #5) > Oh, yes it is the GR3-XZ which I see is unsupported, as you say. I will put > together a cable to hook up my intel laptop to the indy (DB9 to MINI-DIN-8) and > give it a try. Thanks for pointing out my problem so quickly! > Just make sure you use a null modem adapter with that cable. -Steve
I created a liveCD based on the cdrecord line in this bug, but it's not recognized and won't boot. The issue may be that the volume header is not 512 bytes. It is instead 0. The output IRIX FX reading the CD - conejo 101# fx -x fx version 6.5, Dec 8, 2005 fx: "device-name" = (dksc) fx: ctlr# = (0) fx: drive# = (1) 4 fx: lun# = (0) ...opening dksc(0,4,0) ...drive selftest...OK Can't get drive geometry, assuming 64 sectors/track Can't get drive geometry, assuming 8 heads Unable to get device geometry Scsi drive type == TOSHIBA CD-ROM XM-6401TA1003 warning: disagrees with existing volume header parameters show differences? (yes) bytes/sec = volume header 0 ; should be 512 to match drive use existing volume header? (yes) ----- please choose one (? for help, .. to quit this menu)----- [exi]t [d]ebug/ [l]abel/ [a]uto [b]adblock/ [exe]rcise/ [r]epartition/ fx> l ----- please choose one (? for help, .. to quit this menu)----- [sh]ow/ [sy]nc [se]t/ [c]reate/ fx/label> sh ----- please choose one (? for help, .. to quit this menu)----- [para]meters [part]itions [b]ootinfo [a]ll [g]eometry [s]giinfo [d]irectory fx/label/show> a ----- current drive parameters----- Error correction enabled Enable data transfer on error Don't report recovered errors Do delay for error recovery Don't transfer bad blocks Error retry attempts 10 No auto bad block reallocation (read) No auto bad block reallocation (write) Read buffer ratio 201/256 Write buffer ratio 0/256 Command Tag Queueing disabled Can't get drive geometry, assuming 64 sectors/track Can't get drive geometry, assuming 8 heads ----- current drive geometry----- Tracks/zone = 1 Sect/track = 64 Alt sect/zone = 0 Interleave = 1 Cylinders = 577 Alt track/volume = 0 Cylinder skew = 0 Heads = 8 Alt track/zone = 0 Track skew = 0 Data bytes/sec = 512 ----- partitions----- part type blocks Megabytes (base+size) 0: raw 80520 + 215000 39 + 105 8: volhdr 0 + 80520 0 + 39 10: volume 0 + 295520 0 + 144 ----- bootinfo----- root partition = 0 swap partition = 0 bootfile = unix ----- directory entries----- 0: ip22r4k block 4 size 5774926 5: ip32r5k block 66213 size 7229054 1: ip22r5k block 11284 size 5758526 6: sash64 block 80333 size 66122 2: ip27r10k block 22532 size 7484055 7: sashARCS block 80463 size 25388 3: ip28r10k block 37150 size 6775205 8: arc.cf block 80513 size 3259 4: ip30r10k block 50383 size 8104467 ----- sgi-info----- serial = name = TOSHIBA CD-ROM XM-6401TA1003 conejo 103# mediad -f mediad: log level is LOG_DEBUG mediad: monitoring device at SCSI ctlr 0, id 4 mediad: Device "CDROM" medium is present. mediad: Checking: /usr/lib/devicelib/fmt_udf.so mediad: Checking: /usr/lib/devicelib/fmt_efs.so mediad: EFS inspect: rawfsname = "/dev/rdsk/dks0d4vh" mediad: Checking: /usr/lib/devicelib/fmt_hfs.so mediad: Checking: /usr/lib/devicelib/fmt_dos.so mediad: Checking: /usr/lib/devicelib/fmt_xfs.so mediad: XFS inspect: rawfsname = "/dev/rdsk/dks0d4vh" mediad: Checking: /usr/lib/devicelib/fmt_iso.so mediad: Checking: /usr/lib/devicelib/fmt_cdda.so mediad: listening for monitor clients on descriptor 5 mediad: listening for compat clients on descriptor 6 As can be seen, the CD can't be identified on IRIX. A normal IRIX install CD would be identified. I also tried installing this CD on my O2 and it stated that it couldn't find sashARCS. Bob
(In reply to comment #7) > I created a liveCD based on the cdrecord line in this bug, but it's not > recognized and won't boot. The issue may be that the volume header is not > 512 bytes. It is instead 0. The output IRIX FX reading the CD - > [snip] > > As can be seen, the CD can't be identified on IRIX. A normal IRIX > install CD would be identified. > > I also tried installing this CD on my O2 and it stated that it > couldn't find sashARCS. What system is this on for the IRIX output above, and for your O2, are you able to run the command "ls dks(x,y,x)" where x/y/z are the numbers pointing to your CD-ROM? I've tested the RC5 CD on my O2, and it's worked fine, same goes for other users. I would also double check the md5/sha1 sums of the CD against the ones posted on the mirror site to make sure a corrupted image wasn't downloaded.
I just tried gentoo-mips-sgi-livecd-rc5 with an O2 that I just brought home from work. I am a total SGI newbie so forgive me if I'm doing something wrong. The O2 has a 180mhz R5000 CPU and 192 megs of RAM. I burned the CD with this command line: cdrecord speed=24 dev=/dev/hdh driveropts=burnfree -pad -verbose gentoo-mips-sgi-livecd-rc5.img I do the usual "click here for system maintenance" and "install system software" stuff (that, by the way, works with the "Irix 6.5.12 Installation Tools" CD), but unfortunately it crashes right after saying "Entering kernel." Here's the output (which I am typing in, so may contain a typo or 2): Exception: <vector=Normal> Status register: 0x34010082<CU1,CU0,FR,DE,IPL=8,KX,MODE=KERNEL> Cause reguster: 0x8024<CE=0,IP8,EXC=BREAK> Exception PC: 0x8052b5a8, Exception RA: 0x80521004 Breakpoint exception at address 0xffffffef Saved user regs in hex (&gpda 0x810617b8, &_regs 0x810619b8): arg: 81070000 8000 8064eff8 a000 tmp: 81070000 2 30 80626d68 c000 670 1 0 sve: 81070000 bfa2a776 0 4605f632 0 c02f731d 0 bec9fbc1 t8 81070000 t9 0 at 0 v0 bfd7d115 v1 0 k1 0 gp 81070000 fp 0 sp 0 ra 0 PANIC: Unexpected exception {Press reset or ENTER to restart.] The only non-standard hardware that I have plugged in is a cheap PC keyboard, a Microsoft Wheelmouse using a USB to PS/2 adapter, and a Toshiba XM-3801b SCSI CD-ROM drive (not the drive the O2 came with, but it does boot Irix just fine).
RC6 will be available shortly. The new Tracker Bug is Bug #150402.
