Talk:Installing Fedora 8 on a ThinkPad T61

Shouldn't you title your page as "Installing Fedora 8 x86_64 on a T61?

I might, if the process varied that much. But I believe that the only difference between i386 and x86_64 installation would be which ISO you used. And none of the other "Installing Fedora X on a XXX" in the Fedora category reference the architecture. I'll leave it as-is until I hear a good reason to change it. --Leedm777 01:55, 16 November 2007 (UTC)

Suspend to RAM works fine for me, but suspend to disk does not. After a long time, it looks like it hibernates with the icon blinking for a few seconds. On resume, it looks like a normal reboot with the BIOS logo and grub menu, except with no timeout After which I just get a black screen with a cursor that disappears after 30 seconds or so and then it appears to be frozen. I have the nvidia driver so it differs from the original author and that may be causing the issue.

With my T61, my experience duplicates yours, except that audio hotkeys do not work (though the gnome applet does pop up and show volume up/down correctly). Another problem is irqbalance always appears to fail on shutdown, because it exits early. I saw an issue manifesting with the same thing was fixed on uniprocessor systems. Finally, my T61 has a Ricoh 4-in-1 memory card reader. The device does show in lspci as an xD card reader and a memory stick reader, however, my camera's xD card did not work.

Scritter 01:13, 8 December 2007 (UTC)

I've had similar Suspend/Hibernate issues. But pressing Alt-Ctl-F1 (switching to a text console) then Alt-F7 back to the X window seemed to fix the post-hibernate black screen. I've also found that the following, saved as /etc/hal/fdi/information/20-video-quirk-pm-lenovo.fdi provides stable suspend/hibernate behavior:

<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
  <device>
    <match key="system.hardware.vendor" string="LENOVO">
      <match key="system.hardware.version" string="ThinkPad T61">
        <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
        <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
      </match>
    </match>
  </device>
</deviceinfo>

Though I believe you need to reboot, or at least restart hal before the quirk-pm file takes effect.

Hdasch 05:54, 8 December 2007 (UTC)

Just wondered if you could elaborate a bit on the NetWorkManager setup. Does standard networking need to be turned off (i.e., chkconfig network off) to free NetWorkManager to do its thing? And, what happens to stuff like cron jobs that use the network if no one's logged in? Thanks