Announcement

**vinnywright** · Apr 10, 2013, 05:12 PM

I thought this box was running / no ,,,,,,by the way nice A$$ box I am jealous ,,,,,,what if anything did you change between the time it was working and now (updates upgrades installs reformatting/partitioning ) what was the original install and partitioning scheme/set up wile it was working yada yada yada ?

VINNY

**Shabakthanai** · Apr 11, 2013, 04:59 AM

*

Originally posted by vinnywright View Post

I thought this box was running / no ,,,,,,by the way nice A$$ box I am jealous ,,,,,,what if anything did you change between the time it was working and now (updates upgrades installs reformatting/partitioning ) what was the original install and partitioning scheme/set up wile it was working yada yada yada ?

VINNY

Hi Vinny, the answer is pretty easy, I was making new configuration in 'System Settings' because monitor 2 was the clone of monitor 1. It took a bit to fix, because my new video card is an AMD style rather than NVidia. When I changed it and got it to work like a twinview screen, I believe the same as when in my other box with a GForce NVidia card, that was the only significant change I made that I can think of.

The problem occurred when I rebooted the next day. It paused in the boot process as described above. I then reviewed the changes made in the BIOS and copied each setting so that I could present it on the forum, if necessary.

It took a while because I had to type it out on my other box, save, copy and send it to the forum. I suppose I could have done something else, but I don't think so.

Right now, I am concerned that I could screw up the works in the BIOS even more. I have never been afraid of working in the BIOS but have heard that some mistakes can be permanent. My limited knowledge and memory suggests that if I remove the CMOS battery for a few seconds and replace it, I can start over at the beginning.

I really am working over my head. I have only built a couple of computers before this and have been fortunate so far. This is the first time I built a unit that is close to cutting edge and probably the last computer I will build, so I really don't want to break it before I can use it a little while.

I realize I may have given too much data for the opening of post, but I expect this problem needs a GURU to keep from further screwing it up. The really smart computer technicians seem to prefer too much rather than too little info.

Kmail has been screwing up on all my computers. Nevertheless, I prefer Kubuntu to Windows, which is the only working email for me. In Kmail, when I download new emails, the data flashes upon open and disappears. I permanently lose the emails. I sent a similar to this post report to AsRock to see if they could help me. I believe their response came and disappeared in a Kmail fetch. I do not know how to follow that one up. It is the reason for this post.

I have to open Vista on second boot of my laptop to get my email. When I do, the emails I lost do not download. I suppose that is because I do not have my emails saved on my server. I do not understand how that works, or if that is the problem why I lose my emails that are downloaded accedentally to the kmail application.

I get a little absent minded anymore and forget about Kmails disfunction. I have uninstalled, rebooted, and re-installed Kmail and it always ends up the same. This post if more important to me than that problem. I am open to suggestions in what to do. The more I learn, the dumber I seem to get. Thanks, friend, for any help you can give me. You are the only responder.

In answer to what was the partitioning scheme, I loade a pre-installed SSD prepared for this installation. I believe where it should have been divided with / as the OS, /home as storage area on a separate 1tb 6gb HDD. Nevertheless, I seem to remember looking at the partition table when first I got the system working because the mount point for the /home partition was actually entered as /media/?, I don't remember what, which was not as originally setup.

I did not do anything about it at that time, because I also have a fancy video card now 2gb DDR5 with 1866 XFX Radeon setup. I had a friend who was going to loan me a Win7 card so that I could set up the BIOS and GPU the way the card was meant to be installed. Setting most everything in the BIOS to defaults was how I got it working in the first place, but unlike NVidia, Radeon cards do not have the download features for drivers that GForce cards have.

I suspected if I customised the BIOS using the Win7 approach, I could then remove Kubuntu, install Win7, and reinstall Kubuntu again. I thougt any important settings in the BIOS that might differ from the two installations may remain when I installed Kubuntu again. It is probably foolish on my part, because I am so computer stupid, but it seemed a good approach.

I never anticipated having a working machine that would stop so abruptly as has happened. And, the Email debachle ??sp. further exacerbated ??sp. the problem. I am so unqualified, this time.

**Shabakthanai** · Apr 11, 2013, 04:19 PM

Vinny, I reset the BIOS to default settings and only modified boot seqeunce order and saved it. This time the boot screen paused at a different set of boot steps as follows:

* Starting bluetooth daemon [OK]
* Starting regular background program processing daemon [OK]
* Starting automatic crash report generation [OK]
* Starting deferred execution scheduler [OK]
* Stopping anac(h)ronistic cron [OK]
* Stopping save kernel messages [OK]
* Starting anac(h)ronistic cron [OK]

