Bug#239012: sun ultra 2 beta 3 install
On Sat, Mar 20, 2004 at 09:28:47AM -0500, Jeff Bailey wrote:
> On Sat, 2004-03-20 at 03:57, Blars Blarson wrote:
Sparcs had problems negociating 100Mbs full with some early ethernet
switches, I wonder if the network problem is related.
> > Loading sr_mod failed. This needs to be fixed so we can do
> > non-network installs. The busybox modprobe is broken on sparc64, and
> > I've also had problems with the one in the udeb, so this isn't a new
> > problem.
>
> I think sr_mod is built into the kernel. Also, the miniiso is only
> intended to be a netboot kernel, so might not have those drivers (and I
> thought shouldn't have that menu option). Do you mind taking a look at
> that?
No, it isn't. (wishlist bug filed on kernel, d-i bug fixed by adding
module with cdrom drivers) This is the problem I was banging
into hard when I paused my d-i work a month ago.
> > The first reboot failed, however power cyclining the system got me
> > through the second-stage installer. Errors about respawning were
> > received.
> What type of failure?
VFS: Mounted root (ext3 filesystem) readonly.
INIT: version 2.85 booting
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Activating swap.
Adding Swap: 397296k swap-space (priority -1)
Checking root file system...
fsck 1.35-WIP (31-Jan-2004)
/dev/sda1: clean, 10325/1056640 fiElXeTs3, F8S5 328.94/-201.191.21392, b1l9o c
Akusg u(scth e2c0k0 2a fotne rs dn(e8x,t1 )m,o uinntt)er
nal journal
System time was Sat Mar 20 07:40:14 UTC 2004.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Sat Mar 20 07:40:16 UTC 2004.
Calculating module dependencies... done.
Loading modules: sr_mod Attached scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun
0
esp0: target 6 asynchronous
Type 'go' to resume
{0} ok g^Go^GM~M~M~
[It didn't recognize the return, echoed M~ to it.]
The messed up message when fscking sda1 happened again, but it didn't
drop to the openboot prompt.
I've got a couple other sparcs to try (ultra 30, LX) and may try the ultra2
with a head.
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: