You are not logged in.
As you I use external SSDs for different systems. When I upgraded my (external) Beowulf installations, I ended up in dual-boot grub entries.
But I must say that I did not care about that during the upgrade process.
Thanks @Head_on_a_Stick. The problem was that I could not find any error message. Wpa_supplicant was running, as well as dhclient, but they never were able to connect the machine.
I did what you said and disabled avahi, network-manager and modem-manager, step by step and one after the other. After that and without any further other changing the wpa_supplicant connects the machine as all the years before.
Did the upgrade process started all these daemons?
During the last days I upgraded 7 machines from beowulf or chimaera-testing to the stable chimaera version - without any problem - perfect.
And today I did the upgrade on the last machine - an old Asus eee701, running chimaere-beta-386.
Upgrade went fine, but after the following reboot I had no connection to the internet. Ifconfig showed why: No IP address for wlan0.
The network handling for wlan0 was made by the wpa_supplicant, also perfect and stable. Now I saw that the wpa_supplicant was running on wlan0, but the dhclient was unable to give an ip.
Then I saw that further daemons were :
- avahi-daemon, which created an own interface wlan0:avahi with a fall-back ip adress from a wrong range.
-network-manager
-modem-manager
I never ever had configured this daemons to run and to handle my wlan interface - but they did. However none of the programs were able to fire up wlan0 and connect to my dhcp server. OK, to many cooks probably.
All this only happened on the old eee701 Asus machine, other computer with wlan interface are still running fine with wpa_supplicant.
What is the best way to connect to the internet? Is it time to say good-bye to the wpa_supplicant? Or shall I deactivate network-manager and modem-manager and let still do wpa_supplicant the job?
Hints are highly appreciated.
Regards
Berni
I play AisleRiot too, beside gnome-mahjongg, Solitaire Klondike (xpat2) and cuyo. That's it.
Thanks @fsmithred, so I will do.
Yesterday I installed the latest minimal-live image onto an older Gigabyte Brix machine with 8GB of RAM and Celeron N2807. The Brix is from 2015 and is able to boot BIOS and UEFI. However the UEFI boot will not always work and therefore I made a BIOS installation.
This was not my first minimal-live installation and it is the best option for my personal Devuan.
OK, I started installation and everything seems to be fine - no errors, no problems.
But when I booted into the new system, grub starts, loads the kernel, and the the system hung! The last message was:
Kernel Panic: VFS: unable to mount root-fs on unknown block (0,0)
I tried multi- and single user mode, I repeated the grub-install, but nothing helped.
Later on, when I had no more ideas, I downloaded the refracta_11_nox image, which has the same kernel version. Installation was OK - and the system started perfectly. No kernel panic, nothing. Everything fine.
Any idea what went wrong with my minimal-live installation?
Regards
Berni
Ooops, sorry.
After several installations of Devuan in UEFI mode with the refractainstaller my experience is as follows:
- better make the disk partioning before running the installer
- never forget the EFI partition
- also never forget to write a fat filesystem onto the EFI partition
- run the installer
- repeat the install-grub procedure manually after installation
- boot the machine in EFI mode
Running only the installer I often had the situation, that the system did not boot: No boot device found, Grub Rescue or a fragmented Grub screen - all this has happened in the past.
Honestly the Grub installation of the refractainstaller seems to be not perfect.
Regards
Berni
PS: Using the lates minimal-live I ran into a problem when choosing GParted during installation. GParted was not part of minimal-live, and the refractainstaller ended in an endless loop between selecting the partition tool and going ahed without partitioning. Choosing another tool (gdisk, cfdisk) always brought the indication "GParted is not installed".
That happened yesterday when setting up a Daedalus system, based on minimal live.
Finally some manual work as described afore was successful.
Don't be suprised, @zapper.
Off course my Beowulf- and Chimaera machines will be untouched, but an Alpha-installation with Daedalus on an external SSD is quite nice. A good toy for gray and boring autumn evenings, which will come soon.
Regards
Berni (just preparing a SSD)
Thx, I'll try it now.
Please excuse my silly question: Did you simply upgrade to Daedalus by changing the repository?
Or is there a Daedalus boot image available to build the system from scratch?
Clueless, Berni
Both will run fine on your hardware. I can*t see any exotic components in your system, which may cause problems.
My personal hint: Try chimaera!
Why not simply use a mini script which only contains one line: cd / && su
Calling that script will bring you to / as root.
OK - I tried it on 2 Pi 4 (8GB), and it works fine. But you are right: It was much more fun than installing Chimaera onto an AMD64 machine.
Poor guy! I have the same problem on 6 machines, all running chimaera.
Hi,
when Im on the road with a motorcycle I always have my old Asus eee701 PC in the saddlebags: Its small, very small, has an old 868 processor and 2 GB of RAM. There is no internal HD and instead I use the build-in SSD (4GB) and a SD card of 128GB for OS, apps and swap.
The system runs beowulf without Xorg.
My applications are:
text processing: joe, nano, emacs
spread sheet: sc
browsing the net: lynx, links
mail & news: alpine
file manager: mc
music: mpg123
playing: bsdgames
programming: php, ruby26
off course various tools are installed as ncftp, neofetch, nmap, arp-scan, wpa_supplicant,wget, git and a lot more.
All that may sound very poor, but for me its perfect on travelling. And the eeePC offers enough entertainment for a long and rainy eveneing in a hotel.
And believe me: After a while you will love the pure shell (bash) with its various options.
Thats my solution.
Regards
Berni
Simply disable your Login-Manager (xdm, lightdm, gdm, slim - whatever you use). Now your booting ends up at a non-graphical login. Alt+ctrl+F1/2/3... gives virtual screens, again without GUI.
If you want to start Xorg via startx, you may need the .xinitrc file. Link your .xsession to .xinitrc or create a new file. In the simplest case your .xinitrc contains only the call of the window-manager of your choice, maybe "exec xfce4-session".
Yes, I did.
The tools was too fast - suspisious fast.
However your image works very good!
@cOrnelius: Thanks, that worked perfect and the image now runs fine at an USB-3 port. On another raspi 4 I use one of your images and there I must not fix the quirk issue. Is this depending from the SSD type and manufacturer?
@samhain: Using raspi-config did not work correctly. Some tool showed the new size of 470 G, other the old size of 8 G. Then I copied lots of file to / and at 8 G it stops and indicated that it is full.
I then did the expand manually via fdisk and now I have the full size off the SSD.
Thanks, will try to expand now. I did not test the image with SD card yet, but will do it tomorrow.
...........
Enjoy
I did so! Nice job, the image runs fine on my raspi 4 (8GB) - if I connect the ssd to an USB-2 port. Using USB-3 brings lots of errors and long delays. However on USB-2 it's OK.
This is my first Trinity system and its fast on the small machine - what I never have expected.
Is there an option to expand the images partition to the full ssd size?
Regards
Berni
Thanks HoaS, your hint was 100% correct and I was able to solve the problem! Reading the BoottimeEntropyStarvation opened my eyes and brought me to tpm. Indeed the T500 has a tpm chip and it requires randomizing. Disabling the tpm security chip was the solution and my old T500 now boots boot very fast. Thanks again for the help. ; )
Berni
Haveged is running, but how can it help?
Yepp, I know, but I have 150 sec.!! That's not slightly.