[Bug 311890] Re: imon driver does not work, irw crashes lircd
I wouldnt wait for any ubuntu dev's to help mate, they dont actually do any coding they just compile the package and their done. Ive been through a similar issue with ubuntu before and your 2 best choices are to buy different hardware or swap to another Distro. Im going to be using anyremote with a usb bluetooth adaptor to get this HTPC up and running. -- imon driver does not work, irw crashes lircd https://bugs.launchpad.net/bugs/311890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311890] [NEW] imon driver does not work, irw crashes lircd
Public bug reported: Binary package hint: lirc Description:Ubuntu 8.10 Release:8.10 lirc 0.8.3-0ubuntu2 Linux Infra-red Remote Control support o...@mediapc:~# dmesg | grep imon [ 334.839718] lirc_imon: Driver for Soundgraph iMON MultiMedia IR/VFD w/imon pad2keys patch, v0.3p2k [ 334.839733] lirc_imon: Venky Raju [ 334.841034] usbcore: registered new interface driver lirc_imon r...@mediapc:~# lsmod | grep lirc lirc_imon 23052 0 lirc_dev 20020 1 lirc_imon usbcore 148848 7 lirc_imon,usbhid,usb_storage,libusual,ohci_hcd,ehc i_hcd When I run irw it simply exits the 1st time without any message, the second time it errors and the lirc daemon crashes. r...@mediapc:~# /etc/init.d/lirc restart * Stopping remote control daemon(s): LIRC [ OK ] * Loading LIRC modules [ OK ] * Starting remote control daemon(s) : LIRC [ OK ] r...@mediapc:~# irw r...@mediapc:~# irw connect: Connection refused r...@mediapc:~# /etc/init.d/lirc restart * Stopping remote control daemon(s): LIRC [fail] * Loading LIRC modules [ OK ] * Starting remote control daemon(s) : LIRC [ OK ] I do not have a /dev/lirc0 but I do have /dev/lircd. Running irw /dev/lircd does not help. Mode 2 errors: r...@mediapc:~# mode2 mode2: error opening /dev/lirc mode2: No such file or directory ** Affects: lirc (Ubuntu) Importance: Undecided Status: New -- imon driver does not work, irw crashes lircd https://bugs.launchpad.net/bugs/311890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
> I can assure you the issue absolutely has nothing to do with NTFS. Yes as I said in my previous post, fault ntfs-3g is not at fault in this case. I emailed the manufacturer of my drives and this was their response (unfortunately): Fw: GreenStarME-740PS linux support fromTiffany <[EMAIL PROTECTED]> to [EMAIL PROTECTED], dateMon, May 12, 2008 at 4:43 PM subject Fw: GreenStarME-740PS linux support mailed-by welland.com.tw Hello Sir ME-740PS don't support Linux, please kindly know!! Thanks, Tiffany From: Jacob Jarick [mailto:[EMAIL PROTECTED] Sent: Saturday, May 03, 2008 5:38 PM To: sales; [EMAIL PROTECTED] Subject: Fwd: GreenStarME-740PS linux support The bug does persist with your power saving caddies and the linux kernel in 2.6.25, is their a linux version of your tool available to adjust the drive idle times ?. https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.17/+bug/61235/comments/104 -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
Failure again, while copying from a welland psc (power saving caddy) to a normal firewire caddy. 5gb into copy. Here is the strange ls output: [EMAIL PROTECTED]:/mnt# ls -la usb2/ total 4 drwxrwxrwx 1 mem root 4096 2008-05-03 14:02 . drwxr-xr-x 8 root root 88 2008-05-01 21:08 .. drwxrwxrwx 1 mem root0 2008-05-02 00:01 Media ?- ? ?? ?? usb2/Incomming ?- ? ?? ?? usb2/SuperCopier2beta1-9.exe [EMAIL PROTECTED]:/mnt# cat /etc/fstab | grep usb2 LABEL=sleepy2 /mnt/usb2 ntfs-3g defaults,uid=1000 0 0 var/log/messages output: May 3 13:59:56 cesspit kernel: [167270.573707] XFS mounting filesystem sdb1 May 3 14:07:33 cesspit kernel: [167789.981969] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:10:19 cesspit kernel: [167973.291042] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:10:49 cesspit kernel: [168009.169512] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:10:59 cesspit kernel: [168021.281996] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:11:15 cesspit kernel: [168040.401488] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:11:16 cesspit kernel: [168040.778268] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:11:26 cesspit kernel: [168052.821977] usb 2-4: reset high speed USB device using ehci_hcd and address 17 May 3 14:11:26 cesspit kernel: [168053.058472] sd 10:0:0:0: Device offlined - not ready after error recovery May 3 14:11:26 cesspit kernel: [168053.058508] sd 10:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK May 3 14:11:26 cesspit kernel: [168053.058638] sd 10:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK May 3 14:11:39 cesspit kernel: [168068.578563] printk: 28 messages suppressed. While watching the copy, I noticed the psc power down during a copy, the kde copy dialog stalled while the messages "usb 2-4: reset high speed USB device using ehci_hcd and address 17" were printing to var/log. The copy did resume once, picked back up normal speed but powered down again a 2nd time and failed to come back online. trying to remount the device has been working over the past few days but not today, output (note I use labels for mounting): [EMAIL PROTECTED]:/mnt# umount usb2 [EMAIL PROTECTED]:/mnt# mount usb2 Error opening '/dev/sdc1': No such device or address Failed to mount '/dev/sdc1': No such device or address You seem to have a SoftRAID/FakeRAID hardware and must use an activated, different device under /dev/mapper/, (e.g. /dev/mapper/nvidia_eahaabcc1) to mount NTFS. Please see the 'dmraid' documentation for help. Power cycling fixed the device. I will note this drive is a bit old and noisy but has never presented any issues when in use on my fileserver (connected internally). The issues are also not present in windows xp on any machines. I would suspect ntfs to be contributing to the issue but the other identical psc has the same issue though it doesnt not need to be power cycled as often. I did contact welland regarding the issue and the had this to say: Dear Customer, Thanks for your mail and purchased our product. Pls. use our power saving AP tool to control the time of power down. By the way, may I know where are you from? Thanks. Thanks & Best regards, Jing Lee / Sales department Welland Industrial Co., Ltd Tel: +886-2-8285-2345 ext. 18 Fax: +886-2-8282-5000, 8282-7000 E-mail: - Web: www.welland.com.tw -EOF- I does seem they didnt realise I am in linux but I will plug these psc into a windows pc, use the tool to raise the timeout and retry. The latest kernel does not seem to fix the issue after all but it does seem an improvement. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
I have had both welland power saving drives fail with the errors since the 140gb copy. Interestingly the failures only seem to happen after the drives have been idle for a long time (~ 1 hour +). Seems doing a ls /mnt/usb3 will fail or return a weird listing. The devices will resume working (which never used to on earlier kernels) after doing this: umount drive Power cycle drive mount drive. here is my /var/log/messages from when I was getting the drive back online: May 3 11:16:39 cesspit kernel: [155646.665581] usb 2-4: reset high speed USB device using ehci_hcd and address 10 May 3 11:16:42 cesspit kernel: [155650.930383] usb 2-4: reset high speed USB device using ehci_hcd and address 10 May 3 11:16:42 cesspit kernel: [155651.218163] usb 2-4: device firmware changed May 3 11:16:42 cesspit kernel: [155651.218198] usb 2-4: USB disconnect, address 10 May 3 11:16:42 cesspit kernel: [155651.218594] sd 6:0:0:0: [sde] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:42 cesspit kernel: [155651.218803] sd 6:0:0:0: [sde] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:42 cesspit kernel: [155651.321842] usb 2-5: reset high speed USB device using ehci_hcd and address 11 May 3 11:16:43 cesspit kernel: [155651.474080] usb 2-5: device firmware changed May 3 11:16:43 cesspit kernel: [155651.474080] sd 7:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:43 cesspit kernel: [155651.474249] sd 7:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:43 cesspit kernel: [155651.549534] sd 7:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:43 cesspit kernel: [155651.582133] usb 2-4: new high speed USB device using ehci_hcd and address 16 May 3 11:16:43 cesspit kernel: [155651.613836] sd 7:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:43 cesspit kernel: [155651.660971] sd 7:0:0:0: [sdf] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK May 3 11:16:43 cesspit kernel: [155652.130060] usb 2-4: new high speed USB device using ehci_hcd and address 17 May 3 11:16:44 cesspit kernel: [155652.699106] usb 2-4: configuration #1 chosen from 1 choice May 3 11:16:44 cesspit kernel: [155652.751997] scsi10 : SCSI emulation for USB Mass Storage devices May 3 11:16:44 cesspit kernel: [155652.811351] usb 2-5: USB disconnect, address 11 May 3 11:16:44 cesspit kernel: [155652.811351] lost page write due to I/O error on sdf1 May 3 11:16:44 cesspit kernel: [155652.969331] usb 2-5: new high speed USB device using ehci_hcd and address 18 May 3 11:16:44 cesspit kernel: [155653.105750] usb 2-5: configuration #1 chosen from 1 choice May 3 11:16:44 cesspit kernel: [155653.117219] scsi11 : SCSI emulation for USB Mass Storage devices May 3 11:16:49 cesspit kernel: [155658.678815] scsi 10:0:0:0: Direct-Access WDC WD30 00JB-00KFA0 PQ: 0 ANSI: 2 CCS May 3 11:16:49 cesspit kernel: [155658.687351] sd 10:0:0:0: [sdc] 586070255 512-byte hardware sectors (300068 MB) May 3 11:16:49 cesspit kernel: [155658.688338] sd 10:0:0:0: [sdc] Write Protect is off May 3 11:16:49 cesspit kernel: [155658.690078] sd 10:0:0:0: [sdc] 586070255 512-byte hardware sectors (300068 MB) May 3 11:16:49 cesspit kernel: [155658.691086] sd 10:0:0:0: [sdc] Write Protect is off May 3 11:16:49 cesspit kernel: [155658.691101] sdc:<7>usb-storage: device scan complete May 3 11:16:49 cesspit kernel: [155659.020803] scsi 11:0:0:0: Direct-Access WDC WD20 00JB-00GVC0 PQ: 0 ANSI: 0 May 3 11:16:50 cesspit kernel: [155659.720107] sdc1 May 3 11:16:50 cesspit kernel: [155659.720107] sd 10:0:0:0: [sdc] Attached SCSI disk May 3 11:16:50 cesspit kernel: [155659.720107] sd 10:0:0:0: Attached scsi generic sg1 type 0 May 3 11:16:50 cesspit kernel: [155659.720107] sd 11:0:0:0: [sdd] 390721968 512-byte hardware sectors (200050 MB) May 3 11:16:50 cesspit kernel: [155659.721120] sd 11:0:0:0: [sdd] Write Protect is off May 3 11:16:50 cesspit kernel: [155659.723127] sd 11:0:0:0: [sdd] 390721968 512-byte hardware sectors (200050 MB) May 3 11:16:50 cesspit kernel: [155659.725148] sd 11:0:0:0: [sdd] Write Protect is off May 3 11:16:50 cesspit kernel: [155659.725174] sdd: sdd1 May 3 11:16:50 cesspit kernel: [155659.741298] sd 11:0:0:0: [sdd] Attached SCSI disk May 3 11:16:50 cesspit kernel: [155659.741366] sd 11:0:0:0: Attached scsi generic sg2 type 0 May 3 11:17:47 cesspit kernel: [155726.433030] xfs_force_shutdown(sdb1,0x1) called from line 420 of file fs/xfs/xfs_rw.c. Return address = 0xf098f5b3 May 3 11:17:47 cesspit kernel: [155726.434051] xfs_force_shutdown(sdb1,0x1) called from line 420 of file fs/xfs/xfs_rw.c. Return address = 0xf098f5b3 May 3 11:18:55 cesspit kernel: [155807.791257] usb 2-6: USB disconnect, address 15 May 3 11:19:37 cesspit kernel: [155857.500764] usb 2-6: new high speed USB device using ehci_h
[Bug 61235] Re: USB mass storage stops working after a while
Transfer test worked excellent last night, I shifted 140gb from 1 welland caddy to the other welland caddy (Welland caddies are one of the ones containing the chipset pre 2.6.25 has issues with). So solution can be confirmed. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
Files finished uploading, have at it. kernel: http://rapidshare.de/files/39283576/linux-headers-2.6.25-custom.tar.bz2.html [EMAIL PROTECTED]:/usr/src# sha1 linux-headers-2.6.25-custom.tar.bz2 9c0e457675b326af59c615a6423682441bf366f4 linux-headers-2.6.25-custom.tar.bz2 [EMAIL PROTECTED]:/usr/src# md5 linux-headers-2.6.25-custom.tar.bz2 bb22393ce57b31cd4ffb92d0208763eflinux-headers-2.6.25-custom.tar.bz2 nvidia legacy driver: http://rapidshare.de/files/39283713/NVIDIA-Linux-x86-71.86.04-pkg1-custom.run.html [EMAIL PROTECTED]:/home/mem/downloads# sha1 NVIDIA-Linux-x86-71.86.04-pkg1-custom.run 0ac4efc7b3bc37b9944257620e80b6a5f22f6093 NVIDIA-Linux-x86-71.86.04-pkg1-custom.run [EMAIL PROTECTED]:/home/mem/downloads# md5 NVIDIA-Linux-x86-71.86.04-pkg1-custom.run 86e6fb93c254764f6978984eda3c9e11 NVIDIA-Linux-x86-71.86.04-pkg1-custom.run note: I run a asus tnt2 ultra - hence legacy driver, people needing a driver for a later model card will need to do the patch themselves. -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61235] Re: USB mass storage stops working after a while
Well after alot of searching via google I came across this thread, not much in the way of answers but enough research done to dismiss the "faulty caddy/usb controller/ hardware" excuse. Seems its just an issue with ubuntu's current kernel. 2.6.25 does not have the issue. I have created the needed deb's for people who do not like compiling their own kernel (hosted via rapidshare due to size). A side note for people who do upgrade to the latest kernel beware that the nvidia drivers currently do not work without patching them, check the link below on howto patch the driver yourself or just download the 1 I have uploaded to rapidshare. I will post the links to the files once the upload has finished (hopefully tonight but I do only have 25kb upstream). To install the new kernel simply do the following commands: tar xjvf linux-headers-2.6.25-custom.tar.bz2 dpkg -i linux*2.6.25-custom*.deb To compile the kernel yourself download the latest from http://www.kernel.org and then follow this very nice ubuntu howto: https://help.ubuntu.com/6.10/ubuntu/installation-guide/i386/kernel-baking.html If you happen to have a nvidia card like I mentioned before and wish to manually patch the driver yourself read this forum thread: http://www.nvnews.net/vbulletin/showthread.php?t=110088 Note: I misnamed the archive when creating it it was ment to be linux-2.6.25-custom.tar.bz2 not linux-headers-2.6.25-custom.tar.bz2, but I assure you it has the debs you want. Quick plug for my own program (cool batch file renamer): http://namefix.blogspot.com Any questions drop me a line - [EMAIL PROTECTED] -- USB mass storage stops working after a while https://bugs.launchpad.net/bugs/61235 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
