jani@sargeX:~/tmp/conan$ ls
tvtime-output-23:50:49.png
tvtime-output-23:51:02.png
tvtime-output-23:51:22.png
tvtime-output-23:51:32.png
tvtime-output-23:51:37.png
tvtime-output-23:52:07.png
tvtime-output-23:53:00.png
tvtime-output-23:53:11.png
tvtime-output-23:53:39.png
tvtime-output-23:53:42.png
tvtime-output-23:54:11.png
tvtime-output-23:54:27.png
tvtime-output-23:54:43.png
tvtime-output-23:55:27.png
tvtime-output-23:55:30.png
tvtime-output-23:55:33.png
tvtime-output-23:55:41.png
tvtime-output-23:55:54.png
jani@sargeX:~/tmp/conan$ for i in * ; do \
> echo mv $i `echo $i | tr [:] [_]` >> tee.sh ; done
jani@sargeX:~/tmp/conan$ cat tee.sh
mv tvtime-output-23:50:49.png tvtime-output-23_50_49.png
mv tvtime-output-23:51:02.png tvtime-output-23_51_02.png
mv tvtime-output-23:51:22.png tvtime-output-23_51_22.png
mv tvtime-output-23:51:32.png tvtime-output-23_51_32.png
mv tvtime-output-23:51:37.png tvtime-output-23_51_37.png
mv tvtime-output-23:52:07.png tvtime-output-23_52_07.png
mv tvtime-output-23:53:00.png tvtime-output-23_53_00.png
mv tvtime-output-23:53:11.png tvtime-output-23_53_11.png
mv tvtime-output-23:53:39.png tvtime-output-23_53_39.png
mv tvtime-output-23:53:42.png tvtime-output-23_53_42.png
mv tvtime-output-23:54:11.png tvtime-output-23_54_11.png
mv tvtime-output-23:54:27.png tvtime-output-23_54_27.png
mv tvtime-output-23:54:43.png tvtime-output-23_54_43.png
mv tvtime-output-23:55:27.png tvtime-output-23_55_27.png
mv tvtime-output-23:55:30.png tvtime-output-23_55_30.png
mv tvtime-output-23:55:33.png tvtime-output-23_55_33.png
mv tvtime-output-23:55:41.png tvtime-output-23_55_41.png
mv tvtime-output-23:55:54.png tvtime-output-23_55_54.png

-O Optimize; remove unused color-table entries. Normally these
trigger an error message and disable -d (but conversion is
completed anyway). Also, use zlib compression level 9 (best
compression) instead of the default level. The recovery
algorithm enabled by -r is as follows: Unused color table
entries will not trigger an error message as they normally
do, but will still be preserved unless -O is also on, in
which case they will be discarded. Missing color tables will
be patched with a default that puts black at index 0, white at
index 1, and supplies red, green, blue, yellow, purple and
cyan as the remaining color values. Missing image pixels will
be set to 0. Unrecognized or corrupted extensions will be
discarded.

Residential Network Statistics
Your IP address: 130.234.192.123

Quota used: 43.75%
Traffic transferred: 437.5 MB
You can transfer: 562.5 MB (462.5 MB until starting to slow traffic speed)

jani@sargeX:~/omat/photos/Sony/[04-05-25] --- Siiri ja Irma$ umount -v /mnt/Sony/
umount: /mnt/Sony: laite on varattu
umount: /mnt/Sony: laite on varattu

[...]
Updating mozilla chrome registry...done.
Removing mozilla-psm ...
Updating mozilla chrome registry...done.
Removing mozilla-browser ...

