Re: [gentoo-user] [OT] Flashing an old NOKIA 3310 with Linux?
On February 16, 2019 5:15:48 AM UTC, Andrew Savchenko wrote: >Hi! > >On Tue, 12 Feb 2019 18:59:06 +0100 tu...@posteo.de wrote: >> Hi, >> >> I got my hands on one of the well known NOKIA 3310 (2001...not the >new NOKIA 3310 >> ones) phones. It seems the previous seller has branded the phone with >> his own firmware and I want to reflash the original NOKIA firmware >> onto it again...if I have a true phone I want the "real true" >> phone...you know ... :) >> >> There are some flasher out therewhich are compatible to windows >> versions, which are long forgotten. >> >> As far as my investigations in this case :) has reached: The phone >> needs what they call it a "DCT-3 flasher". >> >> Does anyone has knowledge in handling this wonderful retro peace >> of technique this way and knows a linux compatible flasher for >> the firmware? > >If a flasher you have is for old windows, wine may be your friend. >Usually they have good support for emulating old win api. > >Best regards, >Andrew Savchenko Alternatively, run an old windows version inside virtualbox. Usb passthrough works really well. (Only time I actually use windows is for stuff that like that) -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
[gentoo-user] dracut and UUID's
Hi all, I have cloned a gentoo image for a raspberry pi to another sdcard. It fails to boot because the storage uuid's have changed and dracut has the previous uuid's stored internally. Is there a way around this without changing the new storage's uuids back to match the original (its bad practise to duplicate uuids) or using an original rpi kerneal and rebuild the custom one? BillK
Re: [gentoo-user] dracut and UUID's
On Sat, Feb 16, 2019 at 8:48 PM Bill Kenworthy wrote: > > I have cloned a gentoo image for a raspberry pi to another sdcard. > It fails to boot because the storage uuid's have changed and dracut has > the previous uuid's stored internally. Is there a way around this > without changing the new storage's uuids back to match the original (its > bad practise to duplicate uuids) or using an original rpi kerneal and > rebuild the custom one? Are you passing root=UUID=xyz on the command line? Also, do you have the correct UUID in /etc/fstab? Dracut does save a snapshot of fstab internally, but I think it should work if passed the UUID on the command line. You do want the real /etc/fstab to have the correct UUID, because after dracut mounts root it checks fstab and remounts root with any options in case its internal copy is stale. If the fstab on the hard drive is incorrect that could lead it astray. If it isn't breaking to a shell you can force it to with a command line option, and then from there just mount root yourself on /sysroot, and exit the shell, and then it should boot. Another option is to just use it as a rescue image and just mount root on /sysroot and then just chroot into it, and now you're basically at a semi-working system. You could easily rebuild dracut from there. Or you can just boot from a rescue disk and regenerate dracut. But, I suspect just editing your command line in grub will do the trick if /etc/fstab on the hard drive is good. -- Rich
Re: [gentoo-user] dracut and UUID's
On 17/2/19 10:08 am, Rich Freeman wrote: > On Sat, Feb 16, 2019 at 8:48 PM Bill Kenworthy wrote: >> I have cloned a gentoo image for a raspberry pi to another sdcard. >> It fails to boot because the storage uuid's have changed and dracut has >> the previous uuid's stored internally. Is there a way around this >> without changing the new storage's uuids back to match the original (its >> bad practise to duplicate uuids) or using an original rpi kerneal and >> rebuild the custom one? > Are you passing root=UUID=xyz on the command line? Also, do you have > the correct UUID in /etc/fstab? > > Dracut does save a snapshot of fstab internally, but I think it should > work if passed the UUID on the command line. You do want the real > /etc/fstab to have the correct UUID, because after dracut mounts root > it checks fstab and remounts root with any options in case its > internal copy is stale. If the fstab on the hard drive is incorrect > that could lead it astray. > > If it isn't breaking to a shell you can force it to with a command > line option, and then from there just mount root yourself on /sysroot, > and exit the shell, and then it should boot. Another option is to > just use it as a rescue image and just mount root on /sysroot and then > just chroot into it, and now you're basically at a semi-working > system. You could easily rebuild dracut from there. Or you can just > boot from a rescue disk and regenerate dracut. > > But, I suspect just editing your command line in grub will do the > trick if /etc/fstab on the hard drive is good. > Hi Rich, no grub! A rpi uses a custom loader (apparently the GPU starts the boot process). I'll investigate if it can passthrough a UUID. Looks like next stop is the pi forums, but most use their kernel, not a custom one. BillK
Re: [gentoo-user] dracut and UUID's
On Sat, Feb 16, 2019 at 9:24 PM Bill Kenworthy wrote: > > Hi Rich, no grub! A rpi uses a custom loader (apparently the GPU starts > the boot process). I'll investigate if it can passthrough a UUID. > Looks like next stop is the pi forums, but most use their kernel, not a > custom one. > Doh! Missed that it was a pi. https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md I believe that is just a FAT32 partition so you can edit it pretty trivially. -- Rich
