Showing posts with label Problem. Show all posts
Showing posts with label Problem. Show all posts

Monday, November 30, 2015

Slow shutdown/reboot when mounting CIFS/SMB shares on Ubuntu and derivatives

My laptop with Linux Mint 17.2 suddenly started taking full minutes for every reboot/shutdown. What might have caused it?

I then remembered I had previously placed some new entries in the fstab, since I needed to mount some remote CIFS shares. Could this be the culprit?

Well, it seems it was exactly that: there is a bug in Network Manager which shuts down before unmounting the network shares. This will cause CIFS to hang and wait for 60 seconds or so for every share.

Even though the Ubuntu Wiki says that this bug has been solved since version 12.04, I have applied the suggested solution and it worked.
Now the shutdowns/reboots happen in an instant!

So, is the bug back? I don't know, but what I know is that this is how to fix this problem:
sudo ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K14umountnfs.sh
sudo ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K14umountnfs.sh

Thursday, November 26, 2015

Disable touchpad while writing

I'm now running Linux Mint 17.2 "Rafaela" on my Amilo SI1520, but even though there is a specific option to disable the touchpad while writing (you can find it in Preferences > Mouse & Touchpad) this solution wouldn't work.

The workaround is easy though, and can be accomplished by using the command syndaemon:

syndaemon -d -i 1
This disable the touchpad while typing on the keyboard, and will enable it again 1 second after the last key has been pressed. The -d option makes the command run as a daemon.

If you only want to disable tapping and scrolling (but not the mouse movements) when you type, just add the -t option:

syndaemon -d -t -i 1
To avoid having to type the command every time you logon, simply put the command above as a new entry in System > Preferences > Startup Applications

Tuesday, April 15, 2008

eBay gone crazy

Today, eBay shipping fees for some items I've put in my "my eBay" page have gone crazy.
Look at these shipping costs: one million dollars to ship a $5 item!


Luckily if I enter the items' auction pages, the shipping fees go back to normal. :-)

Wednesday, March 19, 2008

Seagate FreeAgent Desktop USB Drives on Ubuntu 7.10

A few weeks ago, I've bought an external USB drive. I chose a Seagate FreeAgent Desktop 500Gb, even though I knew it would not work 100% smoothly in Ubuntu. Anyway, I've read around about the problems it might give in linux and I was well prepared to solve them. Unfortunately the only problem I encountered after I bought it, was different from anything I've read on the various forums I browsed before buying.

Basically, the disk automounted only the first time I plugged it in my PC. From that moment on, when I plug it in, the front led would blink for some time, but nothing else would happen. I tried to unplug both the USB cable and the power cable, which seemed to work for some people, but it wouldn't solve my problem.

So, I had to solve in some other way.

I've found this "workaround" online, but I can't find the link anymore. Anyway here is what I did, for those people who might be interested:

STEP 1:
Open a terminal and give the following command:

sudo vol_id /dev/sd##

