[RFH,Status] Sony Vaio VGN-Z11 support

[RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

Dear all,

I am trying to get the beast from $subject more or less working. Here is
the current status running 2.6.27.3:
config: http://www.logic.at/people/preining/sony/vgn-z11vn/config-2.6.27
dmesg output: http://www.logic.at/people/preining/sony/vgn-z11vn/dmesg.txt
DMI decode: http://www.logic.at/people/preining/sony/vgn-z11vn/dmidecode.txt
DSDT: http://www.logic.at/people/preining/sony/vgn-z11vn/DSDT.dsl

Working fine:
  eth Intel e1000e
  wlan: iwlagn (with hangs now and then)
  intel graphics
  nvidia graphics (both built in, switch on the fly on vista possible,
    on linux needs reboot)
  sata harddisk and cd
  usb camera usb_video_class 05ca:18b0 Ricoh Co., Ltd
  audio: HDA
  touchpad: AlpsPS/2
  usual stuff like cpufreq etc

not tested (but detected)
  bluetooth (044e:3017 Alps Electric Co., Ltd)
  cardbus
  firewire (Ricoh Co Ltd R5C832, config_firewire_ohci)


=====================================================

not working, and here we start with the problems:

WLAN
====
iwl sometimes shuts itself down and immediately again turn on, the rest
of the computer hangs for that time, about 2sec:
[  120.345217] PM: Removing info for No Bus:iwl-phy0:assoc
[  120.346008] PM: Removing info for No Bus:iwl-phy0:RX
[  120.347747] PM: Removing info for No Bus:iwl-phy0:TX
[  120.347803] PM: Removing info for No Bus:iwl-phy0:radio
[  122.344972] iwlagn 0000:06:00.0: PCI INT A disabled
[  122.482967] iwlagn 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  122.483150] iwlagn 0000:06:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
[  122.510812] PM: Adding info for No Bus:iwl-phy0:radio
[  122.511741] Registered led device: iwl-phy0:radio
[  122.511856] PM: Adding info for No Bus:iwl-phy0:assoc
[  122.512627] Registered led device: iwl-phy0:assoc
[  122.512716] PM: Adding info for No Bus:iwl-phy0:RX
[  122.513395] Registered led device: iwl-phy0:RX
[  122.513481] PM: Adding info for No Bus:iwl-phy0:TX
[  122.514227] Registered led device: iwl-phy0:TX

WWAN
====
  after rebooting *from* Vista to Linux I see the following USB device:
  Bus 004 Device 002: ID 0af0:6911 Option
  which is an Option Globetrotter HSDPA Modem
  but cold-booting directly into linux this device does not appear
  functionality not tested since devices are strangly enough not created!
  Something similar has been reported in 
    http://fedoraforum.org/forum/showthread.php?t=196654



Card reader
===========

SD/MMC card reader
  PCI: 0b:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
MemoryStick card reader
  PCI: 0b:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus
Host Adapter (rev 11)
  
  When I introduce the a SD card nothing works, but the kernel log shows
  me:
  mmc0: Reset 0x1 never completed.
  sdhci: ============== REGISTER DUMP ==============
  sdhci: Sys addr: 0x00000000 | Version:  0x00000400
  sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
  sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
  sdhci: Present:  0x00020000 | Host ctl: 0x00000000
  sdhci: Power:    0x0000000e | Blk gap:  0x00000000
  sdhci: Wake-up:  0x00000000 | Clock:    0x00008003
  sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
  sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
  sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
  sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
  sdhci: ===========================================




not supported devices
=====================

Fingerprint Scanner TouchStrip USB: Bus 003 Device 002: ID 147e:1000
  no device driver as far as I see




(sony_)acpi things:
===================

fans practically permanently running, that has been reported on several
forums. Is there a way around it?


brightness adjustment via hardware buttons does not work
there is /sys/class/backlight/sony but writing to brightness therein
does not do anything, neither does xbrightness, nor are any events sent
(see below for unknown methods in SNC/SPIC)


rfkill switch does turn of bluetooth AND WLAN, which is not what I want.
Problably only the SNC/SPIC routines can do something like turning
on/off specific hardware, see below.



SNC/SPIC sony_acpi stuff
========================
(as documented in Documentation/laptops/sony-acpi.txt)

The list of reported methods together with comments of my self and my
findings:

methods as reported by sony-laptop debug=1
method: name: _INI, args 0
	called
method: name: ECON, args 1
	unknown
method: name: GBRT, args 0
	get brightness, not working
method: name: SBRT, args 1
	set brightness, not working

method: name: PWAK, args 0
	unknown
method: name: EAWK, args 1
	unknown

	testing those two as reading and writing pair:
	reading PWAK gives 0
	writing "1" to it does not change anything AFAIS

method: name: SN00, args 1
	unknown
method: name: SN01, args 0
	unknown
method: name: SN02, args 1
	used in sony_nc_C_enable
method: name: SN03, args 1
	used in sony_nc_C_enable
method: name: SN04, args 0
	unknown
method: name: SN05, args 1
	unknown
method: name: SN06, args 1
	unknown
method: name: SN07, args 1
	used in sony_nc_C_enable


method: name: SNIN, args 0
	unknown
method: name: SNCF, args 2
	unknown
method: name: SNNE, args 1
	unknown
	testing these three in the a way that
		SN_set -> SNIN
		SN_get -> SNNE, SNCF	(no idea if this is the way for 2 args)
	reading SN: 16
	writing "1" or "1 2" does not change anything in the reading of SN
	nor do I see changes


method: name: F100, args 0
method: name: F113, args 0
method: name: F101, args 0
method: name: F105, args 0
method: name: F114, args 0
method: name: F115, args 0
method: name: F11D, args 0
method: name: F119, args 0
method: name: F121, args 0
method: name: F122, args 0
method: name: F124, args 0
method: name: F125, args 0
method: name: F126, args 0
method: name: F128, args 0
	all unknown
method: name: GPID, args 0
	PID_get
	returns 13


method: name: HSC0, args 0
method: name: HSC1, args 0
method: name: HSC2, args 0
method: name: HSC3, args 1
method: name: HSC4, args 1
	all unknown
	testing: 
	  HSC0 only get
	  HSC13 set/get	
	  HSC24 set/get
	reading HSC24 (ie HSC2) gives keyboard.c: can't emulate rawmode for keycode 240
	same with writing to HSC13 (HSC3)
	booting in normal mode gives values:
		HSC0:	0
		HSC13:	2
		HSC24:	1
	writing "0" to HSC24 did not change anything
	writing "1" to HSC13 did not change anything


	booting with nvidia card selected with hot switch
		HSC0:	0
		HSC13:	0
		HSC24:	1 but also echos some strange symbol to stdout
			  which *cannot* be redirected with > or 2>


method: name: HOMP, args 0
	reading gives 0, cannot be changed, same with nvidia selected
	unknown



other things with sony_acpi:
  writing and reading to wwanpower is possible EVEN if the wwan
  device is not present/exhibited/listed as device (lsusb)



=======================

So, that are my current findings. If anyone has some suggestions or
ideas please let me know, I will happily hack my kernel or anything
else.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BROMSGROVE
Any urban environment containing a small amount of dogturd and about
forty-five tons of bent steel pylon or a lump of concrete with holes
claiming to be sculpture. 'Oh, come my dear, and come with me. And
wander 'neath the bromsgrove tree' - Betjeman.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Joshua Wise]

>  intel graphics
>  nvidia graphics (both built in, switch on the fly on vista possible,
>    on linux needs reboot)

Hmm, that is very interesting!  On my SZ4, which has a (factory) Vista
install, a reboot is needed; and if you ever suspend the machine from Linux,
a clean boot from Vista is needed in order to switch the graphics card.

I think I know what PCI config registers need to be poked, at least on my
SZ4, to change on the fly, but I haven't experimented to come up with a
reliable way of actually doing it (or changing over the all-important LED).

>  after rebooting *from* Vista to Linux I see the following USB device:
>  Bus 004 Device 002: ID 0af0:6911 Option
>  which is an Option Globetrotter HSDPA Modem
>  but cold-booting directly into linux this device does not appear
>  functionality not tested since devices are strangly enough not created!
>  Something similar has been reported in
>    http://fedoraforum.org/forum/showthread.php?t=196654

I'm surprised that you get it when rebooting from Vista to Linux; usually
the BIOS shuts it off.   I don't have my SZ with me, but there should be a
'wwan-power' file somewhere in /sys -- try echoing '1' to it?  Other than
that, it behaves exactly like a GSM modem; you may need to modify the
'option' kernel module to learn about the new USB device ID.  On my SZ, to
wake up the modem, I believe you need to send the command 'AT+CFUN=1' to
actually put it in 'connect to the network' state, as opposed to the default
'transceiver off'.

> Fingerprint Scanner TouchStrip USB: Bus 003 Device 002: ID 147e:1000
>  no device driver as far as I see

Last I talked to the guys who make this thing, it is a device supported by
their driver (I can't remember the name of the manufacturer), but they have
some Sony special firmware on it that does some sort of over-the-wire
authentication, and the keys for that are only in the Windows Sony drivers. 
Thanks, guys...

> brightness adjustment via hardware buttons does not work
> there is /sys/class/backlight/sony but writing to brightness therein
> does not do anything, neither does xbrightness, nor are any events sent
> (see below for unknown methods in SNC/SPIC)

That works only if in Intel mode; use smartdimmer in nVidia mode.

> rfkill switch does turn of bluetooth AND WLAN, which is not what I want.
> Problably only the SNC/SPIC routines can do something like turning
> on/off specific hardware, see below.

rfkill is in hardware, I think.  To turn off bluetooth, take a look at the
'spicctrl' command.

> other things with sony_acpi:
>  writing and reading to wwanpower is possible EVEN if the wwan
>  device is not present/exhibited/listed as device (lsusb)

Writing '1' to it should create the device...

Does your system have "SmartWi" under Windows?  Perhaps the "wwan wakeup"
requests differ on your VAIO from my SZ.

joshua

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

Hi Joshua,

first of all, thanks a lot!

On Sat, 25 Oct 2008, Joshua Wise wrote:
>>  nvidia graphics (both built in, switch on the fly on vista possible,
>>    on linux needs reboot)
>
> Hmm, that is very interesting!  On my SZ4, which has a (factory) Vista
> install, a reboot is needed; and if you ever suspend the machine from Linux,
> a clean boot from Vista is needed in order to switch the graphics card.

Hmm, good question. I will check. I actually hardly use Vista, but read
that hot switching on Vista is possible.

And I never suspended till now, or better, I did and the laptop froooozze.

> I think I know what PCI config registers need to be poked, at least on my
> SZ4, to change on the fly, but I haven't experimented to come up with a
> reliable way of actually doing it (or changing over the all-important LED).

Since I am not in need of it anyway, that is not important.

>>  after rebooting *from* Vista to Linux I see the following USB device:
>>  Bus 004 Device 002: ID 0af0:6911 Option
>>  which is an Option Globetrotter HSDPA Modem
>>  but cold-booting directly into linux this device does not appear
>>  functionality not tested since devices are strangly enough not created!
>>  Something similar has been reported in
>>    http://fedoraforum.org/forum/showthread.php?t=196654
>
> I'm surprised that you get it when rebooting from Vista to Linux; usually
> the BIOS shuts it off.   I don't have my SZ with me, but there should be a

If I shut down Vista and restart (cold boot) linux it is gone.
If I tell Vista to restart and go directly from grub to linux it is
there.
Tested, several times.

> 'wwan-power' file somewhere in /sys -- try echoing '1' to it?  Other than

You mean
	/sys/devices/platform/sony-laptop/wwanpower
?

I echoed 1 to it and the usb device is still not showing up in lsusb. Is
there something else I have to do?

> that, it behaves exactly like a GSM modem; you may need to modify the
> 'option' kernel module to learn about the new USB device ID.  On my SZ, to

So that needs src changes, there is no modinfo option to force a device
id?

> wake up the modem, I believe you need to send the command 'AT+CFUN=1' to
> actually put it in 'connect to the network' state, as opposed to the default
> 'transceiver off'.

That should go to /dev/ttyUSBsomething I suppose?

> authentication, and the keys for that are only in the Windows Sony 
> drivers. Thanks, guys...

Ok, bummer. Let us forget it for now.

>> brightness adjustment via hardware buttons does not work
>> there is /sys/class/backlight/sony but writing to brightness therein
>> does not do anything, neither does xbrightness, nor are any events sent
>> (see below for unknown methods in SNC/SPIC)
>
> That works only if in Intel mode; use smartdimmer in nVidia mode.

I never got it working, and I am always running in intel = stamina mode.
Nothing whatever I do changes the brightness of the screen. Neither
using 
	/sys/devices/virtual/backlight/sony/brightness
nor 
	/sys/devices/virtual/backlight/acpi_video0/brightness

>> rfkill switch does turn of bluetooth AND WLAN, which is not what I want.
>> Problably only the SNC/SPIC routines can do something like turning
>> on/off specific hardware, see below.
>
> rfkill is in hardware, I think.  To turn off bluetooth, take a look at the
> 'spicctrl' command.

Ok, will try that one.

>> other things with sony_acpi:
>>  writing and reading to wwanpower is possible EVEN if the wwan
>>  device is not present/exhibited/listed as device (lsusb)
>
> Writing '1' to it should create the device...

But it didn't, unfortunately.

> Does your system have "SmartWi" under Windows?  Perhaps the "wwan wakeup"
> requests differ on your VAIO from my SZ.

SmartWi? I have some application that allows me to switch on/off
bluetooth, eth, modem, wwan, wlan. I will check the name.

Thanks a lot for all your suggestions

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
WARLEGGAN (n. archaic)
One who does not approve of araglins (q.v.)
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

Hi Joshua, hi all,

On So, 26 Okt 2008, Norbert Preining wrote:
> > 'wwan-power' file somewhere in /sys -- try echoing '1' to it?  Other than
> 
> You mean
> 	/sys/devices/platform/sony-laptop/wwanpower
> ?

That doesn't work. I tried it again. Going the
"first-boot-Vista-and-then-reboot-to-linux" way it does, without the
Vista route echo-ing 1 does not do anything.

> > wake up the modem, I believe you need to send the command 'AT+CFUN=1' to
> > actually put it in 'connect to the network' state, as opposed to the default
> > 'transceiver off'.
> 
> That should go to /dev/ttyUSBsomething I suppose?

No, I guess ttyHS4, the Modem interface of the usb device, right?

> > That works only if in Intel mode; use smartdimmer in nVidia mode.
> 
> I never got it working, and I am always running in intel = stamina mode.
> Nothing whatever I do changes the brightness of the screen. Neither
> using 
> 	/sys/devices/virtual/backlight/sony/brightness
> nor 
> 	/sys/devices/virtual/backlight/acpi_video0/brightness

Running in Intel mode, no changes what-so-ever in brightness.

Mattia, are you listening? Do you have any idea what might go wrong
here?

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
AASLEAGH (n.)
A liqueur made only for drinking at the end of a revoltingly long
bottle party when all the drinkable drink has been drunk.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Mattia Dongili]

