Melissa - Mark did mean that USB stick you created to install Peppermint. If you boot using that, you can check your HDD for errors as the system will be running from the USB, not the HDD (technically, when you boot from USB, you could unplug the HDD - it’s completely uninvolved).
There’s a series of commands you’d need to run from a terminal once booted from USB (to run fsck against the HDD partition), I can’t give them right now as I’m a bit busy, but I’ll try to check in tonight/tomorrow morning!
Sorry, I must have missed that posting … thanks chemicalfan … yes, I mean have you still got the Peppermint installation disk, or installation USB stick ?
Can you remember how to boot the USB stick ? … or did you NEED to create a CD ?
What I need you to do is boot the Peppermint LiveCD or LiveUSB, then select “Try Peppermint” NOT “Install Peppermint”
Eventually you’ll end up at a Peppermint desktop with an icon called “Install Peppermint” … if you can see that icon on the desktop, you’re in a “Live” environment.
DO NOT open the file manager, or do anything else that may mount the partition
Just open a terminal (Ctrl+Alt+T)
and run:
sudo fsck -f /dev/sda1
to run the file system check.
DO NOT run that command unless booted to the LiveCD/LiveUSB … or if the hard drive is mounted … running fsck on a mounted partition can screw up your file system.
You sent me files to download onto the data stick then we ripped some files to the CD, which loaded Peppermint onto this laptop. So I presume we use the CD.
fsck won’t let you execute it against a mounted filesystem (ext3/4, at least)
Melissa - I’m not sure why that response came up. I’m also not sure what the “-f” switch does :-[
Try booting from the liveCD again, selecting Try Peppermint, then loading up a terminal window, and run:
There could be two (amongst other) reasons why it is running slowly:
a) High temperatures forcing the CPU into limp mode or
b) Agressive power saving forcing the CPU to its lowest frequency available.
To test current temperature:
You might need to install lm-sensors:
sudo apt-get install lm-sensors
then (run a few times to get temperatures)
sensors
To get current CPU frequency:
You might need to install cpufrequtils
Thanks Se Zo- maybe this will shed some light to you- I don’t know what it means:
melissa@melissa-HP-Compaq-nx6325-RH628ES-ABU ~ $ sudo apt-get install lm-sensors[sudo] password for melissa:
Reading package lists… Done
Building dependency tree
Reading state information… Done
lm-sensors is already the newest version.
lm-sensors set to manually installed.
The following packages were automatically installed and are no longer required:
language-pack-en-base language-pack-kde-en libwxgtk2.8-0
language-pack-kde-en-base kde-l10n-engb libwxsqlite3-2.8-0 libwxbase2.8-0
firefox-locale-en language-pack-en amarok-help-en
Use ‘apt-get autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded.
melissa@melissa-HP-Compaq-nx6325-RH628ES-ABU ~ $ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +38.0°C (crit = +105.0°C)
temp2: +38.0°C (crit = +100.0°C)
temp3: +16.0°C (crit = +100.0°C)
melissa@melissa-HP-Compaq-nx6325-RH628ES-ABU ~ $ sudo apt-get install cpufrequtils
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
language-pack-en-base language-pack-kde-en libwxgtk2.8-0
language-pack-kde-en-base kde-l10n-engb libwxsqlite3-2.8-0 libwxbase2.8-0
firefox-locale-en language-pack-en amarok-help-en
Use ‘apt-get autoremove’ to remove them.
The following extra packages will be installed:
libcpufreq0
The following NEW packages will be installed
cpufrequtils libcpufreq0
0 upgraded, 2 newly installed, 0 to remove and 80 not upgraded.
Need to get 49.3 kB of archives.
After this operation, 275 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 Index of /ubuntu precise/universe libcpufreq0 i386 007-2 [13.3 kB]
Get:2 Index of /ubuntu precise/universe cpufrequtils i386 007-2 [36.0 kB]
Fetched 49.3 kB in 0s (49.3 kB/s)
Preconfiguring packages …
Selecting previously unselected package libcpufreq0.
(Reading database … 196813 files and directories currently installed.)
Unpacking libcpufreq0 (from …/libcpufreq0_007-2_i386.deb) …
Selecting previously unselected package cpufrequtils.
Unpacking cpufrequtils (from …/cpufrequtils_007-2_i386.deb) …
Processing triggers for man-db …
Processing triggers for ureadahead …
ureadahead will be reprofiled on next reboot
Setting up libcpufreq0 (007-2) …
Setting up cpufrequtils (007-2) …
Loading cpufreq kernel modules… [ OK ]
CPUFreq Utilities: Setting ondemand CPUFreq governor… * CPU0… [ OK ]
Processing triggers for libc-bin …
ldconfig deferred processing now taking place
melissa@melissa-HP-Compaq-nx6325-RH628ES-ABU ~ $ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.80 GHz
available frequency steps: 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor “ondemand” may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.80 GHz:25.40%, 1.60 GHz:20.21%, 800 MHz:54.40% (24888)
melissa@melissa-HP-Compaq-nx6325-RH628ES-ABU ~ $
