Re: sparc64 and ipsec anyone?
> Ben Collins wrote: > > > >The problem is specific to any arch where the userspace and kernel run > >different bitness. Like sparc64, where userland is 32bit (same for > >ppc64, mips64 and some other arch's atleast for a short time). > > > >Ioctl's from userspace have to be translated in this case from 32bit to > >64bit. Those translations have to be done by someone, and no one has > >tried it yet. I'm showing my ignorance here, but I'd really like to know: Is it so bad to just run a 32 bit kernel on on a sparc64 box? I know that with the solaris kernel you're actually going to lose performance in more cases where you'll gain it by booting the 64-bit kernel. Of course everyone runs the solaris 64-bit kernel on ultrasparc, and the decreases (if any) aren't likely to be perceptible anyways. I currently run the 64-bit Linux kernel on my 10 or so ultrasparc boxes running debian, but am I actually gaining anything? I realize the instruction set expanded with ultrasparc, so let's for argument's sake compare 32 and 64-bit kernels compiled with the v9 instruction set on ultrasparc. Sorry if this is something basic that I should know. -- Nate Campi http://www.campin.net "The secret source of humour itself is not joy, but sorrow. There is no humour in heaven." - Samuel Clemens
Re: sparc64 and ipsec anyone?
I really thing it worth looking at the native linux implemetation in 2.5. I will upload openbsd isakmpd this week ported to linux. It does work on intel and i'll do some test on alpha and sun (well, i still cant install debian on my netra though). I bet the stack part'll be working on sparc64 as some of it have been written by David Miller. JeF On Mon, 2003-01-27 at 19:32, Ulrich Wurst wrote: > "Daniel van Eeden" <[EMAIL PROTECTED]> schrieb im Newsbeitrag > news:[EMAIL PROTECTED] > > Is it an sparc64 only problem or is ipsec also unusable on sparc32? > > > > I think it is only an sparc64 Problem. Since sparc64 uses a 64 bit Kernel > and 32 bit Userland there has to be a translater 32/64 bit in ioctl calls > (or so I understood). Since the IPSEC-Translater overlaps with other > translaters (namely the one for PPP) there will be a problem if your kernel > supports PPP and IPSEC (which mine does). > In sparc32 you (obviously) need no such translator. > > HTH, > > Uli > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- -> Jean-Francois Dive --> [EMAIL PROTECTED] There is no such thing as randomness. Only order of infinite complexity. - Marquis de LaPlace - deterministic Principles -
Re: sparc64 and ipsec anyone?
Ben Collins wrote: On Sun, Jan 26, 2003 at 09:35:03PM +0100, Daniel van Eeden wrote: Is it an sparc64 only problem or is ipsec also unusable on sparc32? The problem is specific to any arch where the userspace and kernel run different bitness. Like sparc64, where userland is 32bit (same for ppc64, mips64 and some other arch's atleast for a short time). Ioctl's from userspace have to be translated in this case from 32bit to 64bit. Those translations have to be done by someone, and no one has tried it yet. I actually did all of the changes about a year ago, but ran into other problems (I think DES was broken in some way, or the key wasn't making it in right). I didn't have time to debug it further, and I don't have the changes anymore. I may take a look again in the near future, because my firewall is sparc64 (the other option being to try to get 2.5 ipsec working on it), but I just moved, started a new job, and have way too much stress to work on it at the moment. Anyways, you have to write translators for the data structures passed in the ioctls. There are some examples in the kernel, it's not too tricky to do. Steve [EMAIL PROTECTED]
Re: sparc64 and ipsec anyone?
On Tue, Jan 28, 2003 at 04:14:56PM -0500, Noah L. Meyerhans wrote: > On Tue, Jan 28, 2003 at 07:47:10AM +, Paul Hedderly wrote: > > On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote: > > > In my experience, it's been unusable on anything big-endian. > > > > Nah many people use freeswan on sparc/alpha/PPC ... > > I thought that both Alpha and PPC were little endian... Nope, big. Intel is the odd duck. > I know that I got freeswan to compile on my MIPS box, though I don't > think I ever got it to actually work. But then again, I don't remember > how hard I tried. Well, Mips can be either Big- or Little-Endian. I've heard rumor of a jumper on some motherboards to flip it. Of course, that sounds just too cool to be true. - chad
Re: Help with Creator 3D! on woody
On Wed, 15 Jan 2003, Joel A. Matz wrote: [SS20/SX] > I had a very similar issue, I sovled the screen aspect by setting the > default depth at 32bbp: > ie: > > Section "Device" > Identifier "Card0" > Driver "suncg14" > BusID "SBUS:/obio/[EMAIL PROTECTED],0" > EndSection > It seems that I haven't got the hang on Xfree on debian yet. Now I'm updating another machine from RH6.2 to debian woody and I stumbled on the same issue as before. This is an U2SMP with a Creator 3D (series 3). This time I selected sunffb and manually configured che config file to 32 bit. Same behaviour as SS20/SX, i.e. no X running. This was tested with kernel 2.2.20 and 2.4.18. fbset reports: mode "1024x864-113", tried a resolution of 1024x864 with no difference in output. Are there some other issues with the Creator ? Is woody fatally flawed on sparc? Is sid any better in relation to getting X running (4.2 rather than 4.1) ? Any comment will be appreciated as the transition to debian is getting bloodier by the machine. -- Regards, Antonio Prioglio [EMAIL PROTECTED] http://www.cbtcentre.co.uk Cognitive Behavioural Therapy Centre - London
Re: Sparc5 woody boot woes update
On Tue, Jan 28, 2003 at 08:27:00PM +, Roger Burton West wrote: > On Tue, Jan 28, 2003 at 01:06:58PM -0600, Nathan E Norman wrote: > >DHCP != RARP. > >Install the RARP server (rarpd); create/edit /etc/ethers, and have > >fun. > > Yup. > > Also: it appears that some switches won't pass RARP packets. I have a > Netgear FS108 as part of the homenet, and I couldn't get my SS20 > netbooting until I swapped it out for a generic hub... Hmm, well ... I've got two of those, and I never had problems with RARP packets. I just checked; one of those switches has had an Ultra 30, an Ultra 60, and two SS5s netboot through it. Disclaimer: the FS108 is connected with a crossover to a 3Com switch. The RARP server is connected to the 3Com. -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] Q: What's the difference between a computer salesman and a used car salesman? A: A used car salesman knows when he's lying.
Re: sparc64 and ipsec anyone?
On Tue, Jan 28, 2003 at 07:47:10AM +, Paul Hedderly wrote: > On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote: > > In my experience, it's been unusable on anything big-endian. > > Nah many people use freeswan on sparc/alpha/PPC ... I thought that both Alpha and PPC were little endian... I know that I got freeswan to compile on my MIPS box, though I don't think I ever got it to actually work. But then again, I don't remember how hard I tried. noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html pgpw0aPZsWmtt.pgp Description: PGP signature
Re: RAID 1 on Sun E250 running 3.0 sparc r1
Daren,
I'm replying to the list directly, although I'm not subscribed. If anyone
has replies to this message, they're probably better off going to this list
where everyone can benefit. With that said...
I wrote a somewhat cryptic guide on setting up a root RAID for Linux Sparc64
on my Ultra 30. You can find the most up-to-date version here:
http://www.doorbot.com/guides/linux/sparc64/rootraid/
I used Linux 2.4.18 with the RAID 1 patch for Sparc64 (to work around the
egcs64 miscompile). Below is a copy of revision 0.2 of the guide:
Mirrored Root RAID On Sparc64 Linux
Summary: Experiences configuring a Sun Ultra 30 to boot off of a mirrored
software RAID under Debian Linux with kernel version 2.4.18.
As part of my migration to a Sun Ultra 30 from my previous Slackware-based
server, I wanted to utilize the Linux built-in software raid ("md") to
protect my root (and boot) partition. I made many mistakes along the way,
and this guide will not attempt to recount all of them. It will attempt to
explain how I (finally) got my UltraSparc to boot off of a software RAID1,
and point out a few of the pitfalls so readers can avoid them.
My chosen operating system is Debian "Woody" running the Linux kernel
version 2.4.18. Newer versions of the Linux kernel are available, and you
may chose to use one of these instead. To start, I did a base install of
Debian, being sure to install the latest versions of the packages as
recommended by apt and dselect.
The RAID devices will be built from partitions on two 18 GB SCSI drives,
/dev/sda and /dev/sdb. The layout is as follows:
* /dev/md0 - /dev/sda1, /dev/sdb1 - RAID1 (Mirror) - Mounted as / (root
directory)
* /dev/md1 - /dev/sda4, /dev/sdb4 - RAID0 (Stripe) - Mounted as /tmp
* /dev/md2 - /dev/sda5, /dev/sdb5 - RAID1 (Mirror) - Mounted as /var/log
* /dev/md3 - /dev/sda6, /dev/sdb6 - RAID0 (Stripe) - Mounted as /var
(mounts before /var/log)
* /dev/md4 - /dev/sda7, /dev/sdb7 - RAID0 (Stripe) - Mounted as /usr
* /dev/md5 - /dev/sda8, /dev/sdb8 - RAID0 (Stripe) - Mounted as /home
* swap - /dev/sda2, /dev/sdb2 - Striped swap (each use "priority=0" as a
mount option)
I started out by getting the Woody install image on CD. In OBP, while the
memory is counting, hit L1-A (Stop-A), then "boot cdrom" to start the Debian
install. The ISO I downloaded would not boot normally with SILO; use the
"rescue" feature and the system will boot off the CD as expected. I
partitioned both drives so they both had identical partition maps. Note that
partition 3 usually fills the whole disk. When this was done, I selected
/dev/sda8 as my root partition, and installed Debian to it.
To compile a kernel on Debian-Sparc64, you need to install a few packages
first: egcs64, libncurses-dev, dpkg-dev, and kernel-package as well as the
"regular" compiler tools. In all likelihood GCC and friends are already
installed, but you will need to install egcs64 to compile the 64-bit kernel
for Sparc. You can install the required packages with the following command:
apt-get install egcs64 libncurses-dev dpkg-dev kernel-package
You can also add these packages through dselect, using the '/' key to find
them by name. If you're adventurous, GCC 3.2.1 may work; it is available as
a package from Debian "Sid" ("unstable" as of this writing).
Next I downloaded the kernel sources. I wanted to use 2.4.20, which was the
latest available, but I always got "mcount" errors on all the modules. After
I finished with this project, I stumbled upon a solution
(http://lists.debian.org/debian-sparc/2002/debian-sparc-200212/msg00124.html)
on the Debian-Sparc Mailing List. I ended up with version 2.4.18, but you
may end up with a different version. You can get the kernel sources via apt,
using a command such as "apt-get source kernel-image-2.4.18" but I opted to
download the source directly from the Linux Kernel Archives. Be sure to get
the "full" source and not just one of the patches. I extracted them (tar
xzvf file.tgz) to /usr/src/linux-2.4.18 and then changed to that directory.
If you're running any kernel prior to 2.4.20, you will need to patch the
RAID1 support in the kernel, as egcs64 miscompiles it on Sparc, and will
lead to an "oops" when you try to write to your new software raid. Here is
the patch
(http://marc.theaimsgroup.com/?l=linux-kernel&m=103075370821523&w=2) from
the Linux Kernel Mailing List.
Configure your kernel as necessary and then compile it; you may wish to
refer to the Debian FAQ on building custom kernels. Be sure to answer "yes"
to RAID support, and verify that RAID1 support is compiled into the kernel
(instead of a module). When you have finished with the kernel configuration,
save the configuration, and run the "make-kpkg" command with the appropriate
arguments to build the new kernel. Next, install the kernel using the "dpkg"
command.
If you already have RAID support enabled in the kernel, we can configure the
RAID devices. Otherwise, reboot the system. Save the fol
Re: Sparc5 woody boot woes update
On Tue, Jan 28, 2003 at 01:06:58PM -0600, Nathan E Norman wrote: >DHCP != RARP. >Install the RARP server (rarpd); create/edit /etc/ethers, and have >fun. Yup. Also: it appears that some switches won't pass RARP packets. I have a Netgear FS108 as part of the homenet, and I couldn't get my SS20 netbooting until I swapped it out for a generic hub... Roger
Re: Sparc5 woody boot woes update
You won't need a rarp enabled kernel, just install rarpd. and make sure you give the bootfile the right uppercase name. http://www.debian.org/releases/stable/sparc/ch-install-methods.en.html#s-install-tftp Taras Ciuriak wrote: An update for those interested in my progress with getting this working. :-) I set up my Linux laptop as a DHCP server. I can confirm it's working as, quite coincidentally, a colleague popped by my desk to ask what the next free IP address was. Sure enough, in my log he'd already been picked up by the new DHCP server...so far so good. Next, I fiddled with xinetd to get tftpd set up. It's the only service I configured to run under xinetd and xinetd duly informs me now that it actually has one service configured to run. Unfortunately, still, when I "boot net", I get the message "Timeout waiting for ARP/RARP packet". I found this trolling the web for solutions (http://lists.debian.org/debian-boot/2002/debian-boot-200211/msg00280.html) so tried that (i.e. "boot net:dhcp") but it continues issuing the timeout message. I've run watch-net and it only reports good packets, so clearly something is getting through. However my laptop's logs show me nothing by way of communication. I can set the arp entry on my laptop for the sparc5 ok fine (my kernel doesn't support rarp (yet)), but still the timeout messages flow. The above link doesn't seem to think that should matter though, so I'm kinda done for the day on this. If any of this is ringing alarm bells for anyone, please let me know! Thanks../Taras -- +-+ | Daniel van Eeden <[EMAIL PROTECTED]> | | icq: 36952189 | | aim: Compukid128| | msn: [EMAIL PROTECTED]| | phone: +31 343 522622 | | http://compukid.no-ip.org/about_me.html | +-+
Re: Sparc5 woody boot woes update
On Tue, Jan 28, 2003 at 06:00:17PM +, Taras Ciuriak wrote: > An update for those interested in my progress with getting this working. > :-) > > I set up my Linux laptop as a DHCP server. I can confirm it's working > as, quite coincidentally, a colleague popped by my desk to ask what the > next free IP address was. Sure enough, in my log he'd already been > picked up by the new DHCP server...so far so good. Next, I fiddled with > xinetd to get tftpd set up. It's the only service I configured to run > under xinetd and xinetd duly informs me now that it actually has one > service configured to run. > > Unfortunately, still, when I "boot net", I get the message "Timeout > waiting for ARP/RARP packet". DHCP != RARP. Install the RARP server (rarpd); create/edit /etc/ethers, and have fun. I assume you have RTFM on how to name your tftp files for booting. -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] For the next hour, WE will control all that you see and hear.
Re: Sparc5 woody boot woes update
An update for those interested in my progress with getting this working. :-) I set up my Linux laptop as a DHCP server. I can confirm it's working as, quite coincidentally, a colleague popped by my desk to ask what the next free IP address was. Sure enough, in my log he'd already been picked up by the new DHCP server...so far so good. Next, I fiddled with xinetd to get tftpd set up. It's the only service I configured to run under xinetd and xinetd duly informs me now that it actually has one service configured to run. Unfortunately, still, when I "boot net", I get the message "Timeout waiting for ARP/RARP packet". I found this trolling the web for solutions (http://lists.debian.org/debian-boot/2002/debian-boot-200211/msg00280.html) so tried that (i.e. "boot net:dhcp") but it continues issuing the timeout message. I've run watch-net and it only reports good packets, so clearly something is getting through. However my laptop's logs show me nothing by way of communication. I can set the arp entry on my laptop for the sparc5 ok fine (my kernel doesn't support rarp (yet)), but still the timeout messages flow. The above link doesn't seem to think that should matter though, so I'm kinda done for the day on this. If any of this is ringing alarm bells for anyone, please let me know! Thanks../Taras
Re: Bug#178465: fix for bug #178465
retitle 178465 xlibs: [XKB] missing semicolon in patch to keycodes/sun reassign 178465 xlibs severity 178465 normal tag 178465 - upstream tag 178465 + patch pending thanks On Mon, Jan 27, 2003 at 07:10:12PM +0100, Daniel van Eeden wrote: > (just add the semicolon) Whoops. Thanks! This will be fixed in the next release. -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. pgpssPtPdeBFJ.pgp Description: PGP signature
Re: raid 1 on Sun E250 running 3.0 sparc r1 (kernel 2.4.18 - patched)
On Tue, Jan 28, 2003 at 09:14:35AM -0700, [EMAIL PROTECTED] wrote: > 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 md code had significant changes in either 2.4.19 or 2.4.20 (I forget which, sorry). I'm running RAID over LVM on a sun4u here on 2.4.20 with no difficulty. 2.4.18 would freak out regularly with the same setup; I wasted an entire night fighting with it. [EMAIL PROTECTED]:~ $ uname -a Linux doriath 2.4.20 #1 SMP Thu Jan 16 16:41:14 CST 2003 sparc64 unknown [EMAIL PROTECTED]:~ $ mount /dev/vg00/lvol01 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) tmpfs on /tmp type tmpfs (rw,size=512m,nr_inodes=64k) tmpfs on /dev/shm type tmpfs (rw,size=256m,nr_inodes=32k) /dev/sda1 on /boot type ext2 (rw) /dev/vg00/lvol02 on /usr type ext3 (rw) /dev/vg00/lvol03 on /var type ext3 (rw) /dev/vg00/lvol04 on /home type ext3 (rw) /dev/vg00/lvol05 on /var/spool type ext3 (rw) /dev/vg00/lvol06 on /var/log type ext3 (rw) /dev/vg00/lvol07 on /usr/local type ext3 (rw) [EMAIL PROTECTED]:~ $ cat /proc/mdstat Personalities : [raid1] read_ahead 1024 sectors md0 : active raid1 scsi/host0/bus0/target1/lun0/part4[1] scsi/host0/bus0/target0/lun0/part4[0] 8513472 blocks [2/2] [UU] unused devices: How have you set up SILO? I used a non-RAID /boot as you can see. I'm interested in other approaches. Best regards, -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] For myself, I can only say that I am astonished and somewhat terrified at the results of this evening's experiments. Astonished at the wonderful power you have developed, and terrified at the thought that so much hideous and bad music may be put on record forever. -- Sir Arthur Sullivan, message to Edison, 1888
Re: SUN Blade 100 + floppy support
I know i haven't got the problem to work on my machine either and i don't know of anyone who did, i fear it's more a kernel issue but who needs floppy's anyhow ;) > What kind of error did you get? what did you try to get it working? > > Harka Gyozo wrote: > > HELP! > > > > I can't use the floppy drives on sun blade 100 machines... > > It would be good to make something, there are 40 machines now at a > > labor.. and my boss tends to install solaris if I can't solve this > > problem :((( > > > > If somebody has got the answer or just something news for me, please > > reply!! > > > > With thanks: > > Carlos -- <=> Elie De Brauwer www.de-brauwer.be <=>
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
Re: sparc64 and ipsec anyone?
On Tue, Jan 28, 2003 at 08:21:42AM -0500, Ben Collins wrote: > On Sun, Jan 26, 2003 at 09:35:03PM +0100, Daniel van Eeden wrote: > > Is it an sparc64 only problem or is ipsec also unusable on sparc32? > > The problem is specific to any arch where the userspace and kernel run > different bitness. Like sparc64, where userland is 32bit (same for > ppc64, mips64 and some other arch's atleast for a short time). > > Ioctl's from userspace have to be translated in this case from 32bit to > 64bit. Those translations have to be done by someone, and no one has > tried it yet. Stupid question: Aren't 64-bit userland binaries supported by the sun4u kernels? If so, can't ipsec userland be compiled as a 64-bit app? Please enlighten me; I know I don't know all the details. -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] Avoid gunfire in the bathroom tonight.
Re: SUN Blade 100 + floppy support
What kind of error did you get? what did you try to get it working? Harka Gyozo wrote: HELP! I can't use the floppy drives on sun blade 100 machines... It would be good to make something, there are 40 machines now at a labor.. and my boss tends to install solaris if I can't solve this problem :((( If somebody has got the answer or just something news for me, please reply!! With thanks: Carlos -- +-+ | Daniel van Eeden <[EMAIL PROTECTED]> | | icq: 36952189 | | aim: Compukid128| | msn: [EMAIL PROTECTED]| | phone: +31 343 522622 | | http://compukid.no-ip.org/about_me.html | +-+
Re: sparc64 and ipsec anyone?
On Tue, Jan 28, 2003 at 02:31:02PM +0100, Martin Rusko wrote: > > > Paul Hedderly wrote: > >On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote: > > > >>In my experience, it's been unusable on anything big-endian. > > > > > >Nah many people use freeswan on sparc/alpha/PPC ... > > I was unable to compile freeswan on Sun Ultra1 (sparc64) due use of two Ahh.. > So maybe it is working on sparc32, but in my experience not on sparc64. Yea I guess so... -- Paul
SUN Blade 100 + floppy support
HELP! I can't use the floppy drives on sun blade 100 machines... It would be good to make something, there are 40 machines now at a labor.. and my boss tends to install solaris if I can't solve this problem :((( If somebody has got the answer or just something news for me, please reply!! With thanks: Carlos
RE: Sparc5 woody CDR boot woes
Title: RE: Sparc5 woody CDR boot woes Does the devalias `cdrom' of OpenBoot point to the correct boot device? `devalias' at ok prompt should look similar like this: ... cdrom /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f ... >Anyway, I put the first CDR I burned from the downloaded ISO in and >typed "boot cdrom" at the Ok prompt. Result? "Can't read disk label. >Can't open disk label package. Can't open boot device." Cheers, Roland LGT Financial Services Limited Herrengasse 12, P.O. Box 85, FL-9490 VADUZ Principality of Liechtenstein Tel. +423 235 24 44, Fax +423 235 24 40 Mail: [EMAIL PROTECTED] Web: http://www.lgt.com -- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. ---
Re: sparc64 and ipsec anyone?
Paul Hedderly wrote: On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote: In my experience, it's been unusable on anything big-endian. Nah many people use freeswan on sparc/alpha/PPC ... I was unable to compile freeswan on Sun Ultra1 (sparc64) due use of two compilers. One for kernel (egcs64), other for userland. If a code is not written with this issue in mind (freeswan is not), then you will end with problems, when userland part of freeswan (compiled with gcc) will call code from kernel (which is compiled with egcs64). So maybe it is working on sparc32, but in my experience not on sparc64. I'm using TINC now ;-) mARTin -- Paul Daniel van Eeden wrote: Is it an sparc64 only problem or is ipsec also unusable on sparc32? Daniel van Eeden <[EMAIL PROTECTED]> Noah L. Meyerhans wrote: On Sun, Jan 26, 2003 at 11:06:51AM +0100, Ulrich Wurst wrote: Has anyone of you successfully managed to use ipsec on a sparc64 machine? I've still never managed to get it working. I've basically given up on freeswan on SPARC64. Hopefully the ipsec implementation that's going in to Linux 2.6 will give better results. I don't remember the details of the freeswan problem, but it has something to do with the way ioctls are implemented on sparc64. There's some kind of translation or something that goes on in kernel space. But that's only what I can recall from my vague memories of hearing it explained; I've never actually looked at the code, and don't know my way around the kernel source well enough to know where to look. noah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Martin Rusko PhD student Department of Automation and Measurement Faculty of Mechanical Engineering Slovak University of Technology -- E-mail: [EMAIL PROTECTED] Web:http://sunsite.mine.nu/~rusko -- motto: We are Microsoft! Resistance is futile. Open your source code and prepare for assimilation.
Re: sparc64 and ipsec anyone?
On Sun, Jan 26, 2003 at 09:35:03PM +0100, Daniel van Eeden wrote: > Is it an sparc64 only problem or is ipsec also unusable on sparc32? The problem is specific to any arch where the userspace and kernel run different bitness. Like sparc64, where userland is 32bit (same for ppc64, mips64 and some other arch's atleast for a short time). Ioctl's from userspace have to be translated in this case from 32bit to 64bit. Those translations have to be done by someone, and no one has tried it yet. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Re: Sparc5 woody CDR boot woes
Daniel van Eeden wrote: hava a look at... Excellent, thanks! The machine is laid out as follows; Sparc5 with 64MB (sorry, don't know which CPU...banner isn't telling at power-on or at OpenBoot prompt!), did you look on the back? Ummm, no! Must think laterally... :-) http://www.sunstuff.org/hardware/partnumbers/599/2/0/4/4/ My bookmarks file overfloweth! You're sure it's the sparc version? Yep! Try a different color recordable or a different brand... Nope! did you use md5sum to check the image? Yep! My sparcstation doesn't have a cdrom nor a floppydriveso I used 'boot net' and it worked just fine As advised by many others, I'll try the netboot solution this morning. Many thanks to all for the advice! ../Taras
Re: Sparc5 woody CDR boot woes
Taras Ciuriak wrote: I settled on Debian as the Linux I wanted to install on it and have since been downloading the ISOs. However, I cannot get the machine to boot from CDROM. While I'm no schlub when it comes to PCs, I'll hold my hand up, I'm no expert on Sun hardware...still, this perplexes me and I hope someone out there with some expertise can help. hava a look at http://docs.sun.com/ (doesn't work with tcp_ecn enabled) and http://www.sunstuff.org/ and http://www.sunhelp.org/ and http://www.sun.com/bigadmin http://docs.sun.com/db/doc/801-6396-11 <-- SS5 http://docs.sun.com/db/doc/802-7085-10 <-- SS5-110 The machine is laid out as follows; Sparc5 with 64MB (sorry, don't know which CPU...banner isn't telling at power-on or at OpenBoot prompt!), did you look on the back? two internal HDAs, first is 4.2GB, second is 2.?GB. Two external 1GB probaly 2.1GB... SCSI disks are attached as devices 4 & 5 and device 6 is an external CDROM drive. This CDROM is P/N 599-2044-02, packaged as a SUN unit, model #611. That's all I can find off the box to indentify it. Googling on the part number reveals a zilch. Wretch. http://www.sunstuff.org/hardware/partnumbers/599/2/0/4/4/ Anyway, I put the first CDR I burned from the downloaded ISO in and typed "boot cdrom" at the Ok prompt. Result? "Can't read disk label. Can't open disk label package. Can't open boot device." You're sure it's the sparc version? Try a different color recordable or a different brand... did you use md5sum to check the image? I verified the disc as readable on my Linux laptop. I googled my dupa off trying everyone & their uncle's suggestions for problems of this ilk, all to no avail. I stuck in an official Solaris 2.7 CD and it booted, so Stop-A'd and stuck in a CDR of Solaris 2.6 on the off chance the CDROM drive merely couldn't read CDRs. It booted. My only stab is that it can't read the CDR I've written 'cause it's on a 700MB CDR, but I can't find any evidence anywhere on the web that that could be a problem. Basically, I'm stuffed if I know what's wrong. So, if you've read this far, thanks and have you got any ideas I can try out? My sparcstation doesn't have a cdrom nor a floppydriveso I used 'boot net' and it worked just fine -- +-+ | Daniel van Eeden <[EMAIL PROTECTED]> | | icq: 36952189 | | aim: Compukid128| | msn: [EMAIL PROTECTED]| | phone: +31 343 522622 | | http://compukid.no-ip.org/about_me.html | +-+
Re: sparc64 and ipsec anyone?
On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote: > In my experience, it's been unusable on anything big-endian. Nah many people use freeswan on sparc/alpha/PPC ... -- Paul > > Daniel van Eeden wrote: > > >Is it an sparc64 only problem or is ipsec also unusable on sparc32? > > > >Daniel van Eeden <[EMAIL PROTECTED]> > > > >Noah L. Meyerhans wrote: > > > >>On Sun, Jan 26, 2003 at 11:06:51AM +0100, Ulrich Wurst wrote: > >> > >>>Has anyone of you successfully managed to use ipsec on a sparc64 > >>>machine? > >>> > >> > >> > >>I've still never managed to get it working. I've basically given up on > >>freeswan on SPARC64. Hopefully the ipsec implementation that's going in > >>to Linux 2.6 will give better results. > >> > >>I don't remember the details of the freeswan problem, but it has > >>something to do with the way ioctls are implemented on sparc64. There's > >>some kind of translation or something that goes on in kernel space. But > >>that's only what I can recall from my vague memories of hearing it > >>explained; I've never actually looked at the code, and don't know my way > >>around the kernel source well enough to know where to look. > >> > >>noah > >> > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] >
