a grey geek learning by mistakes

Ubuntu Learner

February 13th, 2007 at 10:37 am

Some progress with the Razr?

in: mobile

If you glance at the previous post [Permanent Link] you’ll see that the Terminal spewed out a lot of seeming nonsense when I tried to start the Motorola Linux Manager. Well, it’s not nonsense at all of course.

If you follow the instructions of Jun-Dai on the Unbuntu Forum re Reload this Page X Error: BadDevice, invalid or uninitialized input device 168 you will get rid of it.

The error is most likely due to some “wacom” devices in your xorg.conf”

My xorg.conf file is arranged somewhat differently, and yours may be too, but essentially the lines he mentions are probably all there. Be careful not to comment out any other lines!

Another contributor called rand0m3r gave this formula to start the xorg.conf from the Terminal:
kate /etc/X11/xorg.conf

but it didn’t work for me, somehow. Permission denied, etc even though I was using it as root. (In Ubuntu, you type in sudo su, then give your password, to work as root).

So I went to File System/etc/X11/xorg.conf

right-clicked on the file, chose Scripts/geddit-root, typed in the password and that allowed me to edit and save the file.

That was in the late am so when I rebooted this morning, opened the the terminal, did my sudu su and password, then typed: moto4lin

the Motorola for Linux manager launched and lo, all of that bumpf had gone.
This had replaced it (in Terminal)

Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Form1
PhoneMan
New mode: 1
P2kProc::doConnect()
(E_sendControl: no connection)
(E_fileCount: E001)
(E_fileList: E000)
doActConnect
doActConnect
P2kProc::doConnect()
(E_sendControl: no connection)
(E_drv_reboot: E001)
doActConnect
doActConnect
P2kProc::doConnect()

It still didn’t connect to the phone but I got the intriguing message that the phone was busy.

[error] Unable to get file list
Try to connect
[error] Phone is busy. Please try later
[error] Unable to connect

The saga will obviously continue…

 

RSS feed for comments on this post | TrackBack URI