On Tue, 24 Apr 2007 15:11:19 +0530 "Anil Kalasa" wrote:

Either that does work, I have found the solution, need to install lshw.rpm, which gives the exact hardware detials.

I see. though too late, I had forgotten hwinfo. IIRC, this is installed for SUSE by default. # hwinfo --cpu # hwinfo --help # man hwinfo Thanks, eshsf

On 4/24/07, eshsf wrote:

...

Hello,

On Tue, 24 Apr 2007 10:43:12 +0530 "Anil Kalasa" wrote:

...

Hi,

I need an urgent help, how to check weather the processor is 32 bit or 64bit, not the OS.

This is for SUSE linux.

How about this？

uname -m man uname

Thanks, eshsf

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 16 June 2007 19:29, Clark Sann wrote:

Anyone have any idea how I can get a 100 MB Iomega parallel port drive to work. I've connected it, have a zip drive in the drive, and rebooted. AFAIK, the system did not recognize the drive. I've spent an hour googling and am afraid I will have to recompile the kernel to add support for this think. Heck with that! I bet openSuse has an easier way. I've also browsed around Yast but couldn't find anything there. Finally, I installed 2 programs....gtkzip and ziptool. Neither work.

Thanks for your help!

Clark

Hi Clark, Please post your question as a new message to opensuse mail list. Changing subject doesn't remove referrals that make message threaded, so you basically hijacked the thread which is not very popular. BTW, gtkzip and ziptool are file compression tools that will not make Iomega ZIP drive running. Until you repost message I'll see how to connect parallel port ZIP drive. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, On Sat, 16 Jun 2007 19:29:18 -0500 Clark Sann <...> wrote:

Anyone have any idea how I can get a 100 MB Iomega parallel port drive to work. I've connected it, have a zip drive in the drive, and rebooted. AFAIK, the system did not recognize the drive. I've spent an hour googling and am afraid I will have to recompile the kernel to add support for this think. Heck with that! I bet openSuse has an easier way. I've also browsed around Yast but couldn't find anything there. Finally, I installed 2 programs....gtkzip and ziptool. Neither work.

Thanks for your help!

Clark

I'm sorry, can't recall the details how I exactly installed years ago my parallel Iomega 100Mb drive on a laptop running SUSE Linux 9.1! Maybe two info helps you, 1. needed the ppa module loaded, 2. the device can be mounted now e.g. via fstab /dev/sdaX /media/zippo vfat noauto,user,exec,sync 0 0 sdaX could be easily sda4, if originally formatted media... Regards, pelibali -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 17 June 2007 05:24, Carlos E. R. wrote:

The Saturday 2007-06-16 at 19:29 -0500, Clark Sann wrote:

...

Anyone have any idea how I can get a 100 MB Iomega parallel port drive to work. I've connected it, have a zip drive in the drive, and rebooted. AFAIK, the system did not recognize the drive. I've spent an hour googling and am afraid I will have to recompile the kernel to add support for this think. Heck with that! I bet openSuse has an easier way. I've also browsed around Yast but couldn't find anything there. Finally, I installed 2 programs....gtkzip and ziptool. Neither work.

First, you hijacked the tread: «Subject: [opensuse] How to check processor is 32 bit or 64 bit ? in suse OS?»

About your question, it will not be autodetected. I haven't tried recently (ie, with 10.2), but basically you need to manually load the corresponding iomega module, which for the 250 unit means doing:

modprobe imm

if I remember correctly; the module is included in the kernel, you don't need compiling anything. After you do that, then maybe the tools you mentioned start to work; I havent tried them.

There is a howto with a lot of info:

/usr/share/doc/howto/en/txt/ZIP-Drive.gz

if you installed them, or in the net somewhere. It says to use the imm module for 100M drives, too.

You will also need a line in fstab for manually mounting; depending where it appears, you will need something like:

/dev/sda4 /media/zip2 auto defaults,noauto,user,exec 0 0

(zip disks come partitioned using the 4th partition).

You remember correct the imm for newer drives and ppa for older are both included. I just loaded them with: modprobe imm modprobe ppa without any error reported, but I have no such drive so I can't say do they work. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 17 June 2007 14:23, Clark Sann wrote:

