Re: Updated installer images 2020-12-03

2020-12-04 Thread Dennis Clarke
On 12/3/20 2:05 PM, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> I uploaded updated Debian installer CD images today.
> 
> These come with the latest versions of the kernel and the debian-installer
> application as well as various other updates. The images can be found at
> the usual location [1] as well as the debian-installer for netboot [2].
> 
> Known issues:
> 
> - We still don't have support for contrib and non-free, so the images are
>   missing non-free firmware. It is planned that the Debian Ports FTP server
>   will be extended to support contrib and non-free but I don't have any
>   influence on that as this is up to the Debian Ports FTP maintainers.
> 
> So far, I have tested the images on sparc64 only. Please test on the other
> architectures and report back.
> 
> Thanks,
> Adrian
> 
>> [1] https://cdimage.debian.org/cdimage/ports/snapshots/2020-12-03/
>> [2] https://cdimage.debian.org/cdimage/ports/debian-installer/2020-12-03/
> 

Install on sparc64 went smoothly. Initial first boot hangs at some
systemd related process. I will try to get logs regarding that. I was
able to boot to single user mode and then from there to bring up the
server to full multi-user mode whereupon everything seems to "just work"
and that includes the improved and fixed gcc :

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97939

Surprised that bug was in the sparc64 world since at least gcc 7.3.0.


-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional



Updated installer images 2020-12-03

2020-12-03 Thread John Paul Adrian Glaubitz
Hi!

I uploaded updated Debian installer CD images today.

These come with the latest versions of the kernel and the debian-installer
application as well as various other updates. The images can be found at
the usual location [1] as well as the debian-installer for netboot [2].

Known issues:

- We still don't have support for contrib and non-free, so the images are
  missing non-free firmware. It is planned that the Debian Ports FTP server
  will be extended to support contrib and non-free but I don't have any
  influence on that as this is up to the Debian Ports FTP maintainers.

So far, I have tested the images on sparc64 only. Please test on the other
architectures and report back.

Thanks,
Adrian

> [1] https://cdimage.debian.org/cdimage/ports/snapshots/2020-12-03/
> [2] https://cdimage.debian.org/cdimage/ports/debian-installer/2020-12-03/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Updated installer images

2017-09-11 Thread Frank Scheiner

On 09/11/2017 11:23 AM, Frank Scheiner wrote:

On 09/10/2017 07:42 PM, John Paul Adrian Glaubitz wrote:

