You are not logged in.
There are two testing stages for software releases:
1. Before it is released.
2. After it is released.
And now the big suprise: this is the case not just for software, but for everything humans create!
On Devuan 6 Excalibr I can not get the european keyboard to work on tty with that method.
Under X it works.
This How To is based on this tutorial:
https://web.archive.org/web/20230402114 … stall.html
But it is not the same, because the original does not work anymore.
Note:
This setup will give you a working xserver without the need for a displaymanager or a desktop enviroment.
1. List all available video drivers in the repos with a short description
apt-cache search xserver-xorg-video-.* | pager2. Install the one(s) you need
apt-get install xserver-xorg-video-Your_GPU_Vendor_Here3. Install the minimum packages to get a working and useable xserver
apt-get install x11-xserver-utils xfonts-100dpi xfonts-75dpi xfonts-base xfonts-scalable xinit xorg xserver-xorg-input-kbd xserver-xorg-input-libinput xserver-xorg-input-mouse4. Install a window manager (I use evilwm, but you can use what ever you want)
apt-get install evilwm5. Install a terminal emulator (I use rxvt-unicode, but you can use what ever you want)
apt-get install rxvt-unicode6. Install a hotkey utility to start programs with keybindings
I use keylaunch since ages.
Sadly the developer has dropped it, but the deb-files for it are still available here:
https://packages.debian.org/bullseye/keylaunch
It still works on Devuan 5 Daedalus and on Devuan 6 Excalibur.
It is very small, it only dependencies are libc6 and libx11-6 (so packages every system has normally) and has only one configuration file in text format, wich is pretty easy to understand and to edit.
Download the deb-file you need and install it with:
dpkg --install keylaunch_1.3.9+b2_amd64.deb7. Create the configuration file for keylaunch in the home directory of the user who will run the xsession
touch ~.keylaunchrc8. Edit the configuration file for keylaunch
Put this at the top of the file content, it explains the whole file:
# Format:
# key=...KeyName:Command
#
# ... No modifier
# *.. Shift
# .*. Ctrl
# ..* AltAnd then some actual binding, here for example to start the rxvt-unicode terminal emulator:
key=*.*t:rxvt-unicodeThis means, when you in a running xsession, you can press and hold down Shift and Alt and then press t and this will spawn a terminal.
Of course you can use the hotkey combination you like the most, this is just an example.
9. Create a xinit file in the home directory of the user who will run the xsession
touch ~/.xinitrc10. Put the starting command for the windowmanager in that file, so that the windowmanager will start right after the xsession has started
evilwmThis is an example, if you use a different windowmanager than evilwm, use the start command of that instead.
11. Reboot your computer
rebootYou need to do this for the drivers, so you could have done it before, but to do it after setting all things up is easier.
12. Start the xsession with the prefered user (so the user who has the .xinitrc and .keylaunchrc files in the home directory).
startx13. End the xsession by killing the windowmanager
pidof evilwm | xargs kill1. Install Chromium from the official Devuan Repository
apt-get install chromium2. Start chromium once to be sure it starts and all directories it creates will be created.
chromium3. Exit chromium
4. Download google Chrome (not chromium) from upstream
https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb5. Extract the files from the deb-file
dpkg --extract google-chrome-stable_current_amd64.deb .(this command will extract them into the actual directory, but you can choose any path you like instead).
6. Copy the Widevine directory from the extracted chrome deb-file into the chromium directory where chromium looks for it
cp -r /opt/google/chrome/WidevineCdm /usr/lib/chromium-browser/.7. Start chromium again and check if netflix will play.
= = =
Note:
I used this setup for years, till the last chromium update break something for me on Devuan 5 Daedalus.
I also started it with firejail, so it was sandboxed:
firejail chromiumOn Devuan 5 Daedalus Desktop Live I tested this setup and it was working too.
However, I couldn't fix it on my Daedalus installation, so I made a fresh new install of Devuan 6 Excalibur and it works there too, except with firejail.
I will try to get this to work with firejail too again and then extend this How To.
Just don't use flatpak:
https://flatkill.org/
https://flatkill.org/2020/
Well the infiltration and the hostile takeover just continuing.
I wonder why people do wondering about that...
Official End of life (EOL) for i386 will be 2026-06-11.
The LTS team (they are not debian officials, but volunteers) will probably give LTS till 2028-06-30.
https://wiki.debian.org/LTS/
But you could pay Freexian to get 10 years of LTS: https://wiki.debian.org/LTS/Extended
EOL for 32-bit kernel would the be 2033-06-30.
Maybe that's an option for Devuan, depending on their pricing, we could run a donation campaign.
That's the important part I guess:
pre-up [ $(cat /sys/class/net/eth0/carrier) -eq 1 ]But I don't understand it.
Where does the -eq option belongs to?
To the pre-up?
Nice work!
But I think it will be useless a year after the Debian 13 release, because there will be no security and compatibility updates anymore.
Sure there could be community updates, but that's not for sure and not a reliable source, because you don't know how long someone is willing to offer non-paid support.
Debians politics indicates only one thing imo: it's a sinking ship, supported only by yeasayers and (traumatized) people, who are not accepting the reality of all the bad things that happen to the whole project since many years.
A genuine Devuan kernel would be nice, I agree.
It would make Devuan more independent from Debian and their dumb decisions like the drop of 32-bit kernels.
For myself I use Linux-libre since years.
It's the upstream kernel but all unfree code and all BLOBs are removed.
Works perfectly fine ever since.
I use the LTS version, so you don't get tons of updates all the time.
There is an offical .deb-Repository, with support for a lot of CPU architectures, including 32-bit x86:
https://www.fsfla.org/ikiwiki/selibre/l … sh.en.html
I want to have dhcp to try to establish a network connection at boot time, but when there is no ethernet cable plugged in, or no wlan card, it takes up to 60 seconds before dhcp gives up.
So let's decrease the timeout.
Edit
/etc/dhcp/dhclient.confSearch for the line
#timeout 60;uncomment it and change it to the value (amount of amount of seconds) you like.
For example:
timeout 15;That's it.
Note 1: If the dhcp server did not offer an ip address before the time out runs down. you wont get an established network connection!
Note 2: udhcpc can be a replacement for isc-dhcp-client and isc-dhcp-common. I noticed, that it times out very quickly by default, when it can not find any of the interfaces defined in /etc/network/interfaces
Thanks to ralph.ronnquist (rrq) for helping with the timeout issue and mentioning udhcpc in IRC.
Ok done.
Happy flashing! ![]()
Why documentation section? It is not Devuan specific.
Method 2: Using an external CDROM drive connected via USB (my favorite)
Works with the following Eee PC models:
* 700 (2G surf)
* 900A
Works __not__ with the following Eee PC models:
* 1201N
- Download the BIOS ROM file, rename it to Modelname_here.ROM and burn it to a data CD (__not__ DVD!)
- I used for burning xfburn.
- Connect the external CDROM drive via USB and insert the disc.
- After Splashscreen appears press and hold Alt and then press and then hold F2.
- EZ Flash will do the flash automatically.
Method 3: Messing arround with partitioning an USB stick or an SD card with small partitions, like 32mb and such, using FAT16 for it and cylinders instead of sectors to allocate the partitioning size.
Read this to mess arround with it if you like to (it's where I started from weeks ago):
https://www.reddit.com/r/EeePC/comments … us_eee_pc/
I am pretty sure, that the HowTo I described in the first post is exactly this, only that dd write the FreeDOS image with all formating that is needed just in the correct way.
I tested the reddit suggesstions, with cfdisk, gnome-disks, gparted...
I really made several attempts with different combinations of the suggessted techniques using different USB flash drives and SD cards with different storage capacity.
I got some combinations to work on the 900A.
One example:
- 4 GB SD-Card with to partitions:
1. Partition: 32 MB FAT16.
2. Partition: remaining storage as Ext4 (I did that to have EZ Flash ignore it, because I thought it can not reconize it and would threat it as non-existent, what is probably the case. Leaving the reamining space unformatted did not work).
- Copy the Modelname_here.ROM to the 32 MB FAT16 partition and run EZ Flash.
But for me the easiest way was to burn the ROM to a data CD and run EZ Flash and if that not works copying it to a FreeDOSLite partition and run EZ Flash.
Method 4: Using AFUDOS (good for backup your BIOS!)
- Copy an AFUDOS.exe to a FreeDOSLite partition.
- Start FreeDOSLITE.
- Set language.
- Then break up the installation (it will ask you after choosing language, choose "No...foobar").
- You will get a FreeDOS shell
- Run AFUDOS by typing:
AFUDOS /Some_commandSome_fileIt knows two commands:
1. For backup up the actual BIOS (highly recommended!)
AFUDOS.EXE /oBACKUP-BIOS-Eee-PC-Modelname.ROM(You can choose whatever filename you want, but better be precise).
2. For flashing a new BIOS ROM:
AFUDOS.EXE /iModelname_here.ROMThat's it.
Method 5: Using Bupdater
!!! Use Bupdater at your own risk !!!!
Only tried it once and it failed for me.
On the 1201N I couldn't get any of the methods this HowTo listed to work (except the FreeDOS + EZ Flash method described in the first post of this thread, but I only found that out after I messed arround with all other methods, described in the second post here).
The Bupdater tool can be found here for example:
https://www.asus.com/supportonly/eee%20 … desk_bios/
under Tab: Driver & Tools -> Section: Driver & Tools -> Tab: Driver & Tools
(What idiot came up with that structure and more important: is someone paying that idiot for this?)
It is downloadable from the vendor page of a specific Eee PC model, in this case the Eee PC 1201N, but maybe it could work for other Eee PCs too (I saw some videos on youtube where people flashing different Eee PC models with that tool).
You also have to run it from FreeDOSLite and it has the same syntax as AFUDOS (its probably the successor of AFUDOS).
It gives you some curses interface and everything runs automatically, but for me it errors after the write started.
I waited for half an hour and after that I couldn't turn the Eee PC off.
So I pulled out the AC connector and the battery.
I was ready for a bricked device but it just started normal.
But it did not flash the new BIOS.
!!! Use Bupdater at your own risk !!!!
PLEASE report any issues you run into using this HowTo and also report if you know other methods, or how to improve this HowTo. Thank you very much! ![]()
The following is just a summary of the imo easiest way to flash the BIOS of an Eee PC.
I tested it on following Models for now:
* 700 (also known as 2G surf)
* 900A
* 1201N
What you need:
* An USB stick or a SD card.
* An image file of FreeDOS (.img not .iso !): https://freedos.org/download/ Use the LITE version, it does not take much space.
* A BIOS ROM file. Best to get from Asus: https://www.asus.com/
Note 1: The search function of asus.com is not good, I searched for 1201N and checked all of the results but it wasn't in there. But using a searchengine with a search term like "eee pc 1201n bios" gave me the link to the asus page.
So here's the summary for everyone who wants to flash the BIOS of an Eee PC:
Important Note: Use an AC adapter to be sure the Eee PC does not power off while the flashing process runs, cause this can causing your Eee PC to brick!
- Use an usb stick or a SD card.
- Write a FreeDOSLITE.img (__not__ ISO!) on it with dd.
- Mount that FreeDOS partition.
- Copy the BIOS ROM file on it.
- Rename the BIOS ROM file to Modelname_of_the_Eee_PC.ROM (so 900.ROM for example).
- Plug the usb stick in an usb port of the Eee PC, or the sdcard in the sdcard slot (do __not__ use a card reader! EZ flash wont be able to find the ROM file).
- Power on the Eee PC and as soon as the splash screen of the vendor appears press and hold Alt and then press and hold F2. The screen should go black and after some time EZ flash should get started and runs the whole flashing process automatically. You do not have do anything else.
Note 2: That button pressing to start EZ flash does sometimes not work. Just power off the Eee PC and try it again.
The whole process should look similiar to this:
Boot Block Compatible Version Ver.Some_foobar_versionumber_here
Please do NOT insert any disc into CD-ROM or Floppy drive
if you want to recovery with an USB device.
EZ-Flash starting BIOS update.....
DO KEEP the power supply on and NOT touch the system while performing BIOS
update.
Checking for USB Device...
USB Device found.
Reading file "Modelnumber_of_Eee_PC_here.ROM". Completed.
Start Erasing...\
Start Programming...\
Start Erasing Boot Block...\
Start Programming Boot Block...\
The BIOS update is finished.
Please press power button to shut down the system.Note 3: On the 1201N it does not show
Start Erasing...\ And after
Start Programming...\is done it shows:
BIOS update succesfully completed.
Flashed successfully. Rebooting...but only for a half second (catched that only because I made a video of the process).
In the second post here in this topic, you will find additional information about other methods that will work on some models while they do not work on others (trust me I tested them all, messed arround with that topic a lot).
PLEASE report any issues you run into using this HowTo and also report if you know other methods, or how to improve this HowTo. And also report if you got this to work on Eee PC models that are not listed here. Thank you very much! ![]()
Good reply einpoklum.
But an official reply would be nice, since the question from stopAI was posted two weeks ago.
Thank you very much for that! ![]()
What did you fear? Dataloss? If so do redundant backups! ![]()
Both are not in the main branch, only sntop is.
igozwx wrote:
NOTE: If you want to use Firefox for video conferences, you have to run it with apulse
So that is the problem!
wtf?!
firefox became poetterware 8 years ago as it seems:
https://www.mozilla.org/en-US/firefox/5 … easenotes/
rolfie wrote:
Devuan Daedalus is not compatible to Ventoy. Does not work.
I can confirm that.
Also keep in mind that other operating system ISOs are affected too (not all), I discovered that. No matter if they are installers or live-media.
Update:
Today I removed plymouth from the computer.
After that grub and intiramfs were updated.
I did a reboot.
Since then the layout is eu everywhere, also in the decryption screen.
So of course the issue I described has (probably) nothing to do with plymouth, but with the initramfs and grub.
So updating them after running the steps in the first post should keep those settings permanently.
Ehmm.. so you two tell me not to force my personal preference on guests, but your preference [is] force to guests...
Well... how about a button for easy switching?
@Dutch_Master don't force your preference to log in for read only to other users.
On my productive system I got the following messages after the reboot:
CHKBOOT ALERT!
Changes have been detected in your boot files!
The following list of files contained in have changed since the last time this script was run (filename sha512):
List of changed files on date_and_time_here:
338c338
< ./grub/grub.cfg foobar_with_a_lot_of_numbers
---
> ./grub/grub.cfg foobar_with_a_lot_of_numbers
This notification will continue to appear until you either run "chkboot" again as root or restart your computerI then log in as root and runned chkboot.
After that the message not pop up when i changed the tty.
The next day i rebooted the computer and the eu layout was gone on the tty.
I runned the process again and after a reboot I did not get that "CHKBOOT ALERT" and eu was working again.
Any clues?
Next problem: the eu layout is not active in the decryption screen before boot. Hot to fix that?
(This How To! changed to a How To? as it seems :/)
I like to read here without being logged in.
But that bright, white theme hurts my eyes.
Can we have the Mercury theme per default?
Cobalt, or Radium would also work, but Mercury has the best contrast, especially when using a blue-light filter on a dimmed display (sct 1200 0.6 for example).
@stopAI: I think it will be used to pay the devs. They deserve it.