* Stopping anac(h) ronistic cron [OK]
* Stopping Read required files in advance (for other mountpoints) [OK]
* Checking battery state... [OK]
* Stopping System B runlevel compatibility [OK]
* Starting [OK]
* Starting [OK]
* Stopping [OK]

Starting CUPS printing spooler/server [OK]

Does this help at all in diagnosis? Sure would like to hear from anyone on this matter. Thx.

**Shabakthanai** · Apr 11, 2013, 04:22 PM

*

Originally posted by Shabakthanai View Post

Vinny, I reset the BIOS to default settings and only modified boot seqeunce order and saved it. This time the boot screen paused at a different set of boot steps as follows:

* Starting bluetooth daemon [OK]
* Starting regular background program processing daemon [OK]
* Starting automatic crash report generation [OK]
* Starting deferred execution scheduler [OK]
* Stopping anac(h)ronistic cron [OK]
* Stopping save kernel messages [OK]
* Starting anac(h)ronistic cron [OK]

* Stopping anac(h) ronistic cron [OK]
* Stopping Read required files in advance (for other mountpoints) [OK]
* Checking battery state... [OK]
* Stopping System B runlevel compatibility [OK]
* Starting [OK]
* Starting [OK]
* Stopping [OK]

Starting CUPS printing spooler/server [OK]

Does this help at all in diagnosis? Sure would like to hear from anyone on this matter. Thx.

Should I re-install Kubuntu. It seems inappropriate at this time, however, could that correct boot instruction? I just do not have knowledge in what happens at boot level. Thx again.

**vinnywright** · Apr 11, 2013, 05:25 PM

maby it's a video problem (was the last thing you were changing) try booting in vesa moad and with no acpi

at the grub screen , befor it starts to boot ,,,, press the e key , use the arow key's to place the cursor at the end of the line that starts with linux right behind the "quiet splash" and back space out quiet splash ,, now type in vga=791 noacpi and then press and hold down ctrl and x then relece ........this should boot this one time with those options

cant hurt and may work

VINNY

**Shabakthanai** · Apr 11, 2013, 07:59 PM

*

Originally posted by vinnywright View Post

maby it's a video problem (was the last thing you were changing) try booting in vesa moad and with no acpi

at the grub screen , befor it starts to boot ,,,, press the e key , use the arow key's to place the cursor at the end of the line that starts with linux right behind the "quiet splash" and back space out quiet splash ,, now type in vga=791 noacpi and then press and hold down ctrl and x then relece ........this should boot this one time with those options

cant hurt and may work

VINNY

The new BIOS works using the mouse. When I restarted the computer, I attempted to enter pressing the e key. Nothing happened. I then rebooted and pressed f11, which opens the boot menu in GUI form. I entered my SSD identity, because that is where the OS is located. I immediately pressed the e key to attempt your suggestion again. The boot process paused again just a few steps into the boot. I was unable to continue with your other instructions.

I am a bit frustrated. Unable to communicate with anyone who is familiar with my new system, and intellectually illequiped, I just don't know what to do next.

For the better part of the first day of installation, I had a working computer. I was able to configure most things in System Settings, connect with the Internet, and communicate with the forum. For much of the time, I used on monitor and the former build and the other monitor with the new build. I updated and upgraded the system, loaded kubuntu-restricted-extras, and most of the medibuntu applications. I played Texas Holdem in Facebook a little and played a couple of movies on Netflix. Then I shut down for the night. It was when I booted next day that it would not boot to a screen. It seems I know just enought to get into trouble.

What do you advise as a next step? As I recall, I had similar problems when I built the last computer, so I suppose I will figure it out eventually. I sure would like the process to happen a little faster. I worry that I somehow broke it. Your continued help is greatly appreciated. Thanks friend.

**vinnywright** · Apr 11, 2013, 09:19 PM

Originally posted by Shabakthanai View Post

*The new BIOS works using the mouse. When I restarted the computer, I attempted to enter pressing the e key. Nothing happened. I then rebooted and pressed f11, which opens the boot menu in GUI form. I entered my SSD identity, because that is where the OS is located.

are you saying that you never see the grub menu ?
did you install the system to just boot strate up without displaying the grub menu ?
if so press and hold the shift key wile the system starts ,,,right after you "enter your SSD identity" this SHOULD cause the grub menu to display ,,, if so try what I suggested again wile your looking at the grub menu.

I never install a system to not show the grub menu for this and similar reasons ,,,,,if you ever get booted back up we can change this

and no I do not think you broke your new box ,,,,,,,,just the install some

try booting up your installation Medea (the live cd/usb) to see if it will boot as well .

VINNY

**Shabakthanai** · Apr 12, 2013, 04:22 AM

I realize this is going to make me sound stupider than ever, but is the grub menu the part of boot where system information is posted? If so, that does not appear. If grub is when you have choices which drive to select, that appears when I press f11. That is how I have been attempting to boot. I press f11 and select the SSD. If grub is the continuous print of opening steps, that is when the boot process pauses at the points shown in the previous screens that are indicated by the [OK]'s.

