Re: [Server-devel] eth1 problems
On Sun, 2009-10-25 at 20:11 -0700, Alex Kleider wrote: > I'd be grateful if someone on the list could help me set up an XS > using a > desktop. > > For reasons I can not understand, the eth1 is not recognized > although research suggests that the correct driver is there. > ie dmesg output includes > skge eth1: addr 00:26:5a:05:ac:31 > ... > bonding: lanbond0 is being created.. > ADDRCONF(NETDEV_UP): lanbond0: link is not ready > > during boot up the following flashes by: > Bringing up interface lanbond0: Device eth1 does not seem to be > present. > That would be normal if you have only one nic. How many nics are installed in this machine? Did you edit any config files? > On the same computer, if I use an Ubuntu live CD > with eth1 connected to my home network, it picks up an IP address > without any difficulty. Its mac is 00:26:5a:ac:31. If your looking to just get internet access to XS have a look at README.networking in /usr/share/doc/xs-config-*/ The *bond interfaces that are shown with "ip addr" are just holders for the ip addresses that the default XS layout would use. This allows a cleaner DHCP server installation, where the internal interfaces that dhcp is bound to don't need to be present at boot. If eth1 is present it should be added to lanbond0. With your saying "it picks up an IP address", that suggests that your home network has a dhcp server on it already. If eth0 were to be plugged in to your home network, you should get a dhcp address on eth0. The XS layout assumes that eth0 will be the interface that would have the default gateway to the internet, and would be providing XS services, including dhcp, to whatever is connected to the *bond interfaces. In a terminal window what is the output of "ip addr"? Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] eth1 problems
I'd be grateful if someone on the list could help me set up an XS using a desktop. For reasons I can not understand, the eth1 is not recognized although research suggests that the correct driver is there. ie dmesg output includes skge eth1: addr 00:26:5a:05:ac:31 ... bonding: lanbond0 is being created.. ADDRCONF(NETDEV_UP): lanbond0: link is not ready during boot up the following flashes by: Bringing up interface lanbond0: Device eth1 does not seem to be present. On the same computer, if I use an Ubuntu live CD with eth1 connected to my home network, it picks up an IP address without any difficulty. Its mac is 00:26:5a:ac:31. Any help would be appreciated. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Early F11 XS build
On Sun, 2009-10-25 at 12:44 +0100, Martin Langhoff wrote: > On Sat, Oct 24, 2009 at 9:51 AM, Peter Robinson wrote: > >> -- the vanilla F11 kernels fail to boot on the XO -- expected? > > > > I think it should boot but I don't think the boot.fth is created but > > its been a while since I've got around to trying it on my XO. > Is this with anaconda or with your XO image? I've booted F11's anaconda that was released on the dvd in my prior testing. > boot.fth is created from the kickstart file. The missing thing are the > symlinks (vmlinuz, initrd) but I've created those ok. The initrd is > clearly unpacked and exec'd but t never completes booting. > > If it's expected to work, I can work on tracing WTH is going on. If > it's known not to work for hard-to-fix reasons, well... Around Aug 5 I created an XS iso that is bootable on the XO, uname returns 2.6.29.6-213.fc11.i386 from tty2 in the installer. > >> - However, that means that making a bootable usb is harder for users. > > > > What causes it to be harder to make a bootable usb? > > To clarify -- a bootable installer. Making a bootable installer from a > Fedora DVD involves downloading the netinst iso separately and copying > it into the USB disk. > No, you just need files from /isolinux & /images on the dvd or disc1... Doesn't mkusbinstall work anymore? Well there is one thing that should be updated for F11, to avoid confusing anaconda over method/repo/stage2. Edit the sed replacement line replacing method= with repo=, the inner workings are slightly different between F9 and F11. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] PolicyKit dependency chain for headless machines
On Sun, Oct 25, 2009 at 13:07, Daniel Drake wrote: > 2009/10/23 Martin Langhoff : >> Working on the OLPC XS rebase to F11 -- I end up with random bits of >> gnome and kde, brought in by PolicyKit, which wants a >> PolicyKit-authentication-agent. >> >> Yum only seems to know of KDE and Gnome authentication-agents. >> >> How does PK handle users logging in in a VT? What is the >> authentication agent there? > > The authentication agent is used only when a specific application > requests an operation which the local authority has marked as > requiring authorization. It is not used when logging in. I don't know > of any command line applications that make policykit requests, and I > don't know of any commandline authentication agents. pkcon is a command line tool to install/update/remove packages with PackageKit. It uses PolicyKit, and thus might use some authentication agent. No idea how it does that though. -- Mathieu Bridon (bochecha) ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] PolicyKit dependency chain for headless machines
2009/10/23 Martin Langhoff : > Working on the OLPC XS rebase to F11 -- I end up with random bits of > gnome and kde, brought in by PolicyKit, which wants a > PolicyKit-authentication-agent. > > Yum only seems to know of KDE and Gnome authentication-agents. > > How does PK handle users logging in in a VT? What is the > authentication agent there? The authentication agent is used only when a specific application requests an operation which the local authority has marked as requiring authorization. It is not used when logging in. I don't know of any command line applications that make policykit requests, and I don't know of any commandline authentication agents. Daniel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Early F11 XS build
On Sat, Oct 24, 2009 at 9:51 AM, Peter Robinson wrote: >> -- the vanilla F11 kernels fail to boot on the XO -- expected? > > I think it should boot but I don't think the boot.fth is created but > its been a while since I've got around to trying it on my XO. boot.fth is created from the kickstart file. The missing thing are the symlinks (vmlinuz, initrd) but I've created those ok. The initrd is clearly unpacked and exec'd but t never completes booting. If it's expected to work, I can work on tracing WTH is going on. If it's known not to work for hard-to-fix reasons, well... >> - However, that means that making a bootable usb is harder for users. > > What causes it to be harder to make a bootable usb? To clarify -- a bootable installer. Making a bootable installer from a Fedora DVD involves downloading the netinst iso separately and copying it into the USB disk. >> - Dependency chains are slimmer... but some are still bizarre. Bits >> of kde and gnome are there. > > At a guess this is probably due to PolicyKit. I've had issues with it > in the past. Yes, PK is the main culprit. Posted to fedora-olpc on this topic yesterday... m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
