RE: Does anyone have software RAID 1 mirroring of / set up on Sparc?

2006-04-05 Thread Ashley Hooper
Hmm, now I'm getting a kernel panic as the system prepares to REBOOT (i.e. 
while Linux shuts down services and unmounts filesystems in preparation for 
rebooting).  This means that effectively every time we reboot the server we 
would have to use LOM to reset the chassis, which we really do not want.

I've noticed that although the panic occurs when kernel tries to mount root 
*read-only* before restarting, the data on root gets out of sync between 
reboots.  I can tell this because a minute or so after rebooting I see this on 
the console:

md: md2: sync done.

RAID1 conf printout:

 --- wd:2 rd:2

 disk 0, wo:0, o:1, dev:sda4

 disk 1, wo:0, o:1, dev:sdb4


Does anyone have any ideas on what might be causing this, and if there's a 
workaround for it?

As it seems it might be related to the migration of root to md/addition of LVM, 
here's what my mount table looks like:

/dev/md2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw,errors=remount-ro)
/dev/mapper/volgroup-lvol0 on /var type ext3 (rw)
/dev/mapper/volgroup-lvol1 on /home type ext3 (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)


Below is the panic output:
-

Will now deactivate swap.
swapoff on /dev/md1
Done deactivating swap.
Will now unmount local filesystems.
/dev/mapper/volgroup-lvol0 umounted
/dev/mapper/volgroup-lvol1 umounted
Could not find /dev/.static/dev in mtab
/dev/.static/dev umounted
/dev/md0 umounted
Done unmounting local filesystems.
Shutting down LVM Volume Groups...
  0 logical volume(s) in volume group "volgroup" now active
Mounting root files  \|/  \|/
 ystem read-only "@'/ .. \`@"
 .. /_| \__/ |_\
 \__U_/