Rajko M. wrote:

...

On Sunday 17 June 2007 05:24, Carlos E. R. wrote:

...

The Saturday 2007-06-16 at 19:29 -0500, Clark Sann wrote:

...

Anyone have any idea how I can get a 100 MB Iomega parallel port drive to work. I've connected it, have a zip drive in the drive, and rebooted. AFAIK, the system did not recognize the drive. I've spent an hour googling and am afraid I will have to recompile the kernel to add support for this think. Heck with that! I bet openSuse has an easier way. I've also browsed around Yast but couldn't find anything there. Finally, I installed 2 programs....gtkzip and ziptool. Neither work.

First, you hijacked the tread: «Subject: [opensuse] How to check processor is 32 bit or 64 bit ? in suse OS?»

About your question, it will not be autodetected. I haven't tried recently (ie, with 10.2), but basically you need to manually load the corresponding iomega module, which for the 250 unit means doing:

modprobe imm

if I remember correctly; the module is included in the kernel, you don't need compiling anything. After you do that, then maybe the tools you mentioned start to work; I havent tried them.

There is a howto with a lot of info:

/usr/share/doc/howto/en/txt/ZIP-Drive.gz

if you installed them, or in the net somewhere. It says to use the imm module for 100M drives, too.

You will also need a line in fstab for manually mounting; depending where it appears, you will need something like:

/dev/sda4 /media/zip2 auto defaults,noauto,user,exec 0 0

(zip disks come partitioned using the 4th partition).

You remember correct the imm for newer drives and ppa for older are both included. I just loaded them with: modprobe imm modprobe ppa without any error reported, but I have no such drive so I can't say do they work.

Thanks all for your help. I got the Zip drive working. Sorry for the inadvertent hijack. I won't do that again.

Hi Clark, I got your direct mail earlier today [1], where simple modprobe imm or modprobe ppa didn't worked, but I had no time to answer. Today is Fathers Day here so there are other important activities ;-) and online got to wait. There is few reasons why it didn't worked so it will be nice if you tell the list what happend and how you made it work [2]. [1] Thunderbird is at this time not very good option for this list. That will change in the future as Thunderbird will get option "Reply to list", but right now you should use "Reply to all" and then edit TO and CC fields. TO is filled with private address and it should be deleted, CC is filled with mail list address and it should be changed to TO. The other option is KMail, that has quite few options for handling lists, including the "Reply to list" and also one that confused me as I didn't looked in other possible effects of "Thread messages also by subject" option. ;-) [2] The HOWTO about parallel port ZIP drives is full of broken links, and while it is not many in use today people that have them should be able to use them. I intended to look into, but as mentioned today is not good day for online activity :-) I'll write article on openSUSE wiki about parallel port scanner installation, but I have no ZIP drive and I can't do much to rescue information how to install them. Your experience can help to people like you to give second life to their ZIP drives. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Charles Obler wrote:

--- "Rajko M." wrote:

...

I'll write article on openSUSE wiki about parallel port scanner installation, but I have no ZIP drive and I can't do much to rescue information how to install them. Your experience can help to people like you to give second life to their ZIP drives.

-- Regards, Rajko.

Wow! I HAVE a parallel port scanner with M$ driver disk. I tried to find a way to get the scanner to work with Linux, but finally gave up.

When you write the article, it will be very helpful to me! Thanks!

____________________________________________________________________________________ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222

It turned out to be very easy to make my 100 MB Parallel port zip drive work. Here are 6 simple steps along with some comments.... 1. From a root shell, run modprobe ppa and modprobe imm. One of them should work to install the drivers for your parallel port zip drive. ( I guess "install the drivers" is accurate?? I am a little fuzzy as to just what it is that modprobe does. I'm even more fuzzy about what insmod does.) For me, imm did not work, but ppa did. My research showed that imm only works for newer drives. Mine is REAL old. I don't really understand why, but when running modprobe, the results of the modprobe command are not shown in the terminal window. Goofy linux. Instead you have to go look at var/log/messages to see the results of the execution of the command. One of them should produce messages indicating the parallel port zip drive has been found. The messages will also tell you what device has been created. This will be an entry in the /dev folder. Once I ran modprobe ppa, a new /dev/sda4 folder appeared. Make a note of the folder name. 2. Create a mount point. I added a folder named zip100.0 to /media.... what I ended up was this.... /media/zip100.0. This becomes the place where the directory of the zip drive will be placed when you get the kernel talking to the hardware. 3. Modify /etc/fstab. This ties the device to the mount point. I modified fstab by adding the following line.... /dev/sda4 /media/zip100.0 vfat auto,user,exec,sync 0 0 This tells the kernel to tie the device (/dev/sda4) to the mount point (/media/zip100.0). It also says that the drive will be formatted using FAT, that it should be automatically mounted (which did not work so you might just as well put in noauto instead), that any user can mount the drive, that you can execute binaries, and that the mount occurs synchronously. 4. Now it is time to mount the drive. Everything up to now is setting up the plumbing to allow you to mount. Stuff a zip disk in the drive, preferably one with data on it.

From a shell, type "mount /media/zip100.0" Now you should see the directory of the disk in /media/zip100.0. Isn't linux wonderful? And so easy too!

When you are done, issue the command "umount /media/zip100.0". You will not be able to eject the disk until you unmount it. Note, unmount is "umount" not "unmount". 5. There are only two problems remaining. The first is that it sucks to have to enter "modprobe ppa" or "modprobe imm" every time you boot. To fix this, in /etc/init.d/boot.local, add either "modprobe ppa" or "modprobe imm". This will cause the command to be automatically executed at boot time. 6. The remaining problem is that you might wish there was an icon on your desktop you could click to view the drive contents in Konqueror. It turns out to be surprisingly easy to add this. Right click on the desktop. Select Create New and then Link to Device and then Zip Device. In the Devices tab, select the device (/dev/sda4) and you are done. An icon will be created. How to test your new zip drive installation.... Stuff a disk in the drive. Click the new icon on the desktop. Konqueror should come up with the drive contents. You should be able to add and delete files and folders. When you are done, right click on the icon and select either eject or unmount. Eject should unmount the drive and then eject it. For me eject did not always do the eject but it did always unmount it. You can always eject it manually. Problems. For some reason modprobe ppa did not work at first. Or maybe it did but I didn't know enough about what to look for because the result was in messages. I'm not sure what happened there. Also sometimes, the whole thing stops working and you cannot read or unmount or eject. I had to reboot when this happened. Restarting KDE did not work. I hope this helps. Unfortunately I no longer have my zip drive or any disks. I only had the system long enough to see if any old disks I had laying around had any useful data on them. I will still try to help, especially in the short term while my memory is still good! HA! Clark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 19. June 2007 01:25:56 Clark Sann wrote:

Charles Obler wrote:

...

--- "Rajko M." wrote:

...

I'll write article on openSUSE wiki about parallel port scanner installation, but I have no ZIP drive and I can't do much to rescue information how to install them. Your experience can help to people like you to give second life to their ZIP drives.

-- Regards, Rajko.

Wow! I HAVE a parallel port scanner with M$ driver disk. I tried to find a way to get the scanner to work with Linux, but finally gave up.

When you write the article, it will be very helpful to me! Thanks!

_________________________________________________________________________ ___________ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222

It turned out to be very easy to make my 100 MB Parallel port zip drive work. Here are 6 simple steps along with some comments....

1. From a root shell, run modprobe ppa and modprobe imm. One of them should work to install the drivers for your parallel port zip drive.

( I guess "install the drivers" is accurate?? I am a little fuzzy as to just what it is that modprobe does. I'm even more fuzzy about what insmod does.)

For me, imm did not work, but ppa did.

My research showed that imm only works for newer drives. Mine is REAL old.

I don't really understand why, but when running modprobe, the results of the modprobe command are not shown in the terminal window. Goofy linux. Instead you have to go look at var/log/messages to see the results of the execution of the command. One of them should produce messages indicating the parallel port zip drive has been found. The messages will also tell you what device has been created. This will be an entry in the /dev folder. Once I ran modprobe ppa, a new /dev/sda4 folder appeared. Make a note of the folder name.

2. Create a mount point. I added a folder named zip100.0 to /media.... what I ended up was this.... /media/zip100.0. This becomes the place where the directory of the zip drive will be placed when you get the kernel talking to the hardware.

3. Modify /etc/fstab. This ties the device to the mount point. I modified fstab by adding the following line....

/dev/sda4 /media/zip100.0 vfat auto,user,exec,sync 0 0

This tells the kernel to tie the device (/dev/sda4) to the mount point (/media/zip100.0). It also says that the drive will be formatted using FAT, that it should be automatically mounted (which did not work so you might just as well put in noauto instead), that any user can mount the drive, that you can execute binaries, and that the mount occurs synchronously.

4. Now it is time to mount the drive. Everything up to now is setting up the plumbing to allow you to mount. Stuff a zip disk in the drive, preferably one with data on it. From a shell, type "mount /media/zip100.0" Now you should see the directory of the disk in /media/zip100.0. Isn't linux wonderful? And so easy too!

When you are done, issue the command "umount /media/zip100.0". You will not be able to eject the disk until you unmount it. Note, unmount is "umount" not "unmount".

5. There are only two problems remaining. The first is that it sucks to have to enter "modprobe ppa" or "modprobe imm" every time you boot. To fix this, in /etc/init.d/boot.local, add either "modprobe ppa" or "modprobe imm". This will cause the command to be automatically executed at boot time.

The correct place for loading kernel modules on boot is /etc/modules ---8<--- /etc/modules ---8<--- # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. ppa #imm ---8<--- ---8<--- ---8<---

6. The remaining problem is that you might wish there was an icon on your desktop you could click to view the drive contents in Konqueror. It turns out to be surprisingly easy to add this.

Right click on the desktop. Select Create New and then Link to Device and then Zip Device. In the Devices tab, select the device (/dev/sda4) and you are done. An icon will be created.

How to test your new zip drive installation....

Stuff a disk in the drive. Click the new icon on the desktop. Konqueror should come up with the drive contents. You should be able to add and delete files and folders.

When you are done, right click on the icon and select either eject or unmount. Eject should unmount the drive and then eject it. For me eject did not always do the eject but it did always unmount it. You can always eject it manually.

Problems.

For some reason modprobe ppa did not work at first. Or maybe it did but I didn't know enough about what to look for because the result was in messages. I'm not sure what happened there. Also sometimes, the whole thing stops working and you cannot read or unmount or eject. I had to reboot when this happened. Restarting KDE did not work.

I hope this helps. Unfortunately I no longer have my zip drive or any disks. I only had the system long enough to see if any old disks I had laying around had any useful data on them.

I will still try to help, especially in the short term while my memory is still good! HA!

regards, thomas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

The Monday 2007-06-18 at 18:25 -0500, Clark Sann wrote:

...

It turned out to be very easy to make my 100 MB Parallel port zip drive work. Here are 6 simple steps along with some comments....

...

1. From a root shell, run modprobe ppa and modprobe imm.

That should be "or".

...

One of them should work to install the drivers for your parallel port zip drive.

Right.

...

( I guess "install the drivers" is accurate??

No, it "loads" the driver, or rather, module, which was already "installed" with the kernel. It is an integral part of the kernel, in module form.

...

I am a little fuzzy as to just what it is that modprobe does. I'm even more fuzzy about what insmod does.)

Let's just say that the former has some intelligence and can load extra modules if necessary, with options, while insmod is "dumb", or rather lower level if you like.

...

For me, imm did not work, but ppa did.

...

My research showed that imm only works for newer drives. Mine is REAL old.

Yes, that's correct, ppa is the old version.

...

I don't really understand why, but when running modprobe, the results of the modprobe command are not shown in the terminal window. Goofy linux.

Classic Linux commands doesn't say any thing if all went well ;-)

...

Instead you have to go look at var/log/messages to see the results of the execution of the command. One of them should produce messages indicating the parallel port zip drive has been found. The messages will also tell you what device has been created. This will be an entry in the /dev folder. Once I ran modprobe ppa, a new /dev/sda4 folder appeared. Make a note of the folder name.

Or just use the folder straight away.

...

2. Create a mount point. I added a folder named zip100.0 to /media.... what I ended up was this.... /media/zip100.0.

...

This becomes the place where the directory of the zip drive will be placed when you get the kernel talking to the hardware.

...

3. Modify /etc/fstab. This ties the device to the mount point. I modified fstab by adding the following line....

...

/dev/sda4 /media/zip100.0 vfat auto,user,exec,sync 0 0

...

This tells the kernel to tie the device (/dev/sda4) to the mount point (/media/zip100.0). It also says that the drive will be formatted using FAT, that it should be automatically mounted (which did not work so you might just as well put in noauto instead),

It will probably be mounted as soon as you load the ppa module. This can be done on boot if wanted.

...

that any user can mount the drive, that you can execute binaries, and that the mount occurs synchronously.

I prefer to use "noexec" for vfat mounts. I don't like all files be thought as executables in vfat dirs.

...

4. Now it is time to mount the drive. Everything up to now is setting up the plumbing to allow you to mount.

...

Stuff a zip disk in the drive, preferably one with data on it. From a shell, type "mount /media/zip100.0" Now you should see the directory of the disk in /media/zip100.0. Isn't linux wonderful? And so easy too!

Yep! :-)

...

When you are done, issue the command "umount /media/zip100.0". You will not be able to eject the disk until you unmount it. Note, unmount is "umount" not "unmount".

...

5. There are only two problems remaining. The first is that it sucks to have to enter "modprobe ppa" or "modprobe imm" every time you boot. To fix this, in /etc/init.d/boot.local, add either "modprobe ppa" or "modprobe imm". This will cause the command to be automatically executed at boot time.

Yes, if you have the drive connected permanently.

...

How to test your new zip drive installation....

Ah, I think there are some extra zip tools in the "mtools" suite: look up "mzip". You can, for instance, write-protect a disc, for instance - but I never tried. And they say it is buggy :-}

...

Eject should unmount the drive and then eject it. For me eject did not always do the eject but it did always unmount it. You can always eject it manually.

Try using eject a second time.

...

Also sometimes, the whole thing stops working and you cannot read or unmount or eject. I had to reboot when this happened.

Maybe because you loaded both modules and they conflicted. Also, how the parallel port is defined in the BIOS has an important effect: it may use only 4 bits to communicate with the drive, or 8 bits, or try to use dma - the last doesn't work with mine.

...

Restarting KDE did not work.

...

I hope this helps. Unfortunately I no longer have my zip drive or any disks. I only had the system long enough to see if any old disks I had laying around had any useful data on them.

I should do that and move data to CDs...

...

I will still try to help, especially in the short term while my memory is still good! HA!

I'm going from memory in this respect, too. I haven't used it for more than a year. I could easily be wrong on details.

Just a couple further questions regarding everyones comments.... Regarding etc/modules. I don't have that file. Is that unusual? Can I just create it if I need it? With respect to the problems I was having, I recall there was one disk, I think it was a tools disk...it came with the Iomega drive. Whenever I put that disk in and then tried to mount it, something bad happened and it wouldn't mount. Neither would any other disks until I rebooted. I have a hunch it was some weird format, something other than vfat. It has been so long since I had one of these drives on Win, I just can't remember what was special about that disk. I bet that the suggestion to rmmod and modprobe would have worked. Unfortunately, I don't have the drive any longer so I can't test. Thanks for the comments everyone! Clark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. wrote:

On Monday 18 June 2007 21:38, Clark Sann wrote:

...

Just a couple further questions regarding everyones comments....

Regarding etc/modules. I don't have that file. Is that unusual? Can I just create it if I need it?

etc/modules doesn't exist in openSUSE

ls -w1 /etc/mod* modprobe.conf modprobe.conf.local modprobe.d: <here is listing of files in modprobe.d directory>

The recommendation is to put your modules in /etc/modprobe.conf.local, but the /etc/init.d/boot.local works too for simple cases like this one.

...

With respect to the problems I was having, I recall there was one disk, I think it was a tools disk...it came with the Iomega drive. Whenever I put that disk in and then tried to mount it, something bad happened and it wouldn't mount. Neither would any other disks until I rebooted. I have a hunch it was some weird format, something other than vfat. It has been so long since I had one of these drives on Win, I just can't remember what was special about that disk. I bet that the suggestion to rmmod and modprobe would have worked. Unfortunately, I don't have the drive any longer so I can't test.

Now I know what happened, I'm not so sure that driver reload would work. Maybe.

There must be some trace in /var/log/messages what happened when command mount tried to mount that disk, and that is what you still have ;-)

