No OS found on power up

[josephpatterson]

I am using a new Dell E6500 Latitude laptop with Ubuntu 9.04 installed. I commented out the line in /etc/X11/default-display-manager to suppress the graphics login while debugging changes to /etc/X11/xorg.conf. When the changes to xorg.conf were satisfactorily implemented, I removed the comment indicator from the line in default-display-manager. I performed a reboot as root. When the system finished the bios screen, it stopped with

No OS found
Insert OS setup disk, then press any key

I expected the grub loader menu to come up. It did not.

If I power off and press f12 for a one time diagnostics menu, I get a diagnostics screen that allows selecting the boot source (i.e., usb drive/CDROM/hard disk drive/diagnostics suite). If I select hard disk drive, then grub comes up and the boot sequence is normal from there.

Although my configuration includes a second monitor, I have repeated this process on a second E6500 that only has the laptop display and suffered the identical problem. I repeated this process on the one without a second display because the xorg.conf above fixed the resolution problem with Ubuntu 9.04 not recognizing the 1920x1200 display on the laptop and only permitted 1600x1200 resolution on the laptop display. Setting the virtual attribute in xorg.conf allows the display to use its 1920x1200 resolution. The default xorg.conf restricts the display to 1600x1200.

I suspect that disabling the GDM window manager caused some change in the initialization sequence that is not recovering when it is reenabled. I did this same thing on Ubuntu 8.04 and did not have this problem. The default 8.04 xorg.conf is substantially different from default 9.04 xorg.conf.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=f5788e80-4ca3-4601-afe8-6fa5fac483ae
MachineType: Dell Inc. Latitude E6500
NonfreeKernelModules: wl
Package: linux-image-2.6.28-15-generic 2.6.28-15.52
ProcCmdLine: root=UUID=3b8d9684-1fd1-4fc9-8c36-3c08a5f53de3 ro xforcevesa quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
SourcePackage: linux

[josephpatterson (joseph)]

I ran the following commands and appended the commands and output into a log file that is attached.
lsb_release -rd
uname -a
cat /proc/version_signature
lspci -nn
sudo lspci -vnvn
dmesg
cat /etc/X11/xorg.conf
cat /etc/X11/default-display-manager
cat /var/log/Xorg.0.log
?field.comment=I ran the following commands and appended the commands and output into a log file that is attached.
lsb_release -rd
uname -a
cat /proc/version_signature
lspci -nn
sudo lspci -vnvn
dmesg
cat /etc/X11/xorg.conf
cat /etc/X11/default-display-manager
cat /var/log/Xorg.0.log

[Leann Ogasawara (leannogasawara)]

Hi joseph,

Can you actually give the laster Karmic 9.10 Beta a try - http://cdimage.ubuntu.com/releases/karmic/ . It contains a much newer 2.6.31 based kernel. Please let us know your results. Thanks!

[josephpatterson (joseph)]

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joseph 2121 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 21'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:111d76b2,1028024f,00100302 HDA:80862802,80860101,00100000'
   Controls : 32
   Simple ctrls : 19
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f5788e80-4ca3-4601-afe8-6fa5fac483ae
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Latitude E6500
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=adefe24a-6c65-4851-833f-4dc5daec0e53 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions: linux-firmware 1.19
RfKill:
 0: dell-wifi: Wireless LAN
  Soft blocked: yes
  Hard blocked: yes
Uname: Linux 2.6.31-11-generic i686
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/joseph/.asoundrc.asoundconf>
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0W612R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2009:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.

[josephpatterson (joseph)]

Leann,
Your suggestion led me to a fix for my problem but it reveals that the
beta ubuntu is totally unacceptable for me unless ubuntu fixes a problem
that the sshd-server package is not available.

Thanks for your suggestion. I did the update-manager -d and it aborted
with a message about an unstable system (i.e., it probably detected I had
mucked with the x11 config file and gave up). I downloaded the beta iso
image and rebuilt my system with reformatting of the OS file systems.

My specific problem remained but the beta release is a wonderful
improvement b/c it properly detected my screen resolutions for both the
laptop and the external monitor and permitted 1920x1200 immediately from a
menu in system->preferences->display. I like that.

I found that changing the boot order in the rom bios putting the hard
drive first fixed the "no OS found" message. That is an acceptable
solution generally although it is less than satisfying since I have never
had to do so before. Grub would startup by default.

There is a problem with the beta ubuntu for which I will erase it and
reinstall the 9.04. The package manager indicates there is no sshd-server
package available. This is totally unacceptable. I depend on running
firefox as a different user with no access privileges on my system. That
requires an ssh to the different user to run firefox and the sshd daemon
to be running to process it. Here's hoping my inability to get sshd-server
is a temporary shortcoming.
Joseph

[Jeremy Foshee (jeremyfoshee)]

Hi josephpatterson,

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 from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 446796

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 . 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[josephpatterson (joseph)]

The development release referenced above fixes the problem reported. Commenting out the /etc/X11/default-display-manager causes a command line login to occur and removing the comment in /etc/X11/default-display-manager re-establishes the gui login screen and an OS is found on reboot.

The upstream kernel also fixes the problem. This was tested with only the upstream kernel. The upstream headers did not load properly.

[josephpatterson (joseph)]

I tested this problem as per your suggestions and find the problem does
not occur on either the 9.10 release or the upstream kernel. A bug update
was submitted and status changed to fixed.
Joseph Patterson

> Hi josephpatterson,
>
> 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 from a
> Terminal (Applications->Accessories->Terminal). It will automatically
> gather and attach updated debug information to this report.
>
> apport-collect -p linux 446796
>
> 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 . 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. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> No OS found on power up
> https://bugs.launchpad.net/bugs/446796
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> I am using a new Dell E6500 Latitude laptop with Ubuntu 9.04 installed. I
> commented out the line in /etc/X11/default-display-manager to suppress the
> graphics login while debugging changes to /etc/X11/xorg.conf. When the
> changes to xorg.conf were satisfactorily implemented, I removed the
> comment indicator from the line in default-display-manager. I performed a
> reboot as root. When the system finished the bios screen, it stopped with
>
> No OS found
> Insert OS setup disk, then press any key
>
> I expected the grub loader menu to come up. It did not.
>
> If I power off and press f12 for a one time diagnostics menu, I get a
> diagnostics screen that allows selecting the boot source (i.e., usb
> drive/CDROM/hard disk drive/diagnostics suite). If I select hard disk
> drive, then grub comes up and the boot sequence is normal from there.
>
> Although my configuration includes a second monitor, I have repeated this
> process on a second E6500 that only has the laptop display and suffered
> the identical problem. I repeated this process on the one without a second
> display because the xorg.conf above fixed the resolution problem with
> Ubuntu 9.04 not recognizing the 1920x1200 display on the laptop and only
> permitted 1600x1200 resolution on the laptop display. Setting the virtual
> attribute in xorg.conf allows the display to use its 192...