| Why can't Linux see my NIC? Posted: 19 Feb 2004 09:32 PM PST "Hiawatha Bray" <com> wrote in message news:<QZgZb.62972$gnilink.net>...
Not sure about SUSE specifics and "red failed flags", but there are a
few things you can check.
"lspci" will show you if linux can see the NIC at all (assuming it is
pci)
"ifconfig -a" will show you all configured network interfaces
"lsmod" will show you which modules you have loaded
I'd take a guess that you don't have the module (In "Windows" I guess
you'd call this a "driver") loaded. Either way, running those commands
will show you wether your NIC is correctly set up or not. If there is
no problem with the nic, then you can move on to how you're doing
DHCP.
|
| Mandrake 9.2 - starting up the modem Posted: 19 Feb 2004 07:04 AM PST Andreas Janssen (com) writes:
Andreas,
Thank you very much. That was exactly what I needed. It installed
neatly and I have also created an icon for it on the desktop. Now I am in
business. Thanks again!
Best regards,
.... Martin
|
| File Permission/Group Does Not Stick Posted: 19 Feb 2004 01:54 AM PST In article <uJ%Yb.4769$news.prodigy.com>,
Hank Kingwood <xyz> wrote:
I suspect something in /etc/rc.d or some module (maybe serial?) changes
the mode of /dev/ttyS* early in the boot sequence.
--
-eben rIr.OcoPm home.tampabay.rr.com/hactar
CANCER: The position of Jupiter says that you should spend the
rest of the week face down in the mud. Try not to shove a roll of
duct tape up your nose when taking your driver's test. -- Weird Al
|
| RH9 first boot hanging at "Updating /etc/fstab" Posted: 18 Feb 2004 04:39 PM PST Vilmos,
Thank you for your in-depth explanation... It really helped. My next
goal is to assure /etc/fstab consistency with the devices plugged into
my system.
Tim
Vilmos Soti wrote:
|
| Modules not loading after 2.6.3 Posted: 18 Feb 2004 01:41 PM PST On Wed, 18 Feb 2004 23:41:28 +0200, Theophanis Kontogiannis wrote:
Please follow the directions provided here to create the
/etc/modprobe.conf file; http://thomer.com/linux/migrate-to-2.6.html
A small quote from the above link;
You need a new modprobe, insmod, rmmod, etc. If you don't, you'll get
errors about ``QM_MODULES: Function not implemented.''
And use the latest module-init-tools-3.0-pre9.tar.gz (or .bz2) available
here; ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/
Because you don' have a working /etc/modprob.conf file.
--
Posted under the XFree86 v.1.0 license
Copyright remains with the author
|
| Debian - Problems with kernel-image-2.4.18-12.1tsc Posted: 18 Feb 2004 07:52 AM PST Hello
Film (<org>) wrote:
Yes, or by loading it with modprobe and adding it to /etc/modules (which
is what modconf does). However, if you want to have the driver
available from the beginning, you may have to add it to the initrd.
Also call dmesg and see if it tells you anything about the mode and
driver that is used for your consoles.
best regards
Andreas Janssen
--
Andreas Janssen <com>
PGP-Key-ID: 0xDC801674
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html
|
| i'd like to add new hard disk !! Posted: 18 Feb 2004 07:08 AM PST David wrote:
Ooops!! That should be: mkfs.ext2 -J /dev/hdd1
--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.24 SMP i686 (GCC) 3.3.3
Uptime: 44 days, 8:17, 3 users, load average: 0.20, 0.13, 0.1
|
| LibGl error Posted: 17 Feb 2004 05:08 PM PST Adam K Kirchhoff <com> wrote in message news:<ashke.com>...
I also have an ATI Rage IIC Pci (or ATI Rage Mach64) with the same problem.
|
| USB Modem? Posted: 17 Feb 2004 02:21 PM PST Maurice Batey wrote:
My USB Zip drive is the IOmega 100mB, which receives its power right from
the USB port. I have never had problems booting with it plugged into the
USB port. Also, Linux (2.4.23 kernel) is able to find it on the bus if I
plug it in after booting.
Do you suppose yours fails because you Brits drive on the wrong side of the
road? Hm, probably not.
Roby
|
| Best way to "Clone" a Linux Hard drive? Posted: 17 Feb 2004 02:14 PM PST Chris Cox <net> wrote:
Eh? A copy is a clone. If you are trying to say that you want a copy
that preserves the exact bits on disk, rather than "just" the
arrangement of files, then by all means say so rather than reaching for
a word that does not mean what you think it means!
But unfortunately that will not work to give you a working boot sector
in all situations. In fact. in very few.
Kindly stop insulting people you unpleasant slug ...
?? "on drugs" is an expression meaning "hallucinating, seeing things
in a distorted way, living in a private universe, etc.". That's what
you seem to be!
There is no difference. I am not confusing anything, you are! I told
you what clone means. I'll write it out for you again if you like!
1. An exact duplicate: "Our product is a clone of their
product." Implies a legal reimplementation from documentation
or by reverse-engineering. Also connotes lower price.
2. A shoddy, spurious copy: "Their product is a clone of our
product."
3. A blatant ripoff, most likely violating copyright, patent,
or trade secret protections: "Your product is a clone of my
product." This use implies legal action is pending.
Etc.
Eh?
You said it!
Then you would be wrong. COPYING a boot sector (note,not "cloning")
does not give you a bootable machine.
It doesn't matter, whatever you are trying to say (I suspect you are
trying to get out words that mean that the offset on disk of the
target kernel or secondary stage loader will be changed by the copy
from the original, which means that the CLONED boot sector will miss
it, since it still has the physical location of the original embedded
in it).
That's "right". That's why you have to COPY the boot sector and CHANGE
it for its new environment.
Do YOU get it? Apparently not!
You see - you don't know how that boot sector was generated. Therefore
you don't know what it is aiming at. Theerfore you don't know what to
repoint it at.
Nor do you know which disk it is trying to boot. Nor what the new
bios calls that disk (0x80? 0x81?).
Yes, if you take all the disks from one machine, and copy them to all
the disks of another machine, and put them in exactly the same places,
and remove all other devices, and tell the bioses that the disks have
exactly the same geometry, and arrange the bios boot orders to be
exactly the same on both machines, then you would get a booting disk.
OK?
But nobody has ever seen two machines built more than two weeks apart
that are exactly the same.
Peter
|
| Advice wanted on Laptop Setup Posted: 15 Feb 2004 01:39 PM PST On Sun, 15 Feb 2004 21:39:17 +0000, The Professor wrote:
Please go take a look at http://www.linux-laptop.net
You didn't give us the model of the laptop so it's impossiable to tell if
it is going to ba compatable. Most modern linux distro's are really good
at hardware, but laptops are picky at beat. The above site will point you
in the right direction.
Jayson G
|