As I recall, there is a step in the BIOS that calls for a 'fast boot'. There were 3 choices. One choice was for either Intel or Microsoft systems, so I did not check that box, however, I may have selected the box with a 'fast boot' choice. I believe the 3rd choice was perhaps 'disable'. Is 'disable' the choice I should have made? I have never really understood the differences in grub and boot. I thought they were the same.

When I attempted to boot holding the shift key down and the screen turns black with a blinking cursor in the upper left corner. It remains stalled at that point.

To enter the setup, I repeatedly press the Def key during that point when posting usually takes place, and the BIOS opens. I will check to see if the 'fast boot' option is checked and will 'disable' it while waiting for a response to this reply. Thanks for your patience.

Originally posted by vinnywright View Post

are you saying that you never see the grub menu ?
did you install the system to just boot strate up without displaying the grub menu ?
if so press and hold the shift key wile the system starts ,,,right after you "enter your SSD identity" this SHOULD cause the grub menu to display ,,, if so try what I suggested again wile your looking at the grub menu.

I never install a system to not show the grub menu for this and similar reasons ,,,,,if you ever get booted back up we can change this

and no I do not think you broke your new box ,,,,,,,,just the install some

try booting up your installation Medea (the live cd/usb) to see if it will boot as well .

VINNY

I returned before you read this to tell you that I am currently with the speed selection disabled. I was when I answered this reply. Apparently I had already tried this as an option. By the way, the three choices are as follows:

Disabled (which I currently have selected)
Fast (and)
Ultra Fast

'Ultra Fast' was my first choice when setting up the BIOS initially. 'Fast' was my 2nd attempt. And 'Disabled' was my final attempt at this step and is where it is now.

There is a selection 'Full Screen Logo'. I Disabled that feature after the initial time the new build actually booted and worked.

In my previous build (the Quad-Core), 'Full Screen Logo' was an ASUS Advertisement that did not benefit the boot process in any way and just took up time. It had a disable feature too. I always had to disable that feature when I had to apply default BIOS to fix a problem. It was a pain in the neckta, but I did it to stop wasting boot time and is the reason I disabled the option in this build. Since it does not make any sense to change it, I will wait for your reply before I enable the feature.

I am hesitant to keep changing the process just as a means to try things I do not understand. In the end, I fear it will complicate things even more. I would appreciate an opinion on this thought.

**Shabakthanai** · Apr 12, 2013, 04:51 AM

Originally posted by Shabakthanai View Post

I realize this is going to make me sound stupider than ever, but is the grub menu the part of boot where system information is posted? If so, that does not appear. If grub is when you have choices which drive to select, that appears when I press f11. That is how I have been attempting to boot. I press f11 and select the SSD. If grub is the continuous print of opening steps, that is when the boot process pauses at the points shown in the previous screens that are indicated by the [OK]'s.

As I recall, there is a step in the BIOS that calls for a 'fast boot'. There were 3 choices. One choice was for either Intel or Microsoft systems, so I did not check that box, however, I may have selected the box with a 'fast boot' choice. I believe the 3rd choice was perhaps 'disable'. Is 'disable' the choice I should have made? I have never really understood the differences in grub and boot. I thought they were the same.

When I attempted to boot holding the shift key down and the screen turns black with a blinking cursor in the upper left corner. It remains stalled at that point.

To enter the setup, I repeatedly press the Def key during that point when posting usually takes place, and the BIOS opens. I will check to see if the 'fast boot' option is checked and will 'disable' it while waiting for a response to this reply. Thanks for your patience.I returned before you read this to tell you that I am currently with the speed selection disabled. I was when I answered this reply. Apparently I had already tried this as an option. By the way, the three choices are as follows:

Disabled (which I currently have selected)
Fast (and)
Ultra Fast

'Ultra Fast' was my first choice when setting up the BIOS initially. 'Fast' was my 2nd attempt. And 'Disabled' was my final attempt at this step and is where it is now.

There is a selection 'Full Screen Logo'. I Disabled that feature after the initial time the new build actually booted and worked.

In my previous build (the Quad-Core), 'Full Screen Logo' was an ASUS Advertisement that did not benefit the boot process in any way and just took up time. It had a disable feature too. I always had to disable that feature when I had to apply default BIOS to fix a problem. It was a pain in the neckta, but I did it to stop wasting boot time and is the reason I disabled the option in this build. Since it does not make any sense to change it, I will wait for your reply before I enable the feature.

I am hesitant to keep changing the process just as a means to try things I do not understand. In the end, I fear it will complicate things even more. I would appreciate an opinion on this thought.