On Tue, Oct 28, 2008 at 12:20:51AM +0100, Norbert Preining wrote:
> Hi Joshua, hi all,
...
> > > That works only if in Intel mode; use smartdimmer in nVidia mode.
> > 
> > I never got it working, and I am always running in intel = stamina mode.
> > Nothing whatever I do changes the brightness of the screen. Neither
> > using 
> > 	/sys/devices/virtual/backlight/sony/brightness
> > nor 
> > 	/sys/devices/virtual/backlight/acpi_video0/brightness
> 
> Running in Intel mode, no changes what-so-ever in brightness.
> 
> Mattia, are you listening? Do you have any idea what might go wrong
> here?

Yes, I am. But I have no idea what might be wrong. Did you also try
xbacklight while in X and using the Intel card?

-- 
mattia
:wq!

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

Hi Mattia,

(taking the MMC guy out, this is not about the SD card reader anymore)

On Di, 28 Okt 2008, Mattia Dongili wrote:
> Yes, I am. But I have no idea what might be wrong. Did you also try
> xbacklight while in X and using the Intel card?

I am a step further on. Thanks to Ishikawa-san I have an sony-laptop.c
file which allows setting the backlight using the
/sys/devices/backlight/{sony,acpi_video0}/backlight files
(interestingly, they do not agree on their behaviour, xbacklight can
change in 12.5% jumps, that makes 9 different values, but allowed are
only 8 (from 0 to 7). In sony the 0% is missing, in acpi_video0 the 100%
is missing -- i.e., sony/brightness 0 is brighter than
acpi_video0/brightness 0, and so on).

But still the function keys do not work.

No idea what could be done here.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
HEATON PUNCHARDON (n.) A violent argument which breaks out in the car
on the way home from a party between a couple who have had to be
polite to each other in company all evening.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[ISHIKAWA Mutsumi]

>>>>> In <20081028014708.GA2649@gamma.logic.tuwien.ac.at> 
>>>>>	Norbert Preining <preining@logic.at> wrote:
>> Hi Mattia,
>>
>> (taking the MMC guy out, this is not about the SD card reader anymore)
>>
>> On Di, 28 Okt 2008, Mattia Dongili wrote:
>> > Yes, I am. But I have no idea what might be wrong. Did you also try
>> > xbacklight while in X and using the Intel card?
>>
>> I am a step further on. Thanks to Ishikawa-san I have an sony-laptop.c
>> file which allows setting the backlight using the
>> /sys/devices/backlight/{sony,acpi_video0}/backlight files
>> (interestingly, they do not agree on their behaviour, xbacklight can
>> change in 12.5% jumps, that makes 9 different values, but allowed are
>> only 8 (from 0 to 7). In sony the 0% is missing, in acpi_video0 the 100%
>> is missing -- i.e., sony/brightness 0 is brighter than
>> acpi_video0/brightness 0, and so on).

 There are two points of roblems to enable backlight control on VGN-Z

  1)

      VGN-Z have SNC, but it is not enabled.
        - prevoius patch posted.
        - add VGN-Z entry to sony_nc_ids table

  2)

       In sony_pic_detect_device_type() function, VGN-Z's SPIC is
     detected as SONYPI_DEVICE_TYPE2 (per default).

       But it does not work for me.

       I've checkd throug TYPE1 to TYPE4. Only Type3 and Type4 does
     work (but it is possible to control backlight only, other
     function does not work...)

       I do not have datasheet for this model, but I think SPIC on
     this model is not TYPE2. It is same or variant of  Type3 or
     Type4 SPIC.


  I put this quick dirty hack code on URL bellow:

   http://hanzubon.jp/tmp/VGN-Z90S/sony-laptop.c

  Two kinds of change set are included:

     - add VGN-Z entry to sony_nc_ids
     - add type5 SPIC table (currently same as Type4) and
       use it on VGN-Z.

