Re: Why do ARM images for Leap 15.6 have names with 15.5 in the file name?

2024-05-03 Thread Lubos Kocman
Many thanks Guillaume! accepted.

On Fri, May 3, 2024 at 9:06 AM Guillaume Gardet
 wrote:
>
> Hi,
>
> > -Original Message-
> > From: Freek de Kruijf 
> > Sent: Friday, April 26, 2024 6:32 PM
> > To: arm@lists.opensuse.org
> > Subject: Re: Why do ARM images for Leap 15.6 have names with 15.5 in the 
> > file
> > name?
> >
> > Op vrijdag 26 april 2024 18:01:50 CEST schreef Andreas Schwab:
> > > On Apr 26 2024, Freek de Kruijf wrote:
> > > > Looking in
> > > > http://download.opensuse.org/distribution/leap/15.6/appliances,
> > > > which obviously is about Leap 15.6 I only find file names with 15.5
> > > > in the names. Why?
> > >
> > > Because openSUSE:Leap:15.6:Images/JeOS has never been updated.
> >
> > So whoever can do that, please update the names.
>
> The fix is on the way:
> https://build.opensuse.org/request/show/1171524
>
> Guillaume
>
>
> >
> > --
> > fr.gr.
> >
> > member openSUSE
> > Freek de Kruijf
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose the 
> contents to any other person, use it for any purpose, or store or copy the 
> information in any medium. Thank you.



-- 

Best regards


Luboš Kocman
openSUSE Leap Release Manager


Raspberry Pi 3B no longer starts after reboot

2024-05-03 Thread Robert Munteanu
Hi,

I have a RPi 3B running Leap 15.5. I have recently replaced the failing
SD card about three weeks ago and all was well.

After a zypper patch + reboot cycle it failed to connect to the
network.

Connecting via a serial cable shows that it hangs at 'Reached basic
system'. The early boot messages don't tell me that much, there seem to
be some errors, pasted at the end of the message.

I mounted the SD card in another machine, looks to mount just fine

NAME   MAJ:MIN RM   SIZE RO TYPE 
MOUNTPOINTS
sda  8:01  59.4G  0 disk  
├─sda1   8:1164M  0 part 
/run/media/robert/EFI
├─sda2   8:21   500M  0 part  
└─sda3   8:31   6.8G  0 part 
/run/media/robert/ROOT

dmesg complains about 'not properly unmounted', but that should not be
a big issue

[229713.544212] scsi 0:0:0:0: Direct-Access Generic  STORAGE DEVICE
1402 PQ: 0 ANSI: 6
[229713.544584] sd 0:0:0:0: Attached scsi generic sg0 type 0
[229713.788123] sd 0:0:0:0: [sda] 124669952 512-byte logical blocks:
(63.8 GB/59.4 GiB)
[229713.789352] sd 0:0:0:0: [sda] Write Protect is off
[229713.789357] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[229713.790605] sd 0:0:0:0: [sda] Write cache: disabled, read cache:
enabled, doesn't support DPO or FUA
[229713.800319]  sda: sda1 sda2 sda3
[229713.800711] sd 0:0:0:0: [sda] Attached SCSI removable disk
[229714.844629] FAT-fs (sda1): Volume was not properly unmounted. Some
data may be corrupt. Please run fsck.
[229715.016300] EXT4-fs (sda3): mounted filesystem f9dbd32e-e10c-4b7c-
b75e-1e0dfabdca45 r/w with ordered data mode. Quota mode: none.

I ran fsck, the only thing that it did was clear the dirty bit

$ sudo fsck /dev/sda1
fsck from util-linux 2.39.3
fsck.fat 4.2 (2021-01-31)
Dirty bit is set. Fs was not properly unmounted and some data may be
corrupt.
1) Remove dirty bit
2) No action
[12?q]? 1

*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave
the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged
[12?q]? 1
/dev/sda1: 292 files, 4395/32695 clusters

How can I further check for problems?

Thanks,
Robert

Full early boot message below:

U-Boot 2021.10 (Aug 04 2022 - 12:00:00 +)

DRAM:  992 MiB
RPI 3 Model B (0xa02082)
MMC:   mmc@7e202000: 0, mmcnr@7e30: 1
Loading Environment from FAT... Unable to read "uboot.env" from
mmc0:1... In:serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e98: USB DWC2
scanning bus usb@7e98 for devices... 3 USB Device(s) found
   scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:3...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk m...@7e202000.blk...
No valid Btrfs found
Card did not respond to voltage select! : -110
Scanning disk mm...@7e30.blk...
Disk mm...@7e30.blk not ready
Found 4 disks
Missing RNG device for EFI_RNG_PROTOCOL
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
** Invalid partition 4 **
Couldn't find partition mmc 0:4
No valid Btrfs found
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
BootOrder not defined
EFI boot manager: Cannot load any image
Found EFI removable media binary efi/boot/bootaa64.efi
1509376 bytes read in 67 ms (21.5 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Booting /efi\boot\bootaa64.ef


RE: Why do ARM images for Leap 15.6 have names with 15.5 in the file name?

2024-05-03 Thread Guillaume Gardet
Hi,

> -Original Message-
> From: Freek de Kruijf 
> Sent: Friday, April 26, 2024 6:32 PM
> To: arm@lists.opensuse.org
> Subject: Re: Why do ARM images for Leap 15.6 have names with 15.5 in the file
> name?
>
> Op vrijdag 26 april 2024 18:01:50 CEST schreef Andreas Schwab:
> > On Apr 26 2024, Freek de Kruijf wrote:
> > > Looking in
> > > http://download.opensuse.org/distribution/leap/15.6/appliances,
> > > which obviously is about Leap 15.6 I only find file names with 15.5
> > > in the names. Why?
> >
> > Because openSUSE:Leap:15.6:Images/JeOS has never been updated.
>
> So whoever can do that, please update the names.

The fix is on the way:
https://build.opensuse.org/request/show/1171524

Guillaume


>
> --
> fr.gr.
>
> member openSUSE
> Freek de Kruijf
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.