Thursday, January 31, 2008

New Update for -Current

Pat has just released an update for -Current and also small reports from KDE Release Event where some Slackware contributors came in and have a nice reunion. There's a new package on this batch of updates which is libmowgli-0.6.0-i486-1.tgz. This package is needed for audacious. It also been clarified that Slackware 12.1 will NOT contain KDE 4, but KDE 3.5.9 instead. The next Slackware release after that (12.2 or probably 13.0) will be targeting on KDE 4.1 which should be released on June 2008. Without further ado, here's the latest -Current changelog:
Wed Jan 30 19:07:35 CST 2008
d/ruby-1.8.6_p111-i486-2.tgz: Moved some comments out of the ./configure part of the build script to fix a couple of missed options.
Thanks to Stuart Winter.

kde/amarok-1.4.8-i486-1.tgz: Upgraded to amarok-1.4.8.

l/atk-1.21.5-i486-1.tgz: Upgraded to atk-1.21.5.

l/gtk+2-2.12.7-i486-1.tgz: Upgraded to gtk+-2.12.7.

l/libmowgli-0.6.0-i486-1.tgz: Added libmowgli-0.6.0, which is needed by Audacious.

l/libmtp-0.2.5-i486-1.tgz: Upgraded to libmtp-0.2.5.

l/libgpod-0.6.0-i486-1.tgz: Upgraded to libgpod-0.6.0 (major version bump).

l/libxml2-2.6.31-i486-1.tgz: Upgraded to libxml2-2.6.31.

l/pango-1.19.3-i486-1.tgz: Upgraded to pango-1.19.3.

xap/audacious-1.4.5-i486-1.tgz: Upgraded to audacious-1.4.5.

xap/audacious-plugins-1.4.4-i486-1.tgz: Upgraded to audacious-plugins-1.4.4-i486-1.tgz.

xap/xine-lib-1.1.10-i686-1.tgz: Upgraded to xine-lib-1.1.10.

extra/slackpkg/slackpkg-2.70-noarch-1.tgz: Upgraded to slackpkg-2.70.
Thanks to Piter Punk.

Great thanks are also due to the KDE team, not only for their tremendous accomplishments over the years, but for the gracious reception they gave to the members of the Slackware team who traveled to the release event. What a wonderful group of people! We had a great time there, learned a lot, and will be applying that knowledge and our new contacts within KDE to provide the best possible KDE experience for Slackware users. The next Slackware release will contain KDE 3.5.9, but we're targeting KDE 4.1.x for the one after that. The application end of things doesn't quite fully cover KDE3's functionality yet, but by then it will. As I'm sure most of you know, Robby has put up test packages of the initial KDE 4.0 release which I've tested and found to be consistent with what to expect from a developer's preview.
The look of the new desktop is stunning, and the use of SVG and hardware acceleration gives (IMHO) even something like MacOS a run for its money in terms of appearance and user-friendliness. We look forward with great anticipation to merging KDE4 when it is mature enough (and it's getting there fast), and then watching it just get better and better.
Once again, _huge_ thanks to our KDE friends! Stop by here any time. :-)

End of Poll

Today is the last day of the poll "What is Your Favorite Package Management?". There are already 100 voters and i'm quite happy with the results. I will wait until midnight before i collect the results and publish them on this blog.

I'm preparing for the next questions for February's poll so stay tune on this blog big grin

Tuesday, January 29, 2008

KTorrent 2.2.5

KTorrent team has released two version for KTorrent, one for 2.2.x series and the other for the next KDE 4 release. Some improvements have been introduced in the new RC1 release, while in the stable series, only bug fixes that are applied. Since Slackware-Current hasn't been updated for some time, you can get it by using Pat's Slackbuild and use it to compile it by yourself.

Saturday, January 26, 2008

Wine Support For Photoshop

By the release of Wine 0.9.54, it's support for Adobe Photoshop has been increased once more. Now, it has support of Adobe Photoshop CS/CS2 (but not for ImageReady and CS3). Read the wiki entry about Adobe Photoshop for more detailed information on how to install Adobe Photoshop on Linux using Wine.

