[ltp] T60p Wifi and Display
Alex Deucher
linux-thinkpad@linux-thinkpad.org
Mon, 10 Mar 2008 09:39:08 -0400
On Sat, Mar 8, 2008 at 6:40 AM, Phil Shotton <phil@stairbridge.org.uk> wrote:
> Hi Alex
>
> Looks like the EDID is wrong. Whole log attached, but the important bit
> (I think) is:
>
> (II) RADEON(0): EDID for output VGA-0
> (II) RADEON(0): Manufacturer: SEG Model: 1a85 Serial#: 0
> (II) RADEON(0): Year: 2002 Week: 21
> (II) RADEON(0): EDID Version: 1.3
> (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
> (II) RADEON(0): Sync: Separate
> (II) RADEON(0): Max H-Image Size [cm]: H-Size may change, V-Size may change
> (II) RADEON(0): Gamma: 1.00
>
(II) RADEON(0): clock: 108.0 MHz Image Size: 32 x 32 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1440
h_blank_end 1688 h_border: 0
(II) RADEON(0): v_active: 1024 v_sync: 1026 v_sync_end 1029
v_blanking: 1066 v_border: 0
there's your problem. the mode reports itself as 32x32 mm. They
probably mean 320x320 mm, but even that seems wrong. xserver 1.4.x
will fix cm/mm unit issue automatically, but we can add a quirk for
your monitor as well if you know the real size.
in the interim you can use xrandr --fbmm 320x320 to fix it up.
Alex
> Note the missing size! Actual edid data is:
>
> (II) RADEON(0): Monitor name: RM170
> (II) RADEON(0): Serial No: H111701830
> (II) RADEON(0): EDID (in hex):
> (II) RADEON(0): 00ffffffffffff004ca7851a00000000
> (II) RADEON(0): 150c0103680000ffeabbb9a352469824
> (II) RADEON(0): 0f484cadcf0001010101010101010101
> (II) RADEON(0): 010101010101302a009851002a403070
> (II) RADEON(0): 2300202000000000000000fd003a4b1e
> (II) RADEON(0): 500e000a202020202020000000fc0052
> (II) RADEON(0): 4d313730200a202020202020000000ff
> (II) RADEON(0): 00483131313730313833300a20200078
>
> The internal LCD is correctly reported:
>
> (II) RADEON(0): Manufacturer: LEN Model: 4043 Serial#: 0
> (II) RADEON(0): Year: 2005 Week: 0
> (II) RADEON(0): EDID Version: 1.3
> (II) RADEON(0): Digital Display Input
> (II) RADEON(0): Max H-Image Size [cm]: horiz.: 30 vert.: 23
>
> I'm also running Xserver 1.3, so that's why the Monitor section doesn't
> work :-(
>
> Cheers
> Phil
>
> Alex Deucher wrote:
> > On Thu, Mar 6, 2008 at 12:04 PM, Phil Shotton <phil@stairbridge.org.uk> wrote:
> >
> >> Groan - another minor issue that you may be able to help with.
> >> The font in the login screen name and password entry boxes is way too
> >> big. I suspect the driver is generating the wrong DPI.
> >> xrandr says the Laptop screen is 305mm x228mm (correct) but that the
> >> external monitor is 32mm x 32mm!
> >>
> >
> > Can you post your X log? I'll take a look. It could be a bad edid
> > from your monitor. Lots of monitors have the units wrong in their
> > display size.
> >
> >
> >> I've tried setting the DisplaySize in the Monitor section and specifying
> >> the monitors in the devices section but it makes no difference. Here's
> >> the relevant bits from xorg.conf:
> >>
> >
> > Older versions of the xserver ignored the display size in randr 1.2
> > setups. I think xserver 1.4.x should be ok. You can also adjust the
> > dpi on teh fly with xrandr --fbmm
> >
> > Alex
> >
> >
> >
> >> Section "Monitor"
> >> Identifier "Panel"
> >> Option "VendorName" "IBM Laptop Display"
> >> Option "ModelName" "Generic Autodetecting Monitor"
> >> Option "DPMS" "true"
> >> DisplaySize 304 228
> >> EndSection
> >>
> >> Section "Monitor"
> >> Identifier "External"
> >> Option "VendorName" "DGM"
> >> Option "ModelName" "Generic Autodetecting Monitor"
> >> Option "DPMS" "true"
> >> DisplaySize 390 290
> >> EndSection
> >>
> >> Section "Device"
> >> Identifier "FireGL"
> >> Driver "ati"
> >> Option "Monitor-DVI-0" "External"
> >> Option "Monitor-VGA-0" "External"
> >> Option "Monitor-LVDS" "Panel"
> >> EndSection
> >>
> >> Any clues?
> >>
> >> Cheers
> >> Phil
> >>
> >> Phil Shotton wrote:
> >> > Ah, that would explain it :-)
> >> > OK, I'm happy. Keep up the good work and good luck with the 3D support.
> >> >
> >> > Phil
> >> >
> >> > Alex Deucher wrote:
> >> >> On Thu, Mar 6, 2008 at 7:36 AM, Phil Shotton
> >> >> <phil@stairbridge.org.uk> wrote:
> >> >>
> >> >>> Whee heee! It works.
> >> >>> Had to pull from git and build myself, but now have twin-head and
> >> >>> suspend/resume working. Thank you very much for your patient help.
> >> >>> Great work radeon driver developers!
> >> >>>
> >> >>> If I can impose one more time, DRI is failing. From Xorg log whole
> >> >>> bunch of
> >> >>> drmOpenDevice: node name is /dev/dri/card0
> >> >>> drmOpenDevice: open result is -1, (No such device)
> >> >>>
> >> >>> and finally
> >> >>>
> >> >>> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
> >> >>> [dri] Disabling DRI.
> >> >>>
> >> >>> The directory /dev/dri is empty. The Xorg dri module is loading,
> >> >>> agpgart
> >> >>> and ati_agp kernel modules are present.
> >> >>> I can live without DRI but it would be nice to have everything
> >> >>> working.
> >> >>>
> >> >>>
> >> >>
> >> >> There's no 3D support yet for r5xx cards yet. We're working on it :)
> >> >>
> >> >> Alex
> >> >>
> >> >>
> >> >>> Cheers
> >> >>> Phil
> >> >>>
> >> >>> Alex Deucher wrote:
> >> >>> > On Wed, Mar 5, 2008 at 12:02 PM, Phil Shotton
> >> >>> <phil@stairbridge.org.uk> wrote:
> >> >>> >
> >> >>> >> radeon fails to start at all, even with a minimal xorg.conf. I
> >> >>> simply
> >> >>> >> get booted into a 800x600 failsafe screen with my xorg.conf
> >> >>> trashed.
> >> >>> >> That's 2.5 days wasted. For now I've gone back to proprietary
> >> >>> and living
> >> >>> >> with no suspend/resume, but boy am I fed up with the whole thing.
> >> >>> >> Thanks for your help.
> >> >>> >>
> >> >>> >
> >> >>> > You need to make sure you have at least xf86-video-ati version 6.8.0
> >> >>> > or newer. Previous versions didn't support your chip.
> >> >>> >
> >> >>> > Alex
> >> >>> >
> >> >>> >
> >> >>> >> Phil
> >> >>> >>
> >> >>> >> Alex Deucher wrote:
> >> >>> >> > On Wed, Mar 5, 2008 at 5:34 AM, Phil Shotton
> >> >>> <phil@stairbridge.org.uk> wrote:
> >> >>> >> >
> >> >>> >> >> Alex
> >> >>> >> >>
> >> >>> >> >> Thanks for your help. I found a resolution key and removed
> >> >>> it, but it
> >> >>> >> >> makes no difference.
> >> >>> >> >> If I boot the laptop out of the dock, I get a 1400x1050
> >> >>> display on the
> >> >>> >> >> laptop. If I then plug the external monitor in and do
> >> >>> "xrandr --auto"
> >> >>> >> >> nothing happens.
> >> >>> >> >> I tried "xrandr --output VGA_1 --mode 1280x1024" and the
> >> >>> external
> >> >>> >> >> monitor displayed a beautiful mosaic of colours!
> >> >>> >> >>
> >> >>> >> >> So right now, I can have a laptop that suspends but only
> >> >>> runs one
> >> >>> >> >> monitor, or one that's dual-head but hangs on sleep.
> >> >>> Judging by chat on
> >> >>> >> >> the web I'm not the only one. Colleagues are suggesting I
> >> >>> stick Windoze
> >> >>> >> >> back on and after burning over 2 working days on this
> >> >>> already I can see
> >> >>> >> >> their point :-(
> >> >>> >> >>
> >> >>> >> >> Interesting that the ATI-based thinkpads always seem
> >> >>> cheaper than the
> >> >>> >> >> nvidia ones. I certainly would not use my own money to buy
> >> >>> any machine
> >> >>> >> >> with an ATI graphics card.
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >
> >> >>> >> > Have you tried that radeon driver (xf86-video-ati version
> >> >>> 6.8.0 or
> >> >>> >> > newer) as I suggested earlier? That will probably work
> >> >>> better for
> >> >>> >> > you. You could also file a bug for radeonhd:
> >> >>> >> > https://bugs.freedesktop.org
> >> >>> >> >
> >> >>> >> > Alex
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >> Phil
> >> >>> >> >>
> >> >>> >> >> Alex Deucher wrote:
> >> >>> >> >> > On Tue, Mar 4, 2008 at 12:13 PM, Phil Shotton
> >> >>> <phil@stairbridge.org.uk> wrote:
> >> >>> >> >> >
> >> >>> >> >> >> Hi Alex
> >> >>> >> >> >>
> >> >>> >> >> >> I tried the radeonhd driver, and after a bit of
> >> >>> fiddling I've managed to
> >> >>> >> >> >> get suspend/resume working - great.
> >> >>> >> >> >> However, with an external monitor plugged in I get no
> >> >>> display on the
> >> >>> >> >> >> laptop screen once I've logged in (the login screen shows
> >> >>> >> >> >> on both).
> >> >>> >> >> >>
> >> >>> >> >> >
> >> >>> >> >> > This is due to the video resolution gui in gnome (or
> >> >>> kde). If you've
> >> >>> >> >> > used the gui to set a mdoe it saves that configuration
> >> >>> and resets it
> >> >>> >> >> > when you log in. however, it's not randr 1.2 aware so it
> >> >>> doesn't work
> >> >>> >> >> > well with multi-head. It should work if you remove the
> >> >>> keys in:
> >> >>> >> >> > /desktop/gnome/screen/$hostname/$screennum/
> >> >>> >> >> >
> >> >>> >> >> > Alex
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >> xrandr reports:
> >> >>> >> >> >> Screen 0: minimum 320 x 200, current 1280 x 1024,
> >> >>> maximum 2800 x 1050
> >> >>> >> >> >> VGA_1 connected 1280x1024+0+0 32mm x 32mm
> >> >>> >> >> >> 1280x1024 75.0*
> >> >>> >> >> >> 1024x768 75.1 70.1 60.0
> >> >>> >> >> >> 800x600 72.2 75.0 60.3
> >> >>> >> >> >> 640x480 75.0 72.8 60.0
> >> >>> >> >> >> 720x400 70.1
> >> >>> >> >> >> PANEL connected
> >> >>> >> >> >> 1400x1050 60.0 +
> >> >>> >> >> >> DVI-D_1 disconnected
> >> >>> >> >> >>
> >> >>> >> >> >> Looking in Xorg.0.log (attached) shows lots of "Not
> >> >>> using default mode
> >> >>> >> >> >> ...." with "vrefresh out of range" and "hsync out of
> >> >>> range" and "height
> >> >>> >> >> >> too large for virtual size" but it still returns the
> >> >>> modeline for the
> >> >>> >> >> >> 1400x1050 resolution that xrandr shows.
> >> >>> >> >> >>
> >> >>> >> >> >> My xorg.conf is about as simple as I could make it.
> >> >>> Also attached.
> >> >>> >> >> >>
> >> >>> >> >> >> Cheers
> >> >>> >> >> >> Phil
> >> >>> >> >> >>
> >> >>> >> >> >> Alex Deucher wrote:
> >> >>> >> >> >> > On Tue, Mar 4, 2008 at 9:30 AM, Phil Shotton
> >> >>> <phil@stairbridge.org.uk> wrote:
> >> >>> >> >> >> >
> >> >>> >> >> >> >> After finally getting my T60 working to my
> >> >>> satisfaction I've been
> >> >>> >> >> >> >> upgraded(!) to a T60p, and I now have two problems
> >> >>> after installing
> >> >>> >> >> >> >> Ubuntu Gutsy:
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> 1) Atheros AR5418 wifi card. Not recognized. I've
> >> >>> tried using the
> >> >>> >> >> >> >> latest madwifi for this but with no success. The
> >> >>> ndiswrapper works fine,
> >> >>> >> >> >> >> but it's not getting loaded at boot. The
> >> >>> ndiswrapper config placed an
> >> >>> >> >> >> >> ndiswrapper file in /etc/modprobe.d - containing 1
> >> >>> line:
> >> >>> >> >> >> >> alias wlan0 ndiswrapper
> >> >>> >> >> >> >> but the driver still doesn't get loaded. If I
> >> >>> "modprobe ndiswrapper"
> >> >>> >> >> >> >> everything works fine (in fact I get better wifi
> >> >>> performance than with T60).
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> 2) Display. This T60p has an ATI Mobility FireGL
> >> >>> V5250. I need dual-head
> >> >>> >> >> >> >> support and the only way I could get that on the
> >> >>> T60 (ATI X1400) was to
> >> >>> >> >> >> >> use the ATI proprietary drivers. I'm using the
> >> >>> latest 8.452.1 version,
> >> >>> >> >> >> >> and it all works OK except:
> >> >>> >> >> >> >>
> >> >>> >> >> >> >
> >> >>> >> >> >> > That chips works fine in both radeon (6.8.0 and
> >> >>> newer) and radeonhd.
> >> >>> >> >> >> > No 3D yet however.
> >> >>> >> >> >> >
> >> >>> >> >> >> > Alex
> >> >>> >> >> >> >
> >> >>> >> >> >>
> >> >>> >> >> >>
> >> >>> >> >> >> # xorg.conf (xorg X Window System server configuration
> >> >>> file)
> >> >>> >> >> >> #
> >> >>> >> >> >> # This file was generated by failsafeDexconf, using
> >> >>> >> >> >> # values from the debconf database and some overrides
> >> >>> to use vesa mode.
> >> >>> >> >> >> #
> >> >>> >> >> >> # You should use dexconf or another such tool for
> >> >>> creating a "real" xorg.conf
> >> >>> >> >> >> # For example:
> >> >>> >> >> >> # sudo dpkg-reconfigure -phigh xserver-xorg
> >> >>> >> >> >>
> >> >>> >> >> >> Section "ServerLayout"
> >> >>> >> >> >> Identifier "Default Layout"
> >> >>> >> >> >> Screen 0 "aticonfig-Screen[0]" 0 0
> >> >>> >> >> >> InputDevice "Generic Keyboard"
> >> >>> >> >> >> InputDevice "Configured Mouse"
> >> >>> >> >> >> InputDevice "Synaptics Touchpad"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Files"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Module"
> >> >>> >> >> >> Load "glx"
> >> >>> >> >> >> Load "GLcore"
> >> >>> >> >> >> Load "v4l"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "InputDevice"
> >> >>> >> >> >> Identifier "Generic Keyboard"
> >> >>> >> >> >> Driver "kbd"
> >> >>> >> >> >> Option "CoreKeyboard"
> >> >>> >> >> >> Option "XkbRules" "xorg"
> >> >>> >> >> >> Option "XkbModel" "pc105"
> >> >>> >> >> >> Option "XkbLayout" "gb"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "InputDevice"
> >> >>> >> >> >> Identifier "Configured Mouse"
> >> >>> >> >> >> Driver "mouse"
> >> >>> >> >> >> Option "CorePointer"
> >> >>> >> >> >> Option "Device" "/dev/input/mice"
> >> >>> >> >> >> Option "Protocol" "ImPS/2"
> >> >>> >> >> >> Option "ZAxisMapping" "4 5"
> >> >>> >> >> >> Option "Emulate3Buttons" "true"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "InputDevice"
> >> >>> >> >> >> Identifier "Synaptics Touchpad"
> >> >>> >> >> >> Driver "synaptics"
> >> >>> >> >> >> Option "SendCoreEvents" "true"
> >> >>> >> >> >> Option "Device" "/dev/psaux"
> >> >>> >> >> >> Option "Protocol" "auto-dev"
> >> >>> >> >> >> Option "HorizScrollDelta" "0"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Monitor"
> >> >>> >> >> >> Identifier "PANEL"
> >> >>> >> >> >> Option "VendorName" "IBM"
> >> >>> >> >> >> Option "ModelName" "T60p Panel"
> >> >>> >> >> >> Option "DPMS" "true"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Monitor"
> >> >>> >> >> >> Identifier "VGA_1"
> >> >>> >> >> >> Option "VendorName" "DGM"
> >> >>> >> >> >> Option "ModelName" "LCD Panel"
> >> >>> >> >> >> Option "DPMS" "true"
> >> >>> >> >> >> Option "RightOf" "PANEL"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Device"
> >> >>> >> >> >> Identifier "aticonfig-Device[0]"
> >> >>> >> >> >> Driver "radeonhd"
> >> >>> >> >> >> Option "monitor-VGA_1" "VGA_1"
> >> >>> >> >> >> Option "monitor-PANEL" "PANEL"
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> Section "Screen"
> >> >>> >> >> >> Identifier "aticonfig-Screen[0]"
> >> >>> >> >> >> Device "aticonfig-Device[0]"
> >> >>> >> >> >> Monitor "PANEL"
> >> >>> >> >> >> DefaultDepth 24
> >> >>> >> >> >> SubSection "Display"
> >> >>> >> >> >> Virtual 3500 1800
> >> >>> >> >> >> Depth 24
> >> >>> >> >> >> EndSubSection
> >> >>> >> >> >> EndSection
> >> >>> >> >> >>
> >> >>> >> >> >> #Section "Extensions"
> >> >>> >> >> >> # Option "Composite" "0"
> >> >>> >> >> >> #EndSection
> >> >>> >> >> >>