17f3:6040 Cannot complete Lucid install on Ebox 3300

[Wimpie]

Server 10.04.1 can not install completely on a DMP Ebox 3300 PC. The processor is a VortexDx86.

The installer complains about 2 things:
1. It can't find a usable kernel
2. It can't find the proper network card driver (R6040)

To complete the installation I had to accept 'No network card' and 'Don't install kernel' options.

Afterwards I booted again with install disk in rescue mode and installed the default kernel (linux-image-2.6.32-24-generic). This made the installation bootable.

To activate the network card I had to compile a kernel from source to obtain the R6040 driver and install it manually.

1) Ubuntu Server 10.04.1 LTS
2) linux-image-2.6.32-24-generic, linux-source-2.6.32-24_2.6.32-24.43
3) I expected to do a complete install in one pass like any normal installation
4) I had to take a number of extra steps just to get a working installation

[Wimpie (wimpie)]

I tried to install Maverick RC 1. This is worse than Lucid.

The maverick installer gets to the install menu (Install server, Install cloud, Check disc, etc). When I select Install Ubuntu Server I get the following error:
"This kernel requires the following features not present on the CPU:
cmov
Unable to boot - please use a kernel appropriate for you CPU."

Is there a way to get past this?

[penalvch (penalvch)]

Wimpie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Wimpie (wimpie)]

I do not have access to this hardware any longer. I can not test the
latest release

On 2012/07/25 07:24 PM, Christopher M. Penalver wrote:
> Wimpie, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> Can you try with the latest development release of Ubuntu? ISO CD images
> are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do
> not test the kernel in the daily folder, but the one all the way at the
> bottom. Once you've tested the upstream kernel, please remove the
> 'needs-upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description
> and deleting the 'needs-upstream-testing' text. As well, please comment
> on which kernel version specifically you tested.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream', and comment
> as to why specifically you were unable to test it.
>
> Please let us know your results. Thanks in advance.
>
> Helpful Bug Reporting Links:
> https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
> https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
> https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
> https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug
>
> ** Tags removed: 3300 ebox vortexdx86
> ** Tags added: needs-upstream-testing
>
> ** Summary changed:
>
> - Cannot complete Lucid install on Ebox 3300
> + 17f3:6040 Cannot complete Lucid install on Ebox 3300
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[penalvch (penalvch)]

Wimpie, this bug report is being closed due to your last comment regarding how you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.