swapper(0): Kernel bad sw trap 5 [#1]
TSTATE: 000811f09603 TPC: 00527c08 TNPC: 00527c0c Y: 000
0Not tainted
TPC: 
g0: 0003 g1: 00a4 g2: 0001 g3: f
f5c
g4: f8103f48a4a0 g5: f8001bf98000 g6: f8103eff8000 g7: f8103eca4
018
o0: f8103eca4538 o1: f8103ec5cc18 o2: fae0 o3: 0
000
o4: 0010 o5:  sp: f8103effa831 ret_pc: 0
047a7fc
RPC: 
l0: ff5c l1: f8103ec5cc00 l2: f8103eca2ec0 l3: f8103eca2
ee0
l4:  l5: 0001 l6: 07290400 l7: 0
000
i0: f8103f4aa9c0 i1: f8103ecbd380 i2: f8103eca4000 i3: 0
000
i4: f8103f492c18 i5:  i6: f8103effa8f1 i7: 0047a
318
I7: 
Caller[0047a318]: kmem_cache_free+0x4c/0x7c
Caller[00462d74]: mempool_free+0x88/0x98
Caller[00482f00]: bio_put+0x40/0x50
Caller[0047f9c0]: end_bio_bh_io_sync+0x50/0x64
Caller[004832a0]: bio_endio+0x7c/0x8c
Caller[005f2c28]: raid_end_bio_io+0x34/0xa0
Caller[005f5b20]: raid1_end_write_request+0x264/0x2d4
Caller[004832a0]: bio_endio+0x7c/0x8c
Caller[0050f088]: __end_that_request_first+0x1a8/0x4f4
Caller[005b5670]: scsi_end_request+0x18/0xe0
Caller[005b5908]: scsi_io_completion+0x1d0/0x474
Caller[005c903c]: sd_rw_intr+0x2d8/0x304
Caller[005af848]: scsi_finish_command+0xbc/0xcc
Caller[0050e178]: blk_done_softirq+0x78/0x9c
Caller[00444b70]: __do_softirq+0x4c/0xf8
Caller[00444c58]: do_softirq+0x3c/0x50
Caller[00408894]: tl0_irq4+0x14/0x20
Caller[0040f098]: cpu_idle+0x34/0x58
Caller[0042483c]: do_unlock+0x12c/0x140
Caller[4000]: 0x4000
Instruction DUMP: 0100  8532b01f  80a0a000 <93d03005> 9818  80a2a000  02
600123  96120009  80a2a010
Kernel panic - not syncing: Aiee, killing interrupt handler!
TSTATE: 008080f09606 TPC: 00672fcc TNPC: 00672fc0 Y: 000
0Not tainted
TPC: <_write_unlock_irq+0x7c/0x124>
g0:  g1: 00ff g2: 1000 g3: 0
197
g4: f8103ecb9a00 g5: f8001bfa g6: f8103f47 g7: 0
080
o0: f8103ecbd3cc o1: f8103ecbd400 o2:  o3: 0
000
o4: f8103ee75018 o5:  sp: f8103f473331 ret_pc: 0
047a618
RPC: 
l0: 0001 l1: f8103f4aab28 l2: f8103ecbd3cc l3: 0
001
l4:  l5: 0001 l6:  l7: 3
eea
i0: f8103f4aa9c0 i1: f8103ecbd380 i2: 0001 i3: 0
008
i4:  i5: 00200200 i6: f8103f4733f1 i7: 00450
370
I7: 
 <0>Press Stop-A (L1-A) to return to the boot prom


This email and any files transmitted with it are confidential and
intended solely for the use of the indi

RE: Does anyone have software RAID 1 mirroring of / set up on Sparc?

2006-04-05 Thread Ashley Hooper
> However, when it comes to mounting / from the md the boot dies - at the 
> bottom of this email I've > pasted output of the last stage of the boot 
> process.

Just to let you know, as I suspected, it was a udev problem.

In my case it was because the new filesystem didn't contain the character 
special devices for console & null.

Fixed by:

1. booting non-mirrored root
2. mount /dev/md2 /mnt
3. cd /mnt/dev
4. mknod console c 5 1
5. mknod null c 1 3

Everything's working now, but I find those messages about UUIDs being different 
between the various RAID members a bit annoying - anyone know how to fix that?


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.



RE: Does anyone have software RAID 1 mirroring of / set up on Sparc?

2006-04-05 Thread Ashley Hooper
Thanks for all your help Simon - I've updated the Openboot default boot to be 
partition 3 (All disk) and it works.  We're so close...

I did set things up slightly different to you, in that I created a separate 
/boot (partition 1, starting at cylinder 1, on each disk).  After that I 
created swap and root partitions.  After updating /etc/fstab for mirrored /boot 
& swap I can successfully boot into the system and can see that both are using 
the mirrors.

However, when it comes to mounting / from the md the boot dies - at the bottom 
of this email I've pasted output of the last stage of the boot process.

I can confirm that:

  I compiled kernel with all require storage drivers, RAID support & RAID1 
compiled in
  I've set all of the RAID partitions as type 'fd'.
  I've created the RAID device /dev/md2 for / on /dev/sda4 & /dev/sdb4
  I mkfs'd /dev/md2, mounted on /mnt and copied / to it using cp -ax / /mnt
  I updated /mnt/etc/fstab to use /dev/md2 for /
  I copied the existing silo.conf entry for my working, unmirrored root drive 
(sda5), gave it a unique silo label and added a statement root=/dev/md2

Here's what my .config has to say about RAID
  
CONFIG_RAID_ATTRS=y

# CONFIG_BLK_DEV_3W__RAID is not set

# CONFIG_SCSI_AACRAID is not set

# CONFIG_MEGARAID_NEWGEN is not set

# CONFIG_MEGARAID_LEGACY is not set

# CONFIG_MEGARAID_SAS is not set

# Multi-device support (RAID and LVM)

CONFIG_MD_RAID0=m

CONFIG_MD_RAID1=y

CONFIG_MD_RAID10=m

CONFIG_MD_RAID5=m

CONFIG_MD_RAID6=m
  


And here's the boot output as promised (after the message 'Unable to open an 
initial console', the system has most definitely hung up its guns!):

md: Autodetecting RAID arrays.

md: autorun ...

md: considering sdb4 ...

md:  adding sdb4 ...

md: sdb2 has different UUID to sdb4

md: sdb1 has different UUID to sdb4

md:  adding sda4 ...

md: sda2 has different UUID to sdb4

md: sda1 has different UUID to sdb4

md: created md2

md: bind

md: bind

md: running: 

raid1: raid set md2 active with 2 out of 2 mirrors

md: considering sdb2 ...

md:  adding sdb2 ...

md: sdb1 has different UUID to sdb2

md:  adding sda2 ...

md: sda1 has different UUID to sdb2

md: created md1

md: bind

md: bind

md: running: 

raid1: raid set md1 active with 2 out of 2 mirrors

md: considering sdb1 ...

md:  adding sdb1 ...

md:  adding sda1 ...

md: created md0

md: bind

md: bind

md: running: 

raid1: raid set md0 active with 2 out of 2 mirrors

md: ... autorun DONE.

kjournald starting.  Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem) readonly.