KDE 4 Everywhere

Right now, most blog about Linux will probably talk about KDE 4 (if they use KDE as their window manager). It's one of the big release for Open Source project on this early year. Even one of my student have tried to install KDE 4 on his new Slackware 12.0 installation (he choose not to install KDE at installation so he can have clean KDE installation starting 4.0). I have seen KDE 4 and it is amazing. Almost every parts changed. For example, you will not have a tall menu list, but instead, you will get a left/right menu ordering. Some default application is placed on the desktop (i thought it was an image, but actually it was a shortcut blushing)

I tried to convince myself that KDE 4 is still not ready for every users (including me). Many application is still not ready (for example K3B and Amarok which i often used). I tried to start the battery monitor, but i couldn't find it in the KDE System Settings (it was previously called KDE Control Center). There was an icon saying about power control, but no laptop battery configuration. I think it still need external application to do that.

Probably i will just wait for the updates in the upcoming months. KDE is planning to release minor updates every months until KDE 4.1 is released, which should be in June 2008. I hope when it comes to KDE 4.1, most spot that were known as bugs have been fixed thus it can be as stable as KDE 3.5.x

Friday, January 25, 2008

Start Upgrading

Now i have three machine that uses Slackware and since 2.6.24 has been released, it's time to upgrade all of them. So far, i have successfully upgraded one machine and one is on the way (it's probably finished by now, but i will find it soon after i came back home). The first computer is my computer at work. Since i can work remotely, i connect to it via SSH and do kernel compilation. So when i arrived at office, all i need is reboot the system and test it. So far no big problem appears.

I will let it have two kernels, since 2.6.24 has big changes, mostly due to unification of two architecture. After it has been proven stable for few days, i will delete the old kernel to put some space on my disk.

I think Pat will also upgrade to 2.6.24 soon enough after finishing his TODO list

Here's my uname -a results:
Linux dosen 2.6.24 #1 Fri Jan 25 07:20:22 WIT 2008 i686 Intel(R) Celeron(R) CPU 2.66GHz GenuineIntel GNU/Linux

At Last: 2.6.24

