kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #185891
[Bug 1596281] Re: the target drive is not found when connected via USB 3 while installing Lubuntu alternate
I continued testing the problem with
- the released version lubuntu-16.04-alternate-amd64.iso
- another adapter/box to connect the SSD via USB 3.
And this is the result:
This (new) adapter, Deltaco USB 3.0 to SATA II cable fails also with the
released version, so it is an old bug.
An (older) AKASA box for 2.5" drives to USB3 and eSATA works via USB 3
(with the released version as well as with the current daily iso file).
-o-
Both the new adapter and the old box are recognized during boot, Lubuntu
boots from them, and are recognized by the desktop live system and its
installer. So this bug seems specific for the debian installer and the
particular hardware in the Deltaco adapter (shown as Asmedia by lsusb)
'Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA
6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1596281
Title:
the target drive is not found when connected via USB 3 while
installing Lubuntu alternate
Status in linux package in Ubuntu:
Confirmed
Bug description:
While trying to install from the Lubuntu 16.04 LTS alternate amd64
daily iso file, the target drive is not found when connected via USB
3.
This happens with an SSD connected via USB 3. The corresponding
desktop iso file works, and the released Lubuntu 16.04 LTS alternate
amd64 worked.
This problematic iso file can install into the same SSD, when
connected internally (connected via SATA).
I am writing this bug report booted from Lubuntu 16.04 desktop i364
daily, and I will attach the output of some command lines to
illustrate how the SSD is recognized (and should be recognized also
but the alternate installer).
I think the the bug is located in partman, or some related tool, that
should identify connected drives.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-27-generic 4.4.0-27.46
ProcVersionSignature: Ubuntu 4.4.0-27.46-generic 4.4.13
Uname: Linux 4.4.0-27-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lubuntu 1700 F.... lxpanel
CasperVersion: 1.376
CurrentDesktop: LXDE
Date: Sun Jun 26 09:38:09 2016
LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160624)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=sv_SE.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=sv keyboard-configuration/layoutcode?=se
RelatedPackageVersions:
linux-restricted-modules-4.4.0-27-generic N/A
linux-backports-modules-4.4.0-27-generic N/A
linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.version: PSCBXE-00C00VN5
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596281/+subscriptions
References