Warning: unable to open an initial console.


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.



RE: Does anyone have software RAID 1 mirroring of / set up on Sparc?

2006-04-04 Thread Ashley Hooper
Hi Simon,

> It is quite tricky to get right. You might find this old post (about
> setting up Sarge with root on RAID-1 on my Netra) helpful:
> 
> http://lists.debian.org/debian-sparc/2005/07/msg00143.html

I tried something along the lines of what you advised, but can you
confirm that you have to create your 1st partition (in my case /boot)
starting at cylinder 1?  I am unable to boot the system without doing a
'boot disk0:x' (where x is the partition containing /boot).

When trying a straight 'boot' (i.e. boot disk0) I get the error message
'The file just loaded does not appear to be executable'.

Also, the Silo docs say for the -t option:

"Stores the boot block into the same partition as the second stage
loader.  By default, when using a SCSI or an IDE disk, SILO writes the
boot block  into the master boot (the boot block of the partition
starting at cylinder 0). This behaviour can be changed with the "-t"
argument."

Of course, I don't have any partition starting at cylinder 0.

I'd really appreciate if you could tell me how I can make Silo put
something into cylinder 0 so that a normal boot will work?

Cheers
Ashley


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




Does anyone have software RAID 1 mirroring of / set up on Sparc?

2006-04-04 Thread Ashley Hooper
Hi all,

I've been struggling with this for the last few days but no matter what I do I 
cannot get a mirrored root filesystem on my V240.  Generally what happens is 
that SILO refuses to boot from the partition as soon as it's changed to type 
'fd' (RAID autodetect).  Other times it starts to boot but only gets as far as 
single user mode and then cannot mount root properly.

The way I've been working is like this:

1.  install Debian to /dev/sda:

  /dev/sda1 - 3 GB swap
  /dev/sda2 - 10 GB root
  /dev/sda4 - 20 GB /var
  /dev/sda5 - 15 GB /home

  /dev/sda3 becomes the Sparc 'all disk' partition.
  NB I also tried a separate /boot partition but that didn't work either.

2.  download and compile the 2.6.16.1 kernel, compiling in general RAID 
support, RAID1, and all required filesystems and storage drivers.

3.  partition /dev/sdb as per /dev/sda.

4.  create mirrors for each partition on /dev/sdb but putting the first member 
as 'missing':

i.e. mdadm --create /dev/md0 --auto --verbose --level=1 --raid-devices=2 
missing /dev/sda2

5.  make filesystems for each partition and copy the data:

i.e. mkfs.ext3 /dev/md0 
 mount /dev/md0 /mnt
 cp -dpRx / /mnt

6.  fdisk and set partition types of RAID partitions on /dev/sdb to type 'fd' 
(Linux RAID autodetect)

7.  update /etc/fstab to point to the new md devices.

8.  reboot - everything's ok at this point and mount tells me that we are using 
the md devices.  This leads me to believe that we are now using the md devices 
on /dev/sdb.

9.  then I try to add the partitions on /dev/sda to the md devices:

 i.e. mdadm --add /dev/md0 /dev/sda2

...but it fails, telling me the resource is busy.  I believe this is 
because SILO still references /dev/sda2 and so the system is still actually 
mounting /dev/sda2 as root partition in spite of what /etc/fstab says.

10.  now I edit silo.conf and add the following to the kernel entry for the 
kernel I'm trying to boot
  
partition=/dev/md0
append="md=0,/dev/sda2,/dev/sdb2"

11.  usually at this point SILO will refuse to even bring up the boot prompt.

