Ubuntu上安装与使用putty - philips_lu的日志 -
电子工程世界-论坛
Ubuntu上安装与使用putty
已有 973 次阅读 02:58
|个人分类:
Ubuntu上安装与使用putty& && &下面便是小弟学习安装和是用Putty的过程：
& && & 首先，输入如下命令，并按下Tab键，发现库中存在三个与Putty 相关的文件，直接使用Putty便可：
planck@planck-Ubuntu:/dev$ sudo apt-get install putty
putty& && &&&putty-doc& & putty-tools&&
planck@planck-Ubuntu:/dev$ sudo apt-get install putty
[sudo] password for planck:
Reading package lists... Done
Building dependency tree& && &
Reading state information... Done
The following extra packages will be installed:
&&putty-tools
Suggested packages:
&&putty-doc
The following NEW packages will be installed:
&&putty putty-tools
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
Need to get 581 kB of archives.
After this operation, 2,421 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
//系统会提示您是否要继续，为了达到目的就不得不继续，输入y并按Enter继续：
trusty/universe putty-tools amd64 0.63-4 [297 kB]
trusty/universe putty amd64 0.63-4 [284 kB]
Fetched 581 kB in 11s (52.6 kB/s)& && && && && && && && && && && && && && && &
Selecting previously unselected package putty-tools.
(Reading database ... 198687 files and directories currently installed.)
Preparing to unpack .../putty-tools_0.63-4_amd64.deb ...
Unpacking putty-tools (0.63-4) ...
Selecting previously unselected package putty.
Preparing to unpack .../putty_0.63-4_amd64.deb ...
Unpacking putty (0.63-4) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.54ubuntu1) ...
Setting up putty-tools (0.63-4) ...
Setting up putty (0.63-4) ...
//呵呵，终于安装完成了，进入putty试一下
planck@planck-Ubuntu:/dev$ sudo putty
要求输入管理员密码的哦：sudo] password for planck:
选择串口，并设定串口号为/dev/ttyUSB0,波特率为115200,开始愉快之旅：
**注意，在使用串口通信的过程需要先打开软件再给目标机上电启动，对于使用SSH网络链接的过程则必须要先让系统正常工作之后方可进行链接，否则会出错！！！！切记！！！
(putty:7148): IBUS-WARNING **: The owner of /home/planck/.config/ibus/bus is not root!
(putty:7148): GLib-CRITICAL **: Source ID 1088 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1161 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1254 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1487 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1629 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1720 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1721 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1750 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1918 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1919 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1997 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 1998 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2172 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2342 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2344 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2357 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2390 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2475 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2560 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2587 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2830 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2832 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 2835 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3067 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3069 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3072 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3156 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3213 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3216 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3303 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3457 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3520 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3522 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3737 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3739 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3742 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3882 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3885 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 3888 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4111 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4140 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4248 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4383 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4649 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4651 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4757 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4878 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 4998 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5069 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5071 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5074 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5121 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5123 was not found when attempting to remove it
(putty:7148): GLib-CRITICAL **: Source ID 5158 was not found when attempting to remove it
//这是Putty窗口现实的内容，直接Copy,这里面包含了整个系统的引导过程
U-Boot SPL 2013.04-dirty (May 06 2013 - 16:12:47)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep,
USB Peripheral mode controller at
using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep,
USB Host mode controller at
using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (May 06 2013 - 16:12:47)
I2C:& &ready
DRAM:&&512 MiB
WARNING: Caches not enabled
NAND:&&No NAND device found!!!
MMC:& &OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep,
USB Peripheral mode controller at
using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep,
USB Host mode controller at
using PIO, IRQ 0
Net:& &&ethaddr& not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:&&0
gpio: pin 53 (gpio 53) value is 1
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc0(part 0) is current device
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
No micro SD card found, setting mmcdev to 1
mmc_send_cmd : timeout: No status update
mmc1(part 0) is current device
mmc_send_cmd : timeout: No status update
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
14 bytes read in 3 ms (3.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
gpio: pin 55 (gpio 55) value is 1
4394080 bytes read in 795 ms (5.3 MiB/s)
gpio: pin 56 (gpio 56) value is 1
23469 bytes read in 52 ms (440.4 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
& &Image Name:& &Angstrom/3.8.13/beaglebone
& &Image Type:& &ARM Linux Kernel Image (uncompressed)
& &Data Size:& & 4394016 Bytes = 4.2 MiB
& &Load Address:
& &Entry Point:&&
& &Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
& &Booting using the fdt blob at 0x80f80000
& &XIP Kernel Image ... OK
& &Using Device Tree in place at 80f80000, end 80f88bac
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[& & 0.193780] omap2_mbox_probe: platform not supported
[& & 0.204532] tps65217-bl tps65217-bl: no platform data provided
[& & 0.280991] bone-capemgr bone_capemgr.9: slot #0: No cape found
[& & 0.318100] bone-capemgr bone_capemgr.9: slot #1: No cape found
[& & 0.355206] bone-capemgr bone_capemgr.9: slot #2: No cape found
[& & 0.392315] bone-capemgr bone_capemgr.9: slot #3: No cape found
[& & 0.423872] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[& & 0.488557] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800. cannot claim for gpio-leds.8
[& & 0.500293] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[& & 0.507603] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[& & 1.249377] systemd[1]: Failed to insert module 'autofs4'
[& & 1.539874] systemd[1]: Failed to open /dev/autofs: No such file or directory
[& & 1.547474] systemd[1]: Failed to initialize automounter: No such file or directory
[& & 1.555610] systemd[1]: Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
systemd-fsck[82]: Angstrom: clean,
files, 820 blocks
[& & 5.035251] libphy: PHY 4a101000.mdio:01 not found
[& & 5.040352] net eth0: phy 4a101000.mdio:01 not found on slave 1
|& && & |& && && && && && &.-.& && && &&&o o
|& &|& &|-----.-----.-----.| |& &.----..-----.-----.
|& && & |& &&&| __&&|&&---'| '--.|&&.-'|& &&&|& &&&|
|& &|& &|&&|&&|& &&&|---&&||&&--'|&&|&&|&&'&&| | | |
'---'---'--'--'--.&&|-----''----''--'&&'-----'-'-'-'
& && && && && & -'&&|
& && && && && & '---'
The Angstrom Distribution BeagleBone_Black ttyO0
Angstrom v2012.12 - Kernel 3.8.13
BeagleBone_Black login: root
Last login: Fri Dec 31 19:00:20 EST 1999 on ttyO0
root@BeagleBone_Black:~# pwd
/home/root
root@BeagleBone_Black:~# ifconfig
eth0& && &Link encap:Ethernet&&HWaddr C8:A0:30:B9:7F:2B
& && && & UP BROADCAST MULTICAST&&MTU:1500&&Metric:1
& && && & RX packets:0 errors:0 dropped:0 overruns:0 frame:0
& && && & TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
& && && & collisions:0 txqueuelen:1000
& && && & RX bytes:0 (0.0 B)&&TX bytes:0 (0.0 B)
& && && & Interrupt:56
lo& && &&&Link encap:Local Loopback
& && && & inet addr:127.0.0.1&&Mask:255.0.0.0
& && && & UP LOOPBACK RUNNING&&MTU:65536&&Metric:1
& && && & RX packets:4 errors:0 dropped:0 overruns:0 frame:0
& && && & TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
& && && & collisions:0 txqueuelen:0
& && && & RX bytes:248 (248.0 B)&&TX bytes:248 (248.0 B)
root@BeagleBone_Black:~# shutdown --p now
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
Unmounting /sys/kernel/config.
Unmounting /sys/kernel/debug.
Unmounting /dev/mqueue.
Unmounting /etc/machine-id.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
Detaching loopback /dev/loop7.
Detaching loopback /dev/loop6.
Detaching loopback /dev/loop5.
Detaching loopback /dev/loop4.
Detaching loopback /dev/loop3.
Detaching loopback /dev/loop2.
Detaching loopback /dev/loop1.
Detaching loopback /dev/loop0.
All loop devices detached.
Detaching DM devices.
All DM devi[&&415.790271] (NULL device *): gadget not registered.
ces detached.
[&&415.797272] Power down.
[&&415.802674] Kernel panic - not syncing: Attempted to kill init! exitcode=0x
[&&415.802674]
[&&415.812251] [&c001051d&] (unwind_backtrace+0x1/0x8c) from [&c0385d41&] (panic+0x55/0x14c)
[&&415.820803] [&c0385d41&] (panic+0x55/0x14c) from [&c002ec8f&] (do_exit+0x2ef/0x5dc)
[&&415.828803] [&c002ec8f&] (do_exit+0x2ef/0x5dc) from [&c0036983&] (sys_reboot+0xb5/0x126)
[&&415.837249] [&c0036983&] (sys_reboot+0xb5/0x126) from [&c000c641&] (ret_fast_syscall+0x1/0x46)
[&&415.846242] drm_kms_helper: panic occurred, switching back to text console
下面我们使用网络链接进行远程控制：
planck@planck-Ubuntu:/dev$ sudo putty
[sudo] password for planck:
选择ssh并输入目标机的ip:10.0.1.118
login as: root
root@10.0.1.118's password:
root@BeagleBone_Black:~# ifconfig
eth0& && &Link encap:Ethernet&&HWaddr C8:A0:30:B9:7F:2B
& && && & inet addr:10.0.1.118&&Bcast:10.0.255.255&&Mask:255.255.0.0
& && && & UP BROADCAST RUNNING MULTICAST&&MTU:1500&&Metric:1
& && && & RX packets:68 errors:0 dropped:0 overruns:0 frame:0
& && && & TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
& && && & collisions:0 txqueuelen:1000
& && && & RX bytes: KiB)&&TX bytes:1 KiB)
& && && & Interrupt:56
lo& && &&&Link encap:Local Loopback
& && && & inet addr:127.0.0.1&&Mask:255.0.0.0
& && && & UP LOOPBACK RUNNING&&MTU:65536&&Metric:1
& && && & RX packets:6 errors:0 dropped:0 overruns:0 frame:0
& && && & TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
& && && & collisions:0 txqueuelen:0
& && && & RX bytes:427 (427.0 B)&&TX bytes:427 (427.0 B)
作者的其他最新日志
评论 ( 个评论)
Powered byScreen Resolution Problem with Ubuntu 14.04 and VirtualBox - Ask Ubuntu
to customize your list.
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.
Here's how it works:
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
Environment: Lenovo T530 running Windows 7.
Have installed Ubuntu 14.04 on a virtual machine using VM Virtual Box.
Have installed all the updates from both Virtual Box and Ubuntu.
Problem: While in Ubuntu's desktop and other Ubuntu initiated programs, the window is reduced to about 3x4 inches showing in the middle of the rest of my regular Virtual Box window.
I am seeing only the upper right hand of the screen output of what I would normally see.
Please help.
But, none of these answers works in 14.04.
36.3k1163105
You basically need the Guest additions, log into the Virtual Machine to install the following packages:
sudo apt-get install virtualbox-guest-dkms
Finally restart the VM to complete the installation.
36.3k1163105
On virtualbox you have to install "Guest Additions". There is no need to set a resolution via Ubuntu settings. With your guest window in the foreground select from the top menu:
VirtualBox -& Devices -& Insert Guest Additions CD image
In Ubuntu open a terminal, navigate to cd folder (usually /media/VBOXADDITIONS*) and run
sh ./VBoxLinuxAdditions.run
Note that you should have a working compiler gcc/g++
I had the same problem as you. I did these steps, maybe helps you too:
Go to System settings → Software and Updates → Additional drivers
Use x86 virtualization solutions...
After that reboot your VirtualBox
My VirtualBox is working perfectly.
After having first tried installing the Guest additions, which didn't work, I found another solution elsewhere: .
Use Xdiagnose from the Dashboard. Search for and launch Xdiagnose, then enable all the options under the Debug section. Click the Apply button, then close the window and restart the system.
That's what finally did the trick! Now I get 1024 x 768 resolution instead of 640 x 480.
I never uninstalled the Guest additions, so it might be I needed to take both these measures.
---------- EDIT ---------
I have come to realize that the solution described above is just a fallback, in case installing the Guest Additions failed for some reason. I have finally managed to successfully install them, and can now choose from a bigger range of resolutions in the display settings. Here is how I did it, after having tried all of the above.
One thing I had already tried earlier was
sudo apt-get install virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11
This is not enough in itself, but might be a necessary prerequisite for the following steps (of which some might not be necessary...).
Update Virtualbox to the latest version (currently 4.3.24)
In Terminal in the Guest system type:
sudo apt-get install dkms
sudo apt-get install build-essential module-assistant
sudo m-a prepare
If you have no top menu in the Guest system, it's because you're in scale mode which causes it to be hidden. In that case, press
Host + C to toggle scale mode (where Host is Right Control by default)
In the Guest system, go to the top menu, and click Devices->Insert Guest Additions CD Image. This should mount the CD image.
In my case, Autostart worked, and the installation started with a prompt. If it doesn't autostart, you can do the following
cd /media/&username&/VBOXADDITIONS_4.3.10_93012
sudo ./VBoxLinuxAdditions.run
Just be sure to replace &username& by the logged in user's username.
And then a restart, as JTIM pointed out...
Developing from , and in fact pretty well explained also in . (I really tried everything else posted here but it does not seem to work on my Windows 7 system)
Preliminary steps:
Make sure you have installed the (*). Be careful that if you ask Virtual Box to update to the latest version it might very likely declare being updated even if a newer version exists!
It might be a good idea to start from a clean distribution, creating a new virtual machine, install there Ubuntu (I allowed downloading updated packages from the network during installation), and cloning it before proceeding, so that if you have troubles you can avoid restarting from the very beginning.
Install build-essential and linux-headers-generic packages. Apparently, , as "Running DKMS in the guest OS will keep Guest Additions installed after a guest kernel update".
Start your virtual machine
On Virtualbox menu -> Devices -> Insert Guest Additions CD image...
From Ubuntu you should see a popup, allow the CD autorun to install the program. For me, like many times before, it said he could not find Linux headers but, this time, in the end everything went fine.
If the autorun does not work,
open a terminal (Ctrl+Alt+T), navigate to folder (usually /media/VBOXADDITIONS*) and run
sh ./VBoxLinuxAdditions.run
Shut down and then start again your virtual machine
(*) If, like me, with the new version of the Virtual Box you have trouble with network, take a look at
(In short: use Bridged network, and select "allow VMs")
I had the same problem. I fixed it by installing the guest additions as explained in the other answers and jacking the amount of video RAM in the settings as shown.
7,49341852
To expand on what Sylvain Pineau said, typing sudo apt-get install virtualbox* is much easier (wildcards are accepted with apt-get).
I remained stuck for several days in low screen resolution in a Ubuntu 14.04 guest running on VirtualBox 4.1 on Debian Wheezy. None of the most commonly suggested solutions (e.g. installing virtualbox-guest-dkms, installing guest additions) helped. Installing VirtualBox from the
protected by
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10
on this site.
Would you like to answer one of these
Not the answer you're looking for?
Browse other questions tagged
Ubuntu and Canonical are registered trademarks of Canonical Ltd.
Ask Ubuntu works best with JavaScript enabled}