Activity for Alberto
-
Alberto posted a comment on discussion General Discussion
I've got an update for Mint today. Masking have survive to update, I think because name of masking names haven't change. So problem is 'masked' but not solved. And no response from my email to developer.
-
Thanks for all.
-
Ok thanks for RefindPlus link. And about my question to add the feature inside Refind, I Am on right place to ask or post actual bug ?
-
Yep this one is working perfectly , I have done it via : follow_symlinks ON "opensuse" and entry Debian has gone. But some works on this one to be done, icons for Linux are gone, and efi binary is not signed. Have we a chance to include this feature in next Refind release ?
-
@ roy rodgers : my problem is not detection problem, but false symlink. Please read from the beginning.
-
@ roy rodgers : my problem is not detection problem, but false duplicate. Please read from the begining.
-
No. image above was for Mint. If I disable follow-symlinks, I loose detection of Thumbleweed kernels links (the Icon after Windows), this distro have only links. Secondly the manual stanza above will only show 1 of both kernels. I will test next Mint kernel update and hiding. Attached thumbleweed boot folder
-
No. image above was for Mint. If I disable follow-symlinks, I loose detection of Thumbleweed kernels links (the Icon after Windows), this distro have only links. Secondly the manual stanza above will only show 1 of both kernels. I will test next Mint kernel update and hiding.
-
No. image above was for Mint. If I disable follow-symlinks, I loose detection of Thumbleweed kernels links (the first Icon), this distro have only links. Secondly the manual stanza above will only show 1 of both kernels. I will test next Mint kernel update and hiding.
-
With that option its going a little better , but is buggy too in that case. vmlinuz.old is going to Mint selector ok, but vmlinuz is still in faulty Debian selector. Attached boot folder from Mint, in blue color = links
-
With that option its going a little better , but is buggy too in that case. vmlinuz.old is going to Mint selector ok, but vmlinuz is still in faulty Debian selector.
-
Yep I've hide the unwanted instance, hope the hiding will survive to next Linux Mint update! (but the problem is still not solved but masked) Where to post the bug ? Thanks for your advice for RefindPlus !
-
I have added vmlinuz and vmlinuz.old (the links from Mint /boot folder) to dont_scan_files, but did not help. It still give an entry for Debian (the next volume parsed) as attached picture.
-
I have added vmlinuz vmlinuz.old (the links from Mint /boot folder) to dont_scan_files, but did not help. It still give an entry for Debian (the next volume parsed) as attached picture.
-
Yes, perhaps dont_scan_files , I use it for EFI files, does it work also for links ?
-
It's complicated to me to modify things for Thumbleweed, kernel links are detected correctly and automaticly with follow_symlink option. The problem with this option is /boot parsing from Mint volume. Initramfs generates kernels (no symlinks) +2 links pointed to theses kernels. I will look more at next update, but I think the 2 links are constant names. How to backlist theses symlink names from autodetect ?
-
For thumbleweed, all kernels have a link in /boot and they changed name on update. For Mint / Ubuntu, the 2 links points to previous and last kernel in same /boot folder. The problem is here. I will look on kernel update if name of link change, if not perhaps I can blacklist the boths links scanned ?
-
The entry for Thumbleweed is fixed with follow_symlinks, read my first message. But with follow_symlink It is not fixed for mixed linked / fixed kernels like Mint (I use) or Ubuntu because Mint is base on Ubuntu, it creates an additional (not working) input with symlinks found instead grouping it in Mint input.
-
The entry for Thumbleweed is fixed with follow_symlinks, read my first message. But with follow_symlink It is not fixed for mixed linked / fixed kernels like Mint (I use) or Ubuntu because Mint is base on Ubuntu, it creates an additional (not working) input with symlink found instead grouping it in Mint input.
-
The entry for Thumbleweed is fixed, read my first message. It is not fixed for mixed linked / fixed kernels like Mint (I use) or Ubuntu because Mint is base on Ubuntu.
-
The manual entry works, but this is not the purpose of Refind (have a automated detecting kernels bootmanager). follow_symlink is need to detect Tumbleweed kernels automaticly (or I have missed something?)
-
HI, I've installed since years Refind , works fine and recently I have adde Thumbleweed in addition to Windows, Linux Mint, Debian and Redhat. To detect Thumbleweed kernels, I have added in conf file follow_symlinks for this purpose. It works for Tubleweed. But I have next distro distro boot folder parsed with mixed simlink / non simlink kernels: It's Linux Mint 22 (based on Ubuntu 24). When parsing the /boot folder, it detect vmlinuz and vmlinuz.old simlinks. Well but it creates a new entry and...
1
