Re: Continuing saga of xorg restarts
On Tue, Jul 03, 2007 at 03:26:29PM -0700, Andrew Sackville-West wrote: > but that is induced by a very specific situation: dragging an active > mplayer window from my left-hand screen to my right hand-screen (which > gives me a blank mplayer frame) and then dragging it back. crashes > every time. I can always crash X by saving my VLC hotkey preferences. Before I report, may I assume that you (like myself) are using Lenny and the latest software from debian-multimedia? -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Continuing saga of xorg restarts
On Tue, Jul 03, 2007 at 12:39:05PM -0400, Carl Fink wrote: > On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote: > [much snipping] > > > I've seen some xorg crashes lately too... mostly caused by mplayer, > > but not reliably. I'll grab my backtrace too. > > > contact the xorg team (Debian X strike force?) and see what they > > say... > > I'll wait until you have a backtrace and we can give them more information > in a single package. Meanwhile I'll try booting Knoppix tonight and see if > I get X crashes there. (I want to eliminate the possibility of hardware > failures.) here's mine: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591] 1: /lib/i686/cmov/libc.so.6 [0xb7ddce08] 2: /usr/bin/X11/X [0x80ddae5] 3: /usr/bin/X11/X(miHandleValidateExposures+0x78) [0x813b828] 4: /usr/bin/X11/X(miMoveWindow+0x290) [0x813c1a0] 5: /usr/bin/X11/X(ConfigureWindow+0x6b7) [0x807c517] 6: /usr/bin/X11/X(ProcConfigureWindow+0xa1) [0x808e4c1] 7: /usr/bin/X11/X(PanoramiXConfigureWindow+0x1a6) [0x8150c86] 8: /usr/bin/X11/X [0x8154a21] 9: /usr/bin/X11/X(Dispatch+0x19f) [0x808ed3f] 10: /usr/bin/X11/X(main+0x495) [0x8076e85] 11: /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7dc8ebc] 12: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] Fatal server error: Caught signal 11. Server aborting but that is induced by a very specific situation: dragging an active mplayer window from my left-hand screen to my right hand-screen (which gives me a blank mplayer frame) and then dragging it back. crashes every time. I tried to induce the crash by iterating through a bunch of avi's with mplayer, but it wouldn't go in the time allotted. i'll try again later. hth A signature.asc Description: Digital signature
Re: Continuing saga of xorg restarts
On Tue, Jul 03, 2007 at 08:29:40AM -0700, Andrew Sackville-West wrote: [much snipping] > I've seen some xorg crashes lately too... mostly caused by mplayer, > but not reliably. I'll grab my backtrace too. > contact the xorg team (Debian X strike force?) and see what they > say... I'll wait until you have a backtrace and we can give them more information in a single package. Meanwhile I'll try booting Knoppix tonight and see if I get X crashes there. (I want to eliminate the possibility of hardware failures.) -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Continuing saga of xorg restarts
On Mon, Jul 02, 2007 at 11:07:04PM -0400, Carl Fink wrote: > Per Andrew's advice, I started X in VT1 using startx. During each of the > multiple xorg crashes today (!) I got this: > > > > Backtrace: > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591] > 1: [0xb7f36420] > 2: /usr/bin/X11/X [0x80ddae5] > 3: /usr/bin/X11/X(miHandleValidateExposures+0x78) [0x813b828] > 4: /usr/bin/X11/X(MapWindow+0x3aa) [0x807b6da] > 5: /usr/bin/X11/X(ProcMapWindow+0x59) [0x808e689] > 6: /usr/bin/X11/X [0x8154a21] > 7: /usr/bin/X11/X(Dispatch+0x19f) [0x808ed3f] > 8: /usr/bin/X11/X(main+0x495) [0x8076e85] > 9: /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d49ebc] > 10: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] > > Fatal server error: > Caught signal 11. Server aborting > > xinit: connection to X server lost. > I've seen some xorg crashes lately too... mostly caused by mplayer, but not reliably. I'll grab my backtrace too. > > I will confess that I have no idea what to do with that. Item 10 almost > seems to imply a font problem, but I suspect that's just a red herring. As > before, any suggestions appreciated. contact the xorg team (Debian X strike force?) and see what they say... A signature.asc Description: Digital signature
Re: Continuing saga of xorg restarts
Switching from icewm to fluxbox didn't make any difference. Now I can kill X just by having VLC *open* and task-switching from iceweasel to the open vlc window using alt-tab. This is ludicrous. -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Continuing saga of xorg restarts
Per Andrew's advice, I started X in VT1 using startx. During each of the multiple xorg crashes today (!) I got this: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591] 1: [0xb7f36420] 2: /usr/bin/X11/X [0x80ddae5] 3: /usr/bin/X11/X(miHandleValidateExposures+0x78) [0x813b828] 4: /usr/bin/X11/X(MapWindow+0x3aa) [0x807b6da] 5: /usr/bin/X11/X(ProcMapWindow+0x59) [0x808e689] 6: /usr/bin/X11/X [0x8154a21] 7: /usr/bin/X11/X(Dispatch+0x19f) [0x808ed3f] 8: /usr/bin/X11/X(main+0x495) [0x8076e85] 9: /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d49ebc] 10: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] Fatal server error: Caught signal 11. Server aborting xinit: connection to X server lost. I will confess that I have no idea what to do with that. Item 10 almost seems to imply a font problem, but I suspect that's just a red herring. As before, any suggestions appreciated. -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Continuing saga of xorg restarts
xOn Mon, Jul 02, 2007 at 11:00:19AM -0700, Andrew Sackville-West wrote: > On Sun, Jul 01, 2007 at 08:33:43PM -0400, Carl Fink wrote: > > I tried switching to VLC. I was resetting the hotkeys, clicked Save, and > > xorg restarted. > > how are you start X? xdm > have you looked in .Xsession-errors? No relevant messages. > anything showing in the VT from which X was started (usually VT-1 if > using *dm). No. I'll manually start X from a vt when/if this happens again and use script(1) to record all messages. > .Xsession-errors gets re-written when you log in so, don't log back > in. instead switch to a VT and see what you can find. Oh. Didn't know that. > or start X with startx so you can keep it from re-starting (you'll > just drop back to the shell when X dies). Then you can examine the > onscreen messages and the logs. you might want to use tee with your > startx to capture stuff that might otherwise scroll off the screen > during your session. I'll give that a try, as mentioned above. > > I'm utterly unfamiliar with the internals of X. What would VLC have been > > doing when I clicked Save that would cause a xorg restart? > > who knows, but I've seen it happen a few times in sid with various > things. Usually there is some kind of trail in the logs. Thanks for the tip. I do appreciate it. -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Continuing saga of xorg restarts
On Sun, Jul 01, 2007 at 08:33:43PM -0400, Carl Fink wrote: > I tried switching to VLC. I was resetting the hotkeys, clicked Save, and > xorg restarted. how are you start X? have you looked in .Xsession-errors? anything showing in the VT from which X was started (usually VT-1 if using *dm). .Xsession-errors gets re-written when you log in so, don't log back in. instead switch to a VT and see what you can find. or start X with startx so you can keep it from re-starting (you'll just drop back to the shell when X dies). Then you can examine the onscreen messages and the logs. you might want to use tee with your startx to capture stuff that might otherwise scroll off the screen during your session. > > I'm utterly unfamiliar with the internals of X. What would VLC have been > doing when I clicked Save that would cause a xorg restart? who knows, but I've seen it happen a few times in sid with various things. Usually there is some kind of trail in the logs. A signature.asc Description: Digital signature
Continuing saga of xorg restarts
I tried switching to VLC. I was resetting the hotkeys, clicked Save, and xorg restarted. I'm utterly unfamiliar with the internals of X. What would VLC have been doing when I clicked Save that would cause a xorg restart? -- Carl Fink [EMAIL PROTECTED] Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Java not working, the continuing saga
With netbeans not working, wanted to try Eclipse. Installed all that stuff which also installed a Blackdown JRE and Kaffe. The stuff would not configure so I removed it. Also needed to get rid of a conf file for Kaffe and change a symlink to that in /usr/bin. Did all that, cleaning up with more effort than apt-get remove should have left over. Now, any call to Java yields the message: Error occurred during initialization of VM java/lang/NoClassDefFoundError: java/lang/Object OpenOffice and Jazz continue to work so they must be self-contained. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hotplug: The Continuing Saga
David Baron wrote: I think this module is getting crazier with every update. Last two versions on bootup, "unknown interface sit0:-hotplug" Last version: More repeated module loads AND repeated listings of blacklisted modules (some of which were blacklisted to clean up the repeated listings) :-) Good old (new for 2.6 kernels) uhci-hcd still hangs up on shutdown. I have it blacklisted so I can shutdown correctly. (Can live without the USB-MIDI interface for now.) This is apparently a kernel, not a hotplug problem since I tried this with usbmgr as well. I'm seeing similar things :-( Jaap -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hotplug: The Continuing Saga
I think this module is getting crazier with every update. Last two versions on bootup, "unknown interface sit0:-hotplug" Last version: More repeated module loads AND repeated listings of blacklisted modules (some of which were blacklisted to clean up the repeated listings) :-) Good old (new for 2.6 kernels) uhci-hcd still hangs up on shutdown. I have it blacklisted so I can shutdown correctly. (Can live without the USB-MIDI interface for now.) This is apparently a kernel, not a hotplug problem since I tried this with usbmgr as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: The Continuing Saga of the Kernel that Now Boots, but doesn't Work
On Fri, 2002-03-01 at 18:39, Timothy R. Butler wrote: > Hi everyone, > Anyone who has been following the threads "Linux Progress Patch (Splash > Screen)" and "The Kernel that Wouldn't Boot," have probably gotten really > tired of hearing about my little kernel. > Well, hopefully I'll finally have it fixed soon, so not to worry. :-) > Anyway, my kernel now boots, but many of the modules have undefined symbols. > I have tried rebuilding the modules. As an example, here is the output I get > if I try to initialize my mouse (insmod'ing hid, mousedev, usb-uhci, etc.): > > > /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol > usb_free_dev_Ra38257d3 > /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol snip I've had problems compiling kernels when I've compiled for SMP and later tried to build an UP kernel from the same tree. Make clean did not get rid of all the SMP cruft. So try this: 1. delete this kernel tree 2. Get the 2.4.17 tar ball and signature file. You need GnuPG setup to check the signature. Basically, download the kernel GPG signature into your local keyring. Then you can verify the tar ball is good. Otherwise, check it with gunzip -vt or bunzip2 -vt. 3. Apply your patch and make sure it applied correctly. Save the output from patch. 4. make mrproper 5. make clean 6. make menuconfig 7. If you want multiple versions of the same kernel, i.e. compiled with different options, edit Makefile and change subversion. If you don't do this then make modules_install will overwrite your /lib/modules/2.4.17 dir tree. 7. make dep 8. make bzImage 9. make modules 10. If a /lib/modules/ dir exists delete it before running make modules_install. 11. copy arch/i386/boot/bzImage to /boot/vmlinuz- and setup lilo or grub. I also copy System.map & .config After booting the new kernel make sure your modules config is setup properly in /etc. If you change any module config remember to run update-modules. hope this helps scott [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
The Continuing Saga of the Kernel that Now Boots, but doesn't Work
Hi everyone, Anyone who has been following the threads "Linux Progress Patch (Splash Screen)" and "The Kernel that Wouldn't Boot," have probably gotten really tired of hearing about my little kernel. Well, hopefully I'll finally have it fixed soon, so not to worry. :-) Anyway, my kernel now boots, but many of the modules have undefined symbols. I have tried rebuilding the modules. As an example, here is the output I get if I try to initialize my mouse (insmod'ing hid, mousedev, usb-uhci, etc.): /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_free_dev_Ra38257d3 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_alloc_dev_R3de451b1 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_alloc_bus_Rd5e77c95 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_disconnect_R0e758546 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_root_hub_string_Ra68718f0 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_deregister_bus_R7a42cf83 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_connect_R2f51819d /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_free_bus_Rf4f5a2ee /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_release_bandwidth_Rcc078125 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_check_bandwidth_R9639de08 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_claim_bandwidth_Ra1b10bd6 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_inc_dev_use_R78f0ab93 /lib/modules/2.4.17/kernel/drivers/usb/usb-uhci.o: unresolved symbol usb_register_bus_Raec0cc71 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol __usb_get_extra_descriptor_R9924c496 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_get_class_descriptor_Rb2abb0a4 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_set_idle_R0fda4abb /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_string_R0d8eda51 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_submit_urb_R6c25b636 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_get_report_Rddda010c /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_deregister_R82431a02 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_register_Rd8ebc9e3 /lib/modules/2.4.17/kernel/drivers/usb/hid.o: unresolved symbol usb_unlink_urb_R6fa525ad Needless to say, this means USB doesn't work. Any ideas on what I might be doing wrong that would cause such a nasty set of errors? It seems a number of other modules suffer the same type of errors, running depmod -a returns this: depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/arch/i386/kernel/apm.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/arch/i386/kernel/cpuid.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/arch/i386/kernel/microcode.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/arch/i386/kernel/msr.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/ac_adapter/ospm_ac_adapter.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/battery/ospm_battery.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/busmgr/ospm_busmgr.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/button/ospm_button.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/processor/ospm_processor.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/system/ospm_system.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/acpi/ospm/thermal/ospm_thermal.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/cciss.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/cpqarray.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/floppy.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/loop.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/nbd.odepmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/paride/paride.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/paride/pcd.o depmod: *** Unresolved symbols in /lib/modules/2.4.17/kernel/drivers/block/paride/pd.o That's about an eighth of the total errors output by depmod -a. I'm open (and would *definately* welcome) suggestions. Err... perhaps that was
RE: Continuing saga...
I believe cua* was dropped somewhere along the 2.1.x series... Its gone with 2.2.x On Fri, 16 Apr 1999, Fabio Olive leite wrote: > Hi there, > > ] (the ttyS* and cua* devices are hardware-equivalent, but if I'm > ] not mistaken using the /dev/cua* device is better for dialin, which > ] you might want for a modem). > > Whoah! cua devices have been dropped from Debian (and Linux itself, so to > speak) long ago and their use nowadays is _strongly_ discouraged. They > don't even exist on a recent Debian install. > > There are docs about that somewhere, but I don't recall any URL at the > moment. Just go shopping on your usual Linux docs site. :) > > Cheers! > Fábio > ( Fábio Olivé Leite[EMAIL PROTECTED] ) > ( http://descartes.ucpel.tche.br/~olive ) > ( Linux - Distributed Systems - Fault Tolerance - Security - /etc ) > (BC 50 7F 7A B9 2E 0A 26 91 8A D1 C0 B1 E4 DA A4) > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
RE: Continuing saga...
Hi there, ] (the ttyS* and cua* devices are hardware-equivalent, but if I'm ] not mistaken using the /dev/cua* device is better for dialin, which ] you might want for a modem). Whoah! cua devices have been dropped from Debian (and Linux itself, so to speak) long ago and their use nowadays is _strongly_ discouraged. They don't even exist on a recent Debian install. There are docs about that somewhere, but I don't recall any URL at the moment. Just go shopping on your usual Linux docs site. :) Cheers! Fábio ( Fábio Olivé Leite[EMAIL PROTECTED] ) ( http://descartes.ucpel.tche.br/~olive ) ( Linux - Distributed Systems - Fault Tolerance - Security - /etc ) (BC 50 7F 7A B9 2E 0A 26 91 8A D1 C0 B1 E4 DA A4)
Re: Continuing saga...
On Fri, 16 Apr 1999, Small, Bradley wrote: > Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me > I do when I run His OS. Try as I might I can't seem to convince Linux that > it is there. I assume that I should be using wvdial and when it ran the > configuration utility it said that it didn't detect any modem. So I read the > man page and setup the wvdial.conf file. I pointed it to each /dev/ttySn > 0,1, 2, 3, 4, 5, 6, 7, 8, 9 with no real difference except that 0 threw a > different kind of error. Do I need o do something else to even have my modem > there? Is wvdial the thing I need to be using anyway? Com 1 = ttyS0 (could it be perhaps a Winmodem) If so, you're out of luck. > > Problem #2, I have a Canon BJ4300. Where do I even begin to get support for > this? Install magicfilter and choose the bjc600 (limited to 360x360, iirc). Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
RE: Continuing saga...
On 16-Apr-99 Small, Bradley wrote: >>You may well have the modem on /dev/ttyS0 = COM1, but you probably also >>have your mouse there as well. In that case you are likely to hit >>interrupt conflicts, and Linux will only see one of the devices. > > I don't think so, since my mouse is a "ps/2" mouse rather than a serial > mouse. It could possibly be, but how would I tell. In that case you should have /dev/mouse -> /dev/psaux and no conflict should arise; so probably Andrei Ivanov's diagnosis is correct; and you should try his suggestions. Best of luck! Ted. E-Mail: (Ted Harding) <[EMAIL PROTECTED]> Date: 16-Apr-99 Time: 15:48:40 -- XFMail --
RE: Continuing saga...
>You may well have the modem on /dev/ttyS0 = COM1, but you probably also >have your mouse there as well. In that case you are likely to hit >interrupt conflicts, and Linux will only see one of the devices. I don't think so, since my mouse is a "ps/2" mouse rather than a serial mouse. It could possibly be, but how would I tell. -- snip -- I will look at your other suggestions when I am back at my box.. B
Re: Continuing saga...
> > Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me > I do when I run His OS. Try as I might I can't seem to convince Linux that > it is there. I assume that I should be using wvdial and when it ran the > configuration utility it said that it didn't detect any modem. So I read the > man page and setup the wvdial.conf file. I pointed it to each /dev/ttySn > 0,1, 2, 3, 4, 5, 6, 7, 8, 9 with no real difference except that 0 threw a > different kind of error. Do I need o do something else to even have my modem > there? Is wvdial the thing I need to be using anyway? And the word is yes. But you need a program called isapnp. If your computer does not see the modem, it means that modem is not initialized. Which in turn means that it is either pnp or win. If it's Win, you are screwed. If it's pnp, then you need to get isapnp. It's a program that will initialize ISA PnP cards at boot time. For a procedure how to do it look on my page, URL below. > > Problem #2, I have a Canon BJ4300. Where do I even begin to get support for > this? Sorry, no idea about that one Andrei --- Andrei S. Ivanov [EMAIL PROTECTED] UIN 12402354 http://members.tripod.com/AnSIv <--Little things for Linux.
RE: Continuing saga...
On 16-Apr-99 Small, Bradley wrote: > > Problem #1, I have a modem on Com1. I know I do because Bill Gates > tells me I do when I run His OS. Try as I might I can't seem to > convince Linux that it is there. I assume that I should be using > wvdial and when it ran the configuration utility it said that it > didn't detect any modem. So I read the man page and setup the > wvdial.conf file. I pointed it to each /dev/ttySn > 0,1, 2, 3, 4, 5, 6, 7, 8, 9 with no real difference except that 0 threw > a different kind of error. You may well have the modem on /dev/ttyS0 = COM1, but you probably also have your mouse there as well. In that case you are likely to hit interrupt conflicts, and Linux will only see one of the devices. Suggestion: either move your mouse to /dev/ttyS1 -- plug into the COM2 port, then rm /dev/mouse ln -s /dev/ttyS1 /dev/mouse or move your modem to COM2 (may involve changing jumper settings; I don't know what to do if the modem is PnP), then rm /dev/modem ln -s /dev/ttyS1 /dev/modem or (perhaps better -- comments from others advisable here): ln -s /dev/cua1 /dev/modem (the ttyS* and cua* devices are hardware-equivalent, but if I'm not mistaken using the /dev/cua* device is better for dialin, which you might want for a modem). Hope this helps, Ted. E-Mail: (Ted Harding) <[EMAIL PROTECTED]> Date: 16-Apr-99 Time: 14:55:31 -- XFMail --
Continuing saga...
Hi y'all and thanks for all the help so far.. Now I have X windows up and well it is cool so far. Just so everyone knows, when you D/L and install 3.3.3.1 of XFree86 you must also D/L the stuff in their "Servers" directory. Soon as I got the new SVGA server things got much better. Problem #1, I have a modem on Com1. I know I do because Bill Gates tells me I do when I run His OS. Try as I might I can't seem to convince Linux that it is there. I assume that I should be using wvdial and when it ran the configuration utility it said that it didn't detect any modem. So I read the man page and setup the wvdial.conf file. I pointed it to each /dev/ttySn 0,1, 2, 3, 4, 5, 6, 7, 8, 9 with no real difference except that 0 threw a different kind of error. Do I need o do something else to even have my modem there? Is wvdial the thing I need to be using anyway? Problem #2, I have a Canon BJ4300. Where do I even begin to get support for this? B ___ Bradley M. Small, Developer/Analyst New Breed Corporations Email:[EMAIL PROTECTED] Information Systems Group Phone: 336-856-2079 x 275 Fax: 336-315-9018
Continuing Saga: olwm and xdm
Hi Obi, Hi Everyone - Obi wrote: > I'm using olvwm & xdm with no problem ... I never set up any enviroment > variable to make it work ... I guess you are doing something wrong with your > .xsession file or .Xresources or something during the session startup. xdm is > looking at .xsession while startx is looking at .xinitrc (if I don't remember > wrong: I'm not using anymore startx). mmmhhh, ok, so I disabled .Xresources and .xsession and also did *not* set the OLWMMENU environment variable: No luck, though: The workspace menu works with xdm disabled, but fails to work when I log in via xdm. I also checked .xsession-errors and /var/log/xdm-errors, but the first file is empty and the second doesn't say anything suspicious. So, does anyone know of another error file that may contain diagnostic information? Thanks for the help so far! - Reto BTW: The exact package I am using is olvwm_4.1-5.deb - from stable. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
