Previous Thread
Next Thread
Print Thread
Page 1 of 2 1 2
Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Hello,

I've tried to install some versions of IRIX but unsuccessfully.

IRIX 5.3:
1) Unknown system 'ip224613'.
2) It starts using indy_4613 but crashes showing "segmentation fault" issuing the command "boot -f dksc(0,6,8)sashARCS dksc(0,6,7)stand/fx.ARCS".

IRIX 6.5:
It also crashes showing "segmentation fault" when issuing the command "boot -f dksc(0,6,8)sashARCS dksc(0,6,7)stand/fx.ARCS".

IRIX 6.2:
It starts but crashes showing "segmentation fault" when: *At the prompt Inst> type "4" <enter> for install.*

I had installed the 6.2 successfully a couple of years ago on an older version of Mame, now I'm using 0.241, on Slackware 15, gcc 11.2.0.

Thank you in advance.

Joined: Apr 2005
Posts: 608
Likes: 2
Senior Member
Online Content
Senior Member
Joined: Apr 2005
Posts: 608
Likes: 2
ip224613 is the old system name for indy_4613.

Please post your entire command line. What CD images are you using? softlist? from archive.org?

IRIX was definitely installable during the 0.24x timeframe in MAME, although it required some fiddling (setting MAC address etc.) but it should not crash MAME

Joined: Jun 2001
Posts: 496
Likes: 19
O
Senior Member
Online Content
Senior Member
O
Joined: Jun 2001
Posts: 496
Likes: 19
Note that it could be a segfault of the irix kernel due to the missing ethernet address, not a crash of mame itself.

Joined: Apr 2005
Posts: 608
Likes: 2
Senior Member
Online Content
Senior Member
Joined: Apr 2005
Posts: 608
Likes: 2
Originally Posted by Olivier Galibert
Note that it could be a segfault of the irix kernel due to the missing ethernet address, not a crash of mame itself.
Indeed, although I think IRIX doesn't call this a "segmentation fault" but rather "unexpected exception" or "UTLB miss"... I ran into that a lot in the past

Last edited by Darkstar; 02/16/23 10:33 AM.
Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Thank you all, sorry for not being enough clear.

My command line is:

mame indy_4610 -hard irix62_4096.chd -rp ../../mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /z_distz/unix/IRIX\ 6.2/IRIX\ 6\ 2/IRIX\ 6.2\ CD1.iso


The 6.2 iso image worked on Mame 0.228 (not sure, some time has passed).

The 5.3 and 6.5 iso images are from archive.org.

The "segmentation fault" message shows in the Linux console, not in the Irix console.

Joined: Feb 2004
Posts: 2,461
Likes: 160
Very Senior Member
Online Content
Very Senior Member
Joined: Feb 2004
Posts: 2,461
Likes: 160

Joined: Apr 2005
Posts: 608
Likes: 2
Senior Member
Online Content
Senior Member
Joined: Apr 2005
Posts: 608
Likes: 2
Maybe, but I'm pretty sure that crash wasn't in 0.241 (the offending commit was from november 2022)

Last edited by Darkstar; 02/16/23 05:29 PM.
Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Originally Posted by Vas Crabb

My problem is different: the Mame window running Irix just shut and the "segmentation fault" message shows in the Linux console where I launched my command line.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Errors installing 5.3, 6.2 and 6.5:


bash-5.1$ tail -n 400 /var/log/messages | grep mame
Feb 17 21:35:20 Xinv kernel: mame[2170]: segfault at 0 ip 000000000af43dfa sp 00007fff064feb40 error 4 in mame[425000+af2a000]
Feb 17 21:42:22 Xinv kernel: mame[2308]: segfault at 0 ip 0000000007e824f9 sp 00007ffcf01f1f50 error 4 in mame[425000+af2a000]
Feb 17 21:52:54 Xinv kernel: mame[2637]: segfault at 0 ip 000000000af43dfa sp 00007ffc01ac50f0 error 4 in mame[425000+af2a000]

bash-5.1$ sudo dmesg | grep mame
Password:
[ 455.399812] mame[2170]: segfault at 0 ip 000000000af43dfa sp 00007fff064feb40 error 4 in mame[425000+af2a000]
[ 878.200506] mame[2308]: segfault at 0 ip 0000000007e824f9 sp 00007ffcf01f1f50 error 4 in mame[425000+af2a000]
[ 1510.118769] mame[2637]: segfault at 0 ip 000000000af43dfa sp 00007ffc01ac50f0 error 4 in mame[425000+af2a000]

Last edited by stef-ux; 02/17/23 09:15 PM.
Joined: May 2009
Posts: 2,104
Likes: 143
J
Very Senior Member
Offline
Very Senior Member
J
Joined: May 2009
Posts: 2,104
Likes: 143
Build with SYMBOLS=1 SYMLEVEL=1 and do a single-driver build. Those callstacks are completely useless.

