OpenSUSE Network :: Invalid Command Line Option: Console Is Not Supported (1001) (403)?
Apr 7, 2010
I'm using linux suse 9.3. Recently i try to run execution files but it shows an error try running with the option "-console" or "-silent" When I tried with the -console option, I got the error - The wizard cannot continue because of the following error: Invalid command line option: console is not supported (1001) (403)
I used sg_sata_ident to get the IDENTIFY_DEVICE output on my SATA drive. The output shows the drive as being able to support READ_BUFFER/WRITE_BUFFER. However, when I issue sg_read_buffer /dev/sda, I get an error - DRIVER_SENSE - Invalid command operation supported.
when i show status ricci on centos5.3x86_64 #service ricci status pidof: invalid options on command line pidof: invalid options on command line p is stopped how can i fix that bug ?
...../etc/init.d/before.local...System Console Stolen at line: 266 This line of red warning consistently appears immediately after something that ended with /etc/init.d/before.localThis is during the boot.Have anyone see it before ?It appears both in kernel versions:2.6.37.6-0.5-desktop2.6.37.1-1.2-desktop
I'm aware I can do !commands but I'd like to somehow integrate a shell in vim. Or could I use screen and split the screen so that vim takes up say, half of the screen?
It used to be with (old) grub you could hit a function key and add a runlevel option to boot a console, but I don't know how to do this here, wanting not to edit the grub config file, as seems the only apparent option: I'm trying to boot into SimplyMepis where there is no rescue menu option, so need the prompt?
$ ls one.tar.gz one.tar.gz $ tar -xvfz one.tar.gz tar: z: Cannot open: No such file or directory tar: Error is not recoverable: exiting now $ tar -xvzf one.tar.gz one $ tar -xzvf one.tar.gz one $ tar -zxvf one.tar.gz one $
I would like to manage the firewall from the command line or with files VIA puppet, however this peice of software seems pretty complicated compared to the other distributions and generic iptables commands / configurations we push out.
I am trying to get my standard PS/2 Wheel mouse working on the Console command line, and seem to be having major problems getting it to work.
For the record, I am NOT talking about X, Xterm's or any Graphical Interface, my mouse wheel works fine in these environments.
I am purely concerned with getting the mouse wheel to work on the Console.
After many hours of reading forum posts about getting the wheel to work on the Console, this is what I have tried to date:
1. I have downloaded and installed every version of gpm I could find in the hope that one would utilise the wheel. (No Success).
2. I compiled and installed the latest version of gpm stable (1.20.6) to see if the wheel would work with it. (No Success).
3. I have tried setting up gpm-1.20.6 as a repeater to X, using every string I could find (msc, ms3, pnp .. etc), as well as every /dev entry in xorg.conf /dev/mouse, /dev/input/mice/, dev/gpmdata/, /dev/psaux ... etc). (No Success).
4. Created directories and configured a gpm.conf to both /etc/ and /etc/conf.d/ in the hope that gpm was looking for them there (read that in one forum or another). (No Success).
5. I then tried to find mouse wheel patches for gpm, and then downloaded the relevant version source gpm.***.tar.gz to go with these patches. Nearly every single one of the patches failed to apply (using patch -p1 >), except for one version I tried that did apply ... but then failed to make (stating that the source had a different signedness or some such thing) ??? (No Success).
6. I looked into IMwheel, but that seemed to be a purely X program that was a lazy way of writing ZAxisMapping in xorg.conf. (No Success).
So now I am stumped ... Does anyone know if if is possible to get:
a). A Wheel Mouse Patch for a recent version of gpm (1.20.6) that will actually apply, and then make?
b). A prepackaged recent version of gpm-1.20.6.tgz that has been patched to enable the wheel that I can use?
c). Any other information that may enable the mouse wheel to start working on the console.
I am having memory problems on my old Compaq PC, and am trying to run memtest86+-4.20 to check it. I downloaded the source file, and tried a compile, but had the following problem:
I am having a problem with running the mplayer dvdnav option from the command line or terminal. I run the command and this is what I get:
mplayer -nocache dvdnav://1 /media/CDROM /dev/scd1 MPlayer SVN-r1.0~rc3+svn20090426-4.4.3 (C) 2000-2009 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control.
Playing dvdnav://1. No stream found to handle url dvdnav://1 Playing /media/CDROM. File not found: '/media/CDROM' Failed to open /media/CDROM .....
I went on the forums and they say that some of the packages built to support dvdnav are out of date and that they should be updated. By the way I am running ubuntu 10.04 lucid lynx with lxde as my desktop manager.
I have a Asus EEE PC 1005P which I installed a Command-line system on using the Alternate Installer CD of Ubuntu Lucid Lynx. Altough I think this is a general linux and grub2 question. I do not have (or want) the X Window System installed. I want to change my console screen resolution (not inside X) to 1024x600. But it isn't reported when I use vbeinfo inside grub:
grub> vbeinfo VBE info: version: 3.0 OEM software rev: 1.0 total memory: 8128 KiB List of compatible video modes: Legend: P=Packed pixel, D=Direct color, mask/pos=R/G/B/reserved 0x112: 640 x 480 x 32 Direct, mask: 8/8/8/8 pos: 16/8/0/24
[Code]...
Does it mean I have the driver? how to set it to 1024 x 600 in grub2?
whenever I tried to boot into V1 in the following, it hang.
# uname -a Linux tadpole 2.6.32.12-0.7.1.1381.1.PTF-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/*release*
[code]....
After using yast2 and install "xen" hypervisor, the bootloader show "V1" as label for Xen kernel, if I choose to boot into V1, it will just hang with very little message on screen:
After coming home one evening I found my server was turned off. My suspicions lead me to believe we had a storm and the power went off, then the UPS went off and finally at that point the server went off too. I think my server was set to allow security updates. After it turned of and restarted it seems it made a change to Grub and upgraded it to Grub2. In doing so I now get the following message:
Error 13: Invalid or un supported executable format
I have tried to do the following:
url
This solved the problem for me, from > url
Quote:boot from the live medium and chroot into the Linux installation:
I've just tried to install X on my new debian system which had a nasty side effect. I can see the bootcycle up to "Waiting for /dev to be fully populated." and then the screen switches into a display mode unsupported by my display. I've had problems like this many times before because the display returns it's capabable of resolutions like 2048x1536, which it just isnt. I've had to disable autodetection whenever using this display. One thing to note thought is that it's NOT X that's messing up the display. It's setting the wrong display mode even before the filesystems are mounted. And I've already uninstalled X with no change either. Also recovery(single user) mode has no proper display output either.
after trying several pci and usb network cards none were able to have their ssid broadcasted. The question that i have is: Can a suse box be converted to act as an acces point without the use of atheros based hardware, without switching over to ubuntu and or debian, without the use of openwrt?
I hosed my installation of F14 by installing from some "experimental" repositories. Now I only get XDM at startup and an xterm on login. This would be fine if I could use yum to do some updates, but I have no network connection. I have been over the man page for nmcli dozens of times and none of the options there seems to start anything. I have also tried starting dhclient or using:
ifconfig eth0 up Nothing. So, is there a reliable way I can just connect to the network? This shouldn't be so hard.
I cannot connect to the internet on the command line. Things like firefox or chrome browser work fine. But on the command line programs like 'links' fail to work. This is on a machine behind a proxy, I have the http_proxy and https_proxy environment variables set properly.
For some reason Ubuntu 8.04 doesn't save my college network settings, so I have to connect manually each time. This is what I physically have to do to connect:
1) Click on network manager icon in the notification area 2) Click "connect to other wireless network" 3) Type in "NETWORK_NAME" into network name area field 4) Select WPA enterprise under wireless security 5) Type in "USERNAME" into username field 6) Type in "PASSWORD" into password field
So what I would like to know: is there any command line equivalent for the above six steps? I would like to write a script which will carry out the above six steps for me automatically, using the parameters NETWORK_NAME, USERNAME and PASSWORD.
my Setup is Fedora 14 x64 + radeon hd 4830 i've downloaded .run package from ati site with latest driver for x64 systems. installed it, but didn't edited grub.conf becouse i didn't understood anything there (probably didn't spent enough time to get things understand) Now i've lost possibility to enter my Fedora system. during boot it lost it's modern blue boot screen (with filling drop), it was replaced by standard old boot screen with triple-color stripe. after this boot screen monitor start blinking going on and off. and on last step i'm getting "Fedora 14 boot bla bla bla something" on screen. nothing works except Ctrl+Alt+Delete. system reboots showing successful daemons shutting sequence. How can i edit grub menu from initial grub screen is it possible to it's own 'e' option or 'c' from grub command line?
I am trying to compile the Cisco vpnclient on my Opensuse 11.2 and (after some troubles) I got the module compiled and installed but when I try to load with insmod I got this error
I am able to use the vpnclient forcing the module with modprobe -f cisco_ipsec but I'd prefer to solve the 'invalid format' original problem. I 'googled' around and it seems related with this warning during vpn_install script "WARNING: Symbol version dump /usr/src/linux-2.6.31.12-0.2/Module.symvers is missing; modules will have no dependencies and modversions." I have these rmps:........
i've gotten my fedora 12 to the point where i can run python3 scripts from command line and can call up python 2.6.2 idle with the command 'idle' from command line. what command will call up python3 (3.1.2 to be exact) idle?
I run Ubuntu, and it has a nice GUI widget thing that connects me to my home wireless network when I boot. I don't have a problem with that. But suppose I don't start X, and boot to a recovery console for some reason, like I did recently when my graphics were broken after installing Karmic. In that case, my computer won't be connected to the wireless network until I log into X normally. So I can't apt-get anything or anything. It's very annoying. And I don't know how to connect to my wireless network.
I know my wireless network SSID, and I know my WEP key or WPA passphrase. How can I log onto the network with commandline tools? Is there some basic program that I can just run "networkmanager <myssid> <mywepkey>"? I looked at the iwconfig man page and I honestly couldn't figure out how to simply connect to my network. Once I figure out how to connect to the network with command-line tools, where can I put an "autoconnect" script so that it will connect during startup, like it should anyway?
What I don't understand is, why the Ubuntu network manager nm-applet, doesn't just work as a front-end for more basic networking stuff. I don't see any reason why it should require you to start X before working; it could be a daemon that runs at startup, and there could be a config-file somewhere, but it doesn't even start running until I log onto gnome.
i just installed Debian 5.0.5 ! and i used guided partition (option one) while installing BUT immediately i cannot access my Windows drives C & D. if i click it , it says "Invalid mount option when attempting to mount the volume C " how to fix it?
I am fairly familiar with Linux but had never ventured into Wlan settings / options / too much. I have compatible card (aetheros) and when running - iwlist wlan0 scanning - I get plenty networks showing up - meaning the card works. When I installed distro which is last night (before I ran update), I had that little bars menu at the top of the screen that showed available networks once clicked upon. Since I like to modify and make my settings better - I removed that little AT&T like bar, and now rebooted after update to find that I can not see available networks unless I use iwliset wlan0 scanning.... .#$*&)@&#(&%# - need I say more.
Two questions - how do you connect to the wireless network via command line? What is that vertical bars GUI tool called so I can find it and run it again? Is there (for the love of god) alternative to system-config-network GUI managment tool for wlan?