Linux MIPS Architecture development
 help / color / mirror / Atom feed
* 2.4.5 in cvs - Did anyone try ?
@ 2001-06-15 19:04 Florian Lohoff
  2001-06-16  2:14 ` Ralf Baechle
  0 siblings, 1 reply; 5+ messages in thread
From: Florian Lohoff @ 2001-06-15 19:04 UTC (permalink / raw)
  To: linux-mips


Hi,
i am  just trying 2.4.5 on an Indy and i have no luck. The kernel
gets confused very fast on the root ext2 filesystem the 2.4.3 continues
to boot from. It is spitting our "EXT2: Bit already set for inode x"
and hangs in a tight loop.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.5 in cvs - Did anyone try ?
  2001-06-15 19:04 2.4.5 in cvs - Did anyone try ? Florian Lohoff
@ 2001-06-16  2:14 ` Ralf Baechle
  2001-06-16  9:14   ` Florian Lohoff
  2001-06-19  3:39   ` mipsel-linux-ld problem ´¿¬L©ú
  0 siblings, 2 replies; 5+ messages in thread
From: Ralf Baechle @ 2001-06-16  2:14 UTC (permalink / raw)
  To: Florian Lohoff; +Cc: linux-mips

On Fri, Jun 15, 2001 at 09:04:33PM +0200, Florian Lohoff wrote:

> i am  just trying 2.4.5 on an Indy and i have no luck. The kernel
> gets confused very fast on the root ext2 filesystem the 2.4.3 continues
> to boot from. It is spitting our "EXT2: Bit already set for inode x"
> and hangs in a tight loop.

There was a stupid braino in include/asm-mips/bitops.h, make sure you
have revision 1.16 of that file.

  Ralf

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.5 in cvs - Did anyone try ?
  2001-06-16  2:14 ` Ralf Baechle
@ 2001-06-16  9:14   ` Florian Lohoff
  2001-06-19  3:39   ` mipsel-linux-ld problem ´¿¬L©ú
  1 sibling, 0 replies; 5+ messages in thread
From: Florian Lohoff @ 2001-06-16  9:14 UTC (permalink / raw)
  To: Ralf Baechle; +Cc: linux-mips

On Sat, Jun 16, 2001 at 04:14:55AM +0200, Ralf Baechle wrote:
> On Fri, Jun 15, 2001 at 09:04:33PM +0200, Florian Lohoff wrote:
> 
> > i am  just trying 2.4.5 on an Indy and i have no luck. The kernel
> > gets confused very fast on the root ext2 filesystem the 2.4.3 continues
> > to boot from. It is spitting our "EXT2: Bit already set for inode x"
> > and hangs in a tight loop.
> 
> There was a stupid braino in include/asm-mips/bitops.h, make sure you
> have revision 1.16 of that file.

I have 1.16 of that file.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* mipsel-linux-ld problem
  2001-06-16  2:14 ` Ralf Baechle
  2001-06-16  9:14   ` Florian Lohoff
@ 2001-06-19  3:39   ` ´¿¬L©ú
  2001-06-19  3:39     ` ´¿¬L©ú
  1 sibling, 1 reply; 5+ messages in thread
From: ´¿¬L©ú @ 2001-06-19  3:39 UTC (permalink / raw)
  To: Ralf Baechle; +Cc: linux-mips

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

dear all,
after we replace our mipsel-linux compiler tools with sgi's
we meet a problem which was not occurried before:
(any hint to fix? thanks alot in advanced!:)
##
genromfs -v -f rom_image -d /usr/mnt/rootfs
mipsel-linux-ld -EL -Tld.script.rd -b binary -o /usr/mnt/ramdisk.img
rom_image
##
mipsel-linux-ld: rom_image: compiled for a little endian system and target
is big endian
File in wrong format: failed to merge target specific data of file rom_image
##
(old compiler said:compiled for a little endian system and target is little
endian)
##
ld.script.rd :
OUTPUT_FORMAT("elf32-littlemips")
OUTPUT_ARCH(mips)
SECTIONS
{
  .data :
  {
    __rd_start = .;
    *(.data)
    __rd_end = .;
  }
}


[-- Attachment #2: ld.script.rd --]
[-- Type: application/octet-stream, Size: 145 bytes --]

OUTPUT_FORMAT("elf32-littlemips")
OUTPUT_ARCH(mips)
SECTIONS
{
  .data :
  {
    __rd_start = .;
    *(.data)
    __rd_end = .;
  }
}

^ permalink raw reply	[flat|nested] 5+ messages in thread

* mipsel-linux-ld problem
  2001-06-19  3:39   ` mipsel-linux-ld problem ´¿¬L©ú
@ 2001-06-19  3:39     ` ´¿¬L©ú
  0 siblings, 0 replies; 5+ messages in thread
From: ´¿¬L©ú @ 2001-06-19  3:39 UTC (permalink / raw)
  To: Ralf Baechle; +Cc: linux-mips

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

dear all,
after we replace our mipsel-linux compiler tools with sgi's
we meet a problem which was not occurried before:
(any hint to fix? thanks alot in advanced!:)
##
genromfs -v -f rom_image -d /usr/mnt/rootfs
mipsel-linux-ld -EL -Tld.script.rd -b binary -o /usr/mnt/ramdisk.img
rom_image
##
mipsel-linux-ld: rom_image: compiled for a little endian system and target
is big endian
File in wrong format: failed to merge target specific data of file rom_image
##
(old compiler said:compiled for a little endian system and target is little
endian)
##
ld.script.rd :
OUTPUT_FORMAT("elf32-littlemips")
OUTPUT_ARCH(mips)
SECTIONS
{
  .data :
  {
    __rd_start = .;
    *(.data)
    __rd_end = .;
  }
}


[-- Attachment #2: ld.script.rd --]
[-- Type: application/octet-stream, Size: 145 bytes --]

OUTPUT_FORMAT("elf32-littlemips")
OUTPUT_ARCH(mips)
SECTIONS
{
  .data :
  {
    __rd_start = .;
    *(.data)
    __rd_end = .;
  }
}

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-06-19  3:39 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-06-15 19:04 2.4.5 in cvs - Did anyone try ? Florian Lohoff
2001-06-16  2:14 ` Ralf Baechle
2001-06-16  9:14   ` Florian Lohoff
2001-06-19  3:39   ` mipsel-linux-ld problem ´¿¬L©ú
2001-06-19  3:39     ` ´¿¬L©ú

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox