The officially official Devuan Forum!

You are not logged in.

#51 Re: Installation » SOLVED: Issues using "live" install on Thinkpad T410 » 2021-01-31 15:27:38

fsmithred wrote:
Lomax wrote:

with some nearly unusable GUI widgets, like a drop-down containing every European TZ location (this should be a scroll-window), and the keyboard layout selection sends you on a circuitous journey just so you can tell it that yeah, the keyboard layout is the same as the (already chosen) locale.

This is the standard graphical debconf interface as the graphical install and the exact same language, time zone and keyboard settings in the debian/devuan installer or with dpkg-reconfigure. And yes, it is correct to set the keyboard separate from the language.

Umm... That's not quite true; the text based set-up does default to a UK keyboard layout after you've chosen UK as your locale. And It doesn't put 100s of items in a drop-down list. And it doesn't force you to choose "Other" if you happen to be a non-US user.

fsmithred wrote:
Lomax wrote:

Many of the checkbox options are contradictory; for example I chose on one screen to disable the root account (btw - why does it say this is a bad idea!? It's a really good idea, and ought to be the default!) only to have the next ask me for a root password.

It only asks for a root password if you chose one of the options that preserves the root account. And making sudo the default is a really bad idea. Sudo is not meant to be a replacement for a root account, it's meant for fine-grained privilege escalation.

I respectfully beg to differ. Sudo is easier to audit, easier to administrate (by adding removing users from /etc/sudoers), and it will time out the escalated privileges after a certain interval, reducing the risk of leaving a machine unlocked with a root shell by accident. And if you really do need a root shell, sudo -i is your friend. I didn't come here to argue about that though - to each their own - but I wanted to mention that even when I chose the middle option on the first screen that said "use sudo / disable root account" I was still asked for a root password on the next screen, with another two checkboxes relating to root locking. The wording and function of these (five) checkboxes was pretty confusing.

Also, the installer died whenever I did something it didn't expect, like close a window or Ctrl+C a long running write of /dev/random to disk. The text based installer does not behave like this;  at any point you can go back and redo earlier steps, and cancelling the current step simply takes you back to the menu. Furthermore, as each step is completed it helpfully moves to the next item in the menu, skipping those steps which your choices have made redundant. It's always clear where you are, and what is left to do, and a lot of the time all you need to do is confirm the sensible defaults by pressing return. You also get a lot of options that were missing from the GUI installer, such as configuring the network, setting up NTP, fetching latest packages, choosing what to install...

fsmithred wrote:
Lomax wrote:

the hardware volume up/down/mute buttons don't work. TBH I don't think I tested them before removing pulseaudio, so I can't say if they were working or not, but they're defintely not working now. I can see that they generate the correct events with `acpi_listen`, but it seems nothing is listening to them? `lsmod` shows `thinkpad_acpi` is loaded, so that's not it.

In the Settings menu, go to Keyboard and Application Shortcuts and you can set up the volume keys to activate amixer. There are a few websites that explain how to get Thinkpad keys working in linux.

Oh thousands I'm sure. But they all talk about how to make them work with Pulseaudio. I'll have another look though, now that I have some idea where this is configured - thanks for that! It is odd that I haven't needed to do this on the Thinkpad X220 and X230 laptops I've previously installed Devuan on - maybe because I've built them from netinstall and up, maybe because there's some difference in how the hardware hotkeys work on the T410. 

fsmithred wrote:
Lomax wrote:

2) I was also surprised to see it ask me for an encryption password at boot; I'm used to the encrypted /home being automagically decrypted and mounted at log-on using ecryptfs (including encrypted swap). This should offer enough security for most users I would say, to hinder identity theft in case the laptop is lost or stolen. In any case I can't give the machine to my friend like this; he'd hate having to remember and type two different passwords to turn on his computer - or even the same one twice. I also didn't like how the installer (seemingly) forced me to use a separate partition for /home if I wanted it encrypted.

You have a few choices with this installer. You can install everything in one partition and have it encrypted. Your /boot directory will be part of the encypted partition. You will have to tell grub the passphrase to open it and start the boot. You will then have to repeat it for the kernel. This is referred to as full disk encryption, and it's a new feature in grub to be able ot deal with encrypted /boot.