Joined: Feb 2004
Posts: 2,461
Likes: 160
Very Senior Member
Online Content
Very Senior Member
Joined: Feb 2004
Posts: 2,461
Likes: 160
Or just run under GDB so you can at least get function names.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Originally Posted by Just Desserts
Build with SYMBOLS=1 SYMLEVEL=1 and do a single-driver build. Those callstacks are completely useless.

Originally Posted by Vas Crabb
Or just run under GDB so you can at least get function names.

These are two things that I'm not familiar with and at present haven't the necessary time to look into.

Anyway I've been able to run an existing hp-ux 9.10 installation and reinstall a new one, so I assume that the Mame installation works properly with no broken links or gcc update problems.

Any thoughts?

Joined: Apr 2005
Posts: 608
Likes: 2
Senior Member
Online Content
Senior Member
Joined: Apr 2005
Posts: 608
Likes: 2
Originally Posted by stef-ux
Anyway I've been able to run an existing hp-ux 9.10 installation and reinstall a new one, so I assume that the Mame installation works properly with no broken links or gcc update problems.

Any thoughts?

I don't know what running HP-UX has to do with your initial problems. HP-UX doesn't run on the SGI Indy, so you would need to run it using another driver?

Also, what do you mean by "no broken links or gcc update problems"? did you compile MAME yourself? if so, can you try the release binaries, maybe different versions to pinpoint when the problems started appearing?

Joined: Feb 2004
Posts: 2,461
Likes: 160
Very Senior Member
Online Content
Very Senior Member
Joined: Feb 2004
Posts: 2,461
Likes: 160
Originally Posted by stef-ux
Any thoughts?
HP-UX and Irix run on completely different emulated systems, so that’s completely irrelevant. We can’t debug telepathically, so if you aren’t going to provide useful information, there’s nothing we can do.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Originally Posted by Darkstar
I don't know what running HP-UX has to do with your initial problems. HP-UX doesn't run on the SGI Indy, so you would need to run it using another driver?

Also, what do you mean by "no broken links or gcc update problems"? did you compile MAME yourself? if so, can you try the release binaries, maybe different versions to pinpoint when the problems started appearing?

Please take into account that I'm a beginner, therefore inexperienced. No, I used the binaries.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Originally Posted by Vas Crabb
Or just run under GDB so you can at least get function names.

The following is what I've been able to do:


======================= IRIX 5.3 =======================

bash-5.1$ gdb mame

GNU gdb (GDB) 11.2

(...)

Reading symbols from mame...

(gdb) set args indy_4613 -hard irix53_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 5.3\ for\ Indy\ R4400\ 175MHz.img

(gdb) r

Starting program: /usr/bin/mame indy_4613 -hard irix53_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 5.3\ for\ Indy\ R4400\ 175MHz.img
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4407)]
[New Thread 0x7fffd9cd9640 (LWP 4408)]
[New Thread 0x7fffc9c88640 (LWP 4409)]
[New Thread 0x7fffc9418640 (LWP 4410)]
[Thread 0x7fffc9418640 (LWP 4410) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4403) killed]

(gdb) quit
bash-5.1$


======================= IRIX 6.2 =======================


bash-5.1$ gdb mame

GNU gdb (GDB) 11.2
(...)

Reading symbols from mame...

(gdb) set args indy_4610 -hard irix62_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.2/IRIX\ 6\ 2/IRIX\ 6.2\ CD1.iso

(gdb) r

Starting program: /usr/bin/mame indy_4610 -hard irix62_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.2/IRIX\ 6\ 2/IRIX\ 6.2\ CD1.iso
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4788)]
[New Thread 0x7fffd9cd9640 (LWP 4789)]
[New Thread 0x7fffc9c88640 (LWP 4790)]
[New Thread 0x7fffc9418640 (LWP 4791)]
[Thread 0x7fffc9418640 (LWP 4791) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x0000000007e824f9 in mips3_device::code_compile_block(unsigned char, unsigned int) ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4784) killed]

(gdb) quit
bash-5.1$



======================= IRIX 6.5 =======================


bash-5.1$ gdb mame

GNU gdb (GDB) 11.2
(...)

Reading symbols from mame...

(gdb) set args indy_4610 -hard irix65_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.5/IRIX\ 6.5\ Installation\ Tools\ June\ 1998.img

(gdb) r

Starting program: /usr/bin/mame indy_4610 -hard irix65_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.5/IRIX\ 6.5\ Installation\ Tools\ June\ 1998.img
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4996)]
[New Thread 0x7fffd9cd9640 (LWP 4997)]
[New Thread 0x7fffc5c88640 (LWP 4998)]
[New Thread 0x7fffc5418640 (LWP 4999)]
[Thread 0x7fffc5418640 (LWP 4999) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4992) killed]

