Loading ...
Sorry, an error occurred while loading the content.

Re: [nslu2-general] Re: Total Linux newbie question - Unslung seemed successful, but cant find ipkg

Expand Messages
  • Ludo
    Hi, Just: telnet into the device, rm /.unslung rm /.sd??root reboot where the ? can be a number. You ll see. Good luck, Ludo ... From: Mike Westerhof
    Message 1 of 13 , Feb 25, 2006
    • 0 Attachment
      Hi,

      Just:
      telnet into the device,

      rm /.unslung
      rm /.sd??root
      reboot

      where the ? can be a number. You'll see.

      Good luck,

      Ludo
      ----- Original Message -----
      From: "Mike Westerhof" <mwester@...>
      To: <nslu2-general@yahoogroups.com>
      Sent: Thursday, February 23, 2006 6:34 PM
      Subject: Re: [nslu2-general] Re: Total Linux newbie question - Unslung
      seemed successful, but cant find ipkg


      > Did you reflash your slug before you unslung to the new 512MB USB device?
      >
      > The "unsling" command is a one-time-use-only utility.
      >
      > Once you "unsling" to a device, flags are written to the slug's internal
      > flash disk to note that it will finish the boot from the external device.
      > A
      > side-effect of this flag is that subsequent attempt to use the "unsling"
      > command will create a partially-written device that cannot be booted.
      >
      > You can either remove the flags and reboot (search the mail list for
      > specifics) or just re-flash the slug with unslung again -- either way will
      > result in a slug that can be "unslung" again.
      >
      > Mike (mwester)
      >
      > ----- Original Message -----
      > From: "kdavis11_2" <kdavis11_2@...>
      > To: <nslu2-general@yahoogroups.com>
      > Sent: Monday, February 20, 2006 8:37 PM
      > Subject: [nslu2-general] Re: Total Linux newbie question - Unslung seemed
      > successful, but cant find ipkg
      >
      >
      >> I appear to have a similar problem. Attempted to unsling to 512 meg
      >> usb stick.(PNY Attache) Process appears to have gone fine, but it
      >> appears root is still on internal flash-
      >>
      >> # mount
      >> /dev/mtdblock4 on / type jffs2 (rw)
      >> /proc on /proc type proc (rw)
      >> usbdevfs on /proc/bus/usb type usbdevfs (rw)
      >> /dev/sda1 on /share/hdd/data type ext3 (rw)
      >> /dev/sda2 on /share/hdd/conf type ext3 (rw,sync)
      >> #
      >> # df
      >> Filesystem 1k-blocks Used Available Use% Mounted on
      >> rootfs 6528 5320 1208 81% /
      >> /dev/mtdblock4 6528 5320 1208 81% /
      >> /dev/sda1 298727 18270 277373 6% /share/hdd/data
      >> /dev/sda2 123923 4145 118499 3% /share/hdd/conf
      >>
      >> # cat /proc/mounts
      >> rootfs / rootfs rw 0 0
      >> /dev/root / jffs2 rw 0 0
      >> /proc /proc proc rw 0 0
      >> usbdevfs /proc/bus/usb usbdevfs rw 0 0
      >> /dev/sda1 /share/hdd/data ext3 rw 0 0
      >> /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0
      >>
      >> I followed instructions in the 5.5-beta readme, in fact I have a
      >> working 10 gig drive in an external drive enclosure, no problem with
      >> rootfs. My goal was to silence my slug.
      >>
      >> Any ideas?
      >>
      >>
      >> --- In nslu2-general@yahoogroups.com, <mwester@...> wrote:
      >> >
      >> > Just a quick scan through this email -
      >> >
      >> > a) The slug in question is booting from the internal flash, not
      >> the external USB device. That must be fixed in order to fix the
      >> ipkg problem. If you link the ipkg executable as suggest below, you
      >> will just fill up the internal flash.
      >> >
      >> > b) I see that you followed the arslinux instructions; those
      >> instructions are for unslung 4.x -- it's very likely that following
      >> those instructions for unslung 5.5 will get you into trouble. I
      >> would recommend that you start anew by reflashing the slug with the
      >> 5.5 firmware, and follow the install instructions for 5.5 instead!
      >> >
      >> > Mike (mwester)
      >> >
      >> > > --- In nslu2-general@yahoogroups.com, "Jelle Alten" <jpalten@>
      >> wrote:
      >> > > >
      >> > > > Hi Igngri,
      >> > > >
      >> > > >
      >> > > > Rumours are that your rootfs might be on the (internal) flash
      >> > > memory, which
      >> > > > is not good, and there shouldn't be any ipkg-ing before you
      >> fix it...
      >> > > > If so, please "upgrade" your 5.5 once again, which will
      >> reflash the
      >> > > internal
      >> > > > flash memory, and make sure you don't do anything before being
      >> properly
      >> > > > unslung on the usb stick, and rebooted.
      >> > > >
      >> > > > Mount should look something like this after that:
      >> > > > # mount
      >> > > > /dev/sda1 on /initrd type jffs2 (ro,noatime)
      >> > > > /dev/sda1 on / type ext3 (rw)
      >> > > > proc on /proc type proc (rw,nodiratime)
      >> > > >
      >> > > >
      >> > > > If it is properly setup: strange problem.
      >> > > > Can you confirm that the ipkg program is in /usr/bin/ipkg?
      >> (type "ls -al
      >> > > > /usr/bin" at the commandline, and scroll up to find it)
      >> > > > Can you check your path settings? (type "set" at the
      >> commandline)
      >> > > > What does "which ipkg" reply?
      >> > > > Do you have a /usr/sbin/ipkg-cl program as well?
      >> > > >
      >> > > > Are ipkg-cl and ipkg executables?
      >> > > > (they should look like "-rwxr-xr-x 1 root root 3372 Jan 1
      >> 1970
      >> > > ipkg-cl" )
      >> > > >
      >> > > > Maybe you could unslung again, see if it gets any better.
      >> > > > Or get into the #nslu2-general chatroom to get some online
      >> help, if you
      >> > > > didn't already.
      >> > > >
      >> > > > Good luck.
      >> > > >
      >> > > > Thanks go to caplink811_log for his tips here.
      >> > > >
      >> > > > Jelle
      >> > > >
      >> > > >
      >> > > > ---- from the chatroom ----
      >> > > > (23:56:04) jelle: cat you do a "which ipkg" for us?
      >> > > > (23:56:11) jelle: I'd like to help Igngri out a bit, in the
      >> mailing
      >> > > list.
      >> > > > (23:56:36) caplink811_log: [root@linus rc.d]$ which ipkg
      >> > > > (23:56:36) caplink811_log: /usr/bin/ipkg
      >> > > > (23:56:40) jelle: thanks.
      >> > > > (23:56:44) caplink811_log: no problem
      >> > > > (23:57:29) caplink811_log: which is a link to /usr/sbin/ipkg-cl
      >> > > > (23:57:39) caplink811_log: lrwxrwxrwx 1 root root 16 Jun 13
      >> 12:52
      >> > > ipkg ->
      >> > > > /usr/bin/ipkg-cl
      >> > > > (23:57:39) caplink811_log: -rwxr-xr-x 1 root root 3372 Jan
      >> 1 1970
      >> > > ipkg-cl
      >> > > > (23:58:06) caplink811_log: if it isn't there, than something
      >> went
      >> > > wrong with
      >> > > > /sbin/unsling
      >> > > > (23:59:20) caplink811_log: normally ln -s /usr/bin/ipkg-
      >> cl /usr/bin/ipkg
      >> > > > shoudl resolv his problem
      >> > > > ---- end of chatroom ----
      >> > > >
      >> > > >
      >> > > > -----Oorspronkelijk bericht-----
      >> > > > Van: nslu2-general@yahoogroups.com
      >> > > [mailto:nslu2-general@yahoogroups.com]
      >> > > > Namens lgngri
      >> > > > Verzonden: dinsdag 29 november 2005 6:59
      >> > > > Aan: nslu2-general@yahoogroups.com
      >> > > > Onderwerp: [nslu2-general] Total Linux newbie question -
      >> Unslung seemed
      >> > > > successful, but cant find ipkg
      >> > > >
      >> > > > Upgraded 5.5 firmware successfully. Unsling onto 512MB flash
      >> drive
      >> > > formatted
      >> > > > in slug and connected to Disk1 port seemed OK to me. Tried to
      >> run
      >> > > ipkg list
      >> > > > (or any ipkg commands) - got "No such file or directory" back.
      >> > > >
      >> > > > To research what had happened I spent couple of days reading
      >> Wiki on
      >> > > > nslu2-linux.org as well as wiki.arslinux.com and messages in
      >> this
      >> > > group. I
      >> > > > found no situation similar to mine so any help is greatly
      >> appreciated.
      >> > > >
      >> > > > I was able to successfully change the password and copy the
      >> passwd
      >> > > file to
      >> > > > both /share/hdd/conf/passwd and /usr/local/passwd. I also
      >> added the
      >> > > > diversion script to start up the telnet. This one however
      >> seemed to
      >> > > be saved
      >> > > > in the slug's flash rather than disk (I proved it by booting
      >> without any
      >> > > > disks attached and telnetting into the slug without first
      >> enabling
      >> > > telnet
      >> > > > via web GUI).
      >> > > >
      >> > > > Version of Unslung I installed was 5.5 beta When installing,
      >> exactly
      >> > > > followed an steps from the manual here:
      >> > > > http://wiki.arslinux.com/Unslung_on_the_NSLU2
      >> > > >
      >> > > > Here are the outputs that I think may be useful in
      >> troubleshooting:
      >> > > >
      >> > > > # cat /proc/partitions
      >> > > > major minor #blocks name
      >> > > >
      >> > > > 8 0 500736 scsi/host1/bus0/target0/lun0/disc
      >> > > > 8 1 308481 scsi/host1/bus0/target0/lun0/part1
      >> > > > 8 2 127968 scsi/host1/bus0/target0/lun0/part2
      >> > > > 8 3 63984 scsi/host1/bus0/target0/lun0/part3
      >> > > >
      >> > > > # cat /proc/mounts
      >> > > > rootfs / rootfs rw 0 0
      >> > > > /dev/root / jffs2 rw 0 0
      >> > > > /proc /proc proc rw 0 0
      >> > > > usbdevfs /proc/bus/usb usbdevfs rw 0 0
      >> > > > /dev/sda1 /share/hdd/data ext3 rw 0 0
      >> > > > /dev/sda2 /share/hdd/conf ext3 rw,sync 0 0
      >> > > >
      >> > > > # df
      >> > > > Filesystem 1k-blocks Used Available Use%
      >> Mounted on
      >> > > > rootfs 6528 5320 1208 81% /
      >> > > > /dev/mtdblock4 6528 5320 1208 81% /
      >> > > > /dev/sda1 298727 18271 277372
      >> 6% /share/hdd/data
      >> > > > /dev/sda2 123923 4144 118500
      >> 3% /share/hdd/conf
      >> > > >
      >> > > > # mount
      >> > > > /dev/mtdblock4 on / type jffs2 (rw)
      >> > > > /proc on /proc type proc (rw)
      >> > > > usbdevfs on /proc/bus/usb type usbdevfs (rw)
      >> > > > /dev/sda1 on /share/hdd/data type ext3 (rw)
      >> > > > /dev/sda2 on /share/hdd/conf type ext3 (rw,sync)
      >> > > >
      >> > > > Again, I am totally new to Linux world, so please spare the
      >> harsh
      >> > > remarks.
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > >
      >> > > > Yahoo! Groups Links
      >> > > >I had the same problem mentioned here. Where it said no such
      >> file or
      >> > > directory when trying to use ipkg. This line from the chatroom
      >> > > session mentioned above fixed it for me and now i'm up and
      >> running.
      >> > > Thanks!
      >> > >
      >> > > ln -s /usr/bin/ipkg-cl /usr/bin/ipkg
      >> >
      >>
      >>
      >>
      >>
      >>
      >>
      >>
      >>
      >>
      >> SPONSORED LINKS Computer internet security Firmware development
      >> Computer
      > internet business
      >> Computer internet access Computer internet privacy securities
      > Computer internet help
      >>
      >>
      >> --------------------------------------------------------------------------
      > ------
      >> YAHOO! GROUPS LINKS
      >>
      >> a.. Visit your group "nslu2-general" on the web.
      >>
      >> b.. To unsubscribe from this group, send an email to:
      >> nslu2-general-unsubscribe@yahoogroups.com
      >>
      >> c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of
      > Service.
      >>
      >>
      >> --------------------------------------------------------------------------
      > ------
      >>
      >>
      >
      >
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.