Just looked at messages. Found a few like this... Jun 17 15:36:41 dell8600 kernel: SCSI device sda: 196608 512-byte hdwr sectors (101 MB) Jun 17 15:36:41 dell8600 kernel: sda: Write Protect is off Jun 17 15:36:41 dell8600 kernel: sda: Mode Sense: 25 00 00 08 Jun 17 15:36:41 dell8600 kernel: sda: cache data unavailable Jun 17 15:36:41 dell8600 kernel: sda: assuming drive cache: write through Jun 17 15:36:41 dell8600 kernel: sda: sda4 Jun 17 15:37:31 dell8600 kernel: SCSI device sda: 196608 512-byte hdwr sectors (101 MB) Jun 17 15:37:31 dell8600 kernel: sda: Write Protect is off Jun 17 15:37:31 dell8600 kernel: sda: Mode Sense: 25 00 00 08 Jun 17 15:37:31 dell8600 kernel: sda: cache data unavailable Jun 17 15:37:31 dell8600 kernel: sda: assuming drive cache: write through Jun 17 15:37:31 dell8600 kernel: SCSI device sda: 196608 512-byte hdwr sectors (101 MB) Jun 17 15:37:31 dell8600 kernel: sda: Write Protect is off Jun 17 15:37:31 dell8600 kernel: sda: Mode Sense: 25 00 00 08 Jun 17 15:37:31 dell8600 kernel: sda: cache data unavailable Jun 17 15:37:31 dell8600 kernel: sda: assuming drive cache: write through Jun 17 15:37:31 dell8600 kernel: sda: sda1 Jun 17 15:38:20 dell8600 su: (to root) clark on /dev/pts/1 Jun 17 15:39:27 dell8600 shutdown[4353]: shutting down for system reboot Notice the "sda:sda1" right before I shutdown. I am guessing that sda1 means a different format than sda4 but a quick google isn't telling me much about the difference. Clark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-06-18 at 22:40 -0500, Clark Sann wrote:

