KCLUG

kclug@kclug.org

3240 discussions

Re: SSH Timeouts
by Brian Kelsay 07 Dec '04

07 Dec '04

Gerald, It was Patrick M <pert(a)tas-kc.com> that had the possible Netopia problem this morning. "to establish the case that the Fruit^H^H^H^H^HNetopia is at fault vs your particular SSH client." Brian Kelsay

2 1

Re: Dell Linux Engineering
by Brian Kelsay 07 Dec '04

07 Dec '04

It is possible that the Compaq systems were accessing/running the SMART info excessively, prematurely wearing out the drives, but the reports I heard were that the drives went out in more than just Compaq PCs. The drive itself and its implementation of SMART are more than likely to blame. With the Compaq you have a workaround is all. With other PC models the same should apply. Turn off SMART monitoring in the BIOS and the drive will not burnout prematurely. Problem is, you won't know when it is ready to keel over. What is S.M.A.R.T. technology for hard drives? S.M.A.R.T. stands for Self-Monitoring Analysis and Reporting Technology. S.M.A.R.T. technology was developed by a number of major hard disk drive manufacturers in a concerted effort to increase the reliability of drives. It is a technology that enables the PC to predict the future failure of hard disk drives. S.M.A.R.T. technology has become an industry standard for hard drive manufacturers. Through the S.M.A.R.T. system, modern hard disk drives incorporate a suite of advanced diagnostics that monitor the internal operations of a drive and provide an early warning for many types of potential problems. When a potential problem is detected, the drive can be repaired or replaced before any data is lost or damaged. The S.M.A.R.T. system monitors the drive for anything that might seem out of the ordinary, documents it, and analyzes the data. If it sees something that indicates a problem, it is capable of notifying the user (or system administrator). S.M.A.R.T. monitors disk performance, faulty sectors, recalibration, CRC errors, drive spin-up time, drive heads, distance between the heads and the disk platters, drive temperature, and characteristics of the media, motor and servomechanisms. The errors the system can detect can be predicted by a number of methods. Currently the SMART system can detect about 70% of all hard drive errors. Here's an example: motor and/or bearing failure can be predicted by an increase in the drive spin-up time and the number of retries it takes to get the drive spinning at full speed. Or, if the drive notes that error correction is being needed excessively, it can attribute this to a broken drive head or surface contamination, and it will create an alert before the problem gets worse. Armed with a prediction of failure, the user or system administrator can make a backup copy of key data, replace a suspect device prior to data loss, and avoid undesired downtime. Brian Kelsay >>> Tom Bruno <> 12/07/04 10:31AM >>> Duane Attaway wrote: > On Tue, 7 Dec 2004, Tom Bruno wrote: > >> website, it says YOU MUST disable COMPAQ SMART support in your bios >> or risk drive failure. This is a default option is set to enabled on >> most motherboards, and new pc's. > > > WTF? How would the SMART communications to the drive wreck a drive? > > Next I'll see, "running a virus checker on this computer may overheat > the CPU and cause it to catch fire, burning down your house, and > catching the whole city of Chicago to burst into flames." > > -=Duane > I have no idea, but i still have that 7th drive, and it's still chugging away. the 7th drive was having all kinds of problems, so i took it out of the pc and sat it on the shelf, When i read that one day, i disabled compaq smart support, and put the drive back in. been working now for 2 years.

2 1

RE: Dell Linux Engineering
by Brian Densmore 07 Dec '04

07 Dec '04

> -----Original Message----- > From: Duane Attaway > > Next I'll see, "running a virus checker on this computer may > overheat the > CPU and cause it to catch fire, burning down your house, and > catching the > whole city of Chicago to burst into flames." You obviously don't read enough news. http://www.cnn.com/2004/US/12/06/chicago.fire/index.html That damn M$ AV beta. #$%%$#@@!!! ;') Brian

1 0

RE: Dell Linux Engineering
by Brian Densmore 07 Dec '04

07 Dec '04

