Acer Ferrari 4000 hangs at "Starting udev..." during openSUSE 12.3 installation

I have an Acer Ferrari 4000 laptop and have successfully installed and update openSUSE 11, and 12 series up until 12.3.
I downloaded the iso for openSUSE 12.3 x86_64 version and created a bootable DVD using K3B, checking the disk using openSUSE 12.2
When I try then to install from my bootable DVD, I get as far as Loading Linux Kernel and then a message, “Starting udev …” appears and the.n nothing happens after that

What video in the machine?

You do get the first menu right?

Graphics chip - integrated into laptop sub-assembly - ATI Radeon mobility x700
The screen that prompts for INSTALLATION &c is presented, and when I choose either INSTALLATION or any other item, the system prompts with various comments until “Starting udev …” appears - then the Laptop is stuck.

I join with the questions. I’m exactly the same. There were no problems with 11.4, 12.1-2. With 12.3 RC2 and final (x64 net) I: Starting udev and … end, waiting for salvation. Turn off all devices in the bios but it did not work. I have a Fujitsu E8420 with nVidia 9300 GS. I changed the repositories to 12.3 and did zypper but the laptops can not do a clean install. >:(

At the first menu enter nomodeset on option line this should force a different driver

Nomodeset work.
During the installation you need to scroll the screen, after installing all great but it’s good.

Install the NVIDIA driver this will speed up the display

With the ATI chip install the ATI driver

I cannot tell if I am having the same problem or not. I have a new Acer Aspirev3-771g with two disks in it. The original with a Windows 8 installation (UEFI, Secure Boot), and a second, new one I put in today which I had hoped to install 12.3 on. I downloaded the iso image, burned a DVD, and started. I get the initial menu screen, choose installation, the kernel loads, I get to the udev line and then the screen goes dark. … but then after about a minute, the first installation screen and then the license screen appears, but it is so dim that it is otherwise unreadable. The machine has an NVIDIA 650M in it. I have seen the instructions to use nomodeset, but I see no option line before I hit enter for the original installation option. If I just start typing, I think I get into grub2, but adding nomodeset to the bottom of the parameter list doesn’t help, I get an error saying nomodeset is not recognized, hit any key to continue and the machine goes to the same dim screens. How do I get to an option line? Thanks for the help.

I have tried several times to get the openSUSE 12.3 installation working. Indeed, using a nomodeset argument on the command line allowed me to install the software, but I do not get an opportunity to set up my ATI mobility x700 video support. The machine will boot to a console prompt only and trying to execute kdm or startx from the root ID explains that the X server is locked in some way. As it happens, I have reverted to openSUSE 12.2 for now, because I can install that system from the start with a GUI and everything seems to have been taken care of, apart from the wireless lan, which is quickly fixed with the sudo /usr/sbin/install_bcm43xx_firmware command while being logged on to the network via a hardwired cable.
Perhaps my laptop is rather ancient compared to most models. Many thanks for your suggestions.

Could have used command line yast to install AMD drivers.

To start the gui then as root do init 5
startx no longer works as a user without changing some permissions

Press ‘e’ on a boot menu to edit it, then append nomodeset to line that starts with “linuxefi”.

If you have GNU/Linux with grub installed, then press ‘E’ as noted and edit the appropriate line (which requires some GNU/Linux experience in such editing).

If you do not yet have GNU/Linux installed, then press the ‘video’ selection (F2 (?) ) in the 1st boot menu and chose ‘nokms’. That stands for no kernel mode setting and that will apply the ‘nomodeset’ boot code.

This does not work when booting on EFI systems.

Thnaks for the Grub2 editing instructions. I also realized that the nomodeset option needed to be put on the kernel line and put it there. So that took care of the problem of installing (mostly, but see below). I now have a 12.3 installed system. However, there are still things obviously broken. The first is the dual boot. Despite the appearance of a Windows entry in the initial Grub2 menu, selecting that choice produces no apparent action. I have looked at the Bootloader configuration in YasT, and Probe Foreign OS is checked. This is perhaps a matter for another thread.

The second problem is graphics related, and may or may not be suitable for another thread. During the installation procedure, the nomodeset technique got me through the software loading and up to the point that the machine reboots to do automatic hardware configuration. After the reboot, I was back to dim-screen mode, and it was only through more squinting that I realized that the configuration process was proceeding. When it finished I was presented with the usual login screen, but again completely dim. I logged into my individual (not root) account, and crossed my fingers … and the desktop came up at ordinary screen illumination levels. This problem has persisted across several subsequent reboots. Is this a graphics driver problem? The nouveau driver was loaded during the install, but it is unclear to me what is actually being used. If I scan Xorg.0.log with grep nvidia I get nothing, and if I scan it with grep intel I get lots, apparently related to using the I810 kernel module for integrated graphics chips. Similarly, the use of the Kinfocenter feature shows Graphical information → OpenGL → Direct Rendering → Driver → Kernel module i915. Where else should I be looking for this graphics information? I have forgotten where the DMESG output shows up to monitor.

If possible could you copy the content of the /var/log/Xorg.0.log file and post it to SUSE Paste and press contribute, That will give you a URL/web address that you can post here to show us the content of that log file. One of the graphic guru’s on this forum may have some ideas.

Also, could you send the command in a terminal

/sbin/lspci -nnk | grep VGA -A2

and post here the output ? That will help us review what openSUSE has assessed wrt the graphics.

I’m beginnnig to think your laptop may have hybrid graphics which may require a modified approach.

First here is the output of the lspci command.linux-ekoo:/var/log # /sbin/lspci -nnk | grep VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Acer Incorporated [ALI] Device [1025:0686]
Kernel driver in use: i915

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107 [GeForce GT 650M] [10de:0fd1] (rev a1)
Subsystem: Acer Incorporated [ALI] Device [1025:0686]
07:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)

