HP Mini 1000 blank screen on boot (+other issues).

89c51 · 2014-11-01 19:36:43

I got my hands on a HP Mini 1000 Vivienne Tam (don't laugh please ) and i am having trouble getting it to boot properly.

The only way to get it to boot to something i can type is by passing nomodeset to the syslinux command line.

So far i tried

video=SVIDEO-1:d

&

video=VGA-1:1024x600

with no luck.

I also added i915 & intel_agp to MODULES in mkinitcpio.conf and mkinitcpio -p linux.

Any ideas what i might be missing.

Last edited by 89c51 (2014-11-03 11:47:07)

89c51 · 2014-11-01 23:38:06

Also one more thing.

When i boot with nomodeset and try to ssh into it (the keyboard on the HP is semi-broken) it has to fail 3 times before i can. What do i have to configure to get it from the first try.

jasonwryan · 2014-11-01 23:47:19

That would depend upon why it fails the first two times. Use the verbose option.

89c51 · 2014-11-02 00:32:25

Played with it a bit more and sometimes it works first try.

Anyway the thing is that the laptop boots with acpi=off. But then i have no keyboard on it. And i'll look into it tomorrow. It's late.

BTW does acpi=off mess with KMS or graphics drivers in a way. I tried launching weston and it failed. Also the i915 module was missing.

89c51 · 2014-11-02 07:47:38

I booted it with acpi_oci=Linux and got the following kernel message. Screen still blank but i was able to ssh in it.

Nov 02 09:42:10 testland kernel: BUG: unable to handle kernel NULL pointer dereference at 00000008
Nov 02 09:42:11 testland kernel: IP: [<f84cdc7c>] drm_mm_insert_node_in_range_generic+0x4c/0x2e0 [drm]
Nov 02 09:42:11 testland kernel: *pde = 00000000 
Nov 02 09:42:12 testland kernel: Oops: 0000 [#1] PREEMPT SMP 
Nov 02 09:42:12 testland kernel: Modules linked in: iTCO_vendor_support cfg80211(+) ecb hwmon btusb hp_wmi(+) uvcvideo sparse_keymap pcspkr evdev i915(+) ssb bluetooth videobuf2_
Nov 02 09:42:12 testland kernel: CPU: 1 PID: 165 Comm: systemd-udevd Not tainted 3.17.1-1-ARCH #1
Nov 02 09:42:12 testland kernel: Hardware name: Hewlett-Packard HP Mini/361A, BIOS 361A0 Ver. F.10 12/25/2008
Nov 02 09:42:13 testland kernel: task: f5155140 ti: f4a14000 task.ti: f4a14000
Nov 02 09:42:13 testland kernel: EIP: 0060:[<f84cdc7c>] EFLAGS: 00010286 CPU: 1
Nov 02 09:42:13 testland kernel: EIP is at drm_mm_insert_node_in_range_generic+0x4c/0x2e0 [drm]
Nov 02 09:42:13 testland kernel: EAX: 00000000 EBX: fffffff8 ECX: 0012c000 EDX: f35e7f00
Nov 02 09:42:13 testland kernel: ESI: 00000000 EDI: f2a340e4 EBP: f4a158a8 ESP: f4a1586c
Nov 02 09:42:13 testland kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov 02 09:42:13 testland kernel: CR0: 80050033 CR2: 00000008 CR3: 34a07000 CR4: 000007d0
Nov 02 09:42:13 testland kernel: Stack:
Nov 02 09:42:13 testland kernel:  f4a15878 f35e7f00 00000060 f916f8dc 000080d0 00000000 0012c000 f2a340e4
Nov 02 09:42:13 testland kernel:  f2a340e4 f4a158a8 f916f8dc a27f9f4b 10000000 00010000 f499f900 f4a15910
Nov 02 09:42:13 testland kernel:  f9174929 00010000 00000000 00000000 10000000 00000000 00000000 000020dc
Nov 02 09:42:13 testland kernel: Call Trace:
Nov 02 09:42:14 testland kernel:  [<f916f8dc>] ? i915_gem_obj_lookup_or_create_vma+0x3c/0x130 [i915]
Nov 02 09:42:14 testland kernel:  [<f916f8dc>] ? i915_gem_obj_lookup_or_create_vma+0x3c/0x130 [i915]
Nov 02 09:42:14 testland kernel:  [<f9174929>] i915_gem_object_pin+0x439/0x6d0 [i915]
Nov 02 09:42:14 testland kernel:  [<f9176b2c>] i915_gem_object_pin_to_display_plane+0x8c/0x1a0 [i915]
Nov 02 09:42:14 testland kernel:  [<f91a04c9>] intel_pin_and_fence_fb_obj+0xc9/0x150 [i915]
Nov 02 09:42:14 testland kernel:  [<f91a2e3f>] __intel_set_mode+0x55f/0x14e0 [i915]
Nov 02 09:42:14 testland kernel:  [<f84ce499>] ? drm_mode_object_get_reg+0x69/0x80 [drm]
Nov 02 09:42:14 testland kernel:  [<f91aadb3>] intel_set_mode+0x23/0x40 [i915]
Nov 02 09:42:14 testland kernel:  [<f91aafb5>] intel_get_load_detect_pipe+0x1e5/0x480 [i915]
Nov 02 09:42:14 testland kernel:  [<f91acd91>] intel_modeset_setup_hw_state+0xb21/0xc10 [i915]
Nov 02 09:42:14 testland kernel:  [<f918e40f>] ? gen4_read32+0x3f/0xd0 [i915]
Nov 02 09:42:14 testland kernel:  [<f918e730>] ? gen4_write64+0xd0/0xd0 [i915]
Nov 02 09:42:14 testland kernel:  [<f91ad54a>] intel_modeset_init+0x6ca/0x1430 [i915]
Nov 02 09:42:14 testland kernel:  [<f9181f15>] ? i915_enable_pipestat+0xa5/0x130 [i915]
Nov 02 09:42:14 testland kernel:  [<f91824c2>] ? i915_irq_postinstall+0xf2/0x100 [i915]
Nov 02 09:42:14 testland kernel:  [<f84c6bf9>] ? drm_irq_install+0xa9/0x180 [drm]
Nov 02 09:42:14 testland kernel:  [<f91da1d9>] i915_driver_load+0xdd9/0xfc0 [i915]
Nov 02 09:42:14 testland kernel:  [<f91d7130>] ? i915_switcheroo_set_state+0x90/0x90 [i915]
Nov 02 09:42:14 testland kernel:  [<c123eb82>] ? kobject_uevent_env+0x162/0x570
Nov 02 09:42:14 testland kernel:  [<c123eb82>] ? kobject_uevent_env+0x162/0x570
Nov 02 09:42:14 testland kernel:  [<c123e8e0>] ? kobj_ns_drop+0x60/0x60
Nov 02 09:42:14 testland kernel:  [<c11dd8e3>] ? sysfs_add_file+0x23/0x30
Nov 02 09:42:14 testland kernel:  [<c13116c4>] ? get_device+0x14/0x30
Nov 02 09:42:14 testland kernel:  [<c1316862>] ? klist_class_dev_get+0x12/0x20
Nov 02 09:42:14 testland kernel:  [<c1465e8e>] ? klist_node_init+0x2e/0x50
Nov 02 09:42:14 testland kernel:  [<c1465f24>] ? klist_add_tail+0x34/0x40
Nov 02 09:42:14 testland kernel:  [<c1312bd4>] ? device_add+0x1a4/0x600
Nov 02 09:42:14 testland kernel:  [<f84c9cae>] drm_dev_register+0x8e/0xd0 [drm]
Nov 02 09:42:14 testland kernel:  [<f84cc0b9>] drm_get_pci_dev+0xa9/0x1c0 [drm]
Nov 02 09:42:14 testland kernel:  [<c11db975>] ? kernfs_new_node+0x35/0x50
Nov 02 09:42:14 testland kernel:  [<f9150405>] i915_pci_probe+0x35/0x60 [i915]
Nov 02 09:42:14 testland kernel:  [<c127530f>] pci_device_probe+0x6f/0xd0
Nov 02 09:42:14 testland kernel:  [<c11ddd05>] ? sysfs_create_link+0x25/0x50
Nov 02 09:42:14 testland kernel:  [<c1315983>] driver_probe_device+0x93/0x3c0
Nov 02 09:42:14 testland kernel:  [<c11dd9f7>] ? sysfs_create_dir_ns+0x37/0x90
Nov 02 09:42:14 testland kernel:  [<c127523a>] ? pci_match_device+0xca/0x100
Nov 02 09:42:14 testland kernel:  [<c1315d69>] __driver_attach+0x79/0x80
Nov 02 09:42:14 testland kernel:  [<c1315cf0>] ? __device_attach+0x40/0x40
Nov 02 09:42:14 testland kernel:  [<c1313c67>] bus_for_each_dev+0x57/0xa0
Nov 02 09:42:14 testland kernel:  [<c131547e>] driver_attach+0x1e/0x20
Nov 02 09:42:14 testland kernel:  [<c1315cf0>] ? __device_attach+0x40/0x40
Nov 02 09:42:14 testland kernel:  [<c13150c7>] bus_add_driver+0x157/0x240
Nov 02 09:42:14 testland kernel:  [<f9217000>] ? 0xf9217000
Nov 02 09:42:14 testland kernel:  [<f9217000>] ? 0xf9217000
Nov 02 09:42:14 testland kernel:  [<c131652d>] driver_register+0x5d/0xf0
Nov 02 09:42:14 testland kernel:  [<c1274b53>] __pci_register_driver+0x33/0x40
Nov 02 09:42:14 testland kernel:  [<f84cc2bd>] drm_pci_init+0xed/0x110 [drm]
Nov 02 09:42:14 testland kernel:  [<f9217000>] ? 0xf9217000
Nov 02 09:42:14 testland kernel:  [<f9217083>] i915_init+0x83/0x85 [i915]
Nov 02 09:42:14 testland kernel:  [<c1000496>] do_one_initcall+0xc6/0x200
Nov 02 09:42:14 testland kernel:  [<f9217000>] ? 0xf9217000
Nov 02 09:42:14 testland kernel:  [<c1164545>] ? kfree+0x165/0x170
Nov 02 09:42:14 testland kernel:  [<c1151da5>] ? __vunmap+0xa5/0xf0
Nov 02 09:42:14 testland kernel:  [<c1151da5>] ? __vunmap+0xa5/0xf0
Nov 02 09:42:14 testland kernel:  [<c1151da5>] ? __vunmap+0xa5/0xf0
Nov 02 09:42:14 testland kernel:  [<c10c9d4b>] load_module+0x1b4b/0x2390
Nov 02 09:42:14 testland kernel:  [<c10ca63f>] SyS_init_module+0xaf/0x120
Nov 02 09:42:14 testland kernel:  [<c146f197>] sysenter_do_call+0x12/0x12
Nov 02 09:42:14 testland kernel: Code: db 0f 85 58 02 00 00 89 c7 89 f3 89 45 e4 83 e3 02 8b 40 04 0f 44 07 89 5d d8 89 4d dc 89 55 c8 39 c7 8d 58 f8 0f 84 84 02 00 00 <f6> 40 08
Nov 02 09:42:14 testland kernel: EIP: [<f84cdc7c>] drm_mm_insert_node_in_range_generic+0x4c/0x2e0 [drm] SS:ESP 0068:f4a1586c
Nov 02 09:42:14 testland kernel: CR2: 0000000000000008
Nov 02 09:42:14 testland kernel: ---[ end trace 7561a27c7058e4d2 ]---

&

Nov 02 09:42:20 testland kernel: [drm:i915_irq_handler] *ERROR* pipe A underrun

Last edited by 89c51 (2014-11-02 08:08:24)

89c51 · 2014-11-03 11:55:10

Two more things that happen:

systemd-analyze
Bootup is not yet finished. Please try again later.

Is this caused by the display-manager.service not being present? Two other things that look suspicious are:

systemd-backlight@backlight:intel_backlight.service                                      loaded    activating start

&

 session-c1.scope                                                                         loaded    active     abandoned

i am logged in it with mosh.

Also there is this weird thing with the network not always starting (no lights in the port). That probably explains why i wasn't able to ssh in it. I use network manager. Sometimes it doesn't start and needs a reboot. Next time it starts.

89c51 · 2014-11-03 14:29:54

Kernel bug reported upstream. Installed lts and it seems to work ok.

piroko · 2015-04-22 12:16:32

Do you happen to have a link to that kernel bug report? I have the same problem with my own HP Mini 1000 and would like to track the issue. Thanks!

Arch Linux

#1 2014-11-01 19:36:43

HP Mini 1000 blank screen on boot (+other issues).

#2 2014-11-01 23:38:06

Re: HP Mini 1000 blank screen on boot (+other issues).

#3 2014-11-01 23:47:19

Re: HP Mini 1000 blank screen on boot (+other issues).

#4 2014-11-02 00:32:25

Re: HP Mini 1000 blank screen on boot (+other issues).

#5 2014-11-02 07:47:38

Re: HP Mini 1000 blank screen on boot (+other issues).

#6 2014-11-03 11:55:10

Re: HP Mini 1000 blank screen on boot (+other issues).

#7 2014-11-03 14:29:54

Re: HP Mini 1000 blank screen on boot (+other issues).

#8 2015-04-22 12:16:32

Re: HP Mini 1000 blank screen on boot (+other issues).

Board footer