Just looked at messages. Found a few like this...

...

Jun 17 15:37:31 dell8600 kernel: sda: Mode Sense: 25 00 00 08 Jun 17 15:37:31 dell8600 kernel: sda: cache data unavailable Jun 17 15:37:31 dell8600 kernel: sda: assuming drive cache: write through Jun 17 15:37:31 dell8600 kernel: sda: sda1 Jun 17 15:38:20 dell8600 su: (to root) clark on /dev/pts/1 Jun 17 15:39:27 dell8600 shutdown[4353]: shutting down for system reboot

Notice the "sda:sda1" right before I shutdown. I am guessing that sda1 means a different format than sda4 but a quick google isn't telling me much about the difference.

Yes... zip disks for DOS came with partition 4 formatted, but those for MACs came with partition 1 - I think; perhaps it was 2 or 3. I know they used a diferent one, not sure which. The howto should tell. Me, I used part 1 in ext2. Now, the tool disk... it came with both partitions prepared. The first time you used it, it deleted the "other" partition, leaving only the "right" one for your system. Now, in which state came the partition table before this magick ocurred, I dunno, but it might be that what hapenned (althouh having a "new" tool disk would be rare). So, there you have a few clues about it. What happened would need a bit more investigation. It could be simply that the disk was really badly damaged and crashed something in the kernel or modules, or needed longer time to straighten out. The system probably tried to automount that partition 1. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGd6gztTMYHG2NR9URAmWJAJoDB+ZKkdqxMxTLQ8BejDZC2/MzJgCfXxcK 9QXO8ZMNZasVZAfpyx1jBGA= =Uy0B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 18 June 2007 10:54, Charles Obler wrote:

--- "Rajko M." wrote:

...

I'll write article on openSUSE wiki about parallel port scanner installation, but I have no ZIP drive and I can't do much to rescue information how to install them. Your experience can help to people like you to give second life to their ZIP drives.

-- Regards, Rajko.

Wow! I HAVE a parallel port scanner with M$ driver disk. I tried to find a way to get the scanner to work with Linux, but finally gave up.

When you write the article, it will be very helpful to me! Thanks!

This is first draft of article: http://en.opensuse.org/User:Rajko_m/wip it would be helpful if you can see how easy is to read and understand, so I can change it tomorrow. (Hmm.. It is actually today.) -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 19 June 2007 02:34, Johannes Meixner wrote:

Hello,

On Jun 19 00:51 Rajko M. wrote (shortened):

...

...

...

I'll write article on openSUSE wiki about parallel port scanner installation,

...

...

This is first draft of article: http://en.opensuse.org/User:Rajko_m/wip

For your information:

I have a "Plustek OpticPro 9630P" parallel port scanner and at least this model works at least for me without any additional software like ppscsi.

I only activated the "plustek_pp" backend in /etc/sane.d/dll.conf and perhaps I adjusted /etc/sane.d/plustek_pp.conf (I don't remember exactly, I tested it some time ago) and finally I set the device file permissions so that a normal user could access it.

Therefore I suggest that you mention that at least some kind of parallel port scanners don't need additional software (but nevertheless need manual setup).

Hi Johannes, thank you for the comment. I would need to include more details based on list: http://www.sane-project.org/sane-mfgs.html There is number of scanners that work without additional software. Though I would need more time and assistance to bring article in proper shape. My scanner was one of those with problem to be recognized, after loading ppscsi and onscsi it was found by YaST. With modified default nice level of ppscsi it works better than ever under windows. The only thing that seems to be a bug is need to set buffer size explicitly. It works fine with default 32768, but it is better if scanner has more. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 20 June 2007 04:38, Johannes Meixner wrote:

Of course there is no need that you write a comprehensive manual about all parallel port scanners.

Not intended. I just want to make owners of dusty old parallel port scanners aware that hardware can be used under openSUSE with points to SANE web page. I have to get idea what steps will user follow in order to install scanner and give answers what to do.

I like to point out that your current article seems to indicate that additional software is needed in any case to get a parallel port scanner working.

I got that with your last post. At the time I wrote the draft, I was still focused on my scanner that still fits my needs, but even after manual selection in YaST it didn't worked.

A note that some parallel port scanners don't need additional software while others do and a hint to read the appropriate SANE man page (e.g. "man sane-microtek2" for your scanner) and a link to the SANE project page for the model-specific details is perfectly sufficient.

So that would be the start: 1- try manual selection, 2- if it doesn't work check SANE list of supported scanners 1- explain what to look for in the list (backend name) 2- read manual page

I like to avoid that various users come up with problems how to compile and use kernel modules because your article may indicate that they need it in any case.

It is still not public (kind of), but I agree on this.

...

My scanner was one of those with problem to be recognized, after loading ppscsi and onscsi it was found by YaST.

The YaST scanner setup module does not serach at all for parallel port scanners. It calls /usr/lib/YaST2/bin/autodetect_scanners which is basically "sane-find-scanner -q" and this searches only for USB and SCSI scanners (see "man sane-find-scanner").

Your special SCSI modules make your parallel port scanner appear as a SCSI scanner so that it is then found by YaST and set up as a SCSI scanner as you described in your article.

In contrast my parallel port scanner works as native parallel port scanner.

Attempt to use manual setup in YaST didn't worked for this particular model. If it would be USB than I would never see ppscsi and company. Thanks again. I'll make changes tonight, at least to mark my example as special case. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 22 June 2007 09:04, James Hatridge wrote:

Hi all...

I just got my July Linux Journal from the States. In the Kernel Development column (page 12) it states that the parallel port code is now marked "unmaintained" and if someone does not step up to be the maintainer the code may be removed from the kernal.

JIM

The chance that someone will jump in for code that has no more use, even for printing, is very small, so we can expect to see that code removed. I guess even if removed it will be able to live long enough in the same way as ppscsi to support few devices that need it. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org