Bob63
April 30th, 2010, 08:16 PM
So, my experience with the upgrade...
Going from 9.10 64-bit to 10.4 64-bit.
Tried to be a decent, sharing sort and downloaded the LiveCD for 64-bit from torrent. No problem.
Didnīt have any blank CDs handy, but I had a 1GB USB thumb drive that I have used to install other distros that I wanted to test, so used unetbootin to make my installation on. No problem.
LiveCD tried to run, but hung with a black screen; no blinking cursor, nothing. Problem.
Restart, go back to my functioning system, and re-create the LiveCD on the thumb drive using USB Startup Disc Creator. No problem.
Reboot. Monitor went into standby and never came out. Problem.
Decided to give up on the LiveCD. Downloaded the alternate-install CD for 64-bit and put it on the thumb drive. No problem.
Installation went fine. No major hang-ups at this point. Had the grub_puts problem, even though I specified the correct place, and so had to reinstall grub, which fixed that.
Although it is still early in the process for me, my main (relatively minor) gripe is the same one I always have: Although Linux seems to be able to tell a lot about the hardware (through what I assume is either ĻaskingĻ the hardware about it capabilities or getting info from the BIOS, perhaps), why can it not tell that my keyboard numlock key is supposed to be ON? My BIOS is set to turn it on at boot. My username and password both have numbers in them, and it is convenient for me to have the numlock on at boot and remain on.
I fully realize that there are many users of notebooks/netbooks that having this setting ON for default is a problem. I donīt want it ON as default. I want a simple way to change the setting. Iīve seen complaints and questions about this since at least Edgy (there may be older postings, but I havenīt needed to research back). System>Preferences>Keyboard can let me do so many things with my keyboard - except this, apparently.
Maybe it is just me, but it doesnīt seem right that one of the first things I have to do after installation is modify a configuration file...
Going from 9.10 64-bit to 10.4 64-bit.
Tried to be a decent, sharing sort and downloaded the LiveCD for 64-bit from torrent. No problem.
Didnīt have any blank CDs handy, but I had a 1GB USB thumb drive that I have used to install other distros that I wanted to test, so used unetbootin to make my installation on. No problem.
LiveCD tried to run, but hung with a black screen; no blinking cursor, nothing. Problem.
Restart, go back to my functioning system, and re-create the LiveCD on the thumb drive using USB Startup Disc Creator. No problem.
Reboot. Monitor went into standby and never came out. Problem.
Decided to give up on the LiveCD. Downloaded the alternate-install CD for 64-bit and put it on the thumb drive. No problem.
Installation went fine. No major hang-ups at this point. Had the grub_puts problem, even though I specified the correct place, and so had to reinstall grub, which fixed that.
Although it is still early in the process for me, my main (relatively minor) gripe is the same one I always have: Although Linux seems to be able to tell a lot about the hardware (through what I assume is either ĻaskingĻ the hardware about it capabilities or getting info from the BIOS, perhaps), why can it not tell that my keyboard numlock key is supposed to be ON? My BIOS is set to turn it on at boot. My username and password both have numbers in them, and it is convenient for me to have the numlock on at boot and remain on.
I fully realize that there are many users of notebooks/netbooks that having this setting ON for default is a problem. I donīt want it ON as default. I want a simple way to change the setting. Iīve seen complaints and questions about this since at least Edgy (there may be older postings, but I havenīt needed to research back). System>Preferences>Keyboard can let me do so many things with my keyboard - except this, apparently.
Maybe it is just me, but it doesnīt seem right that one of the first things I have to do after installation is modify a configuration file...