-- 
ISHIKAWA Mutsumi
 <ishikawa@debian.org>, <ishikawa@hanzubon.jp>, <ishikawa@osdn.jp>

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Mattia Dongili]

On Tue, Oct 28, 2008 at 10:12:20PM +0900, ISHIKAWA Mutsumi wrote:
> >>>>> In <20081028014708.GA2649@gamma.logic.tuwien.ac.at> 
> >>>>>	Norbert Preining <preining@logic.at> wrote:
> >> Hi Mattia,
> >>
> >> (taking the MMC guy out, this is not about the SD card reader anymore)
> >>
> >> On Di, 28 Okt 2008, Mattia Dongili wrote:
> >> > Yes, I am. But I have no idea what might be wrong. Did you also try
> >> > xbacklight while in X and using the Intel card?
> >>
> >> I am a step further on. Thanks to Ishikawa-san I have an sony-laptop.c
> >> file which allows setting the backlight using the
> >> /sys/devices/backlight/{sony,acpi_video0}/backlight files
> >> (interestingly, they do not agree on their behaviour, xbacklight can
> >> change in 12.5% jumps, that makes 9 different values, but allowed are
> >> only 8 (from 0 to 7). In sony the 0% is missing, in acpi_video0 the 100%
> >> is missing -- i.e., sony/brightness 0 is brighter than
> >> acpi_video0/brightness 0, and so on).
> 
>  There are two points of roblems to enable backlight control on VGN-Z
> 
>   1)
> 
>       VGN-Z have SNC, but it is not enabled.
>         - prevoius patch posted.
>         - add VGN-Z entry to sony_nc_ids table
> 
>   2)
> 
>        In sony_pic_detect_device_type() function, VGN-Z's SPIC is
>      detected as SONYPI_DEVICE_TYPE2 (per default).
> 
>        But it does not work for me.
> 
>        I've checkd throug TYPE1 to TYPE4. Only Type3 and Type4 does
>      work (but it is possible to control backlight only, other
>      function does not work...)
> 
>        I do not have datasheet for this model, but I think SPIC on
>      this model is not TYPE2. It is same or variant of  Type3 or
>      Type4 SPIC.

I have adopted a different approach (merge type3 and type4) but I have
included your other changes to my local tree. Hopefully I'll be able to
send a patchset for acpi-test later today.

thanks
-- 
mattia
:wq!

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Pierre Ossman]

On Sat, 25 Oct 2008 23:46:02 +0200
Norbert Preining <preining@logic.at> wrote:

> Card reader
> ===========
> 
> SD/MMC card reader
>   PCI: 0b:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
> MemoryStick card reader
>   PCI: 0b:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus
> Host Adapter (rev 11)
>   
>   When I introduce the a SD card nothing works, but the kernel log shows
>   me:
>   mmc0: Reset 0x1 never completed.

It is possible to wire the Ricoh chips in some odd way that makes them
misbehave whenever the slot is empty. This has only been observed on
Samsung laptops so far though.

The reader worked once you had a card in there in those cases. Could
you enable MMC_DEBUG in the kernel config and see what you get in dmesg
when you insert a card.

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

Hi Pierre,

On Sa, 08 Nov 2008, Pierre Ossman wrote:
> The reader worked once you had a card in there in those cases. Could
> you enable MMC_DEBUG in the kernel config and see what you get in dmesg
> when you insert a card.

I have inserted a card and did a reboot into the kernel with MMC_DEBUG
enabled and got that (irrelevant lines removed):


