#define INV_ODSY_MEMCFG_512

SGI hardware problems, solutions, tips, hacks, etc.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
iKitsune
Posts: 504
Joined: Thu May 14, 2009 10:31 am
Location: Huntsville, Alabama, USA

Re: #define INV_ODSY_MEMCFG_512

Unread postby iKitsune » Fri May 29, 2009 7:09 am

recondas wrote:The other <unanswered> question is; if the V10 iss an identical to the V12 fab to save making two different PCBs - why did they switch an to the Samsung chips?

Probably got a better deal on the RAM from Samsung? NEC couldn't meet their volume needs? Who knows? It wouldn't be a major change to change RAM brands, as long as they were the same configuration.
:O3000: :1600SW: :Indigo2IMP: :0300:

"Remember, if they can't find you handsome, they should at least find you handy."

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 7:10 am

The way I figure it, when the original V10/V12 for Fuel was made, the price of RAM was such that there was an advantage to going with two types of RAM as they had done with the Octane V12's. As production continued, RAM prices fell, and it was cost effective to just go with the higher-density stuff, and build out to either a V10 or a V12 - this also meant that in production they only had to stock one set of parts and could build either way depending on demand much later in the manufacturing cycle. The resistor could be added or removed from the BOM at the time the production order went in, and the ID strings were programmable.

As a note, I too was poking around in the kernel files, and note that there is only one set of BUZZ microcode that get's uploaded. With all of the 'types' of V10/V12 part numbers out there, I can't actually imagine that they can actually check by part number, as a V12 is a V12, early or late vintage, and indeed poking through the Odyssey driver binary I didn't see anything obvious. If past history is any indication, I wouldn't be suprised if it was just the 'amount of reported memory' that determines to the system whether it's a V10 or a V12.

I have 2 V10's here, one with the old-style 32MB SGRAM, and one with the Samsungs. Guess I'll have to warm up the soldering iron tonight...

Addendum: Looks like in Hamei's photo's, the PCB part number is the same between both boards. I know the 'old-style' 32MB boards are different (they also have a 'Made in Canada' under the part number) but since the newer boards use the same PCB, it looks really promising...
Last edited by Dr. Dave on Fri May 29, 2009 7:15 am, edited 1 time in total.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day

User avatar
recondas
Moderator
Moderator
Posts: 5442
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: #define INV_ODSY_MEMCFG_512

Unread postby recondas » Fri May 29, 2009 7:14 am

Dr. Dave wrote:Guess I'll have to warm up the soldering iron tonight...
Yer my hero..... :D
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 7:24 am

Probably a good time to build up the FrankenFuel from parts tonight too, for testing.

Addendum: Just had a quick glance at my 'old-style' V10 (XIO edge connector up), resistors are quite different, basically being:

Code: Select all

   top set: x o o o
bottom set: o o o o

where x = resistor, o = open

This may however not mean much. If anyone has a loose Fuel V10/V12 with the larger chips, it would be worth seeing what they are set to and report back here, possibly with ID strings.
Last edited by Dr. Dave on Sat May 30, 2009 7:06 pm, edited 1 time in total.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day

User avatar
recondas
Moderator
Moderator
Posts: 5442
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: #define INV_ODSY_MEMCFG_512

Unread postby recondas » Fri May 29, 2009 7:52 am

V10 030-1826-002 REV A:

R561B = OFF
R563B = OFF
R565B = ON
R567B = ON <guessing at the full "R" number - it's partially obscured by the heatsink>

R562B = OFF
R564B = ON
R566B = ON
R568B = OFF <guessing at the full "R" number - it's partially obscured by the heatsink>

I can't provide the ID string for the board - nothing to put it in <yet - bought it for reference while researching this thread>
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

User avatar
nekonoko
Site Admin
Site Admin
Posts: 8145
Joined: Thu Jan 23, 2003 1:31 am
Location: Pleasanton, California
Contact:

Re: #define INV_ODSY_MEMCFG_512

Unread postby nekonoko » Fri May 29, 2009 8:15 am

Will be interesting to see what happens with this; I have a late B2 rev V10 in my Octane2 that would be fun to convert to V12 ;)
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

User avatar
hamei
Posts: 10437
Joined: Tue Feb 24, 2004 4:10 pm
Location: over the rainbow

Re: #define INV_ODSY_MEMCFG_512

Unread postby hamei » Fri May 29, 2009 8:22 am

iKitsune wrote: I'm just pissing into the dark.

I often do that. Kinda messy but you can sort of tell by the sound when you're hitting the sweet spot :)

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 8:32 am