You can encrypt the root filesystem and have /boot in a separate partition, unencrytped. You then have to give the passphrase during boot. Once.

You can optionally have a separate partition for /home. It's not mandatory, and I usually skip it on a laptop. If you choose to encrypt the separate /home, you will need to enter a passphrase for it, whether or not the root filesystem is encrypted. If you want to eliminate adding the second passphrase, you can create a key and have /home open automatically. This is only secure if the key is kept in an encrypted root filesystem (or a removable device).

You forgot the option I like to go with; use the user's login to decrypt /home. I'm not 100% sure how this bolts together (pam + ecryptfs?), but it certainly doesn't involve storing the decryption key in plain text on the machine, nor does /home need to be on a separate partition - I have to enter my (strong) password to decrypt and mount the directory as /home, but this is done seamlessly from the Slim login window. One login, two actions. And yes, I do think that's secure enough; it would take a pretty determined hacker to brute force my password, or to hijack my locked session if I left my laptop unattended in suspend somewhere - and if they can do that then it doesn't really matter how my data has been encrypted; if you're in you're in. It's not as if I'm storing the next Panama Papers or anything.

fsmithred wrote:
Lomax wrote:

I cannot get the laptop to sleep when I close the lid.

I found that it works just fine when you upgrade to chimaera, which is still in testing. Search the forum. There are a couple of discussions on how to get it working in earlier releases.

Ok, thanks, I'll take a look!

#52 Installation » SOLVED: Issues using "live" install on Thinkpad T410 » 2021-01-31 02:36:36

Lomax
Replies: 41

Hi all,

A friend gave me an old Thinkpad T410, which was timely, because I had just promised another friend that I would help set him up with a laptop that had a CD-ROM drive - which this machine happens to have. I thought it would be the perfect opportunity to introduce him to Linux, and of course went to download and install Devuan, which is what I use myself (thank you very much!). But I balked at the full install ISO at over four gigs - which would eat up a substantial chunk of my monthly bandwidth allowance - so thought I'd give the "live" ISO a shot, which is only just over one gig.

<rant>
Ok, first of all, I have to get this off my chest: I was not impressed by the GUI installer the live ISO comes with. It was throwing up terminal windows and other GUI apps (gparted) left right & centre - some of them partly off screen, and fell over if anything happened to get out of sync. It presented me with some nearly unusable GUI widgets, like a drop-down containing every European TZ location (this should be a scroll-window), and the keyboard layout selection sends you on a circuitous journey just so you can tell it that yeah, the keyboard layout is the same as the (already chosen) locale. Many of the checkbox options are contradictory; for example I chose on one screen to disable the root account (btw - why does it say this is a bad idea!? It's a really good idea, and ought to be the default!) only to have the next ask me for a root password. There are two options for /home encryption & partitioning, and many other things which confused me. I had to go through the process a few times before I got it right, and there was a fair amount of swearing. And when I finally thought I'd done everything properly I rebooted to find /home still under rootfs and not encrypted on a separate partition as I had expected it to be. So I had to start over again. The text based installer is a breeze to use by comparison and far more elegant and user friendly. A simple "Install Devuan on this computer" option in the GRUB menu, which launches the text-mode setup, is all that's needed, no?
</rant>

So anyway, I persevered, and got the system partitioned and installed the way I thought I wanted, but then I ran into some issues, which is really why I came here:

1) I was surprised to see Pulseaudio installed, and then I remembered that's why I always go with the netinstall ISO. Though I have never quite managed to get all the right packages installed from there to get a 100% fully functioning and smooth desktop experience - there's always something not quite right, like "reboot" and "shut down" from the menu taking me to the Slim login screen rather than rebooting (some dbus issue, perhaps?), and missing some control panel functionality, like the menu editor. But that's ok, I'm fine with that, and happy to use the console for a lot of stuff. But I want my friend to have a positive first experience of Linux, with a complete desktop environment and simple controls, so I went for the pre-packaged environment this time. Hey ho, it's easy enough to `apt-get autoremove pulseaudio` and `apt-get install apulse volumeicon-alsa`, which works perfectly - except the hardware volume up/down/mute buttons don't work. TBH I don't think I tested them before removing pulseaudio, so I can't say if they were working or not, but they're defintely not working now. I can see that they generate the correct events with `acpi_listen`, but it seems nothing is listening to them? `lsmod` shows `thinkpad_acpi` is loaded, so that's not it.

