holy smokes. I deleted the part, created ext4 on it, then mkswap'ed it, and I'm
booting!
On December 6, 2024 11:31:51 AM EST, Felix Miata wrote:
>tomas composed on 2024-12-06 10:47 (UTC+0100):
>
>> On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
>>> aha.
>
>>> booted a live USB. on
On Fri 06 Dec 2024 at 19:14:51 (+), Chris Green wrote:
> nsrxnst wrote:
> > [-- text/plain, encoding quoted-printable, charset: utf-8, 70 lines --]
> >
> > The machine was gifted, and I was just so happy I could get Debian to boot
>
> That doesn't mean what you intended! (at least not to m
nsrxnst wrote:
> [-- text/plain, encoding quoted-printable, charset: utf-8, 70 lines --]
>
> The machine was gifted, and I was just so happy I could get Debian to boot
That doesn't mean what you intended! (at least not to me it didn't)
It means the machine was clever (in itself). What you mea
The machine was gifted, and I was just so happy I could get Debian to boot then
I never really investigated the hardware or thought much about it.
it looks like there is a solution floating around this thread that I'm going to
be trying.
I have a Lenovo running Deb 12. The MacBook was
having dug through all the functioning partitions, I have concluded it is my
swap partition. I even had the intuition to reformat the swap partition. I'm
going to try the no resume option and see if that does it.
On December 6, 2024 11:31:51 AM EST, Felix Miata wrote:
>tomas composed on 2024-12
tomas composed on 2024-12-06 10:47 (UTC+0100):
> On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
>> aha.
>> booted a live USB. one of the partitions is now of type "swsuspend". my
>> sleuthing has led me to decide it's a corrupted fs.
> I've got a different hunch from the others expre
On Thu, Dec 05, 2024 at 09:39:55PM -0500, nsrxnst wrote:
> aha.
>
> booted a live USB. one of the partitions is now of type "swsuspend". my
> sleuthing has led me to decide it's a corrupted fs.
I've got a different hunch from the others expressed in this
thread: your computer is trying to resto
Greg Wooledge composed on 2024-12-05 21:41 (UTC-0500):
> Assuming you use GRUB (I don't know whether a "MacBook pro 2014" is an
> amd64 system), you should be able to interrupt the boot sequence, press
Apple didn't drop Intel CPUs until 2023. My iMac 2007 is an Intel
On 12/5/24 18:03, nsrxnst wrote:
while I was at work, chaos happened in my house. my wife cleaned my office, and
her nephew locked himself in there.
my Debian install has never been ideal: the GUI is spotty, but the underlying
system has always functioned just fine, and to that extent, I have
On 12/5/24 21:39, nsrxnst wrote:
> booted a live USB. one of the partitions is now of type "swsuspend". my
> sleuthing has led me to decide it's a corrupted fs.
>
> how do I go about recovering this???
If you do something like
mount /dev/sda1 /mnt/temp -o ro -t ext4
(modify as appropriate)
doe
On 12/5/24 21:03, nsrxnst wrote:
> upon selecting the appropriate option from grub, manually or
> automatically, it begins the boot process, displays errors too fast to
> comprehend,
You may be able to read the errors if you video-record the screen during
boot (higher fps=better) then single-step
So the first thing I'd do is boot without the
GUI.
Assuming you use GRUB (I don't know whether a "MacBook pro 2014" is an
amd64 system), you should be able to interrupt the boot sequence, press
the 'e' key to edit the boot parameters, and add
systemd.unit=multi-us
aha.
booted a live USB. one of the partitions is now of type "swsuspend". my
sleuthing has led me to decide it's a corrupted fs.
how do I go about recovering this???
On December 5, 2024 9:03:45 PM EST, nsrxnst wrote:
>while I was at work, chaos happened in my house. my wife cleaned my office,
while I was at work, chaos happened in my house. my wife cleaned my office, and
her nephew locked himself in there.
my Debian install has never been ideal: the GUI is spotty, but the underlying
system has always functioned just fine, and to that extent, I have used it as a
home server.
it was
On Fri, Nov 10, 2023 at 9:16 AM Kent West wrote:
>
>
> On Thu, Nov 9, 2023 at 10:39 PM Timothy M Butterworth <
> timothy.m.butterwo...@gmail.com> wrote:
>
>>
>>
>> On Thu, Nov 9, 2023 at 11:31 PM Kent West wrote:
>>
>>> I have an M1-
On Thu, Nov 9, 2023 at 10:39 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Thu, Nov 9, 2023 at 11:31 PM Kent West wrote:
>
>> I have an M1-chip 2020 MacBook Air on which I have dual-booted with
>> Debian 12 initially, then "up
4:44, Kent West wrote:
> > I have an M1-chip 2020 MacBook Air on which I have dual-booted with
> > Debian 12 initially, then "upgraded" to sid (in hopes of getting
> > better hardware support).
>
>
> Out of curiosity, does Debian 12 support
On Thu, Nov 9, 2023 at 11:31 PM Kent West wrote:
> I have an M1-chip 2020 MacBook Air on which I have dual-booted with Debian
> 12 initially, then "upgraded" to sid (in hopes of getting better hardware
> support). It has several hardware ... glitches, and my google-fu is fail
On 10/11/23 04:44, Kent West wrote:
I have an M1-chip 2020 MacBook Air on which I have dual-booted with
Debian 12 initially, then "upgraded" to sid (in hopes of getting
better hardware support).
Out of curiosity, does Debian 12 support the M1 NPU (Neural Processing
Unit) ?
Am 09.11.2023 um 14:44:20 Uhr schrieb Kent West:
> Not even from "speaker-test" after I've killed X/Wayland/gdm3, although
> "speaker-test" (as a non-root user) looks like it's working. It acts
> like the speakers are muted, but I can find no way to unmute them.
> When I run "speaker-test" as root
I have an M1-chip 2020 MacBook Air on which I have dual-booted with Debian
12 initially, then "upgraded" to sid (in hopes of getting better hardware
support). It has several hardware ... glitches, and my google-fu is failing
me in finding solutions. I'm hoping someone here can he
* 2023-06-13 01:37:36-0400, Timothy M. Butterworth wrote:
> Thanks for the info. I successfully installed Debian 12 on the MacBook
> Pro.
> The only thing I do not like is the bright white screen that shows up
> with the chime. It stays on for a long time with no status display
On Fri, Jun 9, 2023 at 2:47 AM Teemu Likonen wrote:
> * 2023-06-08 19:32:13-0400, Timothy M. Butterworth wrote:
>
> > I have a 2012 MacBook Pro that I am going to install Debian Bookworm on.
> I
> > will not be keeping OSX on the Mac as it is no longer supported for
> >
On Thu, Jun 8, 2023 at 9:27 PM Dan Ritter wrote:
> Timothy M Butterworth wrote:
> > All,
> >
> > I have a 2012 MacBook Pro that I am going to install Debian Bookworm on.
> I
> > will not be keeping OSX on the Mac as it is no longer supported for
> > updates.
Timothy M Butterworth wrote:
> All,
>
> I have a 2012 MacBook Pro that I am going to install Debian Bookworm on. I
> will not be keeping OSX on the Mac as it is no longer supported for
> updates. Does anyone have any tips or tricks for installing Debian on a
> MacBook Pro?
The
All,
I have a 2012 MacBook Pro that I am going to install Debian Bookworm on. I
will not be keeping OSX on the Mac as it is no longer supported for
updates. Does anyone have any tips or tricks for installing Debian on a
MacBook Pro?
Thanks
Tim
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal
On Sat, May 06, 2023 at 09:13:19PM -0500, Mike Zelenak wrote:
> Hi, I am new here. Can anybody help me with this; I have a 2021 Macbook
> Pro 16" and am trying to install Debian via USB to USB C.
I can't help you with MAC, but perhaps with finding someone who could.
A couple of
Ok, since this is how it works I keep it that way.
I thank everyone for the tips and advice.
Francesco
Well if MacOSX is no longer booting immediately, then it appears installing
rEFInd solved your initial problem, so that is good.
rEFInd is quite configurable via refind.conf, but you may find it is
simpler to just ignore the Windows icon rather than try to force it not to
appear. The hairy details
Hello,
thanks for the help and suggestions:
I don't need to press alt (option) to view the operating systems because I have
rEFInd installed.
However, 2 Debian icons appear, one OS X, and one Windows.
If I click on the latter, a white writing on a black background appears with:
MBR 12: and a flas
ran...@libero.it wrote:
>> I installed Debian 11 (386) on a 2009 Macbook Pro 13 "(5.5).
>>
>> The installation did not give me any problems except it did not detect wifi
>> card and touchpad, but I was connected with ethernet and used an external
>> mouse, so the
> On Nov 24, 2021, at 11:11 AM, David Wright wrote:
>
> On Wed 24 Nov 2021 at 14:59:09 (+0100), fran...@libero.it wrote:
>> I installed Debian 11 (386) on a 2009 Macbook Pro 13 "(5.5).
>>
>> The installation did not give me any problems except it did not detect
On Wed 24 Nov 2021 at 14:59:09 (+0100), fran...@libero.it wrote:
> I installed Debian 11 (386) on a 2009 Macbook Pro 13 "(5.5).
>
> The installation did not give me any problems except it did not detect wifi
> card and touchpad, but I was connected with ethernet and used an exte
Hello,
I installed Debian 11 (386) on a 2009 Macbook Pro 13 "(5.5).
The installation did not give me any problems except it did not detect wifi
card and touchpad, but I was connected with ethernet and used an external
mouse, so the whole process ended.
During the installation phase of G
e "should" work reasonably well, regardless of the
>> underlying firmware. Are you booting via EFI or via the "legacy BIOS"
>> (which at some point was referred to as BootCamp)? You may want to try
>> the other one, just to see if it helps.
>
> I used t
> I also used hibernate as well as the LXDE controls or closing the lid -
> the result is always the same:
>
> 1. Black screen
> 2. Network disabled (ssh session freezes, no ping from other host)
> 3. Fan keeps on moving silently
> 4. Can't wake up to normal operation neither by
> -
u booting via EFI or via the "legacy BIOS"
> (which at some point was referred to as BootCamp)? You may want to try
> the other one, just to see if it helps.
I used the installer default which is EFI. I admit I have no idea how
to convince that MacBook to use something else. Its t
Hi,
I've got some MacBook from 2008 to install Debian on it and hand it over
to some user who needs a decent office machine. I've installed Bullseye
RC1 which worked nicely (except that I had to manually add WLAN driver
broadcom-sta-dkms later).
The only real flaw is that neither s
machine dedicated to Debian.
That sounds like a good solution for trying Debian.
I suggest that you create a macOS bootable installer USB flash drive
before installing Debian, so that you can reinstall macOS on your
MacBook if you so choose:
https://support.apple.com/en-us/HT201372
David
AM riveravaldez
wrote:
> On 4/17/21, David Christensen wrote:
> > On 4/17/21 8:39 AM, Thanos Katsiolis wrote:
> >> Hello,
> >>
> >> I am a new user who would like to try Debian.
> >>
> >> I have a MacBook Pro (Early 11) which runs Mac OS,
On 4/17/21, David Christensen wrote:
> On 4/17/21 8:39 AM, Thanos Katsiolis wrote:
>> Hello,
>>
>> I am a new user who would like to try Debian.
>>
>> I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to
>> also
>> install Deb
On 4/17/21 8:39 AM, Thanos Katsiolis wrote:
Hello,
I am a new user who would like to try Debian.
I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
install Debian. Will I have any issues installing Debian regarding hardware?
I would also appreciate it if you have any
On Sat, Apr 17, 2021 at 06:39:50PM +0300, Thanos Katsiolis wrote:
> Hello,
>
> I am a new user who would like to try Debian.
>
> I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
> install Debian. Will I have any issues installing Debian regarding h
Hello,
I am a new user who would like to try Debian.
I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
install Debian. Will I have any issues installing Debian regarding hardware?
I would also appreciate it if you have any tips before the installation as
well as if there
Sorry, just realised that i forgot to CC Carl on my response. In case
he's not reading the list:
Andy Cater wrote:
>On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
>> Can anyone please help me with this installation?
>>
>> https://wiki.debian.org/Installing
Andy Cater wrote:
>On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
>> Can anyone please help me with this installation?
>>
>> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
>>
>> the line:
>> grub-install --target=i386-efi --efi-dire
On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
> Can anyone please help me with this installation?
>
> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
>
> the line:
> grub-install --target=i386-efi --efi-directory=/mnt/usb
> --boot-directory=/mnt/usb
Can anyone please help me with this installation?
https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
the line:
grub-install --target=i386-efi --efi-directory=/mnt/usb
--boot-directory=/mnt/usb/boot --bootloader-id=boot --removable
I try this and it says 'doesn't look like a
gt;>> So that we can help you further
>>>
>>> On Fri, Dec 18, 2020, 2:38 PM himani agarwal wrote:
>>>
>>>> I downloaded the bullseye alpha 3 installer,
>>>> firmware-bullseye-DI-alpha3-amd64-DVD-1.iso
>>>> MD5: a1e967406869b1b0b64a1
I downloaded the bullseye alpha 3 installer,
firmware-bullseye-DI-alpha3-amd64-DVD-1.iso
MD5: a1e967406869b1b0b64a1b808d39dd1a
My computer is a Macbook Air 2020
I shrank the Apple partition, disabled secure boot and I was able to
boot with the Debian installer.
The keyboard, mouse, wifi and
> - use a USB wireless dongle instead of your integrated wireless card.
OK, I will try that and I will let you know how it went
I have no other option, so I will have to offer myself as some sort
of guinea pig and waste time/effort exploring such territories
Thank you very much,
lbrtchx
>
Le mardi 10 novembre 2020 à 14:20:06 UTC+1, Albretch Mueller a écrit :
[...]
> // __ nach installation: ls -l "/lib/firmware/b43"
[...]
> -rw-r--r-- 1 root root 31176 Nov 7 17:59 ucode11.fw
[...]
> // __ journalctl | grep -i firmware
> Nov 07 17:44:06 debian kernel: acpi PNP0A08:00: [Firmware
OK, here is the whole log of the script I ran to install the b43 drivers.
It is a bit long, but you will certainly be able to quickly visually
scan it and see where teh error is/might be.
Yes, I am descending onto init 2 after I used a live DVD. I am OK
with doing that every time. I can't conn
Le jeudi 5 novembre 2020 à 12:00:06 UTC+1, Albretch Mueller a écrit :
> > "ip l" (for "ip link") lists the network links the kernel is aware of.
> $ ip l
> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN
> mode DEFAULT group default qlen 1
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>
Albretch Mueller wrote:
> and I run dmesg before and after the installation. This is what I got as
> diff:
>
> $ _IFL00="demsg_Wed Nov 4 13:36:51 UTC 2020.log"
> $ _IFL02="dmesg_Wed Nov 4 12:51:11 UTC 2020.log"
>
>
> $ diff "${_IFL00}" "${_IFL02}"
> 1365,1386d1364
> < [ 592.364045] fuse in
and I run dmesg before and after the installation. This is what I got as diff:
$ _IFL00="demsg_Wed Nov 4 13:36:51 UTC 2020.log"
$ _IFL02="dmesg_Wed Nov 4 12:51:11 UTC 2020.log"
$ diff "${_IFL00}" "${_IFL02}"
1365,1386d1364
< [ 592.364045] fuse init (API version 7.26)
< [ 597.114432] perf: i
> "ip l" (for "ip link") lists the network links the kernel is aware of.
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
$ sudo iwconfig
lono wireless extensions.
> And to keep it simple, doe
Le mardi 3 novembre 2020 à 12:10:06 UTC+1, Albretch Mueller a écrit :
> > sudo modprobe b43
>
> Doesn't show to me anything.
>
> and
>
> > ip l
>
> displays a sequence of 0:0:0:0:0: ... chars which don't look like a
> MAC address or any of such things
>
>
> lbrtchx
"modprobe b43" tries
> sudo modprobe b43
Doesn't show to me anything.
and
> ip l
displays a sequence of 0:0:0:0:0: ... chars which don't look like a
MAC address or any of such things
lbrtchx
Albretch Mueller wrote:
> However, I don't see the wireless card being activated (its LED
> blinking) nor do I see the network-manager showing me any connections
> and, of course, if I reboot that laptop I will lose those folders.
Copy them to a USB stick? There's nothing system-specific about
t
stall"
on the target computer (a MacBook Air 1,1). All the data was compited
onto "/lib/firmware/b43" as it should.
However, I don't see the wireless card being activated (its LED
blinking) nor do I see the network-manager showing me any connections
and, of course, if I reboot tha
Le jeudi 22 octobre 2020 à 16:00:06 UTC+2, Albretch Mueller a écrit :
[...]
> what should I do now?
Follow the link Dan Ritter gave to you earlier:
http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/#other_distros
it indicates to install (dpkg -i or apt install) b43-fwcutter
and then:
OK, after installing lspci (again, via dpkg and I write up in kind of
a step by step way because other people may have the same problems,
run into this thread)
$ sudo dpkg --install pciutils_3.5.2-1_amd64.deb
Selecting previously unselected package pciutils.
(Reading database ... 232551 files and
Le jeudi 22 octobre 2020 à 12:30:06 UTC+2, Albretch Mueller a écrit :
> > I suggest using firmware-b43-installer ...
>
> Once again, I am using dpkg and installing the deb packages locally
> because I am trying to troubleshoot, make a wireless card work.
>
> Why would a package used to make a
Albretch Mueller wrote:
> > I suggest using firmware-b43-installer ...
>
> Once again, I am using dpkg and installing the deb packages locally
> because I am trying to troubleshoot, make a wireless card work.
>
> Why would a package used to make a wireless card come to live, have
> to connect
> I suggest using firmware-b43-installer ...
Once again, I am using dpkg and installing the deb packages locally
because I am trying to troubleshoot, make a wireless card work.
Why would a package used to make a wireless card come to live, have
to connect to the Internet to do its things? Isn't
On Wed, Oct 21, 2020 at 4:51 PM Albretch Mueller wrote:
> I got that tar ball and I think i am doing the right thing, but
> something is not going well:
The firmware-b43-installer package uses b43-fwcutter to extract the
firmware from the tarball, I suggest using firmware-b43-installer
instead o
I got that tar ball and I think i am doing the right thing, but
something is not going well:
$ _IFL="broadcom-wl-5.100.138.tar.bz2"
$ ls -l "${_IFL}"
-rwxrwxrwx 1 root root 13514651 Aug 13 2011 broadcom-wl-5.100.138.tar.bz2
$ file --brief "${_IFL}"
bzip2 compressed data, block size = 900k
$ s
On Wed, Oct 21, 2020 at 12:43 PM Albretch Mueller wrote:
> Thank you for all the leads and I was installing
> firmware-b43-installer via dpkg, but after I took care of all
> dependencies firmware-b43-installer was trying to connect to the
> Internet to some lwfinder?
>
> Resolving http://www.lw
Albretch Mueller wrote:
> > apt install firmware-b43-installer
> > will be needed, I think.
>
> Thank you for all the leads and I was installing
> firmware-b43-installer via dpkg, but after I took care of all
> dependencies firmware-b43-installer was trying to connect to the
> Internet to some
> apt install firmware-b43-installer
> will be needed, I think.
Thank you for all the leads and I was installing
firmware-b43-installer via dpkg, but after I took care of all
dependencies firmware-b43-installer was trying to connect to the
Internet to some lwfinder?
Resolving http://www.lwfing
Albretch Mueller wrote:
> I test a MacBook Air 1,1 with Debian Live DVD
>
> $ uname -a
> Linux debian 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
> x86_64 GNU/Linux
>
> and all seems to be fine and dandy, except for the wireless network
> card. This is w
I test a MacBook Air 1,1 with Debian Live DVD
$ uname -a
Linux debian 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
x86_64 GNU/Linux
and all seems to be fine and dandy, except for the wireless network
card. This is what dmidecode and hwinfo tell me about it:
Model: "Apple Ai
On 17/12/19 5:46 am, Kent West wrote:
Unless things have changed recently (and I don't believe they have), you
could also run "sudo tasksel" and pick the Desktop Environment[s] you
prefer.
Just worked for me, when I tried it just for fun
--
Keith Bainbridge
keith.bainbridge.3...@gmail.co
12:04:09 PM, Dan Ritter wrote:
> > Dr. Jason Amerson wrote:
> > > Hello,
> > >
> > > Me again. Different computer with a different problem. I may ask about
> other computers later. I am in the process of migrating my laptops from
> Windows 10 to Debian. This computer is
ain. Different computer with a different problem. I may ask about
> > other computers later. I am in the process of migrating my laptops from
> > Windows 10 to Debian. This computer is a Macbook Pro. I installed Debian
> > without errors, not even network errors like my other co
Dr. Jason Amerson wrote:
> Hello,
>
> Me again. Different computer with a different problem. I may ask about other
> computers later. I am in the process of migrating my laptops from Windows 10
> to Debian. This computer is a Macbook Pro. I installed Debian without errors,
>
Hello,
Me again. Different computer with a different problem. I may ask about other
computers later. I am in the process of migrating my laptops from Windows 10 to
Debian. This computer is a Macbook Pro. I installed Debian without errors, not
even network errors like my other computer. I
Dear Developers of the most amazing OS,
I Triple booted macbook pro but the hibernation feature of debian wont let
me go in my debian partition since it is still thinking its in hibernation
so it black screens for hours and over heated my macbook pro so how do i
fix hibernation i also need you to
Hello Lina,
On 12/04/2019 02:44, lina wrote:
> Hi,
>
> When I tried to install the Debian on latest MacBook Pro, I found the
> keyboard and the touchpad does not work.
>
> It is just the beginning, I know I will meet lots of problems,
>
> Is there any link providin
I also cann't detect the SSD partition I made for debian even I
installed the refind.
On Thu, Apr 11, 2019 at 3:44 PM lina wrote:
>
> Hi,
>
> When I tried to install the Debian on latest MacBook Pro, I found the
> keyboard and the touchpad does not work.
>
> It is ju
Hi,
When I tried to install the Debian on latest MacBook Pro, I found the
keyboard and the touchpad does not work.
It is just the beginning, I know I will meet lots of problems,
Is there any link providing the information how to install and set up
the debian on the latest version? The one I can
>> Really? I thought his old drive was SATA (hence his worries that his
>> new drive would need new drivers).
> No, the old original drive is PCIe 3.0 x4 AHCI. The new one is PCIe 3.0
> x4 NVMe.
If we can't get the two drives connected to the same system at the same
time, I guess I'd use a third
On 17/11/2018 16:50, Stefan Monnier wrote:
Really? I thought his old drive was SATA (hence his worries that his
new drive would need new drivers).
No, the old original drive is PCIe 3.0 x4 AHCI. The new one is PCIe 3.0
x4 NVMe.
>> 1- take out the old SSD and put it into an external reader that you can
>>connect via USB
> I think that's going to be difficult-to-expensive: it's not a
> SATA SSD, it connects through NVMe PCIe.
Really? I thought his old drive was SATA (hence his worries that his
new drive would need new
On 17 Nov 2018, at 16:06, Stefan Monnier wrote:
> Didn't use LVM? Too bad: that means there's a risk your new dirve and
> partitions will get new identifiers so your fstab may need to be adjusted.
Ehm.. no.. I didn’t!
> macOS doesn't touch EFI, AFAIK, so don't expect the Time Machine to
> touch
Stefan Monnier wrote:
> 1- take out the old SSD and put it into an external reader that you can
>connect via USB
I think that's going to be difficult-to-expensive: it's not a
SATA SSD, it connects through NVMe PCIe.
There are external boxes that can support PCIe via Thunderbolt,
but the chea
> 4 23.2GB 31.2GB 8000MB linux-swap(v1) swap
> 5 31.4GB 121GB 89.8GB ext4linux
Didn't use LVM? Too bad: that means there's a risk your new dirve and
partitions will get new identifiers so your fstab may need to be adjusted.
> Now, here is what I would perform:
>
>
On 16/11/2018 14:46, Stefan Monnier wrote:
I would expect the clone to work just fine. I'd expect your initrd
contains drivers for both SATA and NVMe anyway.
OK. Now that I know that initrd does contain NVMe drivers, I would ask
whether my strategy for cloning is sensible.
Firstly, here's m
Stefan Monnier wrote:
>> I've got 8 of them:
>
> So you should be all set.
It is worth trying, though Appli plays always dirty, but chances are good.
> I've got 8 of them:
So you should be all set.
Stefan
On 16/11/2018 14:46, Stefan Monnier wrote:
I would expect the clone to work just fine. I'd expect your initrd
contains drivers for both SATA and NVMe anyway.
But it's easy to check:
zcat /boot/initrd.img- | cpio -vt | grep nvm
will show you the relevant files in the your initrd.
You shou
> However my main concern is with the linux partition. How can I migrate it?
> If I simply clone the linux partition from the old drive to the new drive,
> I fear something would go wrong, as the new drive is different and would
> require different drivers, missing in the original linux system.
I
Another issue I have is--how to migrate my debian system from the old
original SSD to the new larger SSD?
As for macOS [1], it should be easy. There is a macOS application called
Time Machine that allows to backup macOS from the old SSD and to restore
it to the new SSD. This would work with a
On 15/11/2018 21:48, deloptes wrote:
Check first if someone has used it on your type
of hardware and what is the feedback - I assume you are not the first. NVMe
is working fine - debian provide the kernel which provides the support and
I have seen M.2 working just fine
Late 2016 - Mid 2017 MacB
solitone wrote:
> The thing is the form factor, which unfortunately is proprietary [1].
> The connector resembles the standard M.2, but in fact is different.
OK this is a valid argument. Check first if someone has used it on your type
of hardware and what is the feedback - I assume you are not th
On 15/11/2018 21:01, deloptes wrote:
I also do not think you have to stick to this specific
drive (JetDrive 850) - perhaps macOS certified, but from linux perspective
it would make no difference.
The thing is the form factor, which unfortunately is proprietary [1].
The connector resembles the
solitone wrote:
> What do you think in terms of compatibility with debian? What worries me
> is that JetDrive 850 requires macOS version 10.13 or later, and I wonder
> whether debian supports it. Is this only a matter of NVMe (macOS
> supports NVMe starting from version 10.13; linux since kernel v
Hi, I've got a compatibility question regarding SSDs.
I run debian 9.6 on a MacBookPro12,1 (Early 2015, 13"). I'm thinking of
upgrading the stock 128 GB SSD [1]. Specifically, I'm considering the
Trascend JetDrive 850 [2].
The original SSD uses a PCIe 3.0 x4 interface and the AHCI protocol.
On 09.01.2018 08:39, john doe wrote:
> On 1/9/2018 8:30 AM, juh wrote:
>> Is there a hack to boot such a Macbook from USB or do I have to buy a
>> new cd drive?
>>
>
> http://www.idownloadblog.com/2015/09/14/how-to-start-up-mac-from-bootable-media/
Strange. I tried t
1 - 100 of 255 matches
Mail list logo
