Re: New thread -> X1 fun stuff
On Thu, Aug 30, 2001 at 12:30:03AM +0100, Richard Mortimer wrote: > That looks similar to the errors that I first got when the csr0 values > were set wrongly. I wonder if a chip register is not getting setup > correctly in certain circumstances. The main thing that I did with > this was to have a look at the chip registers and looked at what was > different between working and non-working versions. > > Can you get the following information from situations where the system > is working and not-working. You need to drop into OBP and then use > these commands to dump the hardware registers for the device that is > not working (I think that it was eth1 in your case). > > eth1 > > 1fe.0201 100 piodump > 1fe.01006000 100 piodump > > eth0 > > 1fe.02010100 100 piodump > 1fe.01002800 100 piodump Not working: ok 1fe.0201 100 piodump 1fe \/ 1 2 3 4 5 6 7 8 9 a b c d e f v123456789abcdef 201 00 50 00 fe ff ff ff ff ff ff ff ff ff ff ff ff .P.~ 2010010 ff ff ff ff ff ff ff ff 70 00 00 7f ff ff ff ff p... 2010020 a0 80 00 7f ff ff ff ff 00 a8 12 fd ff ff ff ff (.} 2010030 07 20 00 00 ff ff ff ff ef eb ff ff ff ff ff ff . ..ok.. 2010040 00 00 00 00 ff ff ff ff f0 83 05 01 ff ff ff ff p... 2010050 00 00 fc ff ff ff ff ff 00 00 fe ff ff ff ff ff ..|...~. 2010060 49 ff ff ff ff ff ff ff 00 00 00 00 ff ff ff ff I... 2010070 00 00 00 00 ff ff ff ff 00 00 00 00 ff ff ff ff 2010080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2010090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20100f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ok 1fe.01006000 100 piodump 1fe \/ 1 2 3 4 5 6 7 8 9 a b c d e f v123456789abcdef 1006000 82 12 02 91 47 01 10 12 31 00 00 02 00 a0 00 00 G...1 .. 1006010 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 1006020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1006030 00 00 04 00 50 00 00 00 00 00 00 00 00 01 14 28 P..( 1006040 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 [EMAIL PROTECTED] 1006050 01 00 32 c1 00 00 00 00 00 00 00 00 00 00 00 00 ..2A 1006060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1006070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1006080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1006090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10060f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ok 1fe.02010100 100 piodump 1fe \/ 1 2 3 4 5 6 7 8 9 a b c d e f v123456789abcdef 2010100 00 00 00 fe ff ff ff ff ff ff ff ff ff ff ff ff ...~ 2010110 ff ff ff ff ff ff ff ff 00 00 00 00 ff ff ff ff 2010120 00 00 00 00 ff ff ff ff 00 00 00 fc ff ff ff ff ...| 2010130 00 00 04 02 ff ff ff ff 00 00 fe ff ff ff ff ff ..~. 2010140 00 00 00 00 ff ff ff ff f0 83 05 00 ff ff ff ff p... 2010150 00 00 fc ff ff ff ff ff 00 00 fe ff ff ff ff ff ..|...~. 2010160 00 ff ff ff ff ff ff ff 00 00 00 00 ff ff ff ff 2010170 00 00 00 00 ff ff ff ff 00 00 00 00 ff ff ff ff 2010180 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 2010190 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20101f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ok 1fe.01002800 100 piodump 1fe \/ 1 2 3 4 5 6
New thread -> X1 fun stuff
That looks similar to the errors that I first got when the csr0 values were set wrongly. I wonder if a chip register is not getting setup correctly in certain circumstances. The main thing that I did with this was to have a look at the chip registers and looked at what was different between working and non-working versions. Can you get the following information from situations where the system is working and not-working. You need to drop into OBP and then use these commands to dump the hardware registers for the device that is not working (I think that it was eth1 in your case). eth1 1fe.0201 100 piodump 1fe.01006000 100 piodump eth0 1fe.02010100 100 piodump 1fe.01002800 100 piodump The first command dumps the chip registers and the second command dumps the devices pci configuration space. I'm not convinced that this is exactly what I saw because I didn't get the SABRE0: messages I just got the "System Error occured (2)" message but it might give a clue to what is wrong. Richard Adam McKenna writes: > So, I finally managed to get Debian installed on my Netra X1, I now have a > repeatable problem (well, repeatable in the sense that it happens every other > boot.) I figured I'd start a new thread, and trim the headers, since I > figure most of the people who were included in the last thread are on one of > these two lists. > > For the boot log, please see http://spotted.flounder.net/~adam/boot-log.txt > > It seems to happen exactly every other boot. I've rebooted about 8 times now > and it always boots fine the second time (after crashing.) > > --Adam > > -- > Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > - > To unsubscribe from this list: send the line "unsubscribe sparclinux" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html >
errror in gcc-3.0-sparc64_1%3a3.0.2-0pre010826_sparc.deb
Hello, today I'm trying to update an ultra10 (last update was performed on June 19) and I get an error when it comes the turn of gcc-3.0 I've tried with --force-overwrite but it gives the same error, that is shown here: [EMAIL PROTECTED]:~ # dpkg -i --force-overwrite /var/cache/apt/archives/gcc-3.0-sparc64_1%3a3.0.2-0pre010826_sparc.deb (Reading database ... 54785 files and directories currently installed.) Preparing to replace gcc-3.0-sparc64 1:3.0-0pre010427 (using .../gcc-3.0-sparc64_1%3a3.0.2-0pre010826_sparc.deb) ... dpkg-divert: rename involves overwriting `/usr/lib/gcc-lib/sparc-linux/3.0/cc1' with different file `/usr/lib/gcc-lib/sparc-linux/3.0/cc1.32', not allowed dpkg: error processing /var/cache/apt/archives/gcc-3.0-sparc64_1%3a3.0.2-0pre010826_sparc.deb (--install): subprocess pre-installation script returned error exit status 2 dpkg-divert: rename involves overwriting `/usr/bin/gcc-3.0' with different file `/usr/bin/gcc-3.0-32', not allowed dpkg: error while cleaning up: subprocess post-removal script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/gcc-3.0-sparc64_1%3a3.0.2-0pre010826_sparc.deb [EMAIL PROTECTED]:~ # any idea? is this a known bug or should I file one? Pf -- --- Pierfrancesco Caci |System Administrator @ seabone.net [EMAIL PROTECTED] | Telecom Italia S.p.A. - International Operations Linux paperino 2.4.9 #1 Wed Aug 29 15:09:31 CEST 2001 i686 unknown
Re: SPARC5 boot problems
Mandi! Wes Byne In chel di` si favelave... > I've got a sparc5 with potato installed. I managed to mess up the boot > process so that I can't get it to boot from the hard disk. I tried to get > the OBP to boot the kernel image directly instead of silo, and then I read > the docs. My root disk is /dev/sda2, or /iommu/sbus/espdma/esp/[EMAIL > PROTECTED],0 but when I try to boot [EMAIL PROTECTED],0:2/sbin/silo from the > OK prompt it complains that it can't find the image. The disk doesn't have a > sun disklabel (does it require one?). Can someone tell me what I need to try? SUN Disklabels are required (you can read the debian sparc install manual...), but also i (with a ss10, sun disklables both of the two disks) i've had to mess up with prom to make boot. I've to do: boot disk1 instead of the default ``boot disk'' (or boot). -- dott. ing. Marco Gaiarin Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/ Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN) gaio(at)sv.lnf.it tel +39-0434-842711fax +39-0434-842797 (Altra)informazione sul G8!!! http://www.peacelink.it/altrinformazione/
Re: Sun Hardware Replacement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Do a network install, all you'll need is rarp, tftp and ftp/http on another boxen, you can then suck the files from that. Cheers, Si snip >>>Hi, >>>I was given a Sun Sparc 2 that our office had lying around. >>>I got all prepared to install Debian Linux and have found that the CDRom is >>>missing the drive caddy, hence I can't use it. snip - -- Todays letter from the sysadmin alphabet is ... "B" is for Bastard, the New Zealand one. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7jL3XmbZ7rwJkPkARAiKIAKCE56H05JwVWEdI167vI39zMRHKeACfdPOu kr+XoXhpTM+KiX7Dho9Wpzw= =9ODb -END PGP SIGNATURE-
New thread -> X1 fun stuff
So, I finally managed to get Debian installed on my Netra X1, I now have a repeatable problem (well, repeatable in the sense that it happens every other boot.) I figured I'd start a new thread, and trim the headers, since I figure most of the people who were included in the last thread are on one of these two lists. For the boot log, please see http://spotted.flounder.net/~adam/boot-log.txt It seems to happen exactly every other boot. I've rebooted about 8 times now and it always boots fine the second time (after crashing.) --Adam -- Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