[    2.797345] sdhci: Secure Digital Host Controller Interface driver
[    2.797399] sdhci: Copyright(c) Pierre Ossman
[    2.797461] sdhci-pci 0000:0b:04.2: SDHCI controller found [1180:0822] (rev 21)
[    2.797533] sdhci-pci 0000:0b:04.2: found 1 slot(s)
[    2.797542] sdhci-pci 0000:0b:04.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[    2.896956] mmc0: Reset 0x1 never completed.
[    2.897008] sdhci: ============== REGISTER DUMP ==============
[    2.897019] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[    2.897023] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    2.897027] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    2.897031] sdhci: Present:  0x00030000 | Host ctl: 0x00000000
[    2.897034] sdhci: Power:    0x00000000 | Blk gap:  0x00000000
[    2.897038] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[    2.897042] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    2.897046] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[    2.897049] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    2.897052] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[    2.897053] sdhci: ===========================================
[    2.897057] sdhci-pci 0000:0b:04.2: Will use DMA mode even though HW doesn't fully claim to support it.
[    2.897129] sdhci-pci 0000:0b:04.2: setting latency timer to 64
[    2.996456] mmc0: Reset 0x1 never completed.
[    2.996507] sdhci: ============== REGISTER DUMP ==============
[    2.996510] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[    2.996513] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    2.996516] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    2.996520] sdhci: Present:  0x00030000 | Host ctl: 0x00000000
[    2.996523] sdhci: Power:    0x00000000 | Blk gap:  0x00000000
[    2.996526] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[    2.996529] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    2.996532] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[    2.996535] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    2.996538] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[    2.996539] sdhci: ===========================================
[    2.996541] sdhci: ============== REGISTER DUMP ==============
[    2.996543] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[    2.996547] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    2.996550] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    2.996553] sdhci: Present:  0x00030000 | Host ctl: 0x00000000
[    2.996556] sdhci: Power:    0x00000000 | Blk gap:  0x00000000
[    2.996559] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[    2.996562] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    2.996565] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[    2.996568] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    2.996572] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[    2.996573] sdhci: ===========================================
[    2.996581] PM: Adding info for No Bus:mmc0
[    2.996632] Registered led device: mmc0
[    2.996729] PM: Adding info for No Bus:mmc0
[    2.996755] mmc0: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
[    3.000612] mmc0: Reset 0x1 never completed.
[    3.000612] sdhci: ============== REGISTER DUMP ==============
[    3.000612] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[    3.000612] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    3.000612] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    3.000612] sdhci: Present:  0x00030000 | Host ctl: 0x00000000
[    3.000612] sdhci: Power:    0x00000000 | Blk gap:  0x00000000
[    3.000612] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[    3.000612] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    3.000612] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[    3.000612] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    3.000612] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[    3.000612] sdhci: ===========================================
[    3.096174] mmc0: SDHCI controller on PCI [0000:0b:04.2] using DMA
[    3.096208] mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 21 width 0 timing 0
[    3.098194] mmc0: clock 128906Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
[    3.100184] mmc0: clock 128906Hz busmode 1 powermode 2 cs 1 Vdd 21 width 0 timing 0
[    3.101179] mmc0: starting CMD0 arg 00000000 flags 000000c0
[    3.101223] ricoh-mmc: Ricoh MMC Controller disabling driver
[    3.101282] ricoh-mmc: Copyright(c) Philip Langdale
[    3.488968] usb 1-2: New USB device found, idVendor=05ca, idProduct=18b0
[    3.489028] usb 1-2: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[    3.489084] usb 1-2: Manufacturer: Ricoh co. Ltd.

[   13.104029] mmc0: Timeout waiting for hardware interrupt.
[   13.104083] sdhci: ============== REGISTER DUMP ==============
[   13.104087] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   13.104090] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   13.104093] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   13.104096] sdhci: Present:  0x00030000 | Host ctl: 0x00000000
[   13.104100] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   13.104103] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   13.104106] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   13.104109] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   13.104112] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   13.104116] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   13.104117] sdhci: ===========================================
[   13.108026] mmc0: Reset 0x2 never completed.
[   13.108026] sdhci: ============== REGISTER DUMP ==============
[   13.108026] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   13.108026] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   13.108026] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   13.108026] sdhci: Present:  0x01ff0000 | Host ctl: 0x00000000
[   13.108026] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   13.108026] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   13.108026] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   13.108026] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   13.108026] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   13.108026] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   13.108026] sdhci: ===========================================
[   13.108026] mmc0: Reset 0x4 never completed.
[   13.108026] sdhci: ============== REGISTER DUMP ==============
[   13.108026] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   13.108026] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   13.108026] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   13.108026] sdhci: Present:  0x01ff0000 | Host ctl: 0x00000000
[   13.108026] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   13.108026] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   13.108026] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   13.108026] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   13.108026] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   13.108026] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   13.108026] sdhci: ===========================================
[   13.302923] mmc0: req done (CMD0): -110: 00000000 00000000 00000000 00000000
[   13.303937] mmc0: clock 128906Hz busmode 1 powermode 2 cs 0 Vdd 21 width 0 timing 0
[   13.304933] mmc0: starting CMD8 arg 000001aa flags 000002f5

[   23.300042] mmc0: Timeout waiting for hardware interrupt.
[   23.300096] sdhci: ============== REGISTER DUMP ==============
[   23.300100] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   23.300103] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   23.300106] sdhci: Argument: 0x000001aa | Trn mode: 0x00000000
[   23.300109] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   23.300112] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   23.300115] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   23.300118] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   23.300121] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   23.300124] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   23.300127] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   23.300129] sdhci: ===========================================
[   23.302120] mmc0: req done (CMD8): -110: 00000000 00000000 00000000 00000000
[   23.302129] mmc0: starting CMD5 arg 00000000 flags 000002e1