On 09/10/2017 06:32 PM, Frank Scheiner wrote:
I yesterday tested the image from [1] (SHA256: 
b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on 
an Ultra 10. Sadly the boot loader
installation still didn't work. Unfortunately I also forgot to go 
back and check the available menu items before finishing up the 
installation without boot
loader installation. I could later on install the boot loader 
manually via the rescue mode, so a workaround is still possible with 
the current image.


Can you please re-run the installation and save the installation log 
from /var/log/syslog?


I can't really work on this problem if I don't have any debug logs.



Ok, I have two syslog files at hand (see attachments). One before 
finishing up at the "nobootloader" step and one when the installation 
was finished. Hope this helps.


I forgot to mention that this time the installer correctly detected the 
installed ATA disk. So maybe it didn't detect it last time because of 
the original partitioning. This time I already had a Sun disklabel and 
the partitions from the last try on it.




Re: Updated installer images

2017-09-11 Thread Frank Scheiner

On 09/10/2017 07:42 PM, John Paul Adrian Glaubitz wrote:

On 09/10/2017 06:32 PM, Frank Scheiner wrote:

I yesterday tested the image from [1] (SHA256: 
b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on an Ultra 
10. Sadly the boot loader
installation still didn't work. Unfortunately I also forgot to go back and 
check the available menu items before finishing up the installation without boot
loader installation. I could later on install the boot loader manually via the 
rescue mode, so a workaround is still possible with the current image.


Can you please re-run the installation and save the installation log from 
/var/log/syslog?

I can't really work on this problem if I don't have any debug logs.



Ok, I have two syslog files at hand (see attachments). One before 
finishing up at the "nobootloader" step and one when the installation 
was finished. Hope this helps.




You could try installing "silo-installer" using "anna install silo-installer" 
after
switching to a terminal using Alt+Fn keys.


Did that:
```
~ # anna install silo-installer
CAPB backup

GET anna/retriever

~ # echo $?
0
```
...but it looked like it hang after the "CAPB backup" message. Hitting 
the Enter key it emitted the "GET [...]" message and exited. Although it 
exited with 0 I don't think it worked and the installer menu also didn't 
change.


I believe these are the relevant lines from the syslog (happened after 
finishing the installation so not included in the above mentioned logs):

```
Sep 10 18:50:50 main-menu[192]: INFO: Menu item 'di-utils-shell' selected
Sep 10 18:52:06 anna[7511]: sh:
Sep 10 18:52:06 anna[7511]: /usr/lib/debian-installer/retriever/: 
Permission denied

Sep 10 18:52:06 anna[7511]:
Sep 10 18:52:06 anna[7511]: sh:
Sep 10 18:52:06 anna[7511]: /usr/lib/debian-installer/retriever/: 
Permission denied

Sep 10 18:52:06 anna[7511]:
```

I later also tried `anna-install silo-installer` but that also didn't 
change anything on the installer menu, the corresponding log entry is 
most likely this one:

```
Sep 10 18:55:54 anna-install: Installing silo-installer
```

Cheers,
Frank


syslog-after-installation-finished.gz
Description: application/gzip


syslog-before-finishing-up.gz
Description: application/gzip


Re: Updated installer images

2017-09-11 Thread Witold Baryluk
Hi John. Thanks a lot for these images for alpha, I will be trying them
soon probably, as I was unlucky with some previous ones. :)

Thanks.


2017-09-10 21:35 GMT+02:00 Anatoly Pugachev :

> On Sun, Sep 10, 2017 at 10:12 PM, Christoph Biedl
>  wrote:
> > John Paul Adrian Glaubitz wrote...
> >
> >> Please test and report back on the individual architecture
> >> mailing lists
> >
> > So far, the ride for ppc64 has been *extremely* painful. This is not
> > necessarly due to your efforts, but it feels a lot like nobody ever has
> > tried to set up Debian on a G5 using netboot.
> >
> > So far (might be incomplete, and I'm both tired and fairly upset):
> >
> > * Any reasonable documentation on this anywhere? No about how to set up
> >   DHCP/TFTP server, I've done this many time. But what about which files
> >   are needed, and how to provide a netboot-adjusted yaboot.conf, and
> >   mostly: How to make yaboot make using it?
> >
> > * The OF bootloader needs two rounds to load yaboot.
> >
> > * yaboot should either get a decent on-line help or see bitrot.
> >
> > * yaboot's "conf /path/to/config" command, when initially using netboot,
> >   happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
> >   using TFTP instead.
> >
> > * After a lot of trickery, the installer's vmlinux now gets loaded. At a
> >   whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
> >   and initrd take some 35 megabytes, and the G5 has already turned to
> >   airplane mode. My neighbors will love me.
> >
> > This isn't getting anywhere useful soon.
>
> I was able to install netboot sparc64 ldom (but not latest sid version
> , which is too big to load by OBP. There's also #645657 debian bug,
> but somehow it got closed).
>
> Also, installed ppc64 LPAR, failed to install yaboot and using grub2
> on Power8 server, but that installation wasn't netboot, but usual
> iso/cdrom install.
>
> I could probably try to install test ppc64 lpar with netboot just to
> check how it will go, but i need to know where do i get netboot image,
> since https://cdimage.debian.org/cdimage/ports/ does not have netboot
> images.
>
> Thanks
>
>


-- 
Witold Baryluk
My PGP keys for 2017-02-17 - 2019-02-17:
5B8C 48CB 8B2F CF53 CA55  0995 16D9 6FA2 20A8 F130
https://functor.xyz/pgp/witold.baryluk-gmail.gpg.asc
https://keys.mailvelope.com/pks/lookup?op=get=0x16D96FA220A8F130


Re: Updated installer images

2017-09-10 Thread Anatoly Pugachev
On Sun, Sep 10, 2017 at 10:12 PM, Christoph Biedl
 wrote:
> John Paul Adrian Glaubitz wrote...
>
>> Please test and report back on the individual architecture
>> mailing lists
>
> So far, the ride for ppc64 has been *extremely* painful. This is not
> necessarly due to your efforts, but it feels a lot like nobody ever has
> tried to set up Debian on a G5 using netboot.
>
> So far (might be incomplete, and I'm both tired and fairly upset):
>
> * Any reasonable documentation on this anywhere? No about how to set up
>   DHCP/TFTP server, I've done this many time. But what about which files
>   are needed, and how to provide a netboot-adjusted yaboot.conf, and
>   mostly: How to make yaboot make using it?
>
> * The OF bootloader needs two rounds to load yaboot.
>
> * yaboot should either get a decent on-line help or see bitrot.
>
> * yaboot's "conf /path/to/config" command, when initially using netboot,
>   happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
>   using TFTP instead.
>
> * After a lot of trickery, the installer's vmlinux now gets loaded. At a
>   whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
>   and initrd take some 35 megabytes, and the G5 has already turned to
>   airplane mode. My neighbors will love me.
>
> This isn't getting anywhere useful soon.

I was able to install netboot sparc64 ldom (but not latest sid version
, which is too big to load by OBP. There's also #645657 debian bug,
but somehow it got closed).

Also, installed ppc64 LPAR, failed to install yaboot and using grub2
on Power8 server, but that installation wasn't netboot, but usual
iso/cdrom install.

I could probably try to install test ppc64 lpar with netboot just to
check how it will go, but i need to know where do i get netboot image,
since https://cdimage.debian.org/cdimage/ports/ does not have netboot
images.

Thanks



Re: Updated installer images

2017-09-10 Thread Christoph Biedl
John Paul Adrian Glaubitz wrote...

> Please test and report back on the individual architecture
> mailing lists

So far, the ride for ppc64 has been *extremely* painful. This is not
necessarly due to your efforts, but it feels a lot like nobody ever has
tried to set up Debian on a G5 using netboot.

So far (might be incomplete, and I'm both tired and fairly upset):

* Any reasonable documentation on this anywhere? No about how to set up
  DHCP/TFTP server, I've done this many time. But what about which files
  are needed, and how to provide a netboot-adjusted yaboot.conf, and
  mostly: How to make yaboot make using it?

* The OF bootloader needs two rounds to load yaboot.

* yaboot should either get a decent on-line help or see bitrot.

* yaboot's "conf /path/to/config" command, when initially using netboot,
  happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy
  using TFTP instead.

* After a lot of trickery, the installer's vmlinux now gets loaded. At a
  whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel
  and initrd take some 35 megabytes, and the G5 has already turned to
  airplane mode. My neighbors will love me.

This isn't getting anywhere useful soon.

Christoph


signature.asc
Description: Digital signature


Re: Updated installer images

2017-09-10 Thread John Paul Adrian Glaubitz
On 09/10/2017 06:32 PM, Frank Scheiner wrote:
> I yesterday tested the image from [1] (SHA256: 
> b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on an Ultra 
> 10. Sadly the boot loader
> installation still didn't work. Unfortunately I also forgot to go back and 
> check the available menu items before finishing up the installation without 
> boot
> loader installation. I could later on install the boot loader manually via 
> the rescue mode, so a workaround is still possible with the current image.

Can you please re-run the installation and save the installation log from 
/var/log/syslog?

I can't really work on this problem if I don't have any debug logs.

> Attached are my notes. As the installer strangely didn't detect the installed 
> ATA HDD, although the kernel detected it and I could write to it with dd, the
> failing boot loader installation could possibly also be related to this issue.

We need the logfile.

> I also had a look into the netinst installer images for i386 and amd64 for 
> Debian 9.1.0. They only use one `pool` directory.
> 
> Why are two pool directories needed for sparc64? The `nobootloader` udeb 
> (all) is located below `pool`, the `silo-installer` udeb (sparc64) is located 
> below
> `pool-sparc64`. On the i386 installer ISO, e.g. the `lilo-installer` udeb is 
> located below `pool`, where there are both `all` and `i386` packages 
> available. So
> would it be possible to move or just copy the `silo-installer` udeb to the 
> pool directory structure for testing?

That's because debian-ports separates between pool and pool-$ARCH [1]. That's
not something I can change at the moment. But I also don't know whether it makes
a difference given the fact the kernel packages - linux-image-sparc64 - is also
installed from pool-sparc64.

pool = arch:all packages
pool-sparc64 = arch:sparc64 packages

In any case, we need the contents of /var/log/syslog. It might be that 
debian-installer
is picking "nobootloader" over "silo-installer" over this fact. Or it takes it 
over
"silo-installer" because silo-installer comes "unreleased" and "nobootloader" 
comes
from "unstable".

You could try installing "silo-installer" using "anna install silo-installer" 
after
switching to a terminal using Alt+Fn keys.

Adrian

> [1] http://ftp.ports.debian.org/debian-ports/

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Updated installer images

2017-09-10 Thread Frank Scheiner

Hi Adrian,

On 09/08/2017 04:22 PM, John Paul Adrian Glaubitz wrote:

[...]
Will recreate the images in the evening. Sorry for that.


I yesterday tested the image from [1] (SHA256: 
b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on an 
Ultra 10. Sadly the boot loader installation still didn't work. 
Unfortunately I also forgot to go back and check the available menu 
items before finishing up the installation without boot loader 
installation. I could later on install the boot loader manually via the 
rescue mode, so a workaround is still possible with the current image.


[1]: 
https://cdimage.debian.org/cdimage/ports/debian-9.0-sparc64-NETINST-1.iso


Attached are my notes. As the installer strangely didn't detect the 
installed ATA HDD, although the kernel detected it and I could write to 
it with dd, the failing boot loader installation could possibly also be 
related to this issue.


I also had a look into the netinst installer images for i386 and amd64 
for Debian 9.1.0. They only use one `pool` directory.


Why are two pool directories needed for sparc64? The `nobootloader` udeb 
(all) is located below `pool`, the `silo-installer` udeb (sparc64) is 
located below `pool-sparc64`. On the i386 installer ISO, e.g. the 
`lilo-installer` udeb is located below `pool`, where there are both 
`all` and `i386` packages available. So would it be possible to move or 
just copy the `silo-installer` udeb to the pool directory structure for 
testing?


Cheers and have a nice evening,
Frank

* the installer didn't detect the installed ATA HDD, although it's present in the kernel boot messages and I could write to it with busybox's dd in a shell. When I selected continue from the red screen, the disk could be used by the partitioner and I could continue with partitioning:
```

  ┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐   
  │ │   
  │ This is an overview of your currently configured partitions and mount   │   
  │ points. Select a partition to modify its settings (file system, mount   │   
  │ point, etc.), a free space to create partitions, or a device to │   
  │ initialize its partition table. │   
  │ │   
  │Guided partitioning- │   
  │Configure software RAID▒ │   
  │Configure the Logical Volume Manager   ▒ │   
  │Configure ZFS  ▒ │   
  │Configure encrypted volumes▒ │   
  │Configure iSCSI volumes0 │   
  │   ▒ │   
  │SCSI1 (0,0,0) (sda) - 40.0 GB ATA ST340810A▒ │   
  │> 40.0 GB  FREE SPACE  . │   
  │ │   
  ││   
  │ │   
  └─────────────────────────────────────────────────────────────────────────┘   

 for help;  moves;  selects;  activates buttons  
```

* Later on a kernel message displayed over the installer screen, but the installation continues. Checking in a shell yielded the following messages:
```
[ 3542.859672] mandb[2465]: segfault at 5c78 ip f801006238f4 (rpc f801006237f0) sp 07feffc91ea1 error 30001 in libc-2.24.so[f8010056c000+15e000]
[ 3542.860190] BUG: Bad rss-counter state mm:f8f1d740 idx:1 val:3
[ 3542.937756] BUG: non-zero nr_ptes on freeing mm: 1
```
I sometimes saw a rapidly increasing memory usage during mandb updates on Alpha machines with similar amounts of memory (512 MiB or less) which lead to the OOM killer starting to kill processes when no swap partition was used and heavy swapping when a swap partition was used. I'm unsure if this could be a similar issue. 

* It again does not offer the boot loader installation, but this might be due to the same reason it did not detect any disks, though there were disks detected by the kernel.




Re: Updated installer images

2017-09-08 Thread Frank Scheiner

On 09/08/2017 11:32 AM, John Paul Adrian Glaubitz wrote:

Hi!

I have generated an updated set of debian-installer images for
Debian Ports which also now includes alpha [1].

I have fixed the installation issues on hppa and sparc64, in
both cases the bootloader installer was missing.



I have now tried the latest image on an Ultra 80, everything works 
similar to the V245 until during installation of the base system (at 
about 67 %). Checking the logs, there seems to be a dependency problem 
with gnupg:


```
[...]
Sep  8 13:39:58 debootstrap: Errors were encountered while processing: 

Sep  8 13:39:58 debootstrap:  gnupg 

Sep  8 13:39:59 debootstrap: dpkg: dependency problems prevent 
configuration of
gnupg: 

Sep  8 13:39:59 debootstrap:  gnupg depends on gnupg-l10n (= 2.2.0-2); 
however:
Sep  8 13:39:59 debootstrap:   Version of gnupg-l10n on system is 
2.2.0-1.
Sep  8 13:39:59 debootstrap: 

Sep  8 13:39:59 debootstrap: dpkg: error processing package gnupg 
(--configure):
Sep  8 13:39:59 debootstrap:  dependency problems - leaving unconfigured 

Sep  8 13:39:59 debootstrap: Errors were encountered while processing: 

Sep  8 13:39:59 debootstrap:  gnupg 

Sep  8 13:40:00 debootstrap: dpkg: dependency problems prevent 
configuration of
gnupg: 


[...]
```

It looks like gnupg requires a newer version of gnupg-l10n then 
available. As I wasn't yet asked for the mirror, I assume these packages 
are from the installer disc.




Updated installer images

2017-09-08 Thread John Paul Adrian Glaubitz

Hi!

I have generated an updated set of debian-installer images for
Debian Ports which also now includes alpha [1].

I have fixed the installation issues on hppa and sparc64, in
both cases the bootloader installer was missing.

ppc64 has still some issues with the partition manager, but I'm
working on fixing that.

Please test and report back on the individual architecture
mailing lists, i.e. please don't post to debian-ports@l.d.o
as this reaches the mailing lists of all ports.

Adrian


[1] https://cdimage.debian.org/cdimage/ports/


--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Updated installer images for sparc64

2016-05-06 Thread Bryce
On 06/05/16 10:10, John Paul Adrian Glaubitz wrote:
> Bryce!
>
> Please use the images from the next day (2016-05-04) and look at the recent
> discussion on #sparc.
>
> The glibc issue has already been resolved, however we're still missing a
> symlink to /dev/cdrom which udev needs to create.
>
> I have already patched /lib/udev/rules.d/60-cdrom-info.rules (not sure whether
> I remember the filename correctly, I'm on mobile), but udev upstream won't
> accept my pull request in its current form.
>
> Adrian
>

erk,.. ok 2016-05-04's ISO pulled down,.. installing,..


  ┌┤ [!!] Install the base system ├─┐
  ┌───│ │ 
──┐
  │   │ Base system installation error  │   
│
  │   │ The debootstrap program exited with an error (return value 1).  │   
│
  │   │ │   
│
  │ Ex│ Check /var/log/syslog or see virtual console 4 for the details. │   
│
  │   │ │   
│
  └───│  │ 
──┘
  │ │
  └─┘



Something really unhappy with the serial terminal though ,.. keeps injecting [[C
[[B chars from the cursor keys which makes menu navigation really awkward. For
now I'll assume thats something in my setup
Reran install since it got impossible to navigate the menus.
blah blah install,..

ftp.debian-ports.org/debian still errors out but thats expected so skip on to 
installing the bootloader


  │  Install the SILO boot loader on a hard disk │

   ┌───┤ [!!] Finish the installation ├┐
  ┌│   │
  ││ Installation complete │
  ││ Installation is complete, so it is time to boot into your new system. │
  ││ Make sure to remove the installation media, so that you boot into the │
  ││ new system rather than restarting the installation.   │
  ││   │
  └││
   │   │
   └───┘

reboot

SPARC T7-1, No Keyboard
Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.37.0.build_27, 8. GB memory available, Serial #83457349.
Ethernet address 0:14:4f:f9:75:45, Host ID: 84f97545.



Boot device: /virtual-devices@100/channel-devices@200/disk@1  File and args:
WARNING: Unsupported bootblk image, can not extract fcode
SILO Version 1.4.14
boot:
LinuxLinuxOLD
boot:

So we spin forward through that
AH,...

[  OK  ] Reached target Network.
 Starting /etc/rc.local Compatibility...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started getty on tty2-tty6 if dbus and logind are not available.
[  OK  ] Started Getty on tty4.
[  OK  ] Started Getty on tty5.
[  OK  ] Started Getty on tty3.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Getty on tty2.
[  OK  ] Started Getty on tty6.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
 Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.


Course this is a headless install so  we need the console running on tty??..

Hurm,.. on the 2016-04-10/
 ISO, that dropped
through to a usable console fine (just looking at it now)
so,. the sunv* stuff in 2016-05-04
 looks like it's fine, 
just have to figure out where the 'console' went

Old:
root@bryce-deb:~# tty
/dev/console

/lib/udev/rules.d/90-console-setup.rules



Re: Updated installer images for sparc64

2016-05-06 Thread John Paul Adrian Glaubitz
Bryce!

Please use the images from the next day (2016-05-04) and look at the recent 
discussion on #sparc.

The glibc issue has already been resolved, however we're still missing a 
symlink to /dev/cdrom which udev needs to create.

I have already patched /lib/udev/rules.d/60-cdrom-info.rules (not sure whether 
I remember the filename correctly, I'm on mobile), but udev upstream won't 
accept my pull request in its current form.

Adrian

> On May 6, 2016, at 10:57 AM, Bryce  wrote:
> 
>> On 04/05/16 00:35, John Paul Adrian Glaubitz wrote:
>> Hi!
>> 
>> I just created two new installer images for sparc64, based on Linux
>> 4.5.2. These images contain my kernel patches which fix the automatic
>> loading of the vio modules sunvdc and sunvnet when installing in an
>> LDOM.
>> 
>>> https://people.debian.org/~glaubitz/debian-cd/2016-05-03/
>> Feedback welcome.
>> 
>> Known issues:
>> 
>> - Installing additional software packages may fail; just install
>>   a minimal set of packages.
>> 
>> - Serial console may not be enabled by default after install,
>>   see: http://0pointer.net/blog/projects/serial-console.html
>> 
>> Adrian
>> 
> 
> 
> Sorry it's taken me a while to get time to go look at this ISO set.
>   ┌──┤ [!] Detect disks ├───┐
>   │   
>   │
>   │ No disk drive was detected. If you know the name of the driver needed   │
>   │ by your disk drive, you can select it from the list.│
>   │   
>   │
>   │ Driver needed for your disk drive:  │
>   │   
>   │
>   │ continue with no disk drive │
>   │ 3w-9xxx │
> ...
>   │ sunvdc   ▒
>   │
> 
> 
> Selected sunvdc
> but the same screen panel pops back up
> 
> popped out to a shell to see if it was loaded
> ~ # lsmod
> Module  Size  Used by
> isofs  38521  1
> sunvnet20497  0
> sunvdc  9695  1
> ~ # cat /proc/partitions 
> major minor  #blocks  name
> 
>  2540 172780 vdiska
>  2541 172780 vdiska1
>  2542 172780 vdiska2
>  2543 172780 vdiska3
>  2544 172780 vdiska4
>  2545 172780 vdiska5
>  2546 172780 vdiska6
>  2547 172780 vdiska7
>  2548   33554432 vdiskb
> 
> [1762093.930815] sunvdc: module verification failed: signature and/or 
> required key missing - tainting kernel
> [1762093.931013] sunvdc.c:v1.2 (November 24, 2014)
> [1762093.937286] sunvdc: Virtual CDROM vdiska
> [1762093.937294] sunvdc: vdiska: 345560 sectors (168 MB) protocol 1.1
> [1762093.937517]  vdiska: vdiska1 vdiska2 vdiska3 vdiska4 vdiska5 vdiska6 
> vdiska7
> [1762093.941663] sunvdc: Virtual Hard disk vdiskb
> [1762093.941669] sunvdc: vdiskb: 67108864 sectors (32768 MB) protocol 1.1
> [1762093.941929] sunvnet.c:v1.0 (June 25, 2007)
> [1762093.942264] vnet_port vnet-port-0-0 eth0: Sun LDOM vnet 00:14:4f:fb:9b:94
> [1762093.942305] sunvnet: eth0: PORT ( remote-mac 00:14:4f:f8:4b:37 
> switch-port )
> 
> vdiska is the cdrom and the 8 partitions are as expected (they all point to 
> the same partition) and vdiskb is seen by the kernel
> so popped back into the install and asked it to detect disks again.
> "No disk drive was detected"
> Hurm,...
> Ok lets have a look at what partman thinks is there
> May  6 08:47:36 partman: pvscan: /lib/libc.so.6: version `GLIBC_2.22' not 
> found (required by /lib/libdevmapper.so.1.02.1)
> May  6 08:47:36 partman: vgscan: /lib/libc.so.6: version `GLIBC_2.22' not 
> found (required by /lib/libdevmapper.so.1.02.1)
> Ugh was that because I jumped the gun a little through the shell?
> 
> ~ # grep GLIBC /lib/libc.so.6 
> GLIBC_2.2
> GLIBC_2.2.1
> GLIBC_2.2.2
> GLIBC_2.2.3
> GLIBC_2.2.4
> GLIBC_2.2.6
> GLIBC_2.3
> GLIBC_2.3.2
> GLIBC_2.3.3
> GLIBC_2.3.4
> GLIBC_2.4
> GLIBC_2.5
> GLIBC_2.6
> GLIBC_2.7
> GLIBC_2.8
> GLIBC_2.9
> GLIBC_2.10
> GLIBC_2.11
> GLIBC_2.12
> GLIBC_2.13
> GLIBC_2.14
> GLIBC_2.15
> GLIBC_2.16
> GLIBC_2.17
> GLIBC_2.18
> GLIBC_PRIVATE
> GNU C Library (Debian GLIBC 2.21-9) stable release version 2.21, by Roland 
> McGrath et al.
> nooo,...ok this might explain a bit of it
> 


Re: Updated installer images for sparc64

2016-05-06 Thread Bryce
On 04/05/16 00:35, John Paul Adrian Glaubitz wrote:
> Hi!
>
> I just created two new installer images for sparc64, based on Linux
> 4.5.2. These images contain my kernel patches which fix the automatic
> loading of the vio modules sunvdc and sunvnet when installing in an
> LDOM.
>
>> https://people.debian.org/~glaubitz/debian-cd/2016-05-03/
> Feedback welcome.
>
> Known issues:
>
> - Installing additional software packages may fail; just install
>   a minimal set of packages.
>
> - Serial console may not be enabled by default after install,
>   see: http://0pointer.net/blog/projects/serial-console.html
>
> Adrian
>


Sorry it's taken me a while to get time to go look at this ISO set.

  ┌──┤ [!] Detect disks 
├───┐
  │ 
│
  │ No disk drive was detected. If you know the name of the driver needed   
│
  │ by your disk drive, you can select it from the list.
│
  │ 
│
  │ Driver needed for your disk drive:  
│
  │ 
│
  │ continue with no disk drive 
│
  │ 3w-9xxx 
│
...
  │ sunvdc   ▒  
│


Selected sunvdc
but the same screen panel pops back up

popped out to a shell to see if it was loaded

~ # lsmod
Module  Size  Used by
isofs  38521  1
sunvnet20497  0
sunvdc  9695  1

~ # cat /proc/partitions
major minor  #blocks  name

 2540 172780 vdiska
 2541 172780 vdiska1
 2542 172780 vdiska2
 2543 172780 vdiska3
 2544 172780 vdiska4
 2545 172780 vdiska5
 2546 172780 vdiska6
 2547 172780 vdiska7
 2548   33554432 vdiskb

[1762093.930815] sunvdc: module verification failed: signature and/or
required key missing - tainting kernel
[1762093.931013] sunvdc.c:v1.2 (November 24, 2014)
[1762093.937286] sunvdc: Virtual CDROM vdiska
[1762093.937294] sunvdc: vdiska: 345560 sectors (168 MB) protocol 1.1
[1762093.937517]  vdiska: vdiska1 vdiska2 vdiska3 vdiska4 vdiska5 vdiska6
vdiska7
[1762093.941663] sunvdc: Virtual Hard disk vdiskb
[1762093.941669] sunvdc: vdiskb: 67108864 sectors (32768 MB) protocol 1.1
[1762093.941929] sunvnet.c:v1.0 (June 25, 2007)
[1762093.942264] vnet_port vnet-port-0-0 eth0: Sun LDOM vnet 
00:14:4f:fb:9b:94
[1762093.942305] sunvnet: eth0: PORT ( remote-mac 00:14:4f:f8:4b:37
switch-port )

vdiska is the cdrom and the 8 partitions are as expected (they all point to the
same partition) and vdiskb is seen by the kernel
so popped back into the install and asked it to detect disks again.

"No disk drive was detected"

Hurm,...
Ok lets have a look at what partman thinks is there

May  6 08:47:36 partman: pvscan: /lib/libc.so.6: version `GLIBC_2.22' not
found (required by /lib/libdevmapper.so.1.02.1)
May  6 08:47:36 partman: vgscan: /lib/libc.so.6: version `GLIBC_2.22' not
found (required by /lib/libdevmapper.so.1.02.1)

Ugh was that because I jumped the gun a little through the shell?

~ # grep GLIBC /lib/libc.so.6
GLIBC_2.2
GLIBC_2.2.1
GLIBC_2.2.2
GLIBC_2.2.3
GLIBC_2.2.4
GLIBC_2.2.6
GLIBC_2.3
GLIBC_2.3.2
GLIBC_2.3.3
GLIBC_2.3.4
GLIBC_2.4
GLIBC_2.5
GLIBC_2.6
GLIBC_2.7
GLIBC_2.8
GLIBC_2.9
GLIBC_2.10
GLIBC_2.11
GLIBC_2.12
GLIBC_2.13
GLIBC_2.14
GLIBC_2.15
GLIBC_2.16
GLIBC_2.17
GLIBC_2.18
GLIBC_PRIVATE
GNU C Library (Debian GLIBC 2.21-9) stable release version 2.21, by Roland
McGrath et al.

nooo,...ok this might explain a bit of it




Updated installer images for sparc64

2016-05-03 Thread John Paul Adrian Glaubitz
Hi!

I just created two new installer images for sparc64, based on Linux
4.5.2. These images contain my kernel patches which fix the automatic
loading of the vio modules sunvdc and sunvnet when installing in an
LDOM.

> https://people.debian.org/~glaubitz/debian-cd/2016-05-03/

Feedback welcome.

Known issues:

- Installing additional software packages may fail; just install
  a minimal set of packages.

- Serial console may not be enabled by default after install,
  see: http://0pointer.net/blog/projects/serial-console.html

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913