Can't install on Lenovo T400

[Frank]

Hello,

I try to install QubesOS on my Lenovo T400.
After the kernel is loaded (i think it is the kernel), I only see a
black screen.
After a while no activity of the system is observed. So i can't install
the OS.

At the moment i use Ubuntu on the system.

Because the hardware is very long, thanks for you help.

This is my Hardware:

frank-thinkpad
Beschreibung: Computer
Breite: 64 bits
Fähigkeiten: smbios-2.4 vsyscall32
*-core
Beschreibung: Motherboard
Physische ID: 0
*-memory
Beschreibung: Systemspeicher
Physische ID: 0
Größe: 7878MiB
*-cpu
Produkt: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz
Hersteller: Intel Corp.
Physische ID: 1
Bus-Informationen: cpu@0
Größe: 2533MHz
Kapazität: 2534MHz
Breite: 64 bits
Fähigkeiten: fpu fpu_exception wp vme de pse tsc msr pae mce
cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse
sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts
nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
cpufreq
*-pci
Beschreibung: Host bridge
Produkt: Mobile 4 Series Chipset Memory Controller Hub
Hersteller: Intel Corporation
Physische ID: 100
Bus-Informationen: pci@0000:00:00.0
Version: 07
Breite: 32 bits
Takt: 33MHz
Konfiguration: driver=agpgart-intel
Ressourcen: irq:0
*-display:0
Beschreibung: VGA compatible controller
Produkt: Mobile 4 Series Chipset Integrated Graphics
Controller
Hersteller: Intel Corporation
Physische ID: 2
Bus-Informationen: pci@0000:00:02.0
Version: 07
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: msi pm vga_controller bus_master cap_list rom
Konfiguration: driver=i915 latency=0
Ressourcen: irq:31 memory:f4400000-f47fffff
memory:d0000000-dfffffff ioport:1800(Größe=8)
*-display:1 UNGEFORDERT
Beschreibung: Display controller
Produkt: Mobile 4 Series Chipset Integrated Graphics
Controller
Hersteller: Intel Corporation
Physische ID: 2.1
Bus-Informationen: pci@0000:00:02.1
Version: 07
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pm bus_master cap_list
Konfiguration: latency=0
Ressourcen: memory:f4200000-f42fffff
*-communication:0
Beschreibung: Communication controller
Produkt: Mobile 4 Series Chipset MEI Controller
Hersteller: Intel Corporation
Physische ID: 3
Bus-Informationen: pci@0000:00:03.0
Version: 07
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pm msi bus_master cap_list
Konfiguration: driver=mei_me latency=0
Ressourcen: irq:30 memory:fc226800-fc22680f
*-communication:1
Beschreibung: Serial controller
Produkt: Mobile 4 Series Chipset AMT SOL Redirection
Hersteller: Intel Corporation
Physische ID: 3.3
Bus-Informationen: pci@0000:00:03.3
Version: 07
Breite: 32 bits
Takt: 66MHz
Fähigkeiten: pm msi 16550 bus_master cap_list
Konfiguration: driver=serial latency=0
Ressourcen: irq:17 ioport:1830(Größe=8)
memory:fc024000-fc024fff
*-network
Beschreibung: Ethernet interface
Produkt: 82567LM Gigabit Network Connection
Hersteller: Intel Corporation
Physische ID: 19
Bus-Informationen: pci@0000:00:19.0
Logischer Name: eth0
Version: 03
Seriennummer: 00:27:13:68:ea:c6
Kapazität: 1Gbit/s
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pm msi bus_master cap_list ethernet physical
tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
Konfiguration: autonegotiation=on broadcast=yes
driver=e1000e driverversion=2.3.2-k firmware=1.8-3 latency=0 link=no
multicast=yes port=twisted pair
Ressourcen: irq:28 memory:fc000000-fc01ffff
memory:fc025000-fc025fff ioport:1840(Größe=32)
*-usb:0
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #4
Hersteller: Intel Corporation
Physische ID: 1a
Bus-Informationen: pci@0000:00:1a.0
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:20 ioport:1860(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@3
Logischer Name: usb3
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:1
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #5
Hersteller: Intel Corporation
Physische ID: 1a.1
Bus-Informationen: pci@0000:00:1a.1
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:21 ioport:1880(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@4
Logischer Name: usb4
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:0 UNGEFORDERT
Beschreibung: Allgemeines USB-Gerät
Produkt: Fingerprint Sensor
Hersteller: AuthenTec, Inc.
Physische ID: 1
Bus-Informationen: usb@4:1
Version: 17.03
Fähigkeiten: usb-2.00
Konfiguration: maxpower=100mA speed=12Mbit/s
*-usb:1
Beschreibung: Bluetooth-Schnittstelle
Produkt: ThinkPad Bluetooth with Enhanced Data Rate II
Hersteller: Lenovo Computer Corp
Physische ID: 2
Bus-Informationen: usb@4:2
Version: 3.99
Fähigkeiten: bluetooth usb-2.00
Konfiguration: driver=btusb maxpower=100mA
speed=12Mbit/s
*-usb:2
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #6
Hersteller: Intel Corporation
Physische ID: 1a.2
Bus-Informationen: pci@0000:00:1a.2
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:22 ioport:18a0(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@5
Logischer Name: usb5
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:3
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB2 EHCI Controller #2
Hersteller: Intel Corporation
Physische ID: 1a.7
Bus-Informationen: pci@0000:00:1a.7
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pm debug ehci bus_master cap_list
Konfiguration: driver=ehci-pci latency=0
Ressourcen: irq:23 memory:fc226c00-fc226fff
*-usbhost
Produkt: EHCI Host Controller
Hersteller: Linux 3.19.0-33-generic ehci_hcd
Physische ID: 1
Bus-Informationen: usb@1
Logischer Name: usb1
Version: 3.19
Fähigkeiten: usb-2.00
Konfiguration: driver=hub slots=6 speed=480Mbit/s
*-multimedia
Beschreibung: Audio device
Produkt: 82801I (ICH9 Family) HD Audio Controller
Hersteller: Intel Corporation
Physische ID: 1b
Bus-Informationen: pci@0000:00:1b.0
Version: 03
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pm msi pciexpress bus_master cap_list
Konfiguration: driver=snd_hda_intel latency=0
Ressourcen: irq:33 memory:fc020000-fc023fff
*-pci:0
Beschreibung: PCI bridge
Produkt: 82801I (ICH9 Family) PCI Express Port 1
Hersteller: Intel Corporation
Physische ID: 1c
Bus-Informationen: pci@0000:00:1c.0
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pci pciexpress msi pm normal_decode
bus_master cap_list
Konfiguration: driver=pcieport
Ressourcen: irq:24 ioport:8000(Größe=4096)
memory:c0000000-c01fffff ioport:c0200000(Größe=2097152)
*-pci:1
Beschreibung: PCI bridge
Produkt: 82801I (ICH9 Family) PCI Express Port 2
Hersteller: Intel Corporation
Physische ID: 1c.1
Bus-Informationen: pci@0000:00:1c.1
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pci pciexpress msi pm normal_decode
bus_master cap_list
Konfiguration: driver=pcieport
Ressourcen: irq:25 ioport:9000(Größe=4096)
memory:f4300000-f43fffff ioport:c0400000(Größe=2097152)
*-network
Beschreibung: Kabellose Verbindung
Produkt: Ultimate N WiFi Link 5300
Hersteller: Intel Corporation
Physische ID: 0
Bus-Informationen: pci@0000:03:00.0
Logischer Name: wlan0
Version: 00
Seriennummer: 00:21:6a:b3:17:3e
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pm msi pciexpress bus_master cap_list
ethernet physical wireless
Konfiguration: broadcast=yes driver=iwlwifi
driverversion=3.19.0-33-generic firmware=8.83.5.1 build 33692
ip=192.168.43.181 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
Ressourcen: irq:32 memory:f4300000-f4301fff
*-pci:2
Beschreibung: PCI bridge
Produkt: 82801I (ICH9 Family) PCI Express Port 4
Hersteller: Intel Corporation
Physische ID: 1c.3
Bus-Informationen: pci@0000:00:1c.3
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pci pciexpress msi pm normal_decode
bus_master cap_list
Konfiguration: driver=pcieport
Ressourcen: irq:26 ioport:2000(Größe=4096)
memory:f8000000-f9ffffff ioport:f4000000(Größe=1048576)
*-pci:3
Beschreibung: PCI bridge
Produkt: 82801I (ICH9 Family) PCI Express Port 5
Hersteller: Intel Corporation
Physische ID: 1c.4
Bus-Informationen: pci@0000:00:1c.4
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pci pciexpress msi pm normal_decode
bus_master cap_list
Konfiguration: driver=pcieport
Ressourcen: irq:27 ioport:3000(Größe=4096)
memory:fa000000-fbffffff ioport:f4100000(Größe=1048576)
*-usb:4
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #1
Hersteller: Intel Corporation
Physische ID: 1d
Bus-Informationen: pci@0000:00:1d.0
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:16 ioport:18c0(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@6
Logischer Name: usb6
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:5
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #2
Hersteller: Intel Corporation
Physische ID: 1d.1
Bus-Informationen: pci@0000:00:1d.1
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:17 ioport:18e0(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@7
Logischer Name: usb7
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:6
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB UHCI Controller #3
Hersteller: Intel Corporation
Physische ID: 1d.2
Bus-Informationen: pci@0000:00:1d.2
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: uhci bus_master cap_list
Konfiguration: driver=uhci_hcd latency=0
Ressourcen: irq:18 ioport:1c00(Größe=32)
*-usbhost
Produkt: UHCI Host Controller
Hersteller: Linux 3.19.0-33-generic uhci_hcd
Physische ID: 1
Bus-Informationen: usb@8
Logischer Name: usb8
Version: 3.19
Fähigkeiten: usb-1.10
Konfiguration: driver=hub slots=2 speed=12Mbit/s
*-usb:7
Beschreibung: USB controller
Produkt: 82801I (ICH9 Family) USB2 EHCI Controller #1
Hersteller: Intel Corporation
Physische ID: 1d.7
Bus-Informationen: pci@0000:00:1d.7
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pm debug ehci bus_master cap_list
Konfiguration: driver=ehci-pci latency=0
Ressourcen: irq:19 memory:fc227000-fc2273ff
*-usbhost
Produkt: EHCI Host Controller
Hersteller: Linux 3.19.0-33-generic ehci_hcd
Physische ID: 1
Bus-Informationen: usb@2
Logischer Name: usb2
Version: 3.19
Fähigkeiten: usb-2.00
Konfiguration: driver=hub slots=6 speed=480Mbit/s
*-pci:4
Beschreibung: PCI bridge
Produkt: 82801 Mobile PCI Bridge
Hersteller: Intel Corporation
Physische ID: 1e
Bus-Informationen: pci@0000:00:1e.0
Version: 93
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pci subtractive_decode bus_master cap_list
Ressourcen: ioport:4000(Größe=16384)
memory:f4800000-f7ffffff ioport:f0000000(Größe=67108864)
*-pcmcia
Beschreibung: CardBus bridge
Produkt: RL5c476 II
Hersteller: Ricoh Co Ltd
Physische ID: 0
Bus-Informationen: pci@0000:15:00.0
Version: ba
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pcmcia bus_master cap_list
Konfiguration: driver=yenta_cardbus latency=176
maxlatency=5 mingnt=128
Ressourcen: iomemory:b01716150-b0171614f irq:16
memory:f4800000-f4800fff ioport:4000(Größe=256) ioport:4400(Größe=256)
memory:f0000000-f3ffffff memory:c4000000-c7ffffff
*-firewire
Beschreibung: FireWire (IEEE 1394)
Produkt: R5C832 IEEE 1394 Controller
Hersteller: Ricoh Co Ltd
Physische ID: 0.1
Bus-Informationen: pci@0000:15:00.1
Version: 04
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: pm ohci bus_master cap_list
Konfiguration: driver=firewire_ohci latency=32
maxlatency=4 mingnt=2
Ressourcen: irq:17 memory:f4801000-f48017ff
*-isa
Beschreibung: ISA bridge
Produkt: ICH9M-E LPC Interface Controller
Hersteller: Intel Corporation
Physische ID: 1f
Bus-Informationen: pci@0000:00:1f.0
Version: 03
Breite: 32 bits
Takt: 33MHz
Fähigkeiten: isa bus_master cap_list
Konfiguration: driver=lpc_ich latency=0
Ressourcen: irq:0
*-storage
Beschreibung: SATA controller
Produkt: 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA
Controller [AHCI mode]
Hersteller: Intel Corporation
Physische ID: 1f.2
Bus-Informationen: pci@0000:00:1f.2
Version: 03
Breite: 32 bits
Takt: 66MHz
Fähigkeiten: storage msi pm ahci_1.0 bus_master cap_list
Konfiguration: driver=ahci latency=0
Ressourcen: irq:29 ioport:1c48(Größe=8)
ioport:183c(Größe=4) ioport:1c40(Größe=8) ioport:1838(Größe=4)
ioport:1c20(Größe=32) memory:fc226000-fc2267ff
*-serial UNGEFORDERT
Beschreibung: SMBus
Produkt: 82801I (ICH9 Family) SMBus Controller
Hersteller: Intel Corporation
Physische ID: 1f.3
Bus-Informationen: pci@0000:00:1f.3
Version: 03
Breite: 64 bits
Takt: 33MHz
Konfiguration: latency=0
Ressourcen: memory:fc227400-fc2274ff ioport:1c60(Größe=32)
*-scsi:0
Physische ID: 2
Logischer Name: scsi0
Fähigkeiten: emulated
*-disk
Beschreibung: ATA Disk
Produkt: WDC WD7500BPVT-7
Hersteller: Western Digital
Physische ID: 0.0.0
Bus-Informationen: scsi@0:0.0.0
Logischer Name: /dev/sda
Version: 1A01
Seriennummer: WXQ1E82EDND9
Größe: 698GiB (750GB)
Fähigkeiten: partitioned partitioned:dos
Konfiguration: ansiversion=5 logicalsectorsize=512
sectorsize=4096 signature=73298ced
*-volume:0
Beschreibung: EXT4-Laufwerk
Hersteller: Linux
Physische ID: 1
Bus-Informationen: scsi@0:0.0.0,1
Logischer Name: /dev/sda1
Logischer Name: /
Version: 1.0
Seriennummer: f7f6baf4-084f-4d7d-98f4-0eec4356d5a2
Größe: 690GiB
Kapazität: 690GiB
Fähigkeiten: primary bootable journaled
extended_attributes large_files huge_files dir_nlink extents ext4 ext2
initialized
Konfiguration: created=2015-06-17 21:18:30
filesystem=ext4 lastmountpoint=/ modified=2015-11-17 19:07:02
mount.fstype=ext4
mount.options=rw,relatime,errors=remount-ro,data=ordered
mounted=2015-11-17 19:07:02 state=mounted
*-volume:1
Beschreibung: Extended partition
Physische ID: 2
Bus-Informationen: scsi@0:0.0.0,2
Logischer Name: /dev/sda2
Größe: 8084MiB
Kapazität: 8084MiB
Fähigkeiten: primary extended partitioned
partitioned:extended
*-logicalvolume
Beschreibung: Linux swap / Solaris partition
Physische ID: 5
Logischer Name: /dev/sda5
Kapazität: 8084MiB
Fähigkeiten: nofs
*-scsi:1
Physische ID: 3
Logischer Name: scsi1
Fähigkeiten: emulated
*-cdrom
Beschreibung: DVD-RAM writer
Produkt: DVD RW AD-7930H
Hersteller: Optiarc
Physische ID: 0.0.0
Bus-Informationen: scsi@1:0.0.0
Logischer Name: /dev/cdrom
Logischer Name: /dev/cdrw
Logischer Name: /dev/dvd
Logischer Name: /dev/dvdrw
Logischer Name: /dev/sr0
Version: 1.D0
Fähigkeiten: removable audio cd-r cd-rw dvd dvd-r dvd-ram
Konfiguration: ansiversion=5 status=nodisc

[Michael Carbone]

Frank:

If the problem is not being able to boot into the installer (your
description is not clear as to when this problem happens), you probably
need to make sure that you made the installation USB/DVD correctly,
using dd:

https://www.qubes-os.org/doc/installation-guide/#burning-the-iso-onto-a-dvd-or-usb-stick

specifically make sure that /dev/sdX is used, not /dev/sdX#

--
Michael Carbone

Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>

GPG fingerprint: 2DBE 2014 E7B0 0730 303D 7AAB 99AB 0624 6EEB F5A8

[Frank]

Hello,
to make it clear, with my bad english.
I see the Bootloader and can select between
to verify and start the installer
or
only start the installation.

After the selection the computer loads some files. After this i get a
black screen but the backlight stays active.
No error message is vissible.

I use Ashampoo Burning Studio 2012 to burn the DVD-ISO to a DVD.
Like i did for the Ubuntu or Debian installer.

[Michael Carbone]

Frank:

> Hello,
> to make it clear, with my bad english.
> I see the Bootloader and can select between
> to verify and start the installer
> or
> only start the installation.
>
> After the selection the computer loads some files. After this i get a
> black screen but the backlight stays active.
> No error message is vissible.
>
> I use Ashampoo Burning Studio 2012 to burn the DVD-ISO to a DVD.
> Like i did for the Ubuntu or Debian installer.
>

>> If the problem is not being able to boot into the installer (your
>> description is not clear as to when this problem happens), you probably
>> need to make sure that you made the installation USB/DVD correctly,
>> using dd:
>>
>> https://www.qubes-os.org/doc/installation-guide/#burning-the-iso-onto-a-dvd-or-usb-stick
>>
>>
>> specifically make sure that /dev/sdX is used, not /dev/sdX#
>>

As previously stated, you need to follow the above instructions to
create a bootable USB.

Ashampoo Burning Studio 2012 will not create a usable Qubes installation
USB/DVD, you need to use dd.

Let us know if you run into any issues with booting from installation
USB/DVD created using dd.

--
Michael Carbone
Manager of Security Education
Digital Security Helpline
Access Now | https://www.accessnow.org

[Frank]

The same error. Nothing changed.
I try it with the rufus tool and selected dd-mode. In rufus i can't select the DVD so i used a flashdrive.



And the rufus-log:

Rufus version: 2.5.799
Windows version: Windows 7 SP1 64-bit
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.02~beta2
Locale ID: 0x0407
Found USB 2.0 device 'Lexar JumpDrive USB Device' (05DC:A20A)
1 device found
No volume information for drive 0x82
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 15567, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x5B96B2A3
Drive has an unknown Master Boot Record
Partition 1:
  Type: Hidden NTFS (0x17)
  Size: 3.3 GB (3596615168 bytes)
  Start Sector: 1, Boot: Yes, Recognized: Yes
Scanning image...
ISO analysis:
  Image is an ISO9660 image
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
  Will use '/isolinux/isolinux.cfg' for Syslinux
  Detected Syslinux version: 4.05/2011-12-09 (from '/isolinux/isolinux.bin')
Disk image analysis:
  Image has an unknown Master Boot Record
  Image is a bootable disk image
ISO label: 'Qubes R3.0-rc3 x86_64'
  Size: 3596615680 bytes
  Has a >64 chars filename: Yes
  Has Symlinks: No
  Has a >4GB file: No
  Uses Bootmgr: No
  Uses EFI: No
  Uses Grub 2: No
  Uses Grub4DOS: No
  Uses isolinux: Yes (4.05)
    With an old menu.c32: No
    With an old vesamenu.c32: No
  Uses KolibriOS: No
  Uses ReactOS: No
  Uses WinPE: No
Using image: Qubes-R3.0-rc3-x86_64-DVD.iso

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE2 for write access
No drive letter was assigned...
Will use 'F:' as volume mountpoint
Analyzing existing boot records...
Drive has an unknown Master Boot Record
Volume does not have an x86 Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 2176 sectors
Writing Image...
Drive has an unknown Master Boot Record
Done

Found USB 2.0 device 'Lexar JumpDrive USB Device' (05DC:A20A)
1 device found
No volume information for drive 0x82
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 15567, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x5B96B2A3
Drive has an unknown Master Boot Record
Partition 1:
  Type: Hidden NTFS (0x17)
  Size: 3.3 GB (3596615168 bytes)
  Start Sector: 1, Boot: Yes, Recognized: Yes

[Michael Carbone]

Frank:

> The same error. Nothing changed.
> I try it with the rufus tool and selected dd-mode. In rufus i can't select the
> DVD so i used a flashdrive.
>
>
>

Please make sure to email the list not me individually, and to
bottom-post: https://www.qubes-os.org/doc/mailing-lists/

All I know is the problem you are facing is you are not creating usable
installation USB/DVDs. It is not related to your hardware.

Double-check the settings with Rufus, or boot into Ubuntu and use dd
from the command line. Or try a new installation medium.

--
Michael Carbone

Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>

[Phil]

On Friday, November 20, 2015 at 9:37:12 AM UTC-5, Frank wrote:Hello,

I try to install QubesOS on my Lenovo T400.

After the kernel is loaded (i think it is the kernel), I only see a

black screen.

After a while no activity of the system is observed. So i can't install

the OS.

At the moment i use Ubuntu on the system.

<snip>

The T400 and T410 don't work with the Qubes install if you have VT-d turned on in the BIOS. There's some horrible screen corruption on my box, so after a lot of hacking around, I tried turning VT-d off, and it installed fine. So you might try that.

Cheers

Phil

[Frank]

After a new download.
I do it with the new iso file and verfy the md5.
Also i use dd from Ubuntu to write the iso to the usb-stick.

But still the same error.
The last thing befor i see the blackscreen is a blinking underscore.
And the last thing loaded is initrd or somethin like this.

At the bootloader i can select Troubleshooting and other settings for
graphics. But how can i select the flash drive as source. i only see
dvd, local iso and network?

So I think it's a problem with the grafics?

[Frank]

But I think it is better with VT-d on.
The FAQ means "required for effective isolation of network VMs".

[Tim W]

> Phil )
>

You keep "TOP POSTING"     I know English is not your native language so I will example what we are talking about.  When you click the reply button you need to go all the way to the bottom of the page after the text from the message you are replying to and write your message there.   See how my reply is below the quote and see how yours is above the post that was actually before yours.  Your post should be below his.  Whenever you reply make sure you scroll down to the end of the post ( the text ) and then type your message there.


As to you statement about the Vt-d.  Yes of course you are correct it is much better to have this on.  What the Phil is trying to explain to you is that on your machine T400 there is something wrong in the BIOS and it screws up the way it works VT-d and that is very likley what is causing your issues with the blank screen,.   While it would be best how does that matter if its preventing you from even installing it.   But I think I may have a fix for you.

 Please read below

I went and did some searching for you on this issue.  I am not sure what you can find in your language as the answers I found are all in English.  But if you do a google search on 'lenovo t400 virtualbox Vt-D '  you sjhould be able to finid the same threads I did.  You will also see there are plenty of people that have had this say issue wihen trying to get virutalization running on the T400/410 series Lenovo

Some say that the Intel 8600 does not support Vt-d but this is not true as you can go on Intel ark site and see it supports Vt-d VT-x TXT  it does not support the AES so it will run a bit slower than ones that support the AES instruction set.  So that is not the issue.

Others have concluded that since its clear the Intel E8600 supports this then the issue must be with the Bios implemenation.  This is certainly the most reasonable deduction and is actually in part correct.  That is if the info I found is indeed correct.

I then found a few posts were people had this issue but then did what I guess you could call a 'bios reset' not really sure what the tech correct name for the procedure is but from whatever I can tell it basically does a full power off reset.  This procedure I have seen used when some sort of bios feature is tripped by allowing a battery to go dead while machine is still powered on/sleep mode.  From what I have seen the lenovo techs this trips some sort of saftey function to protect the unit from a power surge or static charge.  Not sure the validity of this as I have been told many incorrect things by various tech supports over the years.

Point being I have now found a few different posts by people who were trying to run virtualization software and after bios enabling vt-d were getting an error message that Vt-d was not enabled.  Specifically it was Linux trying to run virtual box.   They each did some version of this power down bios reset procedure and then upon power up the Vt-d was then working and the error was gone allowing virtual box to run.


Here are a couple of the posts that have pointed to this working:

https://superuser.com/questions/787053/lenovo-t400-virtualization-fails-despite-set-in-bios  (The procedure at the end is the full procedure as I have seen it from Lenovo tech support and what I recommend doing just to be on the safe side.  I post it in full below)

http://comments.gmane.org/gmane.org.user-groups.linux.portland/43176  ( the forth post states where it worked.)

Try doing the following:

Reboot into BIOS settings
Restore to defaults
Enable virtualization
Power down
Remove power cord
Remove battery from laptop
Hold down power button 30 secs by the clock to drain any remaining capacitors
Battery in, power cord in
Power up

After you do that try to install Qubes


If I had not seen variations of this mentioned by more than one or two people I would have discarded it as possibly incorrect but when a number of people with the same issue get it working.........

I hope this works for you. 

[Frank]

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/244de432-0a3d-4862-9e29-4772224dae14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thank you. Top Posting in my language is something else (keep posting and posting to hold the question on the top).
I install Qubes without VT-d and I hope it's secure for normal use. If not please explain why.

Do i have to reinstall Qubes if i try to enable VT-d yet?

Thank you

[Tim W]

No you should be able to turn it on I think.  But if not I am sure someone will speak up.   Try following those instructions at the end of my last post and see if it works.   I am interested to see.  If it does it will also help others to confirm it works.

[pudd...@gmail.com]

Hi. I had a similiar problem with my L520. A BIOS Update helped in my case. Good luck!

[Manuel Amador (Rudd-O)]

On 11/20/2015 06:45 PM, Frank wrote:
> But I think it is better with VT-d on.
> The FAQ means "required for effective isolation of network VMs".

Please stop top-posting. When you write your replies, please reply
below the text you are replying to, preferably right below the sentences
you want to respond to.

Thanks.

--
Rudd-O
http://rudd-o.com/

[Lib berrò]

I'm having the same issue with a Lenovo x230 / Release 3.0 and the operation to reset BIOS didn't solve it, what else should I try? BIOS is updated.

Anyway I am able to install with vt-D disabled but also once with the option "acpi=off" and selecting an old kernel (the other times the installer freezes at the first page, the choose language one)
With ACPI disabled I see troubles setting the IRQ of the USB disk where I'm booting from while with ACPI on and without the "quiet" option the installer stops after the message ACPI tables loaded successfully.

Will I be able to boot once I switch on the vt-D? I'll try later on..

[Steven]

On 01/06/2016 03:59 PM, Lib berrò wrote:
> I'm having the same issue with a Lenovo x230 / Release 3.0 and the
> operation to reset BIOS didn't solve it, what else should I try? BIOS
> is updated.
>
> Anyway I am able to install with vt-D disabled but also once with the
> option "acpi=off" and selecting an old kernel (the other times the
> installer freezes at the first page, the choose language one)
> With ACPI disabled I see troubles setting the IRQ of the USB disk
> where I'm booting from while with ACPI on and without the "quiet"
> option the installer stops after the message ACPI tables loaded
> successfully.
>
> Will I be able to boot once I switch on the vt-D? I'll try later on..

Thinkpad X230 with current Bios (version 2.65) and the correct processor
(!!!) will work (install + normal daily usage) with active VT-x + VT-d
and Qubes OS R3.0. I'm using a Thinkpad X230 with Core i5 3320m + 16 GB
RAM + S3500 SSD successfull with Qubes OS R3.0.

VT-d needs a combination of a chipset supporting VT-d and a processor
supporting VT-d.

So which CPU model does your X230 have?


Best Regards

Steven

[Lib berrò]

Thanks for the reply,
the CPU is VT-d capable, i5-3360M, BIOS 2.65 (8Gb RAM, 250Gb mSata Crucial).

I'm assuming there's a problem in the BIOS but the reset didn't solve it, since HCL and you report compatibility, now I don't know what I should do..

Regarding "acpi=off" setting with vt-d off the option prevent the OS from booting while it boots and works normally with default settings.

[Steven]

On 01/07/2016 11:47 AM, Lib berrò wrote:
> Thanks for the reply,
> the CPU is VT-d capable, i5-3360M, BIOS 2.65 (8Gb RAM, 250Gb mSata
> Crucial).
>
> I'm assuming there's a problem in the BIOS but the reset didn't solve
> it, since HCL and you report compatibility, now I don't know what I
> should do..
>
> Regarding "acpi=off" setting with vt-d off the option prevent the OS
> from booting while it boots and works normally with default settings.

Hmm that is strange. The only "main" difference (you have better CPU +
less RAM) i see is that you are using a mSATA SSD and i an use a normal
2,5'' SATA SSD.

If you have a 2,5'' SATA SSD or hard drive available then you could
check if the issue persist when using the 2,5'' SATA SSD or hard drive
instead of the mSATA SSD.


Best Regards

Steven

[Lib berrò]

I tried with a SATA (not SSD) but nothing changed. So no way of having VT-d I guess.

[Andrew]

Steven:

FWIW I use an mSATA SSD on my x230 and Qubes 3.0 works just fine with
defaults, and has full VT-d support.

Andrew

[Lib berrò]

 Yeah I don't think that's the problem, but I can't get my head around it...BIOS settings are default, no hardware differences, what could it be? Maybe I'll try more BIOS reset ways

[Steven]

On 01/08/2016 09:03 AM, Lib berrò wrote:
> I tried with a SATA (not SSD) but nothing changed. So no way of having VT-d I guess.
>

Ok the only other thing i can think off is that there are some Bios
settings which needs to turned on or to turned off. If you could provide
us the Bios options which are turned off and which are turned on then we
can compare if you want.


Best Regards

Steven

[hbar...@gmail.com]

I use a W500: if I turn on Intel graphics, I have the same issue. If I use "discrete" it works. You may try... BIOS - Config - Display
Guess "switchable" will also _not_ work.
Cheers Heiko

[Lib berrò]

Actually my BIOS settings are resetted to default, which ones would you need?