Linus has finally made up his mind and release kernel 2.6.24 (i hope he's satisfied with this release and so does other users who have waited for a long time for this release). So far, it's the longest kernel release, mostly since we have holiday break that took some time. But the process is now completed and it has been released for public.

This also means developers gets their entrance for new code inclusion in merge window that soon be included in 2.6.25.

Tuesday, January 22, 2008

SlackBasics Translations Started

Ozzie has put the SlackBasics source into CVS and now the SlackBasics translation project can be started. I already translate the index page so that next page can be synchronized with the index page. If you would like to help, then please ask Ozzie on how to get the account for writing to CVS Server.

Monday, January 21, 2008

Slackware Basic

For some time, SlackBook has been an official guide for Slackware users. No matter you are newbie or expert, most Slackware users will refer to SlackBook when they were asked about something basic. Unfortunately, SlackBook is no longer updated and the Slackware version being used is about 9.1 if i'm not mistaken. Slackware has evolved so much since Slackware 9.1, so there's a need for replacement.

It's a long wait until finally Slackware Basic comes up with a revised article that was previously made for Slackware 10.2 and now it has been updated for Slackware 12.0. I hope it can cover much areas that are new in Slackware 12.0 and further development of Slackware.

I will ask for translations in Indonesian language for Slackware-ID community. I hope it will get a good response.

Update (22 Jan 2008 : 21:08): I got a reply today from the author, Daniel de Kok. Here's my request and his answer:
-- My Request --
I (representing Indonesian Slackware community) would like asking for your permission to translate SlackBasic documentation that you have made into Indonesian Language. Is it OK with you?

Last year, we have finished translating the SlackBook and results are very good. People in Indonesia can read them while they are using Slackware, but as you know, it's kindda out-dated. I saw that SlackBasic is based on 12.0, so i guess it's more up to date than SlackBook

-- Daniel's Answer --
Thanks for your interest in SlackBasics! It would be great if you can translate the book in Indonesian, it's ok with me as long as the license (as listed on the table of contents page) is kept in translated versions.

Great work, thanks for contributing to the Slackware community in such a major way!

With kind regards,
Daniel de Kok

Saturday, January 19, 2008

KDE 4 Release Schedule

Even though KDE team has just released KDE 4.0 for public use, it doesn't mean that they are satisfied with it's results. Most people agreed that KDE 4.0 is more suitable for developers to test their application whether it works or not with the new infrastructure of KDE 4. It also gives developer time to adopt or port their application to work with KDE 4 libraries which has changed quite a lot.

From Phoronix, i got this KDE 4.1 release schedule:
January - KDE 4.0.1
February - KDE 4.0.2
March - KDE 4.0.3
April - KDE 4.0.4
May - KDE 4.0.5
June - KDE 4.0.6
July - KDE 4.1.0
August - KDE 4.1.1

In my opinion, Slackware will try to include the KDE 4 package after it has released their first maintenance update (the bold one) since most of the problems found during public testing will be found and (hopefully) has been fixed in their regular maintenance version of 4.0.x version that will be released each month. It's too risky to include them now (probably on /testing) since it requires a lot of changes to be made before you can enjoy them.

For the -Stable version of KDE, next month is the month where KDE 3.5.9 will be released, so i guess we should stick with this version for now (unless you want to start hacking your system to use KDE 4)

Thursday, January 17, 2008

KDE 4 on Slackware

KDE 4 has been released for several days and many big distro have started to put their efforts to release KDE 4 for their products (in several formats of course, depending the format they used).

Meanwhile for Slackware, KDE is still considered unstable for now and *MAY* not be included in the next Slackware release, which will be 12.1 (no exact date though). I think it will be included in the next major release (13.0 my guess).

BUT..... if you have a testing machine, and very curious about how KDE 4 looks like, you can grab KDE 4 packages from Robby Workman's site

PLEASE NOTE: This is a big efforts, as you will have to remove all kde apps and every package related to KDE, mostly QT and the compile all of KDE apps and the dependencies (there are a lot of them and you must compile them in order to work perfect) before you can enjoy them (Robby has managed to provide the tgz format though, if you are too lazy to compile KDE, but you have to use machine running -CURRENT for this). PLEASE READ the _README file first. Take your own risk by using this package as it has been stated:
This contains new and *very* experimental build scripts for KDE4. From what I understand, kde-4.0.0 is not intended as a replacement for the stable kde-3.5.x series; rather, this is more of a "preview" release mainly geared for interested users and developers of add-on applications.
Here's the build order for dependencies:
1. boost 2. qt 3. eigen 4. clucene 5. raptor 6. rasqal
7. redland 8. strigi 9. soprano 10. qimageblitz 11. qca
12. qca-$plugins 13. optional/*

I personally would rather to wait for the official package to be released in Slackware.

Read also the discussion on LQ. Robby said that Pat would push some more official packages after he came back from KDE Release Events (That's a good news), but i think it would be in /testing rather than in the main tree of /kde)

Wednesday, January 16, 2008

Y2K38 Bug

In the next three days, every Linux or Unix people will start the thirty years of countdown before the unix timestamps overflows. This bug is called Y2K38 and it affects all unix-like operating system which represent system time as the number of seconds since January 1, 1970. Here's some technical description about it from Wikipedia:
This representation also affects software written for most other operating systems because of the broad deployment of C. On most 32-bit systems, the time_t data type used to store this second count is a signed 32-bit integer. The latest time that can be represented in this format, following the POSIX standard, is 03:14:07 UTC on Tuesday, January 19, 2038. Times beyond this moment will "wrap around" and be represented internally as a negative number, and cause programs to fail, since they will see these times not as being in 2038 but rather in 1901. Erroneous calculations and decisions may therefore result.
If you have used 64 bit system, then you can relax a bit, since 64 bit system have used longer bits to hold the date. I hope before 2038, i already bought a new 64 bit system big grin

Here's some illustration from Wikipedia

Tuesday, January 15, 2008

Another Stable Kernel Released

The -Stable team has managed to release another release before the final 2.6.24, which is 2.6.23.14. It contains a single fix for a problem that could cause a local user to cause file system corruption on some types of filesystems that was spotted by Bill Roman and the workaround was done by Linus. I think it's an important update that should be implemented to those who used 2.6.23.x version.

Sunday, January 13, 2008

Slackware Chat Room Logs

If you joined #Slackware on irc.freenode.org, you will find an active conversations between the members (most of them will be silent until "someone wake them up"). When they woke up, the chat room will be full and sometimes it's not easy to find the answer for you. Luckily, the channel has provided a public log which can be accessed from the founder's website. It's log collected from Slackware's bot guardian, Slackboy.

They are very friendly, unless you start making war on the room big grin
Please note that it's Slackware's room, not SLAX, ZenCafe, ZenWalk, or any other Slackware-derivative Linux distribution. It's a very important note or you will be ignored by the rest of the users.

RF Presenter on Slackware


Few days ago (Friday, 11 January 2008), i bought a new RF remote presenter which i need for presentation at work. I bought this device in Harrisma. There i met my junior on college and we had a chat for a while. He helped me during my search for good product and there were about three products that i examined. Finally i choose the product from Avov, with model number: AVOV PreMio PS-2432. It was quite expensive and during some testing on the store, we had some problems with the device. Later on, we found out that the problem lies on the USB ports. After we changed device to another port, it works just fine. So i decided to bought this device.

Tonight, i was preparing my presentation for tomorrow and i guess it's time to test the device on my laptop. I booted to my Slackware and guess what? The kernel detected the device perfectly and it works instantly, without any further driver installation. Here's the dmesg:

usb 4-1: new low speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
input: Raytac Corporation Wireless USB Device (2.4G) as /class/input/input8
input: USB HID v1.00 Keyboard [Raytac Corporation Wireless USB Device (2.4G)] on usb-0000:00:1d.2-1
input: Raytac Corporation Wireless USB Device (2.4G) as /class/input/input9
input: USB HID v1.00 Mouse [Raytac Corporation Wireless USB Device (2.4G)] on usb-0000:00:1d.2-1


I tried to play some slides for tomorrow's presentation and i can use the device to go to the next/previous slide, run the slide show, quit from the slideshow, show a blank white/black screen, and also point a laser pointer on it. In simple words, IT WORKS!!!

I also get a nice black pouch on the bundle and the receiver can be placed on the back of the device, make it a nice unity device. Everything is so simple and beautiful.

Honestly, i was worried whether the device can work on Linux or not, but now i'm more confident that Linux has matured on device/hardware detection due to the use of kernel 2.6.x and also contributions from developers around the world.

Friday, January 11, 2008

Chrooting User in VSFTPD

For FTP Server, i personally like VSFTPD, since it's very small in size, easy to configure, and it's very secure. You also have two kinds of options for starting the vsftpd daemon, either via inetd or standalone (i would prefer the first one though).

Few days ago, one of my friend asked me a FTP configuration that could prevent users to go up to the root level. I said that VSFTPD should have prevent that, but when i tried to reproduce, it seems that the default configuration didn't enable this option: chroot_local_user=yes. The results? User who have a local account can access the whole system, including getting the /etc/passwd or /etc/shadow password (even though he had to crack it to get access for all system). This is not a good default configuration. So i asked my friend who is working as a sysadmin in my campus. He used proFTPD, but he managed to look the VSFTPD configuration for me, and he found the chroot_local_user option. Here's the description for that option from VSFTPD's Man Page:
chroot_local_user
If set to YES, local users will be (by default) placed in a chroot() jail in their home directory after login. Warning: This option has security implications, especially if the users have upload permission, or shell access. Only enable if you know what you are doing. Note that these security implications are not vsftpd specific. They apply to all FTP daemons which offer to put local users in chroot() jails.

Default: NO
I'm quite confused with the security implication. I thought it would be a good idea to place users on their home directory and not other place. Can somebody give a good explanation on this?

Thursday, January 10, 2008

Slackware Become Slicker

Ever since i upgrade my Slackware box with the latest -Current updates, the icon has become slicker. I thought it was because of the new gtk+-2.12.4 and pango-1.19.2 package. I don't know if py* package does affect the layout of application. GIMP, Liferea, and many other gtk-based application has changed and it's more fancy then before. No wonder people were asking for a change for gtk update in LQ. It's not only fix compilation problem, but also improves look and feel big grin

Wednesday, January 9, 2008

First Update in New Year

Finally, the long awaited update for new year has arrived. It's quite interesting update, since there are some new packages, mostly are Python-related packages, like pycairo, pygobject, pygtk, and pyrex. I believe this packages will fix broken nmapfe after being upgraded last month (you will still need to install sqlite3 package though). Here's the latest -Current changelog:
Tue Jan 8 22:42:01 CST 2008
ap/nano-2.0.7-i486-1.tgz: Upgraded to nano-2.0.7.

d/mercurial-0.9.5-i486-1.tgz: Upgraded to mercurial-0.9.5.

d/ruby-1.8.6_p111-i486-1.tgz: Upgraded ruby-1.8.6 to patchlevel 111.

l/atk-1.20.0-i486-1.tgz: Upgraded to atk-1.20.0.

l/glib2-2.14.5-i486-1.tgz: Upgraded to glib-2.14.5.

l/gtk+2-2.12.4-i486-1.tgz: Upgraded to gtk+-2.12.4.

l/libxml2-2.6.30-i486-1.tgz: Upgraded to libxml2-2.6.30.

l/libxslt-1.1.22-i486-1.tgz: Upgraded to libxslt-1.1.22.

l/pango-1.19.2-i486-1.tgz: Upgraded to pango-1.19.2.

l/pycairo-1.4.12-i486-1.tgz: Added pycairo-1.4.12.
Thanks to Eric Hameleers.

l/pygobject-2.14.1-i486-1.tgz: Added pygobject-2.14.1.
Thanks to Erik Hanson and SBo (slackbuilds.org).

l/pygtk-2.12.1-i486-1.tgz: Added pygtk-2.12.1.
Thanks to Erik Hanson, Andrew Brouwers, and SBo.

l/pyrex-0.9.6.4-i486-1.tgz: Added Pyrex-0.9.6.4.
Thanks to David Somero.

x/dejavu-fonts-ttf-2.22-noarch-1.tgz: **NOTE PACKAGE NAME CHANGE**
Upgraded to version 2.22.

x/liberation-fonts-ttf-0.2-noarch-3.tgz: Added liberation-fonts-ttf-0.2-3.

x/xf86-video-ati-6.7.197-i486-1.tgz: Upgraded to xf86-video-ati-6.7.197.

x/xf86-video-radeonhd-1.1.0-i486-1.tgz: Upgraded to xf86-video-radeonhd-1.1.0.

xap/seamonkey-1.1.7-i486-2.tgz: Use the system cairo to avoid a compile error.
Thanks to Eric Hameleers for helping to figure this out.
Patched a Makefile.in to avoid another compile error with the new GTK+.
Thanks to the BLFS contributors for posting the solution to this.

Tuesday, January 8, 2008

Slackware For Work

For the last two days, i have been busy working on Slackware installation on my new office (UKDW). I finally got a computer and i decided to use only Slackware Linux for the operating system. It's adequate for my job and i can do lots of thing by using Linux, which i couldn't do it if i use Windows. Besides, i'm tired of having virus problem on Windows platform. The computer has quite a plenty of space (80GB), but with only small RAM on it (only 256 MB). I think Slackware is perfect for this specs.

Yesterday, i was quite frustrated, since i always get a kernel panic after i compile a new kernel. So here's the chronology. First, i installed Slackware as usual, using Slackware 12.0 CDs and after that, i upgraded to -Current directly by using the default Slackware kernel (2.6.21.5-SMP). It went smoothly, after i tried to compile the new kernel (2.6.23.12) and reboot. I got a kernel panic, saying that i must add "root=" options, because the system couldn't find my root partition. Strange confused since my installation was fine and the root partition was there at /dev/sda1.

So i booted to the default kernel and i looked at dmesg (one of the best way to debug things). The harddisk was detected as hda, but suddenly it changed to sda. That's why the new system couldn't detect this and the kernel panic happened (in time, it turns to be user panic big grin). Some people said to me that it could be caused by udev, and i think it's very possible.

So i tried several modifications on the kernel and recompile the kernels and also modifying /etc/lilo.conf but everything failed. I was quite frustrated yesterday, since it was supposed to be simple. At the end, i left the office and the problem still persists with some hopes that today i will have some inspiration on how to solve the problem. At night, i remote my computer from my house and i did some kernel compilation using my .config that i used at my desktop computer. It's just a time saving, so i only have to test the configuration tomorrow.

This morning i went to the office earlier so that i could try the new kernel results, but evidently, it failed also angry. So i re-checked the log system and i even reinstalled the Slackware from scratch in order to have a clean system. This time, i didn't upgrade to -Current directly, but i started with upgrading to 2.6.23.12 first. The results? The same as before... kernel panic!!

So i was thinking, What if i change the fstab and lilo.conf so that it would point to hda instead of sda?

I tried to change the lilo.conf first, but it also failed, since the system couldn't find any hda (if i use the default kernel, it will only find sda). Finally, i took the rough way. I boot using CD 1 and mount the system and chroot to the partition. I can change the fstab and lilo.conf directly and i tried the new configuration. Well... IT WORKS!!!!! The system loads normally and everything is back to normal (the disk is now identified as hda again).

After confirming that my installation was fine, i started to upgrade to -Current (as usual) and right now, i'm installing packages that i need to work remotely via SSH. It's only in console, but i can see the results tomorrow big grin

Now i can use Slackware for Work and i believe that Slackware is mature enough to be used as primary operating system, even for desktop users.

Saturday, January 5, 2008

Adding Printer To libinklevel

You might already know that there are libinklevel and ink that was developed by Markus Heinz that could help you detecting your ink level status for your printer. Too bad, the supported printer is limited currently, but you can make your printer supported by contacting the developer (Markus Heinz) and provide him with the information that he might need. On my cause, he asked about the ink cartridges type, how many cartridges can be inserted at one time, which color are in the cartridge, and also debugging output from libinklevel and ink application.

The debugging output can be done by:
1. Get libinklevel (0.72 or newer)
2. Extract them at some place
3. Open inklevel.h. Change line 12 into #define DEBUG 1
4. Compile and install libinklevel with make and make install (alternatively, you can use SlackBuild script to convert it to tgz).
5. Get ink, and compile it with the same command (make and make install)
6. Run the ink to produce the debugging information with ink -p usb > debug.txt 2>&1
7. Send this information to Markus and he will try to add your printer information on the next release of libinklevel and also ink (hopefully)

On my printer, it resulted in this outout:
ink v0.4.1 © 2007 Markus Heinz

Printer reported size 130, real size is 130
0: MFG:Canon
1: CMD:BJL,HAPS,BSCCe,PLI
2: MDL:iP1800 series
3: CLS:PRINTER
4: DES:Canon iP1800 series
5: VER:1.11
6: STA:10
7: CHD:BK,CL
8: HRI:ASI
9: MSI:E3
10: Aü·7¿
11:
12:
13:
14:
The "MFG:" tag has number 0
The "MDL:" tag has number 2
No "S:" tag found
No "VSTATUS:" tag found
Device file: /dev/usb/lp0
Command:
\x1b[K<\x00\x00\x1e\x00:SSR=BST,SFA,CHD,CIL,CIR,HRI,DBS,DWS,DOC,DSC,DJS,CTK,HCF; Command Response: \x00wBST:00;CHD:BK,CL;HRI:ASI;CIL:ON;CTK:BK,SET,/,CL,SET;CIR:BK=100,CL=070;HCF:NO;DJS:NO;DBS:NO;DOC:4,00,NO;DWS:NO;DSC:NO; Printer not supported. Could not get ink level.

Update (23:44): After giving my debugging information, Markus Heinz sent me updated libinklevel (called 0.7.3rc5) and i tried compiling it and here are the updated results
ink v0.4.1 © 2007 Markus Heinz

Printer reported size 130, real size is 130
0: MFG:Canon
1: CMD:BJL,HAPS,BSCCe,PLI
2: MDL:iP1800 series
3: CLS:PRINTER
4: DES:Canon iP1800 series
5: VER:1.11
6: STA:10
7: CHD:BK,CL
8: HRI:ASI
9: MSI:E3
10: AÈû·HÒ¿
11:
12:
13:
14:
The "MFG:" tag has number 0
The "MDL:" tag has number 2
No "S:" tag found
No "VSTATUS:" tag found
Device file: /dev/usb/lp0
Command:
\x1b[K<\x00\x00\x1e\x00:SSR=BST,SFA,CHD,CIL,CIR,HRI,DBS,DWS,DOC,DSC,DJS,CTK,HCF; Command Response: \x00wBST:00;CHD:BK,CL;HRI:ASI;CIL:ON;CTK:BK,SET,/,CL,SET;CIR:BK=100,CL=070;HCF:NO;DJS:NO;DBS:NO;DOC:4,00,NO;DWS:NO;DSC:NO;
1 colors found
Ink levels :
Level 1 = 100
Canon iP1800 series

Black: 100%

Now it can find the black cartridge, but we are missing the color one (actually, if you look on the bold string above, you will notice that's the information that were used to gather information about the ink level. It said 100% on black and 70% on color). It will be updated again soon again big grin

Update (06/01/2008: 00:08): libinklevel-0.7.3rc6 works like charm and here's the updated results:
ink v0.4.1 © 2007 Markus Heinz

Printer reported size 130, real size is 130
0: MFG:Canon
1: CMD:BJL,HAPS,BSCCe,PLI
2: MDL:iP1800 series
3: CLS:PRINTER
4: DES:Canon iP1800 series
5: VER:1.11
6: STA:10
7: CHD:BK,CL
8: HRI:ASI
9: MSI:E3
10: AHô·(Ñ¿
11:
12:
13:
14:
The "MFG:" tag has number 0
The "MDL:" tag has number 2
No "S:" tag found
No "VSTATUS:" tag found
Device file: /dev/usb/lp0
Command:
\x1b[K<\x00\x00\x1e\x00:SSR=BST,SFA,CHD,CIL,CIR,HRI,DBS,DWS,DOC,DSC,DJS,CTK,HCF;
Command Response:
\x00wBST:00;CHD:BK,CL;HRI:ASI;CIL:ON;CTK:BK,SET,/,CL,SET;CIR:BK=100,CL=070;HCF:NO;DJS:NO;DBS:NO;DOC:4,00,NO;DWS:NO;DSC:NO;
2 colors found
Ink levels :
Level 1 = 100
Level 2 = 70
Canon iP1800 series

Black: 100%
Color: 70%

Markus also told me that Canon printers report their ink levels not in a continuous fashion, like 70%, 69%, 68% etc but in greater steps like 100%, 70%, 50 % etc. So don't be surprised if your ink level dropped so quick (for example from 70% to 50%), because they don't dropped gradually, but they will be updated when it has reached some points.

I think i have to sleep for now.... sleepy

Thursday, January 3, 2008

More Options For Pixma 1800 Series

I found this page for more options on Pixma 1800 series (mine is 1880 which uses the same driver). By adding and changing some options on /usr/share/cups/model/canonip1800.ppd, you can have more options that you can get if you don't modify the file. By the way, here's what i add on the file:

*OpenUI *CNQuality/Quality: PickOne
*DefaultCNQuality: 5
*CNQuality 2/High: "2"
*CNQuality 3/Normal: "3"
*CNQuality 4/Standard: "4"
*CNQuality 5/Economy: "5"
*CloseUI: *CNQuality


Adding this option will add Quality dialog which can be used to set your printing quality (in Windows, you will find this as Best, Normal, and Fast Draft). I set the default to Economy, so my ink will not be wasted too much for something that doesn't need to be printed at best quality.

Please note that you must remove your printer instance and re-add your printer to the system via CUPS's web administration interface before you can get this options.

Ink Detection

I was looking my Liferea application when i found this interesting news. I thought it was impossible to have ink level detection on Linux, but it seems that it was possible to do that, since there are two applications that help user to know the status of their printer's ink. MTink and libinklevel are the applications that you need. The first application only works for Epson, but the second one works for most vendor.

I tried to install linkinklevel from SlackBuild which works perfectly, but it's only a library. I will need a front end that utilize this library. The same developer developed Ink, but this is what i got so far:

root@desktop:/home/willysr/ink# ink -p usb
ink v0.4.1 © 2007 Markus Heinz

Printer not supported.
Could not get ink level


Since it relies on libinklevel, the printer supported also depends on libinklevel, which is shown on their website and it seems that my printer (Canon Pixma 1880) is not yet detected. Perhaps the developer is willing to add this printer support in the future big grin

Tuesday, January 1, 2008

First Update in New Year

A first update in the new year has come up, which is a new package for glibc-zoneinfo for the latest timezone data for all -Current and -Stable branch of Slackware Linux. Here's the changelog:
Mon Dec 31 18:44:01 CST 2007
a/glibc-zoneinfo-2.7-noarch-5.tgz: Some deja vu. ;-)
Upgraded to tzdata2007k. A new year should be started with the latest timezone data, so here it is.
Happy holidays, and a happy new year to all! :-)

A New Poll For New Year

I have created a new poll for the first day of new year. This time, the questions is "What is Your Favorite Package Management?" We have Pkgtool, Slackpkg, Swaret, Slapt-Get, SlackMan, and GetPKG for the options. If you are wondering why rpm, urpmi, apt-get and emerge are not included, then you probably read the title of this blog big grin

Start picking up. You have one month to vote for this one. It will end in the end of this month.

End of Year Poll Results

Well, it's new year and the time for the poll has ended. Here are the results from approximately 102 voters about the most problematic hardware:
  • Video Card 25 (24%)
  • Sound Card 14 (13%)
  • Internal Modem 19 (18%)
  • Removeable Devices 6 (5%)
  • Web Camera 21 (20%)
  • Digital Camera 6 (5%)
  • Bluetooth 10 (9%)
  • Printer 23 (22%)
  • Scanner 13 (12%)
  • WiFI 33 (32%)
It seems that WiFI is the most problematic for most people, even though it's becoming easier these days, as most of the drivers are already included in the kernel, for example Centrino series (IPW2100, IPW2200 and some part of IPW3945) and Broadcom series (through bcm43xx drivers). Some modules does need to be installed separately, for example Atheros through MadWifi and some other will require ndiswrapper and Windows' driver in order to make it work.

We are hoping for a better driver support for Linux in the future (starting on this year), so hopefully, we can have a nice and running operating system out of the installation process. Personally, i'd like quite some challenge before i can get my perfect system, but for some people, minimum configuration is likely what they wanted.

Stay tune for the next poll that will arrive shortly...

Happy New Year 2008

Even though this blog is reserved for Slackware news only, i can't deny that new year is one big events for everyone, so in this occasion, i wanted to say Happy New Year 2008. It's been a great year in 2007 and we are hoping for more good news in 2008.