Re: ssh pause on ultra 2
Thanks to all who responded. Indeed, the fix for my problem was to re-compile libssl with the -mv8 switch. To save the next newbie a bit of the learning curve I went through these are the steps I took to apply this fix:. 1) Installed the source for openssl (apt-get source openssl). This put the source tree in /usr/local/src/openssl-0.9.6c. 2) edited the Configure file in the source tree to add the -mv8 entry. I opened the Configure file in vi, did a search for debian-sparc and added the -mv8 entry directly after the gcc: part of the line. 3) installed some packages I was missing (fakeroot, dpkg-dev, debhelper). I don't know if I really needed all these, but this is what I did. 4) ran /usr/local/src/openssl-0.9.6c/debian/rules binary to rebuild a .deb file 5) installed the new libssl package (dpkg --install /usr/local/src/libssl0.9.6_0.9.6c-2.woody.4_sparc.deb) 6) restarted openssh Viola! Speedy connections to my ultra2. Thanks again for the assistance everybody! JJ Streicher-Bremer Nate Campi wrote: On Mon, Dec 22, 2003 at 11:33:39AM -0600, JJ Streicher-Bremer wrote: I have woody installed on my ultra2 and have had this problem from the beginning. When I'm sshing to my system my clients (every one I have tried) pauses for approx 15 sec before coming back with a prompt (or connecting in the case of key-based auth). I do have forward _and_ reverse name lookups working on this host. I even tried compiling my own openssh with the same problem. When I run sshd in debug mode this is what I get. It's because openssh as compiled for woody doesn't have the gcc -mv8 optimizations compiled in: http://lists.debian.org/debian-sparc/2002/debian-sparc-200212/msg00025.html I ended up maintaining my own openssl and openssh debs with the optimizations compiled in, made all the difference in the world.
Re: Openboot 4.5.9
Upgrade of OBP was succesfull! But I think you should tell me where I get the updated image for debian. I used http://ftp.dk.debian.org/debian/dists/stable/main/disks-sparc/current/tftpboot.img But I get Neither SBUS nor PCI found Program terminated Oh and CDROM install gives same error again Fast Data Access MMU Miss thanks On Mon, 2003-12-22 at 20:02, Nico Ehinger wrote: D Lambrou wrote: Hi there Any ideas where I can find a patch for upgrading the firmware to v. 4.5.9? It looks like 4.5.9 solves an issue I have with installing Debian on a SunBlade 100. i have the same box (blade 100), the latest obp will work when booting via tftp. if you need more info concerning what boot image to take, lemme know. cheers, -neh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- - D Lambrou http://crazylinux.net You can always get my public key block from http://crazylinux.net/public.asc Fingerprint: C7B3 A112 3704 7202 2B33 6B28 5418 78DD 774A 7BCB
Re: Openboot 4.5.9
D Lambrou wrote: Upgrade of OBP was succesfull! But I think you should tell me where I get the updated image for debian. I used http://ftp.dk.debian.org/debian/dists/stable/main/disks-sparc/current/tftpboot.img But I get Neither SBUS nor PCI found Program terminated Oh and CDROM install gives same error again Fast Data Access MMU Miss http://auric.debian.org/~bcollins/disks-sparc/current/sparc64/tftpboot.img greets
Re: Bug#224554: kernel-package: ultrasparc problems
Hi, On Fri, 19 Dec 2003 21:59:21 -0500, Clint Adams [EMAIL PROTECTED] said: Because of some ingenious and well-thought changes to the sparc toolchain, the effect previously achievable with the command make oldconfig now must be expressed as sparc32 make ARCH=sparc64 oldconfig on UltraSPARC, but can still be make oldconfig on sun4[cdm]. If gcc 4:3.3.2-1 ever becomes available on sparc, then one will be able to touch /etc/disable_64_gcc, and thus, I assume, one will be able to run make oldconfig successfully on UltraSPARC. I further extrapolate that under such conditions, make-kpkg will successfully compile kernels. The apparent workaround is to remove the ridiculous gcc wrapper and make /usr/bin/gcc be a link to /usr/bin/gcc-3.3 like on the other 10 architectures. Given that the sparc and gcc people seem to have no intention of returning this behavior to sanity, it would nice for kernel-package to handle the default situation so that poor users don't have to jump through all the hoops to get a kernel compiled. I do not have access to the hardware mentioned above; and thus can't test any changes to the code above. If someone can provide tested patches to me, I'll be happy to incorporate them into kernel-package. manoj -- Winston Churchill: I like pigs. Dogs look up to us. Cats look down on us. Pigs treat us as equals. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
environmental monitoring
On a Netra t1 105, it is possible to use the envctrl kernel module to read the CPU temperature. Is this possible with a Netra T1 AC200?
Re: environmental monitoring
Clint Adams wrote: On a Netra t1 105, it is possible to use the envctrl kernel module to read the CPU temperature. Is this possible with a Netra T1 AC200? Not currently. E
Re: environmental monitoring
Not currently. What needs to be done to adapt the driver?
Re: environmental monitoring
Clint Adams wrote: On a Netra t1 105, it is possible to use the envctrl kernel module to read the CPU temperature. Is this possible with a Netra T1 AC200? Not currently. What needs to be done to adapt the driver? A driver needs to learn about the OBP format used on a particular platform for environmental monitoring. In the case of the T1/200 it may be similar enough to the existing bbc_envctrl driver (written for an SB1000) that you can adapt it for use on your system. At the very least, you'll have to remove the bbc_present() test. If you want temperatures available to userspace, additional modifications will be required as well. I believe the current bbc_envctrl driver monitors, but does not export, this information. If you are interested in doing this work I suggest you post to the development list (ultralinux@vger.kernel.org). E
Re: environmental monitoring
On Tue, 23 Dec 2003, Eric Brower wrote: A driver needs to learn about the OBP format used on a particular platform for environmental monitoring. In the case of the T1/200 it may be similar enough to the existing bbc_envctrl driver (written for an SB1000) that you can adapt it for use on your system. At the very least, you'll have to remove the bbc_present() test. Umm, the Netra T1 doesn't have an envctrl -- or a SUNW,rasctrl on an ebus. (pruned prtconf -pv from solaris -- linux doesn't see anything behind pmu) Node 0xf00793b8 name: 'pmu' compatible: 'pci10b9,7101' + 'pciclass,00' device-id: 7101 vendor-id: 10b9 Node 0xf0079b80 compatible: 'i2c-smbus' name: 'i2c' Node 0xf007b018 compatible: 'i2c-max1617' name: 'temperature' Node 0xf007b2c0 (0xf007b378) compatible: 'i2c-at34c02' name: 'dimm' Node 0xf007b430 compatible: 'i2c-at24c64' device_type: 'nvram' name: 'i2c-nvram' Node 0xf007bf48 device_type: 'idprom' name: 'idprom' Node 0xf007c1fc compatible: 'i2c-at24c64' name: 'motherboard-fru' Node 0xf007cd94 compatible: 'SUNW,smbus-fan-control' name: 'fan-control'
Funkiness in snmpd/mrtg in unstable?
A long time ago I gave up on getting mrtg to graph my bandwidth usage on my ultra 5 in unstable. This afternoon I finally got back to playing with it, but now I'm nearly ready to give up yet again. I've done mrtg before, and even have it running on a couple x86 machines at the moment. The snmpd on my ultra appears to be woking correctly - I can walk and get whatever I'd like from both localhost and remote machines. The mrtg graphs however, always always show me 0s. I have a buddy with an x86 system and a working mrtg setup who was kind enough to lend me his snmpd.conf and mrtg.cfg, both from matching versions of snmpd and mrtg in unstable on x86. Yet even between the snmpd.conf and mrtg.cfg I've come up with and with his two (they were almost identical...), I still get lots of zeros in my mrtg graphs. I have no iptables or tcp_wrappers to worry about. While I'm having difficulty believing it, since I've got a known working set of snmpd and mrtg conf files, I'm starting to wonder if maybe it's somehow a sparc related issue - has anyone here had any luck with mrtg on sparc? Thanks in advance, -Mark -- Mark T. Valites Unix Systems Analyst CIT - SUNY Geneseo --)) --))
Re: environmental monitoring
Umm, the Netra T1 doesn't have an envctrl -- or a SUNW,rasctrl on an ebus. I don't think that's important; all I want is the CPU temperature. This is from a 105 (where the linux 2.6.0 envctrl module works): System Configuration: Sun Microsystems sun4u Memory size: 1024 Megabytes System Peripherals (Software Nodes): SUNW,UltraSPARC-IIi-cEngine packages (driver probably installed) terminal-emulator (driver probably installed) deblocker (driver probably installed) obp-tftp (driver probably installed) disk-label (driver probably installed) ufs-file-system (driver probably installed) cdfs (driver probably installed) SUNW,builtin-drivers (driver probably installed) sun-keyboard (driver probably installed) chosen (driver probably installed) openprom (driver probably installed) client-services (driver probably installed) options (driver probably installed) aliases (driver probably installed) memory (driver probably installed) virtual-memory (driver probably installed) pci (driver probably installed) pci (driver probably installed) ebus (driver probably installed) auxio (driver probably installed) power (driver probably installed) SUNW,pll (driver probably installed) su (driver probably installed) su (driver probably installed) ecpp (driver probably installed) fdthree (driver probably installed) eeprom (driver probably installed) flashprom (driver probably installed) watchdog (driver probably installed) display7seg (driver probably installed) beeper (driver probably installed) flashprom (driver probably installed) flashprom (driver probably installed) i2c (driver probably installed) adc (driver probably installed) gpio (driver probably installed) gpio (driver probably installed) i2c (driver probably installed) SUNW,lom (driver probably installed) network (driver probably installed) scsi (driver probably installed) disk (driver probably installed) tape (driver probably installed) network (driver probably installed) pci (driver probably installed) pci (driver probably installed) ide (driver probably installed) disk (driver probably installed) cdrom (driver probably installed) SUNW,UltraSPARC-IIi (driver probably installed) And this is from a 200 (where it doesn't) System Configuration: Sun Microsystems sun4u Memory size: 512 Megabytes System Peripherals (Software Nodes): SUNW,UltraAX-i2 packages (driver probably installed) terminal-emulator (driver probably installed) deblocker (driver probably installed) obp-tftp (driver probably installed) disk-label (driver probably installed) SUNW,builtin-drivers (driver probably installed) dropins (driver probably installed) kbd-translator (driver probably installed) chosen (driver probably installed) openprom (driver probably installed) client-services (driver probably installed) options (driver probably installed) aliases (driver probably installed) memory (driver probably installed) virtual-memory (driver probably installed) pci (driver probably installed) pci (driver probably installed) ebus (driver probably installed) flashprom (driver probably installed) eeprom (driver probably installed) idprom (driver probably installed) SUNW,lomh (driver probably installed) pmu (driver probably installed) i2c (driver probably installed) temperature (driver probably installed) dimm (driver probably installed) dimm (driver probably installed) i2c-nvram (driver probably installed) idprom (driver probably installed) motherboard-fru (driver probably installed) fan-control (driver probably installed) lomp (driver probably installed) isa (driver probably installed) power (driver probably installed) serial (driver probably installed) serial (driver probably installed) network (driver probably installed) usb (driver probably installed) ide (driver probably installed) disk (driver probably installed) cdrom (driver probably installed) network (driver probably installed) usb (driver
