sony-vaio-z-series team mailing list archive

[Xavier Hallade <xh@xxxxxxxxxxx>]

Ok, I used the archboot 2010 rc2 for my first install, so I made a new one
with same method as yours, and I have no more crashes, even with kernel
2.6.32, but I have a rendering issue with both kernels : the white prompt is
almost green, and X looks really bad (like it was displayed with 256 random
colors). (vesa works better in 800x600 when I use i915.modeset=0)

dmesg gave me that :
mtrr: no more MTRRs available
[drm] MTRR allocation failed. Graphics performance may suffer.

I tried to add "enable_mtrr_cleanup", without success.

I've found what was causing the crashes with debian and my first install of
archlinux, and it's.. weird : grub2 !
I tried to reinstall archlinux with the 2010 rc2 cd with grub instead of
grub2 and it works like with the 2009 cd.

my model is VPCZ11C5E : 1600x900 without optical drive (and I've replaced
the original hdd with a x25-m ssd)

Xavier.

2010/4/8 Chris Cannam <cannam@xxxxxxxxxxxxxxxxxxxxx>

> On Thu, Apr 8, 2010 at 10:18 PM, Xavier Hallade <xh@xxxxxxxxxxx> wrote:
> > new kernel installed and... no difference.
>
> uh-oh.
>
> > what daemons and modules do you have in your rc.conf and mkinitcpio.conf
> ?
>
> Nothing interesting.  rc.conf daemons:
>
>  syslog-ng network crond dbus hal laptop-mode networkmanager cups sshd gdm
>
> but I've added those gradually, the basic i915 modesetting has been
> working since the start with only "syslog-ng network crond" or
> whatever you get.
>
> mkinitcpio.conf modules is empty, hooks is "base udev autodetect pata
> scsi sata filesystems".
>
> This is a current Arch install, i.e. I ran pacman -Syu before building
> anything, just as soon as I had got the network working -- which IIRC
> I did by downloading and installing the current Arch kernel and
> firmware packages manually via a USB disk since the installer image
> didn't have the correct wireless firmware and I couldn't find anywhere
> the firmware download for it.
>
> I have no special boot options... I was using i8042.nopnp for the
> touchpad; Giacomo Bagnoli has pointed out
> https://patchwork.kernel.org/patch/89139/ for that.
>
> The only BIOS change I have made is to enable virtualisation, though I
> did that before trying and failing to get it all working with Ubuntu.
> And just for completeness, this is a VPC Z (current model) with i5,
> 1920x1080, no optical drive, HDD instead of SSD.
>
> I do appreciate how exasperating this is, I was in exactly the same
> situation as you until I apparently got lucky somehow.  Unfortunately,
> it appears that my getting lucky wasn't actually a result of anything
> specific that I did, so it's hard to know how to reproduce it.
>
>
> Chris
>