[Gutsy] Tribe-5 64-bit LiveCD Success report for Sony Vaio VGN-FE41Z

Bug #136807 reported by TJ
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

This report is to assist Gutsy developers in identifying and solving outstanding issues. Attached is an archive containing the important configuration reports and logs that will assist.

Summary:

Laptop Sony Vaio VGN-FE41Z Intel Core2 Duo T7200, 2GB RAM with Nvidia GeForce Go 7600 1280x800 HDA-Sigmatel audio

LiveCD boot
  * When desktop is displayed: "Error starting Gnome Settings Daemon"
    "Failed to connect to socket /tmp/dbus-W1Amuwj410: connection refused"

    This seems to cause many other knock-on effects with various Gnome applications and applets such as no keyboard mappings,
     inability of many applications to save settings, etc.

Detected problems:
  * HDA 'digital' microphone input records static
     (suspect pin assignment wrong - will compare against Feisty and report)
     Tested in both Sound Recorder and Ekiga, and tried altering Sound settings

  * Ekiga softphone cannot display video from built-in MotionEye camera in correct format
       UVC manages the camera correctly, and "luvcview -d /dev/video0 -f yuv" displays camera output correctly
      and *without* needing the r5u870 driver installed (great progress!)

  * No power management facilities available, no Hibernate or Suspend options
     Seems to be caused by the missing dbus

  * Texas Instruments MemoryStick not available. tifm_core detects it, but tifm_ms not yet advanced enough to provide access)

Tests Satisfied:

 * Intel IPW3945 WiFi works immediately
 * NetworkManager switches between WiFi and wired e100
 * Sound playback
 * Playing the introductory video
 * MotionEye camera works (using "luvcview -d /dev/video0 -f yuv" to test)
 * Inserting USB Storage key, volumes recognised and mounted
 * Bluetooth scans and detects devices

Possible Feature Enhancements

 * cryptsetup available on CD so mounting of encrypted devices possible without Internet access

 * Enable connection of Bluetooth mice. This can be done easily through a simple edit to /etc/default/bluetooth:
   HIDD_ENABLED=1 (currently it is set to 0)

   If the device is reset/put into 'discover' mode a scan and connect will allow use of the mouse:
   $ hcitool scan
     Scanning ...
        00:07:61:3B:86:98 Bluetooth Travel Mouse
        00:04:76:BB:2D:03 deskjet 995c S/N MY19P1C13F0L
   $ sudo hidd --connect 00:07:61:3B:86:98

   This can be done automatically with a script similar to this:
   BTDEV="`hcitool scan | grep -i 'mouse' | awk '{print $1}'`"; if [ "x${BTDEV}" != "x" ]; then echo "Trying to connect to ${BTDEV}"; sudo hidd --connect ${BTDEV}; fi;

Revision history for this message
TJ (tj) wrote :
Changed in linux-source-2.6.22:
importance: Undecided → Low
status: New → Confirmed
description: updated
description: updated
description: updated
Revision history for this message
TJ (tj) wrote :

I've just discovered another fault:

 * HDA headphones don't work.
   Plugging in headphones the speakers are muted but no sound in headphones. Unplug and sound returns to speakers.

Revision history for this message
TJ (tj) wrote :

After logging out of the first Gnome session and logging in again the dbus failures are no longer present.

Also, with a bit of xorg.conf editing the Nvidia restricted driver is providing full 3D acceleration and Compiz effects.

Revision history for this message
TJ (tj) wrote :

Gutsy's microphone input doesn't work - Feisty's is confirmed working.
Gutsy's headphone output doesn't work (speaker mute does) - Feisty's is confirmed working.

Comparison of the HDA codec reports of /proc/asound/card0/codec#0 shows the significant differences are:

$ diff -y --left-column Feisty/codec#0 Gutsy/codec#0
Codec: SigmaTel STAC9872AK | Codec: SigmaTel ID 7662
Address: 0
Vendor Id: 0x83847662
Subsystem Id: 0x104d0c00
Revision Id: 0x100201
                                                              > No Modem Function Group found
Node 0x07 [Audio Selector] wcaps 0x300903: Stereo Amp-In
  Amp-In caps: N/A
  Amp-In vals: [0x00 0x00] | Amp-In vals: [0x80 0x80]
  Connection: 1
     0x0e
Node 0x09 [Audio Selector] wcaps 0x300903: Stereo Amp-In
  Amp-In caps: N/A
  Amp-In vals: [0x0d 0x0d] | Amp-In vals: [0x0f 0x0f]
  Connection: 1
     0x15
Node 0x0a [Pin Complex] wcaps 0x400181: Stereo
  Pincap 0x08173c: IN OUT HP Detect
  Pin Default 0x02211020: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Black
  Pin-ctls: 0xc0: OUT HP | Pin-ctls: 0x00:
  Connection: 1
     0x02
Node 0x0e [Pin Complex] wcaps 0x400081: Stereo
  Pincap 0x0824: IN Detect
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
  Pin-ctls: 0x20: IN | Pin-ctls: 0x00:
Node 0x14 [Pin Complex] wcaps 0x400001: Stereo
  Pincap 0x0820: IN
  Pin Default 0x90a7014e: [Fixed] Mic at Int N/A
    Conn = Analog, Color = Unknown
  Pin-ctls: 0x20: IN | Pin-ctls: 0x00:
Node 0x15 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x04, stepsize=0x27, mute=1
  Amp-Out vals: [0x00 0x00] | Amp-Out vals: [0x04 0x04]
  Connection: 4
     0x0a 0x0d 0x14* 0x02 | 0x0a 0x0d* 0x14 0x02

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

TJ:
I'd check whether the headphone socket has a volume of its own in alsamixer...

Revision history for this message
TJ (tj) wrote :

Sitsofe, No it doesn't unfortunately.

I've been hacking snd-hda-intel the past couple of months solving various bugs in Feisty and recently in Gutsy. There's a lot of changes need sorting out not least these. There's issues with it resuming from suspend in AC'97 instead of HDA mode and others!

Overall I'm very impressed with 64-bit Gutsy Tribe-5. I've now got it installed in the test partition and it's running very well. Speed increase especially for package builds is about 40% up on the same 32-bit build.

I've just applied my 'auto-mount for key-file encrypted file-systems' patch to gnome-mount and the related hal script, so have access to my protected areas now.

Trying to find an elegant way to get Google Earth installed without a chroot - it is possible, but takes some fiddling.

Revision history for this message
TJ (tj) wrote :

Okay, good news.

One or other update has enabled the headphone functionality correctly, and I've solved the microphone issue. See my specific comment to bug #134125:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/134125/comments/6

Revision history for this message
TJ (tj) wrote :

Update with kernel 2.6.22-12 64-bit and all updates to 22nd September 2007.

* Using nvidia-glx-new and Compiz/Desktop Effects

All the following devices are working and stable:

* Hibernate/Suspend/Resume all appear to work reliably and repeatedly
* HDA stereo speakers, headphones, internal microphone, external microphone (aka mixer line-in)
* Intel ipw3945, e100
* Wireless radio switch
* NetworkManager WPA2 WiFi
* Touchpad/GlidePad
* Bluetooth (mouse, A2DP headset)
* MotionEye camera (requires separate build of r5u870 and related firmware blobs)
* DVD writer
* Power Management (Power history (watts) isn't detected)
* CPU throttling
* CPU thermal monitoring and management (fan)
* Nvidia back-light control (using additional install of smartdimmer and my Gnome dimmer applet)
* S-Video output
* Analogue VGA output
* PCMCIA/CardBus slot
* IEEE1394 'FireWire' port
* USB 2.0 (three ports)
* ExpressCard/34 5-in-1 memory card adapter (tested with SD, MMC)
* Mute, Volume +/- buttons

Not working

* Built-in MemoryStick slot (open-source driver not yet ready)
* Sony Notebook Control (SNC) controlled blue Fn key +F5/F6 (brightness +/-), +F7 (video output switch), +F12 (Sleep)

Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.