2) I was also surprised to see it ask me for an encryption password at boot; I'm used to the encrypted /home being automagically decrypted and mounted at log-on using ecryptfs (including encrypted swap). This should offer enough security for most users I would say, to hinder identity theft in case the laptop is lost or stolen. In any case I can't give the machine to my friend like this; he'd hate having to remember and type two different passwords to turn on his computer - or even the same one twice. I also didn't like how the installer (seemingly) forced me to use a separate partition for /home if I wanted it encrypted. In my experience slicing up a small SSDs into partitions inevitably leads to one or the other outgrowing its space, while there may be plenty of free space left on another one. I would make an exception for swap, since it doesn't need to grow, and /boot because it doesn't need much space, but /root and /home need to be able to grow unrestricted in a shared volume imo. So I went back and reinstalled again, now without /home encryption. I would still like to set it up though, for the /home directory, but when I checked my notes I found that unfortunately I haven't written down how I achieved this on my own laptop. Perhaps someone here knows the steps?

3) Possibly related to issue #1, I cannot get the laptop to sleep when I close the lid. The "Fn+F4" key combination works, as does choosing "Suspend" from the shutdown menu, but the lid refuses to trigger it. Again, `acpi_listen` shows the proper events (e.g. button/lid LID close), but nothing is listening. Similar thing with the power button; I have set it to "Ask" when the power button is pressed, but nothing happens - and here `acpi_listen` shows no events. Any ideas? Perhaps relevant is that the screen brightness controls do work, and even trigger a nice notification popup.

Phew. Well done if you made it through all that - and apologies for the rant; sometimes you just have to let it out. I love devuan and want to show others what a great alternative it is, not only to Windows but to other Linux flavours, so I'm prepared to invest some time in getting it just right. But unfortunately I have run into these problems which I cannot figure out on my own, so I'm hoping someone here may have some advice!

#53 Re: Hardware & System Configuration » Curious MicroSD storage issues after Beowulf upgrade » 2020-08-07 15:51:51

HevyDevy wrote:

what about what Hoas mentioned using sudo dmesg -w ? run that command and then insert some micro sd cards and see if there is any output to terminal?

Yeah, that was one of the first things I tried - I inserted a card and waited a good while (in case of logging being delayed by caching) but absolutely nothing happens.

#54 Re: Hardware & System Configuration » Curious MicroSD storage issues after Beowulf upgrade » 2020-08-07 11:47:30

With card inserted in SD Card slot:

$ lsblk --all
NAME           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda              8:0    0 465.8G  0 disk  
├─sda1           8:1    0 457.9G  0 part  /
├─sda2           8:2    0     1K  0 part  
└─sda5           8:5    0   7.9G  0 part  
  └─cryptswap1 254:0    0   7.9G  0 crypt [SWAP]

and

# dmesg | grep mmc
[    2.443500] mmc0 bounce up to 128 segments into one, max segment size 65536 bytes
[    2.444147] mmc0: SDHCI controller on PCI [0000:02:00.0] using DMA

#55 Hardware & System Configuration » Curious MicroSD storage issues after Beowulf upgrade » 2020-08-04 20:14:48

Lomax
Replies: 5

I've got a Thinkpad X230 and MicroSD cards are not being detected in the SD Card slot or any of the USB ports. I have tested a handful of different MicroSD cards using different adapters, one MicroSD -> USB and three MicroSD -> SD Card, all with the same result: nothing. I've checked dmesg output as the card is inserted and nothing happens. lsblk shows nothing new when a card is inserted. lsusb (with card inserted via a USB adapter) also draws a blank: 

Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 04f2:b2ea Chicony Electronics Co., Ltd Integrated Camera [ThinkPad]
Bus 003 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bdb:1926 Ericsson Business Mobile Networks BV H5321 gw Mobile Broadband Driver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspcpi shows:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
02:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

Note that the SD Host controller (by Ricoh) is shown. I have read through the dmesg output from boot to inserting a card and found

