Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> Keep me posted please.

Assembled today and dd raspbian to the sd card. All worked fine.
I am under pressure now, so I don't know when I can try the NFS root and
debian.
>From the experience with RPi2 it is much easier to do nfs when testing.

But in general it is very nice piece of hardware. I am wondering if I can
replace my desktop with it. First impression is that video quality is not
the best.

I ordered Joy-It box with two active fans which came with 3 heat syncs. 3A
Power Supply with usb cable and a hdmi cable.

regards

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

David wrote:

> I didn't bother with the heatsinks that came with it. I just wanted a
> fan and some ventilation instead of a sealed little plastic oven.

Yes, a similar was ordered and arrived as well. I tend to plan all of this
in my head and usually it works so well, that I do not have to run to the
shop after. It simply kills the excitement. And imagine it is a Sunday -
you have to wait a whole day or may be longer if you can not find what you
need in the local IT shop and then complain like Gene :)

regards

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas D Dial]

On Tue, 2019-09-10 at 07:18 -0400, Gene Heskett wrote:
> On Monday 09 September 2019 23:06:27 Thomas D Dial wrote:
> 
> > On Mon, 2019-09-09 at 12:21 -0400, Gene Heskett wrote:
(unrelated material omitted)
> > > $PITA problem, raspian insists the first, usr 1000 is
> > > "pi".  Is there a foolproof way to convert that to "gene", or am I
> > > stuck
> > > logging into it as "pi"?
> >
> > I do not know if it is foolproof, but I would try
> >
> > usermod -l gene pi
> >
> > as root (or maybe with sudo; I am not sure that it would work while
> pi
> > is logged in, though).
> >
> > I have used it occasionally, and the only issue is with (mostly
> gnome-
> > related) dotfiles in the login directory that contain the old login
> as
> > a string and after the change need to have that replaced by the new
> > login. An unfortunate number of them are in sqlite files and unless
> > the details are important it probably is easiest to delete them and
> > start over.
> >
> That sounds like its fraught with all sorts of login cockups. 
> Inconvenient at best, so I'll probably skip it.

I would not expect it to be a significant on a fairly fresh install (for
instance, if you haven't used the GUI or, maybe, the web browser), where
those dotfiles are few and often empty.

My recollection was that files under .config were the most trouble, that
on a system where the renamed account had been used extensively and had
absolute paths containing the former username in various configuration
files.
 
Tom Dial.

> (more omissions)

> Question posted on their forum.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law
> respectable.
>  - Louis D. Brandeis
> Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Thursday 12 September 2019 08:16:57 David wrote:

> On Thu, 12 Sep 2019 at 16:14, deloptes  wrote:
> > My RPI4 arrived as well - need to pick up also power supply and
> > cables, which arrived too. Excited to see how it performs.
>
> I have one of the official cases as well but after setting eyes on it
> I never even bothered to try it,  due to the thermal issues.
> I use one of these instead, very happy with it:
> https://www.ebay.com.au/itm/GeeekPi-Raspberry-Pi-Acrylic-Case-with-Coo
>ling-Fan-Heatsinks-for-Raspberry-Pi-4/183870693770
>
> I didn't bother with the heatsinks that came with it. I just wanted a
> fan and some ventilation instead of a sealed little plastic oven.

I have a combo top/heat sink coming all fins on top. Since it will be 
mounted upside down and there is a fan under it, it should be ok. 
Turning it over puts the gpio pins in a straight line to the iface card, 
cable is only an inch long.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David]

On Thu, 12 Sep 2019 at 16:14, deloptes  wrote:

> My RPI4 arrived as well - need to pick up also power supply and cables,
> which arrived too. Excited to see how it performs.

I have one of the official cases as well but after setting eyes on it
I never even bothered to try it,  due to the thermal issues.
I use one of these instead, very happy with it:
https://www.ebay.com.au/itm/GeeekPi-Raspberry-Pi-Acrylic-Case-with-Cooling-Fan-Heatsinks-for-Raspberry-Pi-4/183870693770

I didn't bother with the heatsinks that came with it. I just wanted a
fan and some ventilation instead of a sealed little plastic oven.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Thursday 12 September 2019 02:14:06 deloptes wrote:

> Gene Heskett wrote:
> >> https://wiki.debian.org/RaspberryPiImages
> >> https://www.raspberrypi.org/documentation/installation/
> >
> > Potential timeline?
> >
> > Cheers, Gene Heskett
>
> My RPI4 arrived as well - need to pick up also power supply and
> cables, which arrived too. Excited to see how it performs.

My micro hdmi adapters and heat sink are still on a junk somewhere. 
Considering the troubles in Hong Kong, its probably going to be late.  I 
had a 5v, 5a in the spares box. I've seen activity in the led's like its 
booting, but video remains invisible. I don't think the $16 adapter I 
got from wallies is any good.  I took the monitor to my pi-3b and it 
worked ok there.  So I wait.

Trying to build a fully preemptable kernel for raspian buster 1.1 on the 
pi-3b, but the raspian forum isn't co-operating. video on buster 1.1 is 
around 20x faster, and with a realtime kernel, it would run my big lathe 
very well. I have the src for that kernel, but as the pi-3b is a 
u-booter, no step by step howto that I have found. Debhelper isn't any 
help, demanding a debian/control file, all of which is pure unobtainium 
from raspian.

debian buster for arm isn't pi4 ready, no device tree for it yet. It does 
use grub to boot though, and that greatly simplifies installing a new 
kernel.  And I've already on site, a new hm2_rpspi.ko module that should 
talk to a mesa 7i90HD card, using the same spi interface the pi-3b is 
using.

Its possible raspian might beat debian to working release forthe 4.

Sitting on the proverbial park bench waiting for linux to catch up with 
new hardware sure is boring though. I feel like I'm running out of time. 
I go for a stress test at 9 tomorrow, Friday, and will likely be equipt 
with a new aortic valve before Friday in done. :-(  And I'll likely 
drive myself both ways.

Keep me posted please.

Thanks deloptes.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

>> https://wiki.debian.org/RaspberryPiImages
>> https://www.raspberrypi.org/documentation/installation/
> 
> Potential timeline?
> 
> Cheers, Gene Heskett

My RPI4 arrived as well - need to pick up also power supply and cables,
which arrived too. Excited to see how it performs.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 23:06:27 Thomas D Dial wrote:

> On Mon, 2019-09-09 at 12:21 -0400, Gene Heskett wrote:
> > On Monday 09 September 2019 11:50:12 ghe wrote:
> > > On 9/9/19 8:26 AM, Gene Heskett wrote:
> > > > On Monday 09 September 2019 08:58:10 Greg Wooledge wrote:
> > > >> On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
> > > >>> sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096
> > > >>> of=/dev/sdf1
> > > >>>
> > > >>> /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format
> > > >>> NTFS.
> > > >
> > > > That was one of /my/ screwups, fixed to /dev/sdf later. Now
> >
> > rapbian
> >
> > > > does something but only a magician knows what as I can't get any
> > > > video out of it.  The debian-arm net-installs still stop dead
> >
> > after
> >
> > > > one flash of the green led. Then I start finding rumors that
> > > > debian-arm isn't ready for pi4's, no device tree, and they
> > > > became
> >
> > a
> >
> > > > mob in a few hours.  So now I'm trying to get video out of
> >
> > raspbian,
> >
> > > > failing miserably. In the meantime I'm trying to put together
> > > > another working stretch on my pi3 so I can bring my lathe back
> > > > to life.
> > > >
> > > > I had it working before the heart attack, but have come to the
> > > > conclusion I may have over-wrote that card.  Damned hard to put
> > > > identifying marks on a card that physical size. They should have
> > > > something like a MAC address imprinted so that one could keep an
> > > > index list of what each card does.
> > >
> > > Label them with a Sharpie -- 1, 2, 3, 4... And make notes in a
> > > 'database' (aka 'a piece of paper and a pencil').
> > >
> > > > So I've given up on the pi4 till the heat sink cover and more of
> >
> > the
> >
> > > > micro to normal sized hdmi adapters arrive.
> > >
> > > Amazon. Single connector on both ends. Lots of choices, IIRC. Mine
> > > does good video with the ASUS VE228 monitor over on the table.
> > >
> > > There was a little backAndForth between the connectors to find the
> > > video, though, IIRC.
> > >
> > > > Might be a couple weeks
> > > > yet, coming from banggood.  All I have for that adapter now is
> >
> > some
> >
> > > > sort of a 3 headed contraption I paid $16 for at wallies, and
> > > > I've no clue if it works. I've never seen video come out of it.
> > > >
> > > > I even took the new 22" ONN monitor to the pi3 on the lathe,
> > > > makes
> >
> > a
> >
> > > > decent pix on the pi3 at just noticeably lower contrast.
> > > >
> > > > Cheers, Gene Heskett
> > >
> > > Try the Buster NOOBS from the RPi website.
> > >
> > > Painless and works good here -- eventually. I'm using a 32G
> > > Samsung
> >
> > SD
> >
> > > 'card'. And a USB3 external twirling rust disk.
> > >
> > > 4 is a little persnickety, and the RPi Buster Raspian has been
> >
> > futzed
> >
> > > with. Last I heard, the Debian ARM software wasn't ready for 4
> > > yet.
> >
> > That seems to be the general opinion, darnit.
> >
> > So lets go this way:
> > I'm building a RealtimePi buster-lite on the pi3 right now. Just one
> > $PITA problem, raspian insists the first, usr 1000 is
> > "pi".  Is there a foolproof way to convert that to "gene", or am I
> > stuck
> > logging into it as "pi"?
>
> I do not know if it is foolproof, but I would try
>
> usermod -l gene pi
>
> as root (or maybe with sudo; I am not sure that it would work while pi
> is logged in, though).
>
> I have used it occasionally, and the only issue is with (mostly gnome-
> related) dotfiles in the login directory that contain the old login as
> a string and after the change need to have that replaced by the new
> login. An unfortunate number of them are in sqlite files and unless
> the details are important it probably is easiest to delete them and
> start over.
>
That sounds like its fraught with all sorts of login cockups. 
Inconvenient at best, so I'll probably skip it.

> > debian-arm makes that easy by registering usr 1000 at install time,
> > so
> > the name is arbitrary. Secondary problem will be slow video, about
> > 1/20th speed of new stuff because its all framebuffer. But it runs
> > the
> > machine pretty good.  BTDT.
> >
> > I've copied some stuff to SSD that will make setting up the new
> > realtime
> > card a heck of a lot easier, like fstab and the hosts file, and I
> > have
> > already stashed all the linuxcnc configs and gcodes to an SSD that
> > will
> > be mounted after overwriting the fsatab and rebooting, including 10G
> > of
> > swap on an SSD. Might have to pull a new git of linuxcnc since my
> > local
> > copy is now a month old, and that will pull in a boatload of dev
> > stuff
> > as builddeb works, but thats expected. A pi3b is not that fast at
> > this
> > stuff, but at least with enough swap it doesn't OOM trying at build
> > the
> > rs-274-d interpreter, it just keeps on chugging along.
> >
> > Have I forgot something? Probably...

Last night, in surveying the u-sd chips I had, I found a later raspian 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas D Dial]

On Mon, 2019-09-09 at 12:21 -0400, Gene Heskett wrote:
> On Monday 09 September 2019 11:50:12 ghe wrote:
> 
> > On 9/9/19 8:26 AM, Gene Heskett wrote:
> > > On Monday 09 September 2019 08:58:10 Greg Wooledge wrote:
> > >> On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
> > >>> sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1
> > >>>
> > >>> /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format
> > >>> NTFS.
> > >
> > > That was one of /my/ screwups, fixed to /dev/sdf later. Now
> rapbian
> > > does something but only a magician knows what as I can't get any
> > > video out of it.  The debian-arm net-installs still stop dead
> after
> > > one flash of the green led. Then I start finding rumors that
> > > debian-arm isn't ready for pi4's, no device tree, and they became
> a
> > > mob in a few hours.  So now I'm trying to get video out of
> raspbian,
> > > failing miserably. In the meantime I'm trying to put together
> > > another working stretch on my pi3 so I can bring my lathe back to
> > > life.
> > >
> > > I had it working before the heart attack, but have come to the
> > > conclusion I may have over-wrote that card.  Damned hard to put
> > > identifying marks on a card that physical size. They should have
> > > something like a MAC address imprinted so that one could keep an
> > > index list of what each card does.
> >
> > Label them with a Sharpie -- 1, 2, 3, 4... And make notes in a
> > 'database' (aka 'a piece of paper and a pencil').
> >
> > > So I've given up on the pi4 till the heat sink cover and more of
> the
> > > micro to normal sized hdmi adapters arrive.
> >
> > Amazon. Single connector on both ends. Lots of choices, IIRC. Mine
> > does good video with the ASUS VE228 monitor over on the table.
> >
> > There was a little backAndForth between the connectors to find the
> > video, though, IIRC.
> >
> > > Might be a couple weeks
> > > yet, coming from banggood.  All I have for that adapter now is
> some
> > > sort of a 3 headed contraption I paid $16 for at wallies, and I've
> > > no clue if it works. I've never seen video come out of it.
> > >
> > > I even took the new 22" ONN monitor to the pi3 on the lathe, makes
> a
> > > decent pix on the pi3 at just noticeably lower contrast.
> > >
> > > Cheers, Gene Heskett
> >
> > Try the Buster NOOBS from the RPi website.
> >
> > Painless and works good here -- eventually. I'm using a 32G Samsung
> SD
> > 'card'. And a USB3 external twirling rust disk.
> >
> > 4 is a little persnickety, and the RPi Buster Raspian has been
> futzed
> > with. Last I heard, the Debian ARM software wasn't ready for 4 yet.
> 
> That seems to be the general opinion, darnit.
> 
> So lets go this way:
> I'm building a RealtimePi buster-lite on the pi3 right now. Just one 
> $PITA problem, raspian insists the first, usr 1000 is 
> "pi".  Is there a foolproof way to convert that to "gene", or am I
> stuck 
> logging into it as "pi"? 

I do not know if it is foolproof, but I would try

usermod -l gene pi

as root (or maybe with sudo; I am not sure that it would work while pi
is logged in, though).

I have used it occasionally, and the only issue is with (mostly gnome-
related) dotfiles in the login directory that contain the old login as a
string and after the change need to have that replaced by the new login.
An unfortunate number of them are in sqlite files and unless the details
are important it probably is easiest to delete them and start over.


> 
> debian-arm makes that easy by registering usr 1000 at install time,
> so 
> the name is arbitrary. Secondary problem will be slow video, about 
> 1/20th speed of new stuff because its all framebuffer. But it runs
> the 
> machine pretty good.  BTDT.
> 
> I've copied some stuff to SSD that will make setting up the new
> realtime 
> card a heck of a lot easier, like fstab and the hosts file, and I
> have 
> already stashed all the linuxcnc configs and gcodes to an SSD that
> will 
> be mounted after overwriting the fsatab and rebooting, including 10G
> of 
> swap on an SSD. Might have to pull a new git of linuxcnc since my
> local 
> copy is now a month old, and that will pull in a boatload of dev
> stuff 
> as builddeb works, but thats expected. A pi3b is not that fast at
> this 
> stuff, but at least with enough swap it doesn't OOM trying at build
> the 
> rs-274-d interpreter, it just keeps on chugging along.
> 
> Have I forgot something? Probably...
> 
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law
> respectable.
>  - Louis D. Brandeis
> Genes Web page 

- Tom Dial

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas D Dial]

On Mon, 2019-09-09 at 14:24 -0400, Gene Heskett wrote:
> On Monday 09 September 2019 13:58:03 Greg Wooledge wrote:
> 
> > On Mon, Sep 09, 2019 at 01:47:30PM -0400, Gene Heskett wrote:
> > > Tell that to pam. Even after editing sudoers, pam won't allow yoou
> > > to do squawt as sudo root. BTDT.
> >
> > If you have a serious complaint or question, you must provide
> details.
> 
> Also true, but those details are close to a year old, and my chances
> of 
> remembering it ala copy/paste accuracy are slim and none, so at this 
> late date, I'll not inflict my typo's on you.
> 
> > Your continued pattern of just ranting "it didn't work" for EVERY
> > issue you encounter makes it impossible to help you.
> >
> > In Debian, universal sudo access is granted to any user in the sudo
> > group.  If you want to be able to use sudo to run any command as any
> > user, add your user account to the sudo group.  Either by running
> > "adduser $LOGNAME sudo", or by editing the file with "vigr".
> 
> I should paint that on the wall. :) I've been trying by adding me to 
> sudoers, but that seems to not work as expected.
> 
> > Then, log out and back in to get your new group memberships.
> 
> A detail I forgot, my bad.
> >
> > If that doesn't work in Raspbian, well, too damned bad.  This is a
> > Debian mailing list.  All we know is Debian.
> 
> Touche` However, debian is in effect the broodstock for a lot of
> these 
> variations, so what works for debian has a middling high chance of 
> working with the *pians.
> 
> > > > For safety, you should use "vipw", "vipw -s" and "vigr" to
> perform
> > > > those edits, but it's not actually required on Debian.
> > >
> > > Screwed up already, I used vipw to put me in front of pi, but now
> it
> > > wants genes passwd, which has not been set. So I'll have to bring
> > > that chip to a reader and edit it.
> > >
> > > Is there an order to make all this just work? But I'll have to
> wait
> > > till realtimepi is done. Estimated another couple hours.
> >
> > If you duplicate the lines in both /etc/passwd AND /etc/shadow, your
> > password for "gene" will be the same as the password for "pi". 
> > Because they both use the same salted hash in the shadow file.  You
> > know, the big-ass $1$abcdefgh$crapola string that you saw when you
> > edited the file? It's kinda hard to miss.
> 
> Yup, big sore thumb. But I'll have to fix it in a card reader now. 

You might try (from the pi account):

sudo -l
  (or)
sudo bash --login
passwd

I just did it on a brand new fresh raspbian-buster-lite; it worked fine
and let me su - (with the newly established password) and presumably
would let me log in directly. The approach is a bit old-school and
eventually I will set the image up to allow ssh as the only network
access, ssh to root from the local host only, and no passwords allowed,
as on other systems here.

> When 
> RealtimePi has finished. 
> 
> Thanks Greg.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law
> respectable.
>  - Louis D. Brandeis
> Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 14:24:50 Gene Heskett wrote:

> On Monday 09 September 2019 13:58:03 Greg Wooledge wrote:
> > On Mon, Sep 09, 2019 at 01:47:30PM -0400, Gene Heskett wrote:
> > > Tell that to pam. Even after editing sudoers, pam won't allow yoou
> > > to do squawt as sudo root. BTDT.
> >
> > If you have a serious complaint or question, you must provide
> > details.
>
> Also true, but those details are close to a year old, and my chances
> of remembering it ala copy/paste accuracy are slim and none, so at
> this late date, I'll not inflict my typo's on you.
>
> > Your continued pattern of just ranting "it didn't work" for EVERY
> > issue you encounter makes it impossible to help you.
> >
> > In Debian, universal sudo access is granted to any user in the sudo
> > group.  If you want to be able to use sudo to run any command as any
> > user, add your user account to the sudo group.  Either by running
> > "adduser $LOGNAME sudo", or by editing the file with "vigr".
>
> I should paint that on the wall. :) I've been trying by adding me to
> sudoers, but that seems to not work as expected.
>
> > Then, log out and back in to get your new group memberships.
>
> A detail I forgot, my bad.
>
> > If that doesn't work in Raspbian, well, too damned bad.  This is a
> > Debian mailing list.  All we know is Debian.
>
> Touche` However, debian is in effect the broodstock for a lot of these
> variations, so what works for debian has a middling high chance of
> working with the *pians.
>
> > > > For safety, you should use "vipw", "vipw -s" and "vigr" to
> > > > perform those edits, but it's not actually required on Debian.
> > >
> > > Screwed up already, I used vipw to put me in front of pi, but now
> > > it wants genes passwd, which has not been set. So I'll have to
> > > bring that chip to a reader and edit it.
> > >
> > > Is there an order to make all this just work? But I'll have to
> > > wait till realtimepi is done. Estimated another couple hours.
> >
> > If you duplicate the lines in both /etc/passwd AND /etc/shadow, your
> > password for "gene" will be the same as the password for "pi".
> > Because they both use the same salted hash in the shadow file.  You
> > know, the big-ass $1$abcdefgh$crapola string that you saw when you
> > edited the file? It's kinda hard to miss.
>
> Yup, big sore thumb. But I'll have to fix it in a card reader now.
> When RealtimePi has finished.
>
Which it has, I brought the u-sd to a reader and 
fixed /e/passwd, /e/group, and /e/shadow so they all matched.

but I have another network hookup, using sshfs that is not working  for 
either name
gene@coyote:~$ sshfs pi@picnc:/ /sshnet/picnc
fuse: bad mount point `/sshnet/picnc': Transport endpoint is not 
connected
gene@coyote:~$ sshfs gene@picnc:/ /sshnet/picnc
fuse: bad mount point `/sshnet/picnc': Transport endpoint is not 
connected

What does that tell us? I should see the / directory for any of those 5 
mount points, like this:

gene@coyote:~$ ls -l /sshnet/shop
total 108
drwxr-xr-x 1 root root  4096 Jan 16  2019 bin
drwxr-xr-x 1 root root  4096 Feb 22  2019 boot
drwxr-xr-x 1 root root  3260 Sep  7 16:34 dev
drwxr-xr-x 1 root root 12288 Aug  4 17:23 etc
drwxr-xr-x 1 root root  4096 May 18  2015 GenesAmandaHelper-0.61
drwxr-xr-x 1 root root  4096 May 19  2015 home
lrwxrwxrwx 1 root root35 May 18  2015 
initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae
drwxr-xr-x 1 root root  4096 Jun 24  2017 lib
drwx-- 1 root root 16384 May 18  2015 lost+found
drwxr-xr-x 1 root root  4096 May  7  2018 media
drwxr-xr-x 1 root root  4096 Apr 19  2014 mnt
drwxr-xr-x 1 root root 0 Aug 20 22:03 net
drwxr-xr-x 1 root root  4096 Jul  3  2014 opt
dr-xr-xr-x 1 root root 0 Aug 20 22:02 proc
drwx-- 1 root root  4096 May  6  2018 root
drwxr-xr-x 1 root root   900 Aug 22 11:45 run
drwxr-xr-x 1 root root  4096 Jun  3  2018 sbin
drwxr-xr-x 1 root root  4096 Jun 10  2012 selinux
drwxr-xr-x 1 root root  4096 Jul  3  2014 srv
drwxr-xr-x 1 gene gene  4096 Sep 24  2015 sshnet
dr-xr-xr-x 1 root root 0 Aug 20 22:02 sys
drwxrwxrwt 1 root root  4096 Sep  9 16:17 tmp
drwxr-xr-x 1 root root  4096 May 19  2015 usr
drwxr-xr-x 1 root root  4096 May 21  2015 var
lrwxrwxrwx 1 root root31 May 18  2015 vmlinuz -> 
boot/vmlinuz-3.4-9-rtai-686-pae

Obviously I'd have to cd and sudo to access it all, but 99.9% of the 
activity takes place in /home/gene, so thats not a huge problem.

Right now, the next image I want to dd to a card to run that machine, is 
locked away behind that error.

clues to what I've broken?

Humm, went thru the rmdir etc stuff to refresh the directory, and now it 
works as I go wandering off scratching head.
cp took 15 minutes to move it to this machine, and sha512sum will be used 
to verify the copy. By then I should have my chefs hat on as its dinner 
time in the right coasts time zone. But the customer has gone to sleep.

But I just took that card out and plugged it in, it gets to a text login, 
but no mouse or keyboard 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David Wright]

On Mon 09 Sep 2019 at 13:51:06 (-0400), Gene Heskett wrote:
> On Monday 09 September 2019 13:23:24 John Hasler wrote:
> > Don't you have a serial port rigged up?
>
> No, and nothing to display it on either.
>
> > A pc, minicom, and a USB to serial adapter if the pc has no serial port.
>
> And a usb cable long enough. That will call for a backhoe in this midden 
> heap.  I've got a boosted 10 meter one, someplace.

Why? Surely you make the serial cable as long as needed, and the USB
cable as short as possible.

Cheers,
David.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 13:58:03 Greg Wooledge wrote:

> On Mon, Sep 09, 2019 at 01:47:30PM -0400, Gene Heskett wrote:
> > Tell that to pam. Even after editing sudoers, pam won't allow yoou
> > to do squawt as sudo root. BTDT.
>
> If you have a serious complaint or question, you must provide details.

Also true, but those details are close to a year old, and my chances of 
remembering it ala copy/paste accuracy are slim and none, so at this 
late date, I'll not inflict my typo's on you.

> Your continued pattern of just ranting "it didn't work" for EVERY
> issue you encounter makes it impossible to help you.
>
> In Debian, universal sudo access is granted to any user in the sudo
> group.  If you want to be able to use sudo to run any command as any
> user, add your user account to the sudo group.  Either by running
> "adduser $LOGNAME sudo", or by editing the file with "vigr".

I should paint that on the wall. :) I've been trying by adding me to 
sudoers, but that seems to not work as expected.

> Then, log out and back in to get your new group memberships.

A detail I forgot, my bad.
>
> If that doesn't work in Raspbian, well, too damned bad.  This is a
> Debian mailing list.  All we know is Debian.

Touche` However, debian is in effect the broodstock for a lot of these 
variations, so what works for debian has a middling high chance of 
working with the *pians.

> > > For safety, you should use "vipw", "vipw -s" and "vigr" to perform
> > > those edits, but it's not actually required on Debian.
> >
> > Screwed up already, I used vipw to put me in front of pi, but now it
> > wants genes passwd, which has not been set. So I'll have to bring
> > that chip to a reader and edit it.
> >
> > Is there an order to make all this just work? But I'll have to wait
> > till realtimepi is done. Estimated another couple hours.
>
> If you duplicate the lines in both /etc/passwd AND /etc/shadow, your
> password for "gene" will be the same as the password for "pi". 
> Because they both use the same salted hash in the shadow file.  You
> know, the big-ass $1$abcdefgh$crapola string that you saw when you
> edited the file? It's kinda hard to miss.

Yup, big sore thumb. But I'll have to fix it in a card reader now. When 
RealtimePi has finished. 

Thanks Greg.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 13:23:55 ghe wrote:

> On 9/9/19 10:21 AM, Gene Heskett wrote:
> > Is there a foolproof way to convert that to "gene", or am I stuck
> > logging into it as "pi"?
>
> I tried that a long time ago, and had to reinstall, IIRC. What I do
> now is create a new user 'ghe' and just pretend pi doesn't exist.
>
> Maybe clear out pi's home dir, and some others, to get rid of unwanted
> garbage NOOBS puts everywhere.
>
> > But it runs the
> > machine pretty good.
>
> Not the 4, I betcha.
>
> > I've copied some stuff to SSD
>
> Where SSD is that SD card sticking out the back?

I have 2, a 60G and a 120G, on usb3 to sata cables plugged into a pair of 
the pi3's usb2 ports. Seems to work ok.

I am using the 120Gig as scratchpad to build RealtimePi from a 
buster-lite image on the pi3b right now.  Not fast because the pi3's 
slow usb2 ports, but it works. The 60 has configs on it to be copied 
back to the RealtimePi image when its built and installed on a fresh 64G 
u-sd.  Then it will take at least another gig of stuff before I can 
build linuxcnc, right on the pi3b.

>
> Binarys, from the RPi mirror? They seem to be pretty happy with text
> files, though.
>
> > Have I forgot something? Probably...
>
> Don't fight with it. You'll lose. Computers aren't real bright.
I've already lost that name fight 2x before. :)

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Greg Wooledge]

On Mon, Sep 09, 2019 at 01:47:30PM -0400, Gene Heskett wrote:
> Tell that to pam. Even after editing sudoers, pam won't allow yoou to do 
> squawt as sudo root. BTDT.

If you have a serious complaint or question, you must provide details.

Your continued pattern of just ranting "it didn't work" for EVERY issue
you encounter makes it impossible to help you.

In Debian, universal sudo access is granted to any user in the sudo
group.  If you want to be able to use sudo to run any command as any
user, add your user account to the sudo group.  Either by running
"adduser $LOGNAME sudo", or by editing the file with "vigr".

Then, log out and back in to get your new group memberships.

If that doesn't work in Raspbian, well, too damned bad.  This is a Debian
mailing list.  All we know is Debian.

> > For safety, you should use "vipw", "vipw -s" and "vigr" to perform
> > those edits, but it's not actually required on Debian.
> 
> Screwed up already, I used vipw to put me in front of pi, but now it 
> wants genes passwd, which has not been set. So I'll have to bring that 
> chip to a reader and edit it.
> 
> Is there an order to make all this just work? But I'll have to wait till 
> realtimepi is done. Estimated another couple hours.

If you duplicate the lines in both /etc/passwd AND /etc/shadow, your
password for "gene" will be the same as the password for "pi".  Because
they both use the same salted hash in the shadow file.  You know, the
big-ass $1$abcdefgh$crapola string that you saw when you edited the file?
It's kinda hard to miss.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 13:23:24 John Hasler wrote:

> I wrote:
> > Don't you have a serial port rigged up?
>
> Gene writes:
> > No, and nothing to display it on either.
>
> A pc, minicom, and a USB to serial adapter if the pc has no serial
> port.

And a usb cable long enough. That will call for a backhoe in this midden 
heap.  I've got a boosted 10 meter one, someplace.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 13:10:06 Greg Wooledge wrote:

> On Mon, Sep 09, 2019 at 12:21:45PM -0400, Gene Heskett wrote:
> > I'm building a RealtimePi buster-lite on the pi3 right now. Just one
> > $PITA problem, raspian insists the first, usr 1000 is
> > "pi".  Is there a foolproof way to convert that to "gene", or am I
> > stuck logging into it as "pi"?
>
> You keep asking Raspbian questions on debian-user.  Maybe you should
> be talking to a Raspbian mailing list about your Raspbian questions.

In case you haven't noted, raspian has no mailing lists, only forums, 
with a poorer search engine than google. And no automatic login memory. 
That would be tolerable IF you didn't lose your search results while 
logging in

> From the Debian point of view, you can simply login to the computer as
> root, then edit the /etc/passwd file and the /etc/shadow file (and
> probably the /etc/group file also, because I'm guessing you also want
> to change a group name).  Change "pi" to "gene", save and exit. 
> Voila.

Tell that to pam. Even after editing sudoers, pam won't allow yoou to do 
squawt as sudo root. BTDT.

> For safety, you should use "vipw", "vipw -s" and "vigr" to perform
> those edits, but it's not actually required on Debian.

Screwed up already, I used vipw to put me in front of pi, but now it 
wants genes passwd, which has not been set. So I'll have to bring that 
chip to a reader and edit it.

Is there an order to make all this just work? But I'll have to wait till 
realtimepi is done. Estimated another couple hours.

> If you want to retain the "pi" username, you can copy its lines and
> change "pi" to "gene" only in the copy.  Then you would have two user
> account names (pi and gene) which both map to UID 1000. 

I hadn't considered that, will that get me past pam? It would be nice if 
it had a man page but I've yet to find one. Security by paranoid 
obscurity I guess.

> Files/processes owned by UID 1000 will display with whichever name
> appears first in the passwd file.  This may be a useful alternative if
> Raspbian has some scripts or programs which hard-code the "pi" user
> name.

I'll give it a shot, thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[ghe]

On 9/9/19 10:21 AM, Gene Heskett wrote:

> Is there a foolproof way to convert that to "gene", or am I stuck 
> logging into it as "pi"? 

I tried that a long time ago, and had to reinstall, IIRC. What I do now
is create a new user 'ghe' and just pretend pi doesn't exist.

Maybe clear out pi's home dir, and some others, to get rid of unwanted
garbage NOOBS puts everywhere.

> But it runs the 
> machine pretty good.  

Not the 4, I betcha.

> I've copied some stuff to SSD 

Where SSD is that SD card sticking out the back?

Binarys, from the RPi mirror? They seem to be pretty happy with text
files, though.

> Have I forgot something? Probably...

Don't fight with it. You'll lose. Computers aren't real bright.

-- 
Glenn English

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[John Hasler]

I wrote:
> Don't you have a serial port rigged up?

Gene writes:
> No, and nothing to display it on either.

A pc, minicom, and a USB to serial adapter if the pc has no serial port.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Greg Wooledge]

On Mon, Sep 09, 2019 at 12:21:45PM -0400, Gene Heskett wrote:
> I'm building a RealtimePi buster-lite on the pi3 right now. Just one 
> $PITA problem, raspian insists the first, usr 1000 is 
> "pi".  Is there a foolproof way to convert that to "gene", or am I stuck 
> logging into it as "pi"? 

You keep asking Raspbian questions on debian-user.  Maybe you should be
talking to a Raspbian mailing list about your Raspbian questions.

>From the Debian point of view, you can simply login to the computer as
root, then edit the /etc/passwd file and the /etc/shadow file (and
probably the /etc/group file also, because I'm guessing you also want
to change a group name).  Change "pi" to "gene", save and exit.  Voila.

For safety, you should use "vipw", "vipw -s" and "vigr" to perform those
edits, but it's not actually required on Debian.

If you want to retain the "pi" username, you can copy its lines and
change "pi" to "gene" only in the copy.  Then you would have two user
account names (pi and gene) which both map to UID 1000.  Files/processes
owned by UID 1000 will display with whichever name appears first in the
passwd file.  This may be a useful alternative if Raspbian has some
scripts or programs which hard-code the "pi" user name.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 12:57:08 John Hasler wrote:

> Gene writes:
> > That was one of /my/ screwups, fixed to /dev/sdf later. Now rapbian
> > does something but only a magician knows what as I can't get any
> > video out of it.
>
> Don't you have a serial port rigged up?

No, and nothing to display it on either.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[John Hasler]

Gene writes:
> That was one of /my/ screwups, fixed to /dev/sdf later. Now rapbian
> does something but only a magician knows what as I can't get any video
> out of it.

Don't you have a serial port rigged up?
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 11:50:12 ghe wrote:

> On 9/9/19 8:26 AM, Gene Heskett wrote:
> > On Monday 09 September 2019 08:58:10 Greg Wooledge wrote:
> >> On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
> >>> sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1
> >>>
> >>> /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format
> >>> NTFS.
> >
> > That was one of /my/ screwups, fixed to /dev/sdf later. Now rapbian
> > does something but only a magician knows what as I can't get any
> > video out of it.  The debian-arm net-installs still stop dead after
> > one flash of the green led. Then I start finding rumors that
> > debian-arm isn't ready for pi4's, no device tree, and they became a
> > mob in a few hours.  So now I'm trying to get video out of raspbian,
> > failing miserably. In the meantime I'm trying to put together
> > another working stretch on my pi3 so I can bring my lathe back to
> > life.
> >
> > I had it working before the heart attack, but have come to the
> > conclusion I may have over-wrote that card.  Damned hard to put
> > identifying marks on a card that physical size. They should have
> > something like a MAC address imprinted so that one could keep an
> > index list of what each card does.
>
> Label them with a Sharpie -- 1, 2, 3, 4... And make notes in a
> 'database' (aka 'a piece of paper and a pencil').
>
> > So I've given up on the pi4 till the heat sink cover and more of the
> > micro to normal sized hdmi adapters arrive.
>
> Amazon. Single connector on both ends. Lots of choices, IIRC. Mine
> does good video with the ASUS VE228 monitor over on the table.
>
> There was a little backAndForth between the connectors to find the
> video, though, IIRC.
>
> > Might be a couple weeks
> > yet, coming from banggood.  All I have for that adapter now is some
> > sort of a 3 headed contraption I paid $16 for at wallies, and I've
> > no clue if it works. I've never seen video come out of it.
> >
> > I even took the new 22" ONN monitor to the pi3 on the lathe, makes a
> > decent pix on the pi3 at just noticeably lower contrast.
> >
> > Cheers, Gene Heskett
>
> Try the Buster NOOBS from the RPi website.
>
> Painless and works good here -- eventually. I'm using a 32G Samsung SD
> 'card'. And a USB3 external twirling rust disk.
>
> 4 is a little persnickety, and the RPi Buster Raspian has been futzed
> with. Last I heard, the Debian ARM software wasn't ready for 4 yet.

That seems to be the general opinion, darnit.

So lets go this way:
I'm building a RealtimePi buster-lite on the pi3 right now. Just one 
$PITA problem, raspian insists the first, usr 1000 is 
"pi".  Is there a foolproof way to convert that to "gene", or am I stuck 
logging into it as "pi"? 

debian-arm makes that easy by registering usr 1000 at install time, so 
the name is arbitrary. Secondary problem will be slow video, about 
1/20th speed of new stuff because its all framebuffer. But it runs the 
machine pretty good.  BTDT.

I've copied some stuff to SSD that will make setting up the new realtime 
card a heck of a lot easier, like fstab and the hosts file, and I have 
already stashed all the linuxcnc configs and gcodes to an SSD that will 
be mounted after overwriting the fsatab and rebooting, including 10G of 
swap on an SSD. Might have to pull a new git of linuxcnc since my local 
copy is now a month old, and that will pull in a boatload of dev stuff 
as builddeb works, but thats expected. A pi3b is not that fast at this 
stuff, but at least with enough swap it doesn't OOM trying at build the 
rs-274-d interpreter, it just keeps on chugging along.

Have I forgot something? Probably...


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[ghe]

On 9/9/19 8:26 AM, Gene Heskett wrote:

> On Monday 09 September 2019 08:58:10 Greg Wooledge wrote:
> 
>> On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
>>> sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1
>>>
>>> /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format NTFS.
>>
> That was one of /my/ screwups, fixed to /dev/sdf later. Now rapbian does 
> something but only a magician knows what as I can't get any video out of 
> it.  The debian-arm net-installs still stop dead after one flash of the 
> green led. Then I start finding rumors that debian-arm isn't ready for 
> pi4's, no device tree, and they became a mob in a few hours.  So now I'm 
> trying to get video out of raspbian, failing miserably. In the meantime 
> I'm trying to put together another working stretch on my pi3 so I can 
> bring my lathe back to life.
> 
> I had it working before the heart attack, but have come to the conclusion 
> I may have over-wrote that card.  Damned hard to put identifying marks 
> on a card that physical size. They should have something like a MAC 
> address imprinted so that one could keep an index list of what each card 
> does.

Label them with a Sharpie -- 1, 2, 3, 4... And make notes in a
'database' (aka 'a piece of paper and a pencil').

> So I've given up on the pi4 till the heat sink cover and more of the 
> micro to normal sized hdmi adapters arrive.  

Amazon. Single connector on both ends. Lots of choices, IIRC. Mine does
good video with the ASUS VE228 monitor over on the table.

There was a little backAndForth between the connectors to find the
video, though, IIRC.

> Might be a couple weeks 
> yet, coming from banggood.  All I have for that adapter now is some sort 
> of a 3 headed contraption I paid $16 for at wallies, and I've no clue if 
> it works. I've never seen video come out of it.
> 
> I even took the new 22" ONN monitor to the pi3 on the lathe, makes a 
> decent pix on the pi3 at just noticeably lower contrast. 
> 
> Cheers, Gene Heskett

Try the Buster NOOBS from the RPi website.

Painless and works good here -- eventually. I'm using a 32G Samsung SD
'card'. And a USB3 external twirling rust disk.

4 is a little persnickety, and the RPi Buster Raspian has been futzed
with. Last I heard, the Debian ARM software wasn't ready for 4 yet.

-- 
Glenn English

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Monday 09 September 2019 08:58:10 Greg Wooledge wrote:

> On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
> > sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1
> >
> > /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format NTFS.
>
That was one of /my/ screwups, fixed to /dev/sdf later. Now rapbian does 
something but only a magician knows what as I can't get any video out of 
it.  The debian-arm net-installs still stop dead after one flash of the 
green led. Then I start finding rumors that debian-arm isn't ready for 
pi4's, no device tree, and they became a mob in a few hours.  So now I'm 
trying to get video out of raspbian, failing miserably. In the meantime 
I'm trying to put together another working stretch on my pi3 so I can 
bring my lathe back to life.

I had it working before the heart attack, but have come to the conclusion 
I may have over-wrote that card.  Damned hard to put identifying marks 
on a card that physical size. They should have something like a MAC 
address imprinted so that one could keep an index list of what each card 
does.

So I've given up on the pi4 till the heat sink cover and more of the 
micro to normal sized hdmi adapters arrive.  Might be a couple weeks 
yet, coming from banggood.  All I have for that adapter now is some sort 
of a 3 headed contraption I paid $16 for at wallies, and I've no clue if 
it works. I've never seen video come out of it.

I even took the new 22" ONN monitor to the pi3 on the lathe, makes a 
decent pix on the pi3 at just noticeably lower contrast. 

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Greg Wooledge]

On Sun, Sep 08, 2019 at 03:04:40AM -0400, Gene Heskett wrote:
> sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1
> 
> /dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format NTFS.

You wrote the installer image to a *partition* on the SD card instead
of to the whole SD card?  Is that normal for your architecture?  It
doesn't sound normal for amd64 or i386, but I don't know armhf.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David Wright]

On Sun 08 Sep 2019 at 13:26:16 (-0400), Gene Heskett wrote:
> On Sunday 08 September 2019 12:49:14 Curt wrote:
> > On 2019-09-08, Gene Heskett  wrote:
> > >> > What does this do that the iso doesn't, and note it takes a
> > >> > windows machine to follow those instructions.
> > >>
> > >> Eh? How do you work that out?
> > >
> > > I won't, theres always another way to skin that cat. ;-) Time, if I
> > > have it, will sort that out.
> >
> > He means how did you derive that erroneous notion from the
> > 'README.concatenateable_images,' which says:
> >
> >  To create a complete image from the two parts on Linux systems, you
> > can use zcat as follows:
> >
> >zcat firmware..img.gz partition.img.gz >
> > complete_image.img
> 
> zcat is not a cmnd I use, so I didn't recognize it.

Perhaps you've been brainwashed by the "pointless use of cat" crowd :)

> Besides, it more of 
> the zero info names that one isn't going to remember a week down the log 
> when one trips over partition.img.gz and wonders why it was that I 
> downloaded it.

Easily fixed by placing them in directories with meaningful names,
as in:

debian/iso/buster/10.0.0/netboot/d-i/amd64/initrd.gz (2019-07-01 30581523)
debian/iso/buster/10.0.0/netboot/d-i/amd64/linux (2019-07-01 5221616)
debian/iso/buster/10.0.0/netboot/d-i/amd64/SHA256SUMS (2019-07-01 75295)
debian/iso/buster/10.0.0/netboot/d-i/i386/initrd.gz (2019-07-01 26665346)
debian/iso/buster/10.0.0/netboot/d-i/i386/linux (2019-07-01 4140688)
debian/iso/buster/10.0.0/netboot/d-i/i386/SHA256SUMS (2019-07-01 73988)
debian/iso/buster/10.0.0/netinst/amd64/firmware-10.0.0-amd64-netinst.iso 
(2019-07-06 393216000)
debian/iso/buster/10.0.0/netinst/amd64/SHA512SUMS (2019-07-06 332)
debian/iso/buster/10.0.0/netinst/amd64/SHA512SUMS.sign (2019-07-06 833)
debian/iso/buster/10.0.0/netinst/i386/firmware-10.0.0-i386-netinst.iso 
(2019-07-06 488636416)
debian/iso/buster/10.0.0/netinst/i386/SHA512SUMS (2019-07-06 330)
debian/iso/buster/10.0.0/netinst/i386/SHA512SUMS.sign (2019-07-06 833)
debian/iso/jessie/8.7.1/netinst/i386/firmware-8.7.1-i386-netinst.iso 
(2017-01-16 351272960)
debian/iso/jessie/8.7.1/netinst/i386/SHA512SUMS (2017-01-17 162)
debian/iso/jessie/8.7.1/netinst/i386/SHA512SUMS.sign (2017-01-17 819)
debian/iso/stretch/9.1.0/live/amd64/debian-live-9.1.0-amd64-lxde+nonfree.iso 
(2017-07-22 2346844160)
debian/iso/stretch/9.1.0/live/amd64/SHA512SUMS (2017-07-23 4180)
debian/iso/stretch/9.1.0/live/amd64/SHA512SUMS.sign (2017-07-23 833)
debian/iso/stretch/9.1.0/live/i386/debian-live-9.1.0-i386-lxde+nonfree.iso 
(2017-07-23 2394816512)
debian/iso/stretch/9.1.0/live/i386/SHA512SUMS (2017-07-23 4156)
debian/iso/stretch/9.1.0/live/i386/SHA512SUMS.sign (2017-07-23 833)
debian/iso/stretch/9.5.0/netinst/amd64/firmware-9.5.0-amd64-netinst.iso 
(2018-07-14 341835776)
debian/iso/stretch/9.5.0/netinst/amd64/SHA512SUMS (2018-07-14 163)
debian/iso/stretch/9.5.0/netinst/amd64/SHA512SUMS.sign (2018-07-14 833)
debian/iso/stretch/9.5.0/netinst/i386/firmware-9.5.0-i386-netinst.iso 
(2018-07-14 432013312)
debian/iso/stretch/9.5.0/netinst/i386/SHA512SUMS (2018-07-14 162)
debian/iso/stretch/9.5.0/netinst/i386/SHA512SUMS.sign (2018-07-14 833)

Cheers,
David.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 13:46:11 Gene Heskett wrote:

> On Sunday 08 September 2019 11:34:20 Gene Heskett wrote:
> > On Sunday 08 September 2019 08:35:51 Thomas Schmitt wrote:
> > > Hi,
> > >
> > > i now realize that Gene by "rp4" indicated some known Raspberry
> > > system. So my proposal about netboot might be hopeless according
> > > to the answers of David and didier.gaumet.
> > >
> > > --
> > >-- -- But there is technical stuff left to discuss:
> > >
> > > I wrote:
> > > > > SD card seems to be the intended target for netboot images.
> > > > > http://ftp.debian.org/debian/dists/stable/main/installer-arm64
> > > > >/c ur rent/images/netboot/SD-card-images/ [...]
> > > > > Those are not ISO9660 but rather partitioned images with a
> > > > > FAT32 filesystem:
> > > > > [...]
> > > > >   Device  Boot StartEnd Sectors  Size
> > > > > Id Type firmware.a64-olinuxino.img1 * 2048 19  197952
> > > > > 96.7M c W95
> > >
> > > Gene Heskett wrote:
> > > > What does this do that the iso doesn't,
> > >
> > > Those are images for disk-like devices only and they don't look
> > > like they are supposed to boot directly via EFI. The Debian arm64
> > > ISOs on the other hand offer typical EFI boot equipment.
> > >
> > > > and note it takes a windows  machine to follow those
> > > > instructions.
> > >
> > > If you mean
> > >
> > > http://ftp.debian.org/debian/dists/stable/main/installer-arm64/cur
> > >re nt /images/netboot/SD-card-images/README.concatenateable_images
> > > then immediately before the MS-Windows instructions, i read:
> > >
> > >   "To create a complete image from the two parts on Linux systems,
> > > you can use zcat as follows:
> > >  zcat firmware..img.gz partition.img.gz >
> > > complete_image.img "
> > > I inspected both image parts by gunzip-ing them:
> > >
> > >   $ gunzip firmware.a64-olinuxino.img.gz
> > >   $ /sbin/fdisk -lu firmware.a64-olinuxino.img
> > >   ... lots of message lines ...
> > >   $ gunzip partition.img.gz
> > >   $ sudo mount partition.img /mnt/fat
> > >   $ find /mnt/fat | less
> > >
> > > So i would simply provide another useless use of cat with my
> > > superuser hat on:
> > >
> > >   # cat firmware.a64-olinuxino.img partition.img | dd bs=4096
> > > of=/dev/sdf1
> > >
> > > (Insert "sudo" where needed, if your system has no superuser.)
> > >
> > > > I think what I will do next is send gparted to create a gpt
> > > > table with a fat32 first partition of a gig or so, and do an
> > > > ext4 on the rest of it. Then put the iso on sdf.
> > >
> > > The ISO brings its own partition table. Your gparted work will be
> > > wasted. See the second grey box at
> > >   https://wiki.debian.org/RepackBootableISO#arm64_release_9.4.0
> > > which shows fdisk output for arm64 ISOs.
> > > (Nothing did change in the ISO partitioning for 10.0 since 9.4.)
> > >
> > > > Since these come as NTFS formatted cards these days,
> > >
> > > Filesystems on the card get overwritten by the ISO or at least
> > > lose their entry in the partition table, if they are not reached
> > > by dd's work.
> > >
> > > > I would think that
> > > > writing the iso to /dev/sdf would at least start the install,
> > > > and the installers disk utils could take care of the rest.  What
> > > > the iso wrote should be all that counts.
> > >
> > > As said, Debian arm64 netinst ISOs offer boot entries for EFI.
> > > Googling "raspberry rp4 efi" shows that the combination of
> > > Raspberry and EFI is exotic.
> > >
> > > > I have also been thru your installer docs
> > >
> > > Mine ? I only write docs about things like optical drives or ISO
> > > 9660 filesystems.
> > > By the latter i happen to be involved in the first boot step of
> > > most Debian ISOs.
> > >
> > > > I feel like I'm playing pin the tale on the donkey, blindfolded.
> > >
> > > As said, i think that David and didier.gaumet show more clue than
> > > i do. So try to get a donkey with tail already attached.
> > >
> > > I understand that David's advise is to look at
> > >   https://raspbian.org/RaspbianImages
> > >   https://www.raspberrypi.org/downloads/raspbian/
> > >
> > >
> > > Have a nice day :)
> > >
> > > Thomas
> >
> > I'll have to take your word for it.
> >
> > I now have a 5 amp. 5.09 volt supply, hot on gpio pin 2, common on
> > gpio pin 6, and I just rewrote the debian-10.0.0-armhf-netinst.iso
> > to /dev/sdf, took it to the rpi4b, and got that same single, 10ms
> > maybe, flash of the green led.  Next I try this .img,
> > 2019-06-20-raspbian-buster.img
> >
> > And I restarted the ssh daemon on the rpi3, running stretch, so
> > maybe I can log into it and get something done yet today. gah, damn
> > raspian, passwds no good.
> >
> > Change that, reboot after enabling ssh. fixed pw, loggged in.
> >
> > And I |think| the raspian is booting. After quite some activity of
> > the green led, its lit solid now, but no damned video. Looks like
> > the new monitor 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 11:34:20 Gene Heskett wrote:

> On Sunday 08 September 2019 08:35:51 Thomas Schmitt wrote:
> > Hi,
> >
> > i now realize that Gene by "rp4" indicated some known Raspberry
> > system. So my proposal about netboot might be hopeless according to
> > the answers of David and didier.gaumet.
> >
> > 
> >-- But there is technical stuff left to discuss:
> >
> > I wrote:
> > > > SD card seems to be the intended target for netboot images.
> > > > http://ftp.debian.org/debian/dists/stable/main/installer-arm64/c
> > > >ur rent/images/netboot/SD-card-images/ [...]
> > > > Those are not ISO9660 but rather partitioned images with a FAT32
> > > > filesystem:
> > > > [...]
> > > >   Device  Boot StartEnd Sectors  Size Id
> > > > Type firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M
> > > > c W95
> >
> > Gene Heskett wrote:
> > > What does this do that the iso doesn't,
> >
> > Those are images for disk-like devices only and they don't look like
> > they are supposed to boot directly via EFI. The Debian arm64 ISOs on
> > the other hand offer typical EFI boot equipment.
> >
> > > and note it takes a windows  machine to follow those instructions.
> >
> > If you mean
> >
> > http://ftp.debian.org/debian/dists/stable/main/installer-arm64/curre
> >nt /images/netboot/SD-card-images/README.concatenateable_images then
> > immediately before the MS-Windows instructions, i read:
> >
> >   "To create a complete image from the two parts on Linux systems,
> > you can use zcat as follows:
> >  zcat firmware..img.gz partition.img.gz >
> > complete_image.img "
> > I inspected both image parts by gunzip-ing them:
> >
> >   $ gunzip firmware.a64-olinuxino.img.gz
> >   $ /sbin/fdisk -lu firmware.a64-olinuxino.img
> >   ... lots of message lines ...
> >   $ gunzip partition.img.gz
> >   $ sudo mount partition.img /mnt/fat
> >   $ find /mnt/fat | less
> >
> > So i would simply provide another useless use of cat with my
> > superuser hat on:
> >
> >   # cat firmware.a64-olinuxino.img partition.img | dd bs=4096
> > of=/dev/sdf1
> >
> > (Insert "sudo" where needed, if your system has no superuser.)
> >
> > > I think what I will do next is send gparted to create a gpt table
> > > with a fat32 first partition of a gig or so, and do an ext4 on the
> > > rest of it. Then put the iso on sdf.
> >
> > The ISO brings its own partition table. Your gparted work will be
> > wasted. See the second grey box at
> >   https://wiki.debian.org/RepackBootableISO#arm64_release_9.4.0
> > which shows fdisk output for arm64 ISOs.
> > (Nothing did change in the ISO partitioning for 10.0 since 9.4.)
> >
> > > Since these come as NTFS formatted cards these days,
> >
> > Filesystems on the card get overwritten by the ISO or at least lose
> > their entry in the partition table, if they are not reached by dd's
> > work.
> >
> > > I would think that
> > > writing the iso to /dev/sdf would at least start the install, and
> > > the installers disk utils could take care of the rest.  What the
> > > iso wrote should be all that counts.
> >
> > As said, Debian arm64 netinst ISOs offer boot entries for EFI.
> > Googling "raspberry rp4 efi" shows that the combination of Raspberry
> > and EFI is exotic.
> >
> > > I have also been thru your installer docs
> >
> > Mine ? I only write docs about things like optical drives or ISO
> > 9660 filesystems.
> > By the latter i happen to be involved in the first boot step of most
> > Debian ISOs.
> >
> > > I feel like I'm playing pin the tale on the donkey, blindfolded.
> >
> > As said, i think that David and didier.gaumet show more clue than i
> > do. So try to get a donkey with tail already attached.
> >
> > I understand that David's advise is to look at
> >   https://raspbian.org/RaspbianImages
> >   https://www.raspberrypi.org/downloads/raspbian/
> >
> >
> > Have a nice day :)
> >
> > Thomas
>
> I'll have to take your word for it.
>
> I now have a 5 amp. 5.09 volt supply, hot on gpio pin 2, common on
> gpio pin 6, and I just rewrote the debian-10.0.0-armhf-netinst.iso to
> /dev/sdf, took it to the rpi4b, and got that same single, 10ms maybe,
> flash of the green led.  Next I try this .img,
> 2019-06-20-raspbian-buster.img
>
> And I restarted the ssh daemon on the rpi3, running stretch, so maybe
> I can log into it and get something done yet today. gah, damn raspian,
> passwds no good.
>
> Change that, reboot after enabling ssh. fixed pw, loggged in.
>
> And I |think| the raspian is booting. After quite some activity of the
> green led, its lit solid now, but no damned video. Looks like the new
> monitor I bought isn't working, its stuck on the vga input, and the
> menu button to change it isn't working, so back to wallies with $80
> worth of junk.
>
> Later.
>
> Cheers, Gene Heskett

Took it back and got another, same exact results, monitor says no input, 
menu button does not work so I can't select/test the 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 12:49:14 Curt wrote:

> On 2019-09-08, Gene Heskett  wrote:
> >> > What does this do that the iso doesn't, and note it takes a
> >> > windows machine to follow those instructions.
> >>
> >> Eh? How do you work that out?
> >
> > I won't, theres always another way to skin that cat. ;-) Time, if I
> > have it, will sort that out.
>
> He means how did you derive that erroneous notion from the
> 'README.concatenateable_images,' which says:
>
>  To create a complete image from the two parts on Linux systems, you
> can use zcat as follows:
>
>zcat firmware..img.gz partition.img.gz >
> complete_image.img

zcat is not a cmnd I use, so I didn't recognize it.  Besides, it more of 
the zero info names that one isn't going to remember a week down the log 
when one trips over partition.img.gz and wonders why it was that I 
downloaded it.

So my bad I guess.
> (In fact, in Windows the process is more involved.)
>
> > Cheers, Gene Heskett


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[tomas]

On Sun, Sep 08, 2019 at 07:01:00PM +0200, deloptes wrote:
> to...@tuxteam.de wrote:

[...]

> > I've the hunch that the firmware also has to be on the top-level dir,
> > but haven't checked yet.
> > 
> > Note that this is all Rpi 3B+
> 
> yes kernel has to be there in the root of the partition

Thanks for confirming :)

Cheers
-- t


signature.asc
Description: Digital signature

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

to...@tuxteam.de wrote:

> AFAIK it also had to be the *first* partition on the medium. I don't know
> whether the kernel has to be on that same partition (but that's the only
> configuration I tested).
> 
> I've the hunch that the firmware also has to be on the top-level dir,
> but haven't checked yet.
> 
> Note that this is all Rpi 3B+

yes kernel has to be there in the root of the partition

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Curt]

On 2019-09-08, Gene Heskett  wrote:
>> >
>> > What does this do that the iso doesn't, and note it takes a windows
>> > machine to follow those instructions.
>>
>> Eh? How do you work that out?
>
> I won't, theres always another way to skin that cat. ;-) Time, if I have 
> it, will sort that out.

He means how did you derive that erroneous notion from the
'README.concatenateable_images,' which says:
 
 To create a complete image from the two parts on Linux systems, you can
 use zcat as follows:

   zcat firmware..img.gz partition.img.gz > complete_image.img

(In fact, in Windows the process is more involved.)

> Cheers, Gene Heskett


-- 
“We are all in the gutter, but some of us are looking at the stars.” 
― Oscar Wilde, Lady Windermere's Fan

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 10:48:22 deloptes wrote:

> Gene Heskett wrote:
> > And that contained the seeds of my boot problem, the ntfs cards need
> > to have a fat32 re-formatting. NTFS/SDXC doesn't work.
>
> No idea how the 4b works but the older 2b needed vfat because of the
> firmware. Might be still the same. Your idea to create one smaller
> partition with vfat was good. This is what I intend to do as soon as I
> get the 4b, but now I wonder if I would need it at all. If netboot
> works, then it would be only the TFTP server

I would not figure on the netboot working before bullseye. ;-)

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 08:35:51 Thomas Schmitt wrote:

> Hi,
>
> i now realize that Gene by "rp4" indicated some known Raspberry
> system. So my proposal about netboot might be hopeless according to
> the answers of David and didier.gaumet.
>
> --
> But there is technical stuff left to discuss:
>
> I wrote:
> > > SD card seems to be the intended target for netboot images.
> > > http://ftp.debian.org/debian/dists/stable/main/installer-arm64/cur
> > >rent/images/netboot/SD-card-images/ [...]
> > > Those are not ISO9660 but rather partitioned images with a FAT32
> > > filesystem:
> > > [...]
> > >   Device  Boot StartEnd Sectors  Size Id
> > > Type firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M 
> > > c W95
>
> Gene Heskett wrote:
> > What does this do that the iso doesn't,
>
> Those are images for disk-like devices only and they don't look like
> they are supposed to boot directly via EFI. The Debian arm64 ISOs on
> the other hand offer typical EFI boot equipment.
>
> > and note it takes a windows  machine to follow those instructions.
>
> If you mean
>  
> http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current
>/images/netboot/SD-card-images/README.concatenateable_images then
> immediately before the MS-Windows instructions, i read:
>
>   "To create a complete image from the two parts on Linux systems, you
> can use zcat as follows:
>  zcat firmware..img.gz partition.img.gz >
> complete_image.img "
> I inspected both image parts by gunzip-ing them:
>
>   $ gunzip firmware.a64-olinuxino.img.gz
>   $ /sbin/fdisk -lu firmware.a64-olinuxino.img
>   ... lots of message lines ...
>   $ gunzip partition.img.gz
>   $ sudo mount partition.img /mnt/fat
>   $ find /mnt/fat | less
>
> So i would simply provide another useless use of cat with my superuser
> hat on:
>
>   # cat firmware.a64-olinuxino.img partition.img | dd bs=4096
> of=/dev/sdf1
>
> (Insert "sudo" where needed, if your system has no superuser.)
>
> > I think what I will do next is send gparted to create a gpt table
> > with a fat32 first partition of a gig or so, and do an ext4 on the
> > rest of it. Then put the iso on sdf.
>
> The ISO brings its own partition table. Your gparted work will be
> wasted. See the second grey box at
>   https://wiki.debian.org/RepackBootableISO#arm64_release_9.4.0
> which shows fdisk output for arm64 ISOs.
> (Nothing did change in the ISO partitioning for 10.0 since 9.4.)
>
> > Since these come as NTFS formatted cards these days,
>
> Filesystems on the card get overwritten by the ISO or at least lose
> their entry in the partition table, if they are not reached by dd's
> work.
>
> > I would think that
> > writing the iso to /dev/sdf would at least start the install, and
> > the installers disk utils could take care of the rest.  What the iso
> > wrote should be all that counts.
>
> As said, Debian arm64 netinst ISOs offer boot entries for EFI.
> Googling "raspberry rp4 efi" shows that the combination of Raspberry
> and EFI is exotic.
>
> > I have also been thru your installer docs
>
> Mine ? I only write docs about things like optical drives or ISO 9660
> filesystems.
> By the latter i happen to be involved in the first boot step of most
> Debian ISOs.
>
> > I feel like I'm playing pin the tale on the donkey, blindfolded.
>
> As said, i think that David and didier.gaumet show more clue than i
> do. So try to get a donkey with tail already attached.
>
> I understand that David's advise is to look at
>   https://raspbian.org/RaspbianImages
>   https://www.raspberrypi.org/downloads/raspbian/
>
>
> Have a nice day :)
>
> Thomas
I'll have to take your word for it.

I now have a 5 amp. 5.09 volt supply, hot on gpio pin 2, common on gpio 
pin 6, and I just rewrote the debian-10.0.0-armhf-netinst.iso 
to /dev/sdf, took it to the rpi4b, and got that same single, 10ms maybe, 
flash of the green led.  Next I try this .img, 
2019-06-20-raspbian-buster.img

And I restarted the ssh daemon on the rpi3, running stretch, so maybe I 
can log into it and get something done yet today. gah, damn raspian, 
passwds no good.

Change that, reboot after enabling ssh. fixed pw, loggged in.

And I |think| the raspian is booting. After quite some activity of the 
green led, its lit solid now, but no damned video. Looks like the new 
monitor I bought isn't working, its stuck on the vga input, and the menu 
button to change it isn't working, so back to wallies with $80 worth of 
junk.

Later.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[tomas]

On Sun, Sep 08, 2019 at 04:48:22PM +0200, deloptes wrote:
> Gene Heskett wrote:
> 
> > And that contained the seeds of my boot problem, the ntfs cards need to
> > have a fat32 re-formatting. NTFS/SDXC doesn't work.
> 
> No idea how the 4b works but the older 2b needed vfat because of the
> firmware [...]

AFAIK it also had to be the *first* partition on the medium. I don't know
whether the kernel has to be on that same partition (but that's the only
configuration I tested).

I've the hunch that the firmware also has to be on the top-level dir,
but haven't checked yet.

Note that this is all Rpi 3B+

Cheers
-- t


signature.asc
Description: Digital signature

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Thomas Schmitt wrote:

> As said, Debian arm64 netinst ISOs offer boot entries for EFI.
> Googling "raspberry rp4 efi" shows that the combination of Raspberry and
> EFI is exotic.

Thomas,
the RPI had its own boot process - you can imaging booting mobile phone. Not
sure what they did for the RPI4b now - at least it looks like the
bootloader now is on the EEPROM - it said in the GPU AFAIR.
the boot partition must be vfat in the beginning of the disk, so that the
firmware can load the bootloader. It might be not the case now with the
RPI4

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> And that contained the seeds of my boot problem, the ntfs cards need to
> have a fat32 re-formatting. NTFS/SDXC doesn't work.

No idea how the 4b works but the older 2b needed vfat because of the
firmware. Might be still the same. Your idea to create one smaller
partition with vfat was good. This is what I intend to do as soon as I get
the 4b, but now I wonder if I would need it at all. If netboot works, then
it would be only the TFTP server

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 08:32:30 deloptes wrote:

> Gene Heskett wrote:
> > I have also been thru your installer docs, without finding specific
> > procedures for initializing the u-sd cards its being installed from.
> > Did I miss that link in my searches?  Without that I feel like I'm
> > playing pin the tale on the donkey, blindfolded.
>
> I think you should start reading here
> https://www.raspberrypi.org/documentation/installation/

And that contained the seeds of my boot problem, the ntfs cards need to 
have a fat32 re-formatting. NTFS/SDXC doesn't work.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 07:42:36 Michael Howard wrote:

> On 08/09/2019 12:39, Gene Heskett wrote:
> > On Sunday 08 September 2019 03:59:01 Thomas Schmitt wrote:
> >> Hi,
> >>
> >> Gene Heskett wrote:
> >>> debian-10.0.0-armhf-netinst.iso
> >>> debian-10.0.0-arm64-netinst.iso
> >>
> >> SD card seems to be the intended target for netboot images.
> >> E.g.
> >>
> >> http://ftp.debian.org/debian/dists/stable/main/installer-arm64/curr
> >>ent /images/netboot/SD-card-images/
> >>
> >> Maybe worth a try, if you can get advise about the appropriate
> >> image for your ARM machine.
> >>
> >> Those are not ISO9660 but rather partitioned images with a FAT32
> >> filesystem:
> >>
> >>$ /sbin/fdisk -lu firmware.a64-olinuxino.img
> >>...
> >>Disklabel type: dos
> >>...
> >>Device  Boot StartEnd Sectors  Size Id
> >> Type firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M  c
> >> W95 FAT32 (LBA)
> >>
> >>
> >> Have a nice day :)
> >>
> >> Thomas
> >
> > What does this do that the iso doesn't, and note it takes a windows
> > machine to follow those instructions.
>
> Eh? How do you work that out?

I won't, theres always another way to skin that cat. ;-) Time, if I have 
it, will sort that out.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 06:12:08 David wrote:

> On Sun, 8 Sep 2019 at 19:51, David  wrote:
> > On Sun, 8 Sep 2019 at 06:59, Gene Heskett  
wrote:
> > > [...] What did I do wrong [...] ?
> >
> > I don't know about the Debian ARM images, but if
> > they were relevant then I assume they would be
> > mentioned at the links above.
>
> And here's a very recent discussion of what is required to
> install Ubuntu server in either 32 or 64bit version on
> Raspberry Pi 4, which may be helpful:
> https://jamesachambers.com/raspberry-pi-ubuntu-server-18-04-2-installa
>tion-guide/
>
> I don't have any special needs for my Pi 4 so it is currently
> running with a Raspbian image, like most people do.
> https://raspbian.org/RaspbianImages
> https://www.raspberrypi.org/downloads/raspbian/

I get the impression its going to take till bullseye to begin to get it 
all in "one sock" for the pi4b. The above is fraught with all sorts of 
patches & fixes, none of which have descriptive enough names to their 
downloads to remember what the hell they do next week.  None of that is 
your (debian's) fault, but it does take time to merge all that into an 
it just works package.

Based on that, I may, probably will, revert to a stretch install on the 
pi3b, and put up with the video frame rate you can count on your 
fingers. It does run the machine fairly well. But I'll also have the 
pi4b setup on the table, and keep it on testing I think, just to watch 
progress.

Unless the RealtimePi guy makes a buster kit for the rpi3b that uses the 
new video libraries, that would be awful tempting to play with on a 
pi3b. So far, his realtime kernels are too old to use the new video, 
which is nearly 20x faster.

Whoever gets there first, with a stable os is what it boils down to. At 
this point, it looks like raspians 2nd buster release, if the hm2_rpspi 
driver works with it.  Thats a big if. And it must work else I'll be out 
around $200 for all new interfacing hardware.

Thanks for the heads up David, you are going to save me time. Time I may 
not have, but so far he's not doing anything final. I appreciate it, a 
lot.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[John Hasler]

Sorry.  I don't know why it went out like that.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[John Hasler]

Gene writes:
> I have also been thru your installer docs, without finding specific
> procedures for initializing the u-sd cards its being installed from.

You dd the image directly to the raw device.  What was previously on the
card is irrelevant: it gets overwritten.

I recently installed Armbian on an Espressobin (uses a Marvell chip).
These installs can be a bit gnarly.  I had to upgrade the Uboot loader
and patch some variables on the chip.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas Schmitt]

Hi,

i now realize that Gene by "rp4" indicated some known Raspberry system.
So my proposal about netboot might be hopeless according to the answers
of David and didier.gaumet.

--
But there is technical stuff left to discuss:

I wrote:
> > SD card seems to be the intended target for netboot images.
> > http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current/images/netboot/SD-card-images/
> > [...]
> > Those are not ISO9660 but rather partitioned images with a FAT32
> > filesystem:
> > [...]
> >   Device  Boot StartEnd Sectors  Size Id Type
> >   firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M  c W95

Gene Heskett wrote:
> What does this do that the iso doesn't,

Those are images for disk-like devices only and they don't look like
they are supposed to boot directly via EFI. The Debian arm64 ISOs on the
other hand offer typical EFI boot equipment.


> and note it takes a windows  machine to follow those instructions.

If you mean
  
http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current/images/netboot/SD-card-images/README.concatenateable_images
then immediately before the MS-Windows instructions, i read:

  "To create a complete image from the two parts on Linux systems, you can
   use zcat as follows:
 zcat firmware..img.gz partition.img.gz > complete_image.img
   "
I inspected both image parts by gunzip-ing them:

  $ gunzip firmware.a64-olinuxino.img.gz
  $ /sbin/fdisk -lu firmware.a64-olinuxino.img
  ... lots of message lines ...
  $ gunzip partition.img.gz
  $ sudo mount partition.img /mnt/fat
  $ find /mnt/fat | less

So i would simply provide another useless use of cat with my superuser hat
on:

  # cat firmware.a64-olinuxino.img partition.img | dd bs=4096 of=/dev/sdf1

(Insert "sudo" where needed, if your system has no superuser.)


> I think what I will do next is send gparted to create a gpt table with a
> fat32 first partition of a gig or so, and do an ext4 on the rest of it.
> Then put the iso on sdf.

The ISO brings its own partition table. Your gparted work will be wasted.
See the second grey box at
  https://wiki.debian.org/RepackBootableISO#arm64_release_9.4.0
which shows fdisk output for arm64 ISOs.
(Nothing did change in the ISO partitioning for 10.0 since 9.4.)


> Since these come as NTFS formatted cards these days,

Filesystems on the card get overwritten by the ISO or at least lose their
entry in the partition table, if they are not reached by dd's work.


> I would think that
> writing the iso to /dev/sdf would at least start the install, and the
> installers disk utils could take care of the rest.  What the iso wrote
> should be all that counts.

As said, Debian arm64 netinst ISOs offer boot entries for EFI.
Googling "raspberry rp4 efi" shows that the combination of Raspberry and
EFI is exotic.


> I have also been thru your installer docs

Mine ? I only write docs about things like optical drives or ISO 9660
filesystems.
By the latter i happen to be involved in the first boot step of most
Debian ISOs.


> I feel like I'm playing pin the tale on the donkey, blindfolded.

As said, i think that David and didier.gaumet show more clue than i do.
So try to get a donkey with tail already attached.

I understand that David's advise is to look at
  https://raspbian.org/RaspbianImages
  https://www.raspberrypi.org/downloads/raspbian/


Have a nice day :)

Thomas

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> I have also been thru your installer docs, without finding specific
> procedures for initializing the u-sd cards its being installed from. Did
> I miss that link in my searches?  Without that I feel like I'm playing
> pin the tale on the donkey, blindfolded.

I think you should start reading here
https://www.raspberrypi.org/documentation/installation/

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 06:05:37 didier.gau...@gmail.com wrote:

> Debian Buster is not yet ready for Raspberry Pi 4:
>
> https://wiki.debian.org/RaspberryPiImages
> https://www.raspberrypi.org/documentation/installation/

Potential timeline?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 05:51:43 David wrote:

> On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:
> > [...] What did I do wrong [...] ?
>
> I have attempted to find relevant info from the Debian project
> for you. I found these two pages, which seem to be recently
> updated by active developers:
> [1] https://salsa.debian.org/raspi-team/image-specs
> [2] https://wiki.debian.org/RaspberryPiImages
>
> Quoting from [2] above:
> "The new (June 2019) Raspberry Pi 4 is not yet supported
> (the kernel does not yet have a Device Tree for it) "
>
I may have, as of yesterday, a testable gpio/spi driver for the pi4b, it 
appears the major change is the base address of the gpio stuffs.  One 
conditional define, maybe.

> I don't know about the Debian ARM images, but if
> they were relevant then I assume they would be
> mentioned at the links above.

I'd assume so too, but then the pi4 announce no doubt caught the debian 
folks busier than that famous cat covering his output on a tin roof.
truly good support if lots of changes may wait for bullseye.  That IMO 
can be laid on the Foundations doorstep, the deeper the better, as they 
should have been sharing that under an NDI of some sort.  Catching your 
folks out does not a pretty picture of the Foundation paint.

Thanks David.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 04:03:00 deloptes wrote:

> Gene Heskett wrote:
> > I have a bigger 4 amp supply  but haven't rigged it with output
> > jumpers yet.
>
> But in the specs of the RPI4 it says it requires a 3A PWR supply.

Thats not listed on the multi-language paper in the rpi4 bag. Not your 
(debians fault) but some lawyer wrote that to specificly remove any 
helpfull info, like how to power it up.

I'll get that going with a 4 or 5 amp today. I should have at least one 
of those in the spares box yet.

> However I think it is possible that you have another issue with the
> SD-CARD.
>
> It looks to me that now with RPI4 and the bootloader placed on the
> device.
>
> What I do not understand is if the net boot works or not, cause it is
> saying it will be enabled by optional updates later.

I saw that someplace too, and am confused that net booting was even 
mentioned. Thats a whole new critter.

Net boot is not net installer, by quite a lengthy row of apple trees.

I'll get a new bigger supply hooked up today and let this list sort out 
how to prep a 64Gig, ntfs formatted u-sd card. I believe I now have an 
spi driver that will work with both a pi3b and the new pi4b. Testable at 
least.

Thanks all.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Michael Howard]

On 08/09/2019 12:39, Gene Heskett wrote:

On Sunday 08 September 2019 03:59:01 Thomas Schmitt wrote:


Hi,

Gene Heskett wrote:

debian-10.0.0-armhf-netinst.iso
debian-10.0.0-arm64-netinst.iso

SD card seems to be the intended target for netboot images.
E.g.
  
http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current

/images/netboot/SD-card-images/

Maybe worth a try, if you can get advise about the appropriate image
for your ARM machine.

Those are not ISO9660 but rather partitioned images with a FAT32
filesystem:

   $ /sbin/fdisk -lu firmware.a64-olinuxino.img
   ...
   Disklabel type: dos
   ...
   Device  Boot StartEnd Sectors  Size Id Type
   firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M  c W95
FAT32 (LBA)


Have a nice day :)

Thomas

What does this do that the iso doesn't, and note it takes a windows
machine to follow those instructions.


Eh? How do you work that out?

--
Mike Howard

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 03:59:01 Thomas Schmitt wrote:

> Hi,
>
> Gene Heskett wrote:
> > debian-10.0.0-armhf-netinst.iso
> > debian-10.0.0-arm64-netinst.iso
>
> SD card seems to be the intended target for netboot images.
> E.g.
>  
> http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current
>/images/netboot/SD-card-images/
>
> Maybe worth a try, if you can get advise about the appropriate image
> for your ARM machine.
>
> Those are not ISO9660 but rather partitioned images with a FAT32
> filesystem:
>
>   $ /sbin/fdisk -lu firmware.a64-olinuxino.img
>   ...
>   Disklabel type: dos
>   ...
>   Device  Boot StartEnd Sectors  Size Id Type
>   firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M  c W95
> FAT32 (LBA)
>
>
> Have a nice day :)
>
> Thomas

What does this do that the iso doesn't, and note it takes a windows 
machine to follow those instructions.  No such critter here, hasn't been
been for 50+ years.

I think what I will do next is send gparted to create a gpt table with a 
fat32 first partition of a gig or so, and do an ext4 on the rest of it. 
Then put the iso on sdf.  By using an sd card that big, I have never 
worn one out unless it was a sandisk. Those seem be garbage from the 
gitgo. I've even had one go read-only on the first write with dd.

Since these come as NTFS formatted cards these days, I would think that 
writing the iso to /dev/sdf would at least start the install, and the 
installers disk utils could take care of the rest.  What the iso wrote 
should be all that counts. 

I had one of busters rc3's (arm64) installed and running but got 
sidetracked because while it ran nice, amanda killed it trying to do a 
backup. I think thats an amanda build problem as it seems to apply to 
any arm64 install as it would also kill an armbian install on a rock64. 
armhf's worked fine. arm64's give BUS err.

Now, from my searches just now, I can't find a 10.1 version of these 
installers.  I thought I read that the mirrors s/b updated by now, but 
the web pages apparently have not been, so the new release is still 
hidden from view.  Or is my google-foo broken again?

I have also been thru your installer docs, without finding specific 
procedures for initializing the u-sd cards its being installed from. Did 
I miss that link in my searches?  Without that I feel like I'm playing 
pin the tale on the donkey, blindfolded.

Thanks Thomas.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[didier . gaumet]

Debian Buster is not yet ready for Raspberry Pi 4:

https://wiki.debian.org/RaspberryPiImages
https://www.raspberrypi.org/documentation/installation/

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David]

On Sun, 8 Sep 2019 at 19:51, David  wrote:
> On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:

> > [...] What did I do wrong [...] ?

> I don't know about the Debian ARM images, but if
> they were relevant then I assume they would be
> mentioned at the links above.

And here's a very recent discussion of what is required to
install Ubuntu server in either 32 or 64bit version on
Raspberry Pi 4, which may be helpful:
https://jamesachambers.com/raspberry-pi-ubuntu-server-18-04-2-installation-guide/

I don't have any special needs for my Pi 4 so it is currently
running with a Raspbian image, like most people do.
https://raspbian.org/RaspbianImages
https://www.raspberrypi.org/downloads/raspbian/

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David]

On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:
>
> [...] What did I do wrong [...] ?

I have attempted to find relevant info from the Debian project
for you. I found these two pages, which seem to be recently
updated by active developers:
[1] https://salsa.debian.org/raspi-team/image-specs
[2] https://wiki.debian.org/RaspberryPiImages

Quoting from [2] above:
"The new (June 2019) Raspberry Pi 4 is not yet supported
(the kernel does not yet have a Device Tree for it) "

I don't know about the Debian ARM images, but if
they were relevant then I assume they would be
mentioned at the links above.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> I have a bigger 4 amp supply  but haven't rigged it with output jumpers
> yet.

But in the specs of the RPI4 it says it requires a 3A PWR supply.

However I think it is possible that you have another issue with the SD-CARD. 

It looks to me that now with RPI4 and the bootloader placed on the device.

What I do not understand is if the net boot works or not, cause it is saying
it will be enabled by optional updates later.

regards

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas Schmitt]

Hi,

Gene Heskett wrote:
> debian-10.0.0-armhf-netinst.iso
> debian-10.0.0-arm64-netinst.iso

SD card seems to be the intended target for netboot images.
E.g.
  
http://ftp.debian.org/debian/dists/stable/main/installer-arm64/current/images/netboot/SD-card-images/

Maybe worth a try, if you can get advise about the appropriate image
for your ARM machine.

Those are not ISO9660 but rather partitioned images with a FAT32 filesystem:

  $ /sbin/fdisk -lu firmware.a64-olinuxino.img
  ...
  Disklabel type: dos
  ...
  Device  Boot StartEnd Sectors  Size Id Type
  firmware.a64-olinuxino.img1 * 2048 19  197952 96.7M  c W95 FAT32 (LBA)


Have a nice day :)

Thomas

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 02:18:38 David wrote:

> On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:
> > What did I do wrong in dd-ing
> > the net-install iso to the new 64GB u-sd card?
>
> Please give us a link so that we can identify and test whatever
> file you are calling "the net-install iso".
>
> Please show us exactly the "dd" command you used to write
> it to the sd card.
>
> If you do that, it makes it possible that we can duplicate your
> situation and/or reliably answer your question.

i should have changed the subject, thats an armhf iso, the last one I 
tried, but both were tried yesterday, same results.

The md5sum of the arm64 file
root@coyote:pi-buster$ md5sum debian-10.0.0-arm64-netinst.iso
c957472ce923bf6e0afe0f4c6a22d6c2  debian-10.0.0-arm64-netinst.iso


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Sunday 08 September 2019 02:18:38 David wrote:

> On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:
> > What did I do wrong in dd-ing
> > the net-install iso to the new 64GB u-sd card?
>
> Please give us a link so that we can identify and test whatever
> file you are calling "the net-install iso".

debian-10.0.0-armhf-netinst.iso, located on this machines main drive, 
downloaded from a debian site with FF.

md5sum=df55beefd09acd1db38e6e66cb8308c2
>
> Please show us exactly the "dd" command you used to write
> it to the sd card.

sudo dd if=debian-10.0.0-armhf-netinst.iso bs=4096 of=/dev/sdf1

/dev/sdf1 is an unmounted 64GB PNY u-sd card. Original format NTFS.

Mounting it and reading the directory after the dd write looks like I 
think it should, a directory of the iso, not the iso itself.

The rpi4b is being powered from its gpio pins 2=5.11 volts, 6=common from 
a canna kit v2.5 amp supply, which may not be enough amps as theres 2 
keyboard/mouse dongles in the usb2 ports, and a usb3 hub with two SSD's 
plugged into a usb3 (blue port) and a single micro to std hdmi plugged 
into hdmi#1. and a net cable from my garage switch plugged into the cat5 
jack.  No heat sinks, they're someplace between HongKong and WV yet. No 
detectable heating, just the red led is lit, green flashes for a very 
few milliseconds, once.

This same supply ran a rock64 with all that same stuff plugged in w/o a 
problem, running armbian on the rock64.

Dead stable until amanda touched it, crashed. Amanda is the backup 
utility of choice here, has been for 20 years now.
Amanda from your repo's crashes all arm64 installs, but thats a separate, 
different problem we'll solve later. Probably by building it from src, 
I'm used to that. NBD to me.

I have a bigger 4 amp supply  but haven't rigged it with output jumpers 
yet. 
> If you do that, it makes it possible that we can duplicate your
> situation and/or reliably answer your question.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David]

On Sun, 8 Sep 2019 at 06:59, Gene Heskett  wrote:
>
> What did I do wrong in dd-ing
> the net-install iso to the new 64GB u-sd card?

Please give us a link so that we can identify and test whatever
file you are calling "the net-install iso".

Please show us exactly the "dd" command you used to write
it to the sd card.

If you do that, it makes it possible that we can duplicate your
situation and/or reliably answer your question.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Saturday 07 September 2019 20:09:44 deloptes wrote:

> Gene Heskett wrote:
> > That is what I am trying to boot from, a 64GB u-sd with its
> > filestystem changed from NTFS to #6 (fat16) in fdisk.  May not have
> > the mbr or gpt table properly formatted. Will try gparted next.  But
> > its time I put on my chefs hat. Gotta feed us.  Not sure what yet,
> > might even be road stew!
>
> I do not think it is using GPT or MBR at all. It needs vfat in the
> beginning of the disk, so that it can load the firmware, but not sure
> how the RPI4 will look like.

google is not at all helpfull. You would think, that if they really 
wanted market share fast, such info would by now be falling all over 
itself for search engine rankings.  It doesn't seem to be.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> That is what I am trying to boot from, a 64GB u-sd with its filestystem
> changed from NTFS to #6 (fat16) in fdisk.  May not have the mbr or gpt
> table properly formatted. Will try gparted next.  But its time I put on
> my chefs hat. Gotta feed us.  Not sure what yet, might even be road
> stew!

I do not think it is using GPT or MBR at all. It needs vfat in the beginning
of the disk, so that it can load the firmware, but not sure how the RPI4
will look like.

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Saturday 07 September 2019 17:34:49 deloptes wrote:

> Gene Heskett wrote:
> > There is only a split second of activity of the green led, then it
> > just sits there, no on screen msg of any kind.  What did I do wrong
> > in dd-ing the net-install iso to the new 64GB u-sd card?
>
> Note: The Raspberry Pi 4B does not use the bootcode.bin file - instead
> the bootloader is located in an on-board EEPROM chip. The Pi 4B
> bootloader currently only supports booting from an SD card. Support
> for USB host mode boot and Ethernet boot will be added by a future
> software update. See SPI Boot EEPROM.
> https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmod
>es/README.md

That is what I am trying to boot from, a 64GB u-sd with its filestystem 
changed from NTFS to #6 (fat16) in fdisk.  May not have the mbr or gpt 
table properly formatted. Will try gparted next.  But its time I put on 
my chefs hat. Gotta feed us.  Not sure what yet, might even be road 
stew!

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Saturday 07 September 2019 17:26:33 deloptes wrote:

> Gene Heskett wrote:
> > There is only a split second of activity of the green led, then it
> > just sits there, no on screen msg of any kind.  What did I do wrong
> > in dd-ing the net-install iso to the new 64GB u-sd card?
>
> I ordered also one RPI4 few days ago, waiting for it to arrive. From
> my experience with RPI2 you need to take care of the boot loader
> first. It is not a simple process, but not sure how it looks like in
> RPI4 - I assume the same as mentioned here:
> https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteep
>rom.md
>
> To test the RPI I used TFTP boot and old 256MB sd card where I put the
> bootloader for network boot. It was much easier to compile and test
> any software on the server.
>
> The boot partition must be vfat and hold the firmware.

gpt or mbr, I see later fdisks can do either, so I changed the disk to 
#6, did a w, and rewrote the iso using the armhf net-install file. 
Putting it in the pi4, and powering it up got me the shortest flash of 
the green led I've seen, then just the red was steady nothing else, not 
even any heat from the as yet sinkless SOC. Obviously the raspi faq is 
missing valuable u-sd card prep info.  The rpi4 came in a damned near 
empty box, not even a power hookup showing, so based on that purportedly 
matching a pi3, 5.11 volts on gpio pin 2 and ground on pin 6.

Whats next?

> regards


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> There is only a split second of activity of the green led, then it just
> sits there, no on screen msg of any kind.  What did I do wrong in dd-ing
> the net-install iso to the new 64GB u-sd card?

Note: The Raspberry Pi 4B does not use the bootcode.bin file - instead the
bootloader is located in an on-board EEPROM chip. The Pi 4B bootloader
currently only supports booting from an SD card. Support for USB host mode
boot and Ethernet boot will be added by a future software update. See SPI
Boot EEPROM.
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/README.md

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

> There is only a split second of activity of the green led, then it just
> sits there, no on screen msg of any kind.  What did I do wrong in dd-ing
> the net-install iso to the new 64GB u-sd card?

I ordered also one RPI4 few days ago, waiting for it to arrive. From my
experience with RPI2 you need to take care of the boot loader first. It is
not a simple process, but not sure how it looks like in RPI4 - I assume the
same as mentioned here:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md

To test the RPI I used TFTP boot and old 256MB sd card where I put the
bootloader for network boot. It was much easier to compile and test any
software on the server.

The boot partition must be vfat and hold the firmware.

regards

attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

greetings all;

There is only a split second of activity of the green led, then it just 
sits there, no on screen msg of any kind.  What did I do wrong in dd-ing 
the net-install iso to the new 64GB u-sd card?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page