Re: OpenBSD 3.9 on a Sun Fire x4100
I have not put -current on this system. Would making this machine public and available to developers be of any use? I would also include ilom access. Thoughts? Nick
Re: OpenBSD 3.9 on a Sun Fire x4100
Er, rather I have put current on the x4100. Hmmm... I must still be brain dead from work... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Shank Sent: Thursday, June 08, 2006 6:54 PM To: misc@openbsd.org Subject: Re: OpenBSD 3.9 on a Sun Fire x4100 I have not put -current on this system. Would making this machine public and available to developers be of any use? I would also include ilom access. Thoughts? Nick
Re: OpenBSD 3.9 on a Sun Fire x4100
Paul, Actually, all I wanted to do was see if it worked. I'm loading current atm, and will post a dmesg when I get done... Nick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul de Weerd Sent: Monday, June 05, 2006 10:30 PM To: [EMAIL PROTECTED] Cc: misc@openbsd.org Subject: Re: OpenBSD 3.9 on a Sun Fire x4100 Hi Nick, On Mon, Jun 05, 2006 at 09:51:13PM -0700, [EMAIL PROTECTED] wrote: | I have been looking high and low for instructions on how to get 3.9 | running on an x4100. Not finding any, I decided to play w/ it myself. I | was able to make it work. While I have included the entire dmesg, here is | the interesting (for the SAS controller, anyway) bit: | | mpi0 at pci2 dev 3 function 0 Symbios Logic SAS1064 rev 0x02: apic 6 int | 0 (irq 11) | scsibus0 at mpi0: 63 targets | sd0 at scsibus0 targ 2 lun 0: LSILOGIC, Logical Volume, 3000 SCSI2 | 0/direct fixed | sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec total Good to see your mpi-controller is working as it should ;) | The kernel is the bsd.mp from the amd64 snapshots section, and the rest of | the system is amd64 3.9 That's not good. You're mixing -current kernel with -stable userland. Don't do that. You'll get all sorts of strange things, the longer after -stable became stable you take -current, the more weird things will happen until at some point your system may not make it past loading the kernel anymore. It's OK to play around with stuff like this (to see if your SAS controller is supported by a newer kernel), but don't run anything important in such a configuration. See that the new kernel supports your hardware and then *UPGRADE*. Not just the kernel, your entire system. If running -current is not for you then you have a limited set of options : o Wait for 4.0 which should be released in November (only 5 months from now ;) o Backport the mpi(4) driver to 3.9 (good luck, you're on your own) o Bite the bullet, run -current. If any of the issues you mention below reappear with a complete snapshot or a complete -RELEASE system, feel free to try again ;) Cheers, Paul 'WEiRD' de Weerd PS: Thanks for including a dmesg. -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: OpenBSD 3.9 on a Sun Fire x4100
On 06/06/2006, at 2:51 PM, [EMAIL PROTECTED] wrote: Hi all, I have been looking high and low for instructions on how to get 3.9 running on an x4100. Not finding any, I decided to play w/ it myself. I was able to make it work. While I have included the entire dmesg, here is the interesting (for the SAS controller, anyway) bit: mpi0 at pci2 dev 3 function 0 Symbios Logic SAS1064 rev 0x02: apic 6 int 0 (irq 11) scsibus0 at mpi0: 63 targets sd0 at scsibus0 targ 2 lun 0: LSILOGIC, Logical Volume, 3000 SCSI2 0/direct fixed sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec total ooh, so pretty. how well does it perform? The kernel is the bsd.mp from the amd64 snapshots section, and the rest of the system is amd64 3.9 dont mix current and stable. Here are the things I don't understand, and would like some insight into: 1. I'm getting all kinds of fan failure warnings, system and cpu overheat warnings, etc. This only happens under OpenBSD. The machine is cold to the touch. where are these warnings being presented? ipmi was disabled in current toward the end of last week. these machines also have a problem where they report bogus cutoffs for some of the values, im not sure how we're supposed to address that problem. 2. I can't seem to get sensorsd working. I get an error about allocating memory. Thoughts? don't mix a stable userland with a current kernel. there have been changes to sensors since 3.9 that could cause issues like this. 3. I get the following when connecting to the remote console via the iLOM: uhidev0: bad input length 8 != 0 I get it once per keystroke, and have no idea how to fix it... interesting. i'd have to play on one of these boxes to see whats going on. care to ship me one? ;) dlg
Re: OpenBSD 3.9 on a Sun Fire x4100
Hi Nick, On Mon, Jun 05, 2006 at 09:51:13PM -0700, [EMAIL PROTECTED] wrote: | I have been looking high and low for instructions on how to get 3.9 | running on an x4100. Not finding any, I decided to play w/ it myself. I | was able to make it work. While I have included the entire dmesg, here is | the interesting (for the SAS controller, anyway) bit: | | mpi0 at pci2 dev 3 function 0 Symbios Logic SAS1064 rev 0x02: apic 6 int | 0 (irq 11) | scsibus0 at mpi0: 63 targets | sd0 at scsibus0 targ 2 lun 0: LSILOGIC, Logical Volume, 3000 SCSI2 | 0/direct fixed | sd0: 69618MB, 69618 cyl, 16 head, 128 sec, 512 bytes/sec, 142577664 sec total Good to see your mpi-controller is working as it should ;) | The kernel is the bsd.mp from the amd64 snapshots section, and the rest of | the system is amd64 3.9 That's not good. You're mixing -current kernel with -stable userland. Don't do that. You'll get all sorts of strange things, the longer after -stable became stable you take -current, the more weird things will happen until at some point your system may not make it past loading the kernel anymore. It's OK to play around with stuff like this (to see if your SAS controller is supported by a newer kernel), but don't run anything important in such a configuration. See that the new kernel supports your hardware and then *UPGRADE*. Not just the kernel, your entire system. If running -current is not for you then you have a limited set of options : o Wait for 4.0 which should be released in November (only 5 months from now ;) o Backport the mpi(4) driver to 3.9 (good luck, you're on your own) o Bite the bullet, run -current. If any of the issues you mention below reappear with a complete snapshot or a complete -RELEASE system, feel free to try again ;) Cheers, Paul 'WEiRD' de Weerd PS: Thanks for including a dmesg. -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
