Re: [kde-freebsd] multislot cardreader and hald
On Thursday 20 December 2007 19:13:29 Joe Marcus Clarke wrote: On Thu, 2007-12-20 at 11:03 -0600, Jeremy Messenger wrote: On Thu, 20 Dec 2007 10:51:37 -0600, Andriy Gapon [EMAIL PROTECTED] wrote: on 20/12/2007 18:47 Jeremy Messenger said the following: On Thu, 20 Dec 2007 09:28:01 -0600, Andriy Gapon [EMAIL PROTECTED] wrote: When I connect a USB multislot cardreader (CF, SD, etc) with only one card inserted to my computer my /var/log/messages gets spammed with the endless reports like the following: kernel: Opened disk da1 - 6 kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition kernel: (da2:umass-sim0:0:0:2): NOT READY csi:0,aa,55,41 asc:3a,0 kernel: (da2:umass-sim0:0:0:2): Medium not present field replaceable unit: 1 kernel: (da2:umass-sim0:0:0:2): Unretryable error kernel: Opened disk da2 - 6 kernel: (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 kernel: (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error kernel: (da3:umass-sim0:0:0:3): SCSI Status: Check Condition kernel: (da3:umass-sim0:0:0:3): NOT READY csi:0,aa,55,41 asc:3a,0 kernel: (da3:umass-sim0:0:0:3): Medium not present field replaceable unit: 1 kernel: (da3:umass-sim0:0:0:3): Unretryable error kernel: Opened disk da3 - 6 These reports are for the empty slots. If I disable hald these messages get printed only a few times, but with hald this happens endlessly, apparently every 2 seconds. I am curious if this is hald itself or KDE acting through it. It's FreeBSD since you still get w/out hald, report to [EMAIL PROTECTED] It's true that messages come from the kernel but, as I said, without hald I get only a few of them and that's it. With hald running these messages are produced every 2 seconds until the card-reader is disconnected. So hald must be doing something silly here, like never giving up on probing those da disks without any media behind them. I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. This is a FreeBSD problem, but it's not a hal problem per se. I think the GEOM/SCSI people are working to hide these kind of messages, but in the meantime, you either need to live with them, stop using hal, or tell hal to stop probing that device. The way hal works is that it periodically probes devices to determine if there is media changes. In this manner, hal can auto-mount volumes. If you do not want to auto-mount media from this device, then search the archives for ways to manipulate the .fdi files to stop hal from probing this device. Again, the ideal solution would be for the kernel people to hide these messages behind verbose booting. Ideal solution will be this way if you insert media into reader then it sends kernel a message about insertion (I guess cd/dvd works that way) and tell HALd to mount that device. IIRC then on Linux hald works correctly- this is only FreeBSD problem. ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
on 20/12/2007 19:03 Jeremy Messenger said the following: I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. I now see what you are saying and this makes a lot of sense indeed. And I agree that FreeBSD kernel is overly verbose about such a condition - after all it is normal that a device with a (field) removable media can have no media. I need to check how FreeBSD 7 behaves in this respect - I still use 6.2. BTW, it seems that the messages come from SCSI/CAM code, so USB code might not be a culprit here, it's just a transport for SCSI. OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean the constant querying (errors are still printed on access). This is a very un-educated guess: maybe HAL knows that acd/cd can have have no media and does some checks before accessing it, but maybe it expects that da always has media and so it tries to access it without any special checks ? I.e. one can simply open and try to read da device or one could issue some SCSI commands to query the actual HW. -- Andriy Gapon ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon [EMAIL PROTECTED] wrote: on 20/12/2007 19:03 Jeremy Messenger said the following: I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. I now see what you are saying and this makes a lot of sense indeed. And I agree that FreeBSD kernel is overly verbose about such a condition - after all it is normal that a device with a (field) removable media can have no media. I need to check how FreeBSD 7 behaves in this respect FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in and I will get over 16k lines in message under a minute. http://people.freebsd.org/~mezz/messages.txt.bz2 If I put a blank CD in and I only get less than ten lines in messages. I can't wait for someone to fix FreeBSD because that over 16k lines under a minute is very annoy. Cheers, Mezz - I still use 6.2. BTW, it seems that the messages come from SCSI/CAM code, so USB code might not be a culprit here, it's just a transport for SCSI. OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean the constant querying (errors are still printed on access). This is a very un-educated guess: maybe HAL knows that acd/cd can have have no media and does some checks before accessing it, but maybe it expects that da always has media and so it tries to access it without any special checks ? I.e. one can simply open and try to read da device or one could issue some SCSI commands to query the actual HW. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
Jeremy Messenger wrote: On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon [EMAIL PROTECTED] wrote: on 20/12/2007 19:03 Jeremy Messenger said the following: I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. I now see what you are saying and this makes a lot of sense indeed. And I agree that FreeBSD kernel is overly verbose about such a condition - after all it is normal that a device with a (field) removable media can have no media. I need to check how FreeBSD 7 behaves in this respect FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in and I will get over 16k lines in message under a minute. http://people.freebsd.org/~mezz/messages.txt.bz2 If I put a blank CD in and I only get less than ten lines in messages. I can't wait for someone to fix FreeBSD because that over 16k lines under a minute is very annoy. Disc media is treated differently than USB media. USB umass devices are assumed to have media. This is part of the issue with the card reader (floppy drives behave the same way). Joe Cheers, Mezz - I still use 6.2. BTW, it seems that the messages come from SCSI/CAM code, so USB code might not be a culprit here, it's just a transport for SCSI. OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean the constant querying (errors are still printed on access). This is a very un-educated guess: maybe HAL knows that acd/cd can have have no media and does some checks before accessing it, but maybe it expects that da always has media and so it tries to access it without any special checks ? I.e. one can simply open and try to read da device or one could issue some SCSI commands to query the actual HW. -- Joe Marcus Clarke FreeBSD GNOME Team :: [EMAIL PROTECTED] FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
