From gerrynix at yahoo.com Sun Dec 2 14:20:43 2007 From: gerrynix at yahoo.com (gerrynix) Date: Sun, 2 Dec 2007 06:20:43 -0800 (PST) Subject: The plus symbol in fdisk -l Message-ID: <895766.19798.qm@web51908.mail.re2.yahoo.com> What does the + symbol, at the end of the "Blocks" count, signify in the output of fdisk -l ? Many TIA, Nix -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstevens at internap.com Mon Dec 3 19:05:36 2007 From: rstevens at internap.com (Rick Stevens) Date: Mon, 03 Dec 2007 11:05:36 -0800 Subject: The plus symbol in fdisk -l In-Reply-To: <895766.19798.qm@web51908.mail.re2.yahoo.com> References: <895766.19798.qm@web51908.mail.re2.yahoo.com> Message-ID: <1196708736.23994.28.camel@prophead.corp.publichost.com> On Sun, 2007-12-02 at 06:20 -0800, gerrynix wrote: > What does the + symbol, at the end of the "Blocks" count, signify in > the output of fdisk -l ? It means that the partition does not end on a cylinder boundary. By that, I mean that, after conversion to a CHS layout (cylinder, head, sector), the partition doesn't end on head 254, sector 63 and a cylinder boundary. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - "Yeah, but you're taking the universe out of context." - ---------------------------------------------------------------------- From gerrynix at yahoo.com Mon Dec 3 21:58:05 2007 From: gerrynix at yahoo.com (gerrynix) Date: Mon, 3 Dec 2007 13:58:05 -0800 (PST) Subject: The plus symbol in fdisk -l In-Reply-To: <1196708736.23994.28.camel@prophead.corp.publichost.com> Message-ID: <646764.873.qm@web51902.mail.re2.yahoo.com> On Sun, 2007-12-02 at 06:20 -0800, gerrynix wrote: > What does the + symbol, at the end of the "Blocks" count, signify in > the output of fdisk -l ? It means that the partition does not end on a cylinder boundary. By that, I mean that, after conversion to a CHS layout (cylinder, head, sector), the partition doesn't end on head 254, sector 63 and a cylinder boundary. Thanks Rick, I Googled and "manned" and couldn't find anything on this. I didn't look at the source but then again.... I am not a "source guy". So this situation is not a negative thing... Just a notice? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstevens at internap.com Mon Dec 3 23:08:22 2007 From: rstevens at internap.com (Rick Stevens) Date: Mon, 03 Dec 2007 15:08:22 -0800 Subject: The plus symbol in fdisk -l In-Reply-To: <646764.873.qm@web51902.mail.re2.yahoo.com> References: <646764.873.qm@web51902.mail.re2.yahoo.com> Message-ID: <1196723302.27855.4.camel@prophead.corp.publichost.com> On Mon, 2007-12-03 at 13:58 -0800, gerrynix wrote: > On Sun, 2007-12-02 at 06:20 -0800, gerrynix wrote: > > What does the + symbol, at the end of the "Blocks" count, signify in > > the output of fdisk -l ? > > It means that the partition does not end on a cylinder boundary. By > that, I mean that, after conversion to a CHS layout (cylinder, head, > sector), the partition doesn't end on head 254, sector 63 and a > cylinder > boundary. > > Thanks Rick, > I Googled and "manned" and couldn't find anything on this. I didn't > look at the source but then again.... I am not a "source guy". So > this situation is not a negative thing... Just a notice? Yup, informational only. It's displayed that way because some operating systems (OS/2 comes to mind as well as any that depend heavily on BIOS calls) don't like it. Most somewhat modern systems don't mind since they use LBA (logical block addressing) anyway. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - "Daddy, why doesn't this magnet pick up this floppy disk?" - ---------------------------------------------------------------------- From Yazan.Albakheit at Progressoft.com Tue Dec 4 17:30:00 2007 From: Yazan.Albakheit at Progressoft.com (Yazan Albakheit) Date: Tue, 4 Dec 2007 19:30:00 +0200 Subject: NTP Message-ID: <9F22D67428CC144B93A198ECA35B85BF13B59B0096@PS-MAILBOX.Progressoft.com> Dear , Can you Help me in configuring the NTP between two nodes running RHEL_AS_V4_U5 . I Have two Server (A,B) I want server B to take its time from server A only. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstevens at internap.com Tue Dec 4 19:31:50 2007 From: rstevens at internap.com (Rick Stevens) Date: Tue, 04 Dec 2007 11:31:50 -0800 Subject: NTP In-Reply-To: <9F22D67428CC144B93A198ECA35B85BF13B59B0096@PS-MAILBOX.Progressoft.com> References: <9F22D67428CC144B93A198ECA35B85BF13B59B0096@PS-MAILBOX.Progressoft.com> Message-ID: <1196796710.29645.23.camel@prophead.corp.publichost.com> On Tue, 2007-12-04 at 19:30 +0200, Yazan Albakheit wrote: > Dear , > > > > Can you Help me in configuring the NTP between two nodes running > RHEL_AS_V4_U5 . > > > > I Have two Server (A,B) I want server B to take its time from > server A only. The easiest way is to use system-config-date or redhat-config-date. When the GUI comes up, go to the "Network Time Protocol" tab, check the "Enable Network Time Protocol" box and put add the "A" machine in the NTP Servers box. If you want to do it the hard way, then edit /etc/ntp.conf. Delete all lines that start with the word "server", then add one that specifies your machine: server a.yourdomain.com (domain based) server www.xxx.yyy.zzz (using only an IP address) You should also delete any lines that begin "restrict" and contain the old NTP servers' names and add a line for your machine: restrict a.yourdomain.com mask 255.255.255.255 nomodify notrap noquery (that last bit should all be on one line). ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Real Time, adj.: Here and now, as opposed to fake time, which only - - occurs there and then - ---------------------------------------------------------------------- From micros50 at verizon.net Wed Dec 12 19:53:15 2007 From: micros50 at verizon.net (mylar) Date: Wed, 12 Dec 2007 14:53:15 -0500 Subject: No Video after Kernel Upgrade. Message-ID: <1197489196.4923.13.camel@manhattan.ruffe.edu> Hello I have been running Fedora 7 for several months under the XEN kernel... kernel-xen-2.6.18 for several months with relatively good results. I recently upgraded the kernel to kernel-xen-2.6.20 using yum. However, upon trying to boot the machine into kernel-xen-2.6.20 I get an error message from my monitor saying "cannot display this graphics mode". I don't get it. I am running a Dell Dimension 4600 machine with an integrated 82865G graphics display card and a Dell E172FP Flat Panel LCD monitor. I am using the "i810" driver. I am running at a resolution of 1280 x 1024. It was working fine at these settings under the older 2.6.18 kernel. Matter of fact if I boot into the 2.6.18 kernel my display works fine. But if I try and boot into 2.6.20 I get bupkis along with my display telling me "I cannot display this graphics mode". Any ideas as to why I might be having this problem ? Is there something else I need to update along with the kernel. Had I not kept the old kernel on the system the machine would be unusable right now. Any help would be appreciated... Thanks. mylar -- email-> micros50 at verizon.net "I Speak Mathematics" From micros50 at verizon.net Wed Dec 12 23:05:40 2007 From: micros50 at verizon.net (mylar) Date: Wed, 12 Dec 2007 18:05:40 -0500 Subject: (UPDATE) No Video after Kernel Upgrade In-Reply-To: <1197489196.4923.13.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> Message-ID: <1197500740.3848.5.camel@manhattan.ruffe.edu> Hello... Here's an update... It seems to be working now. After I installed the new kernel via yum I rebooted into the new kernel and I had the video display problem. So I shut down and rebooted the old kernel and everything was OK. After a few hours I shut down and left. When I got back a few hours later I booted the machine and decided to give another shot at trying to boot the new kernel. Viola' it worked !! I have no idea why. I made no configuration changes or anything else, But it seems to be working fine. I am using the new kernel right now and video, sound and everything else seems to be just fine. Quite strange as to why it did not work before. mylar On Wed, 2007-12-12 at 14:53 -0500, mylar wrote: > Hello > > I have been running Fedora 7 for several months under the XEN kernel... > kernel-xen-2.6.18 for several months with relatively good results. I > recently upgraded the kernel to kernel-xen-2.6.20 using yum. However, > upon trying to boot the machine into kernel-xen-2.6.20 I get an error > message from my monitor saying "cannot display this graphics mode". > > I don't get it. I am running a Dell Dimension 4600 machine with an > integrated 82865G graphics display card and a Dell E172FP Flat Panel > LCD monitor. I am using the "i810" driver. I am running at a resolution > of 1280 x 1024. It was working fine at these settings under the older > 2.6.18 kernel. Matter of fact if I boot into the 2.6.18 kernel my > display works fine. But if I try and boot into 2.6.20 I get bupkis along > with my display telling me "I cannot display this graphics mode". > > Any ideas as to why I might be having this problem ? Is there something > else I need to update along with the kernel. Had I not kept the old > kernel on the system the machine would be unusable right now. Any help > would be appreciated... Thanks. > > mylar > > -- email-> micros50 at verizon.net "I Speak Mathematics" From micros50 at verizon.net Wed Dec 12 23:08:51 2007 From: micros50 at verizon.net (mylar) Date: Wed, 12 Dec 2007 18:08:51 -0500 Subject: Kernel remove via yum Message-ID: <1197500931.3848.10.camel@manhattan.ruffe.edu> Hello, Now that I have successfully upgraded my kernel via yum can I remove the old kernel via yum ? In other words can I simply do a "# yum remove "kernel-2.6-18" or are there any additional steps I need to take care to do ? mylar -- email-> micros50 at verizon.net "I Speak Mathematics" From bob at bobcatos.com Wed Dec 12 23:40:55 2007 From: bob at bobcatos.com (Bob McClure Jr) Date: Wed, 12 Dec 2007 17:40:55 -0600 Subject: Kernel remove via yum In-Reply-To: <1197500931.3848.10.camel@manhattan.ruffe.edu> References: <1197500931.3848.10.camel@manhattan.ruffe.edu> Message-ID: <20071212234054.GA21500@bobcat.bobcatos.com> On Wed, Dec 12, 2007 at 06:08:51PM -0500, mylar wrote: > Hello, > > Now that I have successfully upgraded my kernel via yum can I remove the > old kernel via yum ? In other words can I simply do a > > "# yum remove "kernel-2.6-18" Yeah, I guess that will work. I just use rpm: rpm -e kernel-2.6-18 That said, I always keep the previous kernel around in case some disaster strikes the new kernel, which, of course, hasn't happened, ... yet. > or are there any additional steps I need to take care to do ? > > mylar > > > > -- > email-> micros50 at verizon.net > > "I Speak Mathematics" Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob at bobcatos.com http://www.bobcatos.com Charm is deceptive, and beauty is fleeting; but a woman who fears the LORD is to be praised. Proverbs 31:30 (NIV) From rstevens at internap.com Thu Dec 13 01:39:29 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 12 Dec 2007 17:39:29 -0800 Subject: (UPDATE) No Video after Kernel Upgrade In-Reply-To: <1197500740.3848.5.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> Message-ID: <1197509969.29325.42.camel@prophead.corp.publichost.com> On Wed, 2007-12-12 at 18:05 -0500, mylar wrote: > Hello... Here's an update... > > It seems to be working now. After I installed the new kernel via yum I > rebooted into the new kernel and I had the video display problem. So I > shut down and rebooted the old kernel and everything was OK. After a few > hours I shut down and left. When I got back a few hours later I booted > the machine and decided to give another shot at trying to boot the new > kernel. Viola' it worked !! I have no idea why. I made no configuration > changes or anything else, But it seems to be working fine. I am using > the new kernel right now and video, sound and everything else seems to > be just fine. Quite strange as to why it did not work before. The video card may have misread the DRI data from the monitor and held it. The previous reboot didn't clear that data but the power cycle did. Sometimes a cold boot does magic that a warm boot doesn't. Sometimes it's just...magic! :-) > On Wed, 2007-12-12 at 14:53 -0500, mylar wrote: > > Hello > > > > I have been running Fedora 7 for several months under the XEN kernel... > > kernel-xen-2.6.18 for several months with relatively good results. I > > recently upgraded the kernel to kernel-xen-2.6.20 using yum. However, > > upon trying to boot the machine into kernel-xen-2.6.20 I get an error > > message from my monitor saying "cannot display this graphics mode". > > > > I don't get it. I am running a Dell Dimension 4600 machine with an > > integrated 82865G graphics display card and a Dell E172FP Flat Panel > > LCD monitor. I am using the "i810" driver. I am running at a resolution > > of 1280 x 1024. It was working fine at these settings under the older > > 2.6.18 kernel. Matter of fact if I boot into the 2.6.18 kernel my > > display works fine. But if I try and boot into 2.6.20 I get bupkis along > > with my display telling me "I cannot display this graphics mode". > > > > Any ideas as to why I might be having this problem ? Is there something > > else I need to update along with the kernel. Had I not kept the old > > kernel on the system the machine would be unusable right now. Any help > > would be appreciated... Thanks. > > > > mylar > > > > ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Hard work has a future payoff. Laziness pays off now. - ---------------------------------------------------------------------- From rstevens at internap.com Thu Dec 13 01:43:58 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 12 Dec 2007 17:43:58 -0800 Subject: Kernel remove via yum In-Reply-To: <20071212234054.GA21500@bobcat.bobcatos.com> References: <1197500931.3848.10.camel@manhattan.ruffe.edu> <20071212234054.GA21500@bobcat.bobcatos.com> Message-ID: <1197510238.29325.47.camel@prophead.corp.publichost.com> On Wed, 2007-12-12 at 17:40 -0600, Bob McClure Jr wrote: > On Wed, Dec 12, 2007 at 06:08:51PM -0500, mylar wrote: > > Hello, > > > > Now that I have successfully upgraded my kernel via yum can I remove the > > old kernel via yum ? In other words can I simply do a > > > > "# yum remove "kernel-2.6-18" > > Yeah, I guess that will work. I just use rpm: > > rpm -e kernel-2.6-18 > > That said, I always keep the previous kernel around in case some > disaster strikes the new kernel, which, of course, hasn't happened, > ... yet. Heheheheheh! > > or are there any additional steps I need to take care to do ? Normally yum only keeps two versions of each kernel anyway. That's what the "tokeep=2" does in /etc/yum/pluginconf.d/installonlyn.conf. If you want to keep more, then change it to whatever you want. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Blech! ACKth! Ooop! -- Bill the Cat (Outland) - ---------------------------------------------------------------------- From micros50 at verizon.net Thu Dec 13 09:10:01 2007 From: micros50 at verizon.net (mylar) Date: Thu, 13 Dec 2007 04:10:01 -0500 Subject: Kernel remove via yum In-Reply-To: <1197510238.29325.47.camel@prophead.corp.publichost.com> References: <1197500931.3848.10.camel@manhattan.ruffe.edu> <20071212234054.GA21500@bobcat.bobcatos.com> <1197510238.29325.47.camel@prophead.corp.publichost.com> Message-ID: <1197537002.3848.30.camel@manhattan.ruffe.edu> On Wed, 2007-12-12 at 17:43 -0800, Rick Stevens wrote: > On Wed, 2007-12-12 at 17:40 -0600, Bob McClure Jr wrote: > > On Wed, Dec 12, 2007 at 06:08:51PM -0500, mylar wrote: > > > Hello, > > > > > > Now that I have successfully upgraded my kernel via yum can I remove the > > > old kernel via yum ? In other words can I simply do a > > > > > > "# yum remove "kernel-2.6-18" > > > > Yeah, I guess that will work. I just use rpm: > > > > rpm -e kernel-2.6-18 > > > > That said, I always keep the previous kernel around in case some > > disaster strikes the new kernel, which, of course, hasn't happened, > > ... yet. > > Heheheheheh! > > > > or are there any additional steps I need to take care to do ? > > Normally yum only keeps two versions of each kernel anyway. That's > what the "tokeep=2" does in /etc/yum/pluginconf.d/installonlyn.conf. > If you want to keep more, then change it to whatever you want. OK thanks... I didn't know that. For now I'll just leave it as is. There's enough room and I don't mind keeping the old version around. mylar -- email-> micros50 at verizon.net "I Speak Mathematics" From rstevens at internap.com Thu Dec 13 18:21:20 2007 From: rstevens at internap.com (Rick Stevens) Date: Thu, 13 Dec 2007 10:21:20 -0800 Subject: Kernel remove via yum In-Reply-To: <1197537002.3848.30.camel@manhattan.ruffe.edu> References: <1197500931.3848.10.camel@manhattan.ruffe.edu> <20071212234054.GA21500@bobcat.bobcatos.com> <1197510238.29325.47.camel@prophead.corp.publichost.com> <1197537002.3848.30.camel@manhattan.ruffe.edu> Message-ID: <1197570080.29325.64.camel@prophead.corp.publichost.com> On Thu, 2007-12-13 at 04:10 -0500, mylar wrote: > On Wed, 2007-12-12 at 17:43 -0800, Rick Stevens wrote: > > On Wed, 2007-12-12 at 17:40 -0600, Bob McClure Jr wrote: > > > On Wed, Dec 12, 2007 at 06:08:51PM -0500, mylar wrote: > > > > Hello, > > > > > > > > Now that I have successfully upgraded my kernel via yum can I remove the > > > > old kernel via yum ? In other words can I simply do a > > > > > > > > "# yum remove "kernel-2.6-18" > > > > > > Yeah, I guess that will work. I just use rpm: > > > > > > rpm -e kernel-2.6-18 > > > > > > That said, I always keep the previous kernel around in case some > > > disaster strikes the new kernel, which, of course, hasn't happened, > > > ... yet. > > > > Heheheheheh! > > > > > > or are there any additional steps I need to take care to do ? > > > > Normally yum only keeps two versions of each kernel anyway. That's > > what the "tokeep=2" does in /etc/yum/pluginconf.d/installonlyn.conf. > > If you want to keep more, then change it to whatever you want. > > OK thanks... I didn't know that. For now I'll just leave it as is. > There's enough room and I don't mind keeping the old version around. 'Tis always a good thing to keep at least one old kernel around...just in case something evil happens. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - I doubt, therefore I might be. - ---------------------------------------------------------------------- From micros50 at verizon.net Fri Dec 14 11:11:19 2007 From: micros50 at verizon.net (mylar) Date: Fri, 14 Dec 2007 06:11:19 -0500 Subject: Help !! It's Baaack ! In-Reply-To: <1197509969.29325.42.camel@prophead.corp.publichost.com> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> Message-ID: <1197630679.3945.9.camel@manhattan.ruffe.edu> Hello. I retitled this email. Okay, the same problem that I described below is back again. It's really weird. It seems to be hit or miss. Sometimes when I boot the new kernel the display comes up normally and immediately. Other times I'll get the message, "Cannot display this video mode", which will hang for a few seconds then the screen will blink a couple of times and then the display will come up. other times it just sits there with the message "Cannot display this video mode" and does nothing. The only way out when it does that is just to hit the big switch on the front of the machine. However, when I boot the old kernel the display comes up each and every time with no problems. So for now I've gone back to using the old kernel. Any ideas. Where do I start debugging this thing ? Why would it work, then not work, intermittently like that. Its one of the strangest problems I've had in a looooong time. Any suggestions appreciated. Thanks John / mylar On Wed, 2007-12-12 at 17:39 -0800, Rick Stevens wrote: > On Wed, 2007-12-12 at 18:05 -0500, mylar wrote: > > Hello... Here's an update... > > > > It seems to be working now. After I installed the new kernel via yum I > > rebooted into the new kernel and I had the video display problem. So I > > shut down and rebooted the old kernel and everything was OK. After a few > > hours I shut down and left. When I got back a few hours later I booted > > the machine and decided to give another shot at trying to boot the new > > kernel. -- email-> micros50 at verizon.net "I Speak Mathematics" From rstevens at internap.com Fri Dec 14 19:30:15 2007 From: rstevens at internap.com (Rick Stevens) Date: Fri, 14 Dec 2007 11:30:15 -0800 Subject: Help !! It's Baaack ! In-Reply-To: <1197630679.3945.9.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> Message-ID: <1197660615.17461.18.camel@prophead.corp.publichost.com> On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > Hello. > > I retitled this email. Okay, the same problem that I described below is > back again. It's really weird. It seems to be hit or miss. Sometimes > when I boot the new kernel the display comes up normally and > immediately. Other times I'll get the message, "Cannot display this > video mode", which will hang for a few seconds then the screen will > blink a couple of times and then the display will come up. other times > it just sits there with the message "Cannot display this video mode" and > does nothing. The only way out when it does that is just to hit the big > switch on the front of the machine. > > However, when I boot the old kernel the display comes up each and every > time with no problems. So for now I've gone back to using the old > kernel. > > Any ideas. Where do I start debugging this thing ? Why would it work, > then not work, intermittently like that. Its one of the strangest > problems I've had in a looooong time. First off, what kind of video hardware is it? Which driver are you running? This sounds like the driver is misinterpreting the DRI data from the monitor on warm boots. > > Any suggestions appreciated. Thanks > > John / mylar > > > > On Wed, 2007-12-12 at 17:39 -0800, Rick Stevens wrote: > > On Wed, 2007-12-12 at 18:05 -0500, mylar wrote: > > > Hello... Here's an update... > > > > > > It seems to be working now. After I installed the new kernel via yum I > > > rebooted into the new kernel and I had the video display problem. So I > > > shut down and rebooted the old kernel and everything was OK. After a few > > > hours I shut down and left. When I got back a few hours later I booted > > > the machine and decided to give another shot at trying to boot the new > > > kernel. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - "I'd explain it to you, but your brain might explode." - ---------------------------------------------------------------------- From micros50 at verizon.net Sun Dec 16 11:30:18 2007 From: micros50 at verizon.net (mylar) Date: Sun, 16 Dec 2007 06:30:18 -0500 Subject: Help !! It's Baaack ! In-Reply-To: <1197660615.17461.18.camel@prophead.corp.publichost.com> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> Message-ID: <1197804618.17283.74.camel@manhattan.ruffe.edu> On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > Hello. > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > then not work, intermittently like that. Its one of the strangest > > problems I've had in a looooong time. > > First off, what kind of video hardware is it? Which driver are you > running? This sounds like the driver is misinterpreting the DRI data > from the monitor on warm boots. > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video adapter. The video card is an Intel 82865G Integrated Graphics Controller and the monitor is a Dell E172FP flap panel LCD display. The driver is the i810 driver which is the one I was told to use and, the only one which seems to work. I'm running at a screen resolution of 1280x1024 which I have been using on this machine for several years. I had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. To make things confusing (at least for me) it sometimes the display comes up fine. Other times it will flicker a few times then come up fine. other times it sits there like stone and does nothing till I hit the big switch. Oh, one other thing. It also happens on cold boots too. This morning I booted the machine cold and it happened. I had to reboot to the old kernel. Lastly, I can find nothing in the systems logs or anywhere else that might indicate where the glitch is occurring. It's strange. mylar -- email-> micros50 at verizon.net "I Speak Mathematics" From bret_stern at machinemanagement.com Mon Dec 17 16:50:51 2007 From: bret_stern at machinemanagement.com (Bret Stern) Date: Mon, 17 Dec 2007 08:50:51 -0800 Subject: upload speeds - ftp Message-ID: <000001c840cc$fbf25d50$0200a8c0@mmbret> Does anybody have any tips for increasing upload speeds? Perhaps sending the file a different way. I periodically send a zipped 500mb file to my ftp host. (data sent to my server from a dsl client/customer) I have Comcast cable, and host an ftp server on my network. The host is behind an inexpensive router, which is port forwarded to my ftp host. The ftp host is a Dell 2450 with dual 1.2 processors, 2-gb ram routed through a Cisco 2900XL 10/100 switch. I'm getting about 38 - 40 kb upload speed to my host. B Stern From darren at marvellousmobile.com Mon Dec 17 16:57:17 2007 From: darren at marvellousmobile.com (Darren Nye) Date: Mon, 17 Dec 2007 16:57:17 -0000 Subject: upload speeds - ftp In-Reply-To: <000001c840cc$fbf25d50$0200a8c0@mmbret> Message-ID: <20071217165714.72C0245EF7F@smtp-out-68.livemail.co.uk> Use a different compression algorithm to reduce the file size further, .rar or .ace for example... Darren Nye, Marvellous. 56a Poland Street, London W1F 7NN. +44 (0)7748 802340 | marvellousmobile.com -----Original Message----- From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-list-bounces at redhat.com] On Behalf Of Bret Stern Sent: 17 December 2007 16:51 To: redhat-install-list at redhat.com Subject: upload speeds - ftp Does anybody have any tips for increasing upload speeds? Perhaps sending the file a different way. I periodically send a zipped 500mb file to my ftp host. (data sent to my server from a dsl client/customer) I have Comcast cable, and host an ftp server on my network. The host is behind an inexpensive router, which is port forwarded to my ftp host. The ftp host is a Dell 2450 with dual 1.2 processors, 2-gb ram routed through a Cisco 2900XL 10/100 switch. I'm getting about 38 - 40 kb upload speed to my host. B Stern _______________________________________________ Redhat-install-list mailing list Redhat-install-list at redhat.com https://www.redhat.com/mailman/listinfo/redhat-install-list To Unsubscribe Go To ABOVE URL or send a message to: redhat-install-list-request at redhat.com Subject: unsubscribe -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.17.4/1187 - Release Date: 16/12/2007 11:36 From harold at hallikainen.com Mon Dec 17 17:45:38 2007 From: harold at hallikainen.com (Harold Hallikainen) Date: Mon, 17 Dec 2007 09:45:38 -0800 (PST) Subject: upload speeds - ftp In-Reply-To: <000001c840cc$fbf25d50$0200a8c0@mmbret> References: <000001c840cc$fbf25d50$0200a8c0@mmbret> Message-ID: <3920.71.93.35.174.1197913538.squirrel@sujan.hallikainen.org> > > Does anybody have any tips for increasing upload > speeds? > > Perhaps sending the file a different way. > > I periodically send a zipped 500mb file to my ftp host. > (data sent to my server from a dsl client/customer) > > I have Comcast cable, and host an ftp server on my > network. The host is behind an inexpensive router, > which is port forwarded to my ftp host. > > The ftp host is a Dell 2450 with dual 1.2 processors, > 2-gb ram routed through a Cisco 2900XL 10/100 switch. > > I'm getting about 38 - 40 kb upload speed to my > host. > > B Stern Cable and DSL are, of course, asymmetric. They assume you will download more than you upload. Cable is ESPECIALLY asymmetric since they have a small return channel. From what I read, though, on the FTP server end, the transfer is a download through a cable modem. That should be pretty quick. On the FTP client end, it's an upload through DSL. I'd expect them to be able to do 128kbps upload, so your 30 to 40 kbps sounds a bit short. It would be interesting for you to try it from somewhere else to see which end has the problem. Good luck! Harold -- FCC Rules Updated Daily at http://www.hallikainen.com - Advertising opportunities available! From rstevens at internap.com Mon Dec 17 18:31:40 2007 From: rstevens at internap.com (Rick Stevens) Date: Mon, 17 Dec 2007 10:31:40 -0800 Subject: Help !! It's Baaack ! In-Reply-To: <1197804618.17283.74.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> <1197804618.17283.74.camel@manhattan.ruffe.edu> Message-ID: <1197916300.28891.7.camel@prophead.corp.publichost.com> On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > Hello. > > > > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > > then not work, intermittently like that. Its one of the strangest > > > problems I've had in a looooong time. > > > > First off, what kind of video hardware is it? Which driver are you > > running? This sounds like the driver is misinterpreting the DRI data > > from the monitor on warm boots. > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video > adapter. The video card is an Intel 82865G Integrated Graphics > Controller and the monitor is a Dell E172FP flap panel LCD display. The > driver is the i810 driver which is the one I was told to use and, the > only one which seems to work. I'm running at a screen resolution of > 1280x1024 which I have been using on this machine for several years. I > had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. > > To make things confusing (at least for me) it sometimes the display > comes up fine. Other times it will flicker a few times then come up > fine. other times it sits there like stone and does nothing till I hit > the big switch. > > Oh, one other thing. It also happens on cold boots too. This morning I > booted the machine cold and it happened. I had to reboot to the old > kernel. > > Lastly, I can find nothing in the systems logs or anywhere else that > might indicate where the glitch is occurring. It's strange. I've run into a similar thing myself. On occasion after the screen saver blanks the screen (this is on an nVidia with a Viewsonic display), the display wakes up but it's torn and unreadable. A quick "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back to GUI) cures it. I've not found a permanent fix. It seems that the DRI/DRM stuff isn't sticking so the horizontal and vertical refresh aren't sent properly when the screen wakes up and my weird key sequence above causes a reset. This smells like something that should be sent to bugzilla. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - "People tell me I look at the dark side. That's not true. I have - - the heart of a small boy......in a jar right here on my desk." - - -- Stephen King - ---------------------------------------------------------------------- From tpotter at techmarin.com Mon Dec 17 19:05:02 2007 From: tpotter at techmarin.com (Ted Potter) Date: Mon, 17 Dec 2007 11:05:02 -0800 Subject: upload speeds - ftp In-Reply-To: <000001c840cc$fbf25d50$0200a8c0@mmbret> References: <000001c840cc$fbf25d50$0200a8c0@mmbret> Message-ID: <5ce05200712171105s43cad18fif5e523c28b80b9df@mail.gmail.com> best speed I have ever seen from comcast is 15mg download and 1.5mg upload. Now that might work. Might ask if they offer a business class service, comcast does here. I would store large files on my ISP server and let others download from there. Not a real fix since you still are throttled getting the file up, but once there it works. Broadband in the US ? not unless you pay for it. On 12/17/07, Bret Stern wrote: > > > Does anybody have any tips for increasing upload > speeds? > > Perhaps sending the file a different way. > > I periodically send a zipped 500mb file to my ftp host. > (data sent to my server from a dsl client/customer) > > I have Comcast cable, and host an ftp server on my > network. The host is behind an inexpensive router, > which is port forwarded to my ftp host. > > The ftp host is a Dell 2450 with dual 1.2 processors, > 2-gb ram routed through a Cisco 2900XL 10/100 switch. > > I'm getting about 38 - 40 kb upload speed to my > host. > > B Stern > > _______________________________________________ > Redhat-install-list mailing list > Redhat-install-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-install-list > To Unsubscribe Go To ABOVE URL or send a message to: > redhat-install-list-request at redhat.com > Subject: unsubscribe > -- Ted Potter tpotter at techmarin.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bc98kinney at yahoo.com Wed Dec 19 05:17:03 2007 From: bc98kinney at yahoo.com (Bob Kinney) Date: Tue, 18 Dec 2007 21:17:03 -0800 (PST) Subject: upload speeds - ftp In-Reply-To: <000001c840cc$fbf25d50$0200a8c0@mmbret> Message-ID: <438467.32039.qm@web30702.mail.mud.yahoo.com> --- Bret Stern wrote: > > Does anybody have any tips for increasing upload > speeds? > > Perhaps sending the file a different way. > > I periodically send a zipped 500mb file to my ftp host. > (data sent to my server from a dsl client/customer) > > I have Comcast cable, and host an ftp server on my > network. The host is behind an inexpensive router, > which is port forwarded to my ftp host. > > The ftp host is a Dell 2450 with dual 1.2 processors, > 2-gb ram routed through a Cisco 2900XL 10/100 switch. > > I'm getting about 38 - 40 kb upload speed to my > host. > > B Stern > > Is that Kb or KB per second? If it's the latter, that would put you at around 320 Kbits / second, which is where my service gets throttled. You might get a bit more for the first few megabytes (if your service has the speedboost feature) before the vise clamps down. --bc ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From bc98kinney at yahoo.com Wed Dec 19 05:20:06 2007 From: bc98kinney at yahoo.com (Bob Kinney) Date: Tue, 18 Dec 2007 21:20:06 -0800 (PST) Subject: Fwd: Re: upload speeds - ftp Message-ID: <910626.59933.qm@web30713.mail.mud.yahoo.com> Oops, the reply-address was set to the poster... > --- Bret Stern wrote: > > > > > Does anybody have any tips for increasing upload > > speeds? > > > > Perhaps sending the file a different way. > > > > I periodically send a zipped 500mb file to my ftp host. > > (data sent to my server from a dsl client/customer) > > > > I have Comcast cable, and host an ftp server on my > > network. The host is behind an inexpensive router, > > which is port forwarded to my ftp host. > > > > The ftp host is a Dell 2450 with dual 1.2 processors, > > 2-gb ram routed through a Cisco 2900XL 10/100 switch. > > > > I'm getting about 38 - 40 kb upload speed to my > > host. > > > > B Stern > > > > > Is that Kb or KB per second? If it's the latter, that would put you at around 320 Kbits / second, which is where my service gets throttled. You might get a bit more for the first few megabytes (if your service has the speedboost feature) before the vise clamps down. --bc ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping From micros50 at verizon.net Wed Dec 19 11:01:25 2007 From: micros50 at verizon.net (mylar) Date: Wed, 19 Dec 2007 06:01:25 -0500 Subject: Help !! It's Baaack ! In-Reply-To: <1197916300.28891.7.camel@prophead.corp.publichost.com> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> <1197804618.17283.74.camel@manhattan.ruffe.edu> <1197916300.28891.7.camel@prophead.corp.publichost.com> Message-ID: <1198062085.15489.9.camel@manhattan.ruffe.edu> On Mon, 2007-12-17 at 10:31 -0800, Rick Stevens wrote: > On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > > Hello. > > > > > > > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > > > then not work, intermittently like that. Its one of the strangest > > > > problems I've had in a looooong time. > > > > > > First off, what kind of video hardware is it? Which driver are you > > > running? This sounds like the driver is misinterpreting the DRI data > > > from the monitor on warm boots. > > > > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video > > adapter. The video card is an Intel 82865G Integrated Graphics > > Controller and the monitor is a Dell E172FP flap panel LCD display. The > > driver is the i810 driver which is the one I was told to use and, the > > only one which seems to work. I'm running at a screen resolution of > > 1280x1024 which I have been using on this machine for several years. I > > had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 > > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. > > > > To make things confusing (at least for me) it sometimes the display > > comes up fine. Other times it will flicker a few times then come up > > fine. other times it sits there like stone and does nothing till I hit > > the big switch. > > > > Oh, one other thing. It also happens on cold boots too. This morning I > > booted the machine cold and it happened. I had to reboot to the old > > kernel. > > > > Lastly, I can find nothing in the systems logs or anywhere else that > > might indicate where the glitch is occurring. It's strange. > > I've run into a similar thing myself. On occasion after the screen > saver blanks the screen (this is on an nVidia with a Viewsonic display), > the display wakes up but it's torn and unreadable. A quick > "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back to > GUI) cures it. I've not found a permanent fix. > > It seems that the DRI/DRM stuff isn't sticking so the horizontal and > vertical refresh aren't sent properly when the screen wakes up and my > weird key sequence above causes a reset. This smells like something > that should be sent to bugzilla. > I may have found a temporary fix. I lowered the default screen resolution as root and thus far it has booted up with no problems two or three times in a row. However, when i log in and operate under X under my regular non-root account it seems to run fine under the higher 1280x1024 screen resolution that I normally like to use. I googled around a bit to see what I could find about this problem. it seems that I am not alone. Others have reported similar problems. seems something got broke between kernel updates with respect to the i810 driver. I hate it when updates break stuff that has previously worked but that's the nature of the beast. I never submitted a bug report to bugzilla. Is that a relatively painless process ? It would be great if this problem could be patched soon. John / mylar -- email-> micros50 at verizon.net "I Speak Mathematics" From dsrinivasmail at gmail.com Wed Dec 19 13:34:55 2007 From: dsrinivasmail at gmail.com (dabburu srinivas) Date: Wed, 19 Dec 2007 19:04:55 +0530 Subject: how to create driver disk Message-ID: <46c20eef0712190534l3386fc4erc8267e43544d6e1d@mail.gmail.com> Can you please forward how to create linux driver disk, whereby one can use while installing rhel at boot option. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstevens at internap.com Wed Dec 19 17:38:28 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 19 Dec 2007 09:38:28 -0800 Subject: Help !! It's Baaack ! In-Reply-To: <1198062085.15489.9.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> <1197804618.17283.74.camel@manhattan.ruffe.edu> <1197916300.28891.7.camel@prophead.corp.publichost.com> <1198062085.15489.9.camel@manhattan.ruffe.edu> Message-ID: <1198085908.27884.14.camel@prophead.corp.publichost.com> On Wed, 2007-12-19 at 06:01 -0500, mylar wrote: > On Mon, 2007-12-17 at 10:31 -0800, Rick Stevens wrote: > > On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > > > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > > > Hello. > > > > > > > > > > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > > > > then not work, intermittently like that. Its one of the strangest > > > > > problems I've had in a looooong time. > > > > > > > > First off, what kind of video hardware is it? Which driver are you > > > > running? This sounds like the driver is misinterpreting the DRI data > > > > from the monitor on warm boots. > > > > > > > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video > > > adapter. The video card is an Intel 82865G Integrated Graphics > > > Controller and the monitor is a Dell E172FP flap panel LCD display. The > > > driver is the i810 driver which is the one I was told to use and, the > > > only one which seems to work. I'm running at a screen resolution of > > > 1280x1024 which I have been using on this machine for several years. I > > > had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 > > > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. > > > > > > To make things confusing (at least for me) it sometimes the display > > > comes up fine. Other times it will flicker a few times then come up > > > fine. other times it sits there like stone and does nothing till I hit > > > the big switch. > > > > > > Oh, one other thing. It also happens on cold boots too. This morning I > > > booted the machine cold and it happened. I had to reboot to the old > > > kernel. > > > > > > Lastly, I can find nothing in the systems logs or anywhere else that > > > might indicate where the glitch is occurring. It's strange. > > > > I've run into a similar thing myself. On occasion after the screen > > saver blanks the screen (this is on an nVidia with a Viewsonic display), > > the display wakes up but it's torn and unreadable. A quick > > "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back to > > GUI) cures it. I've not found a permanent fix. > > > > It seems that the DRI/DRM stuff isn't sticking so the horizontal and > > vertical refresh aren't sent properly when the screen wakes up and my > > weird key sequence above causes a reset. This smells like something > > that should be sent to bugzilla. > > > > I may have found a temporary fix. I lowered the default screen > resolution as root and thus far it has booted up with no problems two or > three times in a row. However, when i log in and operate under X under > my regular non-root account it seems to run fine under the higher > 1280x1024 screen resolution that I normally like to use. > > I googled around a bit to see what I could find about this problem. it > seems that I am not alone. Others have reported similar problems. seems > something got broke between kernel updates with respect to the i810 > driver. I hate it when updates break stuff that has previously worked > but that's the nature of the beast. I kinda suspected it was something like that. > I never submitted a bug report to bugzilla. Is that a relatively > painless process ? It would be great if this problem could be patched > soon. First, go to https://bugzilla.redhat.com and create an account (don't worry, it's free) and log in. Select "New" in the grey menu bar below the red one at the top. In the next screen, select a product and you'll be taken to the appropriate screen. The items labeled in blue should be filled in as best you can. When you're done, click on the "Commit" button at the bottom of the page. Pretty simple. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Change is inevitable, except from a vending machine. - ---------------------------------------------------------------------- From rstevens at internap.com Wed Dec 19 17:44:48 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 19 Dec 2007 09:44:48 -0800 Subject: how to create driver disk In-Reply-To: <46c20eef0712190534l3386fc4erc8267e43544d6e1d@mail.gmail.com> References: <46c20eef0712190534l3386fc4erc8267e43544d6e1d@mail.gmail.com> Message-ID: <1198086288.27884.19.camel@prophead.corp.publichost.com> On Wed, 2007-12-19 at 19:04 +0530, dabburu srinivas wrote: > Can you please forward how to create linux driver disk, whereby one > can use while installing rhel at boot option. A google search for "redhat driver disk" would point you in the right direction, but Doug Ledford's page is probably the best: http://people.redhat.com/dledford/ Download the driver disk development kit: http://people.redhat.com/dledford/mod_devel_kit.tgz Untar it and use it. Make sure you read the README files before you do anything. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Denial. It ain't just a river in Egypt anymore! - ---------------------------------------------------------------------- From rstevens at internap.com Wed Dec 19 17:45:28 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 19 Dec 2007 09:45:28 -0800 Subject: Fwd: Re: upload speeds - ftp In-Reply-To: <910626.59933.qm@web30713.mail.mud.yahoo.com> References: <910626.59933.qm@web30713.mail.mud.yahoo.com> Message-ID: <1198086328.27884.21.camel@prophead.corp.publichost.com> On Tue, 2007-12-18 at 21:20 -0800, Bob Kinney wrote: > Oops, the reply-address was set to the poster... That may be, but it showed up on the list anyway. :-) > > > > --- Bret Stern wrote: > > > > > > > > Does anybody have any tips for increasing upload > > > speeds? > > > > > > Perhaps sending the file a different way. > > > > > > I periodically send a zipped 500mb file to my ftp host. > > > (data sent to my server from a dsl client/customer) > > > > > > I have Comcast cable, and host an ftp server on my > > > network. The host is behind an inexpensive router, > > > which is port forwarded to my ftp host. > > > > > > The ftp host is a Dell 2450 with dual 1.2 processors, > > > 2-gb ram routed through a Cisco 2900XL 10/100 switch. > > > > > > I'm getting about 38 - 40 kb upload speed to my > > > host. > > > > > > B Stern > > > > > > > > > > > Is that Kb or KB per second? > > If it's the latter, that would put you at around 320 Kbits / second, > which is where my service gets throttled. > > You might get a bit more for the first few megabytes (if your service > has the speedboost feature) before the vise clamps down. > > --bc > > > > > ____________________________________________________________________________________ > Looking for last minute shopping deals? > Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping > > _______________________________________________ > Redhat-install-list mailing list > Redhat-install-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-install-list > To Unsubscribe Go To ABOVE URL or send a message to: > redhat-install-list-request at redhat.com > Subject: unsubscribe ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - The Theory of Rapitivity: E=MC Hammer - - -- Glenn Marcus (via TopFive.com) - ---------------------------------------------------------------------- From micros50 at verizon.net Fri Dec 21 04:52:45 2007 From: micros50 at verizon.net (Micros50) Date: Thu, 20 Dec 2007 23:52:45 -0500 Subject: Help !! It's Baaack ! In-Reply-To: <1198085908.27884.14.camel@prophead.corp.publichost.com> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> <1197804618.17283.74.camel@manhattan.ruffe.edu> <1197916300.28891.7.camel@prophead.corp.publichost.com> <1198062085.15489.9.camel@manhattan.ruffe.edu> <1198085908.27884.14.camel@prophead.corp.publichost.com> Message-ID: <1198212765.4001.53.camel@manhattan.ruffe.edu> On Wed, 2007-12-19 at 09:38 -0800, Rick Stevens wrote: > On Wed, 2007-12-19 at 06:01 -0500, mylar wrote: > > On Mon, 2007-12-17 at 10:31 -0800, Rick Stevens wrote: > > > On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > > > > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > > > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > > > > Hello. > > > > > > > > > > > > > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > > > > > then not work, intermittently like that. Its one of the strangest > > > > > > problems I've had in a looooong time. > > > > > > > > > > First off, what kind of video hardware is it? Which driver are you > > > > > running? This sounds like the driver is misinterpreting the DRI data > > > > > from the monitor on warm boots. > > > > > > > > > > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video > > > > adapter. The video card is an Intel 82865G Integrated Graphics > > > > Controller and the monitor is a Dell E172FP flap panel LCD display. The > > > > driver is the i810 driver which is the one I was told to use and, the > > > > only one which seems to work. I'm running at a screen resolution of > > > > 1280x1024 which I have been using on this machine for several years. I > > > > had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 > > > > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. > > > > > > > > To make things confusing (at least for me) it sometimes the display > > > > comes up fine. Other times it will flicker a few times then come up > > > > fine. other times it sits there like stone and does nothing till I hit > > > > the big switch. > > > > > > > > Oh, one other thing. It also happens on cold boots too. This morning I > > > > booted the machine cold and it happened. I had to reboot to the old > > > > kernel. > > > > > > > > Lastly, I can find nothing in the systems logs or anywhere else that > > > > might indicate where the glitch is occurring. It's strange. > > > > > > I've run into a similar thing myself. On occasion after the screen > > > saver blanks the screen (this is on an nVidia with a Viewsonic display), > > > the display wakes up but it's torn and unreadable. A quick > > > "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back to > > > GUI) cures it. I've not found a permanent fix. > > > > > > It seems that the DRI/DRM stuff isn't sticking so the horizontal and > > > vertical refresh aren't sent properly when the screen wakes up and my > > > weird key sequence above causes a reset. This smells like something > > > that should be sent to bugzilla. > > > > > > > I may have found a temporary fix. I lowered the default screen > > resolution as root and thus far it has booted up with no problems two or > > three times in a row. However, when i log in and operate under X under > > my regular non-root account it seems to run fine under the higher > > 1280x1024 screen resolution that I normally like to use. > > > > I googled around a bit to see what I could find about this problem. it > > seems that I am not alone. Others have reported similar problems. seems > > something got broke between kernel updates with respect to the i810 > > driver. I hate it when updates break stuff that has previously worked > > but that's the nature of the beast. > > I kinda suspected it was something like that. > > > I never submitted a bug report to bugzilla. Is that a relatively > > painless process ? It would be great if this problem could be patched > > soon. > > First, go to https://bugzilla.redhat.com and create an account (don't > worry, it's free) and log in. Select "New" in the grey menu bar below > the red one at the top. In the next screen, select a product and you'll > be taken to the appropriate screen. The items labeled in blue should be > filled in as best you can. When you're done, click on the "Commit" > button at the bottom of the page. > > Pretty simple. Thanks for the help. For the time being I seem to have found a temporary workaround as I described in a prior email. Thus far I've booted this machine several times into the new kernel and it hasn't hung with a blank screen. Meanwhile I'll file a bugzilla report. Hopefully this problem will be fixed in future kernel updates. This new kernel fixes a few other annoying problems I was having with the old kernel. Glad I can use it now. Now I've got to check another (different) machine. Seems the kernel I updated on that one is causing strange system hangups.That's the way it goes I suppose. Fix one break another :) In the event I don't write to the list till next year Happy Holidays John / (mylar) From rstevens at internap.com Fri Dec 21 18:53:33 2007 From: rstevens at internap.com (Rick Stevens) Date: Fri, 21 Dec 2007 10:53:33 -0800 Subject: Help !! It's Baaack ! In-Reply-To: <1198212765.4001.53.camel@manhattan.ruffe.edu> References: <1197489196.4923.13.camel@manhattan.ruffe.edu> <1197500740.3848.5.camel@manhattan.ruffe.edu> <1197509969.29325.42.camel@prophead.corp.publichost.com> <1197630679.3945.9.camel@manhattan.ruffe.edu> <1197660615.17461.18.camel@prophead.corp.publichost.com> <1197804618.17283.74.camel@manhattan.ruffe.edu> <1197916300.28891.7.camel@prophead.corp.publichost.com> <1198062085.15489.9.camel@manhattan.ruffe.edu> <1198085908.27884.14.camel@prophead.corp.publichost.com> <1198212765.4001.53.camel@manhattan.ruffe.edu> Message-ID: <1198263213.20350.65.camel@prophead.corp.publichost.com> On Thu, 2007-12-20 at 23:52 -0500, Micros50 wrote: > On Wed, 2007-12-19 at 09:38 -0800, Rick Stevens wrote: > > On Wed, 2007-12-19 at 06:01 -0500, mylar wrote: > > > On Mon, 2007-12-17 at 10:31 -0800, Rick Stevens wrote: > > > > On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > > > > > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > > > > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > > > > > Hello. > > > > > > > > > > > > > > > > > > > Any ideas. Where do I start debugging this thing ? Why would it work, > > > > > > > then not work, intermittently like that. Its one of the strangest > > > > > > > problems I've had in a looooong time. > > > > > > > > > > > > First off, what kind of video hardware is it? Which driver are you > > > > > > running? This sounds like the driver is misinterpreting the DRI data > > > > > > from the monitor on warm boots. > > > > > > > > > > > > > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board video > > > > > adapter. The video card is an Intel 82865G Integrated Graphics > > > > > Controller and the monitor is a Dell E172FP flap panel LCD display. The > > > > > driver is the i810 driver which is the one I was told to use and, the > > > > > only one which seems to work. I'm running at a screen resolution of > > > > > 1280x1024 which I have been using on this machine for several years. I > > > > > had no problem with Fedora 1, not with Fedora 7 while running the 2.6.18 > > > > > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem began. > > > > > > > > > > To make things confusing (at least for me) it sometimes the display > > > > > comes up fine. Other times it will flicker a few times then come up > > > > > fine. other times it sits there like stone and does nothing till I hit > > > > > the big switch. > > > > > > > > > > Oh, one other thing. It also happens on cold boots too. This morning I > > > > > booted the machine cold and it happened. I had to reboot to the old > > > > > kernel. > > > > > > > > > > Lastly, I can find nothing in the systems logs or anywhere else that > > > > > might indicate where the glitch is occurring. It's strange. > > > > > > > > I've run into a similar thing myself. On occasion after the screen > > > > saver blanks the screen (this is on an nVidia with a Viewsonic display), > > > > the display wakes up but it's torn and unreadable. A quick > > > > "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back to > > > > GUI) cures it. I've not found a permanent fix. > > > > > > > > It seems that the DRI/DRM stuff isn't sticking so the horizontal and > > > > vertical refresh aren't sent properly when the screen wakes up and my > > > > weird key sequence above causes a reset. This smells like something > > > > that should be sent to bugzilla. > > > > > > > > > > I may have found a temporary fix. I lowered the default screen > > > resolution as root and thus far it has booted up with no problems two or > > > three times in a row. However, when i log in and operate under X under > > > my regular non-root account it seems to run fine under the higher > > > 1280x1024 screen resolution that I normally like to use. > > > > > > I googled around a bit to see what I could find about this problem. it > > > seems that I am not alone. Others have reported similar problems. seems > > > something got broke between kernel updates with respect to the i810 > > > driver. I hate it when updates break stuff that has previously worked > > > but that's the nature of the beast. > > > > I kinda suspected it was something like that. > > > > > I never submitted a bug report to bugzilla. Is that a relatively > > > painless process ? It would be great if this problem could be patched > > > soon. > > > > First, go to https://bugzilla.redhat.com and create an account (don't > > worry, it's free) and log in. Select "New" in the grey menu bar below > > the red one at the top. In the next screen, select a product and you'll > > be taken to the appropriate screen. The items labeled in blue should be > > filled in as best you can. When you're done, click on the "Commit" > > button at the bottom of the page. > > > > Pretty simple. > > Thanks for the help. For the time being I seem to have found a temporary > workaround as I described in a prior email. Thus far I've booted this > machine several times into the new kernel and it hasn't hung with a > blank screen. Meanwhile I'll file a bugzilla report. Hopefully this > problem will be fixed in future kernel updates. This new kernel fixes a > few other annoying problems I was having with the old kernel. Glad I can > use it now. It may be a gnome or kde setting that's freaking it out, since it seems to work with regular accounts but not root. > Now I've got to check another (different) machine. Seems the kernel I > updated on that one is causing strange system hangups.That's the way it > goes I suppose. Fix one break another :) Welcome to my world. I have about 5,000 machines I have to ride herd on--a mix of Red Hat, CentOS, Fedora, Ubuntu and SuSE machines. Ye gods! > In the event I don't write to the list till next year Happy Holidays The same to you, John! ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - We have enough youth, how about a fountain of SMART? - ---------------------------------------------------------------------- From sam.peng at foxconn.com Sat Dec 22 07:02:03 2007 From: sam.peng at foxconn.com (sam.peng at foxconn.com) Date: Sat, 22 Dec 2007 01:02:03 -0600 Subject: Sam Peng/USA/FOXCONN is out of the office. Message-ID: I will be out of the office starting 12/18/2007 and will not return until 01/04/2008. I will be out of office during 12/19 to 1/4. I may not access my mail. If there is any production support need, please contact my back up Joel Camargo( Joel.camargo at foxconn.com ) and Leila Marques( leila.marques at foxconn.com ). Regards, Sam Peng Foxconn CMMSG NA IT - Fullerton, CA US Office# 17145253688*8124 , VoIP# 520-8124 US Mobile# 17148634015 IM: sjpeng at hotmail.com From khurshedkhan at gmail.com Mon Dec 24 03:11:00 2007 From: khurshedkhan at gmail.com (khurshed khan) Date: Mon, 24 Dec 2007 08:41:00 +0530 Subject: Redhat-install-list Digest, Vol 46, Issue 13 In-Reply-To: <20071222170027.093F372F31@hormel.redhat.com> References: <20071222170027.093F372F31@hormel.redhat.com> Message-ID: dear, hi pls send red hat cd on this address: KHURSHED AHMED, 301, KM BOARDING, STATION MASJID , KADAK BAZAAR, SAYAIGANJ, VADODARA-390001 MOB:- +91 9898305662 THANKS KHURSHED AHMED +91 9898305662 On 12/22/07, redhat-install-list-request at redhat.com < redhat-install-list-request at redhat.com> wrote: > > Send Redhat-install-list mailing list submissions to > redhat-install-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/redhat-install-list > or, via email, send a message with subject or body 'help' to > redhat-install-list-request at redhat.com > > You can reach the person managing the list at > redhat-install-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Redhat-install-list digest..." > > > Today's Topics: > > 1. Re: Help !! It's Baaack ! (Rick Stevens) > 2. Sam Peng/USA/FOXCONN is out of the office. (sam.peng at foxconn.com) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 21 Dec 2007 10:53:33 -0800 > From: Rick Stevens > Subject: Re: Help !! It's Baaack ! > To: Getting started with Red Hat Linux > > Message-ID: <1198263213.20350.65.camel at prophead.corp.publichost.com> > Content-Type: text/plain > > On Thu, 2007-12-20 at 23:52 -0500, Micros50 wrote: > > On Wed, 2007-12-19 at 09:38 -0800, Rick Stevens wrote: > > > On Wed, 2007-12-19 at 06:01 -0500, mylar wrote: > > > > On Mon, 2007-12-17 at 10:31 -0800, Rick Stevens wrote: > > > > > On Sun, 2007-12-16 at 06:30 -0500, mylar wrote: > > > > > > On Fri, 2007-12-14 at 11:30 -0800, Rick Stevens wrote: > > > > > > > On Fri, 2007-12-14 at 06:11 -0500, mylar wrote: > > > > > > > > Hello. > > > > > > > > > > > > > > > > > > > > > > Any ideas. Where do I start debugging this thing ? Why would > it work, > > > > > > > > then not work, intermittently like that. Its one of the > strangest > > > > > > > > problems I've had in a looooong time. > > > > > > > > > > > > > > First off, what kind of video hardware is it? Which driver > are you > > > > > > > running? This sounds like the driver is misinterpreting the > DRI data > > > > > > > from the monitor on warm boots. > > > > > > > > > > > > > > > > > > > Okay, the machine is 2.8 Ghz Dell 4600 running an Intel on board > video > > > > > > adapter. The video card is an Intel 82865G Integrated Graphics > > > > > > Controller and the monitor is a Dell E172FP flap panel LCD > display. The > > > > > > driver is the i810 driver which is the one I was told to use > and, the > > > > > > only one which seems to work. I'm running at a screen resolution > of > > > > > > 1280x1024 which I have been using on this machine for several > years. I > > > > > > had no problem with Fedora 1, not with Fedora 7 while running > the 2.6.18 > > > > > > XEN kernel. As soon as I upgraded to 2.6.20 whammo, the problem > began. > > > > > > > > > > > > To make things confusing (at least for me) it sometimes the > display > > > > > > comes up fine. Other times it will flicker a few times then come > up > > > > > > fine. other times it sits there like stone and does nothing till > I hit > > > > > > the big switch. > > > > > > > > > > > > Oh, one other thing. It also happens on cold boots too. This > morning I > > > > > > booted the machine cold and it happened. I had to reboot to the > old > > > > > > kernel. > > > > > > > > > > > > Lastly, I can find nothing in the systems logs or anywhere else > that > > > > > > might indicate where the glitch is occurring. It's strange. > > > > > > > > > > I've run into a similar thing myself. On occasion after the > screen > > > > > saver blanks the screen (this is on an nVidia with a Viewsonic > display), > > > > > the display wakes up but it's torn and unreadable. A quick > > > > > "CTRL-ALT-F1" followed by an "ALT-F7" (go to text console and back > to > > > > > GUI) cures it. I've not found a permanent fix. > > > > > > > > > > It seems that the DRI/DRM stuff isn't sticking so the horizontal > and > > > > > vertical refresh aren't sent properly when the screen wakes up and > my > > > > > weird key sequence above causes a reset. This smells like > something > > > > > that should be sent to bugzilla. > > > > > > > > > > > > > I may have found a temporary fix. I lowered the default screen > > > > resolution as root and thus far it has booted up with no problems > two or > > > > three times in a row. However, when i log in and operate under X > under > > > > my regular non-root account it seems to run fine under the higher > > > > 1280x1024 screen resolution that I normally like to use. > > > > > > > > I googled around a bit to see what I could find about this problem. > it > > > > seems that I am not alone. Others have reported similar problems. > seems > > > > something got broke between kernel updates with respect to the i810 > > > > driver. I hate it when updates break stuff that has previously > worked > > > > but that's the nature of the beast. > > > > > > I kinda suspected it was something like that. > > > > > > > I never submitted a bug report to bugzilla. Is that a relatively > > > > painless process ? It would be great if this problem could be > patched > > > > soon. > > > > > > First, go to https://bugzilla.redhat.com and create an account (don't > > > worry, it's free) and log in. Select "New" in the grey menu bar below > > > the red one at the top. In the next screen, select a product and > you'll > > > be taken to the appropriate screen. The items labeled in blue should > be > > > filled in as best you can. When you're done, click on the "Commit" > > > button at the bottom of the page. > > > > > > Pretty simple. > > > > Thanks for the help. For the time being I seem to have found a temporary > > workaround as I described in a prior email. Thus far I've booted this > > machine several times into the new kernel and it hasn't hung with a > > blank screen. Meanwhile I'll file a bugzilla report. Hopefully this > > problem will be fixed in future kernel updates. This new kernel fixes a > > few other annoying problems I was having with the old kernel. Glad I can > > use it now. > > It may be a gnome or kde setting that's freaking it out, since it seems > to work with regular accounts but not root. > > > Now I've got to check another (different) machine. Seems the kernel I > > updated on that one is causing strange system hangups.That's the way it > > goes I suppose. Fix one break another :) > > Welcome to my world. I have about 5,000 machines I have to ride herd > on--a mix of Red Hat, CentOS, Fedora, Ubuntu and SuSE machines. Ye > gods! > > > In the event I don't write to the list till next year Happy Holidays > > The same to you, John! > > ---------------------------------------------------------------------- > - Rick Stevens, Principal Engineer rstevens at internap.com - > - CDN Systems, Internap, Inc. http://www.internap.com - > - - > - We have enough youth, how about a fountain of SMART? - > ---------------------------------------------------------------------- > > > > ------------------------------ > > Message: 2 > Date: Sat, 22 Dec 2007 01:02:03 -0600 > From: sam.peng at foxconn.com > Subject: Sam Peng/USA/FOXCONN is out of the office. > To: redhat-install-list at redhat.com > Message-ID: > < > OF6E3E530F.23CF4590-ON862573B9.0026A3E9-862573B9.0026A3EA at houston.foxconn.com > > > > Content-Type: text/plain; charset=us-ascii > > I will be out of the office starting 12/18/2007 and will not return until > 01/04/2008. > > I will be out of office during 12/19 to 1/4. I may not access my mail. If > there is any production support need, please contact my back up Joel > Camargo( Joel.camargo at foxconn.com ) and Leila Marques( > leila.marques at foxconn.com ). > > > Regards, > Sam Peng > > Foxconn CMMSG NA IT - Fullerton, CA > US Office# 17145253688*8124 , VoIP# 520-8124 > US Mobile# 17148634015 > IM: sjpeng at hotmail.com > > > > > > > > > > > ------------------------------ > > _______________________________________________ > Redhat-install-list mailing list > Redhat-install-list at redhat.com > https://www.redhat.com/mailman/listinfo/redhat-install-list > > End of Redhat-install-list Digest, Vol 46, Issue 13 > *************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: