Re: Unknown boot options
On Sun, 2009-08-30 at 12:44 +0400, Paul Fertser wrote: > David Fokkema writes: > >> Qi reads factory partition to make ethernet gadget use fixed > >> predefined MAC address. If g_ether is statically compiled in there's > >> no way to set MAC address other than supplying it through the kernel > >> command line. If g_ether is a module, the recent modprobe will look at > >> the kernel command line and load the module with corresponding > >> parameters. > >> > >> I guess Qi should support both modular and compiled in g_ether, hence > >> it has use the kernel command line. > >> > >> To sum up, i don't know the answer how to hide those messages but at > >> least now you know why they appear. :) > > > > So... either the FR kernels might include g_ether statically > > compiled or > > Isn't really a solution because most users might want to use another > usb gadget by rmmoding g_ether. Probably unbinding will work too, > needs checking, in this case we can compile g_ether statically but > it'd still be a bad surprise for users who are not used to that. Ah, I see. So it must be a module, then. > > someone might fix the 'unknown command line' logger to be silent on > > 'g_ether' warnings? > > I can't see how that is possible. That's a shame... I really dislike the warnings as well... David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unknown boot options
David Fokkema writes: >> Qi reads factory partition to make ethernet gadget use fixed >> predefined MAC address. If g_ether is statically compiled in there's >> no way to set MAC address other than supplying it through the kernel >> command line. If g_ether is a module, the recent modprobe will look at >> the kernel command line and load the module with corresponding >> parameters. >> >> I guess Qi should support both modular and compiled in g_ether, hence >> it has use the kernel command line. >> >> To sum up, i don't know the answer how to hide those messages but at >> least now you know why they appear. :) > > So... either the FR kernels might include g_ether statically > compiled or Isn't really a solution because most users might want to use another usb gadget by rmmoding g_ether. Probably unbinding will work too, needs checking, in this case we can compile g_ether statically but it'd still be a bad surprise for users who are not used to that. > someone might fix the 'unknown command line' logger to be silent on > 'g_ether' warnings? I can't see how that is possible. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unknown boot options
On Thu, 2009-08-27 at 11:30 +0400, Paul Fertser wrote: > Leonti Bielski writes: > > Unknown boot option 'g_ether.dev_addr=MAC' 4 times in a row. > > > > It does not affect anything but I hate to see error messages when my > > loglevel=1 quiet and my device is perfectly fine. > > It happens to me every time using Qi and I don't know how to make it > > stop. > > Qi reads factory partition to make ethernet gadget use fixed > predefined MAC address. If g_ether is statically compiled in there's > no way to set MAC address other than supplying it through the kernel > command line. If g_ether is a module, the recent modprobe will look at > the kernel command line and load the module with corresponding > parameters. > > I guess Qi should support both modular and compiled in g_ether, hence > it has use the kernel command line. > > To sum up, i don't know the answer how to hide those messages but at > least now you know why they appear. :) So... either the FR kernels might include g_ether statically compiled or someone might fix the 'unknown command line' logger to be silent on 'g_ether' warnings? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unknown boot options
Leonti Bielski writes: > Unknown boot option 'g_ether.dev_addr=MAC' 4 times in a row. > > It does not affect anything but I hate to see error messages when my > loglevel=1 quiet and my device is perfectly fine. > It happens to me every time using Qi and I don't know how to make it > stop. Qi reads factory partition to make ethernet gadget use fixed predefined MAC address. If g_ether is statically compiled in there's no way to set MAC address other than supplying it through the kernel command line. If g_ether is a module, the recent modprobe will look at the kernel command line and load the module with corresponding parameters. I guess Qi should support both modular and compiled in g_ether, hence it has use the kernel command line. To sum up, i don't know the answer how to hide those messages but at least now you know why they appear. :) -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Unknown boot options
Hello! I'm using latest Qi with latest SHR-U. This problem bothers me for a long time but just now I decided to find out what seems to be the root of it. Every time I boot my device I see kernel message stating: Unknown boot option 'g_ether.dev_addr=MAC' 4 times in a row. It does not affect anything but I hate to see error messages when my loglevel=1 quiet and my device is perfectly fine. It happens to me every time using Qi and I don't know how to make it stop. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