[    2.394226] sdhci: Secure Digital Host Controller Interface driver
[    2.394227] sdhci: Copyright(c) Pierre Ossman
[    2.443096] sdhci-pci 0000:02:00.0: SDHCI controller found [1180:e822] (rev 7)

But no errors or warnings relating to the PCI bus, the USB ports or the SD Card controller. And no other errors for that matter. MicroSD cards inserted via a USB adapter get warm, as if they were being accessed. Curious and frustrating - I work a lot with Raspberry Pis and often want to image MicroSD cards for back-up purposes, which I am now unable to do. I have tested a couple of "regular" USB sticks and they work fine. I have apt-get dist-upgraded and rebooted. I have apt-get install --reinstall udisks2 based on a tip I found on the web. I have modprobed sdhci with debug_quirks2="0x2" based on another tip. Few hours spent digging and I've hit bedrock - any ideas?

Edit: I should perhaps clarify that this used to work under ASCII - on the same machine with the same MicroSD cards and the same adapters. I did have an issue where I sometimes had to reboot after a suspend to get the Ricoh SD Card port to function, but it always came back.

#56 Re: News & Announcements » Beowulf Beta is here! » 2020-05-24 13:37:43

Thanks guys, I've learned a lot here - and yes, reboot went without issue, though I jumped as I saw the red boot screen big_smile Only niggle is slightly odd mouse pointer acceleration compared to what I'm used to (I'm a TrackPoint user), and that's really quite minor. I'll get used to it. Beowulf is noticeably faster than ASCII on my machine, which is great! Big thanks once again to the Devuan team for all the hard work you're putting into this project - it's clearly paying off!

#57 Re: News & Announcements » Beowulf Beta is here! » 2020-05-24 02:03:48

dev-1-dash-1 wrote:
Lomax wrote:

The upgrade seems to have gone well, but at the end of it I got a curious warning from update-initramfs:

If you have encrypted root try adding it to crypttab.

That warning means cryptsetup probably won't get included in initramfs unless you manually added it. So do fix it before going on.

If your root is unencypted you may boot but will have to unlock crypt partitions manually.

Thanks! I thought adding CRYPTSETUP=y to /usr/share/initramfs-tools/conf-hooks.d/cryptsetup was how to "manually add it" to initramfs, but since the warning persisted that's probably not correct. How should I do it? I don't have encrypted root, only swap partition and home directory. Home directory isn't decrypted at boot of course, and a missing swap partition should be easy to get around - but I'd still need to fix it...

Edit: Just saw your edited post.

dev-1-dash-1 wrote:

If you've only encrypted home and swap then you don't need cryptsetup in the initramfs and can ignore the warning. The root will be mounted and after that the cryptsetup binaries are accessible to the system in order to unlock the rest of partitions.

Excellent, then it is as I thought, and the warning is misleading. Thank you!

#58 Re: News & Announcements » Beowulf Beta is here! » 2020-05-24 01:28:49

The upgrade seems to have gone well, but at the end of it I got a curious warning from update-initramfs:

cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.

I have spent a good two hours trying to determine if this will mean my system won't boot (I have encrypted swap & home dir), but I'm still not quite sure. I understand that the wording of the warning is a little misleading; it's not saying you cannot include cryptsetup binaries in initramfs but that none are present although the systems may need one in order to boot. My crypptab: 

# <target name> <source device>         <key file>      <options>
cryptswap1 UUID=a01249eb-d97d-47d1-975e-3d34d2dfe94a /dev/urandom swap,offset=1024,cipher=aes-xts-plain64

Without really knowing what I'm doing I tried adding CRYPTSETUP=y to /usr/share/initramfs-tools/conf-hooks.d/cryptsetup and re-running update-initramfs -u but still got the same warning. I suspect the warning is spurious, and that my system will boot just fine, but I am loath to try without being sure. Can anyone confirm?

#59 Re: News & Announcements » Beowulf Beta is here! » 2020-05-23 22:41:49

That was easily fixed by simply doing

apt-get install libelogind0

I now get a clean upgrade plan in aptitude.

12:50 Press return.

#60 Re: News & Announcements » Beowulf Beta is here! » 2020-05-23 22:10:22

rolfie wrote:

Look at the Release Notes. You got the following issue:

libpolkit-backend-consolekit-1-0 <> elogind re. libpolkit-backend-elogind-1-0

Let your old VBox go, and re-install the latest version from Oracle directly.

rolfie

Great, thanks! I read up a bit on consolekit vs. elogind and decided to remove consolekit. I also removed Virtualbox, and all i386 packages, as well as the i386 architecture. Looking better now, but aptitude full-upgrade still chokes on

libelogind0 : Conflicts: libsystemd0 but 241-7~deb10u4 is to be installed

#61 Re: News & Announcements » Beowulf Beta is here! » 2020-05-23 20:51:25

Using aptitude full-upgrade instead gives me the following:

The following packages have unmet dependencies:
 libpolkit-backend-consolekit-1-0 : Conflicts: elogind but 241.4-2 is to be installed
                                    Conflicts: libpam-elogind but 241.4-2 is to be installed
                                    Conflicts: elogind:i386 but it is not going to be installed
 virtualbox : Depends: python3 (< 3.6) but 3.7.3-1 is to be installed
 libelogind0 : Conflicts: libsystemd0 but 241-7~deb10u4 is to be installed
               Conflicts: libsystemd0:i386 but 241-7~deb10u4 is to be installed
The following actions will resolve these dependencies:

     Remove the following packages:                                    
1)     virtualbox [5.2.24-dfsg-4~bpo9+1 (now)]                         
2)     virtualbox-ext-pack [5.2.24-2~bpo9+1 (now)]                     
3)     virtualbox-qt [5.2.24-dfsg-4~bpo9+1 (now)]                      

     Keep the following packages at their current version:             