Mem: 515672 372672 143000 0 28344 137276
-/+ buffers/cache: 207052 308620
Swap: 1991976 0 1991976
jani@sargeX:~$ free
total used free shared buffers cached
Mem: 515672 386552 129120 0 29920 140408
-/+ buffers/cache: 216224 299448
Swap: 1991976 0 1991976
jani@sargeX:~$ free
total used free shared buffers cached
Mem: 515672 393560 122112 0 30884 140968
-/+ buffers/cache: 221708 293964
Swap: 1991976 0 1991976
jani@sargeX:~$ free
total used free shared buffers cached
Mem: 515672 409528 106144 0 32544 145988
-/+ buffers/cache: 230996 284676
Swap: 1991976 0 1991976
jani@sargeX:~$

a:link {
color: #555;
text-decoration: none;
padding-bottom: 2px;
background: transparent url(/kuvat/viiva.gif) repeat-x bottom;
}

localepurge: Disk space freed in /usr/share/locale: 177248K
localepurge: Disk space freed in /usr/share/man: 1996K

Total disk space freed by localepurge: 179244K

Description: Automagically removing unnecessary locale data
This is just a simple script to recover diskspace wasted for unneeded
locale files and localized man pages. It will automagically be invoked
upon completion of any apt installation run.
.
Please note, that this tool is a hack which is *not* integrated with
Debian's package management system and therefore is not for the faint
of heart. This program interferes with the Debian package management
and does provoke strange, but usually harmless, behaviour of programs
related with apt/dpkg like dpkg-repack, debsums, reportbug, etc.
Responsibility for its usage and possible breakage of your system
therefore lies in the sysadmin's (your) hands.
.
Please definitely do abstain from reporting any such bugs blaming
localepurge if you break your system by using it. If you don't know
what you are doing and can't handle any resulting breakage on your own
then please simply don't use this package.

L cdrom /dev/hdc

[...]
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)?

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
it87
#----cut here----

Then, run /etc/init.d/modutils


To make the sensors modules behave correctly, add these lines to
/etc/modutils/local and run update-modules:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
options it87 ignore=-1,0x290
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

--- linux-2.6.0-test9/drivers/input/mouse/logips2pp.c 2003-10-26
03:43:59.000000000 +0900
+++ linux-2.6.0-test9-debug/drivers/input/mouse/logips2pp.c 2003-10-31
13:48:38.000000000 +0900
@@ -154,10 +154,18 @@
psmouse->vendor = "Logitech";
psmouse->model = ((param[0] >> 4) & 0x07) | ((param[0] << 3) & 0x78);

- if (param[1] < 3)
- clear_bit(BTN_MIDDLE, psmouse->dev.keybit);
- if (param[1] < 2)
+ /*
+ * We clear middle BTN_MIDDLE only when the mouse says
+ * there's only one button on it(param[1] < 2).
+ * This is a workaround for some buggy mice which report
+ * they have only 2 buttons though they have wheel-button
+ * which also works as middle button.
+ * 10/31/2003 - junji.kanemaru@xxxxxxxxxxxxxxxxx
+ */
+ if (param[1] < 2) {
clear_bit(BTN_RIGHT, psmouse->dev.keybit);
+ clear_bit(BTN_MIDDLE, psmouse->dev.keybit);
+ }

psmouse->type = PSMOUSE_PS2;

sargeX:/home/jani# cat /dev/input/mice





Allocate 3rd-level pagetables from highmem
CONFIG_HIGHPTE:
The VM uses one page table entry for each page of physical memory.
For systems with a lot of RAM, this can be wasteful of precious
low memory. Setting this option will put user-space page table
entries in high memory.

Power Management Timer Support
CONFIG_X86_PM_TIMER:
The Power Management Timer is available on all ACPI-capable,
in most cases even if ACPI is unusable or blacklisted.
This timing source is not affected by powermanagement features
like aggressive processor idling, throttling, frequency and/or
voltage scaling, unlike the commonly used Time Stamp Counter
(TSC) timing source.

So, if you see messages like 'Losing too many ticks!' in the
kernel logs, and/or you are using this on a notebook which
does not yet have an HPET, you should say "Y" here.