This may be useful additional information relating to 'Fast Boot'.

DescriptionFast Boot minimizes your computer's boot time.

Options:
Disabled: Disable Fast Boot
Fast: When selecting "Fast", it is not allowed to boot from an USB storage device.
Ultra Fast: There are a few restrictions:
1. Only supports Windows 8 UEFI operating system.
2. You will not be able to enter UEFI setup by using keyboard. The only way to enter UEFI Setup is Clear CMOS or "Restart to UEFI" utility in windows.
3. If you are using an external graphics card, the VBIOS must support UEFI GOP in order to boot. (When they say external graphics card, are they referring to my after market vid card and suggesting that an internal graphics card or 'on the motherboard' graphics card is present?)

**vinnywright** · Apr 12, 2013, 03:13 PM

fast boot disabled is good ,,, secure boot disabled is good !!

grub is the boot loader and what actually starts the operating system up (Kubuntu) it is installed and present or you would not get the the system starting to boot up (the continuous print of opening steps) when you see the grub screen it will look some thing like this

Ubuntu 12.10
previous linux versions
memtest
recovery

not exactly like this but close.
when you press F11 to the choice of drives to boot from it is still part of the BIOS/UEFI ,,, but right after you chose the SSD and before the continuous print of opening steps is when to hold down the shift key to try and display the grub menu .

VINNY

**Shabakthanai** · Apr 12, 2013, 04:26 PM

Originally posted by vinnywright View Post

fast boot disabled is good ,,, secure boot disabled is good !!

grub is the boot loader and what actually starts the operating system up (Kubuntu) it is installed and present or you would not get the the system starting to boot up (the continuous print of opening steps) when you see the grub screen it will look some thing like this

Ubuntu 12.10
previous linux versions
memtest
recovery

not exactly like this but close.
when you press F11 to the choice of drives to boot from it is still part of the BIOS/UEFI ,,, but right after you chose the SSD and before the continuous print of opening steps is when to hold down the shift key to try and display the grub menu .

VINNY

After I wrote you, the SSD is no longer shown in the drive list. It has never done that since I first built this system. Looks like the gremlins are in the system. The only thing I can think to do now is try to achieve the default BIOS again. The teribyte drive shows now and a UEFI boot, but no SSD. Another thing I could try to force recognition of the SSD is to disconnect the TB drive. I will do nothing until I get further info from you.

**vinnywright** · Apr 12, 2013, 05:06 PM

strange ,,,,I must admit I have no hands on experience with UEFI mother boards just wat I have read and most of that was hear ,,,in the UEFI help section.

right now I would just try to boot up a live cd/USB and see if it will or not .

then go from their .

did you say you had actually installed the system to the SSD on a different box ?

a member hear that dose have UEFI experience is SteveRiley ,,,,maby he will see this and have something to say .

but go ahead and see if a live cd or USB will start up on it wile you wate.

VINNY

**Shabakthanai** · Apr 12, 2013, 05:52 PM

Originally posted by vinnywright View Post

strange ,,,,I must admit I have no hands on experience with UEFI mother boards just wat I have read and most of that was hear ,,,in the UEFI help section.

right now I would just try to boot up a live cd/USB and see if it will or not .

then go from their .

did you say you had actually installed the system to the SSD on a different box ?

a member hear that dose have UEFI experience is SteveRiley ,,,,maby he will see this and have something to say .

but go ahead and see if a live cd or USB will start up on it wile you wate.

VINNY

I am embarrassed to say that I don't recall installing the OS on my quad. Nonetheless, when I booted after accepting the default BIOS of the new motherboard, I was surprised when Kubuntu 12.10 booted and worked for a day. I must have installed it on my quad, but have no memory of it. In fact, I purchased 2 SSD's and installed the 128gb SSD on the Quad and don't remember ever installing on the 256gb SSD. I purchased the 256 SSD specifically for the new 8core build. It set for a month while my purchases arrived. My personal memory doesn't work very good anymore.

**Shabakthanai** · Apr 15, 2013, 09:27 AM

I am attempting to place this post near the beginning again to hopefully get further input.

Since last posting, I have tried to install Kubuntu 12.10. About midpoint of the attempted installation it was stopped with an installer crash.

I also attempted to install Kubuntu 13.04, the most current download and some fresh downloads. Each of them paused in the 'prepare' segment or 3rd step of the installation.

I formatted the SSD and the TB drives to make sure I was starting with fresh drives. I also attempted installation on both the SSD and the TB HHD.

Every attempt at installation failed in the same way.

AsRock replied that they do not support Linux. It is agonizing to have such wonderful hardware and be unable to get it to work.

Announcement

New System Build. Having problems setting up BIOS for Install of Kubuntu 12.10

New System Build. Having problems setting up BIOS for Install of Kubuntu 12.10

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment