| 2014-10-02 10:24:51 |
Kick In |
bug |
|
|
added bug |
| 2014-10-02 10:30:08 |
Kick In |
description |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had delete the raid an go to 2 separate disk to take advantage of the SSD (involved reinstalling secondary OS).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standards name /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added of being able to destroy the raid it if we let the default /dev/sda for grub install of utopic desktop.
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable,.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it elsewhere, but at install selction of disks and partitions, it is also a bit confusing as it show txo devices /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus /dev/sda, /dev/sdb I don't remember, if we saw partitions on the equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine).
You can find some hardware infos about the config there:
http://paste.ubuntu.com/8478288/ |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid it if we let the default /dev/sda for grub install of utopic desktop.
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable,.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
|
| 2014-10-02 10:37:10 |
Kick In |
description |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid it if we let the default /dev/sda for grub install of utopic desktop.
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable,.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid it if we let the default /dev/sda for grub install of utopic desktop.
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable,.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
|
| 2014-10-02 10:38:36 |
Kick In |
description |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid it if we let the default /dev/sda for grub install of utopic desktop.
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable,.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install).
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
|
| 2014-10-02 11:12:25 |
Kick In |
affects |
linux-ports-meta (Ubuntu) |
linux (Ubuntu) |
|
| 2014-10-02 11:30:09 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2014-10-02 11:52:26 |
Kick In |
tags |
|
apport-collected utopic |
|
| 2014-10-02 11:52:27 |
Kick In |
description |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install).
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/ |
Hi,
I have a MSI GS60E Ghost Pro laptop. It is quite complex:
2 SSD in raid 0 (intel Raid)
1 HDD standard SATA
2 Gpus (intel and nvidia)
I was trying to upgrade my trusty to utopic.
On trusty if I remember well there was no way to have a functionnal intel raid disks. I had to delete the raid an go to 2 separate disks to take advantage of the SSD (involved reinstalling secondary OS used for gaming).
Legacy boot:
On utopic, I can now use it but the name of the device is still strange (don't know if it is expected, but on other scsi harware I had I always had standard names /dev/sdx...):
/dev/mapper/isw_ihbcddegh_SSD, where SSD is the name given at raid creation of the volume.
Despite of this device I still have access to bare device /dev/sda, /dev/sdb, with the added bonus of being able to destroy the raid on it if we let the default /dev/sda for grub install of utopic desktop (destroyed at the end of install).
At install time we see /dev/mapper/isw_.... /dev/sda /dev/sdb and /dev/sdc, but it is readable on legacy installer even if not ideal.
UEFI boot:
If we boot on UEFI, it is more complex, as grub is not able to find the windows bootmanager for unknown reason (maybe not related).
Don't know if I need to put it somewhere else, but at the install selection of disks and partitions, it is also a bit confusing as it show two devices for the raid /dev/mapper/isw_.... each with the copy of the partitions (split the raid) plus bare devices, /dev/sda, /dev/sdb. I don't remember, if I saw partitions on the bare devices equaly.
I can make some undestructive tests for you (had hard time at making a working install on this machine). If really needed, I can switch to work on an other laptop, and go for destructive tests.
You can find some hardware infos about the config there, setup, etc:
http://paste.ubuntu.com/8478288/
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kick 3322 F.... pulseaudio
/dev/snd/controlC2: kick 3322 F.... pulseaudio
/dev/snd/controlC1: kick 3322 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=46a8dc48-0696-4cc1-9ba5-6718ccae8802
InstallationDate: Installed on 2014-10-01 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: Micro-Star International Co., Ltd. GS60 2PE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-17-generic root=UUID=71fadb93-5ab3-4fab-98d7-e558816e33a0 ro quiet splash blacklist=nouveau
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
RelatedPackageVersions:
linux-restricted-modules-3.16.0-17-generic N/A
linux-backports-modules-3.16.0-17-generic N/A
linux-firmware 1.134
Tags: utopic
Uname: Linux 3.16.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H2IMS.10B
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16H2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H2IMS.10B:bd08/16/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H2:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GS60 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd. |
|
| 2014-10-02 11:52:29 |
Kick In |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222268/+files/AlsaInfo.txt |
|
| 2014-10-02 11:52:31 |
Kick In |
attachment added |
|
BootDmesg.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222269/+files/BootDmesg.txt |
|
| 2014-10-02 11:52:33 |
Kick In |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222270/+files/CRDA.txt |
|
| 2014-10-02 11:52:35 |
Kick In |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222271/+files/CurrentDmesg.txt |
|
| 2014-10-02 11:52:36 |
Kick In |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222272/+files/IwConfig.txt |
|
| 2014-10-02 11:52:38 |
Kick In |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222273/+files/Lspci.txt |
|
| 2014-10-02 11:52:40 |
Kick In |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222274/+files/Lsusb.txt |
|
| 2014-10-02 11:52:41 |
Kick In |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222275/+files/ProcCpuinfo.txt |
|
| 2014-10-02 11:52:43 |
Kick In |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222276/+files/ProcEnviron.txt |
|
| 2014-10-02 11:52:44 |
Kick In |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222277/+files/ProcInterrupts.txt |
|
| 2014-10-02 11:52:46 |
Kick In |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222278/+files/ProcModules.txt |
|
| 2014-10-02 11:52:47 |
Kick In |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222279/+files/PulseList.txt |
|
| 2014-10-02 11:52:50 |
Kick In |
attachment added |
|
RfKill.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222280/+files/RfKill.txt |
|
| 2014-10-02 11:52:53 |
Kick In |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222281/+files/UdevDb.txt |
|
| 2014-10-02 11:52:58 |
Kick In |
attachment added |
|
UdevLog.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222282/+files/UdevLog.txt |
|
| 2014-10-02 11:53:00 |
Kick In |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1376661/+attachment/4222283/+files/WifiSyslog.txt |
|
| 2014-10-02 16:33:07 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-07-22 08:31:49 |
Kick In |
removed subscriber Kick In |
|
|
|
