LG 34um95 Ultrawide Monitor Not Waking During Boot on 2013 MP

I have a new LG 34um95 ultra-wide monitor that is Mac Pro comparable and has thunderbolt ports.  When try to boot on my 2013 Mac Pro using bootcamp and switch between OSX and Windows 8, the monitor is black (both HDMI and on thunderbolt) as if the monitor is not recognized.  If I hook up a DVI to MiniDV port to an old school monitor I get a display on that just fine.  Anytime I load OSX, the LG monitor is black until the login page - I cannot see the white screen with the apple  logo ever except for the old DVI monitor.
I also get random flashes and stutters on the picture of the LG monitor?
I don't know if it's the monitor or the Mac Pro?  Already called apple care and they told me to reset the VRam.  That did nothing.
Any Help?

Hi,
I have the same issue with this monitor using Thunderbolt on my Late 2013 6-core Mac Pro with D500 GPUs. I get no image displayed until I get past my FileVault login and it takes me to the desktop. I have to enter my password blind as nothing is displayed at all during the boot. This also prevents me from choosing boot drives, or allowing other users to unlock the FileVault. The issue also occurs during a safe boot, and booting into recovery mode. My Mac Pro is running Yosemite, however it hasn't fixed the issue. I have tried a PRAM and SMC reset, however it hasn't changed the issue over Thunderbolt.
I have contacted LG (which is of no use as their support is really terrible), and Apple who actually sent my issue to engineering. However, engineering was only able to assist me with getting the HDMI working again. To get HDMI working, they had me do a PRAM reset with it plugged in using HDMI. They were unable to get the Thunderbolt working though, as the monitor is not officially supported.
I have been unable to find anyway to make the Thunderbolt work correctly on this monitor. This is very disappointing as this monitor is advertised by LG as being supported by the new Mac Pro.