12.  I reboot using the Debian CD and change silo.conf to use /dev/sdb2 
directly (instead of as a metadevice).

13.  reboot again and then encounter a kernel panic when trying to pivot root.


I would love to hear if anyone else has guidelines on how to set this up.  Can 
anyone confirm that SILO can actually boot from a device that has partition 
type of 'fd' (Linux RAID Autodetect)?

Is my silo.conf syntax correct?

Or does anyone know of a Linux LiveCD distro for Sparc that I could use to set 
up the mirrors before starting the Debian install?

Thanks
Ashley


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.



Etch beta 2 on Sunfire V240 with 2.6.16-1 kernel - works fantastic

2006-03-31 Thread Ashley Hooper
Just to let you know, Etch with the 2.6.16-1 kernel from Sid/Unstable
works great!

Even the Broadcom tg3 NICs are working properly (although I needed udev
rules to fix their names as they seem to change names randomly between
reboots as they are enumerated).

Many thanks Jurij for his assistance.

Procedure to install:

1.  Install a PCI NIC that is known to work on Sparc Linux (i.e. 3Com
3C59x or similar) 

2.  Install from Debian Etch beta
  http://www.nl.debian.org/devel/debian-installer/

3.  Allow the installation to complete and reboot from the hard disk.
At this point the system will hang on rebooting into the new Linux
environment - 'Switching root '

4.  Boot the Etch CD again and type rescue at the Silo boot prompt.

5.  Drop out of the installer to the ash shell (select Go Back then
choose the shell option from the Debian installer menu)

6.  Mount all filesystems and chroot into the new system (partitions
below are for my system, yours may vary):

mkdir /mnt
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
mount /dev/sda4 /mnt/usr
mount /dev/sda5 /mnt/var
chroot /mnt /bin/bash

7.  Mount your pseudo filesystems and bring up your network interfaces:

mount /proc
mount /sys
ifconfig lo up
ifconfig eth0 netmask 255.255.255.0 192.168.0.64
route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.0.254

8.  Add the sid repositories to /etc/apt/sources.list

9.  apt-get update && apt-get install linux-image-2.6.16-1-sparc64-smp

10. update /etc/silo.conf and add the new kernel

11. Reboot into Linux/Sparc joy!


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




RE: More on installing Etch beta 2 on Sunfire V240

2006-03-24 Thread Ashley Hooper
Hi Daniel,

Thanks for that!  The new SILO seems to work fine with the 2.6.16 kernel
I compiled myself.

However, I've just tried booting the Debian 2.6.15 kernel from Etch with
the new SILO and that still doesn't work.  It looks likely that Jurij is
correct with his theory that initrd is the culprit.

Cheers
Ashley

