Newbie problem finding module
I have just installed Woody on my system. My first problem is that I can't start the X server. Searching various archives I have determined that the problem is most likely associated with the i815 graphics chips on the MB. lsmod does not show that agpgart is installed as a module [there is an entry /dev/agpgart] modprobe -l agpgart doesn't return anything the only files that show up in my installed file system are agpgart.h /dev/agpgart Where do I find the files to install that module? TIA Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Newbie problem finding module
Sorry the old stuff didn't get quoted. I've not used mozilla for this previously. My operating system is Linux 2.4.17 i686 [ELF] It came off of CD#1 of the Woody set. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Newbie problem finding module
* Paul Schwartz ([EMAIL PROTECTED]) [031208 10:28]: I have just installed Woody on my system. My first problem is that I can't start the X server. Searching various archives I have determined that the problem is most likely associated with the i815 graphics chips on the MB. lsmod does not show that agpgart is installed as a module [there is an entry /dev/agpgart] modprobe -l agpgart doesn't return anything the only files that show up in my installed file system are agpgart.h /dev/agpgart Where do I find the files to install that module? What kernel are you running? If you don't know, 'uname -r' will tell us. Linux 2.4.17 i686 [ELF] Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Newbie problem finding module
* Paul Schwartz ([EMAIL PROTECTED]) [031208 10:28]: I have just installed Woody on my system. My first problem is that I can't start the X server. Searching various archives I have determined that the problem is most likely associated with the i815 graphics chips on the MB. lsmod does not show that agpgart is installed as a module [there is an entry /dev/agpgart] modprobe -l agpgart doesn't return anything the only files that show up in my installed file system are agpgart.h /dev/agpgart Where do I find the files to install that module? What kernel are you running? If you don't know, 'uname -r' will tell us. Got it wrong last time. The old info came from the XFree86 log file. The actual kernel is 2.2.20-idepci What does that mean for finding the modules? Are they on CD#2? Thanks Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
newbie: more startup problems
Earlier I have written about not being able to find the agpgart module [I can't start X] I have been trying to enable web access to update apt, etc. I have tried two ways: wvdial and pon Both seem to connect to my ISP and establish ppp, but none of the programs I run are able to communicate with the outside. I have tried to ping by name [my ISP's domain] and by numerical address [the DNServers] No responses. The only response is for localhost. I have tried to do this logged in as root, and have tried in separate terminal windows and [with pon] in the same terminal window. Any suggestions would be appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: newbie: more startup problems
Lucas Bergman wrote: Paul Schwartz <[EMAIL PROTECTED]> writes: Earlier I have written about not being able to find the agpgart module [I can't start X] Okay. Is this still a problem? Yes, it is. Browsing through the Contents on CD #2, I find that agpgart.o is supposed to be part of the base kernel. I can't find it in my installation. I have been trying to enable web access to update apt, etc. I have tried two ways: wvdial and pon... Both seem to connect to my ISP and establish ppp, but none of the programs I run are able to communicate with the outside. What do 'ifconfig' and 'cat /etc/resolv.conf' and 'netstat -rn' say after you've connected? Lucas ifconfig gives [what's in IFCONFIG.TXT] /etc/resolv.conf is nameserver 207.217.126.81 nameserver 207.217.120.83 and netstat -rn gives Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 63.215.28.440.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.0.2 0.0.0.0 255.255.255.255 UH0 0 0 sl0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.2.1 0.0.0.0 UG0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 sl0 I think I understand that the ppp0 is what I'm trying to use to access the internet. the 192.168.2.x stuff is from my lan. I don't know where the 192.168.0 came from. Hope this helps you help me. :-) Paul eth0 Link encap:Ethernet HWaddr 00:90:47:02:F2:1D inet addr:192.168.2.94 Bcast:255.255.255.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1748 (1.7 KiB) TX bytes:3923 (3.8 KiB) Interrupt:10 Base address:0xd000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:21 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1327 (1.2 KiB) TX bytes:1327 (1.2 KiB) ppp0 Link encap:Point-to-Point Protocol inet addr:67.31.182.205 P-t-P:63.215.28.44 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1524 Metric:1 RX packets:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:1423 (1.3 KiB) TX bytes:304 (304.0 b) sl0 Link encap:Serial Line IP inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Re: newbie: more startup problems
Lucas Bergman wrote: Paul Schwartz <[EMAIL PROTECTED]> writes: Lucas Bergman <[EMAIL PROTECTED]> writes: Paul Schwartz <[EMAIL PROTECTED]> writes: Earlier I have written about not being able to find the agpgart module [I can't start X] Okay. Is this still a problem? Yes, it is. Browsing through the Contents on CD #2, I find that agpgart.o is supposed to be part of the base kernel. I can't find it in my installation. I've been in the habit of making my own kernel these days, so I admit I have no idea what comes with the standard one. I have been trying to enable web access to update apt, etc. I have tried two ways: wvdial and pon... Both seem to connect to my ISP and establish ppp, but none of the programs I run are able to communicate with the outside. What do 'ifconfig' and 'cat /etc/resolv.conf' and 'netstat -rn' say after you've connected? ifconfig gives... [ ... ] ppp0 Link encap:Point-to-Point Protocol inet addr:67.31.182.205 P-t-P:63.215.28.44 Mask:255.255.255.255 That line says that your IP address is 67.31.182.205 and the IP address of the server end of the PPP connection is 63.215.28.44. Keep that in mind. /etc/resolv.conf is nameserver 207.217.126.81 nameserver 207.217.120.83 Seems okay, I guess. and netstat -rn gives Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 63.215.28.440.0.0.0 255.255.255.255 UH0 0 0 ppp0 192.168.0.2 0.0.0.0 255.255.255.255 UH0 0 0 sl0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.2.1 0.0.0.0 UG0 0 0 eth0 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 sl0 Ding! This (the second-to-last line) says that your default traffic is going through eth0, not ppp0. # route del default # route add default gw 63.215.28.44 This worked! DNS is working and I can ping lots of places [not all; don't know what that means] pppconfig put a default parameter in the ISP file, but it doesn't seem to be taking charge. I am doing apt-get update as I write, so this is progress. Thanks. Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Quickie question before reinstall
I found reference to the other installation kernel flavors on the Woody CD. Is there a way to install another one of those kernels [vanilla, bf2.4] without doing a reinstall? Does anyone know which is likely to include the agpgart module that supports the i810 video chipset? Thanks Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Install confusion
After reading about using the F3 key at the initial boot screen from the Woody CD#1, I decided to try it. At the boot: prompt I typed bf24 and sent the install on its way. Answered all the questions, made a boot floppy, and rebooted using said boot floppy. Result: the new boot floppy was identical to the original; my kernal was still 2.2.xx-idepci Why didn't I get the bf24 kernal? Help! TIA Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install confusion
Hope this isn't a duplicate. Andreas Janssen wrote: Hello Paul Schwartz (<[EMAIL PROTECTED]>) wrote: After reading about using the F3 key at the initial boot screen from the Woody CD#1, I decided to try it. At the boot: prompt I typed bf24 and sent the install on its way. Answered all the questions, made a boot floppy, and rebooted using said boot floppy. Result: the new boot floppy was identical to the original; my kernal was still 2.2.xx-idepci Why didn't I get the bf24 kernal? Maybe 2.4 is installed on your hard disk, but 2.2.20idepci was used for the boot floppy. What is the name of the kernel image in /boot? It should be vmlinuz-2.4.18-bf2.4. If it is, you can create a new boot floppy using that kernel. You can also choose only to install the boot loader on the floppy disk, but use the kernel from the hard disk, by telling lilo to use /dev/fd0 as the boot device. Or you install the bootloader in your MBR and don't use the floppy at all. best regards Andreas Janssen All of the files in /boot are 2.2.20 version, so none of the bf24 kernel was installed. What are some of the gotchas that could be causing it to ignore the bf24 input to boot:? Thanks Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install confusion
Andreas Janssen wrote: Hello Paul Schwartz (<[EMAIL PROTECTED]>) wrote: After reading about using the F3 key at the initial boot screen from the Woody CD#1, I decided to try it. At the boot: prompt I typed bf24 and sent the install on its way. Answered all the questions, made a boot floppy, and rebooted using said boot floppy. Result: the new boot floppy was identical to the original; my kernal was still 2.2.xx-idepci Why didn't I get the bf24 kernal? Maybe 2.4 is installed on your hard disk, but 2.2.20idepci was used for the boot floppy. What is the name of the kernel image in /boot? It should be vmlinuz-2.4.18-bf2.4. If it is, you can create a new boot floppy using that kernel. You can also choose only to install the boot loader on the floppy disk, but use the kernel from the hard disk, by telling lilo to use /dev/fd0 as the boot device. Or you install the bootloader in your MBR and don't use the floppy at all. best regards Andreas Janssen All of the files in /boot are 2.2.20 version, so none of the bf24 kernel was installed. What are some of the gotchas that could be causing it to ignore the bf24 input to boot:? Thanks Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install confusion
Andreas Janssen wrote: Hello Maybe 2.4 is installed on your hard disk, but 2.2.20idepci was used for the boot floppy. What is the name of the kernel image in /boot? It should be vmlinuz-2.4.18-bf2.4. If it is, you can create a new boot floppy using that kernel. You can also choose only to install the boot loader on the floppy disk, but use the kernel from the hard disk, by telling lilo to use /dev/fd0 as the boot device. Or you install the bootloader in your MBR and don't use the floppy at all. All of the files in /boot are 2.2.20 version, so none of the bf24 kernel was installed. What are some of the gotchas that could be causing it to ignore the bf24 input to boot:? Honestly, I don't know. But you still can install a 2.4 Kernel on your system without reinstalling. Make sure security.debian.org is in your sources.list, and run apt-get istall kernel-image-2.4.18-bf2.4 to install the 2.4 installation kernel apt-get install kernel-image-2.4.18-1-686 to install the image for pentium II and later systems. There are also images for 386, 586, k6 and k7 systems. If you don't use the bf kernel, make sure you tell lilo to use the initrd for the kernel you installed. Your current kernel will not be removed and can be loaded by selecting "LinuxOld" from within the lilo startscreen. You maybe want to uncomment the "#promt" line in your lilo.conf as well. best regards Andreas Janssen Thanks for the help. I will try your suggestions. I am just trying to understand what is going on. While somewhat frustrating, the process is also very educational. Right now I am booting from floppy because I don't want to screw up my legacy system [OS/2 4.52 which uses a Boot Manager and LVM. I think it can be sensitive to changes in boot stuff] until I have the Debian system working to some minimal level of completeness. Thanks again. Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install confusion
Andreas Janssen wrote: Hello Paul Schwartz (<[EMAIL PROTECTED]>) wrote: Right now I am booting from floppy because I don't want to screw up my legacy system [OS/2 4.52 which uses a Boot Manager and LVM. I think it can be sensitive to changes in boot stuff] until I have the Debian system working to some minimal level of completeness. As I already wrote, you can install lilo on floppy, but use the kernel from the hard disk It is installed in /boot anyway. This way, your boot loader for OS/2 and other OS partitions will not be touched. This way, booting will also be much faster. Try lilo -b /dev/fd0 best regards Andreas Janssen Thanks again. I was a little dense on the first hint, but I think I understand now. I am installing the 2.4.18 kernel as I write and will put lilo on a floppy when that is done. I feel better already :-) Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
help with lilo diagnostics
I'm trying to make the diagnostic diskette as suggested in the lilo documentation. Executing "make -f Makefile.floppy" from /usr/lib/lilo results in make: nothing to be done for `floppy' What to do? Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Why doesn't pon execute in xterm window
If I execute pon [as root or su] in a console session it works. If I do it in an xterm window [using kde and as su] it comes backwith a new prompt but it doesn't do anything. What am I doing wrong? TIA Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't pon execute in xterm window
s. keeling wrote: Incoming from Paul Schwartz: If I execute pon [as root or su] in a console session it works. If I do it in an xterm window [using kde and as su] it comes backwith a new prompt but it doesn't do anything. What am I doing wrong? Nothing. That's the way it's supposed to work. Now, add yourself to group ppp and you can do it as a user too. "adduser $user ppp" It doesn't seem to have anything to do with group ownership. I did those things, and it still doesn't work. Note that even as root [after su] it doesn't work in the xterm window.. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't pon execute in xterm window
s. keeling wrote: Incoming from Paul Schwartz: s. keeling wrote: Incoming from Paul Schwartz: If I execute pon [as root or su] in a console session it works. If I do it in an xterm window [using kde and as su] it comes backwith a new prompt but it doesn't do anything. What am I doing wrong? Nothing. That's the way it's supposed to work. Now, add yourself to group ppp and you can do it as a user too. "adduser $user ppp" It doesn't seem to have anything to do with group ownership. I did those things, and it still doesn't work. Note that even as root [after su] it doesn't work in the xterm window.. First, my advice was wrong; it's not group ppp, it's dialout and dip. Second, ... what?!? As root, at the console, pon works, but "su -c pon" from an xterm doesn't work?!? That can't be. That's basically what happens. In the xterm [under kde] su password: pon just returns another prompt. At a console as root, pon connects to my isp. And yes, I did use the dip group. Even though the user is a member of dip he can't successfully execute pon [even in a console]. So, it seems reasonable for it to be impossible, but it happens. What could be wrong? Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Why doesn't pon execute in xterm window
Robert Storey wrote: Dear Paul, Did you trying setting /usr/sbin/pppoe as suid root? chmod +s /usr/sbin/pppoe regards, Robert Applied to pon, it solves the problems, but I still don't understand why, before that, the user could execute pon successfully in a console, but not in an xterm window. ? an imponderable? Thanks Paul On Fri, 26 Dec 2003 13:02:53 -0700 paul <[EMAIL PROTECTED]> wrote: Sorry about the thread but this is the first time I'm sending mail from my Debian box, and clicking the reply to at the bottom of the message in the Konqueror display didn't bring anything with it. I have followed the earlier suggestions; adding the dialout group really helped, but ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problem with menuconfig
I'm trying to build a kernel. Do 'make menuconfig' in an xterm window, and it comes back >>Unable to find the Ncurses libraries The following are installed [Woody] libncurses5 ncurses-base ncurses-bin ncurses-term Why can't it be found? TIA Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with menuconfig
Andy Firman wrote: On Mon, Dec 29, 2003 at 11:47:31AM -0700, Paul Schwartz wrote: I'm trying to build a kernel. Do 'make menuconfig' in an xterm window, and it comes back Unable to find the Ncurses libraries The following are installed [Woody] libncurses5 ncurses-base ncurses-bin ncurses-term Why can't it be found? You need: libncurses5-dev Thanks to all. The description given in kpackage didn't seem like that would be the solution. Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lost dhcp on boot up
I just made and installed my first kernel [2.4.18]! and booted too! One problem is that the network initialization that used to occur [2.4.18-bf24] doesn't. The ether net card is recognized but my machine no longer does an inquiry to the router to get an address. Where do I find the stimulus? Nother issue: I thought I was compiling the ALSA driver into the kernel, but dmesg says No ALSA driver installed Starting ALSA sound driver (version none): modprobe: Can't lodcate module snd failed On the other hand sound is now working for the first time. Any idea what happened? Thanks Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lost dhcp on boot up
Jan Minar wrote: On Thu, Jan 01, 2004 at 09:49:00AM -0700, Paul Schwartz wrote: I just made and installed my first kernel [2.4.18]! and booted too! One problem is that the network initialization that used to occur [2.4.18-bf24] doesn't. The ether net card is recognized but my machine no longer does an inquiry to the router to get an address. The dhcp on bootup is used only if you want to mount the root filesystem over network. See the kernel docs for details. The userspace configuration is done in /etc/init.d/network, and /etc/network/*. Look for dhcp in interfaces(5). dhcp is specified for eth0 in the interfaces file. nothing seems to happen. Where do I look for an error message? Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: lost dhcp on boot up
Try dhclient(8) manually from the command line. If that doesn't work, try spying on the connection using tcpdump(8). Punch your firewall properly. That's what I'd do. And please post the useful bits verbatim (e.g. that interfaces entry--who says it's not malformed?). The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8). I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient I tried to paste but :-( ; it's in attachment tcppkt.txt [it doesn't sya anything interesting to me] The /etc/network/interfaces file is also attached. There were no errors related to dhcp or eth0 in dmesg or messages I'll be glad to to try other suggestions. Thanks Paul 20:52:40.587070 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:42.590011 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:44.593076 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:46.596145 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:48.599259 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:50.602308 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:52.605540 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:54.608555 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:56.611514 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:52:58.614579 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:00.617662 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:02.620725 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:04.623806 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:06.626870 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:08.630086 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 20:53:10.633019 802.1d config 8000.02:08:0d:82:35:5e.8001 root 8000.02:08:0d:82:35:5e pathcost 0 age 0 max 8 hello 2 fdelay 5 # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation auto eth0 iface eth0 inet dhcp
Re: Re: Re: lost dhcp on boot up
On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote: >Try dhclient(8) manually from the command line. If that doesn't work, >try spying on the connection using tcpdump(8). Punch your firewall >properly. That's what I'd do. And please post the useful bits verbatim >(e.g. that interfaces entry--who says it's not malformed?). > >The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8). > I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient Great! Now we know there is no DHCP traffic going out your box. Only some 802.1d bridge stuff. Bingo. The configs look fine. I'll be glad to to try other suggestions. Go through the thread, and apply the suggestions already made :-) E.g.: % ifconfig a % ip l % ip a % ip r And: what was the dhclient's commandline? (Read: Was it correct?) And tcpdump's. Post _with_ invocations. So again: # dhclient -d eth0 # tcpdump -i eth0 -- Jan Minar "Please don't CC me, I'm subscribed." x 6 Thanks for your patience. This is really a response the way you requested. I understand the value of that and was preparing it, when I found a message in the daemon.log with a dhclient complaint. [I can't quote it here because I'm on another machine]. It pointed out the need for CONFIG_PACKET and CONFIG_FILTER in the kernel compilation. My kernel has the first but not the second. I'm off to fix that before proceeding with the rest. I'll be back! Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lost dhcp on boot up
Paul Schwartz wrote: On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote: >Try dhclient(8) manually from the command line. If that doesn't work, >try spying on the connection using tcpdump(8). Punch your firewall >properly. That's what I'd do. And please post the useful bits verbatim >(e.g. that interfaces entry--who says it's not malformed?). > >The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8). > I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient Great! Now we know there is no DHCP traffic going out your box. Only some 802.1d bridge stuff. Bingo. The configs look fine. I'll be glad to to try other suggestions. Go through the thread, and apply the suggestions already made :-) E.g.: % ifconfig a % ip l % ip a % ip r And: what was the dhclient's commandline? (Read: Was it correct?) And tcpdump's. Post _with_ invocations. So again: # dhclient -d eth0 # tcpdump -i eth0 -- Jan Minar "Please don't CC me, I'm subscribed." x 6 Thanks for your patience. This is really a response the way you requested. I understand the Oops. I meant NOT. value of that and was preparing it, when I found a message in the daemon.log with a dhclient complaint. [I can't quote it here because I'm on another machine]. It pointed out the need for CONFIG_PACKET and CONFIG_FILTER in the kernel compilation. My kernel has the first but not the second. I'm off to fix that before proceeding with the rest. I'll be back! Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lost dhcp on boot up
Paul Schwartz wrote: Paul Schwartz wrote: On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote: >Try dhclient(8) manually from the command line. If that doesn't work, >try spying on the connection using tcpdump(8). Punch your firewall >properly. That's what I'd do. And please post the useful bits verbatim >(e.g. that interfaces entry--who says it's not malformed?). > >The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8). > I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient Great! Now we know there is no DHCP traffic going out your box. Only some 802.1d bridge stuff. Bingo. The configs look fine. I'll be glad to to try other suggestions. Go through the thread, and apply the suggestions already made :-) E.g.: % ifconfig a % ip l % ip a % ip r And: what was the dhclient's commandline? (Read: Was it correct?) And tcpdump's. Post _with_ invocations. So again: # dhclient -d eth0 # tcpdump -i eth0 -- Jan Minar "Please don't CC me, I'm subscribed." x 6 Thanks for your patience. This is really a response the way you requested. I understand the Oops. I meant NOT. that is, NOT the way you requested ;-) value of that and was preparing it, when I found a message in the daemon.log with a dhclient complaint. [I can't quote it here because I'm on another machine]. It pointed out the need for CONFIG_PACKET and CONFIG_FILTER in the kernel compilation. My kernel has the first but not the second. I'm off to fix that before proceeding with the rest. I'll be back! Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lost dhcp on boot up
Paul Schwartz wrote: Paul Schwartz wrote: Paul Schwartz wrote: On Thu, Jan 01, 2004 at 09:11:39PM -0700, Paul Schwartz wrote: >Try dhclient(8) manually from the command line. If that doesn't work, >try spying on the connection using tcpdump(8). Punch your firewall >properly. That's what I'd do. And please post the useful bits verbatim >(e.g. that interfaces entry--who says it's not malformed?). > >The error messages are dmesg(8), ip(8)/ifconfig(8), tcpdump(8). > I tried executing dhclient; it just returns a prompt. This is what tcpdump collects from eth0 when I execute dhclient Great! Now we know there is no DHCP traffic going out your box. Only some 802.1d bridge stuff. Bingo. The configs look fine. I'll be glad to to try other suggestions. Go through the thread, and apply the suggestions already made :-) E.g.: % ifconfig a % ip l % ip a % ip r And: what was the dhclient's commandline? (Read: Was it correct?) And tcpdump's. Post _with_ invocations. So again: # dhclient -d eth0 # tcpdump -i eth0 -- Jan Minar "Please don't CC me, I'm subscribed." x 6 Thanks for your patience. This is really a response the way you requested. I understand the Oops. I meant NOT. that is, NOT the way you requested ;-) value of that and was preparing it, when I found a message in the daemon.log with a dhclient complaint. [I can't quote it here because I'm on another machine]. It pointed out the need for CONFIG_PACKET and CONFIG_FILTER in the kernel compilation. My kernel has the first but not the second. I'm off to fix that before proceeding with the rest. I'll be back! Paul Problem solved. Recompiling with CONFIG_FILTER set lets dhcp work. I think they ought to change the recommendation in menuconfig; it kind of says it's not important and to set it to N if you're not sure. Doesn't seem like a good choice; it oughtto at least mention its need for dhcp. Thanks to all for the help. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fax, voice, and data answering
Christian Schnobrich wrote: On Sat, 2004-01-10 at 17:32, D. Clarke wrote: I'd like to be able to have a voicemail box, fax, and possibly (although not required) ppp dialup. First, you need something to pick up the line and distinguish wether it is voice, fax or data, and then call the appropriate service. IIRC vgetty is your friend here. ppp dialup will be the easiest of them. Search the web for the "Linux Network Administator Guide". When it comes to faxing under linux, Hylafax is apparently the most common means to do so. It's a full blown client/server setup capable of handling as many faxmodems as you can connect to a single machine, sending on all lines 24/7 -- in short, much more than you are likely to need. However, looking for a smaller solution, I came across "mgetty and sendfax" -- but, I had no luck at all with it. I can't quite remember any more, but it was something very fundamental. I don't know any voice applications -- not my field of interest. cu, Schnobs mgetty/sendfax require a class 2 or 2.0 fax modem. Many are just class 1. There are many interesting examples and addons for vgetty. I have played with some of the simpler ones. If you aren't doing something standard it can get difficult. Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Migration of Knoppix capability
I have a Debian 2.4.18 kernel in which I enabled HPFS support and support for my scsi card [Tekram 390]. On boot the scanner attached to the scsi card is not recognized and I can't mount one of my HPFS partitions. If I boot Knoppix, I can scan and I can look at the HPFS partitions. How do I transfer that capability to my kernel in a way that I can continue to support it? Thanks for the advice. Paul Schwartz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KPM update failure
I tried to update the KPM list [running woody] and got the following error Reading Package Lists... Error! E: Dynamic MMap ran out of room E: Error occured while processing xvfb (NewVersion1) E: Problem with MergeList /var/lib/apt/lists/ftp.de.debian.org_debian_dists_.._project_experimental_main_binary-i386_Packages E: The package lists or status file could not be parsed or opened. RESULT=100 Done this many times before with success. Any help is appreciated. Paul Schwartz __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: KPM update failure
> > >Please tell me that you spent at least 5 seconds on Goole looking for >this. I am not taking this out on you personally, but at least once >month for the past couple of years someone has posted to this list with >the same error. Please just Google for "Dynamic MMap ran out of room" >and follow the instructions on one of the many hits that will result. > >-Roberto > >-- >Roberto C. Sanchez > Thanks for the hint! I had Googled for "debian kpm update failure dynamic memory" but that pulled in nothing relevant. So I came here. Thanks again. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
