1 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
2 |
DENIED
|
moderate
|
App\Entity\Entry {#1566
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-m-trying-to-run-VirtualBox-in-Linux-Mint-but-I"
+title: "I'm trying to run VirtualBox in Linux Mint but I keep getting an error message about Kernel drivers."
+url: null
+body: """
\n
\n
I tried looking into this myself but I couldn’t really find much about this error. The only solutions I could find didn’t work for me. The first one was to use mokutil but at the point where I was supposed to run `sudo mokutil --import MOK.der` it gives me the error message “Failed to get file status, MOK.der” even though I did everything it told me to do. The other one was to disable secure boot and then run `sudo ‘/sbin/vboxconfig’` but even though it looked like it worked, I’m still getting the error message. I have re-enabled secure boot, so you don’t have to worry about that.\n
\n
Is there something else I can try or does VirtualBox not work in Linux Mint for some reason?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 67
+favouriteCount: 55
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1700031440 {#1567
date: 2023-11-15 07:57:20.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1629 …}
+votes: Doctrine\ORM\PersistentCollection {#1626 …}
+reports: Doctrine\ORM\PersistentCollection {#1625 …}
+favourites: Doctrine\ORM\PersistentCollection {#2411 …}
+notifications: Doctrine\ORM\PersistentCollection {#2465 …}
+badges: Doctrine\ORM\PersistentCollection {#2459 …}
+children: []
-id: 12408
-titleTs: "'driver':19 'error':15 'get':13 'keep':12 'kernel':18 'linux':8 'm':2 'messag':16 'mint':9 'run':5 'tri':3 'virtualbox':6"
-bodyTs: "'/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':3 '/sbin/vboxconfig':86 'boot':81,108 'could':24 'couldn':12 'didn':26 'disabl':79 'els':121 'enabl':106 'error':19,56,100 'even':64,88 'everyth':68 'fail':58 'file':61 'find':15,25 'first':32 'get':60,98 'give':53 'import':50 'lemmy.ml':2 'lemmy.ml/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':1 'like':92 'linux':131 'look':6,91 'm':96 'messag':57,101 'mint':132 'mok.der':51,63 'mokutil':37,49 'much':16 'one':33,76 'point':41 're':105 're-en':104 'realli':14 'reason':135 'run':47,84 'secur':80,107 'solut':22 'someth':120 'status':62 'still':97 'sudo':48,85 'suppos':45 'though':65,89 'told':70 'tri':5,124 'use':36 'virtualbox':127 'work':28,94,129 'worri':115"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1699924870
+visibility: "visible "
+apId: "https://lemmy.ml/post/7887071"
+editedAt: null
+createdAt: DateTimeImmutable @1699838470 {#1414
date: 2023-11-13 02:21:10.0 +01:00
}
} |
|
Show voter details
|
3 |
DENIED
|
edit
|
App\Entity\Entry {#1566
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-m-trying-to-run-VirtualBox-in-Linux-Mint-but-I"
+title: "I'm trying to run VirtualBox in Linux Mint but I keep getting an error message about Kernel drivers."
+url: null
+body: """
\n
\n
I tried looking into this myself but I couldn’t really find much about this error. The only solutions I could find didn’t work for me. The first one was to use mokutil but at the point where I was supposed to run `sudo mokutil --import MOK.der` it gives me the error message “Failed to get file status, MOK.der” even though I did everything it told me to do. The other one was to disable secure boot and then run `sudo ‘/sbin/vboxconfig’` but even though it looked like it worked, I’m still getting the error message. I have re-enabled secure boot, so you don’t have to worry about that.\n
\n
Is there something else I can try or does VirtualBox not work in Linux Mint for some reason?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 67
+favouriteCount: 55
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1700031440 {#1567
date: 2023-11-15 07:57:20.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1629 …}
+votes: Doctrine\ORM\PersistentCollection {#1626 …}
+reports: Doctrine\ORM\PersistentCollection {#1625 …}
+favourites: Doctrine\ORM\PersistentCollection {#2411 …}
+notifications: Doctrine\ORM\PersistentCollection {#2465 …}
+badges: Doctrine\ORM\PersistentCollection {#2459 …}
+children: []
-id: 12408
-titleTs: "'driver':19 'error':15 'get':13 'keep':12 'kernel':18 'linux':8 'm':2 'messag':16 'mint':9 'run':5 'tri':3 'virtualbox':6"
-bodyTs: "'/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':3 '/sbin/vboxconfig':86 'boot':81,108 'could':24 'couldn':12 'didn':26 'disabl':79 'els':121 'enabl':106 'error':19,56,100 'even':64,88 'everyth':68 'fail':58 'file':61 'find':15,25 'first':32 'get':60,98 'give':53 'import':50 'lemmy.ml':2 'lemmy.ml/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':1 'like':92 'linux':131 'look':6,91 'm':96 'messag':57,101 'mint':132 'mok.der':51,63 'mokutil':37,49 'much':16 'one':33,76 'point':41 're':105 're-en':104 'realli':14 'reason':135 'run':47,84 'secur':80,107 'solut':22 'someth':120 'status':62 'still':97 'sudo':48,85 'suppos':45 'though':65,89 'told':70 'tri':5,124 'use':36 'virtualbox':127 'work':28,94,129 'worri':115"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1699924870
+visibility: "visible "
+apId: "https://lemmy.ml/post/7887071"
+editedAt: null
+createdAt: DateTimeImmutable @1699838470 {#1414
date: 2023-11-13 02:21:10.0 +01:00
}
} |
|
Show voter details
|
4 |
DENIED
|
moderate
|
App\Entity\Entry {#1566
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-m-trying-to-run-VirtualBox-in-Linux-Mint-but-I"
+title: "I'm trying to run VirtualBox in Linux Mint but I keep getting an error message about Kernel drivers."
+url: null
+body: """
\n
\n
I tried looking into this myself but I couldn’t really find much about this error. The only solutions I could find didn’t work for me. The first one was to use mokutil but at the point where I was supposed to run `sudo mokutil --import MOK.der` it gives me the error message “Failed to get file status, MOK.der” even though I did everything it told me to do. The other one was to disable secure boot and then run `sudo ‘/sbin/vboxconfig’` but even though it looked like it worked, I’m still getting the error message. I have re-enabled secure boot, so you don’t have to worry about that.\n
\n
Is there something else I can try or does VirtualBox not work in Linux Mint for some reason?
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 67
+favouriteCount: 55
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1700031440 {#1567
date: 2023-11-15 07:57:20.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#1629 …}
+votes: Doctrine\ORM\PersistentCollection {#1626 …}
+reports: Doctrine\ORM\PersistentCollection {#1625 …}
+favourites: Doctrine\ORM\PersistentCollection {#2411 …}
+notifications: Doctrine\ORM\PersistentCollection {#2465 …}
+badges: Doctrine\ORM\PersistentCollection {#2459 …}
+children: []
-id: 12408
-titleTs: "'driver':19 'error':15 'get':13 'keep':12 'kernel':18 'linux':8 'm':2 'messag':16 'mint':9 'run':5 'tri':3 'virtualbox':6"
-bodyTs: "'/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':3 '/sbin/vboxconfig':86 'boot':81,108 'could':24 'couldn':12 'didn':26 'disabl':79 'els':121 'enabl':106 'error':19,56,100 'even':64,88 'everyth':68 'fail':58 'file':61 'find':15,25 'first':32 'get':60,98 'give':53 'import':50 'lemmy.ml':2 'lemmy.ml/pictrs/image/b73d1a34-9ad8-4640-8bd4-996ba6e25d17.png)':1 'like':92 'linux':131 'look':6,91 'm':96 'messag':57,101 'mint':132 'mok.der':51,63 'mokutil':37,49 'much':16 'one':33,76 'point':41 're':105 're-en':104 'realli':14 'reason':135 'run':47,84 'secur':80,107 'solut':22 'someth':120 'status':62 'still':97 'sudo':48,85 'suppos':45 'though':65,89 'told':70 'tri':5,124 'use':36 'virtualbox':127 'work':28,94,129 'worri':115"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1699924870
+visibility: "visible "
+apId: "https://lemmy.ml/post/7887071"
+editedAt: null
+createdAt: DateTimeImmutable @1699838470 {#1414
date: 2023-11-13 02:21:10.0 +01:00
}
} |
|
Show voter details
|
5 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
6 |
DENIED
|
moderate
|
App\Entity\Entry {#2371
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "What-would-be-the-best-way-for-me-to-recover"
+title: "What would be the best way for me to recover data from my old laptop's hard drive, which seems to have a bad superblock?"
+url: null
+body: """
I got an external hard drive enclosure for the purpose of recovering some of the files from my old laptops hard drive. The hard drive and all of it’s partitions show up in both disks and gparted but it wont mount. When I tried to mount it manually, it gave the error message stating that it can’t read the superblock. I’ve never had to deal with this issue before, so the only things I’ve tried so far were fsck and the data recovery option in GParted, and neither of them helped.\n
\n
I tried searching about it online but all of the solutions I found online either didn’t work or required methods that are currently not possible for me. The hard drive had Ubuntu (22.04 if I remember correctly) installed on it and I just need access to the files in the sdd3 partition, which was formatted in ext4.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 24
+favouriteCount: 54
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1711562628 {#2457
date: 2024-03-27 19:03:48.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2370 …}
+votes: Doctrine\ORM\PersistentCollection {#2470 …}
+reports: Doctrine\ORM\PersistentCollection {#2469 …}
+favourites: Doctrine\ORM\PersistentCollection {#2364 …}
+notifications: Doctrine\ORM\PersistentCollection {#2380 …}
+badges: Doctrine\ORM\PersistentCollection {#2382 …}
+children: []
-id: 24820
-titleTs: "'bad':24 'best':5 'data':11 'drive':18 'hard':17 'laptop':15 'old':14 'recov':10 'seem':20 'superblock':25 'way':6 'would':2"
-bodyTs: "'22.04':129 'access':141 'correct':133 'current':119 'data':86 'deal':68 'didn':111 'disk':36 'drive':6,22,25,126 'either':110 'enclosur':7 'error':53 'ext4':153 'extern':4 'far':81 'file':16,144 'format':151 'found':108 'fsck':83 'gave':51 'got':2 'gpart':38,90 'hard':5,21,24,125 'help':95 'instal':134 'issu':71 'laptop':20 'manual':49 'messag':54 'method':116 'mount':42,47 'need':140 'neither':92 'never':65 'old':19 'onlin':101,109 'option':88 'partit':31,148 'possibl':121 'purpos':10 'read':60 'recov':12 'recoveri':87 'rememb':132 'requir':115 'sdd3':147 'search':98 'show':32 'solut':106 'state':55 'superblock':62 'thing':76 'tri':45,79,97 'ubuntu':128 've':64,78 'wont':41 'work':113"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1703624123
+visibility: "visible "
+apId: "https://lemmy.ml/post/9748611"
+editedAt: null
+createdAt: DateTimeImmutable @1703537723 {#2460
date: 2023-12-25 21:55:23.0 +01:00
}
} |
|
Show voter details
|
7 |
DENIED
|
edit
|
App\Entity\Entry {#2371
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "What-would-be-the-best-way-for-me-to-recover"
+title: "What would be the best way for me to recover data from my old laptop's hard drive, which seems to have a bad superblock?"
+url: null
+body: """
I got an external hard drive enclosure for the purpose of recovering some of the files from my old laptops hard drive. The hard drive and all of it’s partitions show up in both disks and gparted but it wont mount. When I tried to mount it manually, it gave the error message stating that it can’t read the superblock. I’ve never had to deal with this issue before, so the only things I’ve tried so far were fsck and the data recovery option in GParted, and neither of them helped.\n
\n
I tried searching about it online but all of the solutions I found online either didn’t work or required methods that are currently not possible for me. The hard drive had Ubuntu (22.04 if I remember correctly) installed on it and I just need access to the files in the sdd3 partition, which was formatted in ext4.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 24
+favouriteCount: 54
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1711562628 {#2457
date: 2024-03-27 19:03:48.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2370 …}
+votes: Doctrine\ORM\PersistentCollection {#2470 …}
+reports: Doctrine\ORM\PersistentCollection {#2469 …}
+favourites: Doctrine\ORM\PersistentCollection {#2364 …}
+notifications: Doctrine\ORM\PersistentCollection {#2380 …}
+badges: Doctrine\ORM\PersistentCollection {#2382 …}
+children: []
-id: 24820
-titleTs: "'bad':24 'best':5 'data':11 'drive':18 'hard':17 'laptop':15 'old':14 'recov':10 'seem':20 'superblock':25 'way':6 'would':2"
-bodyTs: "'22.04':129 'access':141 'correct':133 'current':119 'data':86 'deal':68 'didn':111 'disk':36 'drive':6,22,25,126 'either':110 'enclosur':7 'error':53 'ext4':153 'extern':4 'far':81 'file':16,144 'format':151 'found':108 'fsck':83 'gave':51 'got':2 'gpart':38,90 'hard':5,21,24,125 'help':95 'instal':134 'issu':71 'laptop':20 'manual':49 'messag':54 'method':116 'mount':42,47 'need':140 'neither':92 'never':65 'old':19 'onlin':101,109 'option':88 'partit':31,148 'possibl':121 'purpos':10 'read':60 'recov':12 'recoveri':87 'rememb':132 'requir':115 'sdd3':147 'search':98 'show':32 'solut':106 'state':55 'superblock':62 'thing':76 'tri':45,79,97 'ubuntu':128 've':64,78 'wont':41 'work':113"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1703624123
+visibility: "visible "
+apId: "https://lemmy.ml/post/9748611"
+editedAt: null
+createdAt: DateTimeImmutable @1703537723 {#2460
date: 2023-12-25 21:55:23.0 +01:00
}
} |
|
Show voter details
|
8 |
DENIED
|
moderate
|
App\Entity\Entry {#2371
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "What-would-be-the-best-way-for-me-to-recover"
+title: "What would be the best way for me to recover data from my old laptop's hard drive, which seems to have a bad superblock?"
+url: null
+body: """
I got an external hard drive enclosure for the purpose of recovering some of the files from my old laptops hard drive. The hard drive and all of it’s partitions show up in both disks and gparted but it wont mount. When I tried to mount it manually, it gave the error message stating that it can’t read the superblock. I’ve never had to deal with this issue before, so the only things I’ve tried so far were fsck and the data recovery option in GParted, and neither of them helped.\n
\n
I tried searching about it online but all of the solutions I found online either didn’t work or required methods that are currently not possible for me. The hard drive had Ubuntu (22.04 if I remember correctly) installed on it and I just need access to the files in the sdd3 partition, which was formatted in ext4.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 24
+favouriteCount: 54
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1711562628 {#2457
date: 2024-03-27 19:03:48.0 +01:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2370 …}
+votes: Doctrine\ORM\PersistentCollection {#2470 …}
+reports: Doctrine\ORM\PersistentCollection {#2469 …}
+favourites: Doctrine\ORM\PersistentCollection {#2364 …}
+notifications: Doctrine\ORM\PersistentCollection {#2380 …}
+badges: Doctrine\ORM\PersistentCollection {#2382 …}
+children: []
-id: 24820
-titleTs: "'bad':24 'best':5 'data':11 'drive':18 'hard':17 'laptop':15 'old':14 'recov':10 'seem':20 'superblock':25 'way':6 'would':2"
-bodyTs: "'22.04':129 'access':141 'correct':133 'current':119 'data':86 'deal':68 'didn':111 'disk':36 'drive':6,22,25,126 'either':110 'enclosur':7 'error':53 'ext4':153 'extern':4 'far':81 'file':16,144 'format':151 'found':108 'fsck':83 'gave':51 'got':2 'gpart':38,90 'hard':5,21,24,125 'help':95 'instal':134 'issu':71 'laptop':20 'manual':49 'messag':54 'method':116 'mount':42,47 'need':140 'neither':92 'never':65 'old':19 'onlin':101,109 'option':88 'partit':31,148 'possibl':121 'purpos':10 'read':60 'recov':12 'recoveri':87 'rememb':132 'requir':115 'sdd3':147 'search':98 'show':32 'solut':106 'state':55 'superblock':62 'thing':76 'tri':45,79,97 'ubuntu':128 've':64,78 'wont':41 'work':113"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1703624123
+visibility: "visible "
+apId: "https://lemmy.ml/post/9748611"
+editedAt: null
+createdAt: DateTimeImmutable @1703537723 {#2460
date: 2023-12-25 21:55:23.0 +01:00
}
} |
|
Show voter details
|
9 |
DENIED
|
ROLE_USER
|
null |
|
Show voter details
|
10 |
DENIED
|
moderate
|
App\Entity\Entry {#2381
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-used-mokutil-a-while-back-but-now-it-s-preventing"
+title: "I used mokutil a while back but now it's preventing me from booting into other OSs. How do I properly disable it?"
+url: null
+body: """
I need to reinstall Linux Mint but MOK Management is preventing me from booting into the live CD. I tried looking for a solution online but (assuming I did everything correctly) I couldn’t find anything that actually worked for me. How do I properly disable it?\n
\n
Also, I forgot to mention that I do have access to Linux Mint, I just have to run it in recovery mode because it wont boot normally.\n
\n
Update: I was able to bypass MOK using my password, I still wasn’t able to disable it but I was at least able to boot into my Live CD for Linux Mint and I’m in the process of reinstalling it. I would prefure if I could just disable MOK but I at least know how to work around it.\n
\n
Update 2: I have fully reinstalled and updated Linux Mint but for some reason everything looks different despite the fact that I’m using the same settings and software I was before everything broke. But whatever, outside of the fact that I no longer have the dual boot menu and instead I get a string of text saying “booting in insecure mode” for some reason, it seems to be working fine.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 3
+favouriteCount: 21
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1719088547 {#2384
date: 2024-06-22 22:35:47.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2383 …}
+votes: Doctrine\ORM\PersistentCollection {#1906 …}
+reports: Doctrine\ORM\PersistentCollection {#1708 …}
+favourites: Doctrine\ORM\PersistentCollection {#1410 …}
+notifications: Doctrine\ORM\PersistentCollection {#1907 …}
+badges: Doctrine\ORM\PersistentCollection {#1407 …}
+children: []
-id: 27941
-titleTs: "'back':6 'boot':14 'disabl':22 'mokutil':3 'oss':17 'prevent':11 'proper':21 'use':2"
-bodyTs: "'2':137 'abl':78,89,98 'access':57 'actual':38 'also':48 'anyth':36 'around':134 'assum':27 'boot':14,73,100,183,194 'broke':169 'bypass':80 'cd':18,104 'correct':31 'could':122 'couldn':33 'despit':153 'differ':152 'disabl':46,91,124 'dual':182 'everyth':30,150,168 'fact':155,175 'find':35 'fine':206 'forgot':50 'fulli':140 'get':188 'insecur':196 'instead':186 'know':130 'least':97,129 'linux':5,59,106,144 'live':17,103 'longer':179 'look':21,151 'm':110,158 'manag':9 'mention':52 'menu':184 'mint':6,60,107,145 'mode':69,197 'mok':8,81,125 'need':2 'normal':74 'onlin':25 'outsid':172 'password':84 'prefur':119 'prevent':11 'process':113 'proper':45 'reason':149,200 'recoveri':68 'reinstal':4,115,141 'run':65 'say':193 'seem':202 'set':162 'softwar':164 'solut':24 'still':86 'string':190 'text':192 'tri':20 'updat':75,136,143 'use':82,159 'wasn':87 'whatev':171 'wont':72 'work':39,133,205 'would':118"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1704724204
+visibility: "visible "
+apId: "https://lemmy.ml/post/10247900"
+editedAt: DateTimeImmutable @1719190893 {#2378
date: 2024-06-24 03:01:33.0 +02:00
}
+createdAt: DateTimeImmutable @1704664704 {#2379
date: 2024-01-07 22:58:24.0 +01:00
}
} |
|
Show voter details
|
11 |
DENIED
|
edit
|
App\Entity\Entry {#2381
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-used-mokutil-a-while-back-but-now-it-s-preventing"
+title: "I used mokutil a while back but now it's preventing me from booting into other OSs. How do I properly disable it?"
+url: null
+body: """
I need to reinstall Linux Mint but MOK Management is preventing me from booting into the live CD. I tried looking for a solution online but (assuming I did everything correctly) I couldn’t find anything that actually worked for me. How do I properly disable it?\n
\n
Also, I forgot to mention that I do have access to Linux Mint, I just have to run it in recovery mode because it wont boot normally.\n
\n
Update: I was able to bypass MOK using my password, I still wasn’t able to disable it but I was at least able to boot into my Live CD for Linux Mint and I’m in the process of reinstalling it. I would prefure if I could just disable MOK but I at least know how to work around it.\n
\n
Update 2: I have fully reinstalled and updated Linux Mint but for some reason everything looks different despite the fact that I’m using the same settings and software I was before everything broke. But whatever, outside of the fact that I no longer have the dual boot menu and instead I get a string of text saying “booting in insecure mode” for some reason, it seems to be working fine.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 3
+favouriteCount: 21
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1719088547 {#2384
date: 2024-06-22 22:35:47.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2383 …}
+votes: Doctrine\ORM\PersistentCollection {#1906 …}
+reports: Doctrine\ORM\PersistentCollection {#1708 …}
+favourites: Doctrine\ORM\PersistentCollection {#1410 …}
+notifications: Doctrine\ORM\PersistentCollection {#1907 …}
+badges: Doctrine\ORM\PersistentCollection {#1407 …}
+children: []
-id: 27941
-titleTs: "'back':6 'boot':14 'disabl':22 'mokutil':3 'oss':17 'prevent':11 'proper':21 'use':2"
-bodyTs: "'2':137 'abl':78,89,98 'access':57 'actual':38 'also':48 'anyth':36 'around':134 'assum':27 'boot':14,73,100,183,194 'broke':169 'bypass':80 'cd':18,104 'correct':31 'could':122 'couldn':33 'despit':153 'differ':152 'disabl':46,91,124 'dual':182 'everyth':30,150,168 'fact':155,175 'find':35 'fine':206 'forgot':50 'fulli':140 'get':188 'insecur':196 'instead':186 'know':130 'least':97,129 'linux':5,59,106,144 'live':17,103 'longer':179 'look':21,151 'm':110,158 'manag':9 'mention':52 'menu':184 'mint':6,60,107,145 'mode':69,197 'mok':8,81,125 'need':2 'normal':74 'onlin':25 'outsid':172 'password':84 'prefur':119 'prevent':11 'process':113 'proper':45 'reason':149,200 'recoveri':68 'reinstal':4,115,141 'run':65 'say':193 'seem':202 'set':162 'softwar':164 'solut':24 'still':86 'string':190 'text':192 'tri':20 'updat':75,136,143 'use':82,159 'wasn':87 'whatev':171 'wont':72 'work':39,133,205 'would':118"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1704724204
+visibility: "visible "
+apId: "https://lemmy.ml/post/10247900"
+editedAt: DateTimeImmutable @1719190893 {#2378
date: 2024-06-24 03:01:33.0 +02:00
}
+createdAt: DateTimeImmutable @1704664704 {#2379
date: 2024-01-07 22:58:24.0 +01:00
}
} |
|
Show voter details
|
12 |
DENIED
|
moderate
|
App\Entity\Entry {#2381
+user: App\Entity\User {#265 …}
+magazine: Proxies\__CG__\App\Entity\Magazine {#1724 …}
+image: null
+domain: Proxies\__CG__\App\Entity\Domain {#1630 …}
+slug: "I-used-mokutil-a-while-back-but-now-it-s-preventing"
+title: "I used mokutil a while back but now it's preventing me from booting into other OSs. How do I properly disable it?"
+url: null
+body: """
I need to reinstall Linux Mint but MOK Management is preventing me from booting into the live CD. I tried looking for a solution online but (assuming I did everything correctly) I couldn’t find anything that actually worked for me. How do I properly disable it?\n
\n
Also, I forgot to mention that I do have access to Linux Mint, I just have to run it in recovery mode because it wont boot normally.\n
\n
Update: I was able to bypass MOK using my password, I still wasn’t able to disable it but I was at least able to boot into my Live CD for Linux Mint and I’m in the process of reinstalling it. I would prefure if I could just disable MOK but I at least know how to work around it.\n
\n
Update 2: I have fully reinstalled and updated Linux Mint but for some reason everything looks different despite the fact that I’m using the same settings and software I was before everything broke. But whatever, outside of the fact that I no longer have the dual boot menu and instead I get a string of text saying “booting in insecure mode” for some reason, it seems to be working fine.
"""
+type: "article"
+lang: "en"
+isOc: false
+hasEmbed: false
+commentCount: 3
+favouriteCount: 21
+score: 0
+isAdult: false
+sticky: false
+lastActive: DateTime @1719088547 {#2384
date: 2024-06-22 22:35:47.0 +02:00
}
+ip: null
+adaAmount: 0
+tags: null
+mentions: null
+comments: Doctrine\ORM\PersistentCollection {#2383 …}
+votes: Doctrine\ORM\PersistentCollection {#1906 …}
+reports: Doctrine\ORM\PersistentCollection {#1708 …}
+favourites: Doctrine\ORM\PersistentCollection {#1410 …}
+notifications: Doctrine\ORM\PersistentCollection {#1907 …}
+badges: Doctrine\ORM\PersistentCollection {#1407 …}
+children: []
-id: 27941
-titleTs: "'back':6 'boot':14 'disabl':22 'mokutil':3 'oss':17 'prevent':11 'proper':21 'use':2"
-bodyTs: "'2':137 'abl':78,89,98 'access':57 'actual':38 'also':48 'anyth':36 'around':134 'assum':27 'boot':14,73,100,183,194 'broke':169 'bypass':80 'cd':18,104 'correct':31 'could':122 'couldn':33 'despit':153 'differ':152 'disabl':46,91,124 'dual':182 'everyth':30,150,168 'fact':155,175 'find':35 'fine':206 'forgot':50 'fulli':140 'get':188 'insecur':196 'instead':186 'know':130 'least':97,129 'linux':5,59,106,144 'live':17,103 'longer':179 'look':21,151 'm':110,158 'manag':9 'mention':52 'menu':184 'mint':6,60,107,145 'mode':69,197 'mok':8,81,125 'need':2 'normal':74 'onlin':25 'outsid':172 'password':84 'prefur':119 'prevent':11 'process':113 'proper':45 'reason':149,200 'recoveri':68 'reinstal':4,115,141 'run':65 'say':193 'seem':202 'set':162 'softwar':164 'solut':24 'still':86 'string':190 'text':192 'tri':20 'updat':75,136,143 'use':82,159 'wasn':87 'whatev':171 'wont':72 'work':39,133,205 'would':118"
+cross: false
+upVotes: 0
+downVotes: 0
+ranking: 1704724204
+visibility: "visible "
+apId: "https://lemmy.ml/post/10247900"
+editedAt: DateTimeImmutable @1719190893 {#2378
date: 2024-06-24 03:01:33.0 +02:00
}
+createdAt: DateTimeImmutable @1704664704 {#2379
date: 2024-01-07 22:58:24.0 +01:00
}
} |
|
Show voter details
|