Sleep States (EXPERIMENTAL)
CONFIG_ACPI_SLEEP:
This option adds support for ACPI suspend states.
With this option, you will be able to put the system "to sleep".
Sleep states are low power states for the system and devices. All
of the system operating state is saved to either memory or disk
(depending on the state), to allow the system to resume operation
quickly at your request.

Although this option sounds really nifty, barely any of the device
drivers have been converted to the new driver model and hence few
have proper power management support.

This option is not recommended for anyone except those doing driver
power management development.

USB HIDBP Keyboard (simple Boot) support
CONFIG_USB_KBD:
Say Y here only if you are absolutely sure that you don't want
to use the generic HID driver for your USB keyboard and prefer
to use the keyboard in its limited Boot Protocol mode instead.
This is almost certainly not what you want. This is mostly
useful for embedded applications or simple keyboards.
To compile this driver as a module, choose M here: the
module will be called usbkbd.

If even remotely unsure, say N.

Hangcheck timer
CONFIG_HANGCHECK_TIMER:

The hangcheck-timer module detects when the system has gone
out to lunch past a certain margin. It can reboot the system
or merely print a warning.

Magic SysRq key
CONFIG_MAGIC_SYSRQ:
If you say Y here, you will have some control over the system even
if the system crashes for example during kernel debugging (e.g., you
will be able to flush the buffer cache to disk, reboot the system
immediately or dump some status information). This is accomplished
by pressing various keys while holding SysRq (Alt+PrintScreen). It
also works on a serial console (on PC hardware at least), if you
send a BREAK and then within 5 seconds a command keypress. The
keys are documented in . Don't say Y
unless you really know what this hack does.

usb 1-1: USB disconnect, address 2
usb 1-1: new full speed USB device using address 3

$ cd /tmp
$ wget http://files.xvid.org/downloads/xvidcore-1.0.0-rc4.tar.bz2
$ tar xvjf xvidcore-1.0.0-rc4.tar.bz2
$ cd xvidcore-1.0.0-rc4
$ dpkg-buildpackage -rfakeroot
$ cd ..
$ su
# dpkg -i libxvidcore4_1.0-0cvs_i386.deb
# dpkg -i libxvidcore4-dev_1.0-0cvs_i386.deb

<style TYPE="text/css">
<!--

div#esim-040513-1 {
  white-space: pre-wrap;
  color: white;
}

-->
<div id="esim-040513-1">
foo bar foo bar foo bar foo
tähän asti sisentämätöntä tekstiä
   tämä rivi on sisennetty kolmella välillä
tämä rivi on taas sisentämätön
</div>

Setting up python2.3 (2.3.3-7) ...
Compiling python modules in /usr/lib/python2.3 ...
Compiling optimized python modules in /usr/lib/python2.3 ...
/var/lib/dpkg/info/python2.3.postinst: line 49: 3554 Muistialueen ylitys \
/usr/bin/python2.3 -O /usr/lib/python2.3/compileall.py -q $i
dpkg: error processing python2.3 (--configure):
subprocess post-installation script returned error exit status 139

jani@sargeX:~$ free
total used free shared buffers cached
Mem: 515644 509200 6444 0 15012 157536
-/+ buffers/cache: 336652 178992
Swap: 1991976 0 1991976

invalid operand: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[] Not tainted
EFLAGS: 00013202 (2.6.5)
EIP is at radeon_cp_idle+0x49/0xa0 [radeon]
eax: dc8ca440 ebx: dec5e800 ecx: e0c34179 edx: e0c43a70
esi: dfeca740 edi: 00000044 ebp: dd2fd080 esp: dd30df68
ds: 007b es: 007b ss: 0068
Process XFree86 (pid: 2163, threadinfo=dd30c000 task=dd3353e0)
Stack: e0c2e81d dc8ca440 dd2fd080 00006444 00000000 00000001 00001000 c7bed0e0
dd2fd080 00006444 ffffffe7 dd30c000 c01676cf dc8ca440 dd2fd080 00006444
00000000 00001000 c7bed0e0 00000006 0862ed18 08651bc8 c0109377 00000006
Call Trace:
[] radeon_ioctl+0xcd/0x150 [radeon]
[] sys_ioctl+0xef/0x2a0
[] syscall_call+0x7/0xb

