Debian Sparc (Woody) and ATL support
Hello, I was curious to see if anyone has had any success using HP surestore 2/20 ATL with Debian on Sparc (Any flavor). I cannot find anything positive about this combination anywhere. Regards, Daren
Re: [spamcatcher] Re: 2.4 boot disk
> debian 3.0 r0-1 both default to 2.4.18 with the source,headers and > images for both 2.4.18 and 2.4.19 as well Er, make that images for both of those kernels are included as well - sorry for the typo Daren > > Daren > >> Nicolas WILL said: >>> Hi, >>> >>> Is there a woody 3.0rx installation boot CD or floppy with a 2.4 >>> kernel (like the bf24 option on the Intel port)? >>> >>> I'm trying to setup boxes with RAID1 and LVM. >>> >>> Such a boot disk would simplify the setup process so much... >> >> I downloaded debian 3.0r0 ISO images about 3 weeks ago and they >> defaulted to 2.4.something, at least on my ultra 1. perhaps if >> you have a 32bit system it may try to use 2.2.x I'm not sure, >> SILO wouldn't let me load a 32bit kernel even when I tried(didn't care >> either way personally). or maybe it did but the kernel >> wouldn't boot. >> >> nate >> >> >> >> >> >> -- >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >> with a subject of "unsubscribe". Trouble? Contact >> [EMAIL PROTECTED] > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED]
Re: 2.4 boot disk
debian 3.0 r0-1 both default to 2.4.18 with the source,headers and images for both 2.4.18 and 2.4.19 as well Daren > Nicolas WILL said: >> Hi, >> >> Is there a woody 3.0rx installation boot CD or floppy with a 2.4 >> kernel (like the bf24 option on the Intel port)? >> >> I'm trying to setup boxes with RAID1 and LVM. >> >> Such a boot disk would simplify the setup process so much... > > I downloaded debian 3.0r0 ISO images about 3 weeks ago and they > defaulted to 2.4.something, at least on my ultra 1. perhaps if > you have a 32bit system it may try to use 2.2.x I'm not sure, > SILO wouldn't let me load a 32bit kernel even when I tried(didn't > care either way personally). or maybe it did but the kernel > wouldn't boot. > > nate > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED]
raid 1 on Sun E250 running 3.0 sparc r1 (kernel 2.4.18 - patched)
All, I am trying to mirror our root disk. I am on Debian 3.0, r1 kernel 2.4.18 with patches running on an E250 sun box. Building the raid works fine (mkraid /dev/md0), and has no complaints. Rebooting the system shows that the raid is auto-detected and syncs just fine. mkfs.ext3 /dev/md0 runs fine as well. When I try and mount -o error=remount-ro -t ext3 /dev/md1 /mnt (or any other variation of mount) however- I get a kernel panic (See /var/log/messages entry below). the actual device partitions (/dev/sdb1, /dev/sdc1) are set to 0xfd (Linux Raid Autodetect) here is the /dev/md1 entry from /etc/raidtab raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 persistent-superblock 1 chunk-size 4 device /dev/sdb1 raid-disk 0 device /dev/sdc1 raid-disk 1 I am at my wits end here. I have other raid partitions running raid 5 , and they mount fine. I can even build a raid5 using these same disks and it does not complain. Thank you in advance for your help -Daren Eason [EMAIL PROTECTED] 480.446.0500 Jan 24 11:04:49 SNIP_HOSTNAME kernel: data_access_exception: SFSR[00801009] SFAR[f800cbb095fc], going. Jan 24 11:04:49 SNIP_HOSTNAME kernel: \|/ \|/ Jan 24 11:04:49 SNIP_HOSTNAME kernel: "@'/ .. \`@" Jan 24 11:04:49 SNIP_HOSTNAME kernel: /_| \__/ |_\ Jan 24 11:04:49 SNIP_HOSTNAME kernel: \__U_/ Jan 24 11:04:49 SNIP_HOSTNAME kernel: mount(20385): Dax Jan 24 11:04:49 SNIP_HOSTNAME kernel: TSTATE: 004411009600 TPC: 02010c9c TNPC: 02010ca0 Y: 0700Tai nted: P Jan 24 11:04:49 SNIP_HOSTNAME kernel: g0: 000f g1: f8007dd70018 g2: 0001 g3: fff8 Jan 24 11:04:49 SNIP_HOSTNAME kernel: g4: f800 g5: fffee0004dd99600 g6: f800646f8000 g7: 0014 Jan 24 11:04:49 SNIP_HOSTNAME kernel: o0: 0002 o1: f8007dd7001c o2: f8007ea1a5e0 o3: f80002299980 Jan 24 11:04:49 SNIP_HOSTNAME kernel: o4: 0002 o5: 0001 sp: f800646fac61 ret_pc: f8007dd70020 Jan 24 11:04:49 SNIP_HOSTNAME kernel: l0: f8007dd7 l1: f8007dd70448 l2: 0062e000 l3: 0002 Jan 24 11:04:49 SNIP_HOSTNAME kernel: l4: l5: 00626fe0 l6: eb98 l7: Jan 24 11:04:49 SNIP_HOSTNAME kernel: i0: 0008 i1: fffee0004dd995dc i2: i3: Jan 24 11:04:49 SNIP_HOSTNAME kernel: i4: 0002 i5: f8007dd7 i6: f800646fad21 i7: 02010e80 Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[02010e80] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[020003c0] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[004e7a10] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[004e7b00] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[004e7cd0] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0046787c] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[00493790] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0046afa4] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0046b5b0] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0047e8b0] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0047ebe8] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0042de48] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[00410af4] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Caller[0001288c] Jan 24 11:04:49 SNIP_HOSTNAME kernel: Instruction DUMP: f84763d8 b2067fdc 84073fff 80a0e000 12480013 b938a000 c4064009 80a0a000
