summaryrefslogtreecommitdiffstats
path: root/mdk-stage1
Commit message (Collapse)AuthorAgeFilesLines
* 2.49Thierry Vignaud2020-10-142-1/+3
|
* sync with kernel 5.9Thierry Vignaud2020-10-141-0/+2
|
* fix version in logsThierry Vignaud2020-08-191-1/+1
|
* 2.48Thierry Vignaud2020-08-192-1/+3
|
* remove doble entryThierry Vignaud2020-08-191-0/+2
|
* 2.47Thierry Vignaud2020-06-282-1/+3
|
* sync with kernel 5.6/5.7Thierry Vignaud2020-06-281-0/+2
|
* explain /capability checkThierry Vignaud2020-06-131-0/+1
|
* 2.46Pascal Terjan2020-06-122-2/+4
|
* Do not ignore devices lacking capabilityPascal Terjan2020-06-121-1/+1
|
* Fix reading capabilityPascal Terjan2020-06-121-4/+3
|
* Use generic code for everything except DAC960Pascal Terjan2020-06-122-236/+13
|
* Update NEWSPascal Terjan2020-06-121-0/+2
|
* Move CCISS to generic codePascal Terjan2020-06-121-32/+9
|
* Move VirtIO to generic codePascal Terjan2020-06-121-36/+24
|
* Make the NVME code more genericPascal Terjan2020-06-121-6/+17
|
* Simplify NVME codePascal Terjan2020-06-121-67/+45
|
* 2.45Pascal Terjan2020-06-112-1/+3
|
* Fix NVME code to work for disks with no vendorPascal Terjan2020-06-112-22/+38
|
* 2.44Pascal Terjan2020-06-112-1/+3
|
* Add support for NVME disks (mga#26708)Pascal Terjan2020-06-112-0/+79
| | | | | The code is generic using sysfs and the only NVME specific code is the path, we should switch to it for all disks.
* 2.43Thierry Vignaud2020-03-182-1/+3
|
* sync with kernel 5.5Thierry Vignaud2020-03-181-0/+2
|
* 2.422.42Thomas Backlund2019-12-222-1/+3
|
* sync with kernel 5.4Thomas Backlund2019-12-221-0/+2
|
* 2.41Thierry Vignaud2019-10-092-1/+3
|
* sync with kernel 5.3Thierry Vignaud2019-10-091-0/+2
|
* 2.402.40Thomas Backlund2019-06-172-1/+3
|
* recognize 8821ce (mga#24605)Thierry Vignaud2019-06-111-0/+2
|
* 2.392.39Thomas Backlund2019-05-112-1/+3
|
* add AMD PCIe MP2 I2C detectionThomas Backlund2019-05-041-0/+2
|
* 2.38Thierry Vignaud2019-05-032-1/+3
|
* adapt to kernel 5.1Thierry Vignaud2019-05-031-0/+2
|
* 2.37Thierry Vignaud2019-03-082-1/+3
|
* sync with kernel 5.0Thierry Vignaud2019-03-081-0/+2
| | | | Note that we did NOT sync with 4.20
* 2.362.36Martin Whitaker2019-01-062-1/+3
|
* Suppress mount error messages when probing for media (mga#24142)Martin Whitaker2019-01-062-1/+2
| | | | | Probably caused by the switch to using the standalone mount command, the tail end of a mount error message was left showing in the GUI.
* better gcc8 workaroundsThierry Vignaud2018-12-013-5/+7
|
* 2.35Thierry Vignaud2018-12-012-1/+3
|
* gcc8 workaroundsThierry Vignaud2018-12-012-1/+2
| | | | | | | | | | | | Before previous commit, compiling with gcc8 would have need: -Wno-error=format-overflow -Wno-error=format-security But now, only -Wno-error=format-truncation is needed. rationale: gcc bogusly complains about snprintf() being unsafe. See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77721 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
* fix compiling with gcc8Thierry Vignaud2018-12-014-5/+7
|
* 2.34Thierry Vignaud2018-11-302-1/+3
|
* drop our own old unmaintained forked nfs codeThierry Vignaud2018-11-305-1329/+1
| | | | | we now got support for all NFS features, including NFSv4 & co server likely needs to be configured with 'insecure'
* switch to using regular mount for nfsThierry Vignaud2018-11-303-8/+1
|
* simplify now that we use standalone mountThierry Vignaud2018-11-302-10/+3
| | | | | | Let mount uses the blkid library for guessing the filesystem type That's quite a lot better than manually trying a long list of potential fses
* actually call regular mountThierry Vignaud2018-11-302-3/+14
| | | | now that we've it in stage1 anyway (since using dracut)
* 2.332.33Thierry Vignaud2018-11-302-1/+3
|
* add support for disk-iso auto-installThierry Vignaud2018-11-302-5/+23
| | | | | | eg: "method:disk,disk:vdb,partition:vdb1,dir:/Mageia/boot.iso" in the future, we might want to merge back !automatic & automatic paths
* check for builtin modules in /sys/fs tooThierry Vignaud2018-11-292-0/+7
| | | | | | | | eg: ext4 is builtin but appears in /sys/fs, not in /sys/modules Alternatively we could have looked at /proc/filesytem contents like stage2 Thus we've better readable stage1 logs
* advertize "ext4" rather than "ext2"Thierry Vignaud2018-11-295-4/+6
|