Don't piss on the electric fence, though.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day

sgtprobe
Posts: 333
Joined: Thu Nov 20, 2008 11:18 pm
Location: Sweden
Contact:

Re: #define INV_ODSY_MEMCFG_512

Unread postby sgtprobe » Fri May 29, 2009 8:38 am

Really interesting thread guy's.


But this made my day, still laughing. :lol:

hamei wrote:
iKitsune wrote: I'm just pissing into the dark.

I often do that. Kinda messy but you can sort of tell by the sound when you're hitting the sweet spot :)


/Jonas
Image Image Image Image Image Image

-----------------
Old polygon wrangler
___________________
http://www.edgeloop.se

User avatar
recondas
Moderator
Moderator
Posts: 5442
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: #define INV_ODSY_MEMCFG_512

Unread postby recondas » Fri May 29, 2009 8:43 am

hamei wrote:I often do that. Kinda messy but you can sort of tell by the sound when you're hitting the sweet spot :)
...or your shoes.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

User avatar
iKitsune
Posts: 504
Joined: Thu May 14, 2009 10:31 am
Location: Huntsville, Alabama, USA

Re: #define INV_ODSY_MEMCFG_512

Unread postby iKitsune » Fri May 29, 2009 3:09 pm

recondas wrote:
hamei wrote:I often do that. Kinda messy but you can sort of tell by the sound when you're hitting the sweet spot :)
...or your shoes.

Usually my cat does that for me.
:O3000: :1600SW: :Indigo2IMP: :0300:

"Remember, if they can't find you handsome, they should at least find you handy."

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 6:51 pm

Power screwdriver is charged, and got a dozen Timmies donuts... here's the starting point with the 'new-style' V10:

Code: Select all

Dudley 1% hinv
1 600 MHZ IP35 Processor
CPU: MIPS R14000 Processor Chip Revision: 2.4
FPU: MIPS R14010 Floating Point Chip Revision: 2.4
Main memory size: 2048 Mbytes
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 4 Mbytes
Integral SCSI controller 3: Version SAS/SATA LS1064
  Disk drive: unit 0 on SCSI controller 3
Integral SCSI controller 0: Version QL12160, low voltage differential
  Disk drive: unit 1 on SCSI controller 0
Integral SCSI controller 1: Version QL12160, single ended
  CDROM: unit 6 on SCSI controller 1
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: V10
Gigabit Ethernet: tg2, module 001c01, PCI bus 2 slot 1
Integral Fast Ethernet: ef0, version 1, module 001c01, pci 4
Iris Audio Processor: version MAD revision 1, number 1
USB controller: type OHCI

Note I'm using an X-session off my laptop to grab this, thus the 'unmanaged' board.

Code: Select all

Dudley 2% /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
        Unmanaged 1280x1024
        BUZZ version B.1
        PB&J version 1
        32MB memory
                Banks: 2, CAS latency: 3
         Monitor 0 type: Unknown
        Xvc info not available for unmanaged boards

Code: Select all

Dudley 1# configmon -h
  SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
    0              NA            NA                  NA            NA        NA
    1   MODULE_001c01            NA                  NA            NA        NA
    2              L1        001c01                  NA            NA        NA
    3            IP34        001c01              MDB183  030-1707-003        -F
    4       MEMBANK_0        001c01                  NA            NA        NA
    5       MEMBANK_1        001c01                  NA            NA        NA
    6       MEMBANK_2        001c01                  NA            NA        NA
    7       MEMBANK_3        001c01                  NA            NA        NA
    8          R14000        001c01                  NA            NA        NA
    9              NA        001c01                  NA            NA        NA
   10            IP34        001c01              MDB183  030-1707-003        -F
   11       ASTODYV10      XTALK_13              MSX293  030-1826-001        -B
   12            IP34      XTALK_14              MDB183  030-1707-003        -F
   13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   15     SCSI_CTLR_0            NA                  NA            NA        NA
   16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
   17     SCSI_CTLR_1            NA                  NA            NA        NA
   18         CDROM_6            NA                  NA            NA        NA
   19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 7:27 pm

After a sprinkle donut...

Code: Select all

Dudley 1# /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
        Managed (":0.0") 1280x1024
        BUZZ version B.1
        PB&J version 1
        32MB memory
                Banks: 2, CAS latency: 3
         Monitor 0 type: Unknown
        Channel 0:
         Origin = (0,0)
         Video Output: 1280 pixels, 1024 lines, 72.24Hz (1280x1024_72)