Code: c5 c3 e0 c7 04 24 60 df c3 e0 e8 88 d3 4e df 8b 7c 24 14 8b

sargeX:/home/jani# apt-get --purge remove gtkam gphoto2
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
gphoto2* gtkam*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 1163kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 110872 files and directories currently installed.)
Removing gtkam ...
Purging configuration files for gtkam ...
Removing gphoto2 ...
sargeX:/home/jani#

sargeX:/home/jani# dpkg -i opera_7.50-20040422.5-shared-qt_en_i386.deb
Selecting previously deselected package opera.
(Reading database ... 110655 files and directories currently installed.)
Unpacking opera (from opera_7.50-20040422.5-shared-qt_en_i386.deb) ...
Setting up opera (7.50-20040422.5) ...
sargeX:/home/jani#

sargeX:/home/jani# sed -n 28,60p /var/log/syslog
May 11 09:54:00 sargeX syslogd 1.4.1#10: restart.
May 11 09:54:00 sargeX kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
May 11 09:54:00 sargeX kernel: Inspecting /boot/System.map-2.6.5
May 11 09:54:00 sargeX kernel: Loaded 23255 symbols from /boot/System.map-2.6.5.
May 11 09:54:00 sargeX kernel: Symbols match kernel version 2.6.5.
May 11 09:54:00 sargeX kernel: No module symbols loaded - kernel modules not enabled.
May 11 09:54:00 sargeX kernel: 8259A ... failed.
May 11 09:54:00 sargeX kernel: ...trying to set up timer as Virtual Wire IRQ... failed.
May 11 09:54:00 sargeX kernel: ...trying to set up timer as ExtINT IRQ... works.
May 11 09:54:00 sargeX kernel: Using local APIC timer interrupts.
May 11 09:54:00 sargeX kernel: calibrating APIC timer ...
May 11 09:54:00 sargeX kernel: ..... CPU clock speed is 1912.0941 MHz.
May 11 09:54:00 sargeX kernel: ..... host bus clock speed is 332.0685 MHz.
May 11 09:54:00 sargeX kernel: NET: Registered protocol family 16
May 11 09:54:00 sargeX kernel: EISA bus registered
May 11 09:54:00 sargeX kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb790, last bus=3
May 11 09:54:00 sargeX kernel: PCI: Using configuration type 1
May 11 09:54:00 sargeX kernel: mtrr: v2.0 (20020519)
May 11 09:54:00 sargeX kernel: ACPI: Subsystem revision 20040326
May 11 09:54:00 sargeX kernel: ACPI: Interpreter enabled
May 11 09:54:00 sargeX kernel: ACPI: Using IOAPIC for interrupt routing
May 11 09:54:00 sargeX kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
May 11 09:54:00 sargeX kernel: PCI: Probing PCI hardware (bus 00)
May 11 09:54:00 sargeX kernel: PCI: nForce2 C1 Halt Disconnect fixup
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15)

sed -n 36024,36191p patch-2.6.6

diff -Nru a/arch/i386/pci/fixup.c b/arch/i386/pci/fixup.c

--- a/arch/i386/pci/fixup.c	Sun May  9 19:33:46 2004

+++ b/arch/i386/pci/fixup.c	Sun May  9 19:33:46 2004

@@ -187,6 +187,42 @@

 		dev->transparent = 1;

 }

 