Similar Messages

  • Aspire One D255 monitor shuts off during boot

    Every time I boot, immediately after the kernel lauches init, my screen powers off.  About 15 seconds later, it comes back on.
    The delay before coming back on seems to be independent of the init process.  If I speed init up, by the time it comes back on it's waiting at the login prompt.  If I slow it down, it comes back on while init is still running.
    I tried adding an echo -e -n '\033[13]' to my init scripts in an effort to unblank the display, but it doesn't help.
    This happens both booting of the install image and after installation. It makes it extremely hard to figure out what's going on during startup.
    Has anyone seen this before?

    I have a similar issue with my aspire one, but the display is not turning off, it is actually the backlight turning off during boot. I use fbsplash with a dark theme but a bright progress bar. During boot, it appears as if the screen has turned off, but looking closely, I can still see the progress bar.
    I have tried several different methods of keeping the backlight on to no avail.
    Personally I am thinking it is monitor signal detection during a monitor mode reset during boot, ie from console resolution switching to KMS resolution. Most monitors lose signal detection when changing mode (in my experience). Some display a "No Signal" message of some sort, some briefly turn off until signal is detected again, and in the Aspire One case, the backlight turns off. Put it down to monitor manufacturers built in power saving "features".
    Tha same thing happens when I boot windows.
    Of course, if anyone does come up with a solution, I am eagerly listening!
    Cheers.

  • Hard disk not detected during booting or also it does not show in boot menu.

    hard disk not detected during booting or also it does not show in boot menu please tell

    you may have a failed hard drive or bad cables, i would check first to see if the hard drive is powering on. if it doesn't try a different power connection, and if it still doesn't start spinning i would say that it is bad and get a new hard drive. If
    it does start spinning and just isn't being recognized, try a different sata port if you have the option or a different sata cable all together.

  • Monitor blanks off during boot up.

    After zapping the PRAM on my G4 (AGP, Ati rage 128 pro) my monitor now blanks off just after the Apple logo in the boot up sequence. The monitor is a Hewlett Packard HPw19 flat screen. In this blank state the monitor shows the message "Attention - Input Not Supported". I'm guessing that zapping the PRAM has switched OS X into a screen resolution that the monitor can't handle. SO....my problem is... how can i switch screen resolution of the video card etc when i cannot use the display? :-/
    thanks for any help/ideas

    I eventually fixed this by installing a fresh system to the 2nd harddisk - this system booted fine so i could then switch screen resolution and boot from the original system again. Had i had a spare monitor i could have booted from that, switched screen resolution, then plugged in the original monitor. I think it must be an issue with the HP w19 not being 100% ok with OS X.

  • MBP 2011 - Ext. Screen not detected during boot

    Hey everyone,
    I got a new MBP 15" (2011) and I'm having issues with my screen (Acer X243HQ) during boot. It just doesnt get recognized when I boot the machine. Everytime I need to unplug it and plug it back in - which gets kinda annoying as the MBP mainly serves as desktop-replacement for now.
    Anyone else having these issues?
    Edit: Seems to apply to standby-mode as well: http://discussions.apple.com/thread.jspa?threadID=2783561&tstart=30
    Message was edited by: matthewadams

    Alright, I will definitely give it a try.
    I´ve read on various sites and forums, that gnome-shell has some problems with the catalyst driver - Any expericence with that?
    So far I didn´t even get to start a X session, but I tested gnome-shell with ubuntu some while ago, and now want to use it witch arch.
    Besides I would love to see the intel-card running, as it gives me way better batter-life and I don´t really need the power of the Ati-card.
    Is there any way to, at least narrow down whats causing the problems with the intel-gpu?
    Anyways, I really appreciate that you take the time to help me with my problems

  • 2006 Mac Pro + NEC 3090 - grey screen not displayed during boot

    I have a September '06 Mac Pro 1,1 (Woodcrest variant) hooked up to an NEC 3090 30" LCD monitor, running OS X 10.5.7. Previously, I was using an Eizo S2110W 21" LCD; turning the monitor and computer on would cause the following to be displayed (in order):
    1. Light grey background with dark grey Apple logo with spinning thing.
    2. Solid blue background.
    3. Leopard wallpaper.
    4. Log-in dialogue.
    Since using the NEC, the grey screen is not displayed at all: the display stays blank until the blue screen is displayed, and then the Leopard wallpaper and so on. This is using the 2560x1600 native resolution of the display, and has occurred using both 10.5.6 and 10.5.7.
    If I change the resolution to 1280x960 and boot, the grey screen is displayed. If I change it to 1600x1200, I get weird corruption on-screen during the period when the grey screen should be displayed; for some reason, this includes part of the desktop wallpaper I was using before I rebooted.
    Resetting the non-volatile RAM using Command-Option-P-R works for the very first time I boot the computer, though the grey screen is displayed at very low resolution. If I reboot from the log-in dialogue immediately afterwards, normal behaviour occurs - i.e. the blank screen.
    The upshot of all of the above is that if I want to boot into Windows, or install OS X (e.g. when Snow Leopard comes out), I have to remember to boot into my existing OS X installation, change resolution, reboot whilst remembering also to hold down the ALT/Option key. It would be much easier if I could do away with having to change resolution.
    I have tried connecting the monitor to a PPC Mac mini at 1600x1200 (it won't go any higher), using Tiger 10.4.11 (not sure of exact version - the latest). At this resolution, the grey screen is displayed.
    Using a '08 MacBook Air (first generation) and the supplied DVI adapter, also at 1600x1200, nothing is displayed on the NEC until I get to the log-in screen. This occurs if the NEC is set to be the primary display or the secondary one - the only difference is where the log-in dialogue is displayed. I am not familiar with dual-screen behaviour, so I can't say whether anything is supposed to be displayed or not (i.e. does the grey appear on both displays?).
    I have been in touch with NEC Europe support on this issue, who suggested it might have something to do with the 10.5.7 release. I know this not to be the case, as it was occurring prior to 10.5.7 being released.
    Any ideas?

    Put more of your hardware listed in your profile.
    I looked and don't see you list your graphics card anywhere.
    Graphic card it came with was either X1900 (watch for heat and dust bunnies and clogged vent);
    OEM 7300GT (seems unlikely).
    You could have replaced either with 8800GT or ATI 3870.
    Require 10.5.2+ ideally 10.5.6+.
    Some problems cropped up with 10.5.7. 10.5.7 doesn't work on some (many) 3rd party displays and stay with 10.5.6 if necessary until it is fixed or resolved.
    But you say it happens with 10.5.6 also, and was doing so before 10.5.7? which makes your problem somewhat different or unique.
    Zapping PRAM or NVRAM reset obviously shouldn't be needed repeatedly. And your graphics card probably needs to be replaced, or test with another card to rule it out.

  • Dual monitor not working under Boot Camp on Mac Pro ATI HD 2600 XT

    Recently got a brand new Mac Pro with ATI Radeon HD 2600 XT graphics card.
    On the Mac side (Leopard), everything works perfectly: my second monitor (a plasma screen connected with HDMI to the second DVI of the ATI card via HDMI/DVI adapter) is fully recognized and it works as an extended desktop or in Mirroring mode.
    Under Boot Camp (Windows XP Pro) however, NOTHING: the second monitor always appears in the display properties, but it is grayed out (inactive), and when I try to activate it, it switches back to being grayed out immediately and nothing gets displayed on it.
    After reading all the posts I can find on the topic, I tried the following (in pretty much every possible combination - Thank god for WinClone that allows me to restore the Boot Camp basic install image without having to reinstall Windows from scratch every time):
    a) Bootcamp 2.0 (installed by default by Bootcamp assistant)
    b) Update to Bootcamp 2.1
    1) Windows XP Pro SP2c vanilla install (from my Windows XP pro install disk)
    2) Update to Windows XP SP3 (I tried with and without BC 2.1: both worked -> BC 2.1 didn't seem to be required for SP3 - maybe because this is a mac pro and not a MB or MBP)
    i) ATI drivers installed by default by Boot Camp assistant (BC 2.0) or by BC 2.1
    ii) Latest ATI drivers found on ATI web site specifically under Boot Camp / Mac Pro.
    Note: Interestingly, the catalyst installer worked ok (provided .NET framework 2.0 is installed though), but it seems that the Radeon BootCamp/Mac Pro driver set itself from ATI's web site does NOT include a driver for the HD 2600 XT - so when I install this driver set, it tells me that no compatible hardware was found...
    iii) Latest ATI drivers found under Windows XP (these did include one driver specifically for the Radeon HD 2600 XT)
    NOTHING seems to work. I read posts (most of the from late last year) about ATI Catalyst utility showing a 3rd monitor at some point, but I never got any 3rd monitor showing in any of my many many trials with Catalyst. I have yet to get a single image appear on my plasma under Bootcamp Windows. I don't believe its the hardware because everything works great on the max OS X side.
    I am actually considering switching to an NVidia 8800 GT just to get the dual screen to work under BootCamp/Windows XP because I really need it and I read everywhere that drivers for NVidia are far better than ATI ones.
    Any advice? What should I try next before getting an 8800 ?
    Is there a diagnostic utility that I can use to test my config including the GC?
    Thanks!

    Hi there aside from my laptop I have an iMac 20" with the same HD 2600 XT card. I recently installed the Catalyst 8.6 driver by using a driver mod from driverheaven, I use Vista 32. By installing it this way I got boosted performance and many issues with the bootcamp drivers were fixed. As you may already know the ATI drivers do not install on bootcamped macs usually but the mod tool fixes this. Its unofficial so do so at your own risk but try it out and see if you get the second monitor if not just rollback. Hope this helps and I didn't want to say too much about the 8.6 driver mod because it may not be allowed here but google will provide any answers.

  • "ERROR disk not found" during boot cdrom installation

    We were booting a T4-4 server from a Solaris 10 boot ISO and command I used was "boot rcdrom - install as nowin" (i was mounting the ISO using the serial redirection window etc, hence the rcdrom)
    It worked great asking for the" language to be installed" and "network setting and etc."
    then it starts communicating with the jump server to pick up the jumpstart script and etc still working great. but when it start to install, it returned with "ERROR no disk found"
    I am sure there are two 600G disk on the server. not sure why it think there is no disk during the installation. googled it and some said something related to raid and i cannot get a conclusion.
    {0} ok show-disks
    a) /pci@700/pci@1/pci@0/pci@0/LSI,sas@0/disk
    b) /pci@500/pci@1/pci@0/pci@1/pci@0/pci@2/SUNW,qlc@0,1/fp@0,0/disk
    c) /pci@500/pci@1/pci@0/pci@1/pci@0/pci@2/SUNW,qlc@0/fp@0,0/disk
    d) /pci@400/pci@2/pci@0/pci@1/pci@0/pci@2/SUNW,qlc@0,1/fp@0,0/disk
    e) /pci@400/pci@2/pci@0/pci@1/pci@0/pci@2/SUNW,qlc@0/fp@0,0/disk
    {0} ok devalias
    screen /pci@400/pci@1/pci@0/pci@7/pci@0/display@0
    mouse /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/device@1/mouse@1
    keyboard /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/device@1/keyboard@0
    disk7 /pci@700/pci@1/pci@0/pci@0/@0/disk@p3
    disk6 /pci@700/pci@1/pci@0/pci@0/@0/disk@p2
    disk5 /pci@700/pci@1/pci@0/pci@0/@0/disk@p1
    disk4 /pci@700/pci@1/pci@0/pci@0/@0/disk@p0
    scsi1 /pci@700/pci@1/pci@0/pci@0/@0
    net3 /pci@600/pci@2/pci@0/pci@3/network@0,1
    net2 /pci@600/pci@2/pci@0/pci@3/network@0
    rcdrom /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2/disk@0
    rkeyboard /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/device@4/keyboard@0
    rscreen /pci@400/pci@1/pci@0/pci@7/pci@0/display@0:r1280x1024x60
    net1 /pci@400/pci@1/pci@0/pci@2/network@0,1
    net0 /pci@400/pci@1/pci@0/pci@2/network@0
    net /pci@400/pci@1/pci@0/pci@2/network@0
    disk3 /pci@400/pci@1/pci@0/pci@0/@0/disk@p3
    disk2 /pci@400/pci@1/pci@0/pci@0/@0/disk@p2
    disk1 /pci@400/pci@1/pci@0/pci@0/@0/disk@p1
    disk0 /pci@400/pci@1/pci@0/pci@0/@0/disk@p0
    disk /pci@400/pci@1/pci@0/pci@0/@0/disk@p0
    scsi0 /pci@400/pci@1/pci@0/pci@0/@0
    scsi /pci@400/pci@1/pci@0/pci@0/@0
    virtual-console /virtual-devices@100/console@1
    name aliases
    {0} ok select scsi0
    {0} ok show-children
    FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00
    Target 9
    Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB
    SASDeviceName 5000cca0256f4000 SASAddress 5000cca0256f4001 PhyNum 0
    Target a
    Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB
    SASDeviceName 5000cca025671ff4 SASAddress 5000cca025671ff5 PhyNum 1
    f) /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2/disk
    g) /pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk
    h) /iscsi-hba/disk
    q) NO SELECTION
    {0} ok probe-scsi
    This command may hang the system if a Stop-A or halt command
    has been executed. Please type reset-all to reset the system
    before executing this command.
    Do you wish to continue? (y/n) y
    FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00
    Target 9
    Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB
    SASDeviceName 5000cca0256f4000 SASAddress 5000cca0256f4001 PhyNum 0
    Target a
    Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB
    SASDeviceName 5000cca025671ff4 SASAddress 5000cca025671ff5 PhyNum 1
    {0} ok show-volumes
    No volumes to show
    {0} ok

    nothing seems to come up
    {0} ok boot rcdrom -s
    Boot device: /pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2/hub@2/hub@3/storage@2/disk@0 File and args: -s
    SunOS Release 5.10 Version Generic_137137-09 64-bit
    Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    WARNING: consconfig: cannot find driver for screen device /pci@400/pci@1/pci@0/pci@7/pci@0/display@0
    Booting to milestone "milestone/single-user:default".
    Configuring devices.
    Using RPC Bootparams for network configuration information.
    Requesting System Maintenance Mode
    SINGLE USER MODE
    # format
    Searching for disks...done
    No disks found!

  • Keyboard not responing during boot process (MB 865PE Neo2-LS)

    Hi everyone!
    When I try to access the MB BIOS during the boot process my keyboard is not responding. The keyboard comes a live only after Windows XP has started. I am trying to reinstall my computer and make a few changes in my BIOS setup.
    Does anyone know what I should do to get my keyboard working again
    For the timebeing I am using a Logitech G11 with USB, I have also tried an older Logitech keyboard (the one that used to work) but with the same result.
    Should I try using the PS/2 conetctor instead, I could buy an adapter if that would help?
    All help is greatly appreciated!

    Thanks for the quick response, is there any other way to access the BIOS except by using a keyboard plugged in with ps/2?
    Update: I tried with a PS/2 adaptor but with the same result, the keyboard is completelly dead during the boot process, except for a second or so when it makes a flash.

  • MSI R5750 Will not display during boot, crashes on update

    Hello,
    I recently upgraded my PSU and VGA for my computer and am using a generic LCD monitor (hp L1925).  When I installed the VGA, it will not send any video output unless the monitor is first plugged into the motherboard's video.  When I plug the monitor into the VGA, everything runs fine, the VGA works well.  However, when I try to either install or uninstall drivers, part of the monitor turns black and then loses picture.  Live Update has my system at the latest version of BIOS for both the motherboard and VGA.  Any ideas?     

    I swapped out the video cable between the monitor and the vga, now everything is working very well.  Thanks.

  • [SOLVED (mysteriously)] Arch on USB not recognized during boot

    Hi there,
    I hope, someone can help me with my problem, I have been searching and trying different things for quite some time now, without success.
    I treated myself a new Notebook, Acer Aspire S7 and wanted to run Arch on it. However I am new to Linux and want to try it out on an USB-Stick, to keep the factory install of Win8 intact. (Also, this notebook does not have such a great HDD capacity) Additionally I want to have full disk encryption.
    So I followed the Beginner's Guide with modifications described here and here
    When it came to install the bootloader I chose Grub for EFI.
    I then removed the USB-Stick with the live-Arch, which I used for installation and rebooted and it worked!
    However: As soon as I completely shut down and boot again, the USB-Stick with my installation is no longer recognized. If i boot the live-Arch again, reinstall Grub and then reboot, it again works.
    Here is something, I found strange. This is the output of efibootmgr:
    BootCurrent: 0000
    Timeout: 0 seconds
    BootOrder: 2001,0003,0002,2002,2003
    Boot0000* USB HDD: KingstonDataTraveler 2.0
    Boot0001* Intel HDD0
    Boot0002* Windows Boot Manager
    Boot0003* arch_grub
    Boot2001* EFI USB Device
    Boot2002* EFI DVD/CDROM
    Boot2003* EFI Network
    BootCurrent is 0000, but that number does not appear in the Boot-Order list. Could that be something?
    Well, I hope someone has an idea. I will happily share any information about my setup with you, just ask.
    Thanks,
    Max
    Last edited by MaxT (2014-04-07 08:35:20)

    Sorry for digging that threat up again. I just wanted to share with you the solution to the problem I was having. Perhaps it will save someone else some frustration.
    The Acer Aspire S7 has a dongle that goes in the display port and provides an ethernet and an VGA port. It was that dongle that prevented the USB stick with the Arch installation from being recognized. Done attached -> USB stick was ignored, dongle detached -> it worked.
    I have no idea, why that is the case, but maybe this info is helpful for someone.
    Cheers,
    Max

  • "F11 System Recovery" during boot does not work after Cloning hard drive.

    Problem: “F11 System Recovery” during boot does not work after Cloning hard drive.
    HP Envy m6-1125dx UEFI Notebook Computer with GPT hard drive.
    Original Seagate Hard Disk GPT 700GB with Window 8.0_64 upgraded to Windows 8.1_64
    Startup Menu (F11 System Menu works properly) only on original hard drive.
    Following obtained from Disk Management & diskpart in Command Prompt.
                                     GPT Disk <700GB>
    Partition 1 WINRE NTFS Primary 235MB/400MB [Recovery]
    Partition 2 EFI System FAT32 (LBA) Primary 108MB/260MB [System]
    Partition 3 (NONE) Unformatted Primary 128MB/128MB [Reserve]
    Partition 4 Main NTFS Primary 90GB/195GB [Primary “C”]
    Partition 5 (NONE) NTFS Primary 372MB/450MB [Recovery]
    Partition 6 Data NTFS Primary 7GB/475GB [Primary “E”]
    Partition 7 NTFS Primary 26MB/350MB [Recovery]
    Partition 8 Recovery NTFS Primary 24GB/26GB [Recovery “D”]
    I have Cloned the original hard drive to a new HGST 1TB Hard Drive using four different methods (sector by sector):
    Acronis True Image 2015
    Acronis Backup for PC
    AOMEI Backupper Professional
    Macrium Reflect
    Each time the cloning process completes successfully and has the same original partition arrangement. The computer works properly except when trying to use the “F11 System Menu” key during boot. It gives the following error message:
    “Recovery
    Your PC needs to be repaired
    A required device isn’t connected or can’t be accessed.
    Error code: 0xc0000225
    You need to use the recovery tools on your installation media. If you don’t have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. “
    Any suggestions why the F11 System Recovery does not work during boot and how to fix the problem would be appreciated. I have does various disk checking and file checking on both the original and new hard drive with no errors.
    Thank you in advanced.

    Hi,
    How did you clone the HDD ? One-for-one or different method ?
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2011 MBP upgraded to Mavericks.

    hello,
    And thank you in advance.
    I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 20011 MBP upgraded to OS X 10.9 Mavericks. Any ideas?
    I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive. I tried to create an iso image from my Windows XP machine but recieved messages that Windows 8.1 could not run on XP.  I've ordered the Windows 8.1 backup media.
    Any way to proceed?
    Thanks  Tim

    download the win 8 iso from here;
    http://getintopc.com/softwares/operating-systems/download-windows-8-pro/
    then start over. install on to your usb along with the support software.

  • Installer disk not found message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks?

    I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks. Any ideas?
    I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive.
    Thanks  Tim 

    You might have better luck in the Boot Camp community. I'll ask the hosts to relocate your post.
    Boot Camp Community

  • Oracle 11g XE listener does not start automatically during boot

    Hi,
    This happened to me recently I just wanted to share it with you.
    For development I was running Standard Edition, at some point I decided to run also XE on the same server for another reasons. Everything was working fine, except that after restart of the server, the XE listener is not starting automatically. Debugging the startup script I found that this happens because of a bug in the code, which assumes that XE listener is running if it finds the word LISTENER within the processes list. I didn't found any obligation in the docs for running XE without any other databases on the same host.
    In file /etc/init.d/oracle-xe, at line 556 the code is failing:
    1     + status='oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit'
    2     + '[' 'oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit' == '' ']'
    As you can see I have another listener(the one for SE) running and because of the XE startup script found the keyword LISTENER it’s supposing that the XE LISTENER is already running.
    To fix this simply change line 556 from:
    1     status=`ps -ef | grep tns | grep oracle`
    To:
    1     status=`ps -ef | grep tns | grep oracle | grep xe`
    Now XE listener is started automatically during boot.
    Sve
    Blog: http://sve.to
    Twitter: sgyurov

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

Maybe you are looking for