View previous topic :: View next topic |
Author |
Message |
HackingM2 Apprentice
Joined: 26 Jul 2004 Posts: 245 Location: Cambridge, England
|
Posted: Wed Aug 04, 2004 3:29 am Post subject: Netra x1 tail of woe - please help! (2 of 3 solved) |
|
|
Hi, I am trying to install Gentoo on a Sun Netra x1.
It is a painfull process as the machine in question has no monitor, keyboard, fdd or cd! Nor is it possible to attach any of those devices.
So far I have tried the following:
1) Install from stage one following this 'how-to' and the Gentoo Handbook.
https://forums.gentoo.org/viewtopic.php?t=93345&highlight=netboot
It fails with the following stream of errors
Code: | jis0212.c:3179: error: stray '\' in program
jis0212.c:3179: warning: initializer-string for array of chars is too long
jis0212.c:3179: warning: (near initialization for `__jisx0212_from_ucs[8737]')
jis0212.c:3179: error: syntax error before "x57"
jis0212.c:3179: error: stray '\' in program
jis0212.c:3179:72: missing terminating " haracter
jis0212.c:3181:39: \x used with no following hex digits
jis0212.c:3181: error: stray '\' in program
jis0212.c:3181: error: syntax error before "x00"
jis0212.c:3181: error: stray '\' in program
jis0212.c:3181: error: stray '\' in program
jis0212.c:3181: eror: stray '\' in program
jis0212.c:3181: error: stray '\' in program
jis0212.c:3181: error: stray '\' in program
jis0212.c:3181:76: missing terminating " character
jis0212.c:3183: warning: initializer-string for array of chars is too long
jis0212.c:3183: warning: (near initialization for `__jisx0212_from_ucs[8754]')
make[2]: *** [/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/iconvdata/jis0212.os] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/iconvdata'
make[1]: *** [iconvdata/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2'
make: *** [all] Error 2
!!! ERROR: sys-libs/glibc-2.3.2-r9 failed.
!!! Function src_compile, Line 525, Exitcode 2
!!! (no error message) |
2) I then tried a stage 2 install, which fails with the following error...
Code: | ext/IO/t/io_multihomed...............Bad file descriptor at ../ext/IO/t/io_multihomed.t line 112.
Connection timed out at ../ext/IO/t/io_multihomed.t line 98. |
This seems to be caused by not having a loopback interface. After issuing an ifconfig lo 127.0.0.1 netmask 255.0.0.0 it worked fine. Still seem to have the stage 3 problem though...
3) I then tried a stage 3 install, which rather unsurprisingly failed with this error while makeing the kernel...
Code: | In file included from sys_sparc.c:30:
/usr/src/linux-2.4.26/include/asm/utrap.h:1: error: syntax error before '/' token
/usr/src/linux-2.4.26/include/asm/utrap.h:3: error: syntax error at '@' token
In file included from sys_sparc.c:30:
/usr/src/linux-2.4.26/include/asm/utrap.h:51:1: warning: null character(s) ignored
/usr/src/linux-2.4.26/include/asm/utrap.h:51:1: warning: no newline at end of file
sys_sparc.c:498: error: syntax error before "type"
sys_sparc.c:501: warning: function declaration isn't a prototype
sys_sparc.c: In function `sys_utrap_install':
sys_sparc.c:502: error: `type' undeclared (first use in this function)
sys_sparc.c:502: error: (Each undeclared identifier is reported only once
sys_sparc.c:502: error: for each function it appears in.)
sys_sparc.c:504: error: `new_p' undeclared (first use in this function)
sys_sparc.c:505: error: `old_p' undeclared (first use in this function)
sys_sparc.c:507: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:507: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:507: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:507: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:510: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:510: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:510: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:510: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:514: error: `old_d' undeclared (first use in this function)
sys_sparc.c:515: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:515: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:515: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:515: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:545: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:545: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:545: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:545: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:549: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:549: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:549: warning: type defaults to `int' in declaration of `type name'
sys_sparc.c:549: warning: type defaults to `int' in declaration of `type name'
make[1]: *** [sys_sparc.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.26/arch/sparc64/kernel'
make: *** [_dir_arch/sparc64/kernel] Error 2 |
I fixed this by emerging sparc-sources instead of vanilla-sources, the problem is 100% repeatable with vanilla-sources though so I shall file a bug report...
Needless to say I am becoming rather discouraged. I thought it could be a hardware fault but it fails on two boxes. The strange thing is that bootstrapping worked on one of them but not the other, and when I tried it again it worked on the opposite machine!
Has anyone managed to get this to work? I am seriously considering abandoning this seemingly futile attempt.
Oh yes and the MD5s on the tars all check out fine.[/b] |
|
Back to top |
|
|
twos n00b
Joined: 13 Aug 2004 Posts: 2
|
Posted: Fri Aug 13, 2004 1:33 am Post subject: |
|
|
Quote: | It is a painfull process as the machine in question has no monitor, keyboard, fdd or cd! Nor is it possible to attach any of those devices. |
Actually you can connect a CD-ROM. If you open the case you will find a spare IDE cable and power connecter, unless you already have two HDDs. Even then you should be able to use a dual port IDE cable and a power Y to attach the CD-ROM. I've got a CD-ROM from a Ultra 10 hooked up and am installing Gentoo right now.
I've used this method to install SuSE and Solaris 8 & 9. It worked like a charm. |
|
Back to top |
|
|
HackingM2 Apprentice
Joined: 26 Jul 2004 Posts: 245 Location: Cambridge, England
|
Posted: Fri Aug 13, 2004 3:14 pm Post subject: |
|
|
twos wrote: | Quote: | It is a painfull process as the machine in question has no monitor, keyboard, fdd or cd! Nor is it possible to attach any of those devices. |
Actually you can connect a CD-ROM. If you open the case you will find a spare IDE cable and power connecter, unless you already have two HDDs. Even then you should be able to use a dual port IDE cable and a power Y to attach the CD-ROM. I've got a CD-ROM from a Ultra 10 hooked up and am installing Gentoo right now.
I've used this method to install SuSE and Solaris 8 & 9. It worked like a charm. |
I had problems with that. The OpenBOOT rom could tell that the case was open somehow (I never did find the microswitch which I assume must be there somwehere) and would not boot, it would just flash the maintenance light instead.
I thought about putting the CD drive in the case and putting the lid back on during the install but there wasn't quite enough room!
TBH it would be a lot easier if the driver for DEC Tulip networking was in the Gentoo netboot kernel! I had to use the Debian netboot image which had no gzip. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|