> -----Original Message----- > From: D. Hageman > > I see what you are saying now. > > Let me play Devil's advocate. > > In this sue happy country, would you immediately admit fault in a > situation like this? I am sure it is standard procedure to > make claims > that your product couldn't possibly do that. I am sure IBM > would react > the same way. IBM has never had any product defects. All that talk about IBM Deathstars and people sueing IBM to get replacement drives is all Microsoft sponsored FUD. ;') [ my laptop doesn't apply, being the dinosaur that it is] > > In general, in tech support issues they are very good. I > can't tell you > how many times I have used my next-day on-site warranty. You > call them up, Well that's both good and bad. Good that you get timely support. Bad that you *need* to use it frequently. Which would give me shudders to think what happens when the warranty runs out. I guess then it's time to go out and get a new one. > > My laptop is my #1 most important piece of computing > hardware. I can't > take time to send it in and wait in some queue for repairs. > Worse ... I > can't risk having it damaged (or cost me more money) in > shipping it back > and forth. Exactly my point. Of course sometimes you think you had good tedch support, only to discover in the end it isn't that great. Take Subaru for example. They had great support and so did the dealership. That is until the engine blew 4 miles out of warranty. Then all of a sudden, since I didn't have every receipt for every oil change done on the car, it was somehow my fault, even though the current sticker showed less than a thousand miles since the last oil change. That's new engine at $5000 at 60,004 miles. Subaru paid $0, I paid $5000.

3 3

Re: Dell Linux Engineering
by Tom Bruno 07 Dec '04

07 Dec '04

Brian Densmore wrote: >>-----Original Message----- >>From: Tom Bruno >> >> >> >>>IBM has never had any product defects. All that talk about IBM >>>Deathstars and people sueing IBM to get replacement drives is >>>all Microsoft sponsored FUD. ;') >>> >>>[ my laptop doesn't apply, being the dinosaur that it is] >>> >>> >>> >>> >>> >>I garantee this is not FUD, I've had 7 that's right SEVEN deathstar ... >> >> >Please note winking smiley attached to end of original comment. > > > > I should read better, lol... that topic gets me kinda hot headed fast.

1 0

Re: Dell Linux Engineering
by Tom Bruno 07 Dec '04

07 Dec '04

1 0

RE: Dell Linux Engineering
by Brian Densmore 07 Dec '04

07 Dec '04

I have no issue with Dell laptops. I have an IBM laptop. But see the TV-OUT thread ( http://kclug.org/pipermail/kclug/2004-December/024710.html ) for why I said what I said about Dell. It was partly tongue-in-cheek, but it sounds like they aren't very good in the support department. Something that isn't important until you need it. I like to test out the support lines for a company before I buy something from them, that way I know what to expect should I ever need help with their product. On a purchase such as a laptop, good support would be #1 in my requirements for a purchase. > -----Original Message----- > From: D. Hageman > > What in particular is your issue with them and with what models? > > I have had several different models of Dell laptops as well > as several > people that I can mention that you would probably recognize.

2 1

Re: Box stops communicating with switch on reboot
by Brian Kelsay 07 Dec '04

07 Dec '04

Did you try on the XP box "ipconfig /release" and "ipconfig /renew"? And on the Linux box "if eth0 up" or "ifconfig eth0", "dhcpcd" or "dhclient" if these are running DHCP. Give some other details. What happens if you just move the cable to another port without restarting the router? How about if you just wait longer than 2 seconds after boot? Does either ever come up? Brian Kelsay >>> Patrick M <> 12/07/04 08:15AM >>> Hi I have a couple of netopia routers with 4/8 port switches. When I take down my linux box and reboot, it won't connect unless I reset the switch. This in itself was livable I am the admin, I just have to remember to reset the switch or have someone else do it if I am not on site. Now, I reloaded an XP box on a linksys switch that is having the same problem. Is there something I am missing on this. do I need to open a port on the computers so the switches can see them easier? They end up working after resetting the switch, not something easy to do or remember every time you or your users reboot.

1 0

Box stops communicating with switch on reboot
by Patrick M 07 Dec '04

07 Dec '04

Hi I have a couple of netopia routers with 4/8 port switches. When I take down my linux box and reboot, it won't connect unless I reset the switch. This in itself was livable I am the admin, I just have to remember to reset the switch or have someone else do it if I am not on site. Now, I reloaded an XP box on a linksys switch that is having the same problem. Is there something I am missing on this. do I need to open a port on the computers so the switches can see them easier? They end up working after resetting the switch, not something easy to do or remember every time you or your users reboot.

1 0

RE: Dell Linux Engineering
by Brian Densmore 07 Dec '04

07 Dec '04

> -----Original Message----- > From: Jeremy Turner > > Hey all, > > In looking up kernel info, I noticed that Dell has a > Dell-related Linux > mailing list page: > > http://lists.us.dell.com/ > http://lists.us.dell.com/mailman/listinfo/ > That's pretty cool, now if they can only get their laptops to be stable...

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

KCLUG