Problems Installing Jaunty On NSLU2

Attached is an abstract from the end of the Syslog during Installation about the problems showing up in the log file.

Managed to get almost the full syslog, but this is from earlier during the install

Another Syslog file from another attempted install with NTFS errors hopefully gone

I have been choosing the same menu options when asked questions as follows:-

Encrypt Home Directory - Yes
Modules Added For Setup - Non
Enabled All Repository's When Asked about the different ones.
Chosen Yes for UTC near very end of install.
4 Partitions created:- (All in ext3 format)
 250mb /boot
 10gb /home
 20gb /
 750mb swap

The comments/log file here https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/336770/comments/2 I actually got a screen at the end of installation saying it hasd been completed and my NSLU2 rebooted but went back into installer mode.
After loooking at the Syslog I spoted some errors linked to an NTFS partition on my USB HDD which I haev since resolved and a newer log has been posted of my latest install attempt here https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/336770/comments/3 .
The last install is a typical install I get as far as tge UTC Clock option at the end and then my SSH connection gets dropped, but my NSLU2 does not reboot.

The Log file from https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/336770/comments/1 is the end of the log file from the file in the coments here https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/336770/comments/2

Attached is my syslog from another attempt to install tonight with the latest debian intaller dated 4th March, also 2 dmesg dumps one during and one at the end.

This netboot installer here http://ftp.debian.org/debian/dists/lenny/main/installer-armel/current/images/ixp4xx/netboot/di-nslu2.bin for debian 5 causes my NSLU2 to not boot into installer.

But the one from here installs fine http://www.slug-firmware.net/d-click.php?p=download%2Fdebian%2Fnslu2&f=debian-armel-5.0.zip&l=d-license.txt&k=0ed7226999470369e7c31687f59b63c8

Does this help at all

flash-kernel-installer needs to be moved to main.

Attached is my Syslog and dmesg dump from me successfully installing Debian 5 on my NSLU2 if this is any use/help.

Same problem here; same menu option "Continue without bootloader" was my only choice.

From what I can tell, I have a valid install on my target drive, but the NSLU2 itself still keeps booting to installer.

I've tried upslug'ing it to other images, but can't get it to boot from the drive.

It looks like with the addition of this https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/339947 bug report which was raised & got a Fix Comitted yesterday, it should be fixed by the time Jaunty Alpha 6 is released this Thursday.

I am not sure if a new di-nslu.bin is required for the installer or if we can jsut re-run the installer again after it has got changed.

I will be trying it again in a couple of days when Aplha 6 is due, when fingers crossed this should be sorted.

Andy

it should (hopefully) be fixed with the 20081029ubuntu24 build of debian installer, as soon as it shows up at:
http://ports.ubuntu.com/dists/jaunty/main/installer-armel/
feel free to try it out ...

Tried with current installer ubuntu23 & flash-kernel which was picked up by di-nslu2.bin but still had problems.

See syslog attached for various errors.

Same problem at end does not get to UTC time selection before finish of instillation

Flash did write to nslu2 through so things are moving in the correct direction slowly.

could get to a ssh login prompt but did not let me login. Just got disconnected.

Oliver

Has there been any news with the debian-installer for this as looking at this it failed to build https://launchpad.net/ubuntu/+source/debian-installer/20081029ubuntu24/+build/900470

Thanks

Andrew

DOwnloaded 20081029ubuntu25 di-nslu2.bin last night, and 5 hours later iam glad to report I have not got Januty installed onto my NSLU2.

Thanks for fixing this bug.

Sorry to piggyback, but this seems to encompass the overall get-ubuntu-on-NSLU2 effort.

I've run into an issue where I can get root permissions because 1) my user isn't able to sudo (not in the 'admin' group) and 2) I had set the option to allow root login (or something like that), but never was asked for a password to set on the root account. I think my choice for #2 led to not being added to 'admin' that I'm running into in #1.

I'll hookup the HD to my linux box and edit the file system to get past this, but just reporting the issue.

woops, that should say "I've run into an issue where I *can't* get root permissions..."

Not successful on me. The installer eats too much RAM. Anyone with Fat Slug please confirm this

worked fine for me with a recent daily on a std slug, did you make sure to pick swap on the target device during partitioning (else it will indeed stop right after this step, swap is essential) ?

I agree, swap is essential. Please go to shell before start the installation and swapon the swap partition. I assume you created the partitions first on your desktop.

I just installed my slug with Jaunty. I invite you guys to NSLU2 user group so we can our experience there. https://launchpad.net/~ubuntu-nslu2-users

note that we kept the kernel small enough on the nslu2 to finish the partitioning (if it doesnt, thats indeed a bug). if you select to create swapspace in the partitioning step the installer will immediately use it after it created it. so going to the shell should not be necessary.

Yesterday I install [http://ports.ubuntu.com/ubuntu-ports/dists/jaunty/main/installer-armel/current/images/ixp4xx/netboot/di-nslu2.bin] (I supose it correspoding to http://ports.ubuntu.com/ubuntu-ports/dists/jaunty/main/installer-armel/20081029ubuntu33/images/ixp4xx/netboot/ ) in my slug with sucess.

But now I can't run sudo:
$ sudo -s
[sudo] password for xan:
xan is not in the sudoers file. This incident will be reported.

I don't know how to put log files of NSLU2 there. I just want to run reportbug in the slug but there isn't. So I report here.
I think the bug is that the user created in d-i is not pass as sudoers.

Is it another bug or I can report in this bug?

Thanks a lot,
Xan.