4)     elogind [234.4-2 (now)]                                         
5)     libelogind0 [234.4-2 (now)]                                     
6)     libpam-elogind [234.4-2 (now)]                                  
7)     libpolkit-backend-consolekit-1-0 [0.105-25+devuan0~bpo2+1 (now)]
8)     libpolkit-gobject-consolekit-1-0 [0.105-25+devuan0~bpo2+1 (now)]

     Leave the following dependencies unresolved:                      
9)     virtualbox-dkms recommends virtualbox (>= 5.2.24-dfsg-4~bpo9+1) 

Maybe some clues in there?

#62 Re: News & Announcements » Beowulf Beta is here! » 2020-05-22 14:06:52

Lomax wrote:

I could understand if things like Virtualbox might disappear, but cmake!? Something's clearly not right here, what could that be?

I managed to fix most of these by removing some application specific repos, and uninstalling a few things I wasn't really using. dist-upgrade no longer wants to remove cmake for example. But it still wants to drop network-manager, and elogind:

The following packages will be REMOVED:
  elogind gnome-themes-standard-data libboost-python1.62-dev libboost-python1.62.0 libboost1.62-dev libclang1-3.9 libcupscgi1 libcupsmime1 libcupsppdc1 libcurl3
  libgsl2 libllvm3.8 libllvm3.9 libllvm3.9:i386 libmariadbclient18 libnomacscore3 libnomacsgui3 libnomacsloader3 libpam-elogind libqalculate5-data libqalculate5v5
  libreoffice-style-galaxy libsensors4 libsensors4:i386 libthunarx-2-0 network-manager network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome
  nodejs-dev virtualbox virtualbox-ext-pack virtualbox-qt

Isn't elogind required for Gnome to work without systemd-logind? And how can I retain network-manager?

#63 Re: News & Announcements » Beowulf Beta is here! » 2020-05-22 02:52:17

Tremendously excited about this new release - a big thanks to everyone who's been involved in making it happen, you guys rock! Keen to upgrade from ASCII and try out the new shiny things, but dist-upgrade wants to remove a bunch of critical packages:

The following packages will be REMOVED:
  clamav clamav-daemon clamav-freshclam cmake elogind gnome-themes-standard-data kicad libboost-python1.62-dev libboost-python1.62.0 libboost1.62-dev libclamav9
  libclang1-3.9 libcupscgi1 libcupsmime1 libcupsppdc1 libgsl2 libllvm3.8 libllvm3.9 libllvm3.9:i386 libmariadbclient18 libnomacscore3 libnomacsgui3 libnomacsloader3
  libpam-elogind libqalculate5-data libqalculate5v5 libreoffice-style-galaxy libsensors4 libsensors4:i386 libthunarx-2-0 network-manager network-manager-gnome
  network-manager-openvpn network-manager-openvpn-gnome nodejs-dev virtualbox virtualbox-ext-pack virtualbox-qt

This is on an up-to-date ASCII installation and the following atp/sources.list:

deb http://deb.devuan.org/merged beowulf main non-free contrib
deb http://deb.devuan.org/merged beowulf-updates main non-free contrib
deb http://deb.devuan.org/merged beowulf-security main non-free contrib
deb http://deb.devuan.org/merged beowulf-backports main non-free contrib

I could understand if things like Virtualbox might disappear, but cmake!? Something's clearly not right here, what could that be?

#64 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-20 10:41:00

ralph.ronnquist wrote:

I think update-grub uses blkid information about partitions, not fstab.

Ah, many thanks, that clears things up!

ralph.ronnquist wrote:

everything works like magic cool

Well... Considering I can't even get this thing to boot...

How is it that I can boot in rescue mode and chroot to /dev/sda1 but grub can't boot at all? The disk is clearly there, and it clearly has all the right bits on it. This should be a doddle, surely?

#65 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 21:59:30

fsmithred wrote:

Gave up waiting for suspend/resume device

This one can often be fixed by adding RESUME=none to /etc/initramfs-tools/initramfs.conf and then running update-initramfs -u or my manually unpacking the initrd and removing the resume file before repacking it. I suppose it would also be valid to put the correct swap uuid in the resume file if you're planning to hibernate.

Good tips, thanks! I did notice it crashing on resume from suspend when I booted with nomodeset. At this stage though, just getting it to boot with GPU acceleration is my #1 concern. For which this might be the answer: https://www.rodsbooks.com/refind/features.html

Provide the gptsync utility for creating hybrid MBRs. Note that rEFInd's version of gptsync is significantly updated compared to rEFIt's. Also, this tool should be used only on Macs that dual-boot with a BIOS-based OS, such as Windows; or very rarely on other computers.

Edit: I'm still curious though; where does it get the idea to try booting from a UUID when no such reference should be present any more? Doesn't fstab inform update-grub which partitions are available? Not that I think this would fix the problem (the UUIDs did match) but it's just not what I expected to see.

#67 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 17:00:50

ralph.ronnquist wrote:

replace that to say /dev/sda1 instead.

I had the same thought, but first forgot to run update-grub after making the change, and was surprised to still see the same error. So I went back to the rescue shell, verified that fstab was still the same (with /dev/sda1 and /dev/sda2 instead of UUIDs), then I ran update-initramfs -u and update-grub. Guess what; I STILL GET THE SAME BLOODY MESSAGE! How can it complain about a missing UUID when none are present?

ralph.ronnquist wrote:

And you would "activate" the swap space by replacing #UUID=b10e083f-db41-40e4-ac56-13e66da6ee32 (including the #) with /dev/sda2.

Ah yes, that was just a typo (in my post); the swap partition was always active - I had only commented it out prior to copying in order to change to /dev/sda2.

fsmithred wrote:

Does your laptop normally boot in uefi mode, like the one in the article you posted? Have you tried installing with gpt and uefi? Do you know if it needs a 32-bit bootloader to do that? If so, there's a way to use the amd64 desktop-live iso to install on such a system.*

It's not a laptop, it's a white Core 2 Duo iMac. It normally boots in EFI mode (this machine is pre-UEFI), but the GPU stops working at modeset with EFI boot. As the thread on Reddit I linked to makes clear, those iMacs included a "BIOS emulation mode" for compatibility with BootCamp - and this is automatically activated when booting from a disk with a MBR/msdos partition table (there is no GUI for activating this). The GPU (Radeon) works under Linux in BIOS compatibility mode - and that's precisely why I'm battling with all this. As for AMD64 vs i386, from everymac.com:

"Although it has a 64-bit processor, it has a 32-bit EFI and is not capable of booting into 64-bit mode."

It also cannot accept more than 4Gb of RAM, so no need for 64-bit addressing - or indeed even PAE.

fsmithred wrote:

It sounds like Ralph identified the problem. Get rid of that erroneous uuid, and it should work. (Run blkid to prove that the uuid doesn't exist, if you haven't already done that.)

Already done that; the UUIDs both match exatly what is was in fstab.

Edit: Better photos below.

#68 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 14:08:44

HevyDevy wrote:

try wiping out the grub config file.

Isn't that what I've already done? Like three times by now? The result is exactly the same anyway.

#69 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 13:25:43

If I was paid the minimum wage for doing this I'd soon be able to buy a brand new iMac (or whatever they're called these days). Not that I ever would, of course. Get paid I mean. Or buy a Mac.

Edit: What's all this talk about a "hybrid" partition table anyway? Apparently the Macs use some kind of MBR within GPT PT, to allow dual booting with Windows or something like that - but I'll be damned if I had a clue how to create one! This guy didn't seem to need one:

I fired up GParted and created an MBR table and a FAT32 partition and ran the installer. It installed, rebooted, and now she has a fast, perfectly usable machine with full acceleration and everything works, even standby/sleep and WiFi.

#70 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 12:40:55

I launched a shell on /dev/sda1 from rescue mode, and it looks like it's all there. So why won't it boot!?

# fdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 byte, 976773168 sectors
Units: sectors of 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbbbc4bda

Device         Boot     Start       End   Sectors Size Id Type
/dev/sda1      *         2048 966797311 966795264 461G 83 Linux
/dev/sda2           966797312 976771071   9973760 4.8G 82 Linux swap / Solaris
# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.9.0-6-686
Found initrd image: /boot/initrd.img-4.9.0-6-686
done
# grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.

This looked promising, so I rebooted. Alas, the error remains:

ALERT! UUID=9cb7fe29-135e-4471-8b2c-d3e08d6ad44f does not exist.

After another reboot to a rescue shell:

# less /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=9cb7fe29-135e-4471-8b2c-d3e08d6ad44f /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
#UUID=b10e083f-db41-40e4-ac56-13e66da6ee32 none            swap    sw              0       0
/dev/sr0       /media/cdrom    udf,iso9660 user,noauto       0       0

Yep, that's the right UUID. Let's go one level deeper.

# mount /dev/sda1 /mnt
# mount --bind /dev /mnt/dev
# mount --bind /proc /mnt/proc
# mount --bind /sys /mnt/sys
# chroot /mnt
# update-initramfs -u
# update-grub
# reboot

Boo!

ALERT! UUID=9cb7fe29-135e-4471-8b2c-d3e08d6ad44f does not exist.

#71 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 12:24:41

ralph.ronnquist wrote:

No, If you reboot the installer, but choose the "go back" option as soon as there is one, you'll drop down to the installer steps menu, where you can cherry pick the steps. In this case, it'd be the grub installation step (I've forgotten its exact name).

This didn't work; the installer errored out saying I had to install the base system first. But I tried the "rescue mode" and that had the option to re-install grub. I did so, choosing /dev/sda this time, but no dice; the system still fails to boot with ALERT! UUID=9cb7fe29-135e-4471-8b2c-d3e08d6ad44f does not exist. I don't understand why this is so complicated sad

#72 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 10:26:14

Thanks. So I have to re-run the install from scratch then? Only asking because it takes quite a while to install the whole desktop environment...

#73 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 08:21:48

I'm not keen to go through the whole installation process again (what is it, the fift time?), so if there's a way to reconfigure grub so that the system will boot I'd be happy to hear about it!

#74 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 08:17:30

No worries - it was worth a try smile How do I recover from this though? It should be possible to get this to boot, no?

#75 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 08:10:56

I didn't delete anything, but manually configured Grub to install on /dev/sda1, just to try something different. Grub installed without error, but the result is the same; after boot the system cannot find the boot disk and (eventually) errors out to an initramfs prompt with Gave up waiting for root file system device and ALERT! UUID=9cb7fe29-135e-4471-8b2c-d3e08d6ad44f does not exist. This does not happen when I install to a GPT/EFI disk.

Board footer

Forum Software