Dudley 2#

Code: Select all

Dudley 2# configmon -h
  SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
    0              NA            NA                  NA            NA        NA
    1   MODULE_001c01            NA                  NA            NA        NA
    2              L1        001c01                  NA            NA        NA
    3            IP34        001c01              MDB183  030-1707-003        -F
    4       MEMBANK_0        001c01                  NA            NA        NA
    5       MEMBANK_1        001c01                  NA            NA        NA
    6       MEMBANK_2        001c01                  NA            NA        NA
    7       MEMBANK_3        001c01                  NA            NA        NA
    8          R14000        001c01                  NA            NA        NA
    9              NA        001c01                  NA            NA        NA
   10            IP34        001c01              MDB183  030-1707-003        -F
   11         ASTODYB      XTALK_13              MLB811  030-1725-001        -F
   12            IP34      XTALK_14              MDB183  030-1707-003        -F
   13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   15     SCSI_CTLR_0            NA                  NA            NA        NA
   16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
   17     SCSI_CTLR_1            NA                  NA            NA        NA
   18         CDROM_6            NA                  NA            NA        NA
   19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================

This is the 'old style' V10, with the square SGRAM's. Actually glad it works, this is the first time I've powered it up.
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day

User avatar
hamei
Posts: 10437
Joined: Tue Feb 24, 2004 4:10 pm
Location: over the rainbow

Re: #define INV_ODSY_MEMCFG_512

Unread postby hamei » Fri May 29, 2009 7:42 pm

Dr. Dave wrote:

Code: Select all

Dudley 1# /usr/gfx/gfxinfo

Is your other Fuel Snidely or Sweet_Nell ? Don't tell me it's Horse :P

User avatar
Dr. Dave
Posts: 2311
Joined: Fri Feb 13, 2004 10:37 pm
Location: Ottawa, Canada >burp<

Re: #define INV_ODSY_MEMCFG_512

Unread postby Dr. Dave » Fri May 29, 2009 7:51 pm

Boston Creme this time...

Code: Select all

Dudley 1# /usr/gfx/gfxinfo
Graphics board 0 is "ODYSSEY" graphics.
        Managed (":0.0") 1280x1024
        BUZZ version B.1
        PB&J version 1
        32MB memory
                Banks: 2, CAS latency: 3
         Monitor 0 type: Unknown
        Channel 0:
         Origin = (0,0)
         Video Output: 1280 pixels, 1024 lines, 72.24Hz (1280x1024_72)
Dudley 2#

Code: Select all

Dudley 2# configmon -h
  SEQ            NAME      LOCATION          SERIAL_NUM   PART_NUMBER  REVISION
===============================================================================
    0              NA            NA                  NA            NA        NA
    1   MODULE_001c01            NA                  NA            NA        NA
    2              L1        001c01                  NA            NA        NA
    3            IP34        001c01              MDB183  030-1707-003        -F
    4       MEMBANK_0        001c01                  NA            NA        NA
    5       MEMBANK_1        001c01                  NA            NA        NA
    6       MEMBANK_2        001c01                  NA            NA        NA
    7       MEMBANK_3        001c01                  NA            NA        NA
    8          R14000        001c01                  NA            NA        NA
    9              NA        001c01                  NA            NA        NA
   10            IP34        001c01              MDB183  030-1707-003        -F
   11       ASTODYV10      XTALK_13              MSX293  030-1826-001        -B
   12            IP34      XTALK_14              MDB183  030-1707-003        -F
   13     SCSI_CTLR_3            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   14         DRIVE_0            NA     WD-WMAEP3211246  WDC WD2000JB-00F      5R15
   15     SCSI_CTLR_0            NA                  NA            NA        NA
   16         DRIVE_1            NA            J3W8WJVB  HUS151436VL3600      S3C0
   17     SCSI_CTLR_1            NA                  NA            NA        NA
   18         CDROM_6            NA                  NA            NA        NA
   19    ETHERNET_EF0            NA                  NA            NA        NA
===============================================================================


Resistor removed (note: value was 10k). No dice, didn't seem to make a difference. Ah well, up next...
:O3000: <> :O3000: :O2000: :Tezro: :Fuel: x2+ :Octane2: :Octane: x3 :1600SW: x2 :O2: x2+ :Indigo2IMP: :Indigo2: x2 :Indigo: x3 :Indy: x2+

Once you step up to the big iron, you learn all about physics, electrical standards, and first aid - usually all in the same day


Return to “SGI: Hardware”

Who is online

Users browsing this forum: No registered users and 2 guests