On Fri, 14 May 2004 12:18:40 -0400, Ben Collins wrote:
> Am I to understand that this is based on the new cd image with my
> silo/kernel fixes? If so, did you have problems booting the initrd
> before?
I don't think so, unless netinst and businesscard images are being created
from my daily builds.
On Fri, May 14, 2004 at 03:39:53PM -0400, Ben Collins wrote:
> Then you don't have the new second.b, and I've no idea where it is
> getting 0x600. That's not from my sources. The virtual address is
> hardcoded to 0x40c0.
My image come from:
http://cdimage.debian.org/pub/cdimage-testing/dai
On Fri, May 14, 2004 at 08:47:45PM +0200, Julien Danjou wrote:
> On Fri, May 14, 2004 at 02:06:02PM -0400, Ben Collins wrote:
> > So SILO doesn't have a message like:
> >
> > Loading initial ramdisk size (at phys, virt)
>
> Humpf, it was booting from hard disk.
> I have this:
> Loading ini
On Fri, May 14, 2004 at 02:06:02PM -0400, Ben Collins wrote:
> So SILO doesn't have a message like:
>
> Loading initial ramdisk size (at phys, virt)
Humpf, it was booting from hard disk.
I have this:
Loading inital ramdisk (1821913 bytes at 0x600)...
Hope it helps.
--
Julien Danjou
On Fri, May 14, 2004 at 07:58:09PM +0200, Julien Danjou wrote:
> On Fri, May 14, 2004 at 12:36:22PM -0400, Ben Collins wrote:
> > Can you (and anyone else testing this initrd) send me the "Loading
> > initrd" line from silo aswell as the "prtconf -pv" output from the
> > machine if you are able to.
On Fri, May 14, 2004 at 12:36:22PM -0400, Ben Collins wrote:
> Can you (and anyone else testing this initrd) send me the "Loading
> initrd" line from silo aswell as the "prtconf -pv" output from the
> machine if you are able to.
>
I don't see anything about initrd after silo. :-/
Here is the prtc
On Fri, May 14, 2004 at 06:49:06PM +0200, Julien Danjou wrote:
> On Fri, May 14, 2004 at 12:18:40PM -0400, Ben Collins wrote:
> > Am I to understand that this is based on the new cd image with my
> > silo/kernel fixes?
>
> Probably since this ISO was built on 20040511.
>
> > If so, did you have p
On Fri, May 14, 2004 at 12:18:40PM -0400, Ben Collins wrote:
> Am I to understand that this is based on the new cd image with my
> silo/kernel fixes?
Probably since this ISO was built on 20040511.
> If so, did you have problems booting the initrd
> before?
I got problem with beta 4 of the instal
> > > I got the same type of warnings between the boot of the CDROM kernel and
> > > the first stage of the installer.
> >
> > Let's ask debian-sparc about this. So apparently the system boots
> > fine, but those warnings are displayed. Can/should anything be done
> > about this?
Am I to unders
On Fri, May 14, 2004 at 04:11:08PM +0100, Martin Michlmayr wrote:
> * Julien Danjou <[EMAIL PROTECTED]> [2004-05-14 16:53]:
> > > > I did not have any problem, only some warning during boot of the CDROM
> > > > about unimplemented SPARC instruction.
> > >
> > When I boot I still have these warning
* Julien Danjou <[EMAIL PROTECTED]> [2004-05-14 16:53]:
> > > I did not have any problem, only some warning during boot of the CDROM
> > > about unimplemented SPARC instruction.
> >
> When I boot I still have these warnings:
> % dmesg | grep Unimplemented
> readlink[12]: Unimplemented SPARC system
On Fri, May 14, 2004 at 03:44:30PM +0100, Martin Michlmayr wrote:
> * Julien Danjou <[EMAIL PROTECTED]> [2004-05-14 12:39]:
> > I did not have any problem, only some warning during boot of the CDROM
> > about unimplemented SPARC instruction.
>
> Did it say "illegal instruction" or something else?
* Julien Danjou <[EMAIL PROTECTED]> [2004-05-14 12:39]:
> I did not have any problem, only some warning during boot of the CDROM
> about unimplemented SPARC instruction.
Did it say "illegal instruction" or something else? Can you paste
those warnings? They didn't cause any problems, though?
--
Package: installation-reports
Debian-installer-version: Daily ISO built on 20040511 netinst
uname -a: Linux othala 2.4.26-sparc32 #1 Sat Apr 24 00:12:33 EDT 2004
sparc GNU/Linux
Date: Fri May 14 12:32:31 CEST 2004
Method:
I put the CDROM in the drive. Yeah, I did it !
Stop-A
ok boot cdrom
boot: li
14 matches
Mail list logo
