It is supposed to work with Linux (says so on the Amazon page and on the printer list in openprinting.org), but when I downloaded the driver from Brother (CUPS didn't find one), aptitude required more packages to go with it, including something that seemed related to running 32-bit architecture. (I have 64-bit.) I'm running Debian 9, Stretch. Apr 22, 2009 It could not tell you if you had a 64-bit kernel, because it only tells you whether your CPU is able to run a 64-bit kernel, which could be true even when running 32-bit. But your flags line says your CPU is not able to run a 64-bit kernel, so that indicates the running kernel must be 32-bit.
I need to update to Debian Press and there are quite a few guides out now there, but I desire to be safe and make certain I don't crack my system. Will be there a method to check if my present install deals are going to function on Press? If so, how? How can I backup my system to make sure it'h okay to improve?
Gilles560k134134 silver badges11541154 silver badges16601660 bronze badges
DougDoug
migratedfrom serverfault.comFeb 26 '12 at 16:12
This issue arrived from our web site for program and network managers.
2 Solutions
The discharge notes for squeeze go into detail about the correct proceedures and issues to check before the update. You can find the area right here:http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html
jordanmjordanm31.9k33 money badges8989 silver precious metal badges9898 bronze badges
I have upgraded a great deal of servers from sarge to etch, etch to lenny and lenny to press.
Upgrading to press can be a bit of an odd golf ball in that certain essential things have changed, the method devices are called (making use of UUIDs instead of gadget names) and udev mainly because nicely as an upgrade to grub2.
The procedure always arrived down to (I choose to use appropriate in a covering):
I select to NOT chainload grub2 making use of grub but use grub2 right aside. This can become a complicated component but simply be careful. Ideally grub2 should have been configured and fixed up correctly but I observed that's not continually the case. To create certain, you can run (you can operate it as usually as you want):
Then select your shoe disk, state you shoe from /dev/sda after that you select /dev/sda to conserve the shoe record. Usually you put on't want to select partitions like as /dev/sda1 unless that's how you booted before.
Reboot again to find if it functions ok. If therefore that's it.
This has been just a quick review and you should definitely go through the guides. But after many improvements to squeeze I discovered it nearly always boiled down to the above.
aseqaseq