I've got a linksys wireless network and I'm wondering if there is device
support for it in the linux kernel, and more realistically, if there are some
drivers out there that can make it work. Specifically, I'm hoping to find
some way to connect to the internet.
The current setup is a wireless
sorry to be the bearer of bad news, but:
the lexmark Z series are totally useless in linux. they rely heavily on
windows drivers to control them. this is good for the windows user because
the drivers handle a lot of the printers functions (like Linus Torvalds new
CPU that uses software to run
no
he just wants it not to load when he boots, but still work when startx is
invoked
a simple solution to prevent xdm from starting everytime you boot is to
remove xdm from /etc/rc2.d. See, whenever linux boots it runs a script that
causes the files in /etc/rcN.d where N is a number between 1 a
yea, that kind of error also results from incorrect configuration.
Specifically, make sure you specify refresh rate ranges that will work with
whatever resolution and colour choices you make.
phreaking, yea!
anyway... i had the same problem: as it turns out the XFree86 organization
has temporarily phased out XF86Config with XFree86 4.0 (the x server included
in debian's testing distribution).
They suggest using either xf86cfg or XFree86 -configure, but both of these
caused my machi
is there some website, piece of documentation, or man page w/ a complete (or
at least reasonably complete) list of major and minor numbers?
okay, so after learning that XF86Setup is not working anymore (why did they
do that? it seemed like a really good prog) i've installed xserver-XFree86,
etc. so that i could run XFree86 (and in effect, xf86cfg which is dependent
on it). So i installed the packages, and just ran XFree86 as root wi
so then i guess those guys keyboards don't have a shift key, huh? : ) (forget
who kept making the keyboard : program analogies)
anyway, good! i'm getting somewhere, however i'm getting kind of tired of
the debian dpkg approach. however, i'm going to make one more attempt to get
a configuration
a simple solution to prevent xdm from starting everytime you boot is to
remove xdm from /etc/rc2.d. See, whenever linux boots it runs a script that
causes the files in /etc/rcN.d where N is a number between 1 and 6 (called
runlevels). Debian is set to runlevel 2 by default so by removing xdm fro
I'm working on upgrading to woody, and here's my latest x windows problem:
I'd installed xdm and xbase-clients (with all the dependent files and stuff)
then i ran XF86Setup, which worked fine at this point. Afterwards, I finished
my x installation by dpkg ing xserver-common, and xserver-svga (whi
a simple solution to prevent xdm from starting everytime you boot is to
remove xdm from /etc/rc2.d. See, whenever linux boots it runs a script that
causes the files in /etc/rcN.d where N is a number between 1 and 6 (called
runlevels). Debian is set to runlevel 2 by default so by removing xdm fro
i've re-installed the xf86setup packages and all the packages that depend on
it
however, i'm still getting errors such as
"Warning Server spcification missing in card database entry for "
or
"Warning Chipset spcification missing in card database entry for "
perhaps i need to install the severs fo
does woody have XF86Setup, or do you just assume that whoever's running woody
can handle xf86config? b/c after getting my x window system working (more or
less) i decided i needed to reconfigure things a bit (because it was only
more or less running).
i searched for XF86Setup on the packages lis
i'm upgrading to woody, and for various reasons, i'm not able to use apt-get.
i am, however, able to download packages and install them using dpkg.
so far i've installed xdm and xserver-ggi
however i get the following message when i run 'startx'
" /usr/X11/R6/lib/X11/xini/xserverrc: /usr/bin/X11/
when installing xdm_4.0.3-4i386.deb using dpkg_1.9.16.deb i get the following
error message:
"Error: /usr/x11R6/lib/x11/xdm symbolic link does not exitst. Either the
package didin't ship w/ a symbolic link (a bug in the backage), or dpkg
failed to unpack it to the filesystem (a bug in dpkg).
Ple
when installing xdm_4.0.3-4i386.deb using dpkg_1.9.16.deb i get the following
error message:
"Error: /usr/x11R6/lib/x11/xdm symbolic link does not exitst. Either the
package didin't ship w/ a symbolic link (a bug in the backage), or dpkg
failed to unpack it to the filesystem (a bug in dpkg).
Ple
>i ran
>"dpkg -i --auto-deconfigure xlibs-43433-4_i386.deb"
>and got
>dpkg: considering removing xlib6g in favor of xlibs
>dpkg: yes will remove xlib6g in favor of xlibs
>dpkg: /home/wichert/debian/dpkg-1.6.15/main/archives.c:601:check_conflict:
>Assertion 'fixbyrm -> client data -> istobe == itb_
i ran
"dpkg -i --auto-deconfigure xlibs-43433-4_i386.deb"
and got
dpkg: considering removing xlib6g in favor of xlibs
dpkg: yes will remove xlib6g in favor of xlibs
dpkg: /home/wichert/debian/dpkg-1.6.15/main/archives.c:601:check_conflict:
Assertion 'fixbyrm -> client data -> istobe == itb_normal'
okay here's what i did:
dpkg -i libdb3_3.2.9-11_i386.deb
{errors}
dpkg -i libdb3++-dev_3.29-11_i386.deb
{needs libdb3_3.2.9-11_i386.deb installed, so i figure out how to do that:}
dpkg -i --auto-deconfigure libdb3_3.3.9-11_i386.deb
{works fine}
dpkg -i libdb3++-dev_3.29-11_i386.deb
{works}
dpkg -i
i recently tried (and so far failed) to install printtool... and in the
process i seemed to have wiped out gnome... here's what happened:
i'm running 2.2r3 so i had to upgrade a lot of libraries, ect. to get to the
point where i had all the nessicary files to dpkg printtool... (one file that
pri
i recently tried (and so far failed) to install printtool... and in the
process i seemed to have wiped out gnome... here's what happened:
i'm running 2.2r3 so i had to upgrade a lot of libraries, ect. to get to the
point where i had all the nessicary files to dpkg printtool... (one file that
pri
http://www.linuxprinting.org/show_printer.cgi?recnum=464242 says that the
epson stylus color 777 supports direct ascii printing. So i set up the new
printer (using usb, not paralell port and an appropriate device name) and ran
the command
'lptest 35 6 > /dev/usb/lp0'
as root. I've tested the sa
I'm sorry not to have provided more information in my first e-mail although
i'm very glad so many people responded to help, but i've done some more
testing:
specifically i'm getting 'prase error in tmp/x' where x is a long string of
characters that tends to change on every run of the complier (
when i try to use the sqrt function in gcc 3.0, and the gcc that's standard
with 2.2r3 ( i forget the version) i get errors. here's some example code:
#include
#include
double num;
double num_root;
int main ()
{
num = 4;
num_root = sqrt(num);
return (0);
}
fails to compile. i've
a couple of basic questions:
1. if a user's path isn't specified in .bashrc, what path is used, and what
file is it found in?
2. are paths recursive? (i'm thinking not on this one, or else why not just
set the path to the root directory?)
remember, the device NAMES are irrelivant. your mouse could be called
/dev/mongoose and still function as a mouse if you give it the correct major
and minor numbers which you can view w/ 'ls -l'. So if you can't find a mouse
device, consider just making one of your own.
I understand that a command such as 'lptest 20 10 > /dev/lp1' (or lp0) will
print a test page to a parallel port printer assuming the device file
properly links to the printer. I have a usb printer instead (as well as a
kernel that supports it, and the device file '/dev/usb/lp0' with the, i
thi
I understand that a command such as 'lptest 20 10 > /dev/lp1' (or lp0) will
print a test page to a parallel port printer assuming the device file
properly links to the printer. I have a usb printer instead (as well as a
kernel that supports it, and the device file '/dev/usb/lp0' with the, i
thi
I'm attempting to compile kernel 2.4.6 on 2.2r3. Yes, i know .7 is out, but
when i tried to unpack the archive I downloaded from ftp.kernel.org i got
errors using the same method I used to unpack the 2.4.6 kernel successfully
so i thought i'd just stick with it.
Anyway, i've gone through the in
I'm working on building a new kernel (just realized my newly 'bought' debian
2.2r3 has kernel 2.2 not 2.4 for some reason). Currently, the kernel is in
/boot but i thought i'd install the new one in /usr/src/linux as i'm told its
more of a "standard" directory for kernels. I know there's a symbo
i've noticed in a lot of shell scripts for bash items beginning w/ a '$' used
to refer to things. for example: i'm pretty sure '$1" refers to any arguments
given to the script.
so what is this method of referring to things called? and is there somewhere
i can find a list of all of the "$_"
thanks to everyone who helped with my mformat problem, but i am still unable
to get my boot disks working so i though i'd write another e-mail in a little
bit greater detail
the disk created with 'mkboot /boot/vmlinuz2.2.17pre19" does work to boot the
system by starting lilo (produces "LILO boo
I'm running 2.2r3 i-386.
1. When I run 'superformat /dev/fd0' the disk is formatted. However, when
superformat tries to run mformat to created an msdos file system, I get the
error message
'sh: error:command not found'
or something similar. When i simply type 'mformat' i get a similar error
me
33 matches
Mail list logo
