next »

[JoeMac]

The GUI-based system administration tools included in the xubuntu-desktop package turned out to be completely unuseable with Hardy and xfce.  I think there is some sort of bug in the policykit-gnome package that these tools depend on for authentication, so even though I can open the individual tools like System -- Users and Groups, when I click Unlock I wind up with the following error:
Could not authenticate
An unexpected error has occurred.
I have Googled the bug. It appears to be relatively common and there does not seem to be a fix that works as far as I can tell, so I would recommend holding off on installing this package.  It's really a shame this package doesn't work, because it really  extends the range of system administration tools available within xfce. 

[trailboss]

The GUI-based system administration tools included in the xubuntu-desktop package turned out to be completely unuseable with Hardy and xfce.  I think there is some sort of bug in the policykit-gnome package that these tools depend on for authentication, so even though I can open the individual tools like System -- Users and Groups, when I click Unlock I wind up with the following error:
Could not authenticate
An unexpected error has occurred.
I have Googled the bug. It appears to be relatively common and there does not seem to be a fix that works as far as I can tell, so I would recommend holding off on installing this package.  It's really a shame this package doesn't work, because it really  extends the range of system administration tools available within xfce. 

This sounds like a similar problem I had when I installed the core Gnome desktop. (Yes it will run fine on the XO if you have a 4 G SD card)

Try this

go to         /etc/PolicyKit/PolicyKit.conf

it will probably look something like this

<match user="root">
  <return result="yes"/>
</match>

change it to

<match user="root | olpc">
  <return result="yes"/>
</match>

the olpc entry will only work if you haven't changed the default user name from Teapots original setup. If you changed the user name then substitue your current user name. This should give you complete authority to use the administrative tools.

Hope this helps.

[teapot]

The GUI-based system administration tools included in the xubuntu-desktop package turned out to be completely unuseable with Hardy and xfce.  I think there is some sort of bug in the policykit-gnome package that these tools depend on for authentication, so even though I can open the individual tools like System -- Users and Groups, when I click Unlock I wind up with the following error:
Could not authenticate
An unexpected error has occurred.
I have Googled the bug. It appears to be relatively common and there does not seem to be a fix that works as far as I can tell, so I would recommend holding off on installing this package.  It's really a shame this package doesn't work, because it really  extends the range of system administration tools available within xfce. 

It's not a bug -- I have explained how to grant user access to this here.

[JoeMac]

Teapot & Trailboss,

The first thing I did before going into "Users and Groups" was following teapot's instructions for adding olpc to the admin group.  No joy.  Trailboss's edit of PolicyKit.conf did the trick, though.

Nearly everything works;)  Oddly, I can log into xfce as olpc and when starting "Users and Groups" I can now authenticate using my olpc password, but the only users that appear in the user list are root and a user account that I added using the "Users and Groups" GUI.  olpc doesn't show up as a user anywhere in the GUI, but does show up as a group.  Odd, particularly since the authentication for this application now clearly recognizes olpc as an adminstrative user.  Other than that , everything else appears to work fine now.  Thanks for the help 

[JoeMac]

I found another nice feature in the xubuntu-desktop package: rudimentary power management.  It senses when the charger is unplugged and dims the screen automatically

[teapot]

I guess, "admin"group appears in policykit configuration only after some particular set of packages is installed. My /etc/PolicyKit/PolicyKit.conf has "admin" group defined even though the group itself was not created:

Code:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="admin"/>
</config>

"olpc" user is not shown in the GUI because his userid is less than 1000 -- I had to use the same userid as in the original OLPC configuration, so files in NAND flash owned by olpc in Fedora are still owned by olpc in Ubuntu.

[MarkS]

Hello!

I have the Gutsy  of ubuntu installed on the OLPC on a thumb drive. That version doesn't have ndiswrapper installed. There is a ndiswrapper.ko module in the system in its own /lib/modules/<version> directory, but apparently not in the module load path. When I try to force it to install, it thinks it has a version conflict with the kernel. This may be part of a known Debian broken distribution.

So I download a kernel, apply the configuration file. and compile the latest ndiswrapper from sourceforge. Probably I need to do something differently, since it still thinks there is a versioning conflict. When I force it via modprobe, it works briefly but then everything USB starts misbehaving -- including taking the thumb drive off line!

So my questions are:

(1) Will the latest (Hardy) version load the  ndiswrapper module cleanly?

(2) If not, where can I get the exact source code for either the Hardy  or (preferably) the  Gutsy ubuntu OLPC kernel? So that I can compile an exact match module?

(3) When compiling the ndiswrapper module, I got the warning:
     "This kernel uses 4k stack size option...many windows drivers
       will not work with this option"

Is the CONFIG_4KSTACKS option something I can safely play with, or is it something the GEODE processor needs?

Thanks!
Mark

[teapot]

(1) Will the latest (Hardy) version load the  ndiswrapper module cleanly?

(2) If not, where can I get the exact source code for either the Hardy  or (preferably) the  Gutsy ubuntu OLPC kernel? So that I can compile an exact match module?

(3) When compiling the ndiswrapper module, I got the warning:
     "This kernel uses 4k stack size option...many windows drivers
       will not work with this option"

Is the CONFIG_4KSTACKS option something I can safely play with, or is it something the GEODE processor needs?

The kernel that actually loads (copied from OLPC distribution) does not include ndiswrapper. Kernel that comes with Ubuntu is only installed to keep all dependencies satisfied, so its ndiswrapper module does not work. To compile ndiswrapper you need kernel headers (or full sources) from OLPC distribution, and to change the stack size you have to recompile the kernel.

I don't understand, why anyone would want to use ndiswrapper on XO -- It would be a pretty bizarre kind of configuration. XO already has a natively supported wireless adapter, so the only way you might need ndiswrapper would be adding another one, that happens to have only Windows drivers. However if you want to turn XO into a wireless-to-wireless router, wifi scanner or any other imaginable dual-wireless host, it would make no sense to compromise its reliability with a non-native driver, so choosing a natively supported USB wireless adapter would be safer and easier. What are you trying to do that you need ndiswrapper?

[MarkS]

The kernel that actually loads (copied from OLPC distribution) does not include ndiswrapper. Kernel that comes with Ubuntu is only installed to keep all dependencies satisfied, so its ndiswrapper module does not work. To compile ndiswrapper you need kernel headers (or full sources) from OLPC distribution, and to change the stack size you have to recompile the kernel.

It would be really great if I could just use the headers. Unfortunately, the ndiswrapper source wants some other settings that apparently only happen when the source gets built.

From what you're saying, it sounds like I can scrap all the ubuntu kernel source code I was using because its entirely the wrong kernel. Arrr...

I don't understand, why anyone would want to use ndiswrapper on XO -- It would be a pretty bizarre kind of configuration. XO already has a natively supported wireless adapter, so the only way you might need ndiswrapper would be adding another one, that happens to have only Windows drivers.

I'm hoping to boost the range by adding a usb adapter with 10db directional antenna. Just being able to put the antenna up high should be a help in some situations. If there was a way to plug in an external antenna, that might work, but I don't see that capability in the OLPC feature set.

...so choosing a natively supported USB wireless adapter would be safer and easier. What are you trying to do that you need ndiswrapper?

What USB wireless adapter's are supported natively?

I chose the one I'm working with because it was on sale for $15 -- $30 less than usual. I'm not seeing a lot of choice out there, with other adapters selling for $80 or more.

Thanks --
Mark

[teapot]

It would be really great if I could just use the headers. Unfortunately, the ndiswrapper source wants some other settings that apparently only happen when the source gets built.

From what you're saying, it sounds like I can scrap all the ubuntu kernel source code I was using because its entirely the wrong kernel. Arrr...

Yes, you need kernel source that OLPC uses for its builds. moocapiean posted build instructions at http://olpcnews.com/forum/index.php?topic=1436.msg20033#msg20033

I'm hoping to boost the range by adding a usb adapter with 10db directional antenna. Just being able to put the antenna up high should be a help in some situations. If there was a way to plug in an external antenna, that might work, but I don't see that capability in the OLPC feature set.

...so choosing a natively supported USB wireless adapter would be safer and easier. What are you trying to do that you need ndiswrapper?

What USB wireless adapter's are supported natively?

I chose the one I'm working with because it was on sale for $15 -- $30 less than usual. I'm not seeing a lot of choice out there, with other adapters selling for $80 or more.

The usual rule is, anything wireless made with Broadcom chipsets except WRT54G is Windows-only. There is a very large list of wireless chipsets and drivers at http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ , though it usually takes some googling to map particular products to chipsets.

I use Zydas ZD1211-based ZyXEL G220, full list of the devices supported by the same driver is here (some links are broken, however model names can be found at manufacturers' and retailers' sites). Apparently some devices in that list are pretty cheap, and small enough to be placed inside the antenna, and some have large built-in antennas.

This reminds me that I have finally got my parabolic reflector that should work with ZyXEL G220 back from storage, and should do some long-range experiments.

[MarkS]

I use Zydas ZD1211-based ZyXEL G220, full list of the devices supported by the same driver is here (some links are broken, however model names can be found at manufacturers' and retailers' sites). Apparently some devices in that list are pretty cheap, and small enough to be placed inside the antenna, and some have large built-in antennas.

I'm using (based on the windows file names) zd1211bu. Possibly similar enough to the other zd1211 series files?

Are you using the chip you mentioned with the OLPC? If so, how? Scanning the drive I see firmware files under /lib/firmware/2.6.22-14 and kernel modules under /lib/modules/2.6.22-14-generic/... . But doing modprobe zd1211rw gets me a "module not found error" and doing a insmod on the zd1211rw.ko module gets me the versioning error.

So what would I do to get the zd1211 modules working? Compile my own OLPC kernel, but without excluding the wireless modules? Compile my own zd1211 driver and install it myself?

Thanks!
Mark

[teapot]

I'm using (based on the windows file names) zd1211bu. Possibly similar enough to the other zd1211 series files?

Likely so.

Are you using the chip you mentioned with the OLPC? If so, how?

I use it with a regular laptop -- Averatec 2250. When I am connected to a T-Mobile hotspot, I can only use my account from one device at a time, so to connect two laptops I use ZD1211 USB adapter to talk to hotspot's access point and built-in Ralink adapter to talk to XO, providing routing between those interfaces.

Scanning the drive I see firmware files under /lib/firmware/2.6.22-14 and kernel modules under /lib/modules/2.6.22-14-generic/... . But doing modprobe zd1211rw gets me a "module not found error" and doing a insmod on the zd1211rw.ko module gets me the versioning error.

Ubuntu kernel (2.6.24-17-generic if you have it updated, earlier version otherwise) won't work -- it's configured for a regular PC hardware and boot process. Its modules won't work with OLPC kernel, either.

So what would I do to get the zd1211 modules working? Compile my own OLPC kernel, but without excluding the wireless modules? Compile my own zd1211 driver and install it myself?

I will post the result after I'll build the kernel and modules (moocapiean pretty much covered the whole procedure except for the package management integration). Currently I am running kernel and all modules from OLPC binaries, so zd1211rw driver is not installed.

[MarkS]

Well, I think I'm about ready to collapse.

I set up the source code for the kernel (2.6.22-20071121.7.olpc...). I set up the wireless drivers. I compiled the wireless modules. I got them into the module library (somewhat by hand) and depmod'd. Then I tried to load the module zd1211rw ... and got a series of broken dependencies.

When I scanned through the source code (c and h) for both the kernel and for the new drivers, I could not find the definition of

  static inline int netif_subqueue_stopped(...)

Before this I didn't realize it was possible to compile a ko with a missing symbol, so I guess this has been a learning experience.

I think the new wireless drivers may expect this symbol (and several others) to be available in the kernel code, even though the documentation said that 2.6.22 was OK. I also suspect that the missing symbol is in file /include/linux/netdevice.h

Could someone with the Hardy kernel source available look and see if the missing symbol is indeed defined there?

If it is, then I suppose I'll have to decide if its worth it to upgrade the kernel, wait for the wireless guru's to patch their compatibility code, or just forget the whole idea.

Thanks!
Mark 

[teapot]

Well, I think I'm about ready to collapse.

I set up the source code for the kernel (2.6.22-20071121.7.olpc...). I set up the wireless drivers. I compiled the wireless modules. I got them into the module library (somewhat by hand) and depmod'd. Then I tried to load the module zd1211rw ... and got a series of broken dependencies.

When I scanned through the source code (c and h) for both the kernel and for the new drivers, I could not find the definition of

  static inline int netif_subqueue_stopped(...)

It's an inline function, its whole body is in netdevice.h

Before this I didn't realize it was possible to compile a ko with a missing symbol, so I guess this has been a learning experience.

Actually most of symbols are "missing" in .ko files -- they are an equivalent of dynamic libraries.

After running depmod you should be able to run modprobe zd1211rw , and it will load the module plus all modules it depends on.

I think the new wireless drivers may expect this symbol (and several others) to be available in the kernel code, even though the documentation said that 2.6.22 was OK. I also suspect that the missing symbol is in file /include/linux/netdevice.h

Could someone with the Hardy kernel source available look and see if the missing symbol is indeed defined there?

If it is, then I suppose I'll have to decide if its worth it to upgrade the kernel, wait for the wireless guru's to patch their compatibility code, or just forget the whole idea.

It should not even be a "symbol" -- it's inline, so its invocation is converted into inline code while compiling, and it's static, so it is not exported to be visible in other files.

I am going to compile the latest stable kernel with this module (I want to test my adapter on XO, too) and post the binaries.

[MarkS]

When I scanned through the source code (c and h) for both the kernel and for the new drivers, I could not find the definition of

  static inline int netif_subqueue_stopped(...)

It's an inline function, its whole body is in netdevice.h

Except that its not. Its not in netdevice.h in the olpc 2.6.22 source code. Which suggests that there is a backward compatibility issue.

After running depmod you should be able to run modprobe zd1211rw , and it will load the module plus all modules it depends on.

But it doesn't -- because it can't find netif_subqueue_stopped, which then starts a cascade.

It should not even be a "symbol" -- it's inline, so its invocation is converted into inline code while compiling, and it's static, so it is not exported to be visible in other files.

Just using the terminology that modprobe uses. The modprobe utility thinks its looking for a "Unknown symbol in module, or unknown parameter (see dmesg)" and then dmesg says:

  mac80211: Unknown symbol netif_subqueue_stopped
  zd1211rw: Unknown symbol ieee80211_free_hw
   ... (whole bunch of symbols starting with ieee80211) ...

If I compile a new OLPC/ubuntu kernel, will other things break? Or will I be able to use it as is, just with a new kernel? It took a long time to tweak things (like font sizes on every application) and I really don't want to start over.

Thanks!
Mark