> -Original Message-
> From: Daniel J. Priem [mailto:[EMAIL PROTECTED]
> Sent: 24 March 2006 18:13
> To: debian-sparc@lists.debian.org
> Subject: Re: More on installing Etch beta 2 on Sunfire V240
> 
> Uploaded.
> please check it.
> 
> http://flexserv.de/docu/sparc/
> 
> Regards
> Daniel



This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




RE: Etch beta 2 now working on Sunfire V240 with vanilla 2.6.16 compiled from source

2006-03-24 Thread Ashley Hooper
The final instalment in my monologue (for now):

OK, if you follow my previous instructions on booting the Netinst CD and
chrooting into the installed Debian environment, you can then download,
compile and install the vanilla 2.6.16 kernel, and it works.

It seems that the Debian-patched 2.6.15 kernel doesn't like the V240 and
family.

As you can imagine, I'm a very happy chappy!

Rules of thumb:

1.  Install a PCI NIC that is known to work on Sparc Linux (i.e. 3Com
3C59x or similar) 

2.  Install from Debian Etch beta
  http://www.nl.debian.org/devel/debian-installer/

3.  Partition so that your 1st partition is ext2 for /boot, and fully
resident within the first 1 GB of the disk.  Create other partitions for
swap, / etc.

4.  Allow the installation to complete and reboot from the hard disk.
At this point the system will hang on rebooting into the new Linux
environment - 'Switching root '

5.  Boot the Etch CD again and type Rescue at the Silo boot prompt.

6.  Drop out of the installer to the ash shell (select Go Back then
choose the shell option from the Debian installer menu)

7.  Mount all filesystems and chroot into the new system (partitions
below are for my system, yours may vary):

mkdir /mnt
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
mount /dev/sda4 /mnt/usr
mount /dev/sda5 /mnt/var
chroot /mnt /bin/bash

8.  Mount your pseudo filesystems and bring up your network interfaces:

mount /proc
mount /sys
ifconfig lo up
ifconfig eth0 netmask 255.255.255.0 192.168.0.64
route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.0.254

9.  You should now be able to use apt-get to get ncurses-dev which
you'll need if you want to 'make menuconfig'

10. You can now use wget to download and compile a new kernel from the
kernel sources, then copy the binary to /boot and add an entry to
/boot/silo.conf.

11. Reboot into Linux/Sparc joy!

If anyone would like assistance getting Debian working on a V240 (or
similar), email me.

Cheers
Ash


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




More on installing Etch beta 2 on Sunfire V240

2006-03-24 Thread Ashley Hooper
A couple of things I forgot to mention last night:

> -Original Message-
> I've managed to kind of get Testing working on my V240 using the beta
> netinst image located here:

http://www.nl.debian.org/devel/debian-installer/

Also, I had to open the V240 and install a 3Com 3C905C-TX to get the
machine on the network - neither the onboard Broadcom nor the
Qfe/HappyMeal interfaces would work (the latter still send frames with a
MAC address which is offset from their actual burned-in address!)

I've now downloaded the Silo 1.4.11 sources and am trying to compile
them, but when I run 'make' I encounter the below problem.  Two of
Silo's dependencies come from the kernel sources, so I had to install
the 2.6.15 sources and copy include/linux/ext2_fs.h to the Silo source
tree's include/ext2fs subdir.

I suspect the kernel sources have changed substantially and that Silo
development hasn't kept pace for whatever reason.

Is anyone running Etch on Sparc and able to compile Silo 1.4.11?


---

In file included from /usr/include/linux/percpu_counter.h:13,
 from /usr/include/linux/ext2_fs_sb.h:20,
 from ../include/ext2fs/ext2_fs.h:20,
 from ./file.h:22,
 from file.c:23:
/usr/include/linux/percpu.h: In function '__alloc_percpu':
/usr/include/linux/percpu.h:45: error: 'GFP_KERNEL' undeclared (first
use in thi
s function)
/usr/include/linux/percpu.h:45: error: (Each undeclared identifier is
reported o
nly once
/usr/include/linux/percpu.h:45: error: for each function it appears in.)
In file included from ../include/ext2fs/ext2_fs.h:20,
 from ./file.h:22,
 from file.c:23:
/usr/include/linux/ext2_fs_sb.h: At top level:
/usr/include/linux/ext2_fs_sb.h:49: error: syntax error before 'u32'
/usr/include/linux/ext2_fs_sb.h:51: error: syntax error before '*' token
/usr/include/linux/ext2_fs_sb.h:56: error: syntax error before '}' token
file.c: In function 'register_silo_inode':

[ warnings and stuff deleted ].

make[1]: *** [file.o] Error 1
make[1]: Leaving directory `/root/silo/silo-1.4.11/second'
make: *** [all] Error 1


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




RE: sarge on Sunfire V240

2006-03-23 Thread Ashley Hooper
I've managed to kind of get Testing working on my V240 using the beta
netinst image located here:


After completing a full install I encountered a hang on boot - just
after the infamous 'Switching root ...' message, but there were a couple
of messages below it about ext3.

I booted the netinst CD again and selected rescue mode.  I dropped out
to the ash shell and did the following:

1.  Mount all filesystems:

# mkdir /mnt
# mount /dev/sda2 /mnt
# mount /dev/sda1 /mnt/boot
# mount /dev/sda4 /mnt/usr
# mount /dev/sda5 /mnt/var

2.  Chroot into /mnt

# chroot /mnt /bin/bash

3.  Mount /proc and /sys (which are in /etc/fstab already)

# mount /proc
# mount /sys

4.  Connect your Ethernet cable and determine the name of the interface
(note that for me the interface enumeration got all mixed up and what
had been eth0 at install time was now eth4)

5.  Use mii-tool to tell you which interface(s) have have a link

# mii-tool

6.  Bring up the connected Ethernet interface(s)

# ifconfig eth4 netmask 255.255.255.0 192.168.0.64
# route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.0.254

7.  Confirm name resolution is working and that your /etc/resolv.conf
has the correct nameserver(s)

# nslookup www.google.com

8.  Now you should be able to apt-get update && apt-get upgrade etc

I suspect that the kernel hangs we're seeing are occurring when the
kernel hands over to init to continue the boot process.  Does anyone
know how I might be able to troubleshoot?

Cheers
Ashley


> -Original Message-
> From: Ashley Hooper [mailto:[EMAIL PROTECTED]
> Sent: 23 March 2006 15:27
> To: Robin Stevens; debian-sparc@lists.debian.org
> Subject: RE: sarge on Sunfire V240
> 
> > -Original Message-
> > From: Robin Stevens [mailto:[EMAIL PROTECTED]
> >
> > I've been attempting to do a sarge install on a Sunfire V240 system
> > (single CPU, 1GB RAM).
> 
> [Ashley Hooper]
> I am also waiting on a workaround to get any version of Debian onto
the
> Sparc (preferably Testing)
> 
>

> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> [EMAIL PROTECTED]
> 
> This email has been scanned for all viruses by the FFastFill Email
> Security System.
>




This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




RE: sarge on Sunfire V240

2006-03-23 Thread Ashley Hooper
> -Original Message-
> From: Robin Stevens [mailto:[EMAIL PROTECTED]
> 
> I've been attempting to do a sarge install on a Sunfire V240 system
> (single CPU, 1GB RAM).

[Ashley Hooper] 
I am also waiting on a workaround to get any version of Debian onto the
Sparc (preferably Testing)


This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.




Re: RE: SunFire v240

2006-02-17 Thread Ashley Hooper








I’m trying to get at the Debian repos in the hope that
a different kernel version will fix this problem.  After failing to get
any form of networking happening with the onboard Broadcom 4-way interface, I’ve
installed a Sun ‘Happy Meal’ 4-way NIC, and have noticed a very
bizarre anomaly.

 

After plugging an Ethernet cable into the 1st interface
on the Happy Meal (alias eth4) and booting into rescue mode from the Debian
Testing netinst CD, and broadcasting for a DHCP IP address, I see the below in
tcpdump:

 

07:27:25.605818 IP 0.0.0.0.bootpc >
255.255.255.255.bootps: BOOTP/DHCP, Request from 00:03:ba:6c:e5:36 (oui
Unknown), length: 300

 

Yet the interface MAC addresses are as follows:

 

~ # ifconfig | grep 'eth'

eth0  Link encap:Ethernet 
HWaddr 00:03:BA:74:23:C9

eth1  Link encap:Ethernet 
HWaddr 00:03:BA:74:23:CA

eth2  Link encap:Ethernet 
HWaddr 00:03:BA:74:23:C7

eth3  Link encap:Ethernet 
HWaddr 00:03:BA:74:23:C8

eth4  Link encap:Ethernet 
HWaddr 00:03:BA:6C:F5:36

eth5  Link encap:Ethernet 
HWaddr 00:03:BA:6C:F5:37

eth6  Link encap:Ethernet 
HWaddr 00:03:BA:6C:F5:38

eth7  Link encap:Ethernet 
HWaddr 00:03:BA:6C:F5:39

 

Note that in the 2nd to last octet, the ifconfig
utility reports ‘F5’, where tcpdump is seeing ‘E5’.

 

With a statically-configured IP address, and booted into
rescue mode (kernel 2.6.15-1-sparc64) using ping, ARPs originating on the V240 can
be seen also using an incorrect MAC address:

 

08:00:22.179511 00:03:ba:6c:e5:36 (oui Unknown) >
ff:ff:ef:ff:ff:ff (oui Unknown), ethertype ARP (0x0806), length 60: arp who-has
10.10.0.1 tell 10.10.0.2

 

Repeating the exercise with the onboard Broadcom interface,
no DHCP request is even seen by TCPDUMP so I can only assume that the Broadcom
is either not properly supported or is actually as bad as everyone says.






This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]

This email has been scanned for all viruses by the FFastFill Email
Security System.