I hope I can test this with my old laptop which has no ehci either, but I didn't boot it in almost two years. This suggests there is a USB controller loaded, but the device cannot be added. No idea where to go from here. EDIT: Can we get some more output from your boot screen?
Anyone who has not provided this "backdoor" for themselves faces a very difficult task. Same problem for you, the autodetect hook didn't see your host controllers.
The patch Aaron posted above should help you as well. Please see mkinitcpio 0. Well, none of the solutions works for me. At the moment the keyboard and mouse even have no power at password requestion. I don't get the "unable to enumerate" messages anymore, the usb support seems to be disabled completely.
A look at dmesg shows, that usb devices are detected at line , but password requestion is already at line , I guess. Surprisingly few unter [usbinput] Here it is. Tried to contact you with your jabberid, but it seem to be out of date - could be easier for those debugging? You should have similar output. Are you using a custom kernel or the stock kernel? Only a small post this time ;- Patching for - vs. But maybe we should think about the reason for this report: this problem is first since 2.
What have changed in this version on the usb stuff that breaks our process of creating initrd images I personally have not idea ATM. Gerhard, please go through and provide all the info I asked lobotomisator for. The kernel has no bearing on whether modules are included in the ramfs. Laptop, USB1. Here it seems that all would work right. Got me So silly Ok, so - does this new patch actually solve the problem? Then lobotomisator is the only one remaining and I believe in a kernel bug here. Should be fixed by 0.
Please confirm. I've been watching task over the past couple days, but had not applied any of the patches or work-arounds described above. Arch devs sure work fast! I'm willing to paste some log info, just let me know what would be helpful, and where it can be found. Everything that appears on your screen between udev is started and the LUKS prompt will be useful.
You did regenerate your initramfs, right? Found out something interesting: I have a remote for the pc, that's working with an ir-usb-cable and is detected as keyboard - and this works at my boot. My Cherry Stream Evolution usb keyboard for some reason still doesn't. But I had a closer look on my dmesg again see attachment and I wondered a bit.
I don't have much knowledge about the inner processes, so that all are guessings from me, don't blame me if I say something wrong There are the interesting events in this order: line device-mapper: uevent: version 1.
Is it "bad" that the driver says "cherry" and not "generic-usb"? I hope this brings us forward. PS: I forgot to say that it of course pauses before line until I entered the pw. And an addition: If I unplug and plug in my mouse on boot it looks like that: usb Yeah, please post the output of "lsmod" when the system is running.
It looks like it's using usbhid though, but better check. Its quicker. Arch Linux is a rolling release. This means that problems such as this will get fixed on Arch in due course, but on Kubuntu Not only that, but KDE 4. PS: If it helps I doubt it will, but you never know , I can zip up the directory in which I compiled the working driver in Kubuntu, including object files and the final.
I just wanted to know the kernel version for comparison - your answer supports the possible cause I gave above. In this case, no amount of "release-rolling" is going to help. You will just have to wait for VIA to release an updated version that works with kernel 2.
Those identifiers which include the sting "vntwusb" in their name have to do with the VT driver itself, and everything else probably has to do with the USB interface to and from the kernel proper. So, if someone ARCH-knowledgeable and source code savvy could investigate the differences in the kernel's USB interface modules between kernel version 2. Given that VIA have released this driver just twice in a couple of years, and given that it still works as is with Ubuntu Jaunty, I am not hopeful of getting any joy from VIA to address this issue.
It's possible someone somewhere will patch it for 2. I have an image file for Chakra for a USB stick. This is the Alpha 2 version of Chakra, which can be found here:. No joy so far. I can't update to current because a number of packages, such as glibc and madwifi, depend on the kernel version. Make still wont make So I'm still scratching my head. Does anyone have any idea what that error message means? Perhaps I should remove the IgnorePkg line in pacman. As I understand it, it now compiles and works after a fashion.
This driver will be included in Linux kernel 2. Is there any enterprising sole who might be able one day to download code from git and have a try at a preview version for Arch?
Atom topic feed. Arch Linux. Just reinstalled the kernel and did a reboot and all seems to be ok. Pacman did confirm that the package was already installed and that it was going to reinstall it. Don't know what happened but it is fixed now. Sorry for the silly question: did you reboot the machine after the first update? You were running the previous kernel that wasn't obviously able to load the newer installed module.
Ye, it was the morning after the upgrade that I booted and didn't have any shares. It was like that for a few days before I did the reinstall which fixed everything. Its working for me now so I'm happy to close it.
0コメント