[   33.300096] mmc0: Timeout waiting for hardware interrupt.
[   33.300179] sdhci: ============== REGISTER DUMP ==============
[   33.300187] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   33.300193] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   33.300200] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   33.300206] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   33.300212] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   33.300219] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   33.300225] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   33.300231] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   33.300237] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   33.300244] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   33.300248] sdhci: ===========================================
[   33.302244] mmc0: req failed (CMD5): -110, retrying...

[   43.304038] mmc0: Timeout waiting for hardware interrupt.
[   43.304108] sdhci: ============== REGISTER DUMP ==============
[   43.304115] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   43.304122] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   43.304128] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   43.304135] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   43.304141] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   43.304148] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   43.304154] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   43.304160] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   43.304166] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   43.304173] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   43.304177] sdhci: ===========================================
[   43.306172] mmc0: req failed (CMD5): -110, retrying...

[   53.684073] mmc0: Timeout waiting for hardware interrupt.
[   53.684080] sdhci: ============== REGISTER DUMP ==============
[   53.684087] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   53.684094] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   53.684100] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   53.684106] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   53.684113] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   53.684119] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   53.684125] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   53.684132] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   53.684138] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   53.684145] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   53.684148] sdhci: ===========================================
[   53.686167] mmc0: req failed (CMD5): -110, retrying...

[   63.684044] mmc0: Timeout waiting for hardware interrupt.
[   63.684126] sdhci: ============== REGISTER DUMP ==============
[   63.684134] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   63.684140] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   63.684147] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   63.684154] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   63.684161] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   63.684167] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   63.684173] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   63.684180] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   63.684186] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   63.684192] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   63.684196] sdhci: ===========================================
[   63.686193] mmc0: req done (CMD5): -110: 00000000 00000000 00000000 00000000
[   63.686219] mmc0: starting CMD55 arg 00000000 flags 000000f5

[   73.684092] mmc0: Timeout waiting for hardware interrupt.
[   73.684175] sdhci: ============== REGISTER DUMP ==============
[   73.684182] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   73.684188] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   73.684195] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   73.684201] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   73.684207] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   73.684214] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   73.684220] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   73.684226] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   73.684233] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   73.684239] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   73.684243] sdhci: ===========================================
[   73.686260] mmc0: req done (CMD55): -110: 00000000 00000000 00000000 00000000
[   73.686305] mmc0: starting CMD55 arg 00000000 flags 000000f5

[   83.684054] mmc0: Timeout waiting for hardware interrupt.
[   83.684124] sdhci: ============== REGISTER DUMP ==============
[   83.684132] sdhci: Sys addr: 0x00000000 | Version:  0x00000400
[   83.684138] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   83.684145] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[   83.684151] sdhci: Present:  0x01ff0001 | Host ctl: 0x00000001
[   83.684157] sdhci: Power:    0x0000000e | Blk gap:  0x00000000
[   83.684164] sdhci: Wake-up:  0x00000000 | Clock:    0x00008007
[   83.684170] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   83.684176] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[   83.684183] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   83.684189] sdhci: Caps:     0x01c021a1 | Max curr: 0x00000040
[   83.684193] sdhci: ===========================================
[   83.686190] mmc0: req done (CMD55): -110: 00000000 00000000 00000000 00000000
[   83.686215] mmc0: starting CMD55 arg 00000000 flags 000000f5

Let me know if I can be of any other help, and big thanks for taking a
look at it.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
CORRIEARKLET (n.)
The moment at which two people approaching from opposite ends of a
long passageway, recognise each other and immediately pretend they
haven't. This is to avoid the ghastly embarrassment of having to
continue recognising each other the whole length of the corridor.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Pierre Ossman]

On Sun, 9 Nov 2008 00:33:37 +0100
Norbert Preining <preining@logic.at> wrote:

> Hi Pierre,
> 
> On Sa, 08 Nov 2008, Pierre Ossman wrote:
> > The reader worked once you had a card in there in those cases. Could
> > you enable MMC_DEBUG in the kernel config and see what you get in dmesg
> > when you insert a card.
> 
> I have inserted a card and did a reboot into the kernel with MMC_DEBUG
> enabled and got that (irrelevant lines removed):
> 

The hardware is properly reporting that the card is present at least.
But everything else seems completely broken.

I'm afraid there's not much I can do at this point. We need to either
squeeze something useful out of Ricoh, or do some reverse engineering
on their Windows driver to figure out what kind of magic this chip
needs.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Pierre Ossman]

On Tue, 27 Jan 2009 01:48:40 +0100
Norbert Preining <preining@logic.at> wrote:

> 
> Funny things happened: WIth 2.6.29-rc2 inserting the card did not help,
> nothing showed up. But then I did WITH THE CARD IN THE SLOT a suspend
> and afterwards resume, and voila, there is the card, can be read ...
> I send you the output of dmesg, MMC_DEBUG is still on. It shows from
> boot on the errors while
> 
> Maybe you can squeeze something out of that.
> 

