search

dnschneid / crouton

Chromium OS Universal Chroot Environment
https://goo.gl/fd3zc?si=1
BSD 3-Clause "New" or "Revised" License
8.57k stars 1.24k forks source link

Udevd doesn't auto start in chroot #320

Closed nzv8fan closed 11 years ago

nzv8fan commented 11 years ago

I've been working on getting a Huawei E173 USB Modem working. It's one of those frustrating modems that initially appears as a CD Rom drive, then usb_modeset changes it to a modem device.

When I plug the modem into my Chromebook the udev rules within the chroot environment don't run because udevd isn't running inside that environment. Additionally because the underlying Chrome OS environment doesn't have usb_modeset the modem doesn't work.

If within the chroot environment, I manually run sudo udevd --daemon the udev rules will now execute and the modem will work with wvdial.

Is there a way to enable udevd to always run within the chroot? Some posts elsewhere online consider this a bad idea because the base system should do all the udev stuff, but if the base system doesn't have the ability to do the modeswitch, then what other approach can one take?

picostove commented 11 years ago

You could add udevd to your /etc/rc.local - crouton will always run that when you're entering a chroot. As for the repercussions of running multiple udevd instances at once, I have no idea how that'd be handled. I'd recommend at the very least, if you go that route, that you remove all of the rules you don't need from /lib/udev/rules.d/ in the chroot. Hopefully that would keep the chroot udev instance from mucking things up for other devices.

nzv8fan commented 11 years ago

Yup that worked. Now the challenge is to work out how to get the network to work within Chromium, switching back to a crosh shell I can ping, but a standard browser window doesn't access the net.