I'm back on my old computer because of problems with the new one. They were these:
1. I had the same 500kb RAM and hard drive from this computer in the new one.
2. After a couple of problems grub started working just exactly as before.
3. But this F7 would start to load and then go into a kernel panic.
4. I tried FC6 and it was better. It loaded clear up but then I had no "head" on my mouse. I could not see how to do anything.
5. I made a new F7 and it boots up but just like FC6 the mouse was invisable :-)
I am just wiped out today. No ideas here except I may have had the mouse and keyboard plugged in wrong. They are both PS2 connectors.
Any help will be much appreciated!
Karl Larsen wrote:
I'm back on my old computer because of problems with the new one. They were these:
- I had the same 500kb RAM and hard drive from this computer in the
new one.
- After a couple of problems grub started working just exactly as
before.
But this F7 would start to load and then go into a kernel panic.
I tried FC6 and it was better. It loaded clear up but then I had no
"head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisable :-)
I am just wiped out today. No ideas here except I may have had the mouse and keyboard plugged in wrong. They are both PS2 connectors.
Any help will be much appreciated!
Have you checked your memory? You can do a memory check with the installation disk.
Joseph Loo wrote:
Karl Larsen wrote:
I'm back on my old computer because of problems with the new one. They were these:
- I had the same 500kb RAM and hard drive from this computer in the
new one.
- After a couple of problems grub started working just exactly as
before.
But this F7 would start to load and then go into a kernel panic.
I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisable :-)
I am just wiped out today. No ideas here except I may have had the mouse and keyboard plugged in wrong. They are both PS2 connectors.
Any help will be much appreciated!
Have you checked your memory? You can do a memory check with the installation disk.
Why would that be a problem? And how do you do a memory test with the F7 installation disk?
Joseph Loo:
Have you checked your memory? You can do a memory check with the installation disk.
Karl Larsen:
Why would that be a problem?
It could be faulty, or not compatible with your board. That happens.
And how do you do a memory test with the F7 installation disk?
Run memtest86+ from the prompt, see the F key hints for help. Boot the install disc, read the text, don't start installing.
Tim wrote:
Joseph Loo:
Have you checked your memory? You can do a memory check with the installation disk.
Karl Larsen:
Why would that be a problem?
It could be faulty, or not compatible with your board. That happens.
And how do you do a memory test with the F7 installation disk?
Run memtest86+ from the prompt, see the F key hints for help. Boot the install disc, read the text, don't start installing.
Hi Tim and yes RPM was low. I have just 1/2 a gb now but tomorrow the Brown Truck brings me 2 gb of 450 MHz Ram. That may well stop a memory problem. Here is top from this old computer right now:
top - 18:28:51 up 3:02, 1 user, load average: 0.73, 0.32, 0.13 Tasks: 117 total, 1 running, 114 sleeping, 0 stopped, 2 zombie Cpu(s): 6.0%us, 3.2%sy, 0.0%ni, 90.6%id, 0.0%wa, 0.1%hi, 0.0%si, 0.0%st Mem: 482720k total, 476252k used, 6468k free, 16796k buffers Swap: 0k total, 0k used, 0k free, 220196k cached
My swap is real small and that could be a problem too.
Around 01:30am on Monday, August 27, 2007 (UK time), Karl Larsen scrawled:
top - 18:28:51 up 3:02, 1 user, load average: 0.73, 0.32, 0.13 Tasks: 117 total, 1 running, 114 sleeping, 0 stopped, 2 zombie Cpu(s): 6.0%us, 3.2%sy, 0.0%ni, 90.6%id, 0.0%wa, 0.1%hi, 0.0%si, 0.0%st Mem: 482720k total, 476252k used, 6468k free, 16796k buffers Swap: 0k total, 0k used, 0k free, 220196k cached
My swap is real small and that could be a problem too.
top is showing that you don't have any swap at all.
Steve
Steve Searle wrote:
Around 01:30am on Monday, August 27, 2007 (UK time), Karl Larsen scrawled:
top - 18:28:51 up 3:02, 1 user, load average: 0.73, 0.32, 0.13 Tasks: 117 total, 1 running, 114 sleeping, 0 stopped, 2 zombie Cpu(s): 6.0%us, 3.2%sy, 0.0%ni, 90.6%id, 0.0%wa, 0.1%hi, 0.0%si, 0.0%st Mem: 482720k total, 476252k used, 6468k free, 16796k buffers Swap: 0k total, 0k used, 0k free, 220196k cached
My swap is real small and that could be a problem too.
top is showing that you don't have any swap at all.
Steve
Yes this IS a problem and on a 160 GB hard drive you would think you could come up with a large swap. I will fix this TODAY!
On Mon, 2007-08-27 at 09:29 +0930, Tim wrote:
Joseph Loo:
Have you checked your memory? You can do a memory check with the installation disk.
Karl Larsen:
Why would that be a problem?
It could be faulty, or not compatible with your board. That happens.
And how do you do a memory test with the F7 installation disk?
Run memtest86+ from the prompt, see the F key hints for help. Boot the install disc, read the text, don't start installing.
Isn't this probably the old ram from his old machine? Prolly a speed issue on the FSB, no? He'll probably have some trouble getting the ISA sound card into the new board as well, but I'm sure any problems that crop up will be the new kernel's fault.
-- [tim@bigblack ~]$ uname -ipr 2.6.22.1-41.fc7 i686 i386
Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7.
Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Jim Cornette wrote:
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Yes
Mikkel L. Ellertson wrote:
Jim Cornette wrote:
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Yes
Yes the computer motherboard has the Navidia hardware on it. It must be the problem.
On Mon, 2007-08-27 at 08:10 -0600, Karl Larsen wrote:
Mikkel L. Ellertson wrote:
Karl Larsen wrote: Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Yes
Yes the computer motherboard has the Navidia hardware on it. It must
be the problem.
Do you get a cursor when the computer is booting (in rhgb)?
Jonathan
Jonathan Dieter wrote:
On Mon, 2007-08-27 at 08:10 -0600, Karl Larsen wrote:
Mikkel L. Ellertson wrote:
Karl Larsen wrote: Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Yes
Yes the computer motherboard has the Navidia hardware on it. It must
be the problem.
Do you get a cursor when the computer is booting (in rhgb)?
Jonathan
Hi Jonathan, yes, the pointer is present through the loading of the init steps and when you get where you provide name and password it disappears forever.
On Mon, 2007-08-27 at 13:01 -0600, Karl Larsen wrote:
the pointer is present through the loading of the init steps and when you get where you provide name and password it disappears forever.
Try booting without the Red Hat Graphical Booter, I recall comments about it and some graphics cards not getting along nicely. Remove the "rhgb" option from the kernel line before booting (either edit grub.conf, or change the booting parameters through the GRUB menus).
Jim Cornette wrote:
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Good memory Jim. Yes the computer does have a NVidia hardware set and yes if you are young you can raise the voltage on the cpu and it thinks faster :-(
I bet that is what I need to find :-)
Google here I come and hope it is there somewhere.
Karl Larsen wrote:
Jim Cornette wrote:
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I had
no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse was
invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Good memory Jim. Yes the computer does have a NVidia hardware set and yes if you are young you can raise the voltage on the cpu and it thinks faster :-(
I bet that is what I need to find :-)
Google here I come and hope it is there somewhere.
One cure is the below: As a workaround, you might want to try adding Option "SWCursor" "yes" to the Device section of your xorg.conf.
or
Option “HWCursor” “Off”
Regarding my memory, it is selective and only remembers electronics or computer related information for the most part.
Jim
Jim Cornette wrote:
Karl Larsen wrote:
Jim Cornette wrote:
Karl Larsen wrote:
- I tried FC6 and it was better. It loaded clear up but then I
had no "head" on my mouse. I could not see how to do anything.
- I made a new F7 and it boots up but just like FC6 the mouse
was invisible :-)
Was there a solution for the invisible pointer discussed earlier on which adding something to the xorg.conf file remedies? No hardware acceleration or visa versa. NVidia I believe was th discussion.
Good memory Jim. Yes the computer does have a NVidia hardware set and yes if you are young you can raise the voltage on the cpu and it thinks faster :-(
I bet that is what I need to find :-)
Google here I come and hope it is there somewhere.
One cure is the below: As a workaround, you might want to try adding Option "SWCursor" "yes" to the Device section of your xorg.conf.
or
Option “HWCursor” “Off”
Regarding my memory, it is selective and only remembers electronics or computer related information for the most part.
Jim
Very good Jim! What I have is “HWCursor” "false" which means the same as “HWCursor” "no" so wonder which is correct. I will look at man xorg-conf and see if the examples use false true or yes no :-)
Karl Larsen wrote:
Very good Jim! What I have is “HWCursor” "false" which means the same as “HWCursor” "no" so wonder which is correct. I will look at man xorg-conf and see if the examples use false true or yes no :-)
xorg.conf
If you'd done this before posting you'd have discovered that they are synonyms, and that 0 & off and 1 & on are also possible. As is omitting the boolean and using the prefix "No" to indicate negation. The justification for having a total of five ways to write each (times two; since you could use SWCursor as another negation), of which a simple typo can change the meaning, is unclear.
Ian Malone wrote:
Karl Larsen wrote:
Very good Jim! What I have is “HWCursor” "false" which means the same as “HWCursor” "no" so wonder which is correct. I will look at man xorg-conf and see if the examples use false true or yes no :-)
xorg.conf
If you'd done this before posting you'd have discovered that they are synonyms, and that 0 & off and 1 & on are also possible. As is omitting the boolean and using the prefix "No" to indicate negation. The justification for having a total of five ways to write each (times two; since you could use SWCursor as another negation), of which a simple typo can change the meaning, is unclear.
Well I didn't know what I was doing the first time I read the man page. Then the second time I knew I was interested in an option and then the man page made a lot more sense.
By the way "SWCursor" "on" is another way to do the same thing it appears. I will try first just the first one "HWCursor" "false" but keep the other if needed. And yes 1 or 0 can be used if you can remember which is which :-)
Karl Larsen wrote:
Very good Jim! What I have is “HWCursor” "false" which means the same as “HWCursor” "no" so wonder which is correct. I will look at man xorg-conf and see if the examples use false true or yes no :-)
In English either would be the same. I doubt yep or nope would work, but I never tried.
Jim
Jim Cornette wrote:
Karl Larsen wrote:
Very good Jim! What I have is “HWCursor” "false" which means the same as “HWCursor” "no" so wonder which is correct. I will look at man xorg-conf and see if the examples use false true or yes no :-)
In English either would be the same. I doubt yep or nope would work, but I never tried.
Jim
You can also use 1 or 0, if you can remember which is which :-)
On Sun August 26 2007, Karl Larsen wrote:
- I had the same 500kb RAM and hard drive from this computer in the new
one.
I seem to recall you saying that your old computer was 8 years old. I'm surprised the RAM would even fit in the slot. If I were a betting man, I'd guess that your problem is that memory - your new motherboard may have sufficient backwards compatibility to accept it, but I doubt the default BIOS settings would allow for smooth running - something really doesn't make sense -- that memory from your old machine shouldn't even have fit into the socket of your new machine
Claude Jones wrote:
On Sun August 26 2007, Karl Larsen wrote:
- I had the same 500kb RAM and hard drive from this computer in the new
one.
I seem to recall you saying that your old computer was 8 years old. I'm surprised the RAM would even fit in the slot. If I were a betting man, I'd guess that your problem is that memory - your new motherboard may have sufficient backwards compatibility to accept it, but I doubt the default BIOS settings would allow for smooth running - something really doesn't make sense -- that memory from your old machine shouldn't even have fit into the socket of your new machine
Well it was a new motherboard and uses DDRR Ram chips which are the same as the new computer. At least it worked. But it was odd F7 was not able to boot. I will have 2 GB this Monday and will try again. The little new computer is sure tiny and well done.
Eric J. Feldhusen wrote:
Karl Larsen wrote:
- I had the same 500kb RAM and hard drive from this computer in the
new one.
Did you do a fresh install of F7? If so, what partitions did you create?
I did install a new F7 over an old FC4. It boots fine but can't do a thing with it because of the pointer problem. I need to find the change to the X window files that cure that problem. Another person had that problem a few weeks ago. Hope he is still around :-)
On Mon, 2007-08-27 at 08:05 -0600, Karl Larsen wrote:
I need to find the change to the X window files that cure that problem.
Google for software pointer, or read the man files for the X drivers. You'll find it.
Tim wrote:
On Mon, 2007-08-27 at 08:05 -0600, Karl Larsen wrote:
I need to find the change to the X window files that cure that problem.
Google for software pointer, or read the man files for the X drivers. You'll find it.
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
On Mon, 2007-27-08 at 12:30 -0600, Karl Larsen wrote:
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux
and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
It took me about two minutes to find the reference.
The solution is to add the line
Option "HWCursor" "false"
to the section of xorg.conf that defines the video card.
I don't know whether that works, though. I'm just going to test it.
Meanwhile, as an extreme kludge, keep moving the mouse as you login. I find that that works.
Bruce Byfield wrote:
On Mon, 2007-27-08 at 12:30 -0600, Karl Larsen wrote:
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux
and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
It took me about two minutes to find the reference.
The solution is to add the line
Option "HWCursor" "false"
to the section of xorg.conf that defines the video card.
I don't know whether that works, though. I'm just going to test it.
Meanwhile, as an extreme kludge, keep moving the mouse as you login. I find that that works.
I will try both :-)
Thank you so much. I will look for
Option "HWCursor" "false"
and if not there I will add it. And thank you so very much!
Bruce Byfield wrote:
On Mon, 2007-27-08 at 12:30 -0600, Karl Larsen wrote:
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux
and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
It took me about two minutes to find the reference.
The solution is to add the line
Option "HWCursor" "false"
to the section of xorg.conf that defines the video card.
I don't know whether that works, though. I'm just going to test it.
Meanwhile, as an extreme kludge, keep moving the mouse as you login. I find that that works.
It took me about 2 minutes to find the place in xorg.conf which is real short in this computer and added the proper words 8-)
Tomorrow I should have the big RAM cards and they will go in with this hard drive and with luck it will work. Assuming the best I will then be on the new computer with this F7. I will then order a SATA hard drive and learn if dd will let me copy this F7 complete to the new hard drive. That is the long range plan. Then the new computer will be New :-)
On Mon, 2007-08-27 at 13:31 -0600, Karl Larsen wrote:
Bruce Byfield wrote:
On Mon, 2007-27-08 at 12:30 -0600, Karl Larsen wrote:
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux
and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
It took me about two minutes to find the reference.
The solution is to add the line
Option "HWCursor" "false"
to the section of xorg.conf that defines the video card.
I don't know whether that works, though. I'm just going to test it.
Meanwhile, as an extreme kludge, keep moving the mouse as you login. I find that that works.
It took me about 2 minutes to find the place in xorg.conf which is
real short in this computer and added the proper words 8-)
Tomorrow I should have the big RAM cards and they will go in with
this hard drive and with luck it will work. Assuming the best I will then be on the new computer with this F7. I will then order a SATA hard drive and learn if dd will let me copy this F7 complete to the new hard drive. That is the long range plan. Then the new computer will be New :-)
Uh, "dd" won't give you a functional system. It will perform a byte- for-byte copy and unless the source and target disks are identical, will absolutely NOT work. You will need to run a "ghost"-like program to do that or boot the old disk, partition the new disk the way you want and do something really nasty like "cp -a" from the top level of each partition of the old disk to the corresponding partition on the new.
---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Which is worse: ignorance or apathy? I don't know. Who cares? - ----------------------------------------------------------------------
Rick Stevens wrote:
On Mon, 2007-08-27 at 13:31 -0600, Karl Larsen wrote:
Bruce Byfield wrote:
On Mon, 2007-27-08 at 12:30 -0600, Karl Larsen wrote:
I have Googled for nVIDIA and found not much. Tried nVIDIA, Linux
and found some things but not what I am looking for. All about nVIDIA drivers which work on Windows but not Linux. Will try software pointer.
It took me about two minutes to find the reference.
The solution is to add the line
Option "HWCursor" "false"
to the section of xorg.conf that defines the video card.
I don't know whether that works, though. I'm just going to test it.
Meanwhile, as an extreme kludge, keep moving the mouse as you login. I find that that works.
It took me about 2 minutes to find the place in xorg.conf which is
real short in this computer and added the proper words 8-)
Tomorrow I should have the big RAM cards and they will go in with
this hard drive and with luck it will work. Assuming the best I will then be on the new computer with this F7. I will then order a SATA hard drive and learn if dd will let me copy this F7 complete to the new hard drive. That is the long range plan. Then the new computer will be New :-)
Uh, "dd" won't give you a functional system. It will perform a byte- for-byte copy and unless the source and target disks are identical, will absolutely NOT work. You will need to run a "ghost"-like program to do that or boot the old disk, partition the new disk the way you want and do something really nasty like "cp -a" from the top level of each partition of the old disk to the corresponding partition on the new.
- Rick Stevens, Principal Engineer rstevens@internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
-
- Which is worse: ignorance or apathy? I don't know. Who cares? -
Thanks. I have used cp -a many times before and it always worked. I will forget dd and keep using cp -a.
Somebody in the thread at some point said:
Uh, "dd" won't give you a functional system. It will perform a byte-
That's not my understanding... AIUI dd will work fine if he is going to a larger drive. The problem he will be left with is that the partitioning will reflect his smaller drive.
If he was going from a 160GB drive to 500GB as I recall, then he should have a fully functional set of partitions extending over the first 160GB of the drive and the remaining 340GB going begging. He could go on and fix that by adding a new partition and assigning the 340GB to it, then formatting the new partition ext3 or whatever. So dd is not something that should not be considered.
-Andy
Andy Green wrote:
Somebody in the thread at some point said:
Uh, "dd" won't give you a functional system. It will perform a byte-
That's not my understanding... AIUI dd will work fine if he is going to a larger drive. The problem he will be left with is that the partitioning will reflect his smaller drive.
If he was going from a 160GB drive to 500GB as I recall, then he should have a fully functional set of partitions extending over the first 160GB of the drive and the remaining 340GB going begging. He could go on and fix that by adding a new partition and assigning the 340GB to it, then formatting the new partition ext3 or whatever. So dd is not something that should not be considered.
-Andy
Well my plan when this is done will have a sudo LVN that has a partition for /boot and /home and perhaps /usr. This will come together when I do it. With the larger hard drive I may partition for two or three Linux versions out in the future.