Difference between revisions of "Talk:Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61"
|Line 1:||Line 1:|
Revision as of 15:51, 19 October 2007
- 1 Microphone
- 2 Twinview?
- 3 Core 2 Duo running at 800 mHz?
- 4 Desktop_Applet crash on login after update (2007-09-16) with x86 and AMD64 versions (Fixed in daily build 20070918, reappears in 20070919.1)
- 5 Touchpad issues
- 6 Daily build 20070918 AMD64 won't install
- 7 Volume/Sound Buttons
- 8 Brightness buttons
- 9 Compiling existing information
- 10 Desktop effects don't consistenly work
- 11 NetworkManger Intermittently Fails To Start, No Networking When It Fails
- 12 I installed libdvdcss2, but DVD playback still doesn't work
- 13 x86 vs 64bit on core 2 duo
- 14 Black screen at boot
- 15 Update 2007-10-11 works fine
- 16 Power Consumption
This discussion was going on in the wiki and seems a bit confusing. If possible I think we should get a consensus on the problem (if it still exists as of the final release) and solutions.
Attn: Microphone (both internal and external) seems to be working for me with all applications after applying all updates (No need to change device to OSS) Make sure the relevant things (internal microphone, mic boost) etc aren't muted either in alsamixer or gnome-volume-control.
Microphone may not work with applications (like sound recorder and skype) even though sound can be heard through the speakers or headphones. If you have success in using the built in microphone please update this section.
It worked for me after i followed the instructions in this thread for ALSA http://ubuntuforums.org/showthread.php?p=2635174#post2635174
I had to tick the following tracks to make my mic work in Sound Recorder PCM, Microphone, Capture, Capture1, Input Source, Input Source, Internal Mic, Speaker.
For those that find the above instructions vague:
The whole 'Volume Control Center' could be better labelled but here is what i believe to be true: the microphone will work but only through the OSS mixer. the ALSA mixer is what causes the listed problem (not working with applications like skype) but the sound quality of alsa mixer is far better than the OSS mixer and it would be much more convenient to control so it would be hugely beneficial to get it working. Nonetheless here are more detailed instructions for getting sound working.
In the Playback tab you should have PCM, which is the only important one. If you have anything else there you should mute them. [On an X61 at least under playback was the option 'internal mic', unmute that and max it out, mute internal mic boost, make sure capture one is about 70% and thats all it took to get mine working]
In the 'recording' tab should be 'Capture' and 'Capture 1'(if they aren't you have to check them in Edit-->Preferences) 'Capture' controls the volume for the ALSA mic input and 'Capture 1' controls the volume for the OSS mic input. Mute 'Capture' and increase the volume of 'Capture 1'
The 'switches' tab should be as you set it up in the audio section of this wiki. headphones [check] and speakers [check].
The options tab (which i haven't quite figured out) should have a list of two 'Input Sources' I have mine set to 'Internal Mic' on the top and 'Mic' on the bottom. i don't know if that is correct but it is working for me.
Now go to File-->Change Device--> Analog Devices (OSS Mixer) You should see a 'Playback' tab with 'Microphone', 'PCM-2' and 'In-gain'. If you do not see these then open Edit-->Preferences and select them. Place your microphone volume at your desired level (mine is at about 7/8ths) and mute it when you are not using it, otherwise you get the crackle. The 'PCM-2' seems to only go fully up or fully down, i leave it fully up. I haven't figured out what effect the 'In-gain' has yet. (you'll be the first to know when i do)
This should give you the ability to record sound or skype but it is tedious as you will have to mute and unmute the microphone in the Analog Devices OSS area. Maybe there is a way to simplfy this method but i haven't found it. Hopefully soon recording with the ALSA mixer will work.
This was on the wiki so I moved it here for discussion:
Has anyone found a fix for this? Does the Ubuntu wiki <https://help.ubuntu.com/community/NvidiaTVOut> work? What adjustments are needed for Gutsy and NVIDIA Quadro NVS 140M
Is it possible to do set up Twinview with movies that don't span screens in the Applications->System Tools->Nvidia Settings?
Core 2 Duo running at 800 mHz?
The applications Sysinfo and PowerTOP both say that my CPU is running at 800 MHz. When I first open Sysinfo, it says a number around 2 GHz but it then drops to 800 MHz. Sysinfo says something about laptop CPU frequency changing (being "dynamic"), but it remains static at 800 MHz. SteveSims 00:51, 13 September 2007 (UTC)
This is normal. This is the "frequency scaling" feature of the laptop. Whenever the processors aren't being used they drop down to 800MHz to conserve power. All you have to do is run some CPU-intensive task and you'll see them jump up to 2GHz. There's a little applet that you can add to the top panel called "CPU Frequency Scaling Monitor" that will let you watch the processor speed up and down in real time: Right-click on the top panel bar and select "Add to Panel" to find it; it's under "System and Hardware" --Mike Richards 06:31, 13 September 2007 (UTC)
Desktop_Applet crash on login after update (2007-09-16) with x86 and AMD64 versions (Fixed in daily build 20070918, reappears in 20070919.1)
I found out that my Thinkpad T61 is a 64-bit machine so I installed the 64-bit version of Ubuntu 7.10 Tribe 5. I tried updating the machine, which worked fine until it had to configure and install my updates. With about 12 minutes remaining it hangs up and the terminal within the Update Manager says that some components must be restarted (and the update hangs) so I restart my computer. When I log in, I get an error message that says something about a Deskbar_Applet not working, and it asks me if I want to delete it. Regardless of my selection, I can no longer update the machine nor run Applications --> Add/Remove. I thought it must be a difference between AMD64 and Intel's x86-64 near-clone, so I re-installed the 32-bit version. When I updated, the same thing happened after I updated it. I'm guessing this is a bug withing the GUI or the package manager.
However, I can load Firefox from my panel just fine. SteveSims 05:01, 17 September 2007 (UTC)
- I had a similar problem. I found if I just avoided updating the system until after a full reboot, things were fine. Rybu
- The most recent update (9-18-2007) solves this problem.
- The problem appears again in 20070919.1, at least the AMD64 version (I haven't tested the x86-32 version). SteveSims 21:49, 19 September 2007 (UTC)
- And it still exists as of September 20th. SteveSims 04:53, 21 September 2007 (UTC)
After updating on September 18th from the original x86 Tribe 5, tapping the touchpad hard no longer clicks, and the right edge no longer scrolls. SteveSims 01:59, 19 September 2007 (UTC)
- Go to System -> Preferences -> Mouse. In the Touchpad tab you can activate tap to click and vertical scrolling. --aerials 13:05, 21 September 2007 (UTC)
Daily build 20070918 AMD64 won't install
Double-clicking on the Install icon in the LiveCD does nothing. No window loads, I can't install it from the LiveCD. SteveSims 01:59, 19 September 2007 (UTC)
In Kubuntu 7.10 beta work mute button but anything display on screen/desktop. When I press the volume up button, on the screen display a window and always write 11%, and the volume not hight (if mute is on then mute disabled). When I press the volume down button display 0% but the volume not down.
When the mute is enabled the kmix not display mute. Fitopaldi
If add this lines to ~/.kde/share/config/khotkeysrc the volume up button and volume down button works perfectly with kmix with DCOP.
[Data_4] Comment= DataCount=2 Enabled=true Name=Thinkpad SystemGroup=0 Type=ACTION_DATA_GROUP [Data_4Conditions] Comment= ConditionsCount=0 [Data_4_1] Comment= Enabled=true Name=Volume up Type=DCOP_SHORTCUT_ACTION_DATA [Data_4_1Actions] ActionsCount=1 [Data_4_1Actions0] Arguments=1 Call=increaseVolume RemoteApp=kmix RemoteObj=Mixer0 Type=DCOP [Data_4_1Conditions] Comment= ConditionsCount=0 [Data_4_1Triggers] Comment=Simple_action TriggersCount=1 [Data_4_1Triggers0] Key=XF86AudioRaiseVolume Type=SHORTCUT [Data_4_2] Comment= Enabled=true Name=Volume down Type=DCOP_SHORTCUT_ACTION_DATA [Data_4_2Actions] ActionsCount=1 [Data_4_2Actions0] Arguments=1 Call=decreaseVolume RemoteApp=kmix RemoteObj=Mixer0 Type=DCOP [Data_4_2Conditions] Comment= ConditionsCount=0 [Data_4_2Triggers] Comment=Simple_action TriggersCount=1 [Data_4_2Triggers0] Key=XF86AudioLowerVolume Type=SHORTCUT
But this is a temporal solution. ;) With this solution not work the volume info screen. Fitopaldi
The brightness buttons used to work on my system. But now that I have 2 displays, they don't work anymore. When I first installed Ubuntu 7.10 the brightness buttons did not work but I found some tips on-line to enable them... unfortunately I don't remember what those tips were... silly me... I'll dig up the info and put it into the wiki, soon. Rybu
In Kubuntu Gutsy don't work anymore. When I first installed Kubuntu 7.10 (tribe 5) yes work on console screen, but later the first update not work this. (NVIDIA GPU) Fitopaldi
Compiling existing information
Desktop effects don't consistenly work
I installed new themes and updated today and suddenly the new desktop effects that were added to 7.10 don't work.
However, Deskbar_Applet doesn't crash with the update, even though it does with today's most current LiveCD. SteveSims 06:37, 21 September 2007 (UTC)
NetworkManger Intermittently Fails To Start, No Networking When It Fails
After the most recent Kernel patch under Gutsy, NetworkManager doesn't always manage to run when I boot, and when it fails I have no networking. If I try init.d/networking restart, it fails with 'unknown device' for all devices. Looking through the logs, my best guess is ath0 isn't ready when NetworkManager starts, so it starts cycling through other devices until it crashes. Does anyone have any ideas? It seems to only work about 1-2 boots out of 10.
I installed libdvdcss2, but DVD playback still doesn't work
- I always like the idea of using GStreamer instead of Xine, but the fact is, I've never really gotten DVDs to work very well without installing totem-xine. Maybe you don't want to do that, but if you haven't tried it, consider installing totem-xine? --Plumpy 23:32, 25 September 2007 (UTC)
- Here's what I get when I install totem-xine from Synaptic:
SteveSims 00:32, 26 September 2007 (UTC)
- I decided to install some more xine plugins but now Totem closes immediately after opening if I insert a DVD. Here's a log of my xine package installations:
Commit Log for Tue Sep 25 17:25:49 2007 Installed the following packages: libxine1-console (1.1.7-1ubuntu1) libxine1-gnome (1.1.7-1ubuntu1) libxine1-plugins (1.1.7-1ubuntu1) Commit Log for Tue Sep 25 17:23:33 2007 Installed the following packages: libpostproc1d (3:0.cvs20070307-5ubuntu4) libxine1-ffmpeg (1.1.7-1ubuntu1) Commit Log for Tue Sep 25 17:14:25 2007 Removed the following packages: totem-gstreamer Installed the following packages: libmodplug0c2 (1:0.7-5.2ubuntu1) libpulse0 (0.9.6-1ubuntu2) libxcb-shape0 (1.0-3) libxcb-shm0 (1.0-3) libxcb-xv0 (1.0-3) libxcb1 (1.0-3) libxine1 (1.1.7-1ubuntu1) libxvmc1 (2:1.0.4-2ubuntu1) totem-xine (2.20.0-0ubuntu1)
x86 vs 64bit on core 2 duo
What to choose? Why, why not?
- In my case, I've installed the 64bit kernel. I develop some of my own software which has a fair amount of optimizations with the 64-bit architecture. Rybu
- 64-bit will run faster. I say install the AMD64 version. Don't let your new, fast 64-bit processor go to waste! SteveSims 06:16, 5 October 2007 (UTC)
Black screen at boot
When try to boot gutsy-desktop-amd64 the screen turns black, even when i use "Safe Graphics" mode. Having a nVIDIA Quadro NVS 140M card
TURNS OUT I JUST NEED PATIENCE... sorry
Update 2007-10-11 works fine
Announcement. SteveSims 05:15, 2 October 2007 (UTC)
I have enabled laptop-mode (level 2) and also used PowerTOP to optimize the power consumption of my T61 with NVIDIA 140M. But even though the brightness is set at minimum the power consumption just does not want to drop below 19W. Is this a usual behaviour?