So there do seem to be two graphics controllers recognized.

I also append some output from the system log related to the nouveau driver

2013-03-17T16:04:39.767479-07:00 linux-ekoo kernel:     1.241104] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle

 2013-03-17T16:04:39.767480-07:00 linux-ekoo kernel:     1.241124] checking generic (c0000000 12c000) vs hw (a0000000 10000000)
 2013-03-17T16:04:39.767481-07:00 linux-ekoo kernel:     1.241125] checking generic (c0000000 12c000) vs hw (b0000000 2000000)
 2013-03-17T16:04:39.767482-07:00 linux-ekoo kernel:     1.241134] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
 2013-03-17T16:04:39.767483-07:00 linux-ekoo kernel:     1.241649] nouveau    DEVICE][0000:01:00.0] BOOT0  : 0x0e7110a2
 2013-03-17T16:04:39.767484-07:00 linux-ekoo kernel:     1.241652] nouveau    DEVICE][0000:01:00.0] Chipset: GK107 (NVE7)
 2013-03-17T16:04:39.767485-07:00 linux-ekoo kernel:     1.241654] nouveau    DEVICE][0000:01:00.0] Family : NVE0
 2013-03-17T16:04:39.767488-07:00 linux-ekoo kernel:     1.243996] nouveau     VBIOS][0000:01:00.0] checking PRAMIN for image...
 2013-03-17T16:04:39.767490-07:00 linux-ekoo kernel:     1.292375] nouveau     VBIOS][0000:01:00.0] ... signature not found
 2013-03-17T16:04:39.767490-07:00 linux-ekoo kernel:     1.292378] nouveau     VBIOS][0000:01:00.0] checking PROM for image...
 2013-03-17T16:04:39.767491-07:00 linux-ekoo kernel:     1.292445] nouveau     VBIOS][0000:01:00.0] ... signature not found
 2013-03-17T16:04:39.767491-07:00 linux-ekoo kernel:     1.292448] nouveau     VBIOS][0000:01:00.0] checking ACPI for image...
 2013-03-17T16:04:39.767491-07:00 linux-ekoo kernel:     1.342893] usb 2-1: new high-speed USB device number 2 using ehci_hcd
 2013-03-17T16:04:39.767492-07:00 linux-ekoo kernel:     1.414625] nouveau     VBIOS][0000:01:00.0] ... appears to be valid
 2013-03-17T16:04:39.767492-07:00 linux-ekoo kernel:     1.414628] nouveau     VBIOS][0000:01:00.0] using image from ACPI
 2013-03-17T16:04:39.767495-07:00 linux-ekoo kernel:     1.414793] nouveau     VBIOS][0000:01:00.0] BIT signature found
 2013-03-17T16:04:39.767496-07:00 linux-ekoo kernel:     1.414796] nouveau     VBIOS][0000:01:00.0] version
 2013-03-17T16:04:39.767497-07:00 linux-ekoo kernel:     1.415041] nouveau   DEVINIT][0000:01:00.0] adaptor not initialised
 2013-03-17T16:04:39.767498-07:00 linux-ekoo kernel:     1.415044] nouveau     VBIOS][0000:01:00.0] running init tables
 2013-03-17T16:04:39.767499-07:00 linux-ekoo kernel:     1.457076] usb 2-1: New USB device found, idVendor=8087, idProduct=0024

 2013-03-17T16:04:39.767500-07:00 linux-ekoo kernel:     1.457080] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
 2013-03-17T16:04:39.767501-07:00 linux-ekoo kernel:     1.457355] hub 2-1:1.0: USB hub found
 2013-03-17T16:04:39.767505-07:00 linux-ekoo kernel:     1.457449] hub 2-1:1.0: 8 ports detected
 2013-03-17T16:04:39.767506-07:00 linux-ekoo kernel:     1.532768] usb 1-1.1: new high-speed USB device number 3 using ehci_hcd
 2013-03-17T16:04:39.767507-07:00 linux-ekoo kernel:     1.538466] nouveau       MXM][0000:01:00.0] no VBIOS data, nothing to do
 2013-03-17T16:04:39.767508-07:00 linux-ekoo kernel:     1.538490] nouveau       PFB][0000:01:00.0] RAM type: DDR3
 2013-03-17T16:04:39.767508-07:00 linux-ekoo kernel:     1.538492] nouveau       PFB][0000:01:00.0] RAM size: 2048 MiB
 2013-03-17T16:04:39.767509-07:00 linux-ekoo kernel:     1.600316] nouveau W  PGRAPH][0000:01:00.0] disabled, PGRAPH=1 to enable
 2013-03-17T16:04:39.767509-07:00 linux-ekoo kernel:     1.600469] [TTM] Zone  kernel: Available graphics memory: 4004060 kiB
 2013-03-17T16:04:39.767511-07:00 linux-ekoo kernel:     1.600472] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
 2013-03-17T16:04:39.767512-07:00 linux-ekoo kernel:     1.600474] [TTM] Initializing pool allocator
 2013-03-17T16:04:39.767512-07:00 linux-ekoo kernel:     1.600480] [TTM] Initializing DMA pool allocator
 2013-03-17T16:04:39.767513-07:00 linux-ekoo kernel:     1.600497] mtrr: no more MTRRs available
 2013-03-17T16:04:39.767513-07:00 linux-ekoo kernel:     1.600500] nouveau       DRM] VRAM: 2048 MiB
 2013-03-17T16:04:39.767514-07:00 linux-ekoo kernel:     1.600502] nouveau       DRM] GART: 512 MiB
 2013-03-17T16:04:39.767514-07:00 linux-ekoo kernel:     1.600507] nouveau       DRM] BIT BIOS found
 2013-03-17T16:04:39.767516-07:00 linux-ekoo kernel:     1.600510] nouveau       DRM] Bios version
 2013-03-17T16:04:39.767516-07:00 linux-ekoo kernel:     1.600514] nouveau       DRM] TMDS table version 2.0
 2013-03-17T16:04:39.767517-07:00 linux-ekoo kernel:     1.600517] nouveau       DRM] DCB version 4.0
 2013-03-17T16:04:39.767517-07:00 linux-ekoo kernel:     1.600523] [TTM] Finalizing pool allocator
 2013-03-17T16:04:39.767518-07:00 linux-ekoo kernel:     1.600527] [TTM] Finalizing DMA pool allocator
 2013-03-17T16:04:39.767518-07:00 linux-ekoo kernel:     1.600580] [TTM] Zone  kernel: Used memory at exit: 0 kiB
 2013-03-17T16:04:39.767519-07:00 linux-ekoo kernel:     1.600584] [TTM] Zone   dma32: Used memory at exit: 0 kiB
 2013-03-17T16:04:39.767520-07:00 linux-ekoo kernel:     1.601533] pci 0000:00:00.0: Intel Ivybridge Chipset
 2013-03-17T16:04:39.767521-07:00 linux-ekoo kernel:     1.601673] pci 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
 2013-03-17T16:04:39.767521-07:00 linux-ekoo kernel:     1.603029] pci 0000:00:00.0: detected 131072K stolen memory
 2013-03-17T16:04:39.767522-07:00 linux-ekoo kernel:     1.603089] checking generic (c0000000 12c000) vs hw (c0000000 10000000)
 2013-03-17T16:04:39.767522-07:00 linux-ekoo kernel:     1.603091] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver

 2013-03-17T16:04:39.767523-07:00 linux-ekoo kernel:     1.603107] Console: switching to colour dummy device 80x25I find 

 2013-03-17T16:04:39.767524-07:00 linux-ekoo kernel:     1.603197] i915 0000:00:02.0: setting latency timer to 64
 2013-03-17T16:04:39.767527-07:00 linux-ekoo kernel:     1.640507] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear.
 2013-03-17T16:04:39.767528-07:00 linux-ekoo kernel:     1.640632] i915 0000:00:02.0: irq 43 for MSI/MSI-X
 2013-03-17T16:04:39.767529-07:00 linux-ekoo kernel:     1.640640] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
 2013-03-17T16:04:39.767530-07:00 linux-ekoo kernel:     1.640641] [drm] Driver supports precise vblank timestamp query.
 2013-03-17T16:04:39.767531-07:00 linux-ekoo kernel:     1.640754] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
 2013-03-17T16:04:39.767532-07:00 linux-ekoo kernel:     1.640756] vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0

