Earlier quoted context omitted.
No, I have to set it to the latest version (I think? I have acpi_osi="Windows 2019") for things to work correctly
Which kernel version are you running? That string was added in 5.4.
5.11
Initial M1 support merged into Linux SoC tree
321–330 of 337 posts
Re: Initial M1 support merged into Linux SoC tree
#322Re: Initial M1 support merged into Linux SoC tree
#323Earlier quoted context omitted.
Thank you so much for the work put in to documentation; written in kernel or blogged, and streamed. I've watched hours of your streams. I've been working on a bootloader and porting Linux to the Nintendo 3DS; I don't really know what I'm doing, but your streams clarified many questions I had about porting Linux to a new device.
This is so awesome dude! Please let us know where we can find more about your project :D
https://github.com/linux-3ds
https://github.com/linux-3ds/linux/wiki/Table-of-Contents
It's not my project in the sense that I didn't start it, or do most of the work; I just enjoy contributing some fixes here and there and its my first experience working on a bootloader. There's a ton of great documentation (from the community, and ARM) at https://www.3dbrew.org/wiki/Main_Page as well as existing code to reference from others in the community. So I'm still in awe of how marcan goes about finding out how the hardware works without documentation from Apple (which IIUC he has done before with the Wii and BootMii).
I'm hoping to put out a release soon, and maybe stream some development on https://www.twitch.tv/ndesaulniers, then pursue upstreaming what we have.
Re: Initial M1 support merged into Linux SoC tree
#324Earlier quoted context omitted.
Last time I checked, the Android Emulator running on Apple Silicon still has issues and isn't functionally as good as running it on an Intel Mac. There is no point in getting the M1 Macbook (which is last year's model) since they will either announce a M1X or even a M2 Macbook this year which will most certainly be more performant and optimised than the last generation. One of the several reasons why I stayed away fr…
And once the M2 is released there is no point in getting it anymore since then it's the outdated model and the next one will be announced soon ;).
Except that the difference is that I explicitly stated 'first generation of Apple Silicon Macs'.
Apple is known to frequently update their Macbook line up every year so I am in no hurry to upgrade my Intel Macbook, until they eventually 'start' the process of removing Intel support which by then a third or forth generation Apple Silicon Mac will be available.
Plenty of time to wait and use what already works, rather than jumping on early tech and then finding out that the software support is still WIP or in preview state.
Re: Initial M1 support merged into Linux SoC tree
#325Earlier quoted context omitted.
Last time I checked, the Android Emulator running on Apple Silicon still has issues and isn't functionally as good as running it on an Intel Mac. There is no point in getting the M1 Macbook (which is last year's model) since they will either announce a M1X or even a M2 Macbook this year which will most certainly be more performant and optimised than the last generation. One of the several reasons why I stayed away fr…
> There is no point in getting the M1 Macbook since they will either announce a M1X or even a M2 Macbook this year I've been hearing something similar when I got a PS4 in summer 2019. PS5 is still barely available, and I've had almost 2 years of gaming fun. To be fair, the PS4 didn't have as many rough edges back then. But "no point" is a generalization that isn't true for many people.
The hardware upgrade cycle of the Playstation is much longer than an Apple Macbook. Even longer if you only include significant architectural updates.
I only apply this rule to Apple as they seem to think that people upgrade their Macs like they upgrade their iPhones which is every year.
Re: Initial M1 support merged into Linux SoC tree
#326After reading articles last year on Linus insinuating it would be "unlikely" that Linux would appear on the M1 [1] [2], I drank the cool-aid and took that at face value. I guess I should have known better, just like nature, open source "finds a way". [1] https://www.realworldtech.com/forum/?threadid=196533&curpost... [2] https://news.ycombinator.com/item?id=25216680 etc..
There was a time when saying you didn't know how to do x on Linux forums got insults and RTFM replies, but saying that Linux was an incapable of doing x got helpful instructions given in exquisite detail. It did sound a bit like a taunt to enlist the community in figuring it out.
Late Pieter Hintjens of ZeroMQ (and more) openly admitted to using this hack if he needed to have work done. State that something is impossible and watch developers tumble over each other to get it done and prove you wrong.
Re: Initial M1 support merged into Linux SoC tree
#327Earlier quoted context omitted.
This matches my experience with a 2-in-1 Thinkpad. Obscure bugs (WiFi driver periodically crashing when Thunderbolt is connected) still there after 2 years now. I think the best bet is going with as much of a run off the mill device as possible. In my experience a separate tablet works much better than a 2-in-1 compromise anyway. When your sole input device is a touchscreen, UX is (unsurprisingly) massively better wi…
The problem isn't the "compromise" - the problem is there is no touch-first UI on Linux. That's the point. I can detach the screen and use it as a "seperate tablet", but it still sucks. Android, on the other hand, is strictly improved by the addition of a hardware keyboard.
> there is no touch-first UI on Linux
If you’re still looking, you could check out JingOS. I haven’t tried it personally but it seems to be basically an iPadOS desktop environment for Linux.
Re: Initial M1 support merged into Linux SoC tree
#328I say this as a long-time PC user; MacBook laptop hardware is unrivaled in the PC space (trackpad, screen and keyboard - not pure price/performance). Having any distro running Gnome 40 with full gesture support would be seriously compelling for daily driving.
Yep, I've been looking for a linux laptop for a while that is actually compelling compared to my mac book pro. It seems just about everything is a downgrade in terms of shitty trackpads, lower resolution screens, memory, etc. Linux UI is not a problem for me; I can deal with that. The hardware is a problem though. Here's what I want: - Something that is faster than the last Apple laptop I loved which, I bought in 201…
Something like a Thinkpad X1 extreme? Or maybe have a look at the P series - I vaguely remember something like the P51s might fit your bill - the modern equiv. They have a better keyboard than any previous macbook, and up to a 4K screen, up to 64Gb RAM. Shame it doesn't have Ryzen like my 8-core X13 has. Should have all the ports. Thinkpads don't have quite the fit and finish that macbooks do - but they come from a different background/purpose - toughness rather than look/feel. However, more recent Thinkpads are looking smarter these days compared to the bricks of yore (which I liked BTW). My X13 has a magnesium under chassis and glass fibre lid.
Re: Initial M1 support merged into Linux SoC tree
#329Earlier quoted context omitted.
The problem isn't the "compromise" - the problem is there is no touch-first UI on Linux. That's the point. I can detach the screen and use it as a "seperate tablet", but it still sucks. Android, on the other hand, is strictly improved by the addition of a hardware keyboard.
> there is no touch-first UI on Linux If you’re still looking, you could check out JingOS. I haven’t tried it personally but it seems to be basically an iPadOS desktop environment for Linux.
No thanks; it's a closed source GPL-violating fork of Plasma Mobile with heavy (and sketchy) marketing.
Re: Initial M1 support merged into Linux SoC tree
#330Earlier quoted context omitted.
The Emacs startup failure may be due to bad preferences left behind by Emacs in ~/.emacs.d; try moving those aside or deleting them.
Don't think so. It's telling me there's an issue with the binary's signature. (I'm using a macbook air M1, so maybe it works fine with x86) In any case I guess it'll get fixed eventually.
For whatever it's worth, you can launch Emacs from the command line.
cd /Applications/Emacs.app/Contents/MacOS
./Emacs-arm64-11_2