Hmmm...

Could you try building without ricoh_mmc and see if things work? Also
try having the card in during boot.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

On Di, 03 Feb 2009, preining wrote:
> Tests, all with kernel 2.6.29-rc3
> 
> - normal boot without card in the slot -> not detected
>   . suspending with OR without card in the slot makes it work!!!!
>     (that is new, I thought that the card has to be in the slot!)
>   . re-ejecting and re-inserting always make the card show up
>     One sequence of eject/re-insert's syslog output is attached.

       meant was AFTER a suspend/resume cycle the ejecting/re-inserting
       always makes the card show up.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
HEATON PUNCHARDON (n.) A violent argument which breaks out in the car
on the way home from a party between a couple who have had to be
polite to each other in company all evening.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Pierre Ossman]

On Tue, 3 Feb 2009 00:57:54 +0100
Norbert Preining <preining@logic.at> wrote:

> 
> Ok, here are my test. I was wrong in the previous email. The card does
> not have to be in the slot:
> 
> Tests, all with kernel 2.6.29-rc3
> 
> - normal boot without card in the slot -> not detected
>   . suspending with OR without card in the slot makes it work!!!!
>     (that is new, I thought that the card has to be in the slot!)
>   . re-ejecting and re-inserting always make the card show up
>     One sequence of eject/re-insert's syslog output is attached.
> 
> - normal boot WITH card in the slot -> detected!!!
> 
> All tests were made with and without ricoh_mmc built into the kernel. It
> does not change anything, so ricoh_mmc does not do anything at all here,
> can be disabled.
> 

This is extremely odd. I'd normally guess that this is because of a
race with ricoh_mmc, but since you've removed that from the equation...

> Hmm, isn't there a way to read the pci settings and see the difference?
> Could it make *the* difference?

Most likely. You can dump the PCI config using lspci -xxx. Compare the
data for everything on the Ricoh device (not just the MMC interface)
and see if you can see a difference before and after suspend.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Norbert Preining]

On Sa, 21 Feb 2009, Pierre Ossman wrote:
> > Tests, all with kernel 2.6.29-rc3

and -rc5

> > - normal boot without card in the slot -> not detected
> >   . suspending with OR without card in the slot makes it work!!!!
> >     (that is new, I thought that the card has to be in the slot!)
> >   . re-ejecting and re-inserting always make the card show up
> >     One sequence of eject/re-insert's syslog output is attached.
> > 
> > - normal boot WITH card in the slot -> detected!!!
> > 
> > All tests were made with and without ricoh_mmc built into the kernel. It
> > does not change anything, so ricoh_mmc does not do anything at all here,
> > can be disabled.
> > 
> 
> This is extremely odd. I'd normally guess that this is because of a
> race with ricoh_mmc, but since you've removed that from the equation...
> 
> > Hmm, isn't there a way to read the pci settings and see the difference?
> > Could it make *the* difference?
> 
> Most likely. You can dump the PCI config using lspci -xxx. Compare the
> data for everything on the Ricoh device (not just the MMC interface)
> and see if you can see a difference before and after suspend.

No difference, unfortunately. Absolutely no difference. The normal lspci
shows me:
...
0b:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
0b:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
0b:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
0b:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)

So I called
	lspci -xxx -s 0b:04
before and after suspend (before and after working state) and there is
no difference at all.

Anything else one can dump/do?

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
CURRY MALLET (n.)
A large wooden or rubber cub which poachers use to despatch cats or
other game which they can only sell to Indian resturants. For
particulary small cats the price obtainable is not worth the cost of
expending ammunition.
			--- Douglas Adams, The Meaning of Liff

Re: [RFH,Status] Sony Vaio VGN-Z11 support

[Pierre Ossman]

On Wed, 25 Feb 2009 00:44:14 +0100
Norbert Preining <preining@logic.at> wrote:

> On Sa, 21 Feb 2009, Pierre Ossman wrote:
> > 
> > Most likely. You can dump the PCI config using lspci -xxx. Compare the
> > data for everything on the Ricoh device (not just the MMC interface)
> > and see if you can see a difference before and after suspend.
> 
> No difference, unfortunately. Absolutely no difference. The normal lspci
> shows me:
> ...
> 0b:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
> 0b:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
> 0b:04.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
> 0b:04.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
> 
> So I called
> 	lspci -xxx -s 0b:04
> before and after suspend (before and after working state) and there is
> no difference at all.
> 
> Anything else one can dump/do?
> 

Not that I can think of, no. The interrupt control for these chips have
always been hidden in PCI config space, so this must be something new.

At this point I don't think I'm of much more use. See if the ACPI or PM
people can help you figure out what differs between a normal boot and a
resume. Once we know that we can fix up some voodoo that makes it work
every time.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.