I find particularly puzzling the lines near the end where it says

2013-03-17T16:04:39.767522-07:00 linux-ekoo kernel: 1.603091] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver

2013-03-17T16:04:39.767523-07:00 linux-ekoo kernel: 1.603107] Console: switching to colour dummy device 80x25I find

Let me work on the posting of the Xlog file.

A related question: Should I fear the NVIDIA proprietary driver at this point? It is sitting out there in the NVIDIA repo, and every time I do software management it gets appended to the list of things to be updated/changed along with the choice I was after. There seem to be a lot of posts about problems with NVIDIA drivers (i,e, Hardware forum :“12.3+Nvidia+grub2-efi”)

Here is the link to the paste of my Xorg.0.log. I rebooted in between this message and last so the timestamps don’t match. Sorry.

]SUSE Paste

I checked in my BIOS (Insydeh20 3.7), and I have no ability to disable the onboard graphics capability. Apparently ACER must use this motherboard for several models, some of which do not have separate graphics cards.

The reversion to an 80 x 25 character window perhaps explains why the initial grub menu comes up looking like something one would have seen in 1985 on a CRT. None of the menu entries can be completely seen, and there is no kernel parameter line visible at all. Subsequent output during the boot also appears in this fashion. I guess since the X-server starts later, it then overrides this default in some fashion, and using the internal chip goes on to provide a reasonable, though not high-performance, display.

Grub2 no longer has a parameter line. you make changes by selecting a boot option then press e to edit it. find the vmlinuz line and put the changes on the end. And yes that is silly to be more complicated but that is grub 2 interface, change for the sake of change. Certainly makes it harder for newbees then it needs to be.

Yes this appears to be a hybrid graphic setup with nvidia and intel. I believe users with that setup can resort to trying ‘bumblebee’ and ‘primus’. There is a support thread here on this

I don’t know anything about those applications so I can not tell you where to start in that thread. Sorry. You may wish to either join that running thread, or start your own new support thread on hybrid graphics with intel and nvidia - possibly using bumblebee and primus. There do appear to be a number of users on that thread with ‘bumblebee’ and ‘primus’ experience.

There are problems with the nVidia driver in 12.3. But in truth I can not answer this question, but you may get the answer on the ‘bumblebee’ and ‘primus’ thread. At least I hope that is the case.

Good luck.

Thanks for finding this other thread. I will move over there and see what I can learn.