Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using Linksys E1200 router for wireless network, which recently for some reason get knocked off whack. It was not a big problem though to reset the router and reestablish network, all PC and mobile devices are now connected. However, my RHEL655 box (Dell Optiplex 745) that uses Dell 1180 wireless USB adaptor still cannot. There was no change in router settings, access control, etc., all remained the same. Here is output:
[yaximik@SciLinux55 ~]$ dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb usb5: configuration #1 chosen from 1 choice
usb usb6: configuration #1 chosen from 1 choice
usb usb7: configuration #1 chosen from 1 choice
usb 3-2: new full speed USB device using uhci_hcd and address 2
usb 3-2: configuration #1 chosen from 1 choice
usb 7-1: new low speed USB device using uhci_hcd and address 2
usb 7-1: configuration #1 chosen from 1 choice
input: USB HID v1.10 Mouse [Dell Dell USB Mouse] on usb-0000:00:1d.2-1
usb 7-2: new low speed USB device using uhci_hcd and address 3
usb 7-2: configuration #1 chosen from 1 choice
input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1d.2-2
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
prism2usb_init: prism2_usb.o: 0.2.9 Loaded
prism2usb_init: dev_info is: prism2_usb
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
usbcore: registered new driver prism2_usb
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
usbctlx_rrid_completor_fn: RID len mismatch, rid=0xfcbe hlen=2 fwlen=-2
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
hfa384x_usbin_ctlx(0): Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com
Apparently prizm2 driver is loaded, it was working just fine before the router had to be reset. And what the heck is Universe and how to reboot it? Rebooting the box does not help - the log shows red Fail next to network and says No Link. The adaptor also slowly blinks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.