+/*

+ * Fixup for C1 Halt Disconnect problem on nForce2 systems.

+ *

+ * From information provided by "Allen Martin" :

+ *

+ * A hang is caused when the CPU generates a very fast CONNECT/HALT cycle

+ * sequence.  Workaround is to set the SYSTEM_IDLE_TIMEOUT to 80 ns.

+ * This allows the state-machine and timer to return to a proper state within

+ * 80 ns of the CONNECT and probe appearing together.  Since the CPU will not

+ * issue another HALT within 80 ns of the initial HALT, the failure condition

+ * is avoided.

+ */

+static void __init pci_fixup_nforce2(struct pci_dev *dev)

+{

+	u32 val, fixed_val;

+	u8 rev;

+

+	pci_read_config_byte(dev, PCI_REVISION_ID, &rev);

+

+	/*

+	 * Chip  Old value   New value

+	 * C17   0x1F0FFF01  0x1F01FF01

+	 * C18D  0x9F0FFF01  0x9F01FF01

+	 *

+	 * Northbridge chip version may be determined by

+	 * reading the PCI revision ID (0xC1 or greater is C18D).

+	 */

+	fixed_val = rev < 0xC1 ? 0x1F01FF01 : 0x9F01FF01;

+

+	pci_read_config_dword(dev, 0x6c, &val);

+	if (val != fixed_val) {

+		printk(KERN_WARNING "PCI: nForce2 C1 Halt Disconnect fixup\n");

+		pci_write_config_dword(dev, 0x6c, fixed_val);

+	}

+}

+

 struct pci_fixup pcibios_fixups[] = {

 	{

 		.pass		= PCI_FIXUP_HEADER,

@@ -289,6 +325,12 @@

 		.vendor		= PCI_VENDOR_ID_INTEL,

 		.device		= PCI_ANY_ID,

 		.hook		= pci_fixup_transparent_bridge

+	},

+	{

+		.pass		= PCI_FIXUP_HEADER,

+		.vendor		= PCI_VENDOR_ID_NVIDIA,

+		.device		= PCI_DEVICE_ID_NVIDIA_NFORCE2,

+		.hook		= pci_fixup_nforce2

 	},

 	{ .pass = 0 }

 };

jani@sargeX:~$ while [ 0 ] ; do ping -c 3 lkml.org && play /mnt/media2/audio/sounds/human/femeek2.wav -v 0.3 ; done
PING lkml.org (212.79.244.34): 56 data bytes

<B.Zolnierkiewicz@elka.pw.edu.pl>

	[PATCH] fixup for C1 Halt Disconnect problem on nForce2 chipsets

	

	Based on information provided by "Allen Martin" :

	

	A hang is caused when the CPU generates a very fast CONNECT/HALT cycle

	sequence.  Workaround is to set the SYSTEM_IDLE_TIMEOUT to 80 ns.

	This allows the state-machine and timer to return to a proper state within

	80 ns of the CONNECT and probe appearing together.  Since the CPU will not

	issue another HALT within 80 ns of the initial HALT, the failure condition

	is avoided.

sargeX:/dev# ls -l cdrom*
lrwxr-xr-x 1 root cdrom 11 2004-03-22 10:20 cdrom -> /dev/cdrom0
lrwxr-xr-x 1 root cdrom 10 2004-05-10 17:46 cdrom0 -> cdrom0.ide
lrwxr-xr-x 1 root cdrom 3 2004-05-10 17:45 cdrom0.ide -> hdc
lrwxr-xr-x 1 root cdrom 9 2004-03-22 10:20 cdrom0.scsi -> /dev/scd0

/dev/sda1    /mnt/Sony    vfat    user,gid=1001     0    

jani@sargeX:~$ free

	total	used	free	shared	buffers	cached
Mem:	515640	508412	7228	0	11520	158532
-/+ buffers/cache:		338360	177280
Swap:	1991976	600	1991376

jani@sargeX:~$ uname -a
Linux sargeX 2.6.5-ju-040505 #1 Wed May 5 20:11:35 EEST 2004 i686 GNU/Linux