broadcom BCM5700 2.6 kernel (tg3 module)

2004-05-30 Thread Michael Webber
Hi all, I have been working 12/7 for 2 weeks and 5 days on this problem with the help of #debian irc chat. My problem is I can't get my server ( HP DL140) with Broadcom BCM1504 nics to work with a 2.6 kernel of any kind. It is a dual XEON 2.4 with 2 gig of ddr ecc ram (if that matters). I h

Re: mkraid could not lock sda2

2004-03-23 Thread Michael Webber
UPDATE on bottom [snip] ___ sda1 is a swap partition and im 100% sure that isnt being used (I have 2 gigs of ram hehe) sda2 is being used thats what I boot from ... but .. what else can I do ?the error is on sda1 .. /etc/fstab = be

Re: mkraid could not lock sda2

2004-03-23 Thread Michael Webber
UPDATE on bottom On Monday 22 March 2004 22:12, Michael Webber wrote: > hi,   I have to scsi disks that are the same size and have the same > parititon sizes.  when I go   mkraid /dev/md0 > > handeling MD device /dev/md0 > > analyzin super-block > > disk0: /dev/sda1, 9799

Re: mkraid could not lock sda1

2004-03-23 Thread Michael Webber
On Monday 22 March 2004 22:12, Michael Webber wrote: > hi,   I have to scsi disks that are the same size and have the same > parititon sizes.  when I go   mkraid /dev/md0 > > handeling MD device /dev/md0 > > analyzin super-block > > disk0: /dev/sda1, 9799

mkraid could not lock sda1

2004-03-22 Thread Michael Webber
hi,   I have to scsi disks that are the same size and have the same parititon sizes.  when I go   mkraid /dev/md0 handeling MD device /dev/md0 analyzin super-block disk0: /dev/sda1, 979933kb, raid superblock at 979840kB disk1: /dev/sdb1, 979933kb, raid superblock at 979840kB md: could not lock sda