System Log monologues

[Lordshooter]

System Log monologues, or "problema risolto!"..., errr..., with spaghetty, of course!



Dialog with the kernel.

Trying to run a scanner via connected cable to USB port of my laptop.

This might be the question to solve the problem:

„bad superblock on /dev/fd0 „ - what does that mean???

Excursion:

I pluged in my external HDD, into the same port, where my scanner will not work, just to see, how it would react:
I received the following message:

Quote:

Could not mount device.
The reported error was:
mount: block device /dev/fd0 is write-protected, mounting read-only


mount: wrong fs type, bad option, bad superblock on /dev/fd0,

missing codepage or other error

In some cases useful info is found in syslog
try dmesg | tail or so


I gave executable rights to /dev/fd0, but so far no changes happened.



Getting more info from Ksystemlog...:


cupsd Unable to open log file "/var/log/cups/access_log" - Permission denied
OK, gave permission.


[17179780.344000] usb-storage: device found at 5 (meaning the scanner)

Interesting...

[17179780.344000] usb-storage: waiting for device to settle before scanning
(meaning the scanner)
Wow!: Sounds very promissing...

[17179780.784000] end_request: I/O error, dev fd0, sector 0 (meaning the scanner)

Oh, what a pitty.... - Ah, well, hopefully very soon, though...., without error.


[17179785.396000] usb-storage: device scan complete (meaning the scanner)

Ups!...: Whaddya mean???... I did not scan, nor did I see a scanning process.


[17179793.852000] end_request: I/O error, dev fd0, sector 0 (meaning the scanner)

You see!...

[17179806.916000] end_request: I/O error, dev fd0, sector 2 (meaning the scanner)

...Aha, I see... he is talking about dev fdo in sector 0 and sector 2

[17179806.916000] EXT2-fs: unable to read superblock (meaning the scanner)

...Aha, so there is a problem with EXT2-fs!!! - And wyh can't ye read the superlock, hmm???

[17180878.332000] scsi1 : SCSI emulation for USB Mass Storage devices (meaning the HDD)

...Ok, then..., lets whait and see...

[17180878.332000] usb-storage: device found at 6 (meaning the HDD)

...Great!... I hope the scanner will be able to settle with some port, etc., very soon...

...Is that maybe form plugging in and out, that the devise gets a other number?
After all, its alwayst the same device, the same scanner... - Your making me crazy...



[17180878.332000] usb-storage: waiting for device to settle before scanning (but meaning the HDD)

(This must be all about the hard drive disk, I had plugged in, for testing, to see, if the port was ok.
After all, the scanner is not a storage device. Just my common sense again.

Here, he must of got confused. Well, so am I. Storage and scanning are two different things.

I might better not use the same port, once for storage, and once for trying to scan:
I agree more and more, that this might not be good, and might possibly be the problem.
So, probanly best to get a USB-hub, with a few ports, and then have one port for one cause and use each.)

Your talking about the external HDD, arn't ye?

Or... - But why are ye always mentioning the scanning issue as well? - I don't get it...

Talking about storage and scanning: That makes me a little confused...

[17180883.336000] SCSI device sda: 70984690 512-byte hdwr sectors (36344 MB) (meaning the HDD)

I am trying to understand..., yes, ok, go ahead, I am listening/reading...

[17180883.336000] sda: assuming drive cache: write through (meaning the HDD)

-What? Oh, boy, your giving me a headache...

kernel [17180883.336000] Type: Direct-Access ANSI SCSI revision: 02

kernel [17180883.336000] Vendor: Generic Model: USB Disk Rev: 9.02

kernel [17180883.340000] SCSI device sda: 70984690 512-byte hdwr sectors (36344 MB)

kernel [17180883.340000] sda: assuming drive cache: write through

kernel [17180883.340000] sda: sda1 sda2 sda3

kernel [17180883.392000] sd 1:0:0:0: Attached scsi disk sda

kernel [17180883.392000] sd 1:0:0:0: Attached scsi generic sg0 type 0

kernel [17180883.392000] usb-storage: device scan complete

(Here the kernenl was always talking about the HDD)

Nope, thats not about the scanner, that's about the HDD I had plugged in, into the same port, for testing, to see if the port was any good.

NetworkManager <debug info>^I[1195466743.748042] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_5809539a_3cb4_44c7_ae12_a0eac8184ba8') .
(meaning the HDD)
kernel [17180910.176000] usb 1-4: USB disconnect, address 6 (meaning the HDD)

NetworkManager <debug info>^I[1195466769.851646] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_58f_6390_noserial_if0_scsi_host_scsi_de vice_lun0_scsi_generic'). (meaning the HDD)

kernel says:
[17180915.204000] usb 1-4: new high speed USB device using ehci_hcd and address 7

The kernel is speaking about the scanner, which is the USB device, and wich is using the internal USB ports 1-4.



NetworkManager <debug info>^I[1195466775.113345] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_3f0_2305_SCN445B21V67Y').

Yes, this is the scanner:
(hal udi is '/org/freedesktop/Hal/devices/usb_device_3f0_2305_SCN445B21V67Y')

Hmm...: Could this maybe be used as a propper command??

What is: hal udi ?

I figure out, this is the path:

/org/
/freedesktop/
/Hal/
/devices/
/usb_device_3f0_2305_SCN445B21V67Y

Yes, that is the scanner...

I might have to do configurations, about „network“, because I would say, that the scanner is not part of a network.

If I mark the scanner as not part of a network, I might be able to have less confusion.

kernel shows up again, and says:
[17180946.896000] usb 1-4: usbfs: interface 0 claimed by usbfs while 'kooka' sets config #1

Kooka comes onto the scene, and grumbles, and claims his old complaints again:

kooka unable to connect hpssd socket 2207: Connection refused: api/hplip_api.c 738

kooka unable to open /var/run/hplip/hpssd.port: No such file or directory: api/hplip_api.c 103

kooka unable to connect hpssd socket 2207: Connection refused: api/hplip_api.c 738

kooka unable to open /var/run/hplip/hpssd.port: No such file or directory: api/hplip_api.c 103


Ok, Kooka, so it is: api/hplip_api.c 738 and api/hplip_api.c 103

I musst really have a close look into this. Thanks, Kooka, for insisting.

Well, hey, there are also some other guys, who have run into the same problem. Thank you, Google:

api/hplip_api.c - Google-Suche


[Moderator Edit: foreign languages removed... all posts must be in English - please refer to the Forum Rules! Sorry...]

It is always good to be able to study similar cases, and then just try to solve your own problem, with help from to all the useful information.

Here are a few comments and posts, picked out, just like „Tutti Frutti“:


Well, I will have a look at that, take it appart, and follow the hints, and names.

Next Google link:
Here we go: ...
No, sorry, wasn't any good: Long lenghty thread, with a few good ideas, but no solution found.
Ok: Nexto one:
No solution found. Nice thread, but also stuck.
Nex one, se if we might be lucky...:
Errr..., it a spanish thread, sorry, but if I see something like „gracias, etc, and somthing looking like a found solution, I will post it here.
Well, here is at least a interesting link, but the thread attempts where fruitless:

cPanel&#174;
Further, we go, and scrawl our way down...:
Ahh..., no here I just found some good information. Quote:
„Hello,

to follow up on my own mail:

> trixie:~ # scanimage -L
> device `hpaio:/usb/Deskjet_F300_series?serial=CN6A6GF23804KH' is a
> Hewlett-Packard Deskjet_F300_series all-in-one
>
> What is even better: I managed to scan using
>
> scanimage > /tmp/image.pnm
>
> But: running xsane gives:
>
> trixie:~ # xsane
> xsane: error while loading shared libraries:
> /software/hplip-1.7.1/SuSE-7.3/lib/libsane-hpaio.so.1: undefined symbol:
> cupsDoRequest

Ok, turned out that the wrong library was rpathed into the binary.
xsane now works like a charme...



Quote:
„I managed to scan using

scanimage > /tmp/image.pnm „

I tried it out, and the output is:

No Sane devices found.

Then he goes further with saying:
„ But: running xsane gives:

> trixie:~ # xsane
> xsane: error while loading shared libraries:
> /software/hplip-1.7.1/SuSE-7.3/lib/libsane-hpaio.so.1: undefined symbol:
> cupsDoRequest

Ok, turned out that the wrong library was rpathed into the binary.
xsane now works like a charme...
So, I conclude, that „Kooka“ might probably be no good for me, and that I might try my luck with „xsane“. ...I don't know...

Also, that other thread, won't bring us any further. Only if we can „patch a solution onto a unpatched solution“, then we solve our own solution.

Hey, this is a good one, I picked out of a post/thread. Jusst that short sentense, from a long thread:
Quote:
„I find mention of similar problems scattered all over the cybeworld but no solutions I understand or seem to apply to the combination of FC6 and HPLIP/

The whole problem seems to rest upon the errors regarding HPLIP I/O (hpiod).“

Well, maybe he is right. At least, a few files, need to have to be closer looked at.
And hplip, is sure one of them. Very sure.

He, he..., I might maybe just delete the Toolbox? No, I am affraid.

Next thread is polish, same problem, no solution found, lets move on. Or „go back to Italy“, you know, what I mean: „Bella Italia“. Bingo!

At this point, you can decide, to through your scanner out of the window, or to give it a big and warm and heartily hug. I just decided for the second option.

This means, that we still have a little troubleshooting to do. Lets get on with it....

You know, sometimes, you are in a vicious circle, and might just have to step out of it.

Then you maybe do happen to find a solution.



Thank god, Linux is open source, and free, because nobody is paying me, for my timeconsuming troubleshooting. - Might be a sort of a compensation. But it looks like, that it still won't fit the bill.

How expensive is Linux? I mean, at the end?

Don't start counting all the money...

Its like the opposite of buying a Mercedes Benz, expensive at first, to get one, so that you have one, but cheap, cheap, for doing the maintaining.

In tis case, you are cheap, chep,.. oh, I don't really know.

I think with Linux, at first it look, cheap, then you have some expenses in have to use a lot your precious time, meaning to be expensive, because time is money, if you see it that way. And then it gets cheap again. Lets say, in the long therm. But it is not toally free, or inexpensive, mind you.

So, back to our issue:

Oh, there is only one last thread. But boy, its a crazy one: Look yourself:

No, don't look: Hes only copied and pasted loads of files. -What is the output? I wonder...

No, but please don't look at it, I will have to do it, as you can't just skip information, when you are not sure if it is for you, or for the trash bin, trash can:

%(status)s


Hey, lets go back to our friend, the System Log, and read some mor bits and pieces, to make a nice „finale“ of this part of the thread for today:

You know what. After using my common sense again, I say this:
System Log missleads us somtimes, to find a solution. Some info might be good, some info, is jut not worth checking out. Just a waste of time. I just saw it in Google, in the forums: Nada, Njet, nothing.
No results. But wait, I am wrong: Bella Italia had a solution, didn't they? It is good, I understand some italien. Uh, I feel like having a big plate of spaghetty with loads of tomato sauce ontop.

System Log, without the sauce, please:

No, forget it.

System Log, is only repeating, what we allready know.

I feel hungry.


Thank you, for your attention,

Alexander

[fingal]

[Lordshooter]

Hey, thank you so much!

Great post!

Cool!



Alexander

[apoorv_khurasia]

I have no idea what you're talking about....so here's a bunny with a pancake on its head.

Good one