Boot to cursor "i965_irq_handler" error

English Install/Boot/Login
1

I have a dual-boot system between Windows 7 (which I have been trying to get upgraded to Windows 10 but it keeps failing), and openSUSE Tumbleweed running KDE. Some of the specifications are

ubuntu@ubuntu:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

Currently when I log into openSUSE I am stuck at a blank screen with a cursor (but unable to type anything). I go into tty2 and can log in and have CLI capabilities.

I ran # dmesg and see an error message as the last entry

   34.415296] [drm:i965_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun

the irq handler for i965/i915 leads me to believe it is something with the video drivers. The screen and such does work because I can log into Windows or a Linux Live USB and it works just fine.

When I reboot, I can go into Windows 7, but I just cannot get into openSUSE. I tried “zypper up” and am told there is nothing to do so i suspect I am up-to-date on everything.

I just tried looking into /var/log (I’m typing this from an Ubuntu Live USB) and the folder is empty. I can try from inside openSUSE if that will make any difference.

Thanks

p.s. I have just recently found https://forums.opensuse.org/showthread.php/468837-Possible-conflicts-with-Interrupts?highlight=irq_handler and https://forums.opensuse.org/showthread.php/468132-device-8086-340a-error-status which I am starting to go through now, but they reference nvidia graphics and mine is Intel so we’ll see…

2

Hi
How are you trying to upgrade to windows 10? I’ve used the media creation tool without issues on a fair number of machines…
.
Are you running autologin? If so disable and see if that works to get to you login manager.

3

I don’t run autologin, and it is not making it to the login screen. I get to Grub but then after a moment it turns blank.

I think what is killing me from the Windows 10 USB media is a bad USB flash drive.

4

On 2015-08-28 14:46, dragonbite wrote:

> I think what is killing me from the Windows 10 USB media is a bad USB
> flash drive.

For upgrading Windows on traditional partitioning, grub must not be in
the MBR, and the Windows partition should be marked bootable.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

5

On 2015-08-28 03:16, dragonbite wrote:

> Currently when I log into openSUSE I am stuck at a blank screen with a
> cursor (but unable to type anything). I go into tty2 and can log in and
> have CLI capabilities.

You can try:

login as root
init 3
startx

> I just tried looking into /var/log (I’m typing this from an Ubuntu Live
> USB) and the folder is empty. I can try from inside openSUSE if that
> will make any difference.

No, it is systemd journal. You have to use the command “journalctl” in
openSUSE to see it. Or install a syslog package.

> p.s. I have just recently found http://tinyurl.com/os6sdrj and
> http://tinyurl.com/o9bcwh8 which I am starting to go through now, but
> they reference nvidia graphics and mine is Intel so we’ll see…

If they are for nvidia, don’t even read them.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

6

Hi
Change the intel xorg conf file and set the acceleration to uxa rather than the current default sna.

7

I turned around and got Windows 10 installed, a clean install.

NOTE TO PEOPLE: I had on one machine successfully forced and upgrade from Windows 7 to Windows 10 and while it took a long time (probably installing the Windows 7 updates I didn’t already run) it worked fine and the Windows 7 product key was accepted without batting an eyelash.

So on the laptop I ended up doing a clean-install (but openSUSE is still tucked away, safe, in its partitions). Because some Windows 7 updates failed I had to do a clean install. Unfortunately this means the Windows 7 product key was never updated in Microsoft’s systems to include Windows 10 and as such is not accepted as a valid product key.

I could see about throwing in an extra hard drive, install Windows 7 and try the forced-upgrade path that worked in the desktop mentioned above and once it is done go back to the SSSD and re-enter the possilby updated Product Key.

Although I got a key from MSDN so all’s good for now.

So for the openSUSE side, I’ll need to run the grub setup first and then tackle the irq issue again. I can always re-install Tumbleweed if necessary and do get a slight itching to do so and switch from Plasma 5 to Gnome.