It is not recognising USB photographs, whereas 10.1 (don’t ask) did. /proc/partitions shows
no change. No usb modules are loaded, and loading usb_storage, usbhid and hid (which
works on some other Linuces) doesn’t help.
It is not recognizing USB photographs, whereas 10.1 (don’t ask) did. /proc/partitions shows
no change. No usb modules are loaded, and loading usb_storage, usbhid and hid (which
works on some other Linuxes) doesn’t help.
So, when you say USB, what type of device does that mean? Thumb Drive? USB Card Reader Appliance? External Hard drive, CD/DVD ROM drive? When you click on the Device Notifier in the System Tray, do any devices appear?
Thank You,
This works for me on KDE4 and LXDE desktops.
I suspect this could be device specific (ie specific to the device(s) you are using). If you type:
lsusb
it should show the usb device. If it does not (and I suspect it won’t based on the other locations you noted you looked in your post), then IMHO you could be in bug reporting territory.
It is important you obtain the product/device ID for a bug report, as my guess this is hardware specific (sometimes plugging in to a different USB hub helps).
If you can not get the product/device id from openSUSE, you should be able to do so from some other distributions (as you note they work for you), and that information might also be useful in your bug report.
There is guidance here for bug reports: openSUSE:Submitting bug reports - openSUSE and you can use your openSUSE forum username and password when logging on to bugzilla. If the SuSE-GmbH packager comes up with a fix, they are generally very good about submitting their fixes upstream so that all Linux distributions will benefit (which is something some other Linux distributions do not do, or if they do pass fixes upstream they are very slow in doing so).
Thanks for both replies. I am not totally sure what the term ‘system tray’ refers to, but I assume it means one of the acreens
accessible through the ‘Computer’ desktop tab. Anyway, I can’t find a device notifier anywhere plausible, but lsusb notes simply
that I have seven of the things (just ordinary USB connexions, nothing special):
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Of course, I can’t be quite certain that the ports SUSE sees are connected to the sockets on the outside of the case, which
doesn’t entirely help, but it is highly probable.
However, by installing the desktop kernel, I have got a bit further, and USB seems rather more visible in the system, and
I have added ‘user’ to the usbfs entry is fstab (which wasn’t there before). What is more, I have now got SOME messages in
/var/log/messages (hurrah!):
Apr 18 09:04:52 wheeler kernel: [38252.488303] usb 3-2: new full speed USB device using ohci_hcd and address 10
Apr 18 09:04:52 wheeler kernel: [38252.616194] usb 3-2: device descriptor read/64, error -62
Apr 18 09:04:53 wheeler kernel: [38252.845195] usb 3-2: device descriptor read/64, error -62
Apr 18 09:04:53 wheeler kernel: [38253.069197] usb 3-2: new full speed USB device using ohci_hcd and address 11
Apr 18 09:04:53 wheeler kernel: [38253.197195] usb 3-2: device descriptor read/64, error -62
Apr 18 09:04:53 wheeler kernel: [38253.426194] usb 3-2: device descriptor read/64, error -62
Apr 18 09:04:54 wheeler kernel: [38253.650299] usb 3-2: new full speed USB device using ohci_hcd and address 12
Apr 18 09:04:54 wheeler kernel: [38254.054181] usb 3-2: device not accepting address 12, error -62
Apr 18 09:04:54 wheeler kernel: [38254.177193] usb 3-2: new full speed USB device using ohci_hcd and address 13
Apr 18 09:04:54 wheeler kernel: [38254.579193] usb 3-2: device not accepting address 13, error -62
There’s clearly some misconfiguration, but it’s unclear where to attack it.
Progress. I should have to check how the box is wired, but I can now get the kernel to recognise the device on three out
of four slots - naturally, the one I tried first was the bad one. What’s wrong with that port is unclear, but it’s a common one
with USB sockets connected by string and sealing wax.
Next stage: to find out why Gnome/Nautilus/etc. are not picking it up. Sigh.
Curioser and curioser.
I have tried with a common or garden USB stick, and get the same effect. The kernel recognises them correctly
(both dmesg and lsusb give the correct identifications), but they get no further. They appear in /proc/bus/usb
(as a small, regular file) and /dev/bus/usb (as character devices).
However, neither mount -l nor df -a show anything, and I haven’t found how my previous system turned a
character device into a file system!
Sorry about so many self-repetitions, but this is definitely Nautilus (if that is what controls automounting, as I think it is).
Despite the bizarrities, the USB layer is working fine, and I have managed to mount a stick.
Are you able to manually mount the USB devices (assuming they can be seen with " fdisk -l " with root permissions) ?
Ahh ok … so you can manually mount.
Thats good news.
Yes. And handle my camera by invoking shotwell directly. Problem solved at this level.
==============================
It does appear that there is a new bug introduced into 11.4. I’ve been using 11.3 and before for over a year. An upgrade was a total disaster! I just did a fresh install. It is a semi disaster. I have turned off splash, so hopefully next boot I can get more information. What I have seen in safe mode is very long pauses and USB 8-2: Devices descriptor read/64, error -110. I saw this for 2-6 as well. I’m sure there was more, but it took a full 5 minutes to boot.
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 152e:1640 LG (HLDS)
Bus 005 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever
Bus 008 Device 002: ID 045e:0730 Microsoft Corp.
Don’t forget to raise the bug report:
The longer you wait to raise the report, the less likely that it will be looked at, as the SuSE-GmbH development team starts to pay attention to 12.1 instead of 11.4.
I was looking for a little validation before I willy nilliy post useless bug reports. SO many post without making sure and I’ve been blasted years ago for a duplicate or not really a bug… so was hesitant to just post. I’m rapidly becoming disillusioned though, since I’ve wasted 2 days trying to get it back to where I was, because of all the problems. I can’t even get the green banner to go away, so I can see what is going on under the hood during boot. I will confess I was even looking at different distros today. There are bugs that have been posted from 3 versions back that have not been fixed, so not real hopeful it will get addressed.
I would not worry about the risk of a duplicate. Anyone who ‘blasts’ someone else for a duplicate bug report is silly. Thats a sure way to prevent people reporting problems. I find the only occasions where there is annoyance at duplication is when the same bug is obvious and users keep raising a new bug report because of annoyance, and then annoyance continues to beget annoyance. Clearly that is not the case here.
Some bug reports get addressed and fixed. Some don’t. Many of the smaller distros don’t address bug reports. They can’t. They don’t have the resouces. Even larger distros can’t address a large % of the bug reports. I would venture a majority of the bugs rely on an upstream fix.
A lot depends on the expertise of the GNU/Linux distro’s packagers as to whether a bug can be addressed and fixed. And different distributions have different teams, and hence the capability to resolve different bugs. For example, SuSE-GmbH employ one of the alsa sound driver developers. Ergo bugs on one’s sound system have a high probability of being fixed in openSUSE compared to other distributions.
In some cases, if there is an upstream app that has a problem, the way to address the bug is to raise 2 bug reports. One on openSUSE (tracking the problem at a distribution level) and another upstream, tracking the problem at the upstream level. Then watch both bug reports, and try to help in each case. Where ever the fix shows up, one immediately passes the information to the other bug report. Often the fix will show up in the upstream bug report first, and one can pass the information downstream to be incorporated in openSUSE. Sometimes the fix shows up downstream, and typically the SuSE-GmbH packager will pass the fix upstream.
You raise some very good points. I went ahead and posted a bug report. We’ll see what happens. I have learned over the years about what you describe above. For instance the kttmgr program that is supposed to speak the time, is horribly mangled. I reported that in the KDE development area. It must be complex, since it was better in this release but didn’t work out of the box. I have not fooled with it yet, since I am trying hard to fix a bunch of things that broke with the new install. 
Update: I have found what is causing the problem. I have a WinTV USBPVR2 card attached. The Distro does not know what a USBPVR2 card is and chokes. The thing that needs fixing is, it needs to figure out that it doesn’t know what something is and allow a graceful way out. I honestly thought it was totally locked up and that is what started my journey down this failure path. In fact I’m betting the upgrade partially worked. It just didn’t know what my tv card was anymore and was just timing out. I came to an erroneous conclusion and like a moron pulled the trigger instead of pouring over my var/log files first. Had I just done that, I would have figured it out. OH well live and learn.
hi
show me the result of cat /etc/filesystems command
??? What does the file system have to do with it?
cat /etc/filesystems command
vfat
hfs
minix
reiserfs
*
lspci maybe? or?
For some openSUSE kernels (?) some users find adding ‘ntfs’ to that /etc/filesystems list helps recognize NTFS partitions that were not being properly recognized. I don’t recall that being for recognizing NTFS formatted USB devices, but maybe it does. I also do not recall it being the case for fat32 and I note vfat in the list from the ‘cat’ command.
Final update from me on this. It turns out for me that this was a red herring. It turns out the new kernel does not play nice with my Intel motherboard and cpu. It was causing all sorts of weird issues. Once this bios was updated with the latest firmware, it is working like a champ now. Thanks for all the feedback.
Good news to read it is fixed. For the record (and anyone else reading the thread) can you advise us what motherboard you have ?