HCL - Dell Latitude E4300

[Pablo Costa]

Qubes release 2 (R2)

Model Name:     Dell_Inc. Latitude_E4300_

Chipset:        00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)

VGA:            00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)

CPU:            Intel(R) Core(TM)2 Duo CPU     P9600  @ 2.53GHz

BIOS:           A22

VT-x:           Active

VT-d:           Active

* With BIOS A22, and even upgrading to BIOS A24, Qubes-R2-Beta2-x86_64-DVD.iso will hang early on the boot process. Keyboard will not respond and the only way out is to push the power button for some 5 or 7 seconds.

* Passing "nomodeset" to the kernel helps to reach the point where Xorg is launched, although the display is not working (blank screen). Control+Alt+Del gracefully reboots the system but I don't know if the virtual consoles are available Control+Alt+F1..F6 because the screen keeps blank.

* Passing "nomodeset" along with "2" or "3" to the kernel delivers the VT consoles and thus an easy root shell at dom0 although the system is obviously not useful except for debugging purposes. Trying to start the display manager by systemctl start graphical.target leads to the same point as booting with just "nomodeset".

[Zrubecz Laszlo]

On 6 June 2013 21:18, Pablo Costa <modul...@gmail.com> wrote:

> * With BIOS A22, and even upgrading to BIOS A24,
> Qubes-R2-Beta2-x86_64-DVD.iso will hang early on the boot process. Keyboard
> will not respond and the only way out is to push the power button for some 5
> or 7 seconds.
> * Passing "nomodeset" to the kernel helps to reach the point where Xorg is
> launched, although the display is not working (blank screen).
> Control+Alt+Del gracefully reboots the system but I don't know if the
> virtual consoles are available Control+Alt+F1..F6 because the screen keeps
> blank.
> * Passing "nomodeset" along with "2" or "3" to the kernel delivers the VT
> consoles and thus an easy root shell at dom0 although the system is
> obviously not useful except for debugging purposes. Trying to start the
> display manager by systemctl start graphical.target leads to the same point
> as booting with just "nomodeset".

Correct me if I'm wrong but as I see this means I should mark it red (
~not working) in the HCL, right?



--
Zrubi

[Pablo Costa]

On my Dell Latitude E4300, R2B3 runs smoothly, both out of the box and updated as of today. But only with linux 3.9.

3.7 or 3.11 won't boot, as I previously explained.

I've been "living" on this qubes laptop from R2B3 release, and everyday work is quite comfortable.

Thanks a lot! :)

Kernel: 3.9.2-2.pvops.qubes.x86_64

CPU: Intel(R) Core(TM)2 Duo CPU     P9600  @ 2.53GHz
Chipset: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
VGA: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)

00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)

BIOS: A24
VT-x: Active
VT-d: Active

[Alex Hunter-Nickels]

any chance this would still work on a latitude e4300?