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
    sunvnet                20497  0
    sunvdc                  9695  1

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

     254        0     172780 vdiska
     254        1     172780 vdiska1
     254        2     172780 vdiska2
     254        3     172780 vdiska3
     254        4     172780 vdiska4
     254        5     172780 vdiska5
     254        6     172780 vdiska6
     254        7     172780 vdiska7
     254        8   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


Reply via email to