(gdb) quit
bash-5.1$

Joined: Feb 2004
Posts: 2,461
Likes: 160
Very Senior Member
Online Content
Very Senior Member
Joined: Feb 2004
Posts: 2,461
Likes: 160
When it crashes, type “where” in GDB and press return. It does appear to be a different issue though, apparently something with CD-ROM emulation. Have you tried using the IRIX CDs from the software list in CHD format rather than your “IMG” format CD-ROM image? What kind of image is it supposed to be anyway? Is it a raw sector image of a data track or something else? The usual CD-ROM formats are ISO sector images, and various CUE/BIN and TOC/BIN formats with separate table of contents and data files.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Originally Posted by Vas Crabb
When it crashes, type “where” in GDB and press return.

Thank you so much, here you are:

=============== WHERE 5.3 ===============

(gdb) r
Starting program: /usr/bin/mame indy_4613 -hard irix53_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 5.3\ for\ Indy\ R4400\ 175MHz.img

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4629)]
[New Thread 0x7fffd9cd9640 (LWP 4630)]
[New Thread 0x7fffc9c88640 (LWP 4631)]
[New Thread 0x7fffc9418640 (LWP 4632)]
[Thread 0x7fffc9418640 (LWP 4632) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()

(gdb) where
#0 0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()
#1 0x000000000af44308 in cdrom_read_data(cdrom_file*, unsigned int, void*, unsigned int, bool) ()
#2 0x0000000007370671 in nscsi_cdrom_device::scsi_get_data(int, int) ()
#3 0x00000000087efbf7 in nscsi_full_device::step(bool) ()
#4 0x00000000087ee72c in nscsi_bus_device::ctrl_w(int, unsigned int, unsigned int) ()
#5 0x00000000089fa495 in wd33c9x_base_device::step(bool) ()
#6 0x000000000a5fe735 in device_scheduler::timeslice() ()
#7 0x000000000a599000 in running_machine::run(bool) ()
#8 0x0000000006868ae7 in mame_machine_manager::execute() ()
#9 0x0000000006915ffe in cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) ()
#10 0x0000000006916210 in cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#11 0x0000000006866552 in emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#12 0x0000000001fc4671 in main ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4628) killed]

(gdb) quit
bash-5.1$


=============== WHERE 6.2 ===============


(gdb) r
Starting program: /usr/bin/mame indy_4610 -hard irix62_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.2/IRIX\ 6\ 2/IRIX\ 6.2\ CD1.iso

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4688)]
[New Thread 0x7fffd9cd9640 (LWP 4689)]
[New Thread 0x7fffc9c88640 (LWP 4690)]
[New Thread 0x7fffc9418640 (LWP 4691)]
[Thread 0x7fffc9418640 (LWP 4691) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x0000000007e824f9 in mips3_device::code_compile_block(unsigned char, unsigned int) ()

(gdb) where
#0 0x0000000007e824f9 in mips3_device::code_compile_block(unsigned char, unsigned int) ()
#1 0x0000000007e4e348 in mips3_device::execute_run() ()
#2 0x000000000a5fe8a6 in device_scheduler::timeslice() ()
#3 0x000000000a599000 in running_machine::run(bool) ()
#4 0x0000000006868ae7 in mame_machine_manager::execute() ()
#5 0x0000000006915ffe in cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) ()
#6 0x0000000006916210 in cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#7 0x0000000006866552 in emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#8 0x0000000001fc4671 in main ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4684) killed]

(gdb) quit
bash-5.1$


=============== WHERE 6.5 ===============


(gdb) r
Starting program: /usr/bin/mame indy_4610 -hard irix65_4096.chd -rp /mameh/irix/ -window -mouse -nomaximize -resolution 1280x1024 -cdrom /unix/IRIX\ 6.5/IRIX\ 6.5\ Installation\ Tools\ June\ 1998.img

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea964640 (LWP 4795)]
[New Thread 0x7fffd9cd9640 (LWP 4796)]
[New Thread 0x7fffc9c88640 (LWP 4797)]
[New Thread 0x7fffc9418640 (LWP 4798)]
[Thread 0x7fffc9418640 (LWP 4798) exited]

Thread 1 "mame" received signal SIGSEGV, Segmentation fault.
0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()

(gdb) where
#0 0x000000000af43dfa in read_partial_sector(cdrom_file*, void*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, bool) ()
#1 0x000000000af44308 in cdrom_read_data(cdrom_file*, unsigned int, void*, unsigned int, bool) ()
#2 0x0000000007370671 in nscsi_cdrom_device::scsi_get_data(int, int) ()
#3 0x00000000087efbf7 in nscsi_full_device::step(bool) ()
#4 0x00000000087ee72c in nscsi_bus_device::ctrl_w(int, unsigned int, unsigned int) ()
#5 0x00000000089fa495 in wd33c9x_base_device::step(bool) ()
#6 0x000000000a5fe735 in device_scheduler::timeslice() ()
#7 0x000000000a599000 in running_machine::run(bool) ()
#8 0x0000000006868ae7 in mame_machine_manager::execute() ()
#9 0x0000000006915ffe in cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) ()
#10 0x0000000006916210 in cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#11 0x0000000006866552 in emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) ()
#12 0x0000000001fc4671 in main ()

(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 4791) killed]

(gdb) quit
bash-5.1$


Quote
It does appear to be a different issue though, apparently something with CD-ROM emulation. Have you tried using the IRIX CDs from the software list in CHD format rather than your “IMG” format CD-ROM image?

No, I haven't and didn't know that software list exists. Also I never found a reliable site for rom downloads. If you can post the relevant links that would be very appreciated.


Quote
What kind of image is it supposed to be anyway? Is it a raw sector image of a data track or something else? The usual CD-ROM formats are ISO sector images, and various CUE/BIN and TOC/BIN formats with separate table of contents and data files.

All the images come from archive.org:


bash-5.1$ file IRIX\ 5.3\ for\ Indy\ R4400\ 175MHz.img
IRIX 5.3 for Indy R4400 175MHz.img: SGI disk label (volume header)

bash-5.1$ fdisk -l IRIX\ 5.3\ for\ Indy\ R4400\ 175MHz.img
Disk IRIX 5.3 for Indy R4400 175MHz.img: 501.05 MiB, 525393920 bytes, 1026160 sectors
Geometry: 255 heads, 63 sectors/track, 63 cylinders
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: sgi

Device Start End Sectors Size Id Type Attrs
IRIX 5.3 for Indy R4400 175MHz.img8 61504 1025559 964056 470.7M 5 SGI sysv
IRIX 5.3 for Indy R4400 175MHz.img9 0 61503 61504 30M 0 SGI volhdr
IRIX 5.3 for Indy R4400 175MHz.img11 0 1025567 1025568 500.8M 6 SGI volume

Partition table entries are not in disk order.



bash-5.1$ file IRIX\ 6.2\ CD1.iso
IRIX 6.2 CD1.iso: SGI disk label (volume header)

bash-5.1$ fdisk -l IRIX\ 6.2\ CD1.iso
Disk IRIX 6.2 CD1.iso: 544.85 MiB, 571314176 bytes, 1115848 sectors
Geometry: 255 heads, 63 sectors/track, 69 cylinders
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: sgi

Device Start End Sectors Size Id Type Attrs
IRIX 6.2 CD1.iso8 63872 1115255 1051384 513.4M 5 SGI sysv
IRIX 6.2 CD1.iso9 0 63871 63872 31.2M 0 SGI volhdr
IRIX 6.2 CD1.iso11 0 1115263 1115264 544.6M 6 SGI volume

Partition table entries are not in disk order.



bash-5.1$ file IRIX\ 6.5\ Installation\ Tools\ June\ 1998.img
IRIX 6.5 Installation Tools June 1998.img: SGI disk label (volume header)

bash-5.1$ fdisk -l IRIX\ 6.5\ Installation\ Tools\ June\ 1998.img
Disk IRIX 6.5 Installation Tools June 1998.img: 296.73 MiB, 311140352 bytes, 607696 sectors
Geometry: 255 heads, 63 sectors/track, 37 cylinders
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: sgi

Device Start End Sectors Size Id Type Attrs
IRIX 6.5 Installation Tools June 1998.img8 47712 607095 559384 273.1M 5 SGI sysv
IRIX 6.5 Installation Tools June 1998.img9 0 47711 47712 23.3M 0 SGI volhdr
IRIX 6.5 Installation Tools June 1998.img11 0 607103 607104 296.4M 6 SGI volume

Partition table entries are not in disk order.

Joined: Sep 2021
Posts: 34
Likes: 2
S
stef-ux Offline OP
Member
OP Offline
Member
S
Joined: Sep 2021
Posts: 34
Likes: 2
Any chances?

Page 1 of 2 1 2

Link Copied to Clipboard
Who's Online Now
5 members (sairuk, Olivier Galibert, Pernod, 2 invisible), 18 guests, and 5 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,171
Posts120,123
Members5,039
Most Online1,283
Dec 21st, 2022
Our Sponsor
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!

Superior Solitaire
Forum hosted by www.retrogamesformac.com