Where "##" is the partition of the FreeAgent drive (letter and number change from system to system, you just have to guess yours if you don't already know it. Mine, for example, is "d1", making the command "sudo vol_id /dev/sdd1").
This command will report a few info about your disk. Copy the UUID code of the disk/partition, it's a long series of numbers (and sometimes letters)

STEP 2:
Edit /etc/fstab and add the following line:

UUID=longnumber /media/MOUNTPOINT FILESYSTEM user,defaults 0 0

where:
longnumber is the uuid code of the partition you obtained in Step 1
MOUNTPOINT is the directory where you want the disk to be mounted (create the directory if you don't already have it: "sudo mkdir /media/MOUNTPOINT")
FILESYSTEM is the filesystem present on the drive (ntfs? ext3? vfat?)
user should let you mount the Freeagent hard disk without root permissions (but it did not work for me, see below)

STEP 3:
Create a script to mount/unmount your drive (change parameters where necessary).
Save it (I called it 'freeagent'), make it executable and copy/move it somewhere in your path (for example /usr/local/bin)
#!/bin/bash

if `mount grep -q /media/MOUNTPOINT`
then umount /media/MOUNTPOINT
else mount /media/MOUNTPOINT
fi

You then plug the USB drive, wait until its led stops blinking and then launch the script from a terminal (you can also create a shortcut on your desktop for ease of use, if you want).
It works this way: it checks whether the disk is mounted. If it is, it unmounts it. If it's not, it mounts it.
As I said in Step 2, the user option we wrote in the fstab should mount the disk without the need for root permissions, but it did not work for me. I had to edit the script and add "sudo" before 'umount' and 'mount' to make it work:

#!/bin/bash
if `mount grep -q /media/MOUNTPOINT`
then sudo umount /media/MOUNTPOINT
else sudo mount /media/MOUNTPOINT
fi

If you are making it a desktop shortcut to be launched by clicking on it, change sudo with the "graphical" command needed by your desktop environment (for example: "gksu" if using Gnome or "kdesudo" if using KDE).

Tuesday, August 7, 2007

Problem with Wine /2

Sorry for not posting in a while, but the laptop worked just fine lately, so there really was not too much to be said.
The problem with Wine described in the previous post still presents itself intermittently. Oh well, anyway I pretty much got used to it, so if I have to launch any Windows application, I just do that and then I go out for a cup of coffee, so that when I come back the app would be loaded and running. :-)

Another problem with Wine occurred lately though. Although it's not really a problem with Wine, it's more of a problem with Firefox. In fact, when I visit a site which has a flash application (for example YouTube's movies) Firefox stops working and a Wine Desktop appears. As soon as I close the Wine desktop, everything goes back to working fine again.
Still, it's an odd problem, and I can't seem to solve it.

I've already uninstalled and reinstalled both firefox and the flash plugin, with no success.
Even reinstalling Wine did not work... who knows?

Wednesday, June 20, 2007

Problem with wine

I'm not an alcoholic or something. I've just been having problems with WINE ("Wine Is Not an Emulator"), the Open Source implementation of Windows API on top of Unix/Linux.

It all worked well until a couple weeks ago. I don't know what was changed, but suddenly applications began to start very slowly (they can take even a few minutes before they are launched).

I've tried to downgrade to previous versions, tried previous kernel version, tried reinstalling wine... nothing. The problem remains.

On the contrary on my desktop PC, everything is fine. So I'm starting to believe it's a problem related with my laptop. :(

If anyone has any suggestion, I'm listening!

Thursday, May 3, 2007

Windows Vista Activation Failed

I booted Windows Vista about one hour ago and was greeted by a warning that my copy of Windows is not "Genuine".
Considering that it came with the laptop, that I paid for it, and that it has a "Genuine Windows Product" sticker on its back, isn't all this shocking? And isn't it just another demonstration of how poorly Microsoft respects their customers?
I understand that piracy is a common problem and that it hurts the industry (although I sometimes wonder how much it really hurts, considering Microsoft's income), but these anti-piracy measures are insane. They only affect honest customers, since those who use pirate copies of these softwares have probably cracked their copy and will never be affected by these anti-piracy thingies.
I'm sure the misunderstanding will be solved as soon as I manage to call the 800 number provided, but still I wasted almost an hour trying to re-activate my legitimate copy of Vista, which is not able to recognize itself as such.
Thank God for Ubuntu.

Monday, April 16, 2007

Touchpad finally working again after a Suspend/Resume in Feisty

As suggested by fellow user skipper (who I thank very much) there is a way to make the touchpad work after a suspend/resume.

The solution is a downgrade of the BIOS of the laptop to version 1.10. The problem, in fact, seems to be related to the two latest versions of the BIOS (v1.19 and v1.20). Anyone who does not necessarily need one of these two later BIOS versions, should downgrade to v1.10 to make suspend work.

If your SI1520 does not mount an Intel Core Duo (Yonah) D0 stepping processor (which means mainly those CPUs coded T2x00) you can downgrade to version 1.10. Otherwise you'll have to stick with a BIOS version >= 1.17 and with no touchpad after resume. :-(

v1.19 is officially the initial BIOS for Windows Vista 32bit, so downgrading could bring up problems with Vista. I couldn't find anything wrong in my brief test, but I don't plan to be using Vista much, so that's not so important to me.

Please leave a comment with your experiences with this matter, as it can help other fellow SI1520 owners. Thanks.

Necessary legal disclaimer:

Reasonable effort is made to ensure that the information provided on this blog is accurate, however, no guarantees for the currency or accuracy of information are made. This blog's information is provided "as is", without warranty of any kind, whether expressed or implied.

This blog and its author make no guarantee and hold no responsibility for any damage, injury, loss of property, loss of data, loss of any and all resources, or any negative influence what-so-ever, that may result from any and all usage of the information found on this blog, or linked from this blog.

Negative consequences of your usage of this blog are solely your problem and your responsibility. All consequences of the usage of this blog do not involve this blog and its author, at all, ever. You hold full responsibility for your actions.

Use this blog's information resources at your own risk.

4-in-1 Card Reader working again

Updating the kernel to version 2.6.20-15-generic in Ubuntu Feisty 7.04 beta (which should become soon a no-more-beta, since the definitive launch is expected for the end of this week) has fixed the problem with the internal 4-in-1 card reader of the SI1520 that was mentioned in this previous post.

Thursday, April 12, 2007

Feisty beta's Network Manager OK Again

A new update of the Network Manager package for Ubuntu Feisty beta has been released today.
The first reports indicate that everything has gone back to normal.
I have not updated yet, so I can not verify. I will do ASAP.
But the network should now work again.

*EDIT*: I've just updated. Everything looks fine.

Wednesday, April 11, 2007

WARNING: Feisty beta, Updates of April 11, 2007


If you have installed Ubuntu Feisty beta on your SI1520:

DO NOT INSTALL TODAY'S UPDATES (April 11).

Something is wrong with the update, and the network manager stops working. As a consequence, network adapters are not recognized anymore, the wireless IPW3945 will not work, and the "cabled" network will work only after setting it up again (but you will not have any confirmation from the network manager icon, since this won't work).

You have been warned! ;)

*EDIT*:

Temporary solution:
Until the problem is solved, it is possible to downgrade the network manager to the previous (working) version:

sudo dpkg -i /var/cache/apt/archives/
network-manager_0.6.4-6ubuntu4_i386.deb
(please notice: it's a single line of code)


This will work if you still have the package in your cache.

Saturday, April 7, 2007

OpenSUSE 10.2 LiveDVD

I wanted to try OpenSUSE 10.2, since it's said to have the best hardware support among all distros. I inserted the LiveDVD in the CD/DVD reader of the SI1520, and it booted.
After a few seconds, a choice is given to boot the Gnome LiveDVD or the KDE LiveDVD. I chose Gnome and pressed Return.
The DVD started to spin, a splash screen appeared, and then the screen went black with a number of errors. The last few rows stated:

"Cannot find the CD I was booted from - doh!"

And everything stopped. If this is the distro with the best hardware support... :)

*EDIT*: I managed to make the LiveDVD boot by entering the BIOS and enabling 32-bit performance for the CD/DVD drive. Now testing.