Old draft I never published:
Sadly, there aren't any binaries to install orange from. In theory nightly builds are nice as you have the latest changes, however in practice, a lot can go wrong.
Download the nightly build (bottom of page) for linux
Extract the zip file.
follow the instructions for install listed here:
http://www.ailab.si/orange/installation_suse.html
caveots:
- the version of numpy and PyQwt need to be incremented to the verson you downloaded.
- when trying to run Orange Canvas, you will get an error "ImportError: No module named orange"
- create a blank file named __init__.py in the /usr/lib64/python2.6/site-packages/orange directory (this solution found here)
that fixes that error, but then you are stuck by:
> python /usr/lib64/python2.6/site-packages/orange/OrangeCanvas/orngCanvas.pyw
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/orange/OrangeCanvas/orngCanvas.pyw", line 13, in <module>
import orngTabs, orngDoc, orngDlgs, orngOutput, orngHelp, OWReport
File "/usr/lib64/python2.6/site-packages/orange/OrangeWidgets/OWReport.py", line 21, in <module>
from OWWidget import *
File "/usr/lib64/python2.6/site-packages/orange/OrangeWidgets/OWWidget.py", line 7, in <module>
from OWBaseWidget import *
File "/usr/lib64/python2.6/site-packages/orange/OrangeWidgets/OWBaseWidget.py", line 95, in <module>
from orange import ExampleTable
Tuesday, September 10, 2013
Installing OpenSUSE on ASUS K55A
Burned and installed a copy of KDE OpenSUSE 11.4.
Things to prep for install:
Enter "BIOS" Setup (press <esc> during boot.
enable UEFI Compatibility Support Module
disable Fast Boot Mode
Boot the CD/DVD in UEFI mode
Results:
Live CD seemed to work well, but I was unable to activate wirless.
Grub for UFEI worked!!
Wireless after install still did not work as the wireless adaptor seems to not have been detected. Ended up installing Ubuntu, which worked great.
Things to prep for install:
Enter "BIOS" Setup (press <esc> during boot.
enable UEFI Compatibility Support Module
disable Fast Boot Mode
Boot the CD/DVD in UEFI mode
Results:
Live CD seemed to work well, but I was unable to activate wirless.
Grub for UFEI worked!!
Wireless after install still did not work as the wireless adaptor seems to not have been detected. Ended up installing Ubuntu, which worked great.
Thursday, February 25, 2010
Installing Samsung Wifi Printer (CLP-315W) on OpenSUSE
Preamble
After getting up my Brother MFC all set-up I've found that the ink cartiges were empty despite a complete lack of use. Apparently the printer automatically flushes ink every so often to keep the print-heads from clogging. The idea of having to buy new ink 2ce a year when I hardly print really bothered me, so I decided it's time to make the move to laser.
As the rest of the Multifunction Brother is still in working order, I had trouble justifying the purchase of a brand new one with laser, the extra cost was the nail in the coffin. Further, as I checked prices, multi-function units with color were extremly expensive, so it only made sense that if I could find a network-able color laser printer for a reasonable price, I'd probably go with it. With wireless networking and a $130 price tag, the Samsung CLP-315W was impossible not to bring home, despite my grudge against Samsung for it's poor (inexistent) linux support on it's multifunction printers.
Installation
Setting up the printer:
Setting up the printer was relatively easy, it only required removal of some packing tape, and plugging in the power cord and an ethernet cable into my router; the toner cartridges were already installed.
Activating wireless:
This was also simpler than I expected. I have a hidden network and was worried that the printer might have trouble connecting to it. After connecting your pinter via ethernet to your router (assuming your router automatically assigns IPs)
Forget about finding a RPM binary, the tar.gz-ed 'unified driver' download was also a breeze. Assuming you are using KDE:
Adding the printer:
There may be a better (more uniform) way to do this described here (I haven't tried)
Print the image above and verify
Changing color values:
Update
My router died and thus all network devices, including my printer were given new IPs (they weren't force-ably assigned in a logical manner before, and the new router doesn't seem to have the feature to set an IP based on MAC.
Stealing (forcing) an IP
As before you are going to have to either guess your printer's new IP or find it in your routers clients table if your address was previously being assigned by DHCP. Once you know this you can then force the IP of the printer to be what ever you want:
Just follow the instructions under "adding the printer" above but delete the old printer before adding the new one. Reboot before trying to send a test page (to properly reset the samsung utility).
After getting up my Brother MFC all set-up I've found that the ink cartiges were empty despite a complete lack of use. Apparently the printer automatically flushes ink every so often to keep the print-heads from clogging. The idea of having to buy new ink 2ce a year when I hardly print really bothered me, so I decided it's time to make the move to laser.
As the rest of the Multifunction Brother is still in working order, I had trouble justifying the purchase of a brand new one with laser, the extra cost was the nail in the coffin. Further, as I checked prices, multi-function units with color were extremly expensive, so it only made sense that if I could find a network-able color laser printer for a reasonable price, I'd probably go with it. With wireless networking and a $130 price tag, the Samsung CLP-315W was impossible not to bring home, despite my grudge against Samsung for it's poor (inexistent) linux support on it's multifunction printers.
Installation
Setting up the printer:
Setting up the printer was relatively easy, it only required removal of some packing tape, and plugging in the power cord and an ethernet cable into my router; the toner cartridges were already installed.
Activating wireless:
This was also simpler than I expected. I have a hidden network and was worried that the printer might have trouble connecting to it. After connecting your pinter via ethernet to your router (assuming your router automatically assigns IPs)
- Find the printers IP via your routers interface page
- Enter the IP into the address bar of your web browser
- Click on the Network Settings tab and then the Wireless sub-tab
- Enter your SSID and any access credentials.
- Unlplug the ethernet cable
Forget about finding a RPM binary, the tar.gz-ed 'unified driver' download was also a breeze. Assuming you are using KDE:
- Navigate to the download folder and right click on the download.
- Choose "'Extract here, auto detect subfolder"
- Click on the newly made "cdroot" folder
- Open a terminal in this directory by pressing the F4 key
- Execute the autorun shell script as root:
> sudo sh autorunAnswer the install scripts questions (press enter twice to accept defaults). Use the closest numbered print driver: CLP-310splc
Adding the printer:
- Lanch Yast (pres F2, type: yast).
- Click on the Hardware Icon then Printer.
- In the new window click the "Add" button.
- In the new window click "Connection Wizard" button.
- Under "Access Network Printer or Print Server via:" choose TCP port.
- Enter your printers IP adress and brand, choose "test connection"
- Click "Ok"
- Under Assign Driver choose the CLP-310 driver and click "Ok"
- Print a test Page
There may be a better (more uniform) way to do this described here (I haven't tried)
Print the image above and verify
- the magenta, yellow, and cyan colors don't look washed out in the top of the image.
- if not you need to increase the amount of the washed out color
- the lightest levels of magenta, yellow, and cyan all appear to be equally filled.
- if not you should increase or decrease the color value in each channel as needed
- that you can see all of the black gradients.
- if not you should increase or decrease black as needed.
Changing color values:
- Enter the IP address of your printer into the address bar of your web browser.
- Click on "Machine Status"
- Click on "Color"
- Increase/Decrease the color of interest as needed.
Update
My router died and thus all network devices, including my printer were given new IPs (they weren't force-ably assigned in a logical manner before, and the new router doesn't seem to have the feature to set an IP based on MAC.
Stealing (forcing) an IP
As before you are going to have to either guess your printer's new IP or find it in your routers clients table if your address was previously being assigned by DHCP. Once you know this you can then force the IP of the printer to be what ever you want:
- Enter the IP address of your printer into the address bar of your web browser.
- Click on the "Network Settings" tab
- Click on "TCP/IP" in the left side bar
- Increase/Decrease the color of interest as needed.
Just follow the instructions under "adding the printer" above but delete the old printer before adding the new one. Reboot before trying to send a test page (to properly reset the samsung utility).
Friday, February 12, 2010
Networked Brother Devices Including Multifunction Printer, Copier, Scanner, Fax
I have OpenSUSE boxes at home and work as well as networked Brother printers in both environments. Therefore I thought it would be useful to document the install process.
Installing the printer drivers
(if not a network printer see here)
Installing the scanner drivers
Installing the Fax drivers
Installing the printer drivers
- Download both the lpr and cupswrapper drivers for each Brother printer.
- Change to root:
- sudo su
- Install the lpr rpms: rpm -ihv --nodeps (lpr-drivername)
- for MFC-7840W
- rpm -ihv --nodeps brmfc7840wlpr-2.0.2-1.i386.rpm
- for HL-4040CN
- rpm -ihv --nodeps hl4040cnlpr-1.0.3-1.i386.rpm
- Check to see if it's installed: rpm -qa | grep -e (lpr-drivername)
- for MFC-7840W (or any MFC printer)
- rpm -qa | grep -e brmfc
- for HL-4040CN
- rpm -qa | grep -e hl4040
- Open your printcap file for editing (for non-network installs see here)
- nano /etc/printcap
- For each printer replace ":lp" line to the following 2 lines (
when done):
Installing the cups driver
- :rm=(ip address of your printer)\ :rp=lp\
- Set a root password for printing
- lppasswd -g sys -a root
- Create a symlink from cups to lpd
- ln -s /etc/init.d/cups /etc/init.d/lpd
- Install the cups rpms: rpm -ihv --nodeps (cupswrapper-drivername)
- for MFC-7840W
- rpm -ihv --nodeps cupswrapperMFC7840W-2.0.2-1.i386.rpm
- for HL-4040CN
- rpm -ihv --nodeps hl4040cncupswrapper-1.0.3-1.i386.rpm
- Verify both lpr and cupswrapper drivers are installed: rpm -qa | grep -e (lpr-drivername) -e (cupswrapper-drivername)
- for MFC-7840W (or any MFC printer)
- rpm -qa | grep -e brmfc -e cupsw
- for HL-4040CN
- rpm -qa | grep -e hl4040
(if not a network printer see here)
- Open a web-browser and enter: http://localhost:631/printers
- Click "Modify Printer" and set:
- Device
- "LPD/LPR Host or Printer" or "AppSocket/HP JetDirect"
- Device URI
- lpd://(Your printer's IP address)/binary_p
- Make/Manufacturer Selection
- Brother
- Model/Driver Selection
- Your printer's name
Installing the scanner drivers
- Download the appropriate scanner driver
- Double click on the driver and install via your graphical install program
- For the MFC-7840W open the Brsane2.ini file for editing
- nano /usr/local/Brother/sane/Brsane2.ini
- Add the following line at the end of [Support Model] section:
0x01eb,6,1,"MFC-7320",131,4 0x01e7,6,1,"MFC-7340",131,4 0x01e6,6,1,"MFC-7440N",131,4 0x01ee,6,1,"MFC-7450",131,4 0x01ed,6,1,"MFC-7840N",131,4 0x01e5,6,1,"MFC-7840W",131,4 0x01ea,6,1,"DCP-7030",131,4 0x01e9,6,1,"DCP-7040",131,4 0x01e8,6,1,"DCP-7045N",131,4
- exit nano (don't forget to save):
- Set your network scanner: brsaneconfig2 -a name=(name your device) model=(model name) ip=xx.xx.xx.xx
- For the MFC-7840W (change x's to actual IP)
- brsaneconfig2 -a name=7840Scanner model=MFC-7840W ip=xx.xx.xx.xx
- For the MFC-420CN (change x's to actual IP)
- brsaneconfig2 -a name=mfc420cnScanner model=MFC-420CN ip=xx.xx.xx.xx
Note: Use brsaneconfig (for brscan models), brsaneconfig2 (for brscan2 models) or brsaneconfig3 (for brscan3 models) accordingly
Note: The default install instructions here don't work. I somehow luckily stumbled across the proper install directions For users of MFC-7320, MFC-7340, MFC-7440N, MFC-7450, MFC-7840N, MFC-7840W, DCP-7030, DCP-7040, DCP-7045N here. Installing the Fax drivers
- Download the appropriate fax drivers
- Double click on the lpr rpm to install via your grapical package manager
- Double click on the cupswrapperfax rpm to install via your graphical package manager.
- Open a web-browser and enter: http://localhost:631/printers
- Click "Modify Printer" and set (for other connection options see here):
- Device
- "LPD/LPR Host or Printer" or "AppSocket/HP JetDirect"
- Device URI
- lpd://(Your printer's IP address)/binary_p
- Make/Manufacturer Selection
- Brother
- Model/Driver Selection
- Brother BRMFCFAX for CUPS(en)
- Open the file you want to send
- Choose "Print" from the file menu
- Choose the "print to file" option
- Save as "postscript"
- Send the file
- open a terminal and navigate to the directory your file is in
- type: brpcfax -o fax-number=(fax-number) (filename)
- or just type: brpcfax -o (filename).ps
- enter the phone number in the pop-up program
- Open Konquerer
- Go to Settings, Configure konquerer
- Click file associations
- Type “ps” in the search box and select “Application”-- “Postscript” from the list
- Click “Add” and type “brpcfax” and click OK
- Select the new “brpcfax option and click 'Edit”
- Select the Application tab
- In Command line enter: brpcfax -P BRFAX -o PAPER=A4
- For the Name enter Send As Fax
- Click on the blank Icon, System Icons, select printmgr (looks like a fax)
- Click OK and save
- Right click the (filename).ps file and select “Open with”
- click “Send As Fax”, the dialup screen gui should come up
- enter fax number
- click Send.
Wednesday, December 30, 2009
Getting Prism working on OpenSUSE
The reason I updated OpenSUSE 11.1 to 11.2 was that with the update I hoped to get a new version of Firefox that would work with the Mozilla Prism plugin. This was not the case, and after trying a few hacks surrounding the code the prism apps called (switching from Firefox to xulrunner) I still had no luck. Finally I stumbled upon the fact that someone is kind enough to be maintaining a beta repository for Mozilla products at OpenSUSE.
http://download.opensuse.org/repositories/mozilla:/beta/
I added the repository via zypper
http://download.opensuse.org/repositories/mozilla:/beta/
I added the repository via zypper
zypper ar http://download.opensuse.org/repositories/mozilla:/beta/openSUSE_11.2/mozilla:beta.repo
Then I installed Prism via YAST, and now Prism works like a charm!
Tuesday, December 29, 2009
Updateing from OpenSUSE 11.1 to 11.2
For a while I thought there was no straight upgrade path from OpenSUSE 11.1 to 11.2. Indeed, when I first checked the opensuse.org website had told me that I must do a fresh install, or minimally do an update via a live CD due to compatiblity issues. However, yesterday I was having some issues with Prism and decided to check again. Here is what I learned.
The process of updating consists of the following:
Zypper commands
List your repositories
Changing the name of a generic repository (to keep for legacy purposes):
Disabling all repositories:
Adding the new 11.2 repositories:
Adding other repositories (by url):
Refresing the repositories:
Installing a single new package (new version of zypper)
Downloading packages with out installing:
Installing all updated packages:
KDM didn't launch after installing and restarting
I dealt with this by logging in as a normal user then at the prompt typeing the command:
The Xserver crashed
as superuser I restored the old xconfig file:
then tried restarting X again
KDE didn't work well on first run and the widgets had a tenancy to crash, so after playing around and ensuring that KDM was indeed installed, I restarted again and everything was much smoother. Restarting was a bit tricky as it couldn't be done graphically or via sudo. One had to actually log in as root to command a restart.
At this point I noticed that my grub config file had been overwritten and I could no longer boot my other linux (Sidux) partition. I had to restore using the menu.lst file on the Sidux partition, but that was a bit of a headache, hopefully the rest of you backed up your menu.lst file somewhere
- Upgrades are now fully supported: http://en.opensuse.org/Upgrade/Supported
- OpenSUSE has a program called "zypper" that is similar to debian's apt-get
- zypper reporsitories can be eaisly added / removed and updated
The process of updating consists of the following:
- *Back up your /boot/grub/menu.lst file (not mentioned in the above link)
- Check your sources and rename any repositories that will be updated
- Disable all current repositories
- Add the updated repository sources.
- Refresh the repository list and download the latest version of zypper
- Download all the packages before installing.
- Install the new packages.
Zypper commands
List your repositories
zypper ls -d
Changing the name of a generic repository (to keep for legacy purposes):
zypper renamerepo repo-oss 111-repo-oss
Disabling all repositories:
zypper modifyrepo --all --disable
Adding the new 11.2 repositories:
zypper addrepo --name "openSUSE-11.2 OSS" http://download.opensuse.org/distribution/11.2/repo/oss/ repo-oss zypper addrepo --name "openSUSE-11.2 Non-OSS" http://download.opensuse.org/distribution/11.2/repo/non-oss/ repo-non-oss zypper addrepo --name "openSUSE-11.2 Updates" http://download.opensuse.org/update/11.2/ repo-update
Adding other repositories (by url):
zypper ar
Refresing the repositories:
zypper refresh
Installing a single new package (new version of zypper)
zypper in zypper
Downloading packages with out installing:
zypper dup -d
Installing all updated packages:
zypper dup
Problems I Encountered
KDM didn't launch after installing and restarting
I dealt with this by logging in as a normal user then at the prompt typeing the command:
startX
The Xserver crashed
as superuser I restored the old xconfig file:
sudo su
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bad
cp /etc/X11/xorg.conf.saxsave /etc/X11/xorg.conf
exit
then tried restarting X again
startX
KDE didn't work well on first run and the widgets had a tenancy to crash, so after playing around and ensuring that KDM was indeed installed, I restarted again and everything was much smoother. Restarting was a bit tricky as it couldn't be done graphically or via sudo. One had to actually log in as root to command a restart.
su
restart
At this point I noticed that my grub config file had been overwritten and I could no longer boot my other linux (Sidux) partition. I had to restore using the menu.lst file on the Sidux partition, but that was a bit of a headache, hopefully the rest of you backed up your menu.lst file